PDA

View Full Version : [Installscript MSI]error -7132: An error occurred streaming ISSetup.dll support file



salmonin
06-16-2006, 12:00 PM
This error was posted in the Beta newsgroup http://community.installshield.com/showthread.php?t=159392.

I just installed 12 release and can reproduce the same exact issue in three different projects, one newly created in 12 and two imported projects from 11.5. All the projects are Installscript MSI.

Any Ideas?

Thanks in advance

Salim

Christopher Painter
06-16-2006, 12:03 PM
In the beta thread it was implied that the error message was erroneous and that the media was built. Is this true for you?

salmonin
06-16-2006, 12:52 PM
In my case, the media was built. However, when i tried to install, I got an error about missing entry point in the DLL.

MartinMarkevics
06-16-2006, 01:27 PM
Can you reproduce this by creating a new InstallScript MSI and building (sounds like that's what you said, just want to be sure)? In other words, can you build any InstallScript MSI project?

The problem in the Beta occurred when you had multilingual setups that included custom dialogs (i.e. used dialogs built into _isuser.dll). Just wondering if that's the case here or something else is possibly occuring here.

salmonin
06-16-2006, 01:42 PM
I did not have any multi-lungual custom dialogs, but two of the projects that I imported from 11.5 had custom dialogs.

Unfortunately, I have reverted my VM back to a previous snapshot. Since, I am desperately trying to find workarounds for couple of issues in Quickpatch using 11 and 11.5, I decided not to complicate things by introducing yet another version into the mix :)

I will be continuing with IS12 testing later next week and will post my findings in detail here. (I Promise)

Thank you very much for the timely resopnse.

Salim Nair

MartinMarkevics
06-16-2006, 03:28 PM
If you can, send me one of your setup projects (via Private Message) and I'll have a look in the meantime. Any one of the existing setups that failed to build after you upgraded will do fine.

salmonin
06-16-2006, 04:07 PM
That is a great offer. I will send you a failing sample project over the weekend.

Thank you

Salim

salmonin
06-21-2006, 03:40 PM
After doing some research, this is what I could find.

1. The situation where i could reproduce this error so far is in quickpatch creation (I am adding a log file at the end)
2. The update.exe created as part of the buld fails during execution when it is trying to load ISSetup.dll. No messages are shown. It just dies.
3. If I create a brand new quickpatch project in 12, for a base project created in 12, the error doesnt appear
4. If a new quickpatch is created based on an older MSI file or converted QuickPatch file, the error happens..

Following is the log file from one of such effors. IS12 QuickPatch created based on a Base msi built using IS11.5.

Sample project is attached

LOG
=====================
================= Logging started at 6/21/2006 04:13:15 PM ==================
Created release folders
Creating updated setup image...
Setting product version...
Setting package code...
Updating application files...
Updating registry entries...
Creating Patch Configuration Properties...
Building MsiPatchMetadata table
Creating Patch...
Validating MSI input file...
Table: Properties
Table: ImageFamilies
Table: FamilyFileRanges
Table: UpgradedImages
Checking for source files in images...
Upgraded image: QPNewVersion
Table: TargetImages
Target image: QPPrev1
Table: ExternalFiles
Table: UpgradedFiles_OptionalData
Table: UpgradedFilesToIgnore
Table: TargetFiles_OptionalData
Validating MSI input file...
Table: UpgradedImages
Copying upgraded MSI to temp-target location...
Creating file patches...
Family00
QPNewVersion
Generating transforms (MSTs)...
Family00
Creating cabinet file...
Cleaning up temporary files...
Creating update.exe
Copying base files to release location
Preparing the upgraded image
Preparing setup.ini
Streaming InstallScript support files
ISDEV : error -7132: An error occurred adding Update.exe support file ?\ISSetup.dll
Adding Windows Installer 2.0 engine (unicode)
Adding Windows Installer 3.1 engine
Adding Windows Installer 2.0 engine (ansi)
Instrumenting package for localization
Saving setup.ini
Saving update.exe
The patch creation process has completed with: 1 Errors and 0 Warnings.
================= Logging stopped at 6/21/2006 04:13:40 PM ==================
Log file has been created: <file:D:\InstallShield 12 Projects\My Project Name-5\Interm\6-21-2006 04-13-15 PM.txt>
==========================

salmonin
06-21-2006, 04:09 PM
OK, now I know i cannot create quickpatch for IS11.5 Projects. Ofcourse, I did not read the readme of IS12 before trying this.

Can anyone verify that this is the reason for the said error? May be we need a better error reporting?

joshkerr
06-22-2006, 11:32 AM
I upgraded my 11.5 project to 12 and now I get this error. I do not use quickpatch, so what else could cause the error? My project builds successfully, I haven't tested whether or not it installs correctly, but the error is bothersome.

I saw that this was an issue with 12 beta, so why isn't it fixed in the 12 release?

MichaelU
06-23-2006, 10:06 AM
Error -7132 is going to be one of those annoying errors that crops up for a handful of reasons. Some of these were outright bugs in the beta, and as best as we could, we fixed all of those. Others such as the one in this thread are due to trying to build a patch between two pre-12 InstallScript MSIs (a quickpatch is by implementation part the version of the base, part the version of the building IDE, and it's best when those versions match), and these should hopefully all be indicated by the filename "?\ISSetup.dll" in the error message.

It could also occur if various items are missing during your build; perhaps a setup.rul failed to compile to a setup.inx, or some other support file was deleted from your build machine. For instance if I create an InstallScript MSI project, add a syntax error to my script, and build, among other errors I get a -7132 referencing "C:\...\Script Files\Setup.inx". What message are you seeing?

Jim-Panse
01-01-2007, 05:42 PM
I see it too in my Project, but I just wanted to activate the billboards and there was the 7132 error. Now I've reset the billboard-activation to default and the error is still there too. I can't find the, how you said, "syntaxerror" and it seems that I must create a new project. :confused:

PS: I've added my project into the attachments.

Kollár Iván
09-25-2007, 08:10 AM
Hello,

I have the same problem while upgrading from version 8 to 12 .
The only strange thing that I found is the "ISVerifyScriptingRuntime" action between the Custom actions is red marked.
Could someone find the what causes this error?

Thank you

Feigenbaum
05-12-2008, 02:01 PM
I moved my AsonInstall3x2.ism file to a new directory tree (created to facilitate importing to source control) and I now get this error. Any clue what file is missing? The Setup.exe is built but fails with a 1628 right after the installer is exploded. What restrictions are there on moving the .ism file to different directories and then rebuilding?
There are no files in the script Files sub dir (which seem curious).



--------------
================= Logging started at 5/12/2008 09:14:53 AM ==================
Created release folders
InstallShield Script Compiler
Version 14.0.0.162
Copyright 1997-2006 Macrovision Europe Ltd. and/or Macrovision Corporation. All Rights Reserved.

Compiling...
Setup.rul
fatal error F8503: Can't open script input file
Setup.inx - 1 error(s), 0 warning(s)
AdminExecuteSequence table successfully built
AdminUISequence table successfully built
AdvtExecuteSequence table successfully built
AdvtUISequence table successfully built
InstallExecuteSequence table successfully built
InstallUISequence table successfully built
Directory table successfully built
Feature table successfully built
FeatureComponents table successfully built
Component table successfully built
Loading File table
Building File table
Adding file 'Microsoft.Web.Services3.dll' that is a dependency of component 'AsonServices.dll'
File table successfully built
Class table successfully built
Extension table successfully built
ODBCDataSource table successfully built
ODBCDriver table successfully built
ISSQLScriptFile table successfully built
ISSQLScriptReplace table successfully built
ISSQLConnectionScript table successfully built
ISSQLConnection table successfully built
ISSQLConnectionDBServer table successfully built
ISSQLRequirement table successfully built
ISPalmApp table successfully built
ISPalmAppFile table successfully built
ISComPlusProxy table successfully built
ISComPlusApplication table successfully built
ISComCatalogCollection table successfully built
ISComCatalogCollectionObjects table successfully built
ISComCatalogObject table successfully built
ISComCatalogAttribute table successfully built
ISComPlusApplicationDLL table successfully built
ISComPlusServerFile table successfully built
ISComPlusProxyFile table successfully built
ISComPlusServerDepFile table successfully built
ISComPlusProxyDepFile table successfully built
ISXmlFile table successfully built
ISXmlElement table successfully built
ISXmlElementAttrib table successfully built
ActionText table successfully built
Condition table successfully built
AppId table successfully built
AppSearch table successfully built
Property table successfully built
BBControl table successfully built
Billboard table successfully built
Binary table successfully built
BindImage table successfully built
CCPSearch table successfully built
CompLocator table successfully built
Complus table successfully built
ControlCondition table successfully built
ControlEvent table successfully built
CreateFolder table successfully built
CustomAction table successfully built
DrLocator table successfully built
DuplicateFile table successfully built
Environment table successfully built
Error table successfully built
EventMapping table successfully built
FileSFPCatalog table successfully built
Font table successfully built
IniFile table successfully built
IniLocator table successfully built
ISAlias table successfully built
ISCEApp table successfully built
ISCEDir table successfully built
ISCEFileExt table successfully built
ISCEInstall table successfully built
ISCEOtherAppCABs table successfully built
ISCERegistry table successfully built
ISCESetupFile table successfully built
ISCEShtCut table successfully built
ProgId table successfully built
ISComponentExtended table successfully built
ISCustomActionReference table successfully built
ISDRMFile table successfully built
ISFeatureExtended table successfully built
ISFileManifests table successfully built
ISIISAppPool table successfully built
ISIISCommon table successfully built
ISIISMetaData table successfully built
ISIISWebServiceExtension table successfully built
ISObjectProperty table successfully built
IsolatedComponent table successfully built
ISRequiredFeature table successfully built
ISSelfReg table successfully built
ISSetupType table successfully built
ISSetupTypeFeatures table successfully built
ISSQLDBMetaData table successfully built
ISSQLScriptError table successfully built
ISVRoot table successfully built
ISVRootAppMaps table successfully built
Verb table successfully built
ISWebSite table successfully built
ISXmlLocator table successfully built
LaunchCondition table successfully built
LockPermissions table successfully built
MIME table successfully built
MoveFile table successfully built
MsiAssembly table successfully built
MsiAssemblyName table successfully built
MsiDigitalCertificate table successfully built
MsiDigitalSignature table successfully built
MsiDriverPackages table successfully built
MsiPatchCertificate table successfully built
ODBCAttribute table successfully built
ODBCSourceAttribute table successfully built
ODBCTranslator table successfully built
PatchPackage table successfully built
PublishComponent table successfully built
Registry table successfully built
RegLocator table successfully built
RemoveFile table successfully built
RemoveIniFile table successfully built
RemoveRegistry table successfully built
ReserveCost table successfully built
SelfReg table successfully built
ServiceControl table successfully built
ServiceInstall table successfully built
SFPCatalog table successfully built
Shortcut table successfully built
Signature table successfully built
TextStyle table successfully built
TypeLib table successfully built
UIText table successfully built
Upgrade table successfully built
ISVirtualFile table successfully built
ISVirtualRegistry table successfully built
ISVirtualDirectory table successfully built
ISVirtualShortcut table successfully built
ISVirtualPackage table successfully built
ISVirtualRelease table successfully built
_Validation table successfully built
Searching project for extract-at-build components...
Building scanned MsiAssembly records
Building scanned MsiAssemblyName records
Validating Custom Action sequencing
Embedding manifest SetupExe.Invoker.manifest into setup.exe
Resolving strings...
Language English (United States) built
ISDEV : error -7132: An error occurred streaming ISSetup.dll support file C:\feigenba-WS-ASON\brazil\src\appgroup\ason\apps\ASON\mainline\AsonInstall3\AsonInstall3x2\Script Files\Setup.inx
Embedding manifest SetupExe.Invoker.manifest into setup.exe
Adding Microsoft(R) .NET Framework redistributables to setup...
Building CAB files...
Data1.cab built
Files built
ISDEV : warning -6487: If you intend to distribute this upgrade as a patch, you should author the 'Patch Optimization' setting on the Advanced Settings panel of the Release Wizard.
Media table successfully built
Setup.exe created
Automatic update notification disabled
Default Configuration\Default Release - 1 error(s), 1 warning(s)
================= Logging stopped at 5/12/2008 09:15:07 AM ==================
Log file has been created: <file:C:\feigenba-WS-ASON\brazil\src\appgroup\ason\apps\ASON\mainline\AsonInstall3\AsonInstall3x2\Default Configuration\Default Release\LogFiles\5-12-2008 09-14-53 AM.txt>

Eric-Jan
06-05-2008, 03:37 AM
I also get this error. I use my own created objects (obl files). The converted project points to obl files created with a different IS version. Change this ('Build / Options' and perhaps some inclusions from within your script) and the project builds again.

chgruber
06-25-2008, 01:22 PM
Is there a fix for this? My build works fine on my IDE machine but fails with the following error on the StandAlone machine:

ISDEV : error -7132: An error occurred streaming ISSetup.dll support file F:\FinalbuilderTemp\TFS\Build 7\ProjectName\Main\Source\source\Installshield\Scripts\Setup.inx

Thanks!
Chris

Eric-Jan
06-26-2008, 02:21 AM
Hello Chris,

If i'm not mistaken the setup.inx gcan get streamed into the issetup.dll. If streaming is not possible the setup.inx can be missing due to compilation error(s). Check your compilation report for this. Do you use obl files created with a different version of IS?

Eric-Jan

Mescalero
08-20-2008, 06:46 PM
Hello Eric-Jan,

Can you please clarify this last comment? I can also successfully build my project manually, but through standalone, this error -7132 is an issue. Does the setup.inx file need to also be somewhere under the StandaloneBuild folder? I am also receiving error -6003 ("error occurred streaming...setup.bmp into setup.exe") during a standalone build of the same project, and I suspect the causes are closely related, but I'm currently at a loss.

Thanks...

Eric-Jan
08-21-2008, 02:07 AM
Hello Mescalero,

These errors mostly occur because of compilation errors. Look at the Build output tab (corner left below) and look for errors above the 'Linking...' line.
Bescause of these errors no setup.inx is created and can thus not be streamed resulting into error 7132.

Also look if files are readonly or not (due to source control?).

This is my experience and my explanation (this appraoch helped me a couple of times).

Hope this clarifies for you.

Eric-Jan

Mescalero
08-21-2008, 03:18 PM
Hi Eric-Jan,

The file was not read-only, though this would have been a nice, easy resolution! :)

There were warnings during the compile of setup.rul, though no errors. Would warnings be sufficient to cause the error during the standalone build?

I may try to resolve the warnings in the meantime and find out. Thanks very much for your suggestions!

JMiera
06-22-2012, 02:19 PM
Keep in mind that when using certain dialogs, that you may also need to include the obl in your build options.

For instance, say you included the SdLogonUserInformation. That dialog requires NetApiRT.obl. To add it, go to Build | Settings... and place NetApiRT.obl in the Libraries (.obl) field.

If you find a way of identifying prerequisites from a given .isd, I'd love to hear about it.