This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Kudos
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 01, 2012
06:41 PM
WScript.CreateObject: Could not create object named "IswiAuto16.ISWiProject"
Hello All,
My VB script ran OK on Windows 2003 Enterprise until I ran it after
I tried to install the InstallShield 2010 on a Windows 2008 R2, Windows 7.
The error is:
(658, 1) WScript.CreateObject: Could not create object named "IswiAuto16.ISWiProject"
Here is the code snippet:
' Get the Computer/machine name using Wscript.Network
Set wshNetObj = WScript.CreateObject("WScript.Network")
machineNameStr = wshNetObj.ComputerName
' Get file system object
Set fileSysObj = WScript.CreateObject("Scripting.FileSystemObject")
' Get IS Automation Interface Project Object
Set isProjObj = WScript.CreateObject("IswiAuto16.ISWiProject")
If WScript.Arguments.Count = 0 Then
ShowCommandOptions
Else
.
.
.
End If
My VB script ran OK on Windows 2003 Enterprise until I ran it after
I tried to install the InstallShield 2010 on a Windows 2008 R2, Windows 7.
The error is:
(658, 1) WScript.CreateObject: Could not create object named "IswiAuto16.ISWiProject"
Here is the code snippet:
' Get the Computer/machine name using Wscript.Network
Set wshNetObj = WScript.CreateObject("WScript.Network")
machineNameStr = wshNetObj.ComputerName
' Get file system object
Set fileSysObj = WScript.CreateObject("Scripting.FileSystemObject")
' Get IS Automation Interface Project Object
Set isProjObj = WScript.CreateObject("IswiAuto16.ISWiProject")
If WScript.Arguments.Count = 0 Then
ShowCommandOptions
Else
.
.
.
End If
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 01, 2012
09:06 PM
Make sure you are using a 32bit scripting process. If you are defaulting to 64bit it won't be found.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 02, 2012
01:14 AM
Thanks Christopher Painter. It was a good suggestion!!!
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 14, 2013
04:18 PM
Yes Chris, thanks! Our CM guy is trying to get our build process to work on 64-bit Windows for the first time (finally!) and we had this same issue. The Perl script I wrote was failing to instantiate the IswiAuto16:ISWiProject object. After finding this thread I had him check and, sure enough, the new build system was defaulting to the 64-bit Perl process to run Perl scripts.