Winat scheduler runs all of my other batch files just fine. The problem I have is when I run it with a uudecode program winat will not run. I can run this batch file from command line with no problem or execute it from Winnt Explorer with no problem. Can someone give me a solution?

0

To all you guy's running SP5, as there are known bugs in in this service pack try using SP6, also try removing everything from WinAT and resetting also check all of your batch files, check your services as well. Hope this is of some help David

0

I have a machine running SP6 that WinAT runs fine on. However I have another with SP4 that will not run WinAT for the same batch files (things like cmd.exe and telnet.exe run fine). On the SP4 machine I have moved all the batch files I need to schedule into c:\winnt\system32 which seems to work. Odd observation ... When scheduling cmd.exe on the SP6 machine the command window comes up as c:\winnt\system32\cmd.exe. This window will execute all batch files which I have Path entries for. However, when scheduling cmd.exe on the SP4 machine the command window comes up as c:\winnt\system32\MSTask.exe, which will not recognize any batch files I have written with Path entries ... thus the move to c:\winnt\system32 Also, rights are exactly the same on both machines. Hope this helps ... - Dan

0

Funny after 5 days of desperately seeking I came across this site. I have exactly the same problems, on as well NT 4 SP6 as TSE 4 SP6. Since some time the nightsly reboots, as well as the starting of an other batch doesn't work anymore. I had no idea why, but now I get an error every time. Also when I try to schedule something I have some weird problems Any additional suggestions ? Pls help and send me an email Thanx in advance

0

Hi All you Guys, The world seems to shrink with the web, writting from S.Africa. I am running SP6a on NT Server 4 with the exact problem. I don't have any error messages. for the past two weeks I have had a few good backups. I am running batch files (.bat) from a different partition on the same machine. I have checked all other Servers. The PDC is running backups using WinAt and NtBackup wereas, the first BDC uses BackupExec. Part of the problem here is that on the PDC I have a service called "Task Scheduler" but on the other 3 BDC's I have Scheduler and on all my workstations. I can only assume that the "Task Scheduler" serves the same purpose but because of the problem, I can't help but to think that this problem has to do with the service. All my servers are otherwise Identical. Thanx a Million

0

I have stopped using WINAT and have started using the AT command from the command prompt. Why???? you may ask. WINAT was adding text to the end of some of my commands eg C:\schedules.bat would look like this c:\schedules.bat % Microsof TLS. My experiances started with jobs not running from WINAT. Using all the trouble shooting techniques from white papers and fourms like this has helped my identify the following. The environment I am in is NT 4 Server, SP6A (at) = at command 1. The copy & xcopy commands do not appear to work with (at), even with cmd /c preceeding the command. The del command worked in a batch without needing the cmd /c proceeding the batch file. According to Microsoft documentation this should not be the case as kernal commands require the command interpreter to be activated before they can be run from (at) (hence the cmd /c references). Net result being that not even Microsoft understand how scheduling works. 2. Use the /interactive switch and place pause commands in batch files to create break points. This will allow you to see errors. eg. at 15:35 /interactive /next: c:\test.bat test.bat net stop spooler pause del *.* pause 3. Commands like net start and net stop may benefit from having a wait command placed after them (5 seconds is what I use) to prevent errors. This allows the service to completely stop/start before activating the next command. Please not wait is an ntreskit4 command and is not part of standard nt. 4. Go to the www.askjeeves.com and type winat in the search box. This helped me find lots of whitepapers and fourms on the subject. **********Good Luck****************

0