Environment
Novell iManager 2.7
Microsoft Windows Server 2003 Enterprise Edition
Microsoft Windows Server 2003 Standard Edition
Microsoft Windows XP Professional
Microsoft Windows 2000 Professional
Microsoft Windows 2000 Advanced Server
Microsoft Windows 2000 Server
Microsoft Windows 2000
Microsoft Windows Server 2003 Enterprise Edition
Microsoft Windows Server 2003 Standard Edition
Microsoft Windows XP Professional
Microsoft Windows 2000 Professional
Microsoft Windows 2000 Advanced Server
Microsoft Windows 2000 Server
Microsoft Windows 2000
Situation
Novell iManager 2.7 Workstation edition is made to be
portable. To meet these goals it does not have an installer
that adds itself to Add/Remove Programs in Windows. To"install" iManager Workstation the downloaded ZIP archive is simply
extracted to the desired location and run from there.
After running iManager Workstation and moving it to another part of the file system on the same box the user who ran iManager is not able to load iManager again. Another user on the same system who has not previously run iManager can run it from the new location properly. Also if the original copy of iManager is copied (instead of moved) to the new location then iManager will still load properly.
When iManager does not load properly the splash screen does show up but the browser itself fails to completely load.
After running iManager Workstation and moving it to another part of the file system on the same box the user who ran iManager is not able to load iManager again. Another user on the same system who has not previously run iManager can run it from the new location properly. Also if the original copy of iManager is copied (instead of moved) to the new location then iManager will still load properly.
When iManager does not load properly the splash screen does show up but the browser itself fails to completely load.
Resolution
When iManager 2.7 Workstation loads for the first time it writes a
value in the user's registry hive which stores the location for the
bundled browser. When iManager loads on subsequent occasions
the registry is queried for the location that was previously
written. If the files at that location are not available for
one reason or another then iManager will not load properly.
As a result if the files are copied from the first location to the
second and loaded from either location iManager will work but if
they are moved (and not replaced in the original location) then
iManager will not load. Also because these values are stored
in the user-specific registry hives other users should work
properly as long as they do not have the registry values written at
all.
Fixes include modifying the registry removing or modifying the value originally written by iManager and putting iManager back to where it was run for the first time. To clean the registry open regedit or regedt32, open the HKEY_CURRENT_USER hive and browse to the following location:
HKCU/Software/mozilla.org/GRE
Delete all subkeys of the GRE key. If you view the contents of the appropriate key there should
be a 'GreHome' String Value with the full path to your iManager Workstation installation. Modifying this to point to your new location will also resolve the error and allow iManager to load properly.
Fixes include modifying the registry removing or modifying the value originally written by iManager and putting iManager back to where it was run for the first time. To clean the registry open regedit or regedt32, open the HKEY_CURRENT_USER hive and browse to the following location:
HKCU/Software/mozilla.org/GRE
Delete all subkeys of the GRE key. If you view the contents of the appropriate key there should
be a 'GreHome' String Value with the full path to your iManager Workstation installation. Modifying this to point to your new location will also resolve the error and allow iManager to load properly.