Gordon Welling
Admin Group
Manager Technnical Support Services
Joined: 11-December-2003
Location: Canada
Posts: 535
|
| Posted: 13-December-2006 at 3:08pm
|
|
|
NOTICE: This issue has been resolved in the Omni Mobile 2.4.0 (2007.03.26) release. If you have Omni Mobile server release .472 or .470 installed (check the classes\omnimobile.properties file) you will need to follow the steps below to ensure that you properly upgrade to the latest .475 Omni Mobile server module. Contact Omni support if you have any questions before proceeding with an upgrade of your Omni Mobile server.
Problem: We have identified a problem with releases 472 and 470 of the Omni Mobile server module when doing an uninstallation on Windows servers running GroupWise WebAccess application server 7.0.1. This will affect the ability to perform server upgrades.
Issue: This issue only effects Omni Mobile running on GroupWise WebAccess 7 SP1 on Windows Servers.
The uninstaller.jar program has a problem finding files in the templates\frames folder. This causes the uninstaller to restore files from a faulty install procedure. This results in certain files not being renamed, the loss of the omnimobile.properties file and the files in the \data folder. When WebAccess is started, and a user logs in, the top is all white (no tabs appear) and there is a "Compile Error: omnimobile_caprion.inc: Line 0: File does not exist: omnimobile_caption.inc.. Cannot load file: caption.htt" error at the top of the web page. If the Omni Mobile server is re-installed, the "Compile Error:" is fixed, but all of the user policies are missing and users must rebuild their user policies and reprovision their respective device(s).
Does Not Affect: All other installations of Omni Mobile server including Omni Mobile on GroupWise WebAccess 7.0 on Windows server are not affected. It does not effect Omni Mobile running on NetWare or Linux.
Resolution: To perform an upgrade installation of Omni Mobile running on GroupWise 7.01 on Windows server, before running the uninstallation or the upgrade, you need to backup the \data folder and the files in the \classes folder:
- Stop W3SVC and Tomcat 5.5 services.
- Make backup copies of the \data folder (normally c:\novell\tomcat5.5\data) and the \classes folder (normally c:\novell\tomcat5.5\webapps\gw\WEB-INF\classes).
- Run the current Omni Mobile uninstaller.
- Restore the \data folder contents from the backup (step 2. above).
- Restore the omnimobile.properties and version.properties files from the \classes folder backup. Rename the omnimobile.properties file to omnimobile.properties.omnimobile.
- Run the installer for the Omni Mobile server and perform a normal installation.
- Start W3SVC and Tomcat 5.5 services.
To perform a permanent uninstallation of Omni Mobile and restore GroupWise WebAccess, you need to fix the caption.htt files:
- Stop W3SVC and Tomcat 5.5 services.
- Run the current Omni Mobile uninstaller.
- Open Windows explorer and go to templates\css folder (normally C:\novell\tomcat5.5\webapps\gw\WEB-INF\classes\com\novell\we baccess\templates\css). Rename the caption.htt file to caption.htt.bad and rename the caption.htt.omnimobile file to caption.htt. Rename the login.htt to login.htt.bad and rename the login.htt.omnimobile to login.htt.
- Start W3SVC and Tomcat 5.5 services.
- Test WebAccess.
You can manually remove the remaining Omni Mobile files by referring to "Omni Mobile Manual Uninstallation Instructions for GroupWise 7.0.x on Windows Servers".
Edited by Gordon Welling on 27-March-2007 at 2:57pm
|
Omni Web Forum : GroupWise for PDAs and Smart Phones ~ Omni Mobile : Omni Mobile Server for GroupWise Synchronization
Topic: FIX: Corrupt Upgrade on Windows Server
