Patch Taking Long to Apply...
Hi All,
We have a patch that contains approximately 40 files, but they are all fairly small. When we apply the patch, it seems to take a long time to install. What would be causing this? It's actually taking longer to apply the patch than it does to install the complete application.
I guess I'll try logging and examine that to see what is taking so long....
Here's some events and surrounding log file entries where time gaps occur..
MSI © (E8:84) [10:47:33:409]: Validating transform 'Target01ToUpgrade01' with validation bits 0x922
MSI © (E8:84) [10:47:33:409]: Transform 'Target01ToUpgrade01' is valid.
MSI © (E8:84) [10:47:33:472]: Note: 1: 2262 2: Property 3: -2147287038
MSI © (E8:84) [10:47:33:472]: Note: 1: 2262 2: Feature 3: -2147287038
MSI © (E8:84) [10:47:33:472]: Note: 1: 2262 2: Condition 3: -2147287038
MSI © (E8:84) [10:47:34:487]: Exceeded 64K strings. Bumping database string index size.
MSI © (E8:84) [10:50:55:475]: Note: 1: 2262 2: Dialog 3: -2147287038
MSI © (E8:84) [10:50:55:475]: Note: 1: 2262 2: InstallUISequence 3: -2147287038
MSI © (E8:84) [10:50:55:475]: Note: 1: 2262 2: AdminUISequence 3: -2147287038
MSI © (E8:84) [10:50:55:475]: Note: 1: 2262 2: AdminExecuteSequence 3: -2147287038
MSI (s) (34:10) [10:52:18:367]: Validating transform 'Target01ToUpgrade01' with validation bits 0x922
MSI (s) (34:10) [10:52:18:367]: Transform 'Target01ToUpgrade01' is valid.
MSI (s) (34:10) [10:52:18:461]: Note: 1: 2262 2: Property 3: -2147287038
MSI (s) (34:10) [10:52:18:461]: Note: 1: 2262 2: Feature 3: -2147287038
MSI (s) (34:10) [10:52:18:476]: Note: 1: 2262 2: Condition 3: -2147287038
MSI (s) (34:10) [10:52:19:476]: Exceeded 64K strings. Bumping database string index size.
MSI (s) (34:10) [10:55:39:806]: Note: 1: 2262 2: Dialog 3: -2147287038
MSI (s) (34:10) [10:55:39:806]: Note: 1: 2262 2: InstallUISequence 3: -2147287038
MSI (s) (34:10) [10:55:39:806]: Note: 1: 2262 2: AdminUISequence 3: -2147287038
MSI (s) (34:10) [10:55:39:822]: Note: 1: 2262 2: AdminExecuteSequence 3: -2147287038
MSI (s) (34:10) [10:55:39:822]: Note: 1: 2262 2: AdvtExecuteSequence 3: -2147287038
The rest of the logging seemed to indicate no significant time gaps for one operation. Does anyone know what might be causing this? If you need the full log or more snippets, please let me know.
We have a patch that contains approximately 40 files, but they are all fairly small. When we apply the patch, it seems to take a long time to install. What would be causing this? It's actually taking longer to apply the patch than it does to install the complete application.
I guess I'll try logging and examine that to see what is taking so long....
Here's some events and surrounding log file entries where time gaps occur..
MSI © (E8:84) [10:47:33:409]: Validating transform 'Target01ToUpgrade01' with validation bits 0x922
MSI © (E8:84) [10:47:33:409]: Transform 'Target01ToUpgrade01' is valid.
MSI © (E8:84) [10:47:33:472]: Note: 1: 2262 2: Property 3: -2147287038
MSI © (E8:84) [10:47:33:472]: Note: 1: 2262 2: Feature 3: -2147287038
MSI © (E8:84) [10:47:33:472]: Note: 1: 2262 2: Condition 3: -2147287038
MSI © (E8:84) [10:47:34:487]: Exceeded 64K strings. Bumping database string index size.
MSI © (E8:84) [10:50:55:475]: Note: 1: 2262 2: Dialog 3: -2147287038
MSI © (E8:84) [10:50:55:475]: Note: 1: 2262 2: InstallUISequence 3: -2147287038
MSI © (E8:84) [10:50:55:475]: Note: 1: 2262 2: AdminUISequence 3: -2147287038
MSI © (E8:84) [10:50:55:475]: Note: 1: 2262 2: AdminExecuteSequence 3: -2147287038
MSI (s) (34:10) [10:52:18:367]: Validating transform 'Target01ToUpgrade01' with validation bits 0x922
MSI (s) (34:10) [10:52:18:367]: Transform 'Target01ToUpgrade01' is valid.
MSI (s) (34:10) [10:52:18:461]: Note: 1: 2262 2: Property 3: -2147287038
MSI (s) (34:10) [10:52:18:461]: Note: 1: 2262 2: Feature 3: -2147287038
MSI (s) (34:10) [10:52:18:476]: Note: 1: 2262 2: Condition 3: -2147287038
MSI (s) (34:10) [10:52:19:476]: Exceeded 64K strings. Bumping database string index size.
MSI (s) (34:10) [10:55:39:806]: Note: 1: 2262 2: Dialog 3: -2147287038
MSI (s) (34:10) [10:55:39:806]: Note: 1: 2262 2: InstallUISequence 3: -2147287038
MSI (s) (34:10) [10:55:39:806]: Note: 1: 2262 2: AdminUISequence 3: -2147287038
MSI (s) (34:10) [10:55:39:822]: Note: 1: 2262 2: AdminExecuteSequence 3: -2147287038
MSI (s) (34:10) [10:55:39:822]: Note: 1: 2262 2: AdvtExecuteSequence 3: -2147287038
The rest of the logging seemed to indicate no significant time gaps for one operation. Does anyone know what might be causing this? If you need the full log or more snippets, please let me know.
0 Comments
[ + ] Show comments
Answers (10)
Please log in to answer
Posted by:
anonymous_9363
14 years ago
Hmmm...-2147287038 is a decimal representation of the hex FFFFFFFF80030002. Remove the leading 8 Fs (as one does) we're left with 80030002. That is a common OLE error - MSIs are based on the OLE document model - where a stream is missing. Quite what it means here, though, is a mystery to me. Normally, I'd expect to see the text 'Stream Not Found' note, too.
Posted by:
Superfreak3
14 years ago
where a stream is missing
What does this mean? What does stream refer to? Is this indicating a problem with the patch package or the original installation being patched or can that not be determined from this type of error?
Should this patch package deploy with this type of error? It seems the files are placed OK, but I'm waiting to hear from QA as to whether functionality is there or not.
I also wonder that if the patch is applicable, will it cause any problems for update down the road.
I did make it a removable patch and filled in the Description, Display Name and Manufacturer Name in the Wise Patch Removal Settings. I checked the their documentation and Classification is a required setting. I did not have that populated and the doc indicates that it is required...
[font="Trebuchet MS"][font="Microsoft Sans Serif"][font="Courier New"]"(Required.) Enter text to describe the category of updates that this patch
belongs to. The category descriptions are arbitrary. Examples: hot fix, security
rollup, update, critical update, service pack, update rollup, and so on."
I'm currently testing this to see if that possibly caused the problem using the value of service pack.
Any further information is appreciated.
UPDATE: Recreating the patch to include the Category description did not appear to shorten the time of application at all.
Posted by:
anonymous_9363
14 years ago
What does this mean? What does stream refer to?As usual, Google to the rescue. See here. Completing those details in Wise will make no difference: those fields are for information only.
Posted by:
Superfreak3
14 years ago
That's all Greek to me. Does that link present the solution/resolution to the issue?
I don't get it [:o]
What did you search for in Google?
http://blogs.msdn.com/heaths/archive/2006/01/18/error-2262-not-necessarily-a-fatal-error.aspx
???
I don't get it [:o]
What did you search for in Google?
http://blogs.msdn.com/heaths/archive/2006/01/18/error-2262-not-necessarily-a-fatal-error.aspx
???
Posted by:
anonymous_9363
14 years ago
Does that link present the solution/resolution to the issue?You asked what streams were. The link contains details about compound files. Essentially, they're files within files.
The link *you* posted tells you what the log details are all about (good work on that, BTW).
Posted by:
Superfreak3
14 years ago
I emailed the blogger about my log details and he indicated that my log 'stuff' looks to be what is expected or is nothing out of the ordinary.
The Patch eventually finishes to completion and app is funtional afterward in the patched areas.
I have no idea what's going on, but I guess we may have to live with the long application time.
Thanks for the help. I'll appreciate anything else you can think of, of course! :D
The Patch eventually finishes to completion and app is funtional afterward in the patched areas.
I have no idea what's going on, but I guess we may have to live with the long application time.
Thanks for the help. I'll appreciate anything else you can think of, of course! :D
Posted by:
anonymous_9363
14 years ago
Did you read Stephan's reply to your identical post on InstallSite? As he points out, it could simply be that the engine takes a long time to increase the string size limit. I would expect that, being a Microsoft product (actually, a Microsoft-ised Wise product), it makes the change once and fails to raise a flag that it already did so and just keeps repeating the exercise.
Posted by:
Superfreak3
14 years ago
I just wonder what is causing the resizing. It has never happened before. Similar patches have applied in 40 seconds to a minute in the past.
I even tried running the patch silently to see if that bypassed anything, but still same.
I even tried running the patch silently to see if that bypassed anything, but still same.
Posted by:
anonymous_9363
14 years ago
A string somewhere exceeds the normal 64K limit, just like the message in the log is telling you. BTW, you *are* intending to apply the patch to an Administrative Installation point, rather than individual clients, aren't you? In which case, why worry? It's a one-off wait. If you're intending to patch clients, good luck...
Posted by:
Superfreak3
14 years ago
Unfortunately, we patch individual clients. That's just the way it was designed.
I tried run Orca validation to see what limit is being exceeded. With version 3.1.4000.2049 of that tool it asks for a Validation File and what ICEs to run. Does anyone know what these might be?
Folowing reception of this tip, I did run Package Validation in Wise and there was some string overflow stuff in there....
Has anyone seen this type of situation before. These are actually from the inclusion of Microsoft_VC80_CRT_x86.msm and policy_8_0_Microsoft_VC80_CRT_x86.msm. I don't know what might have changed with regard to these as they've been included for a while and never caused any overflow, patch delay problems that I can recall. The same goes for the custom action items caught too.
I hope I'm on the right track!
I tried run Orca validation to see what limit is being exceeded. With version 3.1.4000.2049 of that tool it asks for a Validation File and what ICEs to run. Does anyone know what these might be?
Folowing reception of this tip, I did run Package Validation in Wise and there was some string overflow stuff in there....
String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.762.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E ice03.html Component KeyPath downlevel_manifest.8.0.50727.762.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E
Evaluation: ICE03
String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.193.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E ice03.html Component KeyPath downlevel_manifest.8.0.50727.193.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E
Evaluation: ICE03
String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.104.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E ice03.html Component KeyPath downlevel_manifest.8.0.50727.104.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E
Evaluation: ICE03
String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.103.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E ice03.html Component KeyPath downlevel_manifest.8.0.50727.103.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E
Evaluation: ICE03
String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.101.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E ice03.html Component KeyPath downlevel_manifest.8.0.50727.101.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E
Evaluation: ICE03
String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.100.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E ice03.html Component KeyPath downlevel_manifest.8.0.50727.100.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E
Evaluation: ICE03
String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.100.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E ice03.html Component KeyPath downlevel_manifest.8.0.50727.100.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E
Evaluation: ICE03
String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.101.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E ice03.html Component KeyPath downlevel_manifest.8.0.50727.101.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E
Evaluation: ICE03
String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.103.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E ice03.html Component KeyPath downlevel_manifest.8.0.50727.103.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E
Evaluation: ICE03
String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.104.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E ice03.html Component KeyPath downlevel_manifest.8.0.50727.104.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E
Evaluation: ICE03
String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.762.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E ice03.html Component KeyPath downlevel_manifest.8.0.50727.762.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E
Evaluation: ICE03
String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.193.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E ice03.html Component KeyPath downlevel_manifest.8.0.50727.193.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E
Evaluation: ICE03
String overflow (greater than length permitted in column); Table: Registry, Column: Registry, Key(s): reg_downlevel_manifest.8.0.50727.762.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E ice03.html Registry Registry reg_downlevel_manifest.8.0.50727.762.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E
Evaluation: ICE03
String overflow (greater than length permitted in column); Table: Registry, Column: Registry, Key(s): reg_downlevel_manifest.8.0.50727.193.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E ice03.html Registry Registry reg_downlevel_manifest.8.0.50727.193.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E
Evaluation: ICE03
String overflow (greater than length permitted in column); Table: Registry, Column: Registry, Key(s): reg_downlevel_manifest.8.0.50727.104.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E ice03.html Registry Registry reg_downlevel_manifest.8.0.50727.104.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E
Evaluation: ICE03
String overflow (greater than length permitted in column); Table: Registry, Column: Registry, Key(s): reg_downlevel_manifest.8.0.50727.103.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E ice03.html Registry Registry reg_downlevel_manifest.8.0.50727.103.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E
Evaluation: ICE03
String overflow (greater than length permitted in column); Table: Registry, Column: Registry, Key(s): reg_downlevel_manifest.8.0.50727.101.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E ice03.html Registry Registry reg_downlevel_manifest.8.0.50727.101.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E
Evaluation: ICE03
String overflow (greater than length permitted in column); Table: Registry, Column: Registry, Key(s): reg_downlevel_manifest.8.0.50727.100.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E ice03.html Registry Registry reg_downlevel_manifest.8.0.50727.100.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E
Evaluation: ICE03
String overflow (greater than length permitted in column); Table: Registry, Column: Registry, Key(s): reg_downlevel_manifest.8.0.50727.100.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E ice03.html Registry Registry reg_downlevel_manifest.8.0.50727.100.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E
Evaluation: ICE03
String overflow (greater than length permitted in column); Table: Registry, Column: Registry, Key(s): reg_downlevel_manifest.8.0.50727.101.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E ice03.html Registry Registry reg_downlevel_manifest.8.0.50727.101.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E
Evaluation: ICE03
String overflow (greater than length permitted in column); Table: Registry, Column: Registry, Key(s): reg_downlevel_manifest.8.0.50727.103.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E ice03.html Registry Registry reg_downlevel_manifest.8.0.50727.103.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E
Evaluation: ICE03
String overflow (greater than length permitted in column); Table: Registry, Column: Registry, Key(s): reg_downlevel_manifest.8.0.50727.762.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E ice03.html Registry Registry reg_downlevel_manifest.8.0.50727.762.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E
Evaluation: ICE03
String overflow (greater than length permitted in column); Table: Registry, Column: Registry, Key(s): reg_downlevel_manifest.8.0.50727.104.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E ice03.html Registry Registry reg_downlevel_manifest.8.0.50727.104.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E
Evaluation: ICE03
String overflow (greater than length permitted in column); Table: Registry, Column: Registry, Key(s): reg_downlevel_manifest.8.0.50727.193.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E ice03.html Registry Registry reg_downlevel_manifest.8.0.50727.193.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E
Evaluation: ICE03
String overflow (greater than length permitted in column); Table: CustomAction, Column: Target, Key(s): Set6to8 ice03.html CustomAction Target Set6to8
Evaluation: ICE03
String overflow (greater than length permitted in column); Table: CustomAction, Column: Target, Key(s): Reset8InstallDir ice03.html CustomAction Target Reset8InstallDir
Evaluation: ICE03
String overflow (greater than length permitted in column); Table: CustomAction, Column: Target, Key(s): AVWININIUPDATE ice03.html CustomAction Target AVWININIUPDATE
Evaluation: ICE03
String overflow (greater than length permitted in column); Table: CustomAction, Column: Target, Key(s): Set6to81 ice03.html CustomAction Target Set6to81
Evaluation: ICE03
String overflow (greater than length permitted in column); Table: CustomAction, Column: Target, Key(s): Reset8InstallDir1 ice03.html CustomAction Target Reset8InstallDir1
Evaluation: ICE03
String overflow (greater than length permitted in column); Table: CustomAction, Column: Target, Key(s): PrintEULA ice03.html CustomAction Target PrintEULA
Evaluation: ICE03
String overflow (greater than length permitted in column); Table: CustomAction, Column: Target, Key(s): EULACleanup ice03.html CustomAction Target EULACleanup
Evaluation: ICE03
String overflow (greater than length permitted in column); Table: CustomAction, Column: Target, Key(s): UpdateNotes ice03.html CustomAction Target UpdateNotes
Evaluation: ICE03
Has anyone seen this type of situation before. These are actually from the inclusion of Microsoft_VC80_CRT_x86.msm and policy_8_0_Microsoft_VC80_CRT_x86.msm. I don't know what might have changed with regard to these as they've been included for a while and never caused any overflow, patch delay problems that I can recall. The same goes for the custom action items caught too.
I hope I'm on the right track!
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.