WSUS and Client Updates problems

-

i involved in wsus admin on lan , new wsus.  there issues come here for. rest assured getting boned-up fast can. else involved in seems, there urgent issue requires me fix , lear later.

here's pist client's machine. need unravel mystery machines not connecting.

i have followed steps referred in

http://technet.microsoft.com/en-us/library/cc708554.aspx

and have got down tle log checking part. access port 80 fine.

someone als referred me various links talked office 2003 sp1 don't think issue related reasons can outline if needed.

please on log , tell me first how disect , step thru problem solving if don't mind

and if don;t mind, can ask aside question - - - if wsus being used on wan, , goes windows update on computer , manually downloads updates . . . know mean updates getting on machines have not been approved.  that's understood. update agent used windows update cause incompatability used wsis 3.0???

2009-04-01      04:04:55:388       704      2bc      setup        * isupdaterequired = no
2009-04-01      04:04:58:310       704      2bc      pt      +++++++++++  pt: synchronizing server updates  +++++++++++
2009-04-01      04:04:58:310       704      2bc      pt        + serviceid = {3da21691-e39d-4da6-8a4b-b43877bcb1b7}, server url = http://xxx/clientwebservice/client.asmx
2009-04-01      04:04:58:935       704      2bc      pt      warning: cached cookie has expired or new pid available
2009-04-01      04:04:58:935       704      2bc      pt      initializing simple targeting cookie, clientid = 03456221-54e5-475a-8cc2-dbb7636f2752, target group = , dns name = wcc-tech
2009-04-01      04:04:58:935       704      2bc      pt        server url = http://xxx/simpleauthwebservice/simpleauth.asmx
2009-04-01      04:05:01:185       704      2bc      pt      warning: syncupdates failure, error = 0x8024400e, soap client error = 7, soap error code = 400, http status code = 200
2009-04-01      04:05:01:185       704      2bc      pt      warning: soap fault: 0x000190
2009-04-01      04:05:01:185       704      2bc      pt      warning:     faultstring:fault occurred
2009-04-01      04:05:01:185       704      2bc      pt      warning:     errorcode:internalservererror(5)
2009-04-01      04:05:01:185       704      2bc      pt      warning:     message:(null)
2009-04-01      04:05:01:185       704      2bc      pt      warning:     method:"http://www.microsoft.com/softwaredistribution/server/clientwebservice/syncupdates"
2009-04-01      04:05:01:185       704      2bc      pt      warning:     id:dcc760b3-013c-43e3-952f-cb193d228196
2009-04-01      04:05:01:185       704      2bc      pt      warning: pterror: 0x8024400e
2009-04-01      04:05:01:185       704      2bc      pt      warning: syncupdates_withrecovery failed.: 0x8024400e
2009-04-01      04:05:01:185       704      2bc      pt      warning: sync of updates: 0x8024400e
2009-04-01      04:05:01:185       704      2bc      pt      warning: syncserverupdatesinternal failed: 0x8024400e
2009-04-01      04:05:01:185       704      2bc      agent        * warning: failed synchronize, error = 0x8024400e
2009-04-01      04:05:01:200       704      2bc      agent        * warning: exit code = 0x8024400e
2009-04-01      04:05:01:200       704      2bc      agent      *********
2009-04-01      04:05:01:200       704      2bc      agent      **  end  **  agent: finding updates [callerid = automaticupdates]
2009-04-01      04:05:01:200       704      2bc      agent      *************
2009-04-01      04:05:01:200       704      2bc      agent      warning: wu client failed searching update error 0x8024400e
2009-04-01      04:05:01:216       704       c0      au      >>##  resumed  ## au: search updates [callid = {f378a57e-302c-4fe8-9645-2d393566f13f}]
2009-04-01      04:05:01:216       704       c0      au        # warning: search callback failed, result = 0x8024400e
2009-04-01      04:05:01:216       704       c0      au        # warning: failed find updates error code 8024400e
2009-04-01      04:05:01:216       704       c0      au      #########
2009-04-01      04:05:01:216       704       c0      au      ##  end  ##  au: search updates [callid = {f378a57e-302c-4fe8-9645-2d393566f13f}]
2009-04-01      04:05:01:216       704       c0      au      #############
2009-04-01      04:05:01:216       704       c0      au      au setting next detection timeout 2009-04-01 17:05:01
2009-04-01      04:05:01:216       704       c0      au      setting au scheduled install time 2009-04-01 20:00:00
2009-04-01      04:05:06:200       704      2bc      report      report event: {4548c396-e42e-4a17-8c9d-59ff37912860}      2009-04-01 04:05:01:200-0800      1      148      101      {00000000-0000-0000-0000-000000000000}      0      8024400e      automaticupdates      failure      software synchronization      windows update client failed detect error 0x8024400e.
2009-04-01      04:17:08:904       704      2bc      pt      warning: cached cookie has expired or new pid available
2009-04-01      04:17:08:904       704      2bc      pt      initializing simple targeting cookie, clientid = 03456221-54e5-475a-8cc2-dbb7636f2752, target group = , dns name = wcc-tech
2009-04-01      04:17:08:904       704      2bc      pt        server url = http://xxx/simpleauthwebservice/simpleauth.asmx
2009-04-01      04:17:09:247       704      2bc      report      uploading 1 events using cached cookie, reporting url = http://xxx/reportingwebservice/reportingwebservice.asmx
2009-04-01      04:17:09:341       704      2bc      report      reporter uploaded 1 events.
2009-04-01      08:02:10:857       704      dac      au      au found 0 updates install @ shutdown
2009-04-01      08:02:11:075      2920      398      misc      ===========  logging initialized (build: 7.0.6000.374, tz: -0800)  ===========
2009-04-01      08:02:11:075      2920      398      misc        = process: c:\windows\explorer.exe
2009-04-01      08:02:11:075      2920      398      misc        = module: c:\windows\system32\wuaueng.dll
2009-04-01      08:02:11:075      2920      398      shutdwn      install @ shutdown: no updates install
2009-04-01      08:02:31:497       704      e18      au      ###########  au: uninitializing automatic updates  ###########
2009-04-01      08:02:35:279       704      e18      service      *********
2009-04-01      08:02:35:279       704      e18      service      **  end  **  service: service exit [exit code = 0x240001]
2009-04-01      08:02:35:279       704      e18      service      *************

i realize don't think issue related office 2003, every instance of 0x8024400e/soap 0x190 errors i've seen in past 6 months has been resolved following instructions remediating office 2003 scenario. if don't think it's related: follow instructions. if problem still exists after performing instructions documented, we'll elsewhere.

as wan question -- no, there no incompatibilities. you'll have updates installed on machine that's not approved on wsus server. if update not declined on wsus server, wua should report correct status "installed/not applicable" update.
lawrence garvin, m.s., mcitp:ea, mcdba
principal/cto, onsite technology solutions, houston, texas
microsoft mvp - software distribution (2005-2009)


Windows Server  >  WSUS



Comments

Post a Comment

Popular posts from this blog

for loop and start-job from cmd.exe

-
hello, i have simple script developed debug purposes: $serverlist = @( "sca-c1cor01", "scb-c1cor01" ) ($i=0; $i -lt $serverlist.length; $i++) { start-job -scriptblock {$x=0} } i have saved script off file called test.ps1.  when run ./test.ps1 within interactive powershell runs fine.  i trying to call script dos window, sql server agent command job, or start->run line.  here syntax using: cmd.exe /c powershell -nologo -noninteractive "c:\scripts\powershell\test.ps1" when run way (from dos window), diaglog box pops says: powershell has stopped working  problem caused program stop working correctly.  windows close program , notify if solution available. i close , open eventvwr.msc.  2 pieces of info.  1 application , services log (windows powershell): engine state changed available stopped. details:  newenginestate=stopped  previousenginestate...
Read more

Edit Group Policy

-
i have pc has power settings pushed out default domain policy in ad environment. of course on local machine "some settings managed system adminstrator". the machine temporarily no longer in contact domain controller (it's been physically moved , not on same network now) can't updated gpo settings. i believe if edit local group policy won't make difference because of group policy processing , precedence. since it's temporary away ad network, still want use settings of ad user. is there somewhere in registry stored can edit power plan manually until can sync domain? (i need prevent sleeping while plugged in - it's set 1 hour) thanks! allen crist i found site: http://gpsearch.azurewebsites.net/#7916 i able add policy to hkey_local_machine\software\policies\microsoft\power using specs found on site. looks solved issue. i'll report if didn't. thanks! allen crist ...
Read more

File Share Witness is not a valid File share path

-
i have 2 windows 2008 r2 vms (esxi) running double-take. we have health-check running on our netscaler force failover primary vm secondary vm if netscaler cannot access smb share on primary vm. this hasn't proven method of providing fault tolerance, trying cluster these 2 vms using file share witness. (i should add client engineers solution, implement according requirements). the witness share has been created on emc vnx. domain account , domain cluster computer name account both have full control permissions on share. i have installed the file services role failover clustering feature on both vms. to configure quorum, selecting node , file share majority (for clusters special configuration). i providing ip address , share name in form of \\<ipaddress>\<sharename>. the wizard returns \\<ipaddress>\<sharename> not valid share path. reading documentation microsoft, there statement saying witness share should have nothing else stored or u...
Read more