It could be useful to examine the log where the patching accesses the
network MSI to see what actually happens. Typical reasons include installed
files that no longer match the cached MSI. For example the cached (MSI plus
patches) has entries in the file table that say the version of the file on
disk is one thing, but actually on disk it's something else. Windows
doesn't know whether the patch should be applied until it repairs the
install and gets the "right" file to do the version test. This is why
"version lying" is a bad idea. Similar things happen with data files with
mismatched file hashes. That's about all I can think of right now. If
the patch is uninstallable the behavior is a bit different. The timeout is
more like a network/TCP timeout - are the times the same or do they get
larger after each failure?
Does the patch have a UI? If it's trying to resolve the source inside the
execute sequence it may not pop up a UI there, where I'd expect that it
would in the UI sequence, assuming of course it knows that early that the
source is required.
Phil Wilson
On Wed, Jan 8, 2014 at 7:47 AM, darenko6874 . <dtkob...@gmail.com> wrote:
> Can someone tell me why patching a uncompressed image requires the attempt
> to look for source? I am not prompted asking for credentials, but the
> patch log shows it keeps looking for the original install location like
> this:
>
> Resolving source.
> MSI (s) (9C:30) [08:23:26:466]: User policy value 'SearchOrder' is 'nmu'
> MSI (s) (9C:30) [08:23:26:466]: User policy value 'DisableMedia' is 0
> MSI (s) (9C:30) [08:23:26:466]: Machine policy value 'AllowLockdownMedia'
> is 1
> MSI (s) (9C:30) [08:23:26:466]: SOURCEMGMT: Looking for sourcelist for
> product {F15CB215-59FA-4643-AE03-FDB6655BF13F}
> MSI (s) (9C:30) [08:23:26:466]: SOURCEMGMT: Adding
> {F15CB215-59FA-4643-AE03-FDB6655BF13F}; to potential sourcelist list
> (pcode;disk;relpath).
> MSI (s) (9C:30) [08:23:26:466]: SOURCEMGMT: Now checking product
> {F15CB215-59FA-4643-AE03-FDB6655BF13F}
> MSI (s) (9C:30) [08:23:26:466]: SOURCEMGMT: Attempting to use
> LastUsedSource from source list.
> MSI (s) (9C:30) [08:23:26:466]: SOURCEMGMT: Trying source
>
> \\dkwin8\E\reflection_wit15_trunk\installers\Alloy\release_base_uncomp608\x86\prod\2014\.
> MSI (s) (9C:30) [08:24:13:562]: Note: 1: 1314 2:
>
> \\dkwin8\E\reflection_wit15_trunk\installers\Alloy\release_base_uncomp608\x86\prod\2014\
> MSI (s) (9C:30) [08:24:13:562]: ConnectToSource: CreatePath/CreateFilePath
> failed with: -2147483648 1314 -2147483648
> MSI (s) (9C:30) [08:24:13:562]: ConnectToSource (con't):
> CreatePath/CreateFilePath failed with: -2147483648 -2147483648
> MSI (s) (9C:30) [08:24:13:562]: SOURCEMGMT: net source
>
> '\\dkwin8\E\reflection_wit15_trunk\installers\Alloy\release_base_uncomp608\x86\prod\2014\'
> is invalid.
> MSI (s) (9C:30) [08:24:13:562]: Note: 1: 1706 2: -2147483647 3: 2014R1c.msi
> MSI (s) (9C:30) [08:24:13:562]: SOURCEMGMT: Processing net source list.
> MSI (s) (9C:30) [08:24:13:562]: Note: 1: 1706 2: -2147483647 3: 2014R1c.msi
> MSI (s) (9C:30) [08:24:13:562]: SOURCEMGMT: Processing media source list.
> MSI (s) (9C:30) [08:24:14:638]: Note: 1: 2203 2: 3: -2147287037
> MSI (s) (9C:30) [08:24:14:638]: SOURCEMGMT: Source is invalid due to
> missing/inaccessible package.
> MSI (s) (9C:30) [08:24:14:638]: Note: 1: 1706 2: -2147483647 3: 2014R1c.msi
> MSI (s) (9C:30) [08:24:14:638]: SOURCEMGMT: Processing URL source list.
> MSI (s) (9C:30) [08:24:14:638]: Note: 1: 1402 2: UNKNOWN\URL 3: 2
> MSI (s) (9C:30) [08:24:14:638]: Note: 1: 1706 2: -2147483647 3: 2014R1c.msi
> MSI (s) (9C:30) [08:24:14:638]: Note: 1: 1706 2: 3: 2014R1c.msi
> MSI (s) (9C:30) [08:24:14:638]: SOURCEMGMT: Failed to resolve source
> MSI (s) (9C:30) [08:24:14:638]: Failed to generate patch cache opcodes for:
> {F15CB215-59FA-4643-AE03-FDB6655BF13F} product
> MSI (s) (9C:30) [08:24:14:638]: Resolving source.
> ... and it seems to loop for hours.
>
> The cached MSI is on the machine as isn't missing. I've read some other
> posts where this was the case.
>
> I see the Resolve source text, but I don't have the ResolveSource action in
> my MSI. It continues to look with this same text until some time it
> decides to proceed with applying the patch. It could take a few hours or a
> day and it finally applies successfully.
>
> To give some background, I am installing an uncompressed image (I built it
> uncompressed and it's not an administrative installation uncompress image)
> from a UNC path (mapped drive doesn't matter either). I've then
> disconnected from that source (rebooted to make sure it can't connect).
> I've then created 2 patches. Lets just say patch 1 and patch 2. My first
> patch applies in less than 5 minutes. My second patch is what has this
> problem. If I leave it connected to the original source location, the
> second patch applies in under five minutes as well.
>
> If I create the same install image but have a compressed image (all files
> are in an external cab file), then disconnect from source and apply patches
> 1 and 2 (which were rebuilt with the compressed image build), it never
> loops like the patch log above. The second patch applies in under 5
> minutes.
>
> Is this normal behavior? It seems like the installer either needs to
> prompt me for credentials to original source or move on and apply my patch.
> Taking hours to apply the patch is not acceptable. I am baffled by this
> behavior.
>
> ------------------------------------------------------------------------------
> Rapidly troubleshoot problems before they affect your business. Most IT
> organizations don't have a clear picture of how application performance
> affects their revenue. With AppDynamics, you get 100% visibility into your
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics
> Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
