asked on

win2k server sp4, installed SUS. AD GP complete and correct settings displayed on clients, but clients wont update, here is log

win2k server sp4, installed SUS. AD GP complete and correct settings displayed on clients, but clients wont update, here is log;

2005-04-06      08:43:46+0800       860      5e0      Service Main starts
2005-04-06      08:43:46+0800       860      5e0      Using BatchFlushAge = 20380.
2005-04-06      08:43:46+0800       860      5e0      Using SamplingValue = 165.
2005-04-06      08:43:46+0800       860      5e0      Successfully loaded event namespace dictionary.
2005-04-06      08:43:46+0800       860      5e0      Successfully loaded client event namespace descriptor.
2005-04-06      08:43:46+0800       860      5e0      Successfully initialized local event logger. Events will be logged at C:\WINDOWS\SoftwareDistribution\ReportingEvents.log.
2005-04-06      08:43:46+0800       860      5e0      Successfully initialized NT event logger.
2005-04-06      08:43:46+0800       860      5e0      Successfully initialized event uploader 0.
2005-04-06      08:43:46+0800       860      5e0      Successfully initialized event uploader 1.
2005-04-06      08:43:46+0800       860      5e0      WU client with version 5.4.3790.2182 successfully initialized
2005-04-06      08:43:46+0800       860      5e0      Service status is now SERVICE_RUNNING
2005-04-06      08:44:31+0800       860      5e0      start delayed initialization of WU client
2005-04-06      08:44:32+0800       484      1ec      Trying to make out of proc datastore active
2005-04-06      08:44:32+0800       484      1ec      Out of proc datastore is now active
2005-04-06      08:44:32+0800       860      5e0      Client Call Recorder finished delayed initialization
2005-04-06      08:44:32+0800       860      5e0      Setting next AU detection timeout to 2005-04-06 00:44:32
2005-04-06      08:44:32+0800       860      5e0      AU finished delayed initialization
2005-04-06      08:44:32+0800       860      5e0      AU received event of 1
2005-04-06      08:44:32+0800       860      5e0      WU client succeeds CClientCallRecorder::BeginFindUpdates from AutomaticUpdates with call id {AB2280F8-3173-4438-92E5-684A9B625887}
2005-04-06      08:44:32+0800       860      49c      WU client executing call {AB2280F8-3173-4438-92E5-684A9B625887} of type Search Call
2005-04-06      08:44:34+0800       860      49c      DownloadFileInternal failed for http://10.1.1.38/SelfUpdate/wuident.cab: error 0x80190194
2005-04-06      08:44:34+0800       860      49c      SUS server version is 1.0, client selfupdate not possible
2005-04-06      08:44:34+0800       860      49c      WU client failed Searching for update with error 0x8024002b
2005-04-06      08:44:34+0800       860      49c      Detected Sus 1.0 server
2005-04-06      08:44:34+0800       860      49c      AU Restart required....
2005-04-06      08:44:34+0800       860      49c      Search Callback Failed, hr is 0x8024002b
2005-04-06      08:44:34+0800       860      49c      Setting next AU detection timeout to 2005-04-06 20:18:59
2005-04-06      08:44:34+0800       860      5e0      AU received event of 1
2005-04-06      08:44:34+0800       860      49c      WU client calls back to search call AutomaticUpdates with code Call failed and error 0x8024002b
2005-04-06      08:44:34+0800       860      49c      WU client completed and deleted call {AB2280F8-3173-4438-92E5-684A9B625887}
2005-04-06      08:44:34+0800       860      5e0      Launching Legacy AU client
2005-04-06      08:48:44+0800       484      1ec      Out of proc datastore is shutting down
2005-04-06      08:48:45+0800       484      1ec      Out of proc datastore is now inactive
2005-04-06      08:55:51+0800       860      360      Service received connect notification
2005-04-06      08:55:51+0800       860      360      Forwarding control handler info to legacy AU
2005-04-06      08:55:53+0800       860      360      Service received logon notification
2005-04-06      08:55:53+0800       860      360      Forwarding control handler info to legacy AU
2005-04-06      08:56:15+0800       860      360      Forwarding control handler info to legacy AU
2005-04-06      12:10:22+0800       860      360      Forwarding control handler info to legacy AU

any ideas?

Nirmal Sharma

The error is logged when the Automatic Updates client tries to check the server that is running Software Update Services for driver updates that Software Update Services does not synchronize. Therefore, the Autoupdatedrivers folder does not exist on the server that is running Software Update Services. Error 0x80190194 is actually an HTTP status code 404 (File Not Found). This code is returned to the client by the server that is running Software Update Services.

Let me know.

acetate

ASKER

hi Systmprog,

yes, i know about this problem, but there are other errors in there stopping this from working. on the clients that are succesful i still get that error, is there something else im missing?

Nirmal Sharma

Hi,

>>>on the clients that are succesful i still get that error, is there something else im missing?

You will get errors because SUS does not support updating device drivers. You need to use WUS if you want to deploy third party services, drivers, and applications or patches for other products. One more thing verify the Windows Update Client version installed on client machines.

Let me know.

acetate

ASKER

how do i verify the version of windows update client? some pcs are xp sp1 and some are xp sp2, and some are win2k.

win2k is workign fine.

im only trying to install approved updates from the SUS server

Nirmal Sharma

>>>im only trying to install approved updates from the SUS server

I am just not clear here.

Are XP clients able to pull updates from SUS Server?
What is the exact problem now? Is the problem with the Log you posted?

Thanks

acetate

ASKER

hi sysmprog, i'll get back to you.

thanks,

ASKER CERTIFIED SOLUTION

Nirmal Sharma

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

acetate

ASKER

hi systm prog,

the problem was with the registry key DISABLEWINDOWSUPDATEACCESS i deleted this registry key on the offending pc and then SUS is working! now all my test pcs are working.

Nirmal Sharma

Glad! I could be of some help.

Thanks!