cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
mary_v
Level 6

problem using iswiautomation in is2011

Hi,

used my vbscript since IS2009 but now i am experiencing some problems in Is2011 ...

my script looks like this:

Set oProject = CreateObject("ISWiAuto17.ISWiProject")
oProject.OpenProject "D:\IS2011 Projects\Test\Test.ism"
oProject.ISWiProductConfigs("Product Configuration 1").ISWiReleases("Release 1").Build()
oProject.SaveProject
oProject.CloseProject
Set oProject = Nothing

my script won't compile anymore, the error looks like

...\test.vbs(2, 1) ISWiAuto17: Automation error
> ISWiAutomation.ISWiRelease.BuildInternal
> ISWiAutomation.ISWiRelease.Build


any ideas?

thanks mary
Labels (1)
0 Kudos
(8) Replies
mary_v
Level 6

... just wondering if the solution for me is too obvious ...?

mary
0 Kudos
mary_v
Level 6

... solved it myself ... (ruined my weekend :mad: )

the same workstation had also IS2010 installed - it now works on a clean machine ... :rolleyes:

mary
0 Kudos
Shuttledude
Level 7

Bummer ... I want to use the same computer for IS2009 and IS2011 projects, at least for awhile. Is there no way to use automation to kick off IS2011 projects unless it is the only installed version of InstallShield??!

Anyone know? :confused:
0 Kudos
Shuttledude
Level 7

This code works for me in Visual Build Pro 7.7 (using it in the Script Editor associated with building an InstallShield 2011 project; works with msi projects and installscript msi projects). It should work with any other build tool or automated script as well.

Use the horizontal scroll bar to see all of the code.


Sub vbld_StepStarted()
Dim pInstaller
' IswiAuto15.ISWiProject is for InstallShield 2009; use IswiAuto17.ISWiProject for InstallShield 2011!
Set pInstaller = CreateObject("IswiAuto17.ISWiProject")
Dim pDatabase

pInstaller.OpenProject Step.ExpProperty(Builder, "Filename")
pInstaller.ProductVersion = Application.ExpandMacrosAndScript("%IS_MY_PRODUCT_VERSION%")

'Change the GUID for the package code
guidString = pInstaller.GenerateGUID()
pInstaller.PackageCode = guidString

pInstaller.SaveProject
pInstaller.CloseProject
End Sub

0 Kudos
GarrettDyer
Level 5

Shuttledude wrote:
This code works for me in Visual Build Pro 7.7 (using it in the Script Editor associated with building an InstallShield 2011 project; works with msi projects and installscript msi projects). It should work with any other build tool or automated script as well.


Yeah, I have no problem updating the GUID and Properties using the 2011 Automation Interface, but like Mary, the Build method fails for me. I also have multiple versions of IS installed on my build server.

So, I think the question still remains...
0 Kudos
oivind-i
Level 3

I got the same problem (ISWiAuto17).

Can open project, set versions and guids, open ProductConfig and Release. BUT the build operation fails with:

1> Unspecified error
1> > ISWiAutomation.ISWiRelease.BuildInternal
1> > ISWiAutomation.ISWiRelease.Build

I'm also using an old build server with several generations of InstallShield.

It's not always a possible solution to uninstall old versions of InstallShield - they are in use.

This looks like a bug, and if so, Flexera should be able to provide a fix or workaround!
0 Kudos
oivind-i
Level 3

The project builds just fine in the InstallShield application. It's just when building from scripts that it fail.
0 Kudos

IS 2019 R3 - the same problem

Unspecified error

ISWiAutomation.ISWiRelease.BuildInternal

ISWiAutomation.ISWiRelease.Build

Code: 800A4005

Source: ISWiAuto25

0 Kudos