Half a year ago I had a package which caused a few machines to bring up the Internal Error 2738 (Could not access VBScript runtime for custom action). After reinstalling the Windows Scripting Host, it worked.
Now I have the same issue with a couple of machines when I try to install a newer version of the same software (with a repackaged msi including a vbscript).
However, it no longer helps resolving the problem when installing the Windows Scripting Host.

When I try to execute a simple vbscript (showing a message box) to check if it runs, everything is fine.

Is there a way to check the Windows Scripting Host any further? Unfortunately there isn't any newer version of WSH I could play with...

Thanks for any help in advance

Roland
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Maybe you could install Microsoft Visual Studio. When an error occours in the VB scripts, it opens Visual Studio and shows you at what line of the code the problem is. Maybe this helps you debugging the VB code. VB code can cotain links to surtain objects which aren't available on the PC you want to install the MSI on. Hopefully this tip can help you out.

Good Luck!

Dennis de Haan
The Netherlands
Answered 12/22/2005 by: ddehaan
Senior Yellow Belt

Please log in to comment
0
Can post your script?

Cheers,
Rob.
Answered 12/22/2005 by: MSIPackager
Third Degree Black Belt

Please log in to comment
0
Hi Rob

Please excuse that it took me so long to post the script...
Here it is.
Thanks for any further help.

Roland



'*****************************************************************************
'* File: Twix_UsrProfile_Del.vbs / 1.0
'* Task: Delete the Folder Twixtel in the UserProfile
'* Parameter: nothing
'* History: User Date Task
'*****************************************************************************
OPTION EXPLICIT
'On Error Resume Next

Dim oFSO, oShell, strUserProfile

Set oFSO = CreateObject("Scripting.FileSystemObject")
Set oShell = CreateObject("Wscript.Shell")
strUserProfile = oShell.ExpandEnvironmentStrings("%USERPROFILE%")


'*****************************************************************************
' Programm-Start
'*****************************************************************************
If oFSO.FolderExists(strUserProfile & "\Twixtel") Then
oFSO.DeleteFolder strUserProfile & "\Twixtel", True
End If


'*****************************************************************************
' Programm-Ende
'*****************************************************************************
Answered 12/28/2005 by: rpfenninger
Second Degree Green Belt

Please log in to comment
0
Does the script run on the "broken" machines outside the MSI?
Answered 12/28/2005 by: WiseUser
Fourth Degree Brown Belt

Please log in to comment
0
To me it sounds very strange, but yes, outside the msi the script runs fine [:@]
I just tested it remotely on the users machine.
So I guess there is no problem with the local windows scripting host (anymore).

However, how comes it cannot run within the msi on that machine and on 1000+ machines it runs????!!!!??? [>:]
Answered 12/29/2005 by: rpfenninger
Second Degree Green Belt

Please log in to comment
Answer this question or Comment on this question for clarity