I've created a Custom Action (VBScript) in an Visual Studio .NET 2003 Setup
Project. The Custom Action didn't work. I deleted the Setup-Project, because
it was only a test.
Now I have the problem, that when I start any MSI-based installations, at
the end the Setup confronts me with the following error message:
"Error 1720: There is a problem with this Windows Installer Package. A
script required for this install to complete could not be run. Contact your
support pesonnel or package vendor".
It seems, that all MSI-based installation tries to run these custom acction
(VBScript) and fail (roll back).
Thank you in Advance for any suggestion.
Regards
Rolf
Seems difficult to believe that running ANY msi would cause a custom action
in an old msi (that is not even installed) to run, but none the less, maybe
this will help:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/msizap_exe.asp
--
****************************************
Michael Sanford
Windows Installer MVP
****************************************
"Rolf Cerff" <rolf....@t-online.de> wrote in message
news:10994902...@xkalibur.lexware.de...
msiexec /i <path to the msi> /l*v somelogfile.log
If it is that same vbscript, a log should show the error in the script.
--
Phil Wilson
[Microsoft MVP-Windows Installer]
Definitive Guide to Windows Installer
http://apress.com/book/bookDisplay.html?bID=280
"Rolf Cerff" <rolf....@t-online.de> wrote in message
news:10994902...@xkalibur.lexware.de...
thank you very much. Your suggestion gave me a helpful hint. Suggested by
the help of msizap, I found a hidden folder c:\config.msi. In it, I found a
file with some information of the related msi-package I created, with the
information about the custom action and even the code of the script behind
that action.
After deleting that file, all seems running fine again.
Nevertheless a very strange behaviour.
regards
Rolf
"Michael Sanford [MVP]" <msan...@nospam.com> schrieb im Newsbeitrag
news:eE0dp9aw...@TK2MSFTNGP10.phx.gbl...