Apache OpenOffice (AOO) Bugzilla – Issue 22843
Report Autopilot not running over network install
Last modified: 2006-05-31 14:29:06 UTC
I've a mixed client (2Ksp4/Nt4sp6a) environement, running OO1.1rc4 from a NT4Serversp6a box. This is in regard to a network (setup -net) installation on the Nt4 server. Everything works fine, but when accessing the Report Autopilot from the Data Access window, nothing happens. It appears to be trying to run for a second or two as response to mouse is sluggish, but neither the wizard or another document opens. The Form wizard runs fine, I've Java 1.4.0_02 installed on all the boxes, so no problem there. I've re-installed the OOo network install on the server, and deleted the users workstation installation, but to no avail. I've also tried with both Mysql and spreadsheet data sources - both give the same error.
Hi, I can reproduce this. Workaround: Install a java version on the client side in the _same_ directory as on the server side. f.e. c:\program files\java\j2re1.4.2\. The the report wizard should work. msc -> jl: The problem seems that the java bridge search the java on the client side in the same directory as on the server side. Start the jvmsetup on the client side and select a 'local' java version doesn't solve the problem. Please check also if we can fix this in the OOo 1.1.1 timeframe. Bye Marc
This is a documentation issue. In order to use the Java which was selected during the setup of the base installation (server) it would be necessary that the path to the office and Java is exactly the same on client and server. That is, if the baseinstallation is x:\StarOffice then on the clientmachine the x: volume of the server must be mapped to drive x: The same goes for Java. Because the JRE is ususally installed on C:\Program Files\Java this does not work because C: on the client cannot be assigned to c: on the server. The easiest way to configure java is to run Office_baseinstallation\program\jvmsetup.exe on the client. Then select a Java which is installed on the client.
Here is a more accurate problem description and the proper solution for a networkinstallation: Problem =============== If a network installation (base installation) is to be performed on a windows box and the workstation installation is on a different windows box then Java dependent functionality may not work if the following is not true: 1. The complete path to the office installation of the base installation must be identical on server and client computer. 2. The complete path to the Java installation which was configured during setup of the base installation must be identical on server and client computer. Setup steps ======================== 1. Identify a drive letter which is unused on the server and all client machines. 2. Create a folder on the server, name it OfficeNetDrive (or whatever you like). 3. On the server map <OfficeNetDrive> to the drive as determined by step 1, for example, map OfficeNetDrive to z:. 4. Set the Permissions for <OfficeNetDrive> so that the admin has read, write access and all clients read access. 5. Install the office with setup.exe -net and choose as location drive z:. You can also create a subdirectory. 6. If the Java selection dialog comes up then either install the delivered Java on the common drive z: or select a Java which one has previously installed on drive z: 7. On the client map the folder at \\server-machine\OfficeNetDrive to drive z: 8. Start the setup by running z:\Office\program\setup.exe.
FPE: What are we supposed to do now? Generally, I refuse to document this since this is a workaround for an improper implementation. For 1.1.2 we cannot change documentation anyway since we have no process for changing documentation for dot-dot releases (PUs). If nothing else helps we can put something in the readme for 1.1.2 For OOo2 this should be fixed instead of documented. Given the modified installation process for OOo2, will this be an issue there, too? And if so, it should be addressed there.
FPE: We are going to put the recommended steps into the readme for 1.1.2 (PU3). FPE->DED: After you did that send the issue to Ingo Schmidt so he can check whether this is a pertaining issue for 2 that needs to be addressed. Thx
change subcomponent to 'none'
I'll try to determine which readme this should be added to.
FPE: Retargeted to OOo 2.0 since we cannot update the documentation 1.1.2 (as discussed with TZ) - For 2.0: document in install instructions
Okay, since this is not going into the documentation of 1.1.x, we should check whether we have a problem in 2.0, since there, we have *only* network installations. Ingo, can you please comment on this?
Well, in OOo 2.0 there is only one installation type, that is most comparable with our current network installation. In this installation we will (probably) make no java configuration. JL just told me, that this Java configuration (writing java.ini, javarc) will happen during Office startup (for Unixes) or when Java is demanded for the first time (Windows). Then of course only the locally installed Java will be referenced and this problem will hopefully no longer occur.
sounds promising, thanks!
According to what I've read here, I don't see a need to include the workaround in the readme for OOo 2.0.
FPE: So if this is solved for 2.0 I suggest to close this bug then.
Solved in 2.0