Printing Problem after upgrading to OO4
I've just upgraded OO3 to OO4: installed as usual, changed options in OO (though option "Internet | Browser Plug-in and check Display documents in browser" no longer exists); changed system path, checked that swriter started from command prompt (it did), rebooted server and opened openVPMS.
OV works ok but can't print, preview or mail anything that requires ODT file (.jrxml files print ok). When I click Print, system returns "Please Wait.." for ~30 seconds then returns with error message "Failed to start OpenOffice service: failed to connect after 10 attempts".
What have I missed?
(OV 1.6.2, TCat 6.0, OO4)
Yuri.
Re: Printing Problem after upgrading to OO4
OpenVPMS is trying to launch the soffice binary (soffice.exe on Windows, plain soffice everywhere else). This should be in the same directory as swriter.
Make sure that the user that runs Tomcat can launch soffice from the command line.
Re: Printing Problem after upgrading to OO4
Yuri - I just upgraded to OO4 in my laptop (was previously running 1.7B2 but still with OO3 installed). I had the same problem - could not find swriter.exe. It turned out to be my fault - when I edited the PATH environment variable, I was lazy and simply changed C:\Program Files (x86)\OpenOffice.org 3\program to C:\Program Files (x86)\OpenOffice.org 4\program. No good - it should be C:\Program Files (x86)\OpenOffice 4\program.
I had previously just started swriter.exe via the start menu - ie (in Win 7) search for swrit and let windows find the swriter.exe. However, this worked OK because it knows the path to swriter. A better check is to login as openvpms (or whoever runs the Tomcat service on your machine) and the fire a command prompt window, and then type swriter.exe. That initially failed - which led to my discovery of the correct path.
However, even then I had to reboot the machine for everything to come good.
Hope this helps, Regards, Tim G
Re: Printing Problem after upgrading to OO4
TimG said
>That initially failed - which led to my discovery of the correct path.
I did reboot the server after making the changes to the path. I've just checked the path and it says inter alia ;C:\Program Files\OpenOffice 4\program; which is correct. I just rebooted once more but no improvement.
TimA said
>OpenVPMS is trying to launch the soffice binary (soffice.exe on Windows, plain soffice everywhere else). This should be in the same directory as swriter.
From a Win7 command prompt anywhere on the server/user running Tomcat, soffice (with or without .exe) launches Open Office 4, swriter launches Writer.
That's why I'm puzzled: path is correct, soffice/swriter launch from command prompt, but not from within OV. Should OO4 only be used with 1.7? Should I uninstall OO4 and go back to OO3?
Yuri.
Re: Printing Problem after upgrading to OO4
You could try the approach from this post, although take a backup of the original jars so you can revert easily if needed.
Another possibility may be that the OO user profile of the Tomcat user has been corrupted. In this case, you can move it aside and see if that corrects the issue.
See https://forum.openoffice.org/en/forum/viewtopic.php?p=58403#p58403 for the location of the profile.
-Tim
Re: Printing Problem after upgrading to OO4
>You could try the approach from this post, although take a backup of the original jars so you can revert easily if needed.
Only one problem: neither the work server's OO4 nor a test installation of OO4.0.1 here on my home PC has a java\URE folder. In fact, no URE folder anywhere on the PCs.
At this point, I've chickened out and reverted to OO3.4.1 and everything is working properly again. Whew! I'm glad I didn't try this during the week <g!>
Yuri.
Re: Printing Problem after upgrading to OO4
I have searched the Forums for an hour looking for my post concering upgrading to open office 4 and the reason why we had to do it for Version 1.7.
In essence it had to do with versions reaching End of Life, at this point anything prior to OO 3.4 is not updated with security patches. 3.4 is only recieving security patces and I think hits EOL next year.
That being said from 3.4 to 4.0 does make some changes. I think we were supporting Oo 2.2 up to this point. I think the API framework was updated to 4 for 1.7.
I am sure there was another reason, however we need some more QA on this issue to ensure when 1.7 moves out of beta its seemless.
Ben
Re: Printing Problem after upgrading to OO4
Here?
http://www.openvpms.org/forum/1.7-a5444-first-impressions#comment-6481