Info 1720. There is a problem with this Windows Installer
Hi,
I had a msi which has a VB script in a custom action. This script should be executed is a part of custom action. But I get the below error in the log:
=================================
Action start 10:45:04: add_to_ini_file.
Info 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 personnel or package vendor. Custom action add_to_ini_file script error -2146827788, : Line 23, Column 1,
Action ended 10:45:04: add_to_ini_file. Return value 1.
=================================
Please help....
Thanks in advance...Praveen
I had a msi which has a VB script in a custom action. This script should be executed is a part of custom action. But I get the below error in the log:
=================================
Action start 10:45:04: add_to_ini_file.
Info 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 personnel or package vendor. Custom action add_to_ini_file script error -2146827788, : Line 23, Column 1,
Action ended 10:45:04: add_to_ini_file. Return value 1.
=================================
Please help....
Thanks in advance...Praveen
0 Comments
[ + ] Show comments
Answers (6)
Please log in to answer
Posted by:
plangton
20 years ago
Gday Guys and Gals
Testing your vbs before putting it in the msi will not ensure it will work, due to what gvlaarho mentioned, that wscript functions are not supported. However, in most cases (i.e. if you are doing wscript.createobject) you can just drop the wscript. If you are doing wscript.quit or wscript.sleep etc though you'll have to find another way as it can't be done - in the installshield forum there are some rather lengthy posts on how to work around these issues if you really need to. Its a bit annoying that you have to modify your scripts for msis though.
For example, here is a way to do a sleep as a sub that I copied and pasted from some helpful soul:
Sleep(5)
Sub Sleep(ByVal iSleepPeriod)
' Note: Timer returns the number of seconds that have elapsed since midnight.
Dim iStartTime, iEndTime, iCurrentTime
On Error Resume Next
iStartTime = Timer
iEndTime = iStartTime + iSleepPeriod
Do While Timer <= iEndTime
Loop
End Sub
God bless google :)
Hope this helps
Rgds
Paul
Testing your vbs before putting it in the msi will not ensure it will work, due to what gvlaarho mentioned, that wscript functions are not supported. However, in most cases (i.e. if you are doing wscript.createobject) you can just drop the wscript. If you are doing wscript.quit or wscript.sleep etc though you'll have to find another way as it can't be done - in the installshield forum there are some rather lengthy posts on how to work around these issues if you really need to. Its a bit annoying that you have to modify your scripts for msis though.
For example, here is a way to do a sleep as a sub that I copied and pasted from some helpful soul:
Sleep(5)
Sub Sleep(ByVal iSleepPeriod)
' Note: Timer returns the number of seconds that have elapsed since midnight.
Dim iStartTime, iEndTime, iCurrentTime
On Error Resume Next
iStartTime = Timer
iEndTime = iStartTime + iSleepPeriod
Do While Timer <= iEndTime
Loop
End Sub
God bless google :)
Hope this helps
Rgds
Paul
Posted by:
kkaminsk
20 years ago
Posted by:
wildcat966us
20 years ago
Posted by:
gvlaarho
20 years ago
Posted by:
kkaminsk
20 years ago
Posted by:
cdupuis
20 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.