Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

WSUS working but not

Status
Not open for further replies.

jblewis

MIS
Jun 25, 2003
110
0
0
US
Sorry for the long post but here is the log from one of my (problematic) client PCs:

2005-09-01 08:29:35 1792 784 Misc =========== Logging initialized (build: 5.8.0.2469, tz: -0500) ===========
2005-09-01 08:29:35 1792 784 Misc = Process: C:\WINDOWS\System32\svchost.exe
2005-09-01 08:29:35 1792 784 Misc = Module: C:\WINDOWS\system32\wuaueng.dll
2005-09-01 08:29:35 1792 784 Service *************
2005-09-01 08:29:35 1792 784 Service ** START ** Service: Service startup
2005-09-01 08:29:35 1792 784 Service *********
2005-09-01 08:29:35 1792 784 Agent * WU client version 5.8.0.2469
2005-09-01 08:29:35 1792 784 Agent * SusClientId = 'bdf7fea7-d22f-44f5-b0e2-682045c4a97f'
2005-09-01 08:29:35 1792 784 Agent * Base directory: C:\WINDOWS\SoftwareDistribution
2005-09-01 08:29:35 1792 784 Agent * Access type: No proxy
2005-09-01 08:29:35 1792 784 Agent * Network state: Connected
2005-09-01 08:29:54 1792 784 Service *********
2005-09-01 08:29:54 1792 784 Service ** END ** Service: Service exit [Exit code = 0x240001]
2005-09-01 08:29:54 1792 784 Service *************
2005-09-01 08:29:57 1792 c78 Misc =========== Logging initialized (build: 5.8.0.2469, tz: -0500) ===========
2005-09-01 08:29:57 1792 c78 Misc = Process: C:\WINDOWS\System32\svchost.exe
2005-09-01 08:29:57 1792 c78 Misc = Module: C:\WINDOWS\system32\wuaueng.dll
2005-09-01 08:29:57 1792 c78 Service *************
2005-09-01 08:29:57 1792 c78 Service ** START ** Service: Service startup
2005-09-01 08:29:57 1792 c78 Service *********
2005-09-01 08:29:57 1792 c78 Agent * WU client version 5.8.0.2469
2005-09-01 08:29:57 1792 c78 Agent * WARNING: Failed to obtain SusClientId
2005-09-01 08:29:57 1792 c78 Agent * Base directory: C:\WINDOWS\SoftwareDistribution
2005-09-01 08:29:57 1792 c78 Agent * Access type: No proxy
2005-09-01 08:29:57 1792 c78 Agent * Network state: Connected
2005-09-01 08:30:01 1792 c24 Agent *********** Agent: Initializing Windows Update Agent ***********
2005-09-01 08:30:01 1792 c24 Agent *********** Agent: Initializing global settings cache ***********
2005-09-01 08:30:01 1792 c24 Agent * WSUS server: 2005-09-01 08:30:01 1792 c24 Agent * WSUS status server: 2005-09-01 08:30:01 1792 c24 Agent * Target group: Workstations-SP2
2005-09-01 08:30:01 1792 c24 Agent * Windows Update access disabled: No
2005-09-01 08:30:01 1792 c24 DnldMgr Download manager restoring 0 downloads
2005-09-01 08:30:01 1792 c24 AU ########### AU: Initializing Automatic Updates ###########
2005-09-01 08:30:01 1792 c24 AU AU setting next detection timeout to 2005-09-01 13:30:01
2005-09-01 08:30:01 1792 c24 AU # WSUS server: 2005-09-01 08:30:01 1792 c24 AU # Detection frequency: 22
2005-09-01 08:30:01 1792 c24 AU # Target group: Workstations-SP2
2005-09-01 08:30:01 1792 c24 AU # Approval type: Scheduled (Policy)
2005-09-01 08:30:01 1792 c24 AU # Scheduled install day/time: Every day at 9:00
2005-09-01 08:30:01 1792 c24 AU # Auto-install minor updates: Yes (Policy)
2005-09-01 08:30:01 1792 c78 AU #############
2005-09-01 08:30:01 1792 c78 AU ## START ## AU: Search for updates
2005-09-01 08:30:01 1792 c78 AU #########
2005-09-01 08:30:01 1792 c78 AU <<## SUBMITTED ## AU: Search for updates [CallId = {29999661-47C1-4C33-8414-E7E1ECDAFC83}]
2005-09-01 08:30:01 1792 c24 AU Triggering AU detection through DetectNow API
2005-09-01 08:30:01 1792 c78 AU Another AU detection is already in progress, using it
2005-09-01 08:30:01 1792 138 Agent *************
2005-09-01 08:30:01 1792 138 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2005-09-01 08:30:01 1792 138 Agent *********
2005-09-01 08:30:19 1792 138 Setup *********** Setup: Checking whether self-update is required ***********
2005-09-01 08:30:19 1792 138 Setup * Inf file: C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wusetup.inf
2005-09-01 08:30:24 1792 138 Setup Update NOT required for C:\WINDOWS\system32\cdm.dll: target version = 5.8.0.2469, required version = 5.8.0.2469
2005-09-01 08:30:26 1792 138 Setup Update NOT required for C:\WINDOWS\system32\iuengine.dll: target version = 5.8.0.2469, required version = 5.8.0.2469
2005-09-01 08:30:28 1792 138 Setup Update NOT required for C:\WINDOWS\system32\wuapi.dll: target version = 5.8.0.2469, required version = 5.8.0.2469
2005-09-01 08:30:28 1792 138 Setup Update NOT required for C:\WINDOWS\system32\wuauclt.exe: target version = 5.8.0.2469, required version = 5.8.0.2469
2005-09-01 08:30:29 1792 138 Setup Update NOT required for C:\WINDOWS\system32\wuauclt1.exe: target version = 5.8.0.2469, required version = 5.8.0.2469
2005-09-01 08:30:29 1792 138 Setup Update NOT required for C:\WINDOWS\system32\wuaucpl.cpl: target version = 5.8.0.2469, required version = 5.8.0.2469
2005-09-01 08:30:29 1792 138 Setup Update NOT required for C:\WINDOWS\system32\wuaueng.dll: target version = 5.8.0.2469, required version = 5.8.0.2469
2005-09-01 08:30:31 1792 138 Setup Update NOT required for C:\WINDOWS\system32\wuaueng1.dll: target version = 5.8.0.2469, required version = 5.8.0.2469
2005-09-01 08:30:32 1792 138 Setup Update NOT required for C:\WINDOWS\system32\wucltui.dll: target version = 5.8.0.2469, required version = 5.8.0.2469
2005-09-01 08:30:32 1792 138 Setup Update NOT required for C:\WINDOWS\system32\wups.dll: target version = 5.8.0.2469, required version = 5.8.0.2469
2005-09-01 08:30:32 1792 138 Setup Update NOT required for C:\WINDOWS\system32\wups2.dll: target version = 5.8.0.2469, required version = 5.8.0.2469
2005-09-01 08:30:33 1792 138 Setup Update NOT required for C:\WINDOWS\system32\wuweb.dll: target version = 5.8.0.2469, required version = 5.8.0.2469
2005-09-01 08:30:33 1792 138 Setup * IsUpdateRequired = No
2005-09-01 08:30:43 1792 138 PT +++++++++++ PT: Synchronizing server updates +++++++++++
2005-09-01 08:30:43 1792 138 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = 2005-09-01 08:30:43 1792 138 PT Initializing simple targeting cookie, clientId = 4e796eef-f246-48e2-bb14-8042d62d6f3e, target group = Workstations-SP2, DNS name = pc1283.ema-inc.com
2005-09-01 08:30:43 1792 138 PT Server URL = 2005-09-01 08:32:24 1792 138 PT WARNING: SyncUpdates failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
2005-09-01 08:32:24 1792 138 PT WARNING: SOAP Fault: 0x00012c
2005-09-01 08:32:24 1792 138 PT WARNING: faultstring:Fault occurred
2005-09-01 08:32:24 1792 138 PT WARNING: ErrorCode:RegistrationRequired(3)
2005-09-01 08:32:24 1792 138 PT WARNING: Message:need to call RegisterComputer.
2005-09-01 08:32:24 1792 138 PT WARNING: Method:"2005-09-01 08:32:24 1792 138 PT WARNING: ID:b86357e6-b10c-4bd0-aa1b-a786c490c94e
2005-09-01 08:32:24 1792 138 PT Initializing simple targeting cookie, clientId = 4e796eef-f246-48e2-bb14-8042d62d6f3e, target group = Workstations-SP2, DNS name = pc1283.ema-inc.com
2005-09-01 08:32:24 1792 138 PT Server URL = 2005-09-01 08:32:26 1792 138 PT +++++++++++ PT: Synchronizing extended update info +++++++++++
2005-09-01 08:32:26 1792 138 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = 2005-09-01 08:32:36 1792 138 Agent * Found 0 updates and 9 categories in search
2005-09-01 08:32:36 1792 138 Report *********** Report: Initializing static reporting data ***********
2005-09-01 08:32:36 1792 138 Report * OS Version = 5.1.2600.2.0.65792
2005-09-01 08:32:36 1792 138 Report * Computer Brand = Dell Computer Corporation
2005-09-01 08:32:36 1792 138 Report * Computer Model = Latitude D600
2005-09-01 08:32:36 1792 138 Report * Bios Revision = A08
2005-09-01 08:32:36 1792 138 Report * Bios Name = Phoenix ROM BIOS PLUS Version 1.10 A08
2005-09-01 08:32:36 1792 138 Report * Bios Release Date = 2003-10-29T00:00:00
2005-09-01 08:32:36 1792 138 Report * Locale ID = 1033
2005-09-01 08:32:37 1792 138 Agent *********
2005-09-01 08:32:37 1792 138 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2005-09-01 08:32:37 1792 138 Agent *************
2005-09-01 08:32:37 1792 2dc AU >>## RESUMED ## AU: Search for updates [CallId = {29999661-47C1-4C33-8414-E7E1ECDAFC83}]
2005-09-01 08:32:37 1792 2dc AU # 0 updates detected
2005-09-01 08:32:37 1792 2dc AU #########
2005-09-01 08:32:37 1792 2dc AU ## END ## AU: Search for updates [CallId = {29999661-47C1-4C33-8414-E7E1ECDAFC83}]
2005-09-01 08:32:37 1792 2dc AU #############
2005-09-01 08:32:37 1792 2dc AU AU setting next detection timeout to 2005-09-02 10:53:59
2005-09-01 08:32:39 1792 138 Report Uploading 1 events using cached cookie, reporting URL = 2005-09-01 08:32:39 1792 138 Report Reporter successfully uploaded 1 events.
2005-09-01 08:32:39 1792 138 Report Uploading 1 events using cached cookie, reporting URL = 2005-09-01 08:32:39 1792 138 Report Reporter successfully uploaded 1 events.
2005-09-01 08:32:42 1792 8a4 Report REPORT EVENT: {4987D4D1-94EF-4ED2-8952-B844B505CA8F} 2005-09-01 08:32:36-0500 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Agent has finished detecting items.
2005-09-01 08:32:42 1792 8a4 Report REPORT EVENT: {2027602A-2912-4795-893C-EA080590AF6C} 2005-09-01 08:32:37-0500 1 153 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
2005-09-01 08:37:57 1792 2dc Report Uploading 2 events using cached cookie, reporting URL = 2005-09-01 08:37:57 1792 2dc Report Reporter successfully uploaded 2 events.
2005-09-01 09:00:14 1792 c78 AU Forced install timer expired for scheduled install
------

It seems to be checking in, but if I look at WSUS admin page, it says this PC hasn't checked in in 9 days.

I tried deleting the clientID registries, and resetting the service with wuauclt (it worked once on 8/22) again, but that doesn't seem to doing anything now...
I've pretty much run out of ideas at this point.

JBLewis
 
I also just noticed that in the registry, on this machine, it has an AccountDomainSID entry, and a SusClientID, but not a PingID.

JBLewis
 
Well, one of our first tier analysts worked on this person's machine and now it is working. I actually had a script very similar to that of the KB article set as a *Startup* script on the machine in question.

I think there were some other networking issues going on on it. So it works now, but unfortuantely, no root cause.

JB

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top