Phatado
09-11-2009, 06:40 AM
We are having a problem with a minor upgrade, though we have had this working for other language versions of the installer.
The installer is localised into several languages and there is a Standard and Extended release for each locale. Several languages have had Standard and Extended varients already which work fine.
The differences are:
1. The 4th build number
2. The Package code
3. A property to signify if they are Standard or Extended.
4. A few file minor changes (doc files and their companions)
As stated, this has worked fine for all previous language releases, however we now have one where the setup.exe appears to fail running at all. Looking at the log file for an install that upgrades properly (Brazilian) I see the following:
MSI (c) (EC:1C) [10:54:06:436]: Command Line: REINSTALL=ALL REINSTALLMODE=vomus IS_MINOR_UPGRADE=1 SETUPEXEDIR=C:\Documents and Settings\Test Engineer\Desktop SETUPEXENAME=setup.exe CURRENTDIRECTORY=C:\Documents and Settings\Test Engineer\Desktop CLIENTUILEVEL=0 CLIENTPROCESSID=1772
However with the one that fails to work (Slovak) we get:
MSI (c) (6C:EC) [10:55:48:564]: No Command Line.
I have noticed a difference at the start of the log file that failed - it immediately starts trying to run the MSI logged in the cache from the previous install:
=== Verbose logging started: 9/11/2009 10:55:48 Build type: SHIP UNICODE 3.01.4000.4039 Calling process: C:\Documents and Settings\Test Engineer\Desktop\setup.exe ===
MSI (c) (6C:EC) [10:55:48:346]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'C:\WINDOWS\Installer\34182.msi' against software restriction policy
MSI (c) (6C:EC) [10:55:48:346]: SOFTWARE RESTRICTION POLICY: C:\WINDOWS\Installer\34182.msi has a digital signature
MSI (c) (6C:EC) [10:55:48:471]: SOFTWARE RESTRICTION POLICY: C:\WINDOWS\Installer\34182.msi is permitted to run at the 'unrestricted' authorization level.
MSI (c) (6C:EC) [10:55:48:486]: Cloaking enabled.
However the one that worked seems to run from the current installer cache
=== Verbose logging started: 9/11/2009 10:54:00 Build type: SHIP UNICODE 3.01.4000.4039 Calling process: C:\WINDOWS\system32\MSIEXEC.EXE ===
MSI (c) (EC:1C) [10:54:00:952]: Resetting cached policy values
MSI (c) (EC:1C) [10:54:00:952]: Machine policy value 'Debug' is 0
MSI (c) (EC:1C) [10:54:00:952]: ******* RunEngine:
******* Product: C:\Documents and Settings\All Users\Application Data\i2\Installers Cache\{16852922-4495-42AD-895A-9A6958B6E8B2}\i2 Analyst's Notebook 7.msi
******* Action:
******* CommandLine: **********
MSI (c) (EC:1C) [10:54:00:967]: Machine policy value 'DisableUserInstalls' is 0
MSI (c) (EC:1C) [10:54:04:498]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'C:\Documents and Settings\All Users\Application Data\i2\Installers Cache\{16852922-4495-42AD-895A-9A6958B6E8B2}\i2 Analyst's Notebook 7.msi' against software restriction policy
MSI (c) (EC:1C) [10:54:04:498]: SOFTWARE RESTRICTION POLICY: C:\Documents and Settings\All Users\Application Data\i2\Installers Cache\{16852922-4495-42AD-895A-9A6958B6E8B2}\i2 Analyst's Notebook 7.msi has a digital signature
MSI (c) (EC:1C) [10:54:06:280]: SOFTWARE RESTRICTION POLICY: C:\Documents and Settings\All Users\Application Data\i2\Installers Cache\{16852922-4495-42AD-895A-9A6958B6E8B2}\i2 Analyst's Notebook 7.msi is permitted to run at the 'unrestricted' authorization level.
NOTE: If I run the Slovak MSI with the command line then it upgrades properly - so it appears to be something in the setup.exe. That said the version number of the setup.exe is the same for both locales.
So, what I have observed in summary:
1. Command line is not being set in the Slovak install
2. The one that works (Brazilian) states on the first line of the log that the calling process is "C:\Windows\System\MSIEXEC.exe" whereas the Slovak log states the calling process is the actual setup.exe - I don't know if this has any affect.
3. I have compared the Brazilian and Slovak setup.ini and the only difference I can see (apart from the produce and Package code) is the Slovak has an additional line:
RTLLangs=0401,040d
as well as in the MSI section the "default" and "key" values have their respective language codes as I would expect.
4. The installers that have worked so far are all Western European installers - Slovak is not
Does anyone have any idea why this may be failing to generate the command line?
The installer is localised into several languages and there is a Standard and Extended release for each locale. Several languages have had Standard and Extended varients already which work fine.
The differences are:
1. The 4th build number
2. The Package code
3. A property to signify if they are Standard or Extended.
4. A few file minor changes (doc files and their companions)
As stated, this has worked fine for all previous language releases, however we now have one where the setup.exe appears to fail running at all. Looking at the log file for an install that upgrades properly (Brazilian) I see the following:
MSI (c) (EC:1C) [10:54:06:436]: Command Line: REINSTALL=ALL REINSTALLMODE=vomus IS_MINOR_UPGRADE=1 SETUPEXEDIR=C:\Documents and Settings\Test Engineer\Desktop SETUPEXENAME=setup.exe CURRENTDIRECTORY=C:\Documents and Settings\Test Engineer\Desktop CLIENTUILEVEL=0 CLIENTPROCESSID=1772
However with the one that fails to work (Slovak) we get:
MSI (c) (6C:EC) [10:55:48:564]: No Command Line.
I have noticed a difference at the start of the log file that failed - it immediately starts trying to run the MSI logged in the cache from the previous install:
=== Verbose logging started: 9/11/2009 10:55:48 Build type: SHIP UNICODE 3.01.4000.4039 Calling process: C:\Documents and Settings\Test Engineer\Desktop\setup.exe ===
MSI (c) (6C:EC) [10:55:48:346]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'C:\WINDOWS\Installer\34182.msi' against software restriction policy
MSI (c) (6C:EC) [10:55:48:346]: SOFTWARE RESTRICTION POLICY: C:\WINDOWS\Installer\34182.msi has a digital signature
MSI (c) (6C:EC) [10:55:48:471]: SOFTWARE RESTRICTION POLICY: C:\WINDOWS\Installer\34182.msi is permitted to run at the 'unrestricted' authorization level.
MSI (c) (6C:EC) [10:55:48:486]: Cloaking enabled.
However the one that worked seems to run from the current installer cache
=== Verbose logging started: 9/11/2009 10:54:00 Build type: SHIP UNICODE 3.01.4000.4039 Calling process: C:\WINDOWS\system32\MSIEXEC.EXE ===
MSI (c) (EC:1C) [10:54:00:952]: Resetting cached policy values
MSI (c) (EC:1C) [10:54:00:952]: Machine policy value 'Debug' is 0
MSI (c) (EC:1C) [10:54:00:952]: ******* RunEngine:
******* Product: C:\Documents and Settings\All Users\Application Data\i2\Installers Cache\{16852922-4495-42AD-895A-9A6958B6E8B2}\i2 Analyst's Notebook 7.msi
******* Action:
******* CommandLine: **********
MSI (c) (EC:1C) [10:54:00:967]: Machine policy value 'DisableUserInstalls' is 0
MSI (c) (EC:1C) [10:54:04:498]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'C:\Documents and Settings\All Users\Application Data\i2\Installers Cache\{16852922-4495-42AD-895A-9A6958B6E8B2}\i2 Analyst's Notebook 7.msi' against software restriction policy
MSI (c) (EC:1C) [10:54:04:498]: SOFTWARE RESTRICTION POLICY: C:\Documents and Settings\All Users\Application Data\i2\Installers Cache\{16852922-4495-42AD-895A-9A6958B6E8B2}\i2 Analyst's Notebook 7.msi has a digital signature
MSI (c) (EC:1C) [10:54:06:280]: SOFTWARE RESTRICTION POLICY: C:\Documents and Settings\All Users\Application Data\i2\Installers Cache\{16852922-4495-42AD-895A-9A6958B6E8B2}\i2 Analyst's Notebook 7.msi is permitted to run at the 'unrestricted' authorization level.
NOTE: If I run the Slovak MSI with the command line then it upgrades properly - so it appears to be something in the setup.exe. That said the version number of the setup.exe is the same for both locales.
So, what I have observed in summary:
1. Command line is not being set in the Slovak install
2. The one that works (Brazilian) states on the first line of the log that the calling process is "C:\Windows\System\MSIEXEC.exe" whereas the Slovak log states the calling process is the actual setup.exe - I don't know if this has any affect.
3. I have compared the Brazilian and Slovak setup.ini and the only difference I can see (apart from the produce and Package code) is the Slovak has an additional line:
RTLLangs=0401,040d
as well as in the MSI section the "default" and "key" values have their respective language codes as I would expect.
4. The installers that have worked so far are all Western European installers - Slovak is not
Does anyone have any idea why this may be failing to generate the command line?