/build/static/layout/Breadcrumb_cap_w.png

Internal Error 2738

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

Answers (5)

Posted by: ddehaan 18 years ago
Senior Yellow Belt
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
Posted by: MSIPackager 18 years ago
3rd Degree Black Belt
0
Can post your script?

Cheers,
Rob.
Posted by: rpfenninger 18 years ago
Second Degree Green Belt
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
'*****************************************************************************
Posted by: WiseUser 18 years ago
Fourth Degree Brown Belt
0
Does the script run on the "broken" machines outside the MSI?
Posted by: rpfenninger 18 years ago
Second Degree Green Belt
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????!!!!??? [>:]
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ