Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.

Dismiss

0x800710DD error trying to run windows updates

13 views

Skip to first unread message

mikem

unread,

Sep 28, 2004, 3:11:09 PM9/28/04

Judging from the numerous other postings here it is quite obvious this is a
very serious problem that is not being addressed properly at MS.
I too have the problem and am looking for a reason why when I did not change
any settings except to download the "new" download software.

Scott Davis

unread,

Dec 19, 2004, 1:27:18 AM12/19/04

to mikem

I encountered this, amongst other "un-supported" problems. The general
fix I've found is to manually erase my "client" PCs WU/AU config - and
start fresh.

I find that if I do the steps below to my workstations, they behave
properly thereafter..

1) Remove Registry key:
\\LM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate

2) Remove Registry key:
\\LM\Software\Microsoft\Policies\Microsoft\Windows\WindowsUpdate\AU

3) Workstations NOW report in WindowsUpdate.log that AU is not
configured. Configure the stupid thing.

3b) To config the stupid thing, I go Start-> ControlPanel->
AutomaticUpdates.. and "enable" the Automatic Updates.

My environment is:

MS-SmallBusiness Server 2003, with Active Directory. Group Policies set
to "enforce" AU/WUS setup..

.. so, why step 3b) (above) is required.. is beyond me. But it looks
like the patching will happen. Yay.

Problem:

The WUSAdmin site still dosen't "show" these computers that are now
communicating with the WUS "site" without error. Damned if I dunno why..?

So, those of you with bizarre client errors -- I suggest forcing the
WU/AU client(s) to re-do their config from scratch. It's the most
promising approach to fixing bizarre, undocumented errors (like
800710dd).. in my opinion.

More research and community feedback on this would be *VERY* helpful, to
all of us -- I think!

Thanks,

-- Scott.

--
====================================================
Scott Davis, 45 Dunfield Av, Unit 2117
Self-Employed Toronto, ON, Canada, M4S 2H4
Tech Consultant Mobile. (416) 432-4334

The IP addrs I use to post all UseNet:
66.207.215.240/29
====================================================

Athif

unread,

Dec 20, 2004, 1:35:44 AM12/20/04

Hi,
The error means ERROR_INVALID_OPERATION.
Could you tell us when do you see this error.??

Mohammed.Athif Khaleel.

Scott Davis

unread,

Jan 1, 2005, 4:55:37 AM1/1/05

Yes, I can document when I see this error.. it occurs every 5 minutes,
per my logs.

Here's a snippet from one desktop log (they all seem to be the same..)

Anything you can offer, as advice would be greatly appreciated, Mohammed..

Peace,

-- Scott.

2005-01-01 04:49:43-0500 812 34c Successfully opened event cache file
at
C:\WINDOWS\SoftwareDistribution\EventCache\{DC3B7DD0-9CF9-4369-B661-BB8ACB110D0E}.bin
for reading.
2005-01-01 04:49:44-0500 2440 804 Trying to make out of proc datastore
active
2005-01-01 04:49:44-0500 2440 804 Out of proc datastore is now active
2005-01-01 04:49:44-0500 812 34c PT: Using serverID
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2005-01-01 04:49:44-0500 812 34c PT: Using server URL
http://roeserver:8530/ClientWebService/client.asmx
2005-01-01 04:49:44-0500 812 34c PT: Calling GetConfig on server
2005-01-01 04:49:44-0500 812 34c Add header for accept-encoding: xpress
succeeded
2005-01-01 04:49:44-0500 812 34c DetectCompressionType returning type
0, hr=0x1
2005-01-01 04:49:44-0500 812 34c SendRequest failed with hr = 800710dd.
Proxy List used: <(null)> Bypass List used : <(null)>
2005-01-01 04:49:44-0500 812 34c GetConfig: 0x800710dd
2005-01-01 04:49:44-0500 812 34c PT: Cannot recover from fault,
origin=GetConfig, hr=0x800710dd
2005-01-01 04:49:44-0500 812 34c Failed to obtain cached cookie with hr
= 800710dd.
2005-01-01 04:49:44-0500 812 34c Failed to upload events with hr =
800710dd.
2005-01-01 04:54:01-0500 812 330 Service received SERVICE_CONTROL_STOP
control
2005-01-01 04:54:01-0500 812 77c Exiting Service Main
2005-01-01 04:54:01-0500 2440 804 Out of proc datastore is shutting down
2005-01-01 04:54:01-0500 812 77c WUAUENG ServiceMain exits. Exit code
is 0x240001
2005-01-01 04:54:03-0500 2440 804 Out of proc datastore is now inactive
2005-01-01 04:54:03-0500 812 f78 Service Main starts
2005-01-01 04:54:03-0500 812 f78 Using BatchFlushAge = 24705.
2005-01-01 04:54:03-0500 812 f78 Using SamplingValue = 649.
2005-01-01 04:54:03-0500 812 f78 Successfully loaded event namespace
dictionary.
2005-01-01 04:54:03-0500 812 f78 Successfully loaded client event
namespace descriptor.
2005-01-01 04:54:03-0500 812 f78 Successfully initialized local event
logger. Events will be logged at
C:\WINDOWS\SoftwareDistribution\ReportingEvents.log.
2005-01-01 04:54:03-0500 812 f78 Successfully initialized NT event logger.
2005-01-01 04:54:03-0500 812 f78 Successfully initialized event uploader 0.
2005-01-01 04:54:03-0500 812 f78 Successfully initialized event uploader 1.
2005-01-01 04:54:03-0500 812 f78 WU client with version 5.4.3790.2182
successfully initialized
2005-01-01 04:54:03-0500 812 f78 Service status is now SERVICE_RUNNING
2005-01-01 04:54:03-0500 812 408 Successfully opened event cache file
at
C:\WINDOWS\SoftwareDistribution\EventCache\{DC3B7DD0-9CF9-4369-B661-BB8ACB110D0E}.bin
for reading.
2005-01-01 04:54:03-0500 904 754 Trying to make out of proc datastore
active
2005-01-01 04:54:03-0500 904 754 Out of proc datastore is now active
2005-01-01 04:54:03-0500 812 408 PT: Using serverID
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2005-01-01 04:54:03-0500 812 408 Failed to obtain cached cookie with hr
= 8024001a.
2005-01-01 04:54:03-0500 812 408 Failed to upload events with hr =
8024001a.
2005-01-01 04:54:48-0500 812 f78 start delayed initialization of WU client
2005-01-01 04:54:48-0500 812 f78 Client Call Recorder finished delayed
initialization
2005-01-01 04:54:48-0500 812 f78 Setting AU scheduled install time to
2005-01-02 08:00:00
2005-01-01 04:54:48-0500 812 f78 AU finished delayed initialization

Scott Davis

unread,

Jan 1, 2005, 5:31:44 AM1/1/05

Scott Davis wrote:
> Athif wrote:
>
>> Hi,
>> The error means ERROR_INVALID_OPERATION.
>> Could you tell us when do you see this error.??
>>
>> Mohammed.Athif Khaleel.

Who's this scott goof? :)

Kidding aside, here's some more log fun...

store is now inactive
2005-01-01 05:20:18-0500 872 e38 Service Main starts
2005-01-01 05:20:18-0500 872 e38 Using BatchFlushAge = 31540.
2005-01-01 05:20:18-0500 872 e38 Using SamplingValue = 831.
2005-01-01 05:20:18-0500 872 e38 Successfully loaded event namespace
dictionary.
2005-01-01 05:20:18-0500 872 e38 Successfully loaded client event
namespace descriptor.
2005-01-01 05:20:18-0500 872 e38 Successfully initialized local event

logger. Events will be logged at
C:\WINDOWS\SoftwareDistribution\ReportingEvents.log.

2005-01-01 05:20:18-0500 872 e38 Successfully initialized NT event logger.
2005-01-01 05:20:18-0500 872 e38 Successfully initialized event uploader 0.
2005-01-01 05:20:18-0500 872 e38 Successfully initialized event uploader 1.
2005-01-01 05:20:18-0500 872 e38 WU client with version 5.4.3790.2182
successfully initialized
2005-01-01 05:20:18-0500 872 e38 Service status is now SERVICE_RUNNING
2005-01-01 05:21:03-0500 872 e38 start delayed initialization of WU client
2005-01-01 05:21:03-0500 2068 9b0 Trying to make out of proc datastore
active
2005-01-01 05:21:04-0500 2068 9b0 Out of proc datastore is now active
2005-01-01 05:21:04-0500 872 e38 Client Call Recorder finished delayed
initialization
2005-01-01 05:21:04-0500 872 e38 Setting next AU detection timeout to
2005-01-01 10:21:04
2005-01-01 05:21:04-0500 872 e38 Setting AU scheduled install time to
2005-01-02 08:00:00
2005-01-01 05:21:04-0500 872 e38 AU finished delayed initialization
2005-01-01 05:21:04-0500 872 e38 AU received event of 1
2005-01-01 05:21:04-0500 872 e38 WU client succeeds
CClientCallRecorder::BeginFindUpdates from AutomaticUpdates with call id
{73C068A9-6F54-464A-9CEC-2629DF6E1A6E}
2005-01-01 05:21:04-0500 872 160 WU client executing call
{73C068A9-6F54-464A-9CEC-2629DF6E1A6E} of type Search Call
2005-01-01 05:21:18-0500 872 160 Send failed with hr = 80072f8f.
2005-01-01 05:21:18-0500 872 160 SendRequest failed with hr = 80072f8f.