Software Deployment

Does the installation success without the transform?
What changes are made in the transform?
What does a verbose log tell you regarding why the rollback is triggered?

And first of all:
Don't mess too much with vendor packages as that will break future updates/patches.
If the installation work, then don't fix it.
Ask yourself; are you ever going to install the conflicting package with this vendor package side-by-side? If the answer is not, then why resolve the conflict in the first place.

Thanks for the reply.
Vendor MSI is working fine.
As the process in the environment all the vendor MSI's has to go through the conflict manager(planning to change this process). Please see the below log entries.Pleae advice

Thanks in advance.

[16:35:30:355]: Windows Installer installed the product. Product Name: Quest Software Toad for DB2 v4.6.2.573. Product Version: 4.6.2.573. Product Language: 1033. Installation success or error status: 1603.

MSI (s) (E0:14) [16:35:30:395]: Cleaning up uninstalled install packages, if any exist
MSI (s) (E0:14) [16:35:30:395]: MainEngineThread is returning 1603
=== Logging stopped: 08/24/2010 16:35:30 ===
MSI (s) (E0:04) [16:35:30:425]: User policy value 'DisableRollback' is 0
MSI (s) (E0:04) [16:35:30:425]: Machine policy value 'DisableRollback' is 0
MSI (s) (E0:04) [16:35:30:425]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (E0:04) [16:35:30:425]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (E0:04) [16:35:30:425]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (E0:04) [16:35:30:425]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (E0:04) [16:35:30:425]: Restoring environment variables
MSI (c) (B8:B0) [16:35:30:435]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (B8:B0) [16:35:30:435]: MainEngineThread is returning 1603

Regarding the "verbose" log; please post the lines where the actual error occur.
So what changes are made/applied by the transform?

I made the changes using conflict manager(solved the conflicts automatically) using Admin studio Application manager.

I can see "Machine policy value 'DisableRollback' is 0" in the log file. Will this make any effect to the MSI.

- One, no-one can possibly know what's going on here without at least a clue from the log. Unfortunately, the fragment you posted is useless. 99% of the time, the only relevant sections of a failed install's log are the dozen or so lines above and below where the text 'Return value=3. occurs. As advised, please post these lines, remembering to use the CODE tag (to avoid making the post unwieldy).

- Two, DisableRollback=0 means that rollback hasNOT been disabled, something which 0.24 seconds with Google would have informed you.

STEP1. We will import the vendor MSI into Application Manager(Conflict Manager)
STEP2. We will run the Conflicts. Admin Studio's Application Manager will create 2 transform after resolving the conflicts


am I mistaken or does this result in changing (or well equalising but same difference) component GUIDS for conflicting components? And if so am I wrong to be horrified at doing this to a vendor MSI (as in STEP 4)? Or is this not like the Wise Conflict manager I remember from back in the days?

Just wondering

PJ

I really *must* concentrate more in the morning: I completely missed the fact that the Ramesh was talking about a vendor MSI.

@Ramesh: the generally accepted method for dealing with conflicts with vendor MSIs is to simply document them. As Pieter alludes, once you alter component GUIDs, you potentially mess up patches and upgrades, not to mention the likelihood that the vendor's support for your installation disappears.

maybe i do not correctly understand because my english is not my primary language, but i do not understand when you say you open the msi, apply changes from the mst, and save the msi. this is not the way to work with mst files.

you should never modify a vendor msi. you need to pass the mst file to the msi on the command line, like:

msiexec /i msifile.msi TRANSFORMS=mstfile.mst /qb

am i wrong about your question?

@VBScab, As you mentioned i am including the lines from the log file.

User policy value 'SearchOrder' is 'nmu'
MSI (s) (E0:14) [16:35:15:604]: Machine policy value 'DisableBrowse' is 0
MSI (s) (E0:14) [16:35:15:604]: Machine policy value 'AllowLockdownBrowse' is 1
MSI (s) (E0:14) [16:35:15:604]: Adding new sources is allowed.
MSI (s) (E0:14) [16:35:15:604]: Set LastUsedSource to: Z:\Package_Source\working\Quest Management Suite for DB2 LUW Commercial\1_LegacyInstallation\Quest Management Suite for DB2 LUW Commercial\Toad for DB2 4.6.2 Commercial\.
MSI (s) (E0:14) [16:35:15:604]: Set LastUsedType to: n.
MSI (s) (E0:14) [16:35:15:604]: Set LastUsedIndex to: 1.
MSI (s) (E0:14) [16:35:15:614]: Executing op: ActionStart(Name=DB2PreProcessInstallCA.2BC48F01_561E_4906_8321_946A9F5A90AA,,)
MSI (s) (E0:14) [16:35:16:046]: Executing op: CustomActionSchedule(Action=DB2PreProcessInstallCA.2BC48F01_561E_4906_8321_946A9F5A90AA,ActionType=3073,Source=BinaryData,Target=PreProcessInstallCA,)
MSI (s) (E0:94) [16:35:16:087]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI12.tmp, Entrypoint: PreProcessInstallCA
MSI (s) (E0:14) [16:35:16:851]: User policy value 'DisableRollback' is 0
MSI (s) (E0:14) [16:35:16:851]: Machine policy value 'DisableRollback' is 0
Action ended 16:35:16: InstallFinalize. Return value 3.
MSI (s) (E0:14) [16:35:16:871]: Executing op: Header(Signature=1397708873,Version=405,Timestamp=1025016893,LangId=1033,Platform=0,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
MSI (s) (E0:14) [16:35:16:871]: Executing op: DialogInfo(Type=0,Argument=1033)
MSI (s) (E0:14) [16:35:16:871]: Executing op: DialogInfo(Type=1,Argument=Quest Software Toad for DB2 v4.6.2.573)
MSI (s) (E0:14) [16:35:16:871]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files...,CleanupTemplate=File: [1])

Hi All,

It is working fine now.Thanks for your reply. After running the Vendor MSI in the conflict manager some of the custom actions sequence numbers changed.

Thanks to all

It is working fine now.Thanks for your reply. After running the Vendor MSI in the conflict manager some of the custom actions sequence numbers changed.

I Rest My Case [:D]

I appreciate that you now have a fix...sorry, a work-around but

- One, that doesn't look like a verbose log to me: there are not enough entries for Custom Actions starting, for example;
- Two, you didn't use the CODE tag.

Thanks VBSCAB
Its not the total verbose log file.The actual file is more than 3Mb in size. I just copied some of the entries before and after Return value 3. I am following appdeploy since 5 years but i am not a member and i did not post the enough messages in the forum.So i really dont know how to use the CODE tag. My assumption is <CODE></CODE>.If it is correct i will use this next time onwards.

Thanks

hmmm

don't you see the "code" button, third from the right on first line?

@kardock: if using any browser other than IE, you get a slightly different UI when posting e.g. the CODE tag is marked as '<%'.

@reethu005: you've been browsing for F I V E years and have failed to notice a single mention of the tag?!? You're close, anyway. replace the 'greater than' and 'less than' symbols with square brackets and you have it. And there's no need to wait for your next post: you can edit your old one to include the tag.