Hi Everyone,

This is my first post here. I have some queries related to MSI uninstallation.

Is the source MSI always required during MSI uninstallation? My understanding was, it is not required since the MSI is always cached on the machine where you install it and all data stored in Binary table and accessed in the custom actions is also present in this cached MSI.

In my MSI, all the components and features are designed to Install Local. My MSI is a thick MSI ie. cabs inside. Last few lines of the uninstallation log, where the uninstallation gets stuck for source MSI are as below. Any idea why the source MSI is required and any tips to get rid of the source MSI?
--------------------------------------------------------
Action ended 10:44:55: CostFinalize. Return value 1.
MSI (s) (CC:9C) [10:44:55:374]: Resolving source.
MSI (s) (CC:9C) [10:44:55:374]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (CC:9C) [10:44:55:374]: User policy value 'DisableMedia' is 0
MSI (s) (CC:9C) [10:44:55:374]: Machine policy value 'AllowLockdownMedia' is 0
MSI (s) (CC:9C) [10:44:55:374]: SOURCEMGMT: Media enabled only if package is safe.
MSI (s) (CC:9C) [10:44:55:374]: SOURCEMGMT: Looking for sourcelist for product {297FC405-62BA-4B2E-AA35-33515A0804A4}
MSI (s) (CC:9C) [10:44:55:374]: SOURCEMGMT: Adding {297FC405-62BA-4B2E-AA35-33515A0804A4}; to potential sourcelist list (pcode;disk;relpath).
MSI (s) (CC:9C) [10:44:55:374]: SOURCEMGMT: Now checking product {297FC405-62BA-4B2E-AA35-33515A0804A4}
MSI (s) (CC:9C) [10:44:55:374]: SOURCEMGMT: Media is enabled for product.
MSI (s) (CC:9C) [10:44:55:374]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (s) (CC:9C) [10:44:55:374]: SOURCEMGMT: Trying source \\ixin-vijaym\c$\Program Files\IxiaInstallerCache\IxNetwork\5.30.90.103a\.
MSI (s) (CC:9C) [10:44:56:586]: Note: 1: 1314 2: \\ixin-vijaym\c$\Program Files\IxiaInstallerCache\IxNetwork\5.30.90.103a\
MSI (s) (CC:9C) [10:44:56:586]: ConnectToSource: CreatePath/CreateFilePath failed with: -2147483648 1314 -2147483648
MSI (s) (CC:9C) [10:44:56:586]: ConnectToSource (con't): CreatePath/CreateFilePath failed with: -2147483648 -2147483648
MSI (s) (CC:9C) [10:44:56:586]: SOURCEMGMT: net source '\\ixin-vijaym\c$\Program Files\IxiaInstallerCache\IxNetwork\5.30.90.103a\' is invalid.
MSI (s) (CC:9C) [10:44:56:586]: Note: 1: 1706 2: -2147483647 3: IxNetwork.msi
MSI (s) (CC:9C) [10:44:56:586]: SOURCEMGMT: Processing net source list.
MSI (s) (CC:9C) [10:44:56:586]: Note: 1: 1706 2: -2147483647 3: IxNetwork.msi
MSI (s) (CC:9C) [10:44:56:586]: SOURCEMGMT: Processing media source list.
MSI (s) (CC:9C) [10:44:57:647]: Note: 1: 2203 2: 3: -2147287037
MSI (s) (CC:9C) [10:44:57:647]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (CC:9C) [10:44:57:647]: Note: 1: 1706 2: -2147483647 3: IxNetwork.msi
MSI (s) (CC:9C) [10:44:57:647]: SOURCEMGMT: Processing URL source list.
MSI (s) (CC:9C) [10:44:57:647]: Note: 1: 1402 2: UNKNOWN\URL 3: 2
MSI (s) (CC:9C) [10:44:57:647]: Note: 1: 1706 2: -2147483647 3: IxNetwork.msi
MSI (s) (CC:9C) [10:44:57:647]: Note: 1: 1706 2: 3: IxNetwork.msi
Action start 10:44:55: ResolveSource.
-------------------------------------------------------------------------------

Thanks,

Vijay
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Vijay,

cache msi doesn't contain all the files and details.

You will have to use SOURCELIST property and mention the network location where source exist.

Regards,
Answered 06/02/2009 by: djain3
Second Degree Blue Belt

Please log in to comment
0
Thanks for the response, Deepak.

Would you be able to explain the kind of information that is missing from the cached MSI?

Thanks,

Vijay
Answered 06/02/2009 by: imvijay123
Senior Yellow Belt

Please log in to comment
1
ResolveSource...is your clue. Generally speaking, you don't need to resolve the source of files for uninstallation so this action can be conditioned-out by, for example, using 'NOT Installed'. As usual, MSDN is your friend http://msdn.microsoft.com/en-us/library/aa371232(VS.85).aspx

Would you be able to explain the kind of information that is missing from the cached MSI? MSDN tells all. Again.
Answered 06/02/2009 by: VBScab
Red Belt

Please log in to comment
0
all files are stripped from the cache.

Any CA's that reference the source as Ian eluded to will require source. Its bad practice for the source not to be present anyway.

As djain3 mentioned look into the SourceList property as this is a bad place to be installing from

\\ixin-vijaym\c$\Program Files\IxiaInstallerCache\IxNetwork\5.30.90.103a
Answered 06/03/2009 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment
0
ORIGINAL: jmcfadyen
As djain3 mentioned look into the SourceList property as this is a bad place to be installing from

\\ixin-vijaym\c$\Program Files\IxiaInstallerCache\IxNetwork\5.30.90.103a


John,

Doesn't this look like the deployment tool which is used is first downloading (caching) the original package locally before triggering the installation and then adds the "cache" location to the sourcelist.
Answered 06/03/2009 by: AngelD
Red Belt

Please log in to comment
0
Perfect, Ian !! The MSI uninstallation works smooth after i conditioned the ResolveSource action.

The architechture of our prodcut though requires ResolveSource to excute during uninstallation since it is dependent upon certain other files from the source location.

Thank You,

Vijay
Answered 06/03/2009 by: imvijay123
Senior Yellow Belt

Please log in to comment
0
Thanks John and Kim for your analysis. Just to clarify, i installed the MSI manually from "\\ixin-vijaym\c$\Program Files\IxiaInstallerCache\IxNetwork\5.30.90.103a" only for testing. My test scenario was to install from network and then disconnect and verify the uninstallation.

Regards,

Vijay
Answered 06/03/2009 by: imvijay123
Senior Yellow Belt

Please log in to comment
0
if the file is that important and for some reason you insist on removing the source then make sure the files are copied locally for use later.

cant see many reasons for needing to use resolve source that can't be solved with another method. except for corporate deployments that are trying to make their own workloads lighter by avioding rework through settings files based centrally.
Answered 06/03/2009 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity