Now Commiserating...Update Failure

  • Thread starter Thread starter Donald Anadell
  • Start date Start date
D

Donald Anadell

Greetings,

For the first time since installing WD Beta 2 on a Client Machine(Windows XP SP2)
back on February 14th, I've encountered a problem with updating the Signature(Definition)
file this morning. Downloaded but failed to install.

So I can now commiserate with all those who have been posting in these groups about
their experiences with update problems with WD Beta 2. I thought I was immune to such
problems having never experienced any before(chortle).

I note here that other than the Invalid Pointer error(0x80004003) in the UI, this is the first
time I've encounter a problem with my Windows Defender Beta 2 installation.
And certainly I'd never encountered any problems with Signature updates before this morning.

The good news of course is that I was able to get it to install by running the well publicized
Command line fix:
Msiexec /x {A5CC2A09-E9D3-49EC-923D-03874BBD4C2C}

So that now I in fact have the latest version of the Signatures installed...1.14.1325.6

The bad news is that I've now learned that I'm not immune to update problems as I had
previously thought since my initial installation back on 2-14-06.

If anyone is interested, below are the Event Viewer "Application||System" error reports.
Also included is the Windows Installer Log information on the install failure with error 1603.

Note: In order to get a Windows Installer Log generated I had to turn it on by adding
the following Registry entry:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer
String Value: Logging
Data Value: voicewarmup

Event Viewer Application Error:
Date: 3-17-2006
Time: 8:36:05 AM
Type: Error
Source: MisInstaller
Catagory: None
Event ID: 1024
Discription:
Product: Windows Defender Signatures - Update '{9AD8C4EE-808D-430C-BA88-6075B2053507}'
could not be installed. Error code 1603.

Event Viewer System Error:
Date: 3-17-2006
Time: 8:36:05 AM
Type: Error
Source: Windefend
Catagory: None
Event ID: 2001
Discription:
Windows Defender has encountered an error trying to update signatures.
Error code: 0x80070002
Error description: The system cannot find the file specified.

Windows Installer Log Report:
Property(S): SourcedirProduct = {A5CC2A09-E9D3-49EC-923D-03874BBD4C2C}
MSI (s) (98:04) [07:46:30:125]: Product: Windows Defender Signatures - Update '{9AD8C4EE-808D-430C-BA88-6075B2053507}' could not be
installed.
Error code 1603. Additional information is available in the log file C:\DOCUME~1\PREFER~1\LOCALS~1\Temp\MSI74389.LOG.
MSI (s) (98:04) [07:46:30:125]: Note: 1: 1729
MSI (s) (98:04) [07:46:30:125]: Product: Windows Defender Signatures -- Configuration failed.
MSI (s) (98:04) [07:46:30:125]: Attempting to delete file C:\WINDOWS\Installer\8974406.msp
MSI (s) (98:04) [07:46:30:125]: Cleaning up uninstalled install packages, if any exist
MSI (s) (98:04) [07:46:30:125]: MainEngineThread is returning 1603
MSI (s) (98:88) [07:46:30:234]: Destroying RemoteAPI object.
MSI (s) (98:08) [07:46:30:234]: Custom Action Manager thread ending.
=== Logging stopped: 3/17/2006 7:46:30 ===
MSI (c) (D0:48) [07:46:30:234]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after
decrement: -1
MSI (c) (D0:48) [07:46:30:234]: MainEngineThread is returning 1603
=== Verbose logging stopped: 3/17/2006 7:46:30 ===

Donald Anadell
 
I noticed this problem last nite... originally thought that the key wasn't
released yet... then thought maybe there's a new engine, therefore new key...
no discovery yet. I then thought I had software prob. uninstalled and
reinstalled... no good either.

I'm surprised you never had problem before... do you have winxp with service
pack 2 or windows 2000... xp was the blame for the first problem. The funny
thing about this one is if you look at event viewer for system, it says it
was successful, but look at events for application, it was a failure... gotta
think about how to fix this now...

Donald Anadell said:
Greetings,

For the first time since installing WD Beta 2 on a Client Machine(Windows XP SP2)
back on February 14th, I've encountered a problem with updating the Signature(Definition)
file this morning. Downloaded but failed to install.

So I can now commiserate with all those who have been posting in these groups about
their experiences with update problems with WD Beta 2. I thought I was immune to such
problems having never experienced any before(chortle).

I note here that other than the Invalid Pointer error(0x80004003) in the UI, this is the first
time I've encounter a problem with my Windows Defender Beta 2 installation.
And certainly I'd never encountered any problems with Signature updates before this morning.

The good news of course is that I was able to get it to install by running the well publicized
Command line fix:
Msiexec /x {A5CC2A09-E9D3-49EC-923D-03874BBD4C2C}

So that now I in fact have the latest version of the Signatures installed...1.14.1325.6

The bad news is that I've now learned that I'm not immune to update problems as I had
previously thought since my initial installation back on 2-14-06.

If anyone is interested, below are the Event Viewer "Application||System" error reports.
Also included is the Windows Installer Log information on the install failure with error 1603.

Note: In order to get a Windows Installer Log generated I had to turn it on by adding
the following Registry entry:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer
String Value: Logging
Data Value: voicewarmup

Event Viewer Application Error:
Date: 3-17-2006
Time: 8:36:05 AM
Type: Error
Source: MisInstaller
Catagory: None
Event ID: 1024
Discription:
Product: Windows Defender Signatures - Update '{9AD8C4EE-808D-430C-BA88-6075B2053507}'
could not be installed. Error code 1603.

Event Viewer System Error:
Date: 3-17-2006
Time: 8:36:05 AM
Type: Error
Source: Windefend
Catagory: None
Event ID: 2001
Discription:
Windows Defender has encountered an error trying to update signatures.
Error code: 0x80070002
Error description: The system cannot find the file specified.

Windows Installer Log Report:
Property(S): SourcedirProduct = {A5CC2A09-E9D3-49EC-923D-03874BBD4C2C}
MSI (s) (98:04) [07:46:30:125]: Product: Windows Defender Signatures - Update '{9AD8C4EE-808D-430C-BA88-6075B2053507}' could not be
installed.
Error code 1603. Additional information is available in the log file C:\DOCUME~1\PREFER~1\LOCALS~1\Temp\MSI74389.LOG.
MSI (s) (98:04) [07:46:30:125]: Note: 1: 1729
MSI (s) (98:04) [07:46:30:125]: Product: Windows Defender Signatures -- Configuration failed.
MSI (s) (98:04) [07:46:30:125]: Attempting to delete file C:\WINDOWS\Installer\8974406.msp
MSI (s) (98:04) [07:46:30:125]: Cleaning up uninstalled install packages, if any exist
MSI (s) (98:04) [07:46:30:125]: MainEngineThread is returning 1603
MSI (s) (98:88) [07:46:30:234]: Destroying RemoteAPI object.
MSI (s) (98:08) [07:46:30:234]: Custom Action Manager thread ending.
=== Logging stopped: 3/17/2006 7:46:30 ===
MSI (c) (D0:48) [07:46:30:234]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after
decrement: -1
MSI (c) (D0:48) [07:46:30:234]: MainEngineThread is returning 1603
=== Verbose logging stopped: 3/17/2006 7:46:30 ===

Donald Anadell
Click to expand...
 
Hi Jordan,

I think I noted in my original post that the Machine I have WD installed on is running Windows XP SP2.

LOL...Yes, hard as it is to believe this was the first time I experienced any problems updating the
Signature(Definitions) with this install. I installed WD the day after it was released and it had been
updating just fine until this lastest update.

Near as I can tell, the Product Key {A5CC2A09-E9D3-49EC-923D-03874BBD4C2C} always remains
the same, but it's version number is updated with each Signatures Patch. It's version numbers pretty much
parallel those of the Windows Defener Signature Version numbers that appear in the Help About screen
with the exception of it's Minor Version number.

ProductInfo(ProductKey={A5CC2A09-E9D3-49EC-923D-03874BBD4C2C} versions:
1.20.0.0
1.20.1272.4
1.20.1276.3
1.20.1276.16
1.20.1282.6
1.20.1286.1
1.20.1288.5
1.20.1314.1
1.20.1315.1
1.20.1325.6
Windows Defender Signature Versions:
1.0.0.0
1.14.1272.4
1.14.1276.3
1.14.1276.16
1.14.1282.6
1.14.1286.1
1.14.1288.5
1.14.1314.1
1.14.1315.1
1.14.1325.6

When I encountered this problem, My Event Viewer showed a System (WinDefend) error 0x80070002
with a corresponding Application (MisInstaller) error 1603.

I tried to run the update three times with the same results. So knowing that the 1603 error
that was produced by Microsoft Windows Installer engine a general error code that indicates
a problem occurred during the installation, I thought I'd generate a Windows Installer log file
on my next attempt to see if I could spot exactly where the 0x80070002 error was occuring.

To generate the log file I had to add the following to the Registry:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer
String Value: Logging
Data Value: voicewarmup

Then I ran the update process again with the same results, this generated a rather voluminous
MSI log file(381KB). Examining the log file it appeared that everything was running fine with
the install until the two update files mpasbase.vdm, and mpasdlta.vdm were to be
installed from C:\Windows\Temp.

It's at this point that MSI log file indicates the failure with error 0x080070002:

INSTALL SIGNATURES: 'CustomActionData' property 'Signature Update Location' is C:\WINDOWS\Temp\.
INSTALL SIGNATURES: ERROR: Signature Update Failed. HRESULT = 0x80070002

That ended my examination of the problem and I simply ran the fix:
Msiexec /x {A5CC2A09-E9D3-49EC-923D-03874BBD4C2C}
and the update was then successful.

Sorry for being so long winded Jordon,

Donald Anadell


Jordan "Jmonkey" H. said:
I noticed this problem last nite... originally thought that the key wasn't
released yet... then thought maybe there's a new engine, therefore new key...
no discovery yet. I then thought I had software prob. uninstalled and
reinstalled... no good either.

I'm surprised you never had problem before... do you have winxp with service
pack 2 or windows 2000... xp was the blame for the first problem. The funny
thing about this one is if you look at event viewer for system, it says it
was successful, but look at events for application, it was a failure... gotta
think about how to fix this now...

Donald Anadell said:
Greetings,

For the first time since installing WD Beta 2 on a Client Machine(Windows XP SP2)
back on February 14th, I've encountered a problem with updating the Signature(Definition)
file this morning. Downloaded but failed to install.

So I can now commiserate with all those who have been posting in these groups about
their experiences with update problems with WD Beta 2. I thought I was immune to such
problems having never experienced any before(chortle).

I note here that other than the Invalid Pointer error(0x80004003) in the UI, this is the first
time I've encounter a problem with my Windows Defender Beta 2 installation.
And certainly I'd never encountered any problems with Signature updates before this morning.

The good news of course is that I was able to get it to install by running the well publicized
Command line fix:
Msiexec /x {A5CC2A09-E9D3-49EC-923D-03874BBD4C2C}

So that now I in fact have the latest version of the Signatures installed...1.14.1325.6

The bad news is that I've now learned that I'm not immune to update problems as I had
previously thought since my initial installation back on 2-14-06.

If anyone is interested, below are the Event Viewer "Application||System" error reports.
Also included is the Windows Installer Log information on the install failure with error 1603.

Note: In order to get a Windows Installer Log generated I had to turn it on by adding
the following Registry entry:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer
String Value: Logging
Data Value: voicewarmup

Event Viewer Application Error:
Date: 3-17-2006
Time: 8:36:05 AM
Type: Error
Source: MisInstaller
Catagory: None
Event ID: 1024
Discription:
Product: Windows Defender Signatures - Update '{9AD8C4EE-808D-430C-BA88-6075B2053507}'
could not be installed. Error code 1603.

Event Viewer System Error:
Date: 3-17-2006
Time: 8:36:05 AM
Type: Error
Source: Windefend
Catagory: None
Event ID: 2001
Discription:
Windows Defender has encountered an error trying to update signatures.
Error code: 0x80070002
Error description: The system cannot find the file specified.

Windows Installer Log Report:
Property(S): SourcedirProduct = {A5CC2A09-E9D3-49EC-923D-03874BBD4C2C}
MSI (s) (98:04) [07:46:30:125]: Product: Windows Defender Signatures - Update '{9AD8C4EE-808D-430C-BA88-6075B2053507}' could not
be
installed.
Error code 1603. Additional information is available in the log file C:\DOCUME~1\PREFER~1\LOCALS~1\Temp\MSI74389.LOG.
MSI (s) (98:04) [07:46:30:125]: Note: 1: 1729
MSI (s) (98:04) [07:46:30:125]: Product: Windows Defender Signatures -- Configuration failed.
MSI (s) (98:04) [07:46:30:125]: Attempting to delete file C:\WINDOWS\Installer\8974406.msp
MSI (s) (98:04) [07:46:30:125]: Cleaning up uninstalled install packages, if any exist
MSI (s) (98:04) [07:46:30:125]: MainEngineThread is returning 1603
MSI (s) (98:88) [07:46:30:234]: Destroying RemoteAPI object.
MSI (s) (98:08) [07:46:30:234]: Custom Action Manager thread ending.
=== Logging stopped: 3/17/2006 7:46:30 ===
MSI (c) (D0:48) [07:46:30:234]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter
after
decrement: -1
MSI (c) (D0:48) [07:46:30:234]: MainEngineThread is returning 1603
=== Verbose logging stopped: 3/17/2006 7:46:30 ===

Donald Anadell
Click to expand...
Click to expand...
 
Back
Top