Remote Installation of Imanager on Windows Server Fails

  • 3123780
  • 15-Jan-2007
  • 26-Apr-2012

Environment

Novell iManager 2.x
Microsoft Windows 2003 Server
Microsoft Windows 2000 Server
Win VNC
Microsoft Terminal Services client
VMWare Virtual Center

Situation

Customer attempting install iManager remotely. Repeated attempts via VNC. MS Terminal Services or VMWare Virtual Center all fail at the same point. Console 0 access is being used (via vnc or by using the /console switch with MS TSC)

Steps to duplicate:
1. Remote onto server console
2. Launch iManagerinstall.exe from cd or local copy on disk
3. InstallAnywhere unzips files to temp directory
4. Splash screen pops up, select language and click OK
4. Error screen pops up "InstallerUser Interface Mode Not Supported”
5. Click OK and get additional errorscreen; "This application has unexpectedly quit”
6. Click ‘Details’ and get the following error:

java.lang.NullPointerException

at com.zerog.ia.installer.Main.a(DashoA8113)

at com.zerog.ia.installer.Main.d(DashoA8113)

at com.zerog.ia.installer.Main.d(DashoA8113)

at com.zerog.ia.installer.Main.a(DashoA8113)

at com.zerog.ia.installer.Main.main(DashoA8113)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at com.zerog.lax.LAX.launch(DashoA8113)

at com.zerog.lax.LAX.main(DashoA8113)


Resolution

Ensure that the Windows environment variables for \TEMP & \TMP for the user profile you are using to remote onto the server are changed from the defaults (%userprofile\usename) to a hardcoded directory, c:\TEMP for example.