- This topic has 2 replies, 2 voices, and was last updated 21 years, 2 months ago by Scott Anderson.
-
AuthorPosts
-
HowardGilbertMemberAttempting to install 020600 on Windows Standard Server 2003, the installer quits just after launch with dialog box and message “The installer cannot run on your configuration. It will now quit.”. Examining the InstallAnywhere site, this message is the default when a configured installation rule is violated.
The best guess is that Windows Server 2003 is not recognized as a supported OS level.
The problem is not in Eclipse 2.1, since it hasn’t asked where Eclipse is.
Sun JDK 1.4.2 is unlikely to be the source.
It installs fine with the same JDK, same Eclipse, on Windows XP Pro.
The hardware is a Dell 1600SC server with two Xeon 2.4 GHz processor. Hyperthreaded they appear as 4 CPUs. 700+ megabytes. Two SCSI disks.
Would be quite happy to run with any switch or parameter to generate install log, but don’t know how, or where the log would be.
Scott AndersonParticipantHoward,
You’re probably right in your analysis. It may not be able to recognize Windows Server 2003 properly. I’ll check with the installer guys and get back to you.
–Scott
MyEclipse Support
Scott AndersonParticipantHoward,
We followed up with ZeroG’s support on this issue and found the following thread:
http://community.zerog.com/cgi-bin/ikonboard.cgi?s=3f4f96893a30ffff;act=ST;f=13;t=1892;hl=%indows+and+%erver+and+2003Basically, it looks like JDK 1.4.2 reports the correct value for os.name when running on Windows Server 2003. Prior JDK’s did not, since they were release prior, and would report the platform was Window XP, allowing installers to proceed. It would seem that the workaround would be to run the installer with JDK 1.4.1, at this point. But it’s a little bit complicated. Install Anywhere actually sorts the command path (don’t ask me why) when looking for JDK’s to use for installation. So, you’d have to install 1.4.1 in a directory whose name would be lexicographically early when compared with all your other JDK directories (ie. like c:\\A1.4.1Install)
To turn on debugging so we can see exactly what is going on, please set the environment variable LAX_DEBUG=1 and rerun the installer. This should really be the first step.
–Scott
MyEclipse Support -
AuthorPosts