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
- :
- Update
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
‎May 23, 2015
12:44 PM
Error 1001 (MSI Database) during Build of Single Image
I get this message about 3 out of 10 times. Restarting the build immediately is usually successful. It happens is batch mode, too.
================= Logging started at 5/23/2015 09:59:55 AM ==================
Created release folders
ISEXP : fatal error -1001: Error opening MSI database C:\InstallShield 2014 Projects\JROTrial\Express\Express\SingleImage\DiskImages\DISK1\Jackpot Rodeo Trial Installation.msi
Express\SingleImage - 1 error(s), 0 warning(s)
================= Logging stopped at 5/23/2015 09:59:56 AM ==================
Log file has been created:
Has anybody experienced this? It's very annoying..
================= Logging started at 5/23/2015 09:59:55 AM ==================
Created release folders
ISEXP : fatal error -1001: Error opening MSI database C:\InstallShield 2014 Projects\JROTrial\Express\Express\SingleImage\DiskImages\DISK1\Jackpot Rodeo Trial Installation.msi
Express\SingleImage - 1 error(s), 0 warning(s)
================= Logging stopped at 5/23/2015 09:59:56 AM ==================
Log file has been created:
Has anybody experienced this? It's very annoying..
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 24, 2015
03:09 PM
I've also re-registered the stuff (msi.dll, etc.) the help text tells you to re-register, and I have the latest msi (5.0). I'm on Windows 8.1.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 20, 2015
04:48 PM
FYI, this problem still exists in InstallShield Express 2015, and nobody seems to care that much.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 10, 2015
03:07 PM
It's not reproducible on my end. Would it be possible for you to post a sample project that replicates the behavior so that I can look into the issue further?
Thank you for your patience and cooperation.
Thank you for your patience and cooperation.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 17, 2015
11:51 AM
hidenori wrote:
It's not reproducible on my end. Would it be possible for you to post a sample project that replicates the behavior so that I can look into the issue further?
Thank you for your patience and cooperation.
I'm also getting this error from my service installer. I'm using VS 2012 (tried it also with VS 2015) and Windows 10. I've installed InstallShield 2015 LE and rebuilt the solution, but continue to get the 1001 error when attempting to perform the install. There doesn't appear to be a way to see which InstallShield LE version Visual Studio is actually using. I had been using an older version (2012 I believe).
-Lee
![](/skins/images/8C9D13A71C7F7695F3262372C0172D68/responsive_peak/images/icon_anonymous_message.png)