System error -1072807676 / 0xC00E4014 #2
Simon Scott
Can anybody offer any insight on this snippet from a log while applying a
.msp patch? Particularly interested in what System Error -1072807676 means.
Can't find that error code documented anywhere.
Thanks
MSI (s) (7C:24) [12:00:11:943]: Patch for file
'D:\TrilliumSoftware\Server\bin\scheduler.exe' is redirected to patch
'D:\Config.Msi\PT1D70.tmp' instead.
PatchFiles: File: scheduler.exe, Directory:
D:\TrilliumSoftware\Server\bin\, Size: 1190500
MSI (s) (7C:24) [12:00:11:959]: Re-applying security from existing file.
MSI (s) (7C:24) [12:00:11:959]: SOFTWARE RESTRICTION POLICY: Verifying
object --> 'C:\WINDOWS\Installer\2dd9f8b7.msp' against software restriction
policy
MSI (s) (7C:24) [12:00:11:959]: Note: 1: 2262 2: DigitalSignature
3: -2147287038
MSI (s) (7C:24) [12:00:11:959]: SOFTWARE RESTRICTION POLICY:
C:\WINDOWS\Installer\2dd9f8b7.msp is not digitally signed
MSI (s) (7C:24) [12:00:11:959]: SOFTWARE RESTRICTION POLICY:
C:\WINDOWS\Installer\2dd9f8b7.msp is permitted to run at the 'unrestricted'
authorization level.
MSI (s) (7C:24) [12:00:11:959]: Note: 1: 2318 2: D:\Config.Msi\PF1D73.tmp
MSI (s) (7C:24) [12:00:11:975]: Note: 1: 2302 2: 0
MSI (s) (7C:24) [12:00:11:975]: Note: 1: 1328 2: D:\Config.Msi\PT1D70.tmp
3: -1072807676
MSI (c) (8C:94) [12:00:11:975]: Transforming table Binary.
MSI (c) (8C:94) [12:00:11:975]: Transforming table Binary.
MSI (c) (8C:94) [12:00:11:975]: Note: 1: 2262 2: Binary 3: -2147287038 Info
2835.The control ErrorIcon was not found on dialog SetupError.
Error 1328.Error applying patch to file D:\Config.Msi\PT1D70.tmp. It has
probably been updated by other means, and can no longer be modified by this
patch. For more information contact your patch vendor. System
Error: -1072807676
MSI (s) (7C:24) [12:01:30:678]: Product: TSS 11 - Metabase Server -- Error
1328.Error applying patch to file D:\Config.Msi\PT1D70.tmp. It has probably
been updated by other means, and can no longer be modified by this patch.
For more information contact your patch vendor. System Error: -1072807676
Thanks
Simon
Linda Liu[MSFT]
If the patch is the second MSI patch you have ever applied to the product,
this error may be caused by the second patch not obsoleting the first patch.
For more information on this, you may refer to the following blog article:
http://blogs.msdn.com/rflaming/archive/2005/07/09/439825.aspx
Otherwise, the error usually means that the original Window Installer
Package for the product has been damaged or modified. You can uninstall the
product via the Add or Remove Programs and then reinstall it and apply the
update.
Hope this helps.
If you have any question, please feel free to let me know.
Sincerely,
Linda Liu
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Simon...@trilliumsoftware.com
This is only the first patch, so I guess we're looking at the second
option of a damaged or modified original package.
My customer has re-installed from scratch a couple of times and still gets
the error. Is it possible that if there is system policy that prevents the
original package being stored on the system then this error could occur?
Simon
Simon Scott
>>appear to have used the right posting alias. Trying again with Outlook
>>Express<<
Simon
"Linda Liu[MSFT]" <v-l...@online.microsoft.com> wrote in message
news:mwgYCZcL...@TK2MSFTNGHUB02.phx.gbl...
Manfred Preussig
allready on the system is programed in such a way that the patch
possibly wouldn't fit. For example can the patch be written for another
version of this file as existing on the system. It says possibly there
is another patch allready applied but instead it is also possible that
some older (intervening) patch isn't applied yet. If both (the now to be
applied and the older one) patch the same part of the file the newer
patch isn't applyable if the intervening one isn't yet.
That you can't find any information on the error message possibly have
the reason that at some places hex error numbers are used and at some
decimal. This is 0xC00E 4104 in hex (observe the sign!). I don't looked
for this yet but possibly one can find anything at this.
Change: I've looked for the message at google and found (at german
google; possibly a difference) 40 links.
At the location http://m00.cx/mpl/win32api.txt the not really enlighting
message can be found: ERROR_PATCH_WRONG_FILE which says the same I
allready mentioned but not why.
The location http://www.msusenet.com/archive/topic.php/t-2173252.html
gives an example that this error can happen to each file to be patched.
There it is the win95upg.inf from a spanish XP installation with KB322069.
At http://forums.techarena.in/showthread.php?t=538405 you can find a log
shown by the asker which looks like the patch to be applied there is a
difference patch (with that I mean a patch where not the whole file is
replaced but some codes inside the file willbe changed. That's a
possibility to change for example the pre-setting of a variable allready
set in the code of a much-MB code file. The change is only 32 bit in
size and the length of the whole file isn't changed but if one replaces
the whole file of course these all MB have to be downloaded. The
problem: To find the value to be changed it have to be at a pre-known
position. If the file is changed possibly this value is at another
location and the diff-patchwill fail and destroy the whole file). That's
the most-propable scenario for this error to occur in every case.
( The line I mean is
ApplyDelta(
C:\WINDOWS\SoftwareDistribution\Download\S-1-5-18\20cd36d7283b4940f5d55fba9d008bc7\SP1QFE\asms\60
\msft\windows\common\controls\comctl32.dll,
_sfx_0000._p ) failed (3222159620, 0xC00E4104) )
So the best suggestion is to look for older patches for this file
possibly overlooked in past. Or ask the vendor for a patch version not
relying on the older patch. Or look for a version missmatch from other
source.
greetings
Manfred Preussig
Manfred Preussig
allready on the system is programed in such a way that the patch
possibly wouldn't fit. For example can the patch be written for another
version of this file as existing on the system. It says possibly there
is another patch allready applied but instead it is also possible that
some older (intervening) patch isn't applied yet. If both (the now to be
applied and the older one) patch the same part of the file the newer
patch isn't applyable if the intervening one isn't yet.
There's something happened due to not fully read header (being to fast).
Of course you know the problem with hex and decimal. But the value
you've calculated I think is wrong. Just a little number-turning (or how
this will be said in english) in the middle. This is 0xC00E 4104 not
0xC00E4014 in hex. I've looked for the message at google and found (at
german google; possibly a difference) 40 links. Some of these are stupid
(some commercial 'helpers' make google to show there page on every
question dealing with errors or problems. Most of the time they really
don't have anything on the error just looked for) but some show
additional information:
At the location http://m00.cx/mpl/win32api.txt the not really enlighting
message can be found: ERROR_PATCH_WRONG_FILE which says the same I
allready mentioned but not why.
The location http://www.msusenet.com/archive/topic.php/t-2173252.html
gives an example that this error can happen to each file to be patched.
There it is the win95upg.inf from a spanish XP installation with KB322069.
At http://forums.techarena.in/showthread.php?t=538405 you can find a log
shown by the asker which looks like the patch to be applied there is a
difference patch (with that I mean a patch where not the whole file is
replaced but some codes inside the file will be changed. That's a
possibility to change for example the pre-setting of a variable allready
set in the code of a much-MB code file. The change is only 32 bit in
size and the length of the whole file isn't changed but if one replaces
the whole file of course these all MB have to be downloaded. The
problem: To find the value to be changed it have to be at a pre-known
position. If the file is changed possibly this value is at another
location and the diff-patch will fail and destroy the whole file).
That's the most-propable scenario for this error to occur in every case.
( The line I mean is
ApplyDelta(
C:\WINDOWS\SoftwareDistribution\Download\S-1-5-18\20cd36d7283b4940f5d55fba9d008bc7\SP1QFE\asms\60
\msft\windows\common\controls\comctl32.dll,
_sfx_0000._p ) failed (3222159620, 0xC00E4104) )
So the best suggestion is to look for older patches for this file
possibly overlooked in past. Or ask the vendor for a patch version not
relying on the older patch. Or look for a version missmatch from other
source (for example an in-official patch, an upgrade or a replacement by
a plug-in).
greetings
Manfred Preussig
Simon Scott
the error to look for is 0xC00E4104, not 4014 as in the subject line.
My problem is that I (or rather my employer) is the patch vendor. So the
patch and the original installation package are in my control. But this is
just one customer that fails to install the patch - other customers are
okay. But it seems pretty clear from your links that MSI doesn't think the
original file version in the patch matches the installed version. I'll keep
looking....
Thanks for your help anyway.
"Manfred Preussig" <Preu...@web.de> wrote in message
news:fibodv$q8d$1...@news.albasani.net...
Linda Liu[MSFT]
How about the problem now?
> Is it possible that if there is system policy that prevents the original
package being stored on the system then this error could occur?
What's the version of OS on the problematic machine? I don't think there's
a system policy that prevents the original package being stored on the
system.
If you can uninstall an installed product from a machine via Add/Remove
Programs without a dialog prompted asking for a installation source, the
original installation package must have been stored in the machine properly.