3 replies to this topic

[bannistj]

I put together a piece of JScript (stored directly in a custom action) which allowed me to create a Domain user via ASDI and then install a COM+ Application under this user. It was working fine but then I started getting a 1720 error during install. I changed the script which i was editing back to what it was previously, to no effect. Eventually i removed ALL the JScript Custom Actions I had put in but the error persisted. Can anyone tell me how I can find out more information on the error I'm getting or find out what script is causing the error or what happened to my project as I cant get it back on its feet.

[bannistj]

Forgot to mention: This happens during the Install Phase so it's not a cached copy of the installer running.

[yoavshabtai]

Hi

If there are no others VBScript or JScript then this is probably
a cache msi.
But never the less . . .
Run the msi with the log option like this for example:

Quote

msiexec /i "setuplocation\yourfile.msi" /L*v+ %temp%\yourfile.log

and then use the log to see who is the bad boy.
you can use the utility "WiLogUtl.exe" from the SDK to help
you process the log file. If you don't have it - GET IT!!!

Hope this will help you.
--Yoav

[bannistj]

Thanks for that. I can't seem to get hold of the Windows Installer SDK form the Microsoft website. I dont spose you could mail it to me.