Software Deployment

Have you logged the install? (msiexec /lv for verbose log)

Perhaps there's a launch condition in there or something?

Hi Jamie,

I would suggest you to create a verbose log of the installation and search the log for CAs which fail (i.e. search for actions that have Return value 3). Analyse these actions and comment them using Wise or ORCA and I am sure your application shall run independent of the setup.exe.

Cheers

Thanks for the reply.

OK i have created a log file. Could you give me an idea of the sort of thing i should be looking for?

I seemed to post that question as i got the last reply. I will take a look.

Thanks

ORIGINAL: madjack
Could you give me an idea of the sort of thing i should be looking for?

(i.e. search for actions that have Return value 3).Search for that whole string, including the trailing full-stop i.e. "return value 3."

Jamie,

Just search for the string Return value 3 in the log file. The CAs that fail pass the return value 3. This will indicate which CA fails. Analyse those particular actions, comment them and test.

You may find this video helpful on troubleshooting Windows Installer (it covers log files, tools, things to look for)

http://itninja.com/blog/view/appdeploy.com->-training-videos->-troubleshooting-the-windows-installer

I am finding instances of return value 0,1 and 2 but not 3.

I have found something that says "LaunchCondition 3: -2147287038". Any other suggestions?

I will watch the suggested video when i can.

Thanks

Thinking about this, the whole CA return value thing is a red herring. If the message *was* coming from a CA, it succeded in its execution (since it detected that the MSI wasn't being run by the set-up stub) and would therefore set a return value of '1' (which, in MS's bizarre world equals 'success' - bizarre, because practically everything else in DOS and Windows returns '0' for success...)

Look in the log for the error message "please run setup.exe to install this product" and you've found the rough position of the CA involved. You'll probably need to look at the few preceding lines to locate the actual line containing the CA name.

I've done a search and can find no reference to that i'm afraid.

Now you have to reach out for straws...

Do another install with logging but this time, when you see the error pop up, open the log WHILE THE MESSAGE IS ON-SCREEN. Don't use Notepad, because it can't open files which another app has locked. A few lines from the bottom of the log *should* provide a clue as to which CA is presenting you with that message.

Inspiration!
Alternatively, you could run the MSI through WPS's debugger. Open the MSI in WPS, click 'Debug', then wait. When the message appears, you can see which action is running in the debugger. Bear in mind that the debugger can be very S L O W at times....

After trying everything esle i decided to go for the old fashioned 'trial and error' technique!

After commenting out various custom actions I have finally got it working. The offending custom action is called QuitMSI. By commenting this out it runs the install without the need to call the setup.exe.

The exact syntax is:

If Not Installed And LANGUAGEID=""
Call DLL From Installation Function QuitMSI (QuitMSI)
End

I dont pretend to know exactly what it does but the main thing is the install is working now.

Thanks for everyones help.