Jump to content


This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Photo

IS 2011 update issue


2 replies to this topic

CymapAndy

CymapAndy
  • Full Members
  • 1 posts

Posted 28 October 2010 - 16:05

Hi,

I've now read lots of cases of error 1706 which seem to be related to merge modules. My problem (according to the log file) is that when running the install again it is looking for an MSI (not MSM) even though the install type generates CABs, EXEs etc.

I've looked at the \Program Files\InstallShield Installation Information\{GUIDs} folder and the original install files are there, but obviously not an MSI.

We've only just upgraded from IS 6.1 and it seems to be a nightmare compared to the simple days of IS 6.1. (Never thought i'd say that...), where our testers could install successive builds of the product easily.

I've done the 'cache' option for merge modules, just in case it was that, but no joy.

The install has both standard MMs and some we've created. Here is the section of the log file where it goes pop!

MSI (s) (38:3C) [03:26:24:359]: SOURCEMGMT: Media enabled only if package is safe.
MSI (s) (38:3C) [03:26:24:359]: SOURCEMGMT: Looking for sourcelist for product {BCA3BFCC-A58B-43DF-886A-0E03FCFBF50C}
MSI (s) (38:3C) [03:26:24:359]: SOURCEMGMT: Adding {BCA3BFCC-A58B-43DF-886A-0E03FCFBF50C}; to potential sourcelist list (pcode;disk;relpath).
MSI (s) (38:3C) [03:26:24:359]: SOURCEMGMT: Now checking product {BCA3BFCC-A58B-43DF-886A-0E03FCFBF50C}
MSI (s) (38:3C) [03:26:24:359]: SOURCEMGMT: Media is enabled for product.
MSI (s) (38:3C) [03:26:24:359]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (s) (38:3C) [03:26:24:359]: SOURCEMGMT: Trying source C:\Program Files\Cymap 2011\{BCA3BFCC-A58B-43DF-886A-0E03FCFBF50C}\.
MSI (s) (38:3C) [03:26:24:375]: SOURCEMGMT: Source is invalid due to invalid package code (product code doesn't match).
MSI (s) (38:3C) [03:26:24:375]: Note: 1: 1706 2: -2147483646 3: Cymap 2011.msi
MSI (s) (38:3C) [03:26:24:375]: SOURCEMGMT: Processing net source list.
MSI (s) (38:3C) [03:26:24:375]: Note: 1: 1706 2: -2147483647 3: Cymap 2011.msi
MSI (s) (38:3C) [03:26:24:375]: SOURCEMGMT: Processing media source list.
MSI (s) (38:3C) [03:26:24:468]: SOURCEMGMT: Trying media source D:\.
MSI (s) (38:3C) [03:26:24:468]: Note: 1: 2203 2: D:\Cymap 2011.msi 3: -2147287038
MSI (s) (38:3C) [03:26:24:468]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (38:3C) [03:26:24:468]: Note: 1: 1706 2: -2147483647 3: Cymap 2011.msi
MSI (s) (38:3C) [03:26:24:468]: SOURCEMGMT: Processing URL source list.
MSI (s) (38:3C) [03:26:24:468]: Note: 1: 1402 2: UNKNOWN\URL 3: 2
MSI (s) (38:3C) [03:26:24:468]: Note: 1: 1706 2: -2147483647 3: Cymap 2011.msi
MSI (s) (38:3C) [03:26:24:468]: Note: 1: 1706 2: 3: Cymap 2011.msi
MSI (s) (38:3C) [03:26:24:468]: SOURCEMGMT: Failed to resolve source
MSI (s) (38:3C) [03:27:27:078]: Product: Cymap 2011 -- Error 1706.No valid source could be found for product Cymap 2011. The Windows Installer cannot continue.

So don't understand why it is searching for an MSI when it isn't an MSI project.

Hoping someone can point me in the right direction.

Andy.

Taco Bell

Taco Bell

    IS6 Expert

  • Moderators
  • 1,281 posts

Posted 29 October 2010 - 13:18

Sorry to hear of your troubles, but my best advice to to contact Flexera about such IS upgrade issues.
user posted image

Stefan Krueger

Stefan Krueger

    InstallSite.org

  • Administrators
  • 13,269 posts

Posted 29 October 2010 - 16:04

The log file is from an msi install, not from a pure InstallScript setup. If your project is indeed pure InstallScript (not "InstallScript MSI") and you include merge modules, then InstallShield automatically creates an additional MSI setup that holds the merge modules, and calls this MSI as part of your InstallScript setup. That's required becauee InstallScript doesn't have native support for merge modules.

Which version of InstallShield are you using? I think there was a known problem which might be fixed in later versions (test with the trial of IS 2011).