The following email appeared in my inbox the other day..
I'm installing the release code for IDS 11.10 on my Windows XP SP2 machine and it gives me grief in my native XP environment, but no problems within my Windows XP guest machine in VMWare.
This is the error I'm getting
followed by this:
I can't get a server instance created...
Since the first error tends to be the most salient, I suspected a likely cause of failing to create the Message service was a problem with user rights - perhaps the user didn't have permission to create or start a service. I asked the user (or should I say product manager) to run "whoami /all" from the Windows XP Service Pack 2 tools for Advanced Users package. This shows the user's advanced user rights, which would show if theuser was missing any required user rights like permission to start a service.
In this case all the required user rights appeared to be present. Another possibility was that maybe there was a partialinstallation left over from a previous attempt that had left some corrupted registry keys behind that were causing problemsfor subsequent installs. I connected to the machine via NetMeeting to look at the registry keys and services, and removed all traces of previous installs. Still the same problem occurred at install time.
Now this was starting to annoy me. Tracing the installation sequence it appeared the failure occured when the Instance Manager (instmgr.exe) utility was launched for the first time, which happens when the installer tries to create a demo instance. Running instmgr directlyresulted in the error: instmgr.exe is not a valid Win32 application. Now we were getting somewhere.
Fortunately Visual Studio was installed on the machine, so I ran "dumpbin /headers instmgr.exe" to see if the binary file had valid Win32 header information:
Microsoft (R) COFF/PE Dumper Version 8.00.50727.762Copyright (C) Microsoft Corporation. All rights reserved.
Dump of file instmgr.exe
PE signature found
File Type: EXECUTABLE IMAGE
FILE HEADER VALUES 8664 machine (x64) ....
There was the problem. This was a Windows 64-bit version of IDS installing on 32-bit Windows.
The red herring was that it apparantly worked on a VMWARE image. The only explanation for this is that it was a different versionof IDS that was installed there (or a VMWARE image of 64-bit Windows).
The reason the installer appeared to run correctly until it tried to launch the IDS Instance Manager is that the installer is a 32-bit program even in the 64-bit install media, so the problem only showed up when the first 64-bit program was executed. It would have saved some time if the installer had identified the operating system incompatibility before proceeding. I'll be logging a defect for this..