Discussion:
Error 0x8007000e running Automatic Updates
(too old to reply)
Rob_
2006-07-05 12:13:02 UTC
Permalink
Raw Message
Hello,

I have a Windows 2003 server that does not report back to WSUS. WSUS does
show the missing updates for the server but still shows that it hasn't
reported in x amount of days.

I have researched this error and can't seem to find an answer. I have
included portions of the windowsupdate.log file.
+++++++++++++++++++++++
#############
AU ## START ## AU: Search for updates
AU #########
AU <<## SUBMITTED ## AU: Search for updates [CallId =
{602E6B3A-41B4-47B5-8610-928484089C0C}]
Agent *************
Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
Agent *********
Setup *********** Setup: Checking whether self-update is required
***********
Setup * Inf file:
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wusetup.inf
Setup Update NOT required for C:\WINDOWS\system32\cdm.dll: target version =
5.8.0.2469, required version = 5.8.0.2469
Setup Update NOT required for C:\WINDOWS\system32\iuengine.dll: target
version = 5.8.0.2469, required version = 5.8.0.2469
Setup Update NOT required for C:\WINDOWS\system32\wuapi.dll: target version
= 5.8.0.2469, required version = 5.8.0.2469
Setup Update NOT required for C:\WINDOWS\system32\wuauclt.exe: target
version = 5.8.0.2469, required version = 5.8.0.2469
Setup Update NOT required for C:\WINDOWS\system32\wuauclt1.exe: target
version = 5.8.0.2469, required version = 5.8.0.2469
Setup Update NOT required for C:\WINDOWS\system32\wuaucpl.cpl: target
version = 5.8.0.2469, required version = 5.8.0.2469
Setup Update NOT required for C:\WINDOWS\system32\wuaueng.dll: target
version = 5.8.0.2469, required version = 5.8.0.2469
Setup Update NOT required for C:\WINDOWS\system32\wuaueng1.dll: target
version = 5.8.0.2469, required version = 5.8.0.2469
Setup Update NOT required for C:\WINDOWS\system32\wucltui.dll: target
version = 5.8.0.2469, required version = 5.8.0.2469
Setup Update NOT required for C:\WINDOWS\system32\wups.dll: target version =
5.8.0.2469, required version = 5.8.0.2469
Setup Update NOT required for C:\WINDOWS\system32\wups2.dll: target version
= 5.8.0.2469, required version = 5.8.0.2469
Setup Update NOT required for C:\WINDOWS\system32\wuweb.dll: target version
= 5.8.0.2469, required version = 5.8.0.2469
Setup * IsUpdateRequired = No
Agent * WARNING: Exit code = 0x8007000E
Agent *********
Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
Agent *************
Agent WARNING: WU client failed Searching for update with error 0x8007000e
AU >>## RESUMED ## AU: Search for updates [CallId =
{602E6B3A-41B4-47B5-8610-928484089C0C}]
AU # WARNING: Search callback failed, result = 0x8007000E
AU #########
AU ## END ## AU: Search for updates [CallId =
{602E6B3A-41B4-47B5-8610-928484089C0C}]
AU #############
AU AU setting next detection timeout to 2006-07-05 12:37:31
Report REPORT EVENT: {9C856293-F476-4269-A118-04D8980529AE} 2006-07-05
07:38:59-0400 1 148 101 {00000000-0000-0000-0000-000000000000} 0 8007000e AutomaticUpdates Failure Software
Synchronization Error: Agent failed detecting with reason: 0x8007000e
Report Uploading 1 events using cached cookie, reporting URL =
http://someserver/ReportingWebService/ReportingWebService.asmx
Report Reporter successfully uploaded 1 events.
Agent *************
Agent ** START ** Agent: Finding updates [CallerId = MBSA]
Agent *********
Agent * WARNING: Exit code = 0x8007000E
Agent *********
Agent ** END ** Agent: Finding updates [CallerId = MBSA]
Agent *************
Agent WARNING: WU client failed Searching for update with error 0x8007000e
Report REPORT EVENT: {9F5A08C1-19D4-4AEA-A9CC-E2927A1EB257} 2006-07-05
07:50:40-0400 1 148 101 {00000000-0000-0000-0000-000000000000} 0 8007000e MBSA Failure Software
Synchronization Error: Agent failed detecting with reason: 0x8007000e
PT Initializing simple targeting cookie, clientId =
6fad0b99-d320-4187-9127-31ea9e047233, target group = , DNS name =
problemserver.ott.cginet
PT Server URL = http://someserver/SimpleAuthWebService/SimpleAuth.asmx
Report Uploading 1 events using cached cookie, reporting URL =
http://someserver/ReportingWebService/ReportingWebService.asmx
Report Reporter successfully uploaded 1 events.
++++++++++++++++++++++++++

When I logon to the server, I no longer get the "Globe"/"Shield" that tells
me that updates are available for download.

I use WSUS running on Windows Server 2003 SP1.

Help please, any comment is a good comment.

Thank you!

... Rob

Any ideas why I'm getting these errors?
Rob_
2006-07-05 17:53:02 UTC
Permalink
Raw Message
Hi again!

I have called MS on this problem and here is what I was recommended.

Looks like the MSI has a known memory leak that brings up the process
svchost memory utilization to a high value. In my case, 202MB. When AU starts
the detection cycle, it calls MSI to do so. A work arround is to bring down
the detection to 12-24 hours and of course, reboot the server.

MS has a hot fix for this problem... but you need to call.
Post by Rob_
Hello,
I have a Windows 2003 server that does not report back to WSUS. WSUS does
show the missing updates for the server but still shows that it hasn't
reported in x amount of days.
I have researched this error and can't seem to find an answer. I have
included portions of the windowsupdate.log file.
+++++++++++++++++++++++
#############
AU ## START ## AU: Search for updates
AU #########
AU <<## SUBMITTED ## AU: Search for updates [CallId =
{602E6B3A-41B4-47B5-8610-928484089C0C}]
Agent *************
Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
Agent *********
Setup *********** Setup: Checking whether self-update is required
***********
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wusetup.inf
Setup Update NOT required for C:\WINDOWS\system32\cdm.dll: target version =
5.8.0.2469, required version = 5.8.0.2469
Setup Update NOT required for C:\WINDOWS\system32\iuengine.dll: target
version = 5.8.0.2469, required version = 5.8.0.2469
Setup Update NOT required for C:\WINDOWS\system32\wuapi.dll: target version
= 5.8.0.2469, required version = 5.8.0.2469
Setup Update NOT required for C:\WINDOWS\system32\wuauclt.exe: target
version = 5.8.0.2469, required version = 5.8.0.2469
Setup Update NOT required for C:\WINDOWS\system32\wuauclt1.exe: target
version = 5.8.0.2469, required version = 5.8.0.2469
Setup Update NOT required for C:\WINDOWS\system32\wuaucpl.cpl: target
version = 5.8.0.2469, required version = 5.8.0.2469
Setup Update NOT required for C:\WINDOWS\system32\wuaueng.dll: target
version = 5.8.0.2469, required version = 5.8.0.2469
Setup Update NOT required for C:\WINDOWS\system32\wuaueng1.dll: target
version = 5.8.0.2469, required version = 5.8.0.2469
Setup Update NOT required for C:\WINDOWS\system32\wucltui.dll: target
version = 5.8.0.2469, required version = 5.8.0.2469
Setup Update NOT required for C:\WINDOWS\system32\wups.dll: target version =
5.8.0.2469, required version = 5.8.0.2469
Setup Update NOT required for C:\WINDOWS\system32\wups2.dll: target version
= 5.8.0.2469, required version = 5.8.0.2469
Setup Update NOT required for C:\WINDOWS\system32\wuweb.dll: target version
= 5.8.0.2469, required version = 5.8.0.2469
Setup * IsUpdateRequired = No
Agent * WARNING: Exit code = 0x8007000E
Agent *********
Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
Agent *************
Agent WARNING: WU client failed Searching for update with error 0x8007000e
AU >>## RESUMED ## AU: Search for updates [CallId =
{602E6B3A-41B4-47B5-8610-928484089C0C}]
AU # WARNING: Search callback failed, result = 0x8007000E
AU #########
AU ## END ## AU: Search for updates [CallId =
{602E6B3A-41B4-47B5-8610-928484089C0C}]
AU #############
AU AU setting next detection timeout to 2006-07-05 12:37:31
Report REPORT EVENT: {9C856293-F476-4269-A118-04D8980529AE} 2006-07-05
07:38:59-0400 1 148 101 {00000000-0000-0000-0000-000000000000} 0 8007000e AutomaticUpdates Failure Software
Synchronization Error: Agent failed detecting with reason: 0x8007000e
Report Uploading 1 events using cached cookie, reporting URL =
http://someserver/ReportingWebService/ReportingWebService.asmx
Report Reporter successfully uploaded 1 events.
Agent *************
Agent ** START ** Agent: Finding updates [CallerId = MBSA]
Agent *********
Agent * WARNING: Exit code = 0x8007000E
Agent *********
Agent ** END ** Agent: Finding updates [CallerId = MBSA]
Agent *************
Agent WARNING: WU client failed Searching for update with error 0x8007000e
Report REPORT EVENT: {9F5A08C1-19D4-4AEA-A9CC-E2927A1EB257} 2006-07-05
07:50:40-0400 1 148 101 {00000000-0000-0000-0000-000000000000} 0 8007000e MBSA Failure Software
Synchronization Error: Agent failed detecting with reason: 0x8007000e
PT Initializing simple targeting cookie, clientId =
6fad0b99-d320-4187-9127-31ea9e047233, target group = , DNS name =
problemserver.ott.cginet
PT Server URL = http://someserver/SimpleAuthWebService/SimpleAuth.asmx
Report Uploading 1 events using cached cookie, reporting URL =
http://someserver/ReportingWebService/ReportingWebService.asmx
Report Reporter successfully uploaded 1 events.
++++++++++++++++++++++++++
When I logon to the server, I no longer get the "Globe"/"Shield" that tells
me that updates are available for download.
I use WSUS running on Windows Server 2003 SP1.
Help please, any comment is a good comment.
Thank you!
... Rob
Any ideas why I'm getting these errors?
Chupacabra
2006-07-25 21:27:24 UTC
Permalink
Raw Message
Post by Rob_
Hi again!
I have called MS on this problem and here is what I was recommended.
Looks like the MSI has a known memory leak that brings up the process
svchost memory utilization to a high value. In my case, 202MB. When AU starts
the detection cycle, it calls MSI to do so. A work arround is to bring down
the detection to 12-24 hours and of course, reboot the server.
MS has a hot fix for this problem... but you need to call.
Rob,

We seem to be having the same issue on a Win2K server. When the
auto-updates tries to run, one of the svchost processes shoots way up in
memory utilization, and we get the same 0x8007000e error.

Do you have any other info on this error, or what the hotfix involves? I'd
like to have as much info as possible before calling MS.

Thanks!
Jeff S
2007-04-03 15:52:54 UTC
Permalink
Raw Message
I worked with Microsoft tech support to fix the error: Agent failed
detecting reason: 0x80070000e

Microsoft had me search microsoft.com for KB898708, download and
install this hotfix on my WSUS server including a reboot. It didn't fix
the problem, however. My WSUS server is Win2003 Standard SP1, and I have
WSUS Build 2.0.0.2620.

Microsoft then had me search microsoft.com for KB927891 and install
this hotfix on my WSUS clients, including a reboot. This fixed the
problem. My clients are WinXP SP2.

So, you may be able to get by just installing the KB927891; I'd try
that first.
--
Jeff S
------------------------------------------------------------------------
Jeff S's Profile: http://forums.techarena.in/member.php?userid=24200
View this thread: http://forums.techarena.in/showthread.php?t=545582

http://forums.techarena.in
Lawrence Garvin (MVP)
2007-04-04 22:53:10 UTC
Permalink
Raw Message
Post by Jeff S
I worked with Microsoft tech support to fix the error: Agent failed
detecting reason: 0x80070000e
Microsoft had me search microsoft.com for KB898708, download and
install this hotfix on my WSUS server including a reboot. It didn't fix
the problem, however.
No doubt.. since KB898708 isn't designed to fix the 0x8007000e errors....
:-/

The 0x8007000e error is a special error, related to an XML fault in the WSUS
RTM release that corrupts the database. This issue was fixed in the WSUS SP1
release, but applying SP1 doesn't fix an already existent XML corruption
issue.

In general, encountering an 0x8007000e error on WSUS almost always is only
resolvable by reinstalling WSUS with a new database.
Post by Jeff S
My WSUS server is Win2003 Standard SP1, and I have
WSUS Build 2.0.0.2620.
It's likely the corruption has existed for some time, or that you only
recently upgraded to WSUS SP1, and the issue predates your installation of
the SP.
Post by Jeff S
Microsoft then had me search microsoft.com for KB927891 and install
this hotfix on my WSUS clients, including a reboot. This fixed the
problem.
Interesting, considering that this hotfix is also not associated with the
0x8007000e error, but is designed specifically for those clients exhibiting
the 100% CPU utilization on svchost.exe issue.
--
Lawrence Garvin, M.S., MCTS, MCP
Independent WSUS Evangelist
MVP-Software Distribution (2005-2007)
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E

Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx

And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
....
Jeff S
2007-04-05 13:14:45 UTC
Permalink
Raw Message
Lawrence,

In fact, I did rebuild my Win2003 server and reinstall WSUS from
scratch, including a new database, just two months ago when a bunch of
my PCs first started showing this error. However, the problem came
back.

Microsoft's explaination to your "considering that this hotfix is also
not associated with the 0x8007000e error" was that this hotfix fixes a
bunch of different problems with WSUS clients, not just 0x8007000e.
--
Jeff S
------------------------------------------------------------------------
Jeff S's Profile: http://forums.techarena.in/member.php?userid=24200
View this thread: http://forums.techarena.in/showthread.php?t=545582

http://forums.techarena.in
b***@gmail.com
2015-08-26 09:03:48 UTC
Permalink
Raw Message
Hello, i've got the same error message with a WSUS 3.0 sp2 located on a Windows 2008 R2 server on a windows 2008 R2 client.
May i put my windowsupdate log file here to investigate?

Many thanks for any you could help tou could provide...

Théo

Loading...