Kbase P172753: PROWIN32 hangs when run as a Scheduled Task in Windows when no-one is logged into the machine
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
02/09/2010 |
|
Status: Unverified
SYMPTOM(s):
PROWIN32 hangs when run as a Scheduled Task in Windows when no-one is logged into the machine
Job executes as expected when user is logged into the machine
Job executes as expected when user is logged into the machine and the machine is locked
Job fails when no users are logged into the machine
PROWIN32 hangs and has to be killed
No error messages are displayed
No error messages appear in the Scheduled Task log file
Client logging shows that warning message 5905 is being generated
**All or part of <widget id> is being placed outside of <parent widget id> by setting <attribute>. (5905)
FACT(s) (Environment):
Using Microsoft Windows Scheduled Tasks
Scheduling PROWIN32.EXE to run periodic batch jobs
User account that runs the job has the "Log on as a batch job" privilege
Progress 9.x
OpenEdge 10.x
Windows
CAUSE:
The Progress session hangs as a result of the unacknowledged 5905 warning. The exact cause of the 5905 warning is unknown at the time of this writing. As the Progress client relies on the system font and resolution when calculating application sizes (see P3432 for more details), it could be supposed that having no user logged into the system impacts upon the available fonts.
FIX:
Add SESSION:SUPPRESS-WARNINGS = TRUE to the code to prevent the 5905 warning