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
- :
- Re: SAB is not identifing logutil.dll
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
Sep 08, 2010
09:07 PM
SAB is not identifing logutil.dll
I onstalled , installshield 2008 premier edition on my development machine.
On build server i installed SAB(stand alone build).
On my development machine , i can able to successfully generate MSI using "ISCMDBLD.EXE" tool.
On production, if i use "ISSABLD.EXE" to build installshield project(*.ism), i am getting following error.
system\logutil.dll not found. Cannot stream file into binary table ISDEV
Do i need to pass additional parameters?
On build server i installed SAB(stand alone build).
On my development machine , i can able to successfully generate MSI using "ISCMDBLD.EXE" tool.
On production, if i use "ISSABLD.EXE" to build installshield project(*.ism), i am getting following error.
system\logutil.dll not found. Cannot stream file into binary table ISDEV
Do i need to pass additional parameters?
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Sep 09, 2010
08:06 AM
I believe the reason you are seeing this error is because the logutil.dll file should be installed when you install the Standalone Build, but it is not. This has been resolved in newer versions of the Standalone Build.
To work around this issue with the InstallShield 2008 Standalone Build, try copying the logutil.dll file from your development machine (probably something like C:\Program Files\InstallShield\2009 StandaloneBuild\System\LogUtil.dll) to the Standalone Build System folder on your build machine. Then rebuild the release.
To work around this issue with the InstallShield 2008 Standalone Build, try copying the logutil.dll file from your development machine (probably something like C:\Program Files\InstallShield\2009 StandaloneBuild\System\LogUtil.dll) to the Standalone Build System folder on your build machine. Then rebuild the release.