I remember when that was first posted - I was assuming AuCheck utility did much the same stuff...however I may give it a try as I am becoming increasingly annoyed :-)
2008/11/10 Kelsey, John <[EMAIL PROTECTED]> > Did you try this? > > http://www.espinola.net/wiki/So_you_want_to_fix_all_your_WSUS_clients > > > ******************************* > *John C. Kelsey > *DuBois Regional Medical Center > (: 814.375.3073 > *: [EMAIL PROTECTED] > ******************************* > > -----Original Message----- > *From:* James Rankin [mailto:[EMAIL PROTECTED] > *Sent:* Monday, November 10, 2008 10:29 > *To:* NT System Admin Issues > *Subject:* Re: WSUS/WU error > > Already done that, as noted in my bullet-point list. No dice. > > Cheers, > > > 2008/11/10 Anatoly Podgoretsky <[EMAIL PROTECTED]> > >> Try delete C:\WINDOWS\SoftwareDistribution, may be help. >> >> Anatoly Podgoretsky >> http://www.podgoretsky.com >> >> >> >> ----- Original Message ----- >> *From:* James Rankin <[EMAIL PROTECTED]> >> *To:* NT System Admin Issues <[email protected]> >> *Sent:* Monday, November 10, 2008 5:16 PM >> *Subject:* WSUS/WU error >> >> Hi chaps >> >> I am continually getting an error of "0x800703E3" when trying to download >> updates via WSUS or Windows Update to about three of my servers. All the >> usual stuff doesn't seem to work, I have tried:- >> >> >> - Deleting SoftwareDistribution folder >> - Re-registering WSUS dlls >> - Re-installing the Windows Update Agent with the /wuforce switch >> - Running the AUCheck utility from CodePlex (which seemed really >> promising but didn't seem to do anything) >> >> >> Googling doesn't seem to give me any useful results. These machines were >> all clones of each other, but removing the SusID from the Registry solved >> all that stuff - and that's all to do with appearing in the WSUS console as >> I remember, not picking up updates. WindowsUpdate.log always seems to show >> these entries:- >> >> 2008-11-10 15:08:03:358 980 3874 Service ** START ** >> Service: Service startup >> 2008-11-10 15:08:03:358 980 3874 Service ********* >> 2008-11-10 15:08:03:358 980 3874 Agent * WU client >> version 7.0.6000.374 >> 2008-11-10 15:08:03:358 980 3874 Agent * Base directory: >> C:\WINDOWS\SoftwareDistribution >> 2008-11-10 15:08:03:358 980 3874 Agent * Access type: No >> proxy >> 2008-11-10 15:08:03:358 980 3874 Agent * Network state: >> Connected >> 2008-11-10 15:08:06:327 7800 3944 Setup * WARNING: Exit >> code = 0x800703E3 >> 2008-11-10 15:08:06:327 7800 3944 Setup ********* >> 2008-11-10 15:08:06:327 7800 3944 Setup ** END ** Setup: >> Installing client binaries >> 2008-11-10 15:08:06:327 7800 3944 Setup ************* >> 2008-11-10 15:08:06:327 7800 3944 Setup FATAL: >> InstallUpdatedBinaries failed with error 0x800703e3 >> 2008-11-10 15:08:06:327 7800 3944 WUWeb FATAL: >> InstallUpdatedBinaries failed with error:0x800703e3 >> 2008-11-10 15:08:06:327 7800 3944 WUWeb FATAL: >> UpdateClientWorker failed: error 0x800703e3 >> >> Anyone have any ideas? I am ready to tear them down and rebuild but I'd >> hate to pick up the same error again. I was going to cross-post this to the >> Patch Management list but couldn't handle the flood of OOF messages.... >> >> TIA, >> >> >> >> >> JRR >> >> >> >> >> >> >> >> >> >> >> >> > > > > > > This email and any files transmitted with it are confidential and intended > solely for the use of the individual or entity to whom they are addressed. > If you have received this email in error please notify the system manager. > This message contains confidential information and is intended only for the > individual named. If you are not the named addressee you should not > disseminate, distribute or copy this e-mail. > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
