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
- :
- Chained MSIs
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
‎Oct 15, 2008
10:37 AM
Chained MSIs
I'm attempting to use the Windows Installer 4.5 "chained MSIs" feature using InstallShield 2009, but have been encountering problems. If I set them to stream into the project, I invariably get an error at build time - "Cannot save target databse" (sic). It's not a show-stopper as I can always include the MSIs as components and run them from the temp folder, but it would be nice not to have odd files lying around on the target machine. Can anyone help?
TIA
Ian Johnson.
TIA
Ian Johnson.
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 15, 2008
11:31 AM
I'm scraping my memory here, but I think that error may have been caused by unfortunate choices of package names. I don't remember if it was a length issue, or invalid character issue. If you try renaming the labels in the releases view under Chained .msi packages to short letters-and-numbers-no-spaces names, this would probably go away. (For instance try "msxml3" to replace something like "Microsoft XML 3 Redistributable Package".)
These names are only used internally, so do not have any impact on the install, so it is safe to change them. Unfortunately IS2009 doesn't detect the names that will cause problems and prevent you from choosing them.
These names are only used internally, so do not have any impact on the install, so it is safe to change them. Unfortunately IS2009 doesn't detect the names that will cause problems and prevent you from choosing them.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 16, 2008
08:33 AM
Thanks for the reply - problem solved 🙂 My names already didn't contain any spaces so I knew this wouldn't be the issue, but after some experimentation I've found the limit to be 9 characters - any more than this and the build fails with the aforementioned error.
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)