Posted by Les Toeplitz on December 03, 2015 at 04:59:29:
I'm having trouble again with the wakeup command. Running 494/15.03 on a Windows 2012 Server. I run a job stream every evening using the wakeup command to trigger the process. On a periodic but unpredictable basis the wakeup command fails to recognize the time and just allows the program to initiate. The problem is node specific since I can fire up the program on a different client at the same time I am having the problem and it works. Terminating Comet for a period of time fixes the problem until the next occurrence. The CL1 clock works fine.
Post a Followup
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.