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
- :
- Building several ism on same build agent
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
‎Aug 01, 2012
03:35 AM
Building several ism on same build agent
Hi,
I have a build agent which builds a number of different ism projects.
The build agent has a valid stand-alone build agent license and I am able to build the first ism. However the next ism fails with:
[08:45:15][Step 10/17] InstallShield (R)
[08:45:15][Step 10/17] Release Builder
[08:45:15][Step 10/17] Copyright (C) 2011 Flexera Software, Inc.
[08:45:15][Step 10/17] and/or InstallShield Co. Inc.
[08:45:15][Step 10/17] All Rights Reserved.
[08:45:15][Step 10/17]
[08:45:15][Step 10/17] Build started at aug 1 2012 08:45
[08:45:15][Step 10/17] Building Release: Release
[08:45:15][Step 10/17]
[08:45:15][Step 10/17] ISDEV : fatal error -7159: The product license has expired or has not yet been initialized.
[08:45:15][Step 10/17] Suite\Release - 1 error(s), 0 warning(s)
If I have the build agent sleep/wait before trying to build the next, it works fine.
Does anyone have any ideas?
with regards, Thomas
I have a build agent which builds a number of different ism projects.
The build agent has a valid stand-alone build agent license and I am able to build the first ism. However the next ism fails with:
[08:45:15][Step 10/17] InstallShield (R)
[08:45:15][Step 10/17] Release Builder
[08:45:15][Step 10/17] Copyright (C) 2011 Flexera Software, Inc.
[08:45:15][Step 10/17] and/or InstallShield Co. Inc.
[08:45:15][Step 10/17] All Rights Reserved.
[08:45:15][Step 10/17]
[08:45:15][Step 10/17] Build started at aug 1 2012 08:45
[08:45:15][Step 10/17] Building Release: Release
[08:45:15][Step 10/17]
[08:45:15][Step 10/17] ISDEV : fatal error -7159: The product license has expired or has not yet been initialized.
[08:45:15][Step 10/17] Suite\Release - 1 error(s), 0 warning(s)
If I have the build agent sleep/wait before trying to build the next, it works fine.
Does anyone have any ideas?
with regards, Thomas
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 25, 2013
12:51 AM
I have the same problem with the InstallShield 2012 Spring SP1 Standanlone build.
What I have tested:
Define each VS project (csproj) separatly in the build definition and call all projects with a 1 minute time delay (BuildProcessTemplate modified).
=> No changes!
We have only one standalone concurrent licence, but a lot of project with 2 ism to build in the same VS solution.
Any ideas?
Best regards,
Urs
What I have tested:
Define each VS project (csproj) separatly in the build definition and call all projects with a 1 minute time delay (BuildProcessTemplate modified).
=> No changes!
We have only one standalone concurrent licence, but a lot of project with 2 ism to build in the same VS solution.
Any ideas?
Best regards,
Urs
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 19, 2013
12:30 AM
Hi all,
IS2012 Spring
IS2013
We have used the Flexera support to solve the problem.
The problem exists in our system only with concurrent licenses and digital signing is used inside the setup.
We have made many test to detect the problem in the digital signature.
Solution
InstallShield use the 'Signtool.exe' V5.2.3790.1830 for signing.
Replace the 'Signtool.exe' in InstallShield (system folder in InstallShield) with the 'Signtool.exe' (V6.1.6700.16385) from the Windows SDK 7.1 (C:\Program Files\Microsoft SDKs\Windows\v7.1\bin).
This solution works for us in many projects.
Best regards,
Urs
IS2012 Spring
IS2013
We have used the Flexera support to solve the problem.
The problem exists in our system only with concurrent licenses and digital signing is used inside the setup.
We have made many test to detect the problem in the digital signature.
Solution
InstallShield use the 'Signtool.exe' V5.2.3790.1830 for signing.
Replace the 'Signtool.exe' in InstallShield (system folder in InstallShield) with the 'Signtool.exe' (V6.1.6700.16385) from the Windows SDK 7.1 (C:\Program Files\Microsoft SDKs\Windows\v7.1\bin).
This solution works for us in many projects.
Best regards,
Urs