Apache OpenOffice (AOO) Bugzilla – Issue 125578
soffice.exe instances hang when started by program running by windows task scheduler in background
Last modified: 2016-12-22 01:41:54 UTC
Created attachment 83928 [details] Simple VBS script file to reproduce the issue I'm facing some odd problem running some scripts that use OO to convert files, when this scripts are running by Windows task scheduler after upgrade from OO 3.4.1 to OO 4.0.0. We did a lot of tests and figured out that the problem happens when we set the "Run whether user is logged or not" option in the task scheduler. With the "Run whether user is logged or not" on, the soffice.exe and soffice.bin are started but they appears to not responding to script. I wrote a simple sample VBS script code (attached) that basically just create a ServiceManager and record the results in a log file, bellow the sequence of steps to show the problem: 1 save my script file in some temp directory 2 check/correct the log file path 3 create a simple task in Windows Task scheduler to run the script saved in step 1, be sure that the option "Run only when user is logged on" is on (it's the the default configuration for a new task) 4 run the task 5 look at the log file, the message "All OK!" shows that the ServiceManager instance creation was successful 6 update the task created in step 3, and set "Run whether user is logged or not" to on 7 run the task 8 look at the log file, the message "An error occurred" shows that the ServiceManager instance creation was NOT successful ! Running the task with "Run whether user is logged or not" several times result in many instances of soffice.exe and soffice.bin stuck in the system We need use the "Run whether user is logged or not" option because we need to run this scripts on a server. I can reproduce this behaviour in many computers running Windows 7 32 and 64 bits and Windows 2008 R2 I can reproduce the problem not only with VBS scripts, it happens using other programing languages too. The problem DON'T happens with OO 3.4.1, it begins with OO 4.0.0+
.
Just tested with 4.1.2 and the problem persist. I tested running OO 4.1.2 in Windows and the problem is still there.
(In reply to matafagafo from comment #2) > Just tested with 4.1.2 and the problem persist. > > I tested running OO 4.1.2 in Windows and the problem is still there. When it worked with AOO 3.4, was that on the same Windows 7 configuration? (just checking)
(In reply to orcmid from comment #3) > When it worked with AOO 3.4, was that on the same Windows 7 configuration? > > (just checking) Yes, I installed a fresh 3.4 version and it worked (no problems running as a scheduled task). Then I removed the 3.4 version and installed a fresh 4.1 version on the same computer. In the 4.1 version the problem happens. If you need more test, just ask, I'm available to help in this.
The same still happens with AOO 4.1.3 on Windows 10
The best way to narrow down the problem would be to attach a debugger to the hung OO instance and get a stack trace of all threads. Are you able to do that?