2 replies to this topic

[Richard Eagle]

Check that GUID or unique in products.  

=== Verbose logging started: 15/02/02  16:43:01  Build type: SHIP UNICODE 2.00.2600.00  Calling process: C:\NT\System32\msiexec.exe ===
MSI © (30:2B): Resetting cached policy values
MSI © (30:2B): Machine policy value 'Debug' is 0
MSI © (30:2B): ******* RunEngine:
          ******* Product: \\psn006\release\Pre-Release\Integrated\Nitrogen\Build 95\CD Image\Financials\PS Financials.msi
          ******* Action:
          ******* CommandLine: **********
MSI © (30:2B): Incrementing counter to disable shutdown. Counter after increment: 0
MSI © (30:2B): Machine policy value 'DisableUserInstalls' is 0
MSI © (30:2B): Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
MSI © (30:2B): End dialog not enabled
MSI © (30:2B): Original package ==> \\psn006\release\Pre-Release\Integrated\Nitrogen\Build 95\CD Image\Financials\PS Financials.msi
MSI © (30:2B): Package we're running from ==> C:\NT\Installer\83c70.msi

Properties of C:\NT\Installer\83c70.msi confirm it is not the same product as PS Financials.msi.
Why is it running C:\NT\Installer\83c70.msi?

[Stefan Krueger]

Different product code AND different package code?

[Richard Eagle]

Thanks for pointing me in the right direction.
Package code different in projects but not in msi file!

Caused by the following code:
 var oProject = new ActiveXObject( "ISWiAutomation.ISWiProject" );
   sProjectFile = ...;
   oProject.OpenProject( sProjectFile );
   // Get release
   oRelease.Build();
   oProject.CloseProject();

   sProjectFile = ...;
   oProject.OpenProject( sProjectFile );
   // Get release
   oRelease.Build();
   oProject.CloseProject();

Problem fixed by getting a new oProject for the 2nd build.