I have a script that opens a capture file and writes to it at different steps throughout the script. This process works great when I manually execute the script. However, when the script is executed by the windows scheduler, the capture file is created but it is empty. Has anyone else ever experienced this problem? Any ideas on why this would happen?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
capture file
- Thread starter ppeel
- Start date
Do you have the Windows Scheduler launching Procomm minimized? I seem to recall that caused a problem for someone in the past, but don't recall the details off the top of my head.
Ah, did a little digging on my site and here is the problem I was thinking of:
A recent problem I experienced had to do with a capture file not containing all of the expected data if Procomm Plus was started in a minimized state. The workaround for this problem was to start Procomm as a regular window, but include the line "winminimize $PWMAINWIN" at the end of the STARTUP.WAS script. This still causes the Procomm Plus splash screen to appear for a short time, but at least no data will be lost.
Ah, did a little digging on my site and here is the problem I was thinking of:
A recent problem I experienced had to do with a capture file not containing all of the expected data if Procomm Plus was started in a minimized state. The workaround for this problem was to start Procomm as a regular window, but include the line "winminimize $PWMAINWIN" at the end of the STARTUP.WAS script. This still causes the Procomm Plus splash screen to appear for a short time, but at least no data will be lost.
- Thread starter
- #3
knob,
I don't know what i changed, but i just made sure the command line was pointing to the right directory. I didn't really think i changed anything. Then i ran it using the scheduler to execute it and it worked. Don't know if it was just a fluke or what. We'll see when it runs tomorrow morning.
Thanks for your help!
I don't know what i changed, but i just made sure the command line was pointing to the right directory. I didn't really think i changed anything. Then i ran it using the scheduler to execute it and it worked. Don't know if it was just a fluke or what. We'll see when it runs tomorrow morning.
Thanks for your help!
- Status