Enabling Debug Messages For Install And Configure; History Does Not Automatically Sync Across Multiple Simultaneous User Logins; Imanager Doesn't Work After Installing Groupwise 7.0 Webaccess; Missing Attribute, Object, Or Value Errors - Novell IMANAGER 2.7.3 - ADMINISTRATION Administration Manual

8.5 Enabling Debug Messages for Install and
Configure
If installation fails, you must enable some debugging messages to help determine what is wrong.
Linux: Export LAX_DEBUG=true in the terminal session that you start the iManager
InstallAnywhere program from.
Windows: Hold the Ctrl key down as you start the iManager InstallAnywhere program and
continue holding it until the debugging screen appears.
8.6 History Does Not Automatically Sync Across
Multiple Simultaneous User Logins
Using two instances of the same browser (such as two Firefox or two Mozilla browsers but not
Internet Explorer) avoids the problem. The history book is shared by the two instances.
8.7 iManager Doesn't Work after Installing
Groupwise 7.0 WebAccess (Windows Server
2000/2003)
On Windows 2000 and 2003 Server with IIS 5 or 6, installing Groupwise 7.0 WebAccess to IIS
automatically installs Tomcat 5.5.
As the iManager installation begins, the iManager installer program detects that IIS and Tomcat are
available for use. The installer reports the inability to stop the iisadmin service. Near the end of the
install, the installer reports the inability to start Tomcat.
After the install is completed, Groupwise WebAccess still works, but iManager does not (HTTP
404: Page not found).
Workaround: Do not install iManager and Groupwise on the same server.

8.8 Missing Attribute, Object, or Value Errors

If you have a large installation with synchronization delays, you can force iManager to communicate
with the master replica. This ensures that you have access to any attributes, objects, or values that
have been recently added or modified. This is not recommended for regular use of iManager, but can
be helpful when you are experiencing synchronization delays.
To use this parameter when logging in to iManager, add
after you have loaded the login page. This setting can also be enabled in
TOMCAT_HOME\webapps\nps\WEB-INF\config.xml
servlet/webacc?taskId=fw.Startup&forceMaster=true
You must restart Tomcat after making any changes to the
restarting Tomcat, see "Starting and Stopping Tomcat" on page
to the end of the URL
&forceMaster=true
. For example:
https://127.0.0.1/nps/
.
file. For information about
config.xml
94.
Troubleshooting 91