Discussion:
Agent failed detecting reason: 0x80070000e
(too old to reply)
Les Connor [SBS Community Member - SBS MVP]
2006-07-28 21:24:13 UTC
Permalink
Hi Folks,

I can't seem to find any references to that 'reason'. I have 5 of 17
workstations, in one domain, in this condition. I've tried the customary
wuauclt /resetauthorization /detectnow without any joy, but haven't yet run
the client tool.

The workstations are present in the console, and show current 'last
contacted', but the console says they're not reporting back. They *did* all
work. Something changed.

Here's the latest update/report cycle from one of the workstations, should
it help those in the know.

2006-07-28 15:43:41 1064 7dc AU #############
2006-07-28 15:43:41 1064 7dc AU ## START ## AU: Search for updates
2006-07-28 15:43:41 1064 7dc AU #########
2006-07-28 15:43:41 1064 7dc AU <<## SUBMITTED ## AU: Search for updates
[CallId = {74D769D7-18E0-4D66-A75E-CF91585A3DD1}]
2006-07-28 15:43:41 1064 b80 Agent *************
2006-07-28 15:43:41 1064 b80 Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2006-07-28 15:43:41 1064 b80 Agent *********
2006-07-28 15:43:41 1064 b80 Setup *********** Setup: Checking whether
self-update is required ***********
2006-07-28 15:43:41 1064 b80 Setup * Inf file:
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wusetup.inf
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\cdm.dll: target version = 5.8.0.2607, required version =
5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\iuengine.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wuapi.dll: target version = 5.8.0.2607, required version
= 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wuauclt.exe: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wuauclt1.exe: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wuaucpl.cpl: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wuaueng.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wuaueng1.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wucltui.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wups.dll: target version = 5.8.0.2607, required version
= 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wups2.dll: target version = 5.8.0.2607, required version
= 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wuweb.dll: target version = 5.8.0.2607, required version
= 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup * IsUpdateRequired = No
2006-07-28 15:43:45 1064 b80 Agent * WARNING: Exit code = 0x8007000E
2006-07-28 15:43:45 1064 b80 Agent *********
2006-07-28 15:43:45 1064 b80 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2006-07-28 15:43:45 1064 b80 Agent *************
2006-07-28 15:43:45 1064 b80 Agent WARNING: WU client failed Searching for
update with error 0x8007000e
2006-07-28 15:43:45 1064 b80 AU >>## RESUMED ## AU: Search for updates
[CallId = {74D769D7-18E0-4D66-A75E-CF91585A3DD1}]
2006-07-28 15:43:45 1064 b80 AU # WARNING: Search callback failed, result
= 0x8007000E
2006-07-28 15:43:45 1064 b80 AU #########
2006-07-28 15:43:45 1064 b80 AU ## END ## AU: Search for updates [CallId
= {74D769D7-18E0-4D66-A75E-CF91585A3DD1}]
2006-07-28 15:43:45 1064 b80 AU #############
2006-07-28 15:43:45 1064 b80 AU AU setting next detection timeout to
2006-07-28 21:41:34
2006-07-28 15:43:50 1064 b80 Report REPORT EVENT:
{9D5A236D-7E50-46F9-AE55-911AF4570BCC} 2006-07-28 15:43:45-0500 1 148 101
{00000000-0000-0000-0000-000000000000} 0 8007000e AutomaticUpdates Failure
Software Synchronization Error: Agent failed detecting with reason:
0x8007000e
2006-07-28 15:47:10 1064 43c PT Initializing simple targeting cookie,
clientId = 9d918a8f-5a53-4e31-a943-22e0b156fd1b, target group = , DNS name =
debbieoffice.obo.brandon
2006-07-28 15:47:10 1064 43c PT Server URL =
http://SBS:8530/SimpleAuthWebService/SimpleAuth.asmx
2006-07-28 15:47:22 1064 43c Report Uploading 1 events using cached cookie,
reporting URL = http://SBS:8530/ReportingWebService/ReportingWebService.asmx
2006-07-28 15:47:22 1064 43c Report Reporter successfully uploaded 1 events.
--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me and I'll
understand." - Confucius
Les Connor [SBS Community Member - SBS MVP]
2006-07-28 22:25:49 UTC
Permalink
errrr... make that 0x8007000e.

I'll never find reference to the other one ;-).
--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me and I'll
understand." - Confucius
Post by Les Connor [SBS Community Member - SBS MVP]
Hi Folks,
I can't seem to find any references to that 'reason'. I have 5 of 17
workstations, in one domain, in this condition. I've tried the customary
wuauclt /resetauthorization /detectnow without any joy, but haven't yet
run the client tool.
The workstations are present in the console, and show current 'last
contacted', but the console says they're not reporting back. They *did*
all work. Something changed.
Here's the latest update/report cycle from one of the workstations, should
it help those in the know.
2006-07-28 15:43:41 1064 7dc AU #############
2006-07-28 15:43:41 1064 7dc AU ## START ## AU: Search for updates
2006-07-28 15:43:41 1064 7dc AU #########
2006-07-28 15:43:41 1064 7dc AU <<## SUBMITTED ## AU: Search for updates
[CallId = {74D769D7-18E0-4D66-A75E-CF91585A3DD1}]
2006-07-28 15:43:41 1064 b80 Agent *************
2006-07-28 15:43:41 1064 b80 Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2006-07-28 15:43:41 1064 b80 Agent *********
2006-07-28 15:43:41 1064 b80 Setup *********** Setup: Checking whether
self-update is required ***********
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wusetup.inf
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\cdm.dll: target version = 5.8.0.2607, required version
= 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\iuengine.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wuapi.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wuauclt.exe: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wuauclt1.exe: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wuaucpl.cpl: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wuaueng.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wuaueng1.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wucltui.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wups.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wups2.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wuweb.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup * IsUpdateRequired = No
2006-07-28 15:43:45 1064 b80 Agent * WARNING: Exit code = 0x8007000E
2006-07-28 15:43:45 1064 b80 Agent *********
2006-07-28 15:43:45 1064 b80 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2006-07-28 15:43:45 1064 b80 Agent *************
2006-07-28 15:43:45 1064 b80 Agent WARNING: WU client failed Searching for
update with error 0x8007000e
2006-07-28 15:43:45 1064 b80 AU >>## RESUMED ## AU: Search for updates
[CallId = {74D769D7-18E0-4D66-A75E-CF91585A3DD1}]
2006-07-28 15:43:45 1064 b80 AU # WARNING: Search callback failed,
result = 0x8007000E
2006-07-28 15:43:45 1064 b80 AU #########
2006-07-28 15:43:45 1064 b80 AU ## END ## AU: Search for updates
[CallId = {74D769D7-18E0-4D66-A75E-CF91585A3DD1}]
2006-07-28 15:43:45 1064 b80 AU #############
2006-07-28 15:43:45 1064 b80 AU AU setting next detection timeout to
2006-07-28 21:41:34
{9D5A236D-7E50-46F9-AE55-911AF4570BCC} 2006-07-28 15:43:45-0500 1 148 101
{00000000-0000-0000-0000-000000000000} 0 8007000e AutomaticUpdates Failure
0x8007000e
2006-07-28 15:47:10 1064 43c PT Initializing simple targeting cookie,
clientId = 9d918a8f-5a53-4e31-a943-22e0b156fd1b, target group = , DNS name
= debbieoffice.obo.brandon
2006-07-28 15:47:10 1064 43c PT Server URL =
http://SBS:8530/SimpleAuthWebService/SimpleAuth.asmx
2006-07-28 15:47:22 1064 43c Report Uploading 1 events using cached
cookie, reporting URL =
http://SBS:8530/ReportingWebService/ReportingWebService.asmx
2006-07-28 15:47:22 1064 43c Report Reporter successfully uploaded 1 events.
--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me and I'll
understand." - Confucius
Gus
2006-07-28 23:52:21 UTC
Permalink
Reinstall MSXML3 from http://www.microsoft.com/downloads and see if
that corrects the issue on the problem clients.
Post by Les Connor [SBS Community Member - SBS MVP]
errrr... make that 0x8007000e.
I'll never find reference to the other one ;-).
--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me and I'll
understand." - Confucius
Post by Les Connor [SBS Community Member - SBS MVP]
Hi Folks,
I can't seem to find any references to that 'reason'. I have 5 of 17
workstations, in one domain, in this condition. I've tried the customary
wuauclt /resetauthorization /detectnow without any joy, but haven't yet
run the client tool.
The workstations are present in the console, and show current 'last
contacted', but the console says they're not reporting back. They *did*
all work. Something changed.
Here's the latest update/report cycle from one of the workstations, should
it help those in the know.
2006-07-28 15:43:41 1064 7dc AU #############
2006-07-28 15:43:41 1064 7dc AU ## START ## AU: Search for updates
2006-07-28 15:43:41 1064 7dc AU #########
2006-07-28 15:43:41 1064 7dc AU <<## SUBMITTED ## AU: Search for updates
[CallId = {74D769D7-18E0-4D66-A75E-CF91585A3DD1}]
2006-07-28 15:43:41 1064 b80 Agent *************
2006-07-28 15:43:41 1064 b80 Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2006-07-28 15:43:41 1064 b80 Agent *********
2006-07-28 15:43:41 1064 b80 Setup *********** Setup: Checking whether
self-update is required ***********
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wusetup.inf
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\cdm.dll: target version = 5.8.0.2607, required version
= 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\iuengine.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wuapi.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wuauclt.exe: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wuauclt1.exe: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wuaucpl.cpl: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wuaueng.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wuaueng1.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wucltui.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wups.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wups2.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wuweb.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup * IsUpdateRequired = No
2006-07-28 15:43:45 1064 b80 Agent * WARNING: Exit code = 0x8007000E
2006-07-28 15:43:45 1064 b80 Agent *********
2006-07-28 15:43:45 1064 b80 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2006-07-28 15:43:45 1064 b80 Agent *************
2006-07-28 15:43:45 1064 b80 Agent WARNING: WU client failed Searching for
update with error 0x8007000e
2006-07-28 15:43:45 1064 b80 AU >>## RESUMED ## AU: Search for updates
[CallId = {74D769D7-18E0-4D66-A75E-CF91585A3DD1}]
2006-07-28 15:43:45 1064 b80 AU # WARNING: Search callback failed,
result = 0x8007000E
2006-07-28 15:43:45 1064 b80 AU #########
2006-07-28 15:43:45 1064 b80 AU ## END ## AU: Search for updates
[CallId = {74D769D7-18E0-4D66-A75E-CF91585A3DD1}]
2006-07-28 15:43:45 1064 b80 AU #############
2006-07-28 15:43:45 1064 b80 AU AU setting next detection timeout to
2006-07-28 21:41:34
{9D5A236D-7E50-46F9-AE55-911AF4570BCC} 2006-07-28 15:43:45-0500 1 148 101
{00000000-0000-0000-0000-000000000000} 0 8007000e AutomaticUpdates Failure
0x8007000e
2006-07-28 15:47:10 1064 43c PT Initializing simple targeting cookie,
clientId = 9d918a8f-5a53-4e31-a943-22e0b156fd1b, target group = , DNS name
= debbieoffice.obo.brandon
2006-07-28 15:47:10 1064 43c PT Server URL =
http://SBS:8530/SimpleAuthWebService/SimpleAuth.asmx
2006-07-28 15:47:22 1064 43c Report Uploading 1 events using cached
cookie, reporting URL =
http://SBS:8530/ReportingWebService/ReportingWebService.asmx
2006-07-28 15:47:22 1064 43c Report Reporter successfully uploaded 1 events.
--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me and I'll
understand." - Confucius
Lawrence Garvin (MVP)
2006-07-29 17:18:19 UTC
Permalink
Post by Les Connor [SBS Community Member - SBS MVP]
I can't seem to find any references to that 'reason'.
Les Connor [SBS Community Member - SBS MVP]
I like the easy ones.... :-)

0x8007000E -2147024882 E OUTOFMEMORY


Obtained from the WUA error message site that I use
(when my partial list doesn't have the code documented)
http://perso.orange.fr/doc.jm/WU5-ERR.htm

as referenced from the WSUS Wiki website at
http://www.wsuswiki.com/TroubleshootingClientSetup

The French site has all the codes listed from the legacy AU client.
My site only lists those codes that we've routinely encountered while using
the WSUS WUA, although there are now a couple missing that need to be added.
This is, perhaps, one of those I should add to my list!
--
Lawrence Garvin, M.S., MVP-Software Distribution
Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
And, everything else is at
http://wsusinfo.onsitechsolutions.com
....
Post by Les Connor [SBS Community Member - SBS MVP]
Hi Folks,
I can't seem to find any references to that 'reason'. I have 5 of 17
workstations, in one domain, in this condition. I've tried the customary
wuauclt /resetauthorization /detectnow without any joy, but haven't yet
run the client tool.
The workstations are present in the console, and show current 'last
contacted', but the console says they're not reporting back. They *did*
all work. Something changed.
Here's the latest update/report cycle from one of the workstations, should
it help those in the know.
2006-07-28 15:43:41 1064 7dc AU #############
2006-07-28 15:43:41 1064 7dc AU ## START ## AU: Search for updates
2006-07-28 15:43:41 1064 7dc AU #########
2006-07-28 15:43:41 1064 7dc AU <<## SUBMITTED ## AU: Search for updates
[CallId = {74D769D7-18E0-4D66-A75E-CF91585A3DD1}]
2006-07-28 15:43:41 1064 b80 Agent *************
2006-07-28 15:43:41 1064 b80 Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2006-07-28 15:43:41 1064 b80 Agent *********
2006-07-28 15:43:41 1064 b80 Setup *********** Setup: Checking whether
self-update is required ***********
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wusetup.inf
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\cdm.dll: target version = 5.8.0.2607, required version
= 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\iuengine.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wuapi.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wuauclt.exe: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wuauclt1.exe: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wuaucpl.cpl: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wuaueng.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wuaueng1.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wucltui.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wups.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wups2.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wuweb.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup * IsUpdateRequired = No
2006-07-28 15:43:45 1064 b80 Agent * WARNING: Exit code = 0x8007000E
2006-07-28 15:43:45 1064 b80 Agent *********
2006-07-28 15:43:45 1064 b80 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2006-07-28 15:43:45 1064 b80 Agent *************
2006-07-28 15:43:45 1064 b80 Agent WARNING: WU client failed Searching for
update with error 0x8007000e
2006-07-28 15:43:45 1064 b80 AU >>## RESUMED ## AU: Search for updates
[CallId = {74D769D7-18E0-4D66-A75E-CF91585A3DD1}]
2006-07-28 15:43:45 1064 b80 AU # WARNING: Search callback failed,
result = 0x8007000E
2006-07-28 15:43:45 1064 b80 AU #########
2006-07-28 15:43:45 1064 b80 AU ## END ## AU: Search for updates
[CallId = {74D769D7-18E0-4D66-A75E-CF91585A3DD1}]
2006-07-28 15:43:45 1064 b80 AU #############
2006-07-28 15:43:45 1064 b80 AU AU setting next detection timeout to
2006-07-28 21:41:34
{9D5A236D-7E50-46F9-AE55-911AF4570BCC} 2006-07-28 15:43:45-0500 1 148 101
{00000000-0000-0000-0000-000000000000} 0 8007000e AutomaticUpdates Failure
0x8007000e
2006-07-28 15:47:10 1064 43c PT Initializing simple targeting cookie,
clientId = 9d918a8f-5a53-4e31-a943-22e0b156fd1b, target group = , DNS name
= debbieoffice.obo.brandon
2006-07-28 15:47:10 1064 43c PT Server URL =
http://SBS:8530/SimpleAuthWebService/SimpleAuth.asmx
2006-07-28 15:47:22 1064 43c Report Uploading 1 events using cached
cookie, reporting URL =
http://SBS:8530/ReportingWebService/ReportingWebService.asmx
2006-07-28 15:47:22 1064 43c Report Reporter successfully uploaded 1 events.
--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me and I'll
understand." - Confucius
Les Connor [SBS Community Member - SBS MVP]
2006-07-31 01:31:21 UTC
Permalink
Yeah, I checked your site first off, and didn't see that error code
referenced; got as far as xxxd, but no e ;-).

I used err.exe and got the OUTOFMEMORY from that, but it didn't make sense
to me. I'm thinking, what could possibly be out of memory?

I'll check the links you provided, thanks Lawrence.
--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me and I'll
understand." - Confucius
Post by Lawrence Garvin (MVP)
Post by Les Connor [SBS Community Member - SBS MVP]
I can't seem to find any references to that 'reason'.
Les Connor [SBS Community Member - SBS MVP]
I like the easy ones.... :-)
0x8007000E -2147024882 E OUTOFMEMORY
Obtained from the WUA error message site that I use
(when my partial list doesn't have the code documented)
http://perso.orange.fr/doc.jm/WU5-ERR.htm
as referenced from the WSUS Wiki website at
http://www.wsuswiki.com/TroubleshootingClientSetup
The French site has all the codes listed from the legacy AU client.
My site only lists those codes that we've routinely encountered while
using the WSUS WUA, although there are now a couple missing that need to
be added.
This is, perhaps, one of those I should add to my list!
--
Lawrence Garvin, M.S., MVP-Software Distribution
Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
And, everything else is at
http://wsusinfo.onsitechsolutions.com
....
Post by Les Connor [SBS Community Member - SBS MVP]
Hi Folks,
I can't seem to find any references to that 'reason'. I have 5 of 17
workstations, in one domain, in this condition. I've tried the customary
wuauclt /resetauthorization /detectnow without any joy, but haven't yet
run the client tool.
The workstations are present in the console, and show current 'last
contacted', but the console says they're not reporting back. They *did*
all work. Something changed.
Here's the latest update/report cycle from one of the workstations,
should it help those in the know.
2006-07-28 15:43:41 1064 7dc AU #############
2006-07-28 15:43:41 1064 7dc AU ## START ## AU: Search for updates
2006-07-28 15:43:41 1064 7dc AU #########
2006-07-28 15:43:41 1064 7dc AU <<## SUBMITTED ## AU: Search for updates
[CallId = {74D769D7-18E0-4D66-A75E-CF91585A3DD1}]
2006-07-28 15:43:41 1064 b80 Agent *************
2006-07-28 15:43:41 1064 b80 Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2006-07-28 15:43:41 1064 b80 Agent *********
2006-07-28 15:43:41 1064 b80 Setup *********** Setup: Checking whether
self-update is required ***********
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wusetup.inf
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\cdm.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\iuengine.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wuapi.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wuauclt.exe: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wuauclt1.exe: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wuaucpl.cpl: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wuaueng.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wuaueng1.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wucltui.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wups.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wups2.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup Update NOT required for
C:\WINDOWS\system32\wuweb.dll: target version = 5.8.0.2607, required
version = 5.8.0.2607
2006-07-28 15:43:41 1064 b80 Setup * IsUpdateRequired = No
2006-07-28 15:43:45 1064 b80 Agent * WARNING: Exit code = 0x8007000E
2006-07-28 15:43:45 1064 b80 Agent *********
2006-07-28 15:43:45 1064 b80 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2006-07-28 15:43:45 1064 b80 Agent *************
2006-07-28 15:43:45 1064 b80 Agent WARNING: WU client failed Searching
for update with error 0x8007000e
2006-07-28 15:43:45 1064 b80 AU >>## RESUMED ## AU: Search for updates
[CallId = {74D769D7-18E0-4D66-A75E-CF91585A3DD1}]
2006-07-28 15:43:45 1064 b80 AU # WARNING: Search callback failed,
result = 0x8007000E
2006-07-28 15:43:45 1064 b80 AU #########
2006-07-28 15:43:45 1064 b80 AU ## END ## AU: Search for updates
[CallId = {74D769D7-18E0-4D66-A75E-CF91585A3DD1}]
2006-07-28 15:43:45 1064 b80 AU #############
2006-07-28 15:43:45 1064 b80 AU AU setting next detection timeout to
2006-07-28 21:41:34
{9D5A236D-7E50-46F9-AE55-911AF4570BCC} 2006-07-28 15:43:45-0500 1 148 101
{00000000-0000-0000-0000-000000000000} 0 8007000e AutomaticUpdates
Failure Software Synchronization Error: Agent failed detecting with
reason: 0x8007000e
2006-07-28 15:47:10 1064 43c PT Initializing simple targeting cookie,
clientId = 9d918a8f-5a53-4e31-a943-22e0b156fd1b, target group = , DNS
name = debbieoffice.obo.brandon
2006-07-28 15:47:10 1064 43c PT Server URL =
http://SBS:8530/SimpleAuthWebService/SimpleAuth.asmx
2006-07-28 15:47:22 1064 43c Report Uploading 1 events using cached
cookie, reporting URL =
http://SBS:8530/ReportingWebService/ReportingWebService.asmx
2006-07-28 15:47:22 1064 43c Report Reporter successfully uploaded 1 events.
--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me and I'll
understand." - Confucius
Chupacabra
2006-07-31 13:31:02 UTC
Permalink
Post by Lawrence Garvin (MVP)
I like the easy ones.... :-)
0x8007000E -2147024882 E OUTOFMEMORY
Yeah, it's easy enough to track down the 8007000E meaning "out of memory".
:-)

Where it gets difficult is finding out WHY it thinks it's out of memory?
The server that we're having issues with has plenty of RAM, yet the AU
client always throws a ton of 8007000E errors, even after a fresh reboot.
Chupacabra
2006-07-31 13:32:17 UTC
Permalink
Also, in regard to the 8007000e errors, we have run the Client Diagnostics
on the server that's throwing 8007000e, and everything comes up fine...
Les Connor [SBS Community Member - SBS MVP]
2006-07-31 19:35:17 UTC
Permalink
Do you think the error is coming from the server? I thought the other way,
it's a client error. In any case, it seems like a red herring to me ;-).
--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me and I'll
understand." - Confucius
Post by Chupacabra
Also, in regard to the 8007000e errors, we have run the Client Diagnostics
on the server that's throwing 8007000e, and everything comes up fine...
Chupacabra
2006-07-31 20:12:37 UTC
Permalink
Post by Les Connor [SBS Community Member - SBS MVP]
Do you think the error is coming from the server? I thought the other way,
it's a client error. In any case, it seems like a red herring to me ;-).
Sorry for the confusion. It's a server that is a client of WSUS that's
throwing that error. I do believe it is a client-side issue, even if the
client is also a server (but not the WSUS server!)

:)
Les Connor [SBS Community Member - SBS MVP]
2006-07-31 20:42:47 UTC
Permalink
:-). OK, that clears that up.

I got a response from first level CSS that the most common cause of this
behaviour is certain XML compnents are unexpectedly un-registered or
missing. I'm not sure I buy that, as there's certainly some existing
functionality; in fact the wsus clients are all up to date. But the error
persists, and that messes up the status reports in my customers eyes. ;-/.

<snip>
Please visit the following link to download and install the components by
following the onscreen instructions.

http://download.microsoft.com/download/a/5/e/a5e03798-2454-4d4b-89a3-4a4

7579891d8/msxml3.msi

To ensure that the MSXML files are successfully and accurately registered in
the system, please continue with the steps below.

1. Click on Start, Run and type "REGSVR32 C:\WINDOWS\SYSTEM32\MSXML.DLL"
(w/o the quotes). You should see a popup message that this process
succeeded.

2. Click on Start, Run and type "REGSVR32 C:\WINDOWS\SYSTEM32\MSXML2.DLL"
(w/o the quotes). You should see a popup message that this process
succeeded.

3. Click on Start, Run and type "REGSVR32 C:\WINDOWS\SYSTEM32\MSXML3.DLL"
(w/o the quotes). You should see a popup message that this process
succeeded.

If, however, the problem persists, in order to perform further research,
please gather the following information for me.....

<endsnip>


But I guess I should give it a shot.
--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me and I'll
understand." - Confucius
Post by Chupacabra
Post by Les Connor [SBS Community Member - SBS MVP]
Do you think the error is coming from the server? I thought the other
way, it's a client error. In any case, it seems like a red herring to me
;-).
Sorry for the confusion. It's a server that is a client of WSUS that's
throwing that error. I do believe it is a client-side issue, even if the
client is also a server (but not the WSUS server!)
:)
Lawrence Garvin (MVP)
2006-07-31 21:37:07 UTC
Permalink
I just responded to another thread with a similar 'out of memory' error --
but a different error code .. (It's a Terminal Server).

But the idea may apply to other systems:

(1) Ensure the client system has a properly configured paging file and that
disk space exists to permit the paging file to grow, and

(2) In the case of servers... particularly Standard Edition servers, make
sure that the server really isn't 'out of memory' -- either physical memory
(and being further constrained by lack of paging space), or addressible
memory (because either the OS has allocated all 2GB of it's addressible
space), or applications have sucked up all 2GB of their addressible space.
(This could also occur on an EE server with the /3GB switch if the OS
has allocated all 1GB of addressible memory in that scenario.)
--
Lawrence Garvin, M.S., MVP-Software Distribution
Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
And, everything else is at
http://wsusinfo.onsitechsolutions.com
....
Les Connor [SBS Community Member - SBS MVP]
2006-08-01 20:39:50 UTC
Permalink
I got the error to change on one WSUS client ;-). Various things done,
starting with the re-install of msxml and registering the dll's. Not
surprisingly, that had no effect.

In the end, I stopped Automatic Updates and deleted everything in the
SoftwareDistribution folder, and restarted AU. I get a better result in the
log file, and the server reporting this error for the client 'Last Detection
Result'.

0x80244010 -2145107952 SUS E PT EXCEEDED MAX SERVER TRIPS The maximum
allowed number of round trips to the server was exceeded


That might be as a result of my running wuauclt too many times, or the
client diags (which reports no issues, BTW), while there's actually some
update cycle running. I'll leave it be for a while and see if the error
clears.
--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me and I'll
understand." - Confucius
Post by Lawrence Garvin (MVP)
I just responded to another thread with a similar 'out of memory' error --
but a different error code .. (It's a Terminal Server).
(1) Ensure the client system has a properly configured paging file and
that disk space exists to permit the paging file to grow, and
(2) In the case of servers... particularly Standard Edition servers, make
sure that the server really isn't 'out of memory' -- either physical
memory (and being further constrained by lack of paging space), or
addressible memory (because either the OS has allocated all 2GB of it's
addressible space), or applications have sucked up all 2GB of their
addressible space.
(This could also occur on an EE server with the /3GB switch if the OS
has allocated all 1GB of addressible memory in that scenario.)
--
Lawrence Garvin, M.S., MVP-Software Distribution
Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
And, everything else is at
http://wsusinfo.onsitechsolutions.com
....
Chupacabra
2006-08-01 21:39:10 UTC
Permalink
Post by Les Connor [SBS Community Member - SBS MVP]
I got the error to change on one WSUS client ;-). Various things done,
starting with the re-install of msxml and registering the dll's. Not
surprisingly, that had no effect.
In the end, I stopped Automatic Updates and deleted everything in the
SoftwareDistribution folder, and restarted AU. I get a better result in
the log file, and the server reporting this error for the client 'Last
Detection Result'.
0x80244010 -2145107952 SUS E PT EXCEEDED MAX SERVER TRIPS The maximum
allowed number of round trips to the server was exceeded
That might be as a result of my running wuauclt too many times, or the
client diags (which reports no issues, BTW), while there's actually some
update cycle running. I'll leave it be for a while and see if the error
clears.
I've done that too - stopping automatic updates and blowing away the
SoftwareDistribution folder. No joy.

Also tried the

wuauclt /resetauthorization /detectnow

command with no luck. We reregistered the DLLs and did the msxml thing, but
we're still getting the 8007000e error.
Les Connor [SBS Community Member - SBS MVP]
2006-08-01 22:01:16 UTC
Permalink
Seems I'm one step ahead of you, then ;-).

We could compare client side logfiles, mine looks pretty good - no 0x8
errors at all.

The only other thing I did on this one workstation was repair time
synchronization - it was off by 3 minutes and caused some kerberos errors
which were followed by immediate successes. I don't know if that was
related, or not. I still have 4 workstations with the original 0e error, I
haven't done anything with them - there are no time sync issues with those -
and I have 10 other WSUS clients on the same network with no errors. So it's
a client side thing, I'm quite sure.
--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me and I'll
understand." - Confucius
Post by Chupacabra
Post by Les Connor [SBS Community Member - SBS MVP]
I got the error to change on one WSUS client ;-). Various things done,
starting with the re-install of msxml and registering the dll's. Not
surprisingly, that had no effect.
In the end, I stopped Automatic Updates and deleted everything in the
SoftwareDistribution folder, and restarted AU. I get a better result in
the log file, and the server reporting this error for the client 'Last
Detection Result'.
0x80244010 -2145107952 SUS E PT EXCEEDED MAX SERVER TRIPS The
maximum allowed number of round trips to the server was exceeded
That might be as a result of my running wuauclt too many times, or the
client diags (which reports no issues, BTW), while there's actually some
update cycle running. I'll leave it be for a while and see if the error
clears.
I've done that too - stopping automatic updates and blowing away the
SoftwareDistribution folder. No joy.
Also tried the
wuauclt /resetauthorization /detectnow
command with no luck. We reregistered the DLLs and did the msxml thing,
but we're still getting the 8007000e error.
Les Connor [SBS Community Member - SBS MVP]
2006-08-02 13:19:55 UTC
Permalink
The one workstation I touched is no longer in the error list. I'll try
another one today.
--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me and I'll
understand." - Confucius
Post by Les Connor [SBS Community Member - SBS MVP]
Seems I'm one step ahead of you, then ;-).
We could compare client side logfiles, mine looks pretty good - no 0x8
errors at all.
The only other thing I did on this one workstation was repair time
synchronization - it was off by 3 minutes and caused some kerberos errors
which were followed by immediate successes. I don't know if that was
related, or not. I still have 4 workstations with the original 0e error, I
haven't done anything with them - there are no time sync issues with
those - and I have 10 other WSUS clients on the same network with no
errors. So it's a client side thing, I'm quite sure.
--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me and I'll
understand." - Confucius
Post by Chupacabra
Post by Les Connor [SBS Community Member - SBS MVP]
I got the error to change on one WSUS client ;-). Various things done,
starting with the re-install of msxml and registering the dll's. Not
surprisingly, that had no effect.
In the end, I stopped Automatic Updates and deleted everything in the
SoftwareDistribution folder, and restarted AU. I get a better result in
the log file, and the server reporting this error for the client 'Last
Detection Result'.
0x80244010 -2145107952 SUS E PT EXCEEDED MAX SERVER TRIPS The
maximum allowed number of round trips to the server was exceeded
That might be as a result of my running wuauclt too many times, or the
client diags (which reports no issues, BTW), while there's actually some
update cycle running. I'll leave it be for a while and see if the error
clears.
I've done that too - stopping automatic updates and blowing away the
SoftwareDistribution folder. No joy.
Also tried the
wuauclt /resetauthorization /detectnow
command with no luck. We reregistered the DLLs and did the msxml thing,
but we're still getting the 8007000e error.
Chupacabra
2006-08-02 13:42:03 UTC
Permalink
Post by Les Connor [SBS Community Member - SBS MVP]
Seems I'm one step ahead of you, then ;-).
We could compare client side logfiles, mine looks pretty good - no 0x8
errors at all.
Here's the most recent detect attempt:

2006-08-02 06:33:22 1128 46c AU #############
2006-08-02 06:33:22 1128 46c AU ## START ## AU: Search for updates
2006-08-02 06:33:22 1128 46c AU #########
2006-08-02 06:33:22 1128 46c AU <<## SUBMITTED ## AU: Search for updates
[CallId = {86D0C0AF-99DD-470E-8A5A-0E3030AD36C1}]
2006-08-02 06:33:22 1128 c10 Agent *************
2006-08-02 06:33:22 1128 c10 Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2006-08-02 06:33:22 1128 c10 Agent *********
2006-08-02 06:33:22 1128 c10 Setup *********** Setup: Checking whether
self-update is required ***********
2006-08-02 06:33:22 1128 c10 Setup * Inf file:
C:\WINNT\SoftwareDistribution\SelfUpdate\Default\wusetup.inf
2006-08-02 06:33:22 1128 c10 Setup Update NOT required for
C:\WINNT\system32\cdm.dll: target version = 5.8.0.2469, required version =
5.8.0.2469
2006-08-02 06:33:22 1128 c10 Setup Update NOT required for
C:\WINNT\system32\iuengine.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2006-08-02 06:33:22 1128 c10 Setup Update NOT required for
C:\WINNT\system32\wuapi.dll: target version = 5.8.0.2469, required version =
5.8.0.2469
2006-08-02 06:33:22 1128 c10 Setup Update NOT required for
C:\WINNT\system32\wuauclt.exe: target version = 5.8.0.2469, required version
= 5.8.0.2469
2006-08-02 06:33:22 1128 c10 Setup Update NOT required for
C:\WINNT\system32\wuauclt1.exe: target version = 5.8.0.2469, required
version = 5.8.0.2469
2006-08-02 06:33:22 1128 c10 Setup Update NOT required for
C:\WINNT\system32\wuaucpl.cpl: target version = 5.8.0.2469, required version
= 5.8.0.2469
2006-08-02 06:33:22 1128 c10 Setup Update NOT required for
C:\WINNT\system32\wuaueng.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2006-08-02 06:33:22 1128 c10 Setup Update NOT required for
C:\WINNT\system32\wuaueng1.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2006-08-02 06:33:22 1128 c10 Setup Update NOT required for
C:\WINNT\system32\wucltui.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2006-08-02 06:33:22 1128 c10 Setup Update NOT required for
C:\WINNT\system32\wups.dll: target version = 5.8.0.2469, required version =
5.8.0.2469
2006-08-02 06:33:22 1128 c10 Setup Update NOT required for
C:\WINNT\system32\wups2.dll: target version = 5.8.0.2469, required version =
5.8.0.2469
2006-08-02 06:33:22 1128 c10 Setup Update NOT required for
C:\WINNT\system32\wuweb.dll: target version = 5.8.0.2469, required version =
5.8.0.2469
2006-08-02 06:33:22 1128 c10 Setup * IsUpdateRequired = No
2006-08-02 06:33:22 1128 c10 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2006-08-02 06:33:22 1128 c10 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://sus/ClientWebService/client.asmx
2006-08-02 06:33:22 1128 c10 PT WARNING: Sync of Updates: 0x8007000e
2006-08-02 06:33:22 1128 c10 Agent * WARNING: Failed to synchronize, error
= 0x8007000E
2006-08-02 06:33:22 1128 c10 Agent * WARNING: Exit code = 0x8007000E
2006-08-02 06:33:22 1128 c10 Agent *********
2006-08-02 06:33:22 1128 c10 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2006-08-02 06:33:22 1128 c10 Agent *************
2006-08-02 06:33:22 1128 c10 Agent WARNING: WU client failed Searching for
update with error 0x8007000e
2006-08-02 06:33:22 1128 c10 AU >>## RESUMED ## AU: Search for updates
[CallId = {86D0C0AF-99DD-470E-8A5A-0E3030AD36C1}]
2006-08-02 06:33:22 1128 c10 AU # WARNING: Search callback failed, result
= 0x8007000E
2006-08-02 06:33:22 1128 c10 AU #########
2006-08-02 06:33:22 1128 c10 AU ## END ## AU: Search for updates [CallId
= {86D0C0AF-99DD-470E-8A5A-0E3030AD36C1}]
2006-08-02 06:33:22 1128 c10 AU #############
2006-08-02 06:33:22 1128 c10 AU AU setting next detection timeout to
2006-08-02 17:33:22
2006-08-02 06:33:27 1128 c10 Report REPORT EVENT:
{CBE636B3-A793-4D25-88EA-0AA643559F6A} 2006-08-02 06:33:22-0600 1 148 101
{00000000-0000-0000-0000-000000000000} 0 8007000e AutomaticUpdates Failure
Software Synchronization Error: Agent failed detecting with reason:
0x8007000e
2006-08-02 06:52:04 1128 c10 Report WARNING: Reporter failed to upload
events with hr = 8007000e.


Here's the output from the diagnostics tool:

WSUS Client Diagnostics Tool

Checking Machine State
Checking for admin rights to run tool . . . . . . . . . PASS
Automatic Updates Service is running. . . . . . . . . . PASS
Background Intelligent Transfer Service is not running. PASS
Wuaueng.dll version 5.8.0.2469. . . . . . . . . . . . . PASS
This version is WSUS 2.0

Checking AU Settings
AU Option is 4: Scheduled Install . . . . . . . . . . . PASS
Option is from Policy settings

Checking Proxy Configuration
Checking for winhttp local machine Proxy settings . . . PASS
Winhttp local machine access type
<Direct Connection>
Winhttp local machine Proxy. . . . . . . . . . NONE
Winhttp local machine ProxyBypass. . . . . . . NONE
Checking User IE Proxy settings . . . . . . . . . . . . PASS
User IE Proxy. . . . . . . . . . . . . . . . . NONE
User IE ProxyByPass. . . . . . . . . . . . . . NONE
User IE AutoConfig URL Proxy . . . . . . . . . NONE
User IE AutoDetect
AutoDetect in use

Checking Connection to WSUS/SUS Server
WUServer = http://sus
WUStatusServer = http://sus
UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
Connection to server. . . . . . . . . . . . . . . . . . PASS
SelfUpdate folder is present. . . . . . . . . . . . . . PASS

Press Enter to Complete
Les Connor [SBS Community Member - SBS MVP]
2006-08-02 18:42:46 UTC
Permalink
These are the steps I've taken for success. I don't know if they're all
required or not, nor if they'll work in your specific scenario - but they
worked for me.

1. Check the workstattion page file settings, and set to 'system managed',
if not there already.
2. Ensure time synchronization is working correctly (in this case, the SBS
server, also the WSUS server). Re-configure/reset if required.
3. Stop the Automatic Updates service, and delete everything in/under
SoftwareDistribution.
4. Start the Automatic Updates service, and run wuauclt /resetauthorization
/detectnow
5. Wait a couple of minutes, and check the windowsupdate log for activity
(not paying too much attention to errors, just looking for activity).
6. Restart the workstation.
7. Check windowsupdate log - now we're cooking :-)
8. Some time later (1/2 to 3/4 hour), the errors are cleared and reporting
status is success in the WSUS console (and/or SBS Update console, if you
have SBS).

Not a precision fix, I know, I just wanted to get done rather than document
a solution. It worked in every case. Luckily I only had 5 workstations to
touch ;-).
--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me and I'll
understand." - Confucius
Post by Chupacabra
Post by Les Connor [SBS Community Member - SBS MVP]
Seems I'm one step ahead of you, then ;-).
We could compare client side logfiles, mine looks pretty good - no 0x8
errors at all.
2006-08-02 06:33:22 1128 46c AU #############
2006-08-02 06:33:22 1128 46c AU ## START ## AU: Search for updates
2006-08-02 06:33:22 1128 46c AU #########
2006-08-02 06:33:22 1128 46c AU <<## SUBMITTED ## AU: Search for updates
[CallId = {86D0C0AF-99DD-470E-8A5A-0E3030AD36C1}]
2006-08-02 06:33:22 1128 c10 Agent *************
2006-08-02 06:33:22 1128 c10 Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2006-08-02 06:33:22 1128 c10 Agent *********
2006-08-02 06:33:22 1128 c10 Setup *********** Setup: Checking whether
self-update is required ***********
C:\WINNT\SoftwareDistribution\SelfUpdate\Default\wusetup.inf
2006-08-02 06:33:22 1128 c10 Setup Update NOT required for
C:\WINNT\system32\cdm.dll: target version = 5.8.0.2469, required version =
5.8.0.2469
2006-08-02 06:33:22 1128 c10 Setup Update NOT required for
C:\WINNT\system32\iuengine.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2006-08-02 06:33:22 1128 c10 Setup Update NOT required for
C:\WINNT\system32\wuapi.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2006-08-02 06:33:22 1128 c10 Setup Update NOT required for
C:\WINNT\system32\wuauclt.exe: target version = 5.8.0.2469, required
version = 5.8.0.2469
2006-08-02 06:33:22 1128 c10 Setup Update NOT required for
C:\WINNT\system32\wuauclt1.exe: target version = 5.8.0.2469, required
version = 5.8.0.2469
2006-08-02 06:33:22 1128 c10 Setup Update NOT required for
C:\WINNT\system32\wuaucpl.cpl: target version = 5.8.0.2469, required
version = 5.8.0.2469
2006-08-02 06:33:22 1128 c10 Setup Update NOT required for
C:\WINNT\system32\wuaueng.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2006-08-02 06:33:22 1128 c10 Setup Update NOT required for
C:\WINNT\system32\wuaueng1.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2006-08-02 06:33:22 1128 c10 Setup Update NOT required for
C:\WINNT\system32\wucltui.dll: target version = 5.8.0.2469, required
version = 5.8.0.2469
2006-08-02 06:33:22 1128 c10 Setup Update NOT required for
C:\WINNT\system32\wups.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2006-08-02 06:33:22 1128 c10 Setup Update NOT required for
C:\WINNT\system32\wups2.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2006-08-02 06:33:22 1128 c10 Setup Update NOT required for
C:\WINNT\system32\wuweb.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2006-08-02 06:33:22 1128 c10 Setup * IsUpdateRequired = No
2006-08-02 06:33:22 1128 c10 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2006-08-02 06:33:22 1128 c10 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://sus/ClientWebService/client.asmx
2006-08-02 06:33:22 1128 c10 PT WARNING: Sync of Updates: 0x8007000e
2006-08-02 06:33:22 1128 c10 Agent * WARNING: Failed to synchronize,
error = 0x8007000E
2006-08-02 06:33:22 1128 c10 Agent * WARNING: Exit code = 0x8007000E
2006-08-02 06:33:22 1128 c10 Agent *********
2006-08-02 06:33:22 1128 c10 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2006-08-02 06:33:22 1128 c10 Agent *************
2006-08-02 06:33:22 1128 c10 Agent WARNING: WU client failed Searching for
update with error 0x8007000e
2006-08-02 06:33:22 1128 c10 AU >>## RESUMED ## AU: Search for updates
[CallId = {86D0C0AF-99DD-470E-8A5A-0E3030AD36C1}]
2006-08-02 06:33:22 1128 c10 AU # WARNING: Search callback failed,
result = 0x8007000E
2006-08-02 06:33:22 1128 c10 AU #########
2006-08-02 06:33:22 1128 c10 AU ## END ## AU: Search for updates
[CallId = {86D0C0AF-99DD-470E-8A5A-0E3030AD36C1}]
2006-08-02 06:33:22 1128 c10 AU #############
2006-08-02 06:33:22 1128 c10 AU AU setting next detection timeout to
2006-08-02 17:33:22
{CBE636B3-A793-4D25-88EA-0AA643559F6A} 2006-08-02 06:33:22-0600 1 148 101
{00000000-0000-0000-0000-000000000000} 0 8007000e AutomaticUpdates Failure
0x8007000e
2006-08-02 06:52:04 1128 c10 Report WARNING: Reporter failed to upload
events with hr = 8007000e.
WSUS Client Diagnostics Tool
Checking Machine State
Checking for admin rights to run tool . . . . . . . . . PASS
Automatic Updates Service is running. . . . . . . . . . PASS
Background Intelligent Transfer Service is not running. PASS
Wuaueng.dll version 5.8.0.2469. . . . . . . . . . . . . PASS
This version is WSUS 2.0
Checking AU Settings
AU Option is 4: Scheduled Install . . . . . . . . . . . PASS
Option is from Policy settings
Checking Proxy Configuration
Checking for winhttp local machine Proxy settings . . . PASS
Winhttp local machine access type
<Direct Connection>
Winhttp local machine Proxy. . . . . . . . . . NONE
Winhttp local machine ProxyBypass. . . . . . . NONE
Checking User IE Proxy settings . . . . . . . . . . . . PASS
User IE Proxy. . . . . . . . . . . . . . . . . NONE
User IE ProxyByPass. . . . . . . . . . . . . . NONE
User IE AutoConfig URL Proxy . . . . . . . . . NONE
User IE AutoDetect
AutoDetect in use
Checking Connection to WSUS/SUS Server
WUServer = http://sus
WUStatusServer = http://sus
UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
Connection to server. . . . . . . . . . . . . . . . . . PASS
SelfUpdate folder is present. . . . . . . . . . . . . . PASS
Press Enter to Complete
Lawrence Garvin (MVP)
2006-08-03 22:09:56 UTC
Permalink
Post by Les Connor [SBS Community Member - SBS MVP]
These are the steps I've taken for success. I don't know if they're all
required or not, nor if they'll work in your specific scenario - but they
worked for me.
1. Check the workstattion page file settings, and set to 'system managed',
if not there already.
Les, what were the paging file settings set to, if not "system managed"?
This could definitely account for an out-of-memory error at the client
system, particularly if the system had a small paging file, or no paging
file, and a limited amount of physical RAM. (On XP that would be anything <
512MB; on Win2003 that would be anything < 2GB)
Post by Les Connor [SBS Community Member - SBS MVP]
2. Ensure time synchronization is working correctly (in this case, the SBS
server, also the WSUS server). Re-configure/reset if required.
This could affect domain authentication using Kerberos, but there's nothing
in WSUS that cares about synchronized times.
Post by Les Connor [SBS Community Member - SBS MVP]
Not a precision fix, I know, I just wanted to get done rather than
document a solution. It worked in every case. Luckily I only had 5
workstations to touch ;-).
How many of these five had paging files that were not "system managed"?

How much installed RAM?
--
Lawrence Garvin, M.S., MVP-Software Distribution
Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
And, everything else is at
http://wsusinfo.onsitechsolutions.com
....
Les Connor [SBS Community Member - SBS MVP]
2006-08-05 14:58:23 UTC
Permalink
As I recall, they all had fixed size page files of 768 (or thereabouts), and
they have 512mb ram.

I'll be checking a few more machines (and will confirm this) as I seen a few
more workstations that previously have no errors have now shown up with the
same error.

I should be able to focus on the just page file settings.

Thanks, Les.
--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me and I'll
understand." - Confucius
Post by Lawrence Garvin (MVP)
Post by Les Connor [SBS Community Member - SBS MVP]
These are the steps I've taken for success. I don't know if they're all
required or not, nor if they'll work in your specific scenario - but they
worked for me.
1. Check the workstattion page file settings, and set to 'system
managed', if not there already.
Les, what were the paging file settings set to, if not "system managed"?
This could definitely account for an out-of-memory error at the client
system, particularly if the system had a small paging file, or no paging
file, and a limited amount of physical RAM. (On XP that would be anything
< 512MB; on Win2003 that would be anything < 2GB)
Post by Les Connor [SBS Community Member - SBS MVP]
2. Ensure time synchronization is working correctly (in this case, the
SBS server, also the WSUS server). Re-configure/reset if required.
This could affect domain authentication using Kerberos, but there's
nothing in WSUS that cares about synchronized times.
Post by Les Connor [SBS Community Member - SBS MVP]
Not a precision fix, I know, I just wanted to get done rather than
document a solution. It worked in every case. Luckily I only had 5
workstations to touch ;-).
How many of these five had paging files that were not "system managed"?
How much installed RAM?
--
Lawrence Garvin, M.S., MVP-Software Distribution
Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
And, everything else is at
http://wsusinfo.onsitechsolutions.com
....
Jeff S
2007-04-03 16:09:16 UTC
Permalink
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 with SP2.

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.

EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com
p***@gmail.com
2007-04-04 19:15:24 UTC
Permalink
I have had this error at least 30 times in the past. In 100% of the
cases it was due to the workstation not rebooting for an extended
period (30 or more days) and a simple reboot solved it for me. I am
sorry it was so easy for me compared to other cases here. So you may
want to check the last reboot time of any machines showing this error.

Patrick Egan
Lawrence Garvin (MVP)
2007-04-04 22:54:58 UTC
Permalink
Post by p***@gmail.com
I have had this error at least 30 times in the past. In 100% of the
cases it was due to the workstation not rebooting for an extended
period (30 or more days) and a simple reboot solved it for me.
Now there's a thought. Any chance any updates were installed during that
30-days-without-reboot period of time?

Also, are any of these machines routinely accessed via Remote Desktop?
There's a known issue with this type of scenario involving RDC access to
desktop machines that are not rebooted, nor accessed via the machine console
on a regular basis.
--
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
....
Loading...