I have a customer where the lms-3.2-win-eval.exe fails to run. It doesn't even start the installation, it probably fails to meet some installshield requirement.
The lms-3.1-win-eval.exe that was still on the server doesn't have this issue.
Of course I'm local administrator.
I opened a tac case but its not getting me anywhere.
The engineer doesn't want to investigate installshield but instead wants me the verify if the server meets the requirements, redownload the exe and reboot the server. But I've already done that twice and the server is running LMS 3.1 just fine for almost a year now.
I noticed it has this behavior on all 2003 servers (virtuals and real) but not on the XP PC's. I think a policy somewhere prevents the new installer to work.
Does anyone know how the force the installshield in a debug mode? I need to see what stops it from running. I found this at the installshield site but I don't really know what they are on about. I don't know how to make such a setup.dbg file
Debugging InstallScript code requires the debug-information file Setup.dbg to be available. To debug an InstallScript project on a system other than the development system:
- Copythe InstallScript debugger executable ISDbg.exe (located in the Systemfolder of your InstallShield distribution) to the test system, andregister it by launching the executable with the /REGSERVERcommand-line option.
- Copy Setup.dbg to the test system.
- Run Setup.exe with the command Setup.exe /d"<path>", where path is the directory containing Setup.dbg.
Alternatively does anyone know if the installer can be extracted? Getting the files out and then just running setup will work for sure.