Issue 93031

Summary: Setting UserInstallation prevents binding the socket
Product: General Reporter: wdonne <werner.donne>
Component: uiAssignee: AOO issues mailing list <issues>
Status: UNCONFIRMED --- QA Contact:
Severity: Trivial    
Priority: P3 CC: elish, issues
Version: OOo 2.4.1Keywords: needhelp
Target Milestone: ---   
Hardware: Other   
OS: Linux, all   
Issue Type: DEFECT Latest Confirmation in: ---
Developer Difficulty: ---

Description wdonne 2008-08-22 15:46:56 UTC
I have started soffice with the following command-line:

> soffice -headless -norestore "-accept=socket,host=0,port=22222;urp;"

/tmp/tt is an existing directory.

The process starts and waits, but a client gets "Connection refused", which
leads me to think the socket isn't bound in soffice. When I leave out the
UserInstallation option the client can connect.

With the UserInstallation directory set to /tmp/tt I see the "user" subdirectory
is created with everything in it, but there is no ".lock" file, which would be
the case with the default user directory.

PS: I see no point in locking when soffice is in headless mode.
Comment 1 wdonne 2008-08-22 18:01:42 UTC
I have compared what is inside the generated "user" directory and a normal
"user" directory. The difference that matters is the file
"registry/data/org/openoffice/Setup.xcu". More specifically, when the field
"FirstStartWizardCompleted" is absent or set to "false" and the
"LicenseAcceptDate" absent it doesn't work and otherwise it does.

I understand those fields are set when you first run soffice and that the
headless mode is not able to pop up the required dialogs to do it.
Comment 2 michael.ruess 2008-08-23 12:47:44 UTC
Framework issue.
Comment 3 Olaf Felka 2009-07-15 15:53:23 UTC
@ sg: can you please have a look?
Comment 4 windowsoouser 2010-06-04 14:12:04 UTC
We are trying to run multiple OO instances that bind to different ports . 

'soffice' Command when run with -env:UserInstallation option throws
"NoConnectException". However, without the above option, the 'soffice' process
is launched successfully.

Environment details:
1. Windows 2003 Server SP2 R2.
2. Open Office Version 3.2 
3. Folder is not on Network Drive
4. Write Permissions are available
5. Port is free
6. Soffice Command used: 
C:\Program Files\ 3\program\soffice.bin -headless -nocrashreport
-norestore -nofirststartwizard

Note: IP is given accurately but masked here.