Issue 104947

Summary: Open Office 31. installed as a service on Vista crashes
Product: App Dev Reporter: paulkt <paul>
Component: apiAssignee: AOO issues mailing list <issues>
Status: CONFIRMED --- QA Contact:
Severity: Trivial    
Priority: P3 CC: issues
Version: 3.3.0 or older (OOo)   
Target Milestone: ---   
Hardware: PC   
OS: Windows Vista   
Issue Type: DEFECT Latest Confirmation in: ---
Developer Difficulty: ---
Attachments:
Description Flags
The version of winserv.exe used to install the service none

Description paulkt 2009-09-10 09:48:06 UTC 
I have installed Open Office 3.1 and then subsequently installed a Windows service for Open Office using the winserv.exe 
utility as follows:


"C:\Program Files (x86)\bin\winserv.exe" install OpenOffice -displayname OpenOffice  -start auto "c:\Program Files 
(x86)\OpenOffice.org 3\program\soffice.bin" -headless -invisible -accept=socket,host=127.0.0.1,port=8100;urp;

The service then shows up in the services list, status STOPPED, as expected.

When I start the service it crashes with the following information:

  Problem Event Name:	APPCRASH
  Application Name:	soffice.bin
  Application Version:	3.1.9398.500
  Application Timestamp:	49e78954
  Fault Module Name:	sal3.dll
  Fault Module Version:	6.0.6001.18000
  Fault Module Timestamp:	4791a783
  Exception Code:	c0000135
  Exception Offset:	0006ecfb
  OS Version:	6.0.6001.2.1.0.256.4
  Locale ID:	7177
  Additional Information 1:	9d13
  Additional Information 2:	1abee00edb3fc1158f9ad6f44f0f6be8
  Additional Information 3:	9d13
  Additional Information 4:	1abee00edb3fc1158f9ad6f44f0f6be8

The same process using Open Office 2.4 produces a service which does not crash.  The only difference is the version of 
Open Office used.

I am able to get Open Office running as a service on Ubuntu and Gentoo Linux, though that is an entirely different 
procedure.

I have not yet tested on other Windows systems, I will be doing that as soon as I can.
Comment 1 paulkt 2009-09-10 09:49:08 UTC 
Created attachment 64665 [details]
The version of winserv.exe used to install the service
Comment 2 Olaf Felka 2009-09-10 09:55:16 UTC 
reassigned
Comment 3 jsc 2009-09-14 12:03:29 UTC 
jsc -> cd: probably one for you
Comment 4 paulkt 2009-09-15 13:47:56 UTC 
It would appear that changing the service installation command to the following:

"C:\Program Files (x86)\bin\winserv.exe" install OpenOffice -displayname 
OpenOffice -start auto "C:\Program Files (x86)\OpenOffice.org 
3\program\soffice.exe" -nologo -headless -invisible -nofirststartwizard -
accept="socket,host=127.0.0.1,port=8100;urp;StarOffice.ServiceManager"

produces a Windows service which does not crash.

I have just tested this on both a Vista 64 bit and a Windows 2003 installation.

I am still unsure whether there is an issue with Open Office worth investigating, 
as 2.4 worked with a command which failed on 3.1, but I am happy to be able to say 
I have a running service with 3.1 :)