WU on Win 2003 fails with 0x800706b5
in [Windows Update]
|
From: James W Troy on 16 Dec 2009 13:09 I attempt to run Windows Update on a Win 2003 SP2 server. The home page displays successfully. At that point, whether I click on "Express" or "Custom" the next page displayed says - "The website has encountered a problem and cannot display the page you are trying to view. [Error number: 0x800706b5]" I've searched the Internet for cases where this particular error is returned by WU, but none of them resolve the problem in our situation. Reviewing "WindowsUpdate.log" confirms that all WU components have the most current version (7.4.7600.226). Below, I have pasted in an excerpt of the "WindowsUpdate.log" entries that report the error we encounter - ===================================================== 2009-12-16 12:42:47:565 3232 1c3c COMAPI ------------- 2009-12-16 12:42:47:565 3232 1c3c COMAPI -- START -- COMAPI: Search [ClientId = WindowsUpdate] 2009-12-16 12:42:47:565 3232 1c3c COMAPI --------- 2009-12-16 12:42:47:581 856 5f4 Service WARNING: GetUserTokenFromSessionId failed with error 800706b5 for session 0 2009-12-16 12:42:47:581 3232 1c3c COMAPI WARNING: Unable to listen to self-update/shutdown event (hr=0X800706B5) 2009-12-16 12:42:47:581 3232 1c3c COMAPI WARNING: Unable to establish connection to the service. (hr=800706B5) 2009-12-16 12:42:47:581 3232 1c3c COMAPI - WARNING: Exit code = 0x800706B5 2009-12-16 12:42:47:581 3232 1c3c COMAPI --------- 2009-12-16 12:42:47:581 3232 1c3c COMAPI -- END -- COMAPI: Search [ClientId = <NULL>] 2009-12-16 12:42:47:581 3232 1c3c COMAPI ------------- 2009-12-16 12:42:47:581 3232 1c3c COMAPI FATAL: Unable to initiate asynchronous search, hr=800706B5 ===================================================== If you have any information that might help resolve the problem, please let me know. Thank you. James Troy
From: Robert Aldwinckle on 16 Dec 2009 23:07 "James W Troy" <JamesWTroy(a)discussions.microsoft.com> wrote in message news:477D1F57-D055-46C8-8D5E-50C6F1E5D3EB(a)microsoft.com... >I attempt to run Windows Update on a Win 2003 SP2 server. The home page > displays successfully. At that point, whether I click on "Express" or > "Custom" the next page displayed says - > > "The website has encountered a problem and cannot display the page you are > trying to view. [Error number: 0x800706b5]" > > > I've searched the Internet for cases where this particular error is returned > by WU, but none of them resolve the problem in our situation. <cmd_output OS="XPsp3"> E:\>set /a c = 0x6B5 1717 E:\>net helpmsg %c% The interface is unknown. </cmd_output> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.windowsupdate&mid=21c2389c-18ef-4721-b2dd-09fc9cc395dd&sloc=en-us (Alt-7 search in this newsgroup for 1717 ) --- > > Reviewing "WindowsUpdate.log" confirms that all WU components have the most > current version (7.4.7600.226). > > Below, I have pasted in an excerpt of the "WindowsUpdate.log" entries that > report the error we encounter - > > ===================================================== > > 2009-12-16 12:42:47:565 3232 1c3c COMAPI ------------- > 2009-12-16 12:42:47:565 3232 1c3c COMAPI -- START -- COMAPI: Search > [ClientId = WindowsUpdate] > 2009-12-16 12:42:47:565 3232 1c3c COMAPI --------- > 2009-12-16 12:42:47:581 856 5f4 Service WARNING: GetUserTokenFromSessionId > failed with error 800706b5 for session 0 > 2009-12-16 12:42:47:581 3232 1c3c COMAPI WARNING: Unable to listen to > self-update/shutdown event (hr=0X800706B5) > 2009-12-16 12:42:47:581 3232 1c3c COMAPI WARNING: Unable to establish > connection to the service. (hr=800706B5) > 2009-12-16 12:42:47:581 3232 1c3c COMAPI - WARNING: Exit code = 0x800706B5 > 2009-12-16 12:42:47:581 3232 1c3c COMAPI --------- > 2009-12-16 12:42:47:581 3232 1c3c COMAPI -- END -- COMAPI: Search > [ClientId = <NULL>] > 2009-12-16 12:42:47:581 3232 1c3c COMAPI ------------- > 2009-12-16 12:42:47:581 3232 1c3c COMAPI FATAL: Unable to initiate > asynchronous search, hr=800706B5 > > ===================================================== > > If you have any information that might help resolve the problem, please let > me know. > > Thank you. > > James Troy >
From: James W Troy on 17 Dec 2009 12:00 Thank you for your reply, Robert. Per your suggestion, I reviewed the discussion thread at - http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.windowsupdate&mid=21c2389c-18ef-4721-b2dd-09fc9cc395dd&sloc=en-us Ultimately, that discussion recommends downloading and running a utility called "AU Check" (or "AU Reset") from Codeplex. The discussion even includes this URL for the utility - http://www.codeplex.com/aureset/Release/ProjectReleases.aspx?ReleaseId=17263 However, that URL does not work - it simply puts you on the Codeplex homepage. Searching Codeplex for "au check" or "au reset" or for the actual executable (au_check_v78a_codeplex.exe) does not yield anything of value. Using Google to search for the executable only yields references to download from Codeplex. It appears that the utility has been withdrawn, perhaps due to some problems. Apparently that utility does something similar to the procedure Microsoft describes here - http://support.microsoft.com/kb/931852 I tried that procedure but it did not resolve the issue I reported. James Troy
From: James W Troy on 17 Dec 2009 12:59 I downloaded the latest version of the Windows Update agent from - http://support.microsoft.com/kb/949104/ The executable is called "windowsupdateagent30-x86.exe". I ran it with the "/wuforce" command-line option to force the reinstallation of Windows Update. This solved the 0x800706b5 problem and WU was able to download and attempt to install updates. Unfortunately, the attempted installations of updates all fail. That was the original problem we had (prior to getting 0x800706b5). So we resolved one problem and now face a different one. )-: James Troy
From: PA Bear [MS MVP] on 17 Dec 2009 14:55 To keep track of things, it helps immensely if you quote all of the previous message(s) in your replies to the newsgroup. Thank you. Thread history: http://groups.google.com/group/microsoft.public.windowsupdate/browse_frm/thread/94e44b5046cc0589 What error are the failures throwing now, James? ============= How to troubleshoot Windows Update, Microsoft Update, and Windows Server Update Services installation issues: http://support.microsoft.com/kb/906602 1. See the "Need more help? Tell us what problem you are having" section of http://support.microsoft.com/ph/6527 2. You cannot install some updates or programs http://support.microsoft.com/kb/822798 3a. Check your WindowsUpdate.log (%windir%\WindowsUpdate.log) for errors associated with the download/install. How to read the WindowsUpdate.log file http://support.microsoft.com/kb/902093 3b. Compare errors to those listed here: http://www.bleepingcomputer.com/blogs/mowgreen/index.php?showentry=1122 and/or go to http://windowsupdate.microsoft.com > click on Help and Support link in left pane > Solve problems on your own. Start a free Windows Update support incident request: https://support.microsoft.com/oas/default.aspx?gprid=6527 Support for Windows Update: http://support.microsoft.com/gp/wusupport -- ~Robear Dyer (PA Bear) MS MVP-IE, Mail, Security, Windows Client - since 2002 www.banthecheck.com James W Troy wrote: > I downloaded the latest version of the Windows Update agent from - > > http://support.microsoft.com/kb/949104/ > > The executable is called "windowsupdateagent30-x86.exe". > > I ran it with the "/wuforce" command-line option to force the > reinstallation of Windows Update. > > This solved the 0x800706b5 problem and WU was able to download and attempt > to install updates. > > Unfortunately, the attempted installations of updates all fail. That was > the original problem we had (prior to getting 0x800706b5). > > So we resolved one problem and now face a different one. )-: > > James Troy
|
Pages: 1 Prev: "WindowsUpdate_84BB0001" "WindowsUpdate_dt000" Next: 0x8024401B |