Good Morning All,

I've got a WSUS 3.2 server that is not a DC.  Every few days it crashes with 13042, 12002, 12032, 12022, 12042, 12052, 364, 10032.  I've verified the Virtual Directory, registry, and directory permissions as outlined inAppendix C andAppendix D .  This is a clean install on a recently rebuilt server (2003 Standard). 

Anyone have any ideas?

Thanks!

I recently started deploying drivers through WSUS and I have a question or two. After importing the update from the Microsoft Catalog the clients see the driver as needed.  However, they will not automatically install the driver unless I log on as an administrator.

I see the following warning when I import the update from the MS Catalog "This update requires that the user interact with it, and may not be installable without additional administrator intervention."

I don't see that warning for my Vista and Windows 7 machines.  Why can't I automatically install these drivers.

Oh these are video drivers in case you are wondering.

Thanks!

Friends,

I have Windows Server 2008 R2 and i raise WSUS .... after that i can see workstation on ALL COMPUTERS UNASSIGNED field but i can not move this workstation to WORKSTATION field and can not also change membership ... 

I have this warning also.

Source Windows Server Update Services

Event ID 10021

Could you tell me what i should to do ?

Regards,

Giorgi

Hi,
Is there any possibility to create a custom Updates View based on a KB list?
For example: A view that has only KB1, KB4, KB7, KB8, KB9.

I have seen that the View are keep in the WSUS MMC in a binary form! :( (please correct me if i`m wrong)

Hi

I have a question. Is is possible to make WU get update from a WSUS server other than ssManagedServer option?
ssManagedServer option requires setting up client computers with GPO and all.

What i want to achieve is to use 'ssOthers' option and let client specify the server url. But from documentation the server url
is get only property ... is there a work around for that?

Thanks,
umibau

Hello I installed WSUS on Windows 2012 std, my problem and this, in the configurations I decided I had to download updates on a remote path like this: \ \ server \ wsus. I gave permissions to full control to user domain that is connected to my win2012. I also tried to insert a txt file remotely on this path network and works
Now I get these errors in the event log:
EventID: 12072
WSUS content directory is not accessible.
System.UnauthorizedAccessException: Access to the path '\ \ server \ WSUS \ WSUSContent \ anonymousCheckFile.txt' denied.
 at System.IO.__Error.WinIOError (Int32 errorCode, String maybeFullPath)
 at System.IO.FileStream.Init (String path, FileMode mode, FileAccess access, Int32 rights, Boolean userights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkhost)
 at System.IO.FileStream .. ctor (String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy)
 at System.IO.FileStream .. ctor (String path, FileMode mode, FileAccess access, FileShare share)
 in System.IO.FileInfo.Open (FileMode mode, FileAccess access, FileShare share)
 in type, HealthEventLogger logger)
EventID: 10032
The server fails to download some updates.
EventID: 7032
Unable to connect to the WSUS server via Remote API from the WSUS administration console.
Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services service.
System.Net.WebException - The operation timed out. SourceSystem.Windows.Forms
Stack Trace:
 in System.Windows.Forms.Control.MarshaledInvoke (Control caller, Delegate method, Object [] args, Boolean synchronous)
 in System.Windows.Forms.Control.Invoke (Delegate method, Object [] args)
 in sender, and PerformCleanupCompletedEventArgs)
On what?

Folks,

OS: Windows server 2012 std,VM running in Hyper-V, WSUS version 6.2.9200.16384, new build

Having problems downloading updates when I use Proxy server in WSUS but Sychronization succeds. my proxy account details are correct in WSUS and able to access internet via internet explorer with the proxy account I'm using.

Trigers event ID 10032: The server is failing to download some updates.

Please note: When I by pass the proxy, WSUS server will download the updates successfully.

I have googled up this issue, have not foudn right solution yet.

Look forward to hear from you...!!!

With best regards Siddarth Sajjan : Disclaimer: This posting is provided "as is" with no warranties, and confers no rights. http://siddarthsajjantechnotes.blogspot.co.nz/

Hi, i have 300 computers synchronized on my WSUS server and receiving updates.

however around 50 computers have not reported status for more than 30 days.

i have done a GPupdate / force on the computer and checked the GPresult to make sure they are receiving the GP, which they are.

is there a way to get the computer to update its status with WSUS?

thanks

hi all,

i configured the WSUS server as the guide said in this official web page
http://technet.microsoft.com/en-us/library/hh852346.aspx
but i didn't get any WSUS clients on the Computers page in the WSUS Administration Console and this is a part of the logging messages from the WindowsUpdate.log WSUS Client's file
=======================================================================================
2013-05-02    09:16:46:639     872    bcc    AU    Triggering AU detection through DetectNow API
2013-05-02    09:16:46:639     872    bcc    AU    Triggering Online detection (non-interactive)
2013-05-02    09:16:46:639     872    654    AU    #############
2013-05-02    09:16:46:639     872    654    AU    ## START ##  AU: Search for updates
2013-05-02    09:16:46:639     872    654    AU    #########
2013-05-02    09:16:46:639     872    654    AU    <<## SUBMITTED ## AU: Search for updates [CallId = {7A04B23D-6794-40EA-94BB-DFFAF5308405}]
2013-05-02    09:16:46:639     872    718    Agent    *************
2013-05-02    09:16:46:639     872    718    Agent    ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
2013-05-02    09:16:46:639     872    718    Agent    *********
2013-05-02    09:16:46:639     872    718    Agent      * Online = Yes; Ignore download priority = No
2013-05-02    09:16:46:639     872    718    Agent      * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2013-05-02    09:16:46:639     872    718    Agent      * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2013-05-02    09:16:46:639     872    718    Agent      * Search Scope = {Machine}
2013-05-02    09:16:46:670     872    718    Setup    Checking for agent SelfUpdate
2013-05-02    09:16:46:670     872    718    Setup    Client version: Core: 7.6.7600.256  Aux: 7.6.7600.256
2013-05-02    09:16:46:670     872    718    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2013-05-02    09:16:46:670     872    718    Misc     Microsoft signed: Yes
2013-05-02    09:16:46:670     872    718    Misc    WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190194
2013-05-02    09:16:46:670     872    718    Misc    WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190194
2013-05-02    09:16:46:670     872    718    Misc    WARNING: DownloadFileInternal failed for http://SUS/selfupdate/wuident.cab: error 0x80190194
2013-05-02    09:16:46:670     872    718    Setup    WARNING: SelfUpdate check failed to download package information, error = 0x80244019
2013-05-02    09:16:46:670     872    718    Setup    FATAL: SelfUpdate check failed, err = 0x80244019
2013-05-02    09:16:46:670     872    718    Agent      * WARNING: Skipping scan, self-update check returned 0x80244019
2013-05-02    09:16:46:670     872    718    Agent      * WARNING: Exit code = 0x80244019
2013-05-02    09:16:46:670     872    718    Agent    *********
2013-05-02    09:16:46:670     872    718    Agent    **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
2013-05-02    09:16:46:670     872    718    Agent    *************
2013-05-02    09:16:46:670     872    718    Agent    WARNING: WU client failed Searching for update with error 0x80244019
2013-05-02    09:16:46:670     872    610    AU    >>##  RESUMED  ## AU: Search for updates [CallId = {7A04B23D-6794-40EA-94BB-DFFAF5308405}]
2013-05-02    09:16:46:670     872    610    AU      # WARNING: Search callback failed, result = 0x80244019
2013-05-02    09:16:46:670     872    610    AU      # WARNING: Failed to find updates with error code 80244019
2013-05-02    09:16:46:670     872    610    AU    #########
2013-05-02    09:16:46:670     872    610    AU    ##  END  ##  AU: Search for updates [CallId = {7A04B23D-6794-40EA-94BB-DFFAF5308405}]
2013-05-02    09:16:46:670     872    610    AU    #############
2013-05-02    09:16:46:670     872    610    AU    Successfully wrote event for AU health state:0
2013-05-02    09:16:46:670     872    610    AU    AU setting next detection timeout to 2013-05-02 13:16:46
2013-05-02    09:16:46:670     872    610    AU    Setting AU scheduled install time to 2013-05-02 14:00:00
2013-05-02    09:16:46:670     872    610    AU    Successfully wrote event for AU health state:0
2013-05-02    09:16:46:670     872    610    AU    Successfully wrote event for AU health state:0
2013-05-02    09:16:51:672     872    718    Report    REPORT EVENT: {DB9D3585-8234-48E3-B133-E2B3C8CECA87}    2013-05-02 09:16:46:670+0100    1   148    101    {D67661EB-2423-451D-BF5D-13199E37DF28}    1    80244019    SelfUpdate    Failure    Software Synchronization    Windows Update Client failed to detect with error 0x80244019.
2013-05-02    09:16:51:672     872    718    Report    CWERReporter::HandleEvents - WER report upload completed with status 0x8
2013-05-02    09:16:51:672     872    718    Report    WER Report sent: 7.6.7600.256 0x80244019 D67661EB-2423-451D-BF5D-13199E37DF28 Scan 101 Managed
2013-05-02    09:16:51:672     872    718    Report    CWERReporter finishing event handling. (00000000)

==============================================================================

can anyone tell me how to fix this problem ?
Thanks.

I have a standalone 2008 R2 x32 server that I’m building. I want it to run WSUS but any time I try to install it (using theWSUS30-KB972455-x86.exe installer), I am told that IIS or IIS Server Role needs to be installed.

I’ve added the IIS Role , selecting the components listed in the Step-By-Step guide, which went fine, but still get the same error from the WSUS installer.

I found theWindows6.0-KB940518-x86.msu update that adds WSUS as a Role in Server 2008 and successfully run that. I removed IIS then added the WSUS Role in Server Manager. This prompted me to add the IIS Role again, which was what I wanted to happen. I okayed that and the correct components were selected automatically.

At this point IIS was added successfully but WSUS wasn’t, which was, again, what I expected as there was no way to point to an installer for WSUS. I then ran the WSUS installer again, and got the same error. Namely that IIS needs to be installed.

All installs and uninstalls were followed by reboots, so that's not an issue.

I’ve looked through the forum here back to 2008 and found no-one having the same problem, so now I’m looking for some much needed advice on how to get around this.

Thanks

When trying to complete the post-installation tasks Windows Server Update Services 4.0 (Windows Server 2012 Role) cannot seem to complete them. This is a member server with Default Roles, WDS, NAP, IIS, and (attempting) WSUS. It is intended to be a Network Management Server.

I get a variety of errors and it appears to be related to the attempt to sync with the Windows Update server on the Internet. I also see an error indicating it does not have permissions to the %Install Directory%\Update Services folder. I looked at the security permissions and the folder I designated to use for the update cache had my account and CREATOR/OWNER permissions invisible on the main tab. Going into advanced, I was able to see permissions and grant full control to that directory.

The 'Update Services' directory was owned by Trusted Installer and I observed the same condition with the permissions invisible in the main dialog and visible in the advanced dialog. I was unable to modify those since I was not the owner.

I have uninstalled the Role Service and Re-installed, with the same results. I did the same thing again but deleted all the folders I could find used by the Service, and no help there either.

When I attempt the post-installation tasks my error logs come up blank now? There are some things recorded in the event logs too if anyone wants to see them. Here is one of the error logs from an early attempt at this Role Install:

2013-02-05 15:54:59  Setting WSUSService to autostart...
2013-02-05 15:54:59  WSUSService is set to autostart.
2013-02-05 15:54:59  Starting WSUSService...
2013-02-05 15:54:59  WSUSService is now started.
2013-02-05 15:54:59  Importing default detectoids.
2013-02-05 15:54:59  Importing CriticalUpdates.xml...
2013-02-05 15:57:29  ImportDefaultDetectoids failed. Exception: System.Data.SqlClient.SqlException (0x80131904): Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
Warning: The join order has been enforced because a local join hint is used. ---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out
   at Microsoft.UpdateServices.DatabaseAccess.DBConnection.DrainObsoleteConnections(SqlException e)
   at Microsoft.UpdateServices.DatabaseAccess.DBConnection.ExecuteCommandNoResult()
   at Microsoft.UpdateServices.Internal.DatabaseAccess.CommonDataAccess.ExecuteSPImportUpdate(Int32 upstreamServerLocalId, String xmlUpdateBlob, Byte[] xmlUpdateBlobCompressed, Int32& localRevisionId)
   at Microsoft.UpdateServices.Internal.DatabaseAccess.CommonDataAccess.ImportUpdate(Int32 ussRevLocalId, String xmlUpdateBlob, Byte[] xmlUpdateBlobCompressed, String xmlSdpBlob, Int32& localRevisionId)
   at Microsoft.UpdateServices.Internal.DatabaseAccess.CommonDataAccess.ImportUpdate(Int32 ussRevLocalId, String xmlUpdateBlob, Byte[] xmlUpdateBlobCompressed)
   at Microsoft.UpdateServices.Setup.StartServer.StartServer.ImportDefaultDetectoids()
ClientConnectionId:8cfc8c46-eba0-4c41-bb2a-6930f8e68ece
2013-02-05 15:57:29  StartServer encountered errors. Exception=Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
Warning: The join order has been enforced because a local join hint is used.
2013-02-05 15:57:29  Microsoft.UpdateServices.Administration.CommandException: Failed to start and configure the WSUS service
   at Microsoft.UpdateServices.Administration.PostInstall.Run()
   at Microsoft.UpdateServices.Administration.PostInstall.Execute(String[] arguments)

I recently installed WSUS on Windows server 2008 Ent R2, I followed the best practices from MS. The server has direct connectivity to internet and there is no deny rule in place between server and internet . I am getting below error while try to sync. During initial setup also this dodnt sync . I feel like we have to do some configuration changes to IIS to make this work.

WebException: The request failed with the error message:
--
<html><head><title>Object moved</title></head><body>
<h2>Object moved to <a href="%2fmicrosoftupdate%2fv6%2ferrorinformation.aspx%3ferror%3d15">here</a>.</h2>
</body></html>

--.
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy.GetAuthConfig()
   at Microsoft.UpdateServices.ServerSync.ServerSyncLib.InternetGetServerAuthConfig(ServerSyncProxy proxy, WebServiceCommunicationHelper webServiceHelper)
   at Microsoft.UpdateServices.ServerSync.ServerSyncLib.Authenticate(AuthorizationManager authorizationManager, Boolean checkExpiration, ServerSyncProxy proxy, Cookie cookie, WebServiceCommunicationHelper webServiceHelper)
   at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.SyncConfigUpdatesFromUSS()
   at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect)

I am currently in the same situation as many others; I have imported IE10 via the Windows Update Catalog, and am unable to install it from WSUS on any machine.  I am able to install IE10 by checking directly online for updates, and by manually installing from the executable.

Some seemingly relevant information I have found:

Importing the IE10 packages (which added up to roughly 600MB) occurred almost instantaneously; there was no "download time".

After importing, nothing seemed to have synchronized to the WSUS server.  I manually synchronized, and nothing new was downloaded.

Although the update appears in the console, and the update appears to the client from WSUS, and the client is able to start the update process, the files do not seem to actually exist (as far as I can tell).

I have tried installing to Windows 7(32), Windows 7(64), and Windows 2008R2(64).  All of the platforms I have tried are able to install IE10 directly from Microsoft through Automatic Updates.

I have received the following error codes:

IE10_main.log

00:00.000: ====================================================================
00:00.219: Started: 2013/04/14 (Y/M/D) 01:00:49.057 (local)
00:00.250: Time Format in this log: MM:ss.mmm (minutes:seconds.milliseconds)
00:00.266: Command line: "C:\Windows\SoftwareDistribution\Download\Install\WU-IE10-Windows7-x86.exe" /WSUS
00:00.297: INFO:    Setup installer for Internet Explorer: 10.0.9200.16521
00:00.375: INFO:    Previous version of Internet Explorer: 9.0.8112.16476
00:00.391: INFO:    Checking if iexplore.exe's current version is between 10.0.8100.0...
00:00.422: INFO:    ...and 10.1.0.0...
00:00.453: INFO:    Maximum version on which to run IEAK branding is: 10.1.0.0...
00:00.485: INFO:    iexplore.exe version check success. Install can proceed.
00:00.500: INFO:    Operating System: Windows Workstation: 6.1.7601 (Service Pack 1)
00:00.563: INFO:    Trying to extract ID: SetupDownloadList.txt (0) as "SetupDownloadList.txt"
00:00.610: INFO:    Trying to extract ID: HardwareBlockingList.xml (0) as "HardwareBlockingList.xml"
00:00.641: INFO:    Trying to extract ID: 6006 (0) as "IE10-neutral.Extracted.cab"
00:00.813: INFO:    Trying to extract ID: 5501 (1033) as "Spelling_en.msu"
00:00.953: INFO:    Extracted Spelling dictionary for en to C:\Windows\TEMP\IE14D3E.tmp\Spelling_en.msu.
00:01.016: INFO:    Trying to extract ID: 5502 (1033) as "Hyphenation_en.msu"
00:01.047: INFO:    Extracted Hyphenation dictionary for en to C:\Windows\TEMP\IE14D3E.tmp\Hyphenation_en.msu.
00:01.094: INFO:    Trying to extract ID: 6128 (1033) as "IE10-support.cab"
00:02.219: INFO:    Launched program to check hardware: "C:\Windows\TEMP\IE14D3E.tmp\IE10-SUPPORT\IEXPLORE.EXE" /CheckHardware "C:\Windows\TEMP\IE14D3E.tmp\HardwareBlockingList.xml"
00:03.328: INFO:    Hardware support check succeeded. Installation will continue.
00:03.406: INFO:    Windows 7 operating system detected.
00:03.469: INFO:    Service pack major: 1
00:03.516: INFO:    Service pack minor: 0
00:03.531: INFO:    Service pack name:  Service Pack 1
00:03.563: WARNING: Checking version for C:\Windows\System32\api-ms-win-downlevel-user32-l1-1-0.dll.  The file does not exist.
00:03.578: INFO:    Version Check for (KB2639308) of C:\Windows\System32\Ntoskrnl.exe: 6.1.7601.18113 >= 6.1.7601.17727 (True)
00:03.656: INFO:    Version Check for (KB2533623) of C:\Windows\System32\api-ms-win-security-base-l1-1-0.dll: 6.1.7601.18015 >= 6.1.7601.17617 (True)
00:03.688: INFO:    Version Check for (KB2731771) of C:\Windows\System32\kernel32.dll: 6.1.7601.18015 >= 6.1.7601.17932 (True)
00:03.750: INFO:    Checking for correct version of C:\Windows\Fonts\segoeui.ttf.
00:03.875: INFO:    Version Check for (KB2786081) of C:\Windows\System32\taskhost.exe: 6.1.7601.18010 >= 6.1.7601.18010 (True)
00:26.656: INFO:    Setup exit code: 0x00009C47 (40007) - Required updates failed to download.
00:26.844: INFO:    Scheduling upload to IE SQM server: http://sqm.microsoft.com/sqm/ie/sqmserver.dll
00:31.922: ERROR:   SQM Upload failed while uploading "C:\Windows\system32\config\systemprofile\AppData\Local\Microsoft\Windows\Temporary Internet Files\SQM\iesqmdata_setup0.sqm" with error: 2147500036
00:32.031: INFO:    Cleaning up temporary files in: C:\Windows\TEMP\IE14D3E.tmp
00:32.156: INFO:    Unable to remove directory C:\Windows\TEMP\IE14D3E.tmp, marking for deletion on reboot.
00:32.281: INFO:    Released Internet Explorer Installer Mutex
00:00.000: ====================================================================

WindowsUpdate.log

2013-04-14    01:00:12:869    1180    c90    AU    #############
2013-04-14    01:00:12:869    1180    c90    AU    ## START ##  AU: Search for updates
2013-04-14    01:00:12:869    1180    c90    AU    #########
2013-04-14    01:00:12:869    1180    c90    AU    <<## SUBMITTED ## AU: Search for updates [CallId = {58A7FACD-FF0E-49B7-BDF1-656D17B98938}]
2013-04-14    01:00:12:869    1180    4f8    Agent    *************
2013-04-14    01:00:12:869    1180    4f8    Agent    ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
2013-04-14    01:00:12:869    1180    4f8    Agent    *********
2013-04-14    01:00:12:869    1180    4f8    Agent      * Online = Yes; Ignore download priority = No
2013-04-14    01:00:12:869    1180    4f8    Agent      * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2013-04-14    01:00:12:869    1180    4f8    Agent      * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2013-04-14    01:00:12:869    1180    4f8    Agent      * Search Scope = {Machine}
2013-04-14    01:00:12:869    1180    4f8    Setup    Checking for agent SelfUpdate
2013-04-14    01:00:12:885    1180    4f8    Setup    Client version: Core: 7.6.7600.256  Aux: 7.6.7600.256
2013-04-14    01:00:12:916    1180    4f8    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2013-04-14    01:00:13:697    1180    4f8    Misc     Microsoft signed: Yes
2013-04-14    01:00:17:494    1180    4f8    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2013-04-14    01:00:17:526    1180    4f8    Misc     Microsoft signed: Yes
2013-04-14    01:00:17:572    1180    4f8    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2013-04-14    01:00:17:619    1180    4f8    Misc     Microsoft signed: Yes
2013-04-14    01:00:17:619    1180    4f8    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2013-04-14    01:00:17:635    1180    4f8    Misc     Microsoft signed: Yes
2013-04-14    01:00:17:713    1180    4f8    Setup    Determining whether a new setup handler needs to be downloaded
2013-04-14    01:00:17:729    1180    4f8    Setup    SelfUpdate handler is not found.  It will be downloaded
2013-04-14    01:00:17:729    1180    4f8    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.6.7600.256"
2013-04-14    01:00:17:729    1180    4f8    Setup    Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.6.7600.256" is already installed.
2013-04-14    01:00:17:729    1180    4f8    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256"
2013-04-14    01:00:17:760    1180    4f8    Setup    Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256" is already installed.
2013-04-14    01:00:17:760    1180    4f8    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256"
2013-04-14    01:00:17:807    1180    4f8    Setup    Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256" is already installed.
2013-04-14    01:00:17:807    1180    4f8    Setup    SelfUpdate check completed.  SelfUpdate is NOT required.
2013-04-14    01:00:18:776    1180    4f8    PT    +++++++++++  PT: Synchronizing server updates  +++++++++++
2013-04-14    01:00:18:776    1180    4f8    PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://*****:8530/ClientWebService/client.asmx
2013-04-14    01:00:19:432    1180    4f8    PT    WARNING: Cached cookie has expired or new PID is available
2013-04-14    01:00:19:432    1180    4f8    PT    Initializing simple targeting cookie, clientId = a6aa9dc9-dc78-4bcb-b23b-de6d377f3cb2, target group = Testbed, DNS name = ****.****.com
2013-04-14    01:00:19:432    1180    4f8    PT      Server URL = http://*****:8530/SimpleAuthWebService/SimpleAuth.asmx
2013-04-14    01:00:27:213    1180    4f8    PT    +++++++++++  PT: Synchronizing extended update info  +++++++++++
2013-04-14    01:00:27:213    1180    4f8    PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://*****:8530/ClientWebService/client.asmx
2013-04-14    01:00:28:229    1180    4f8    Agent      * Added update {87E13ECB-C669-43BE-9E2A-01E567285031}.203 to search result
2013-04-14    01:00:28:229    1180    4f8    Agent      * Found 1 updates and 69 categories in search; evaluated appl. rules of 756 out of 1007 deployed entities
2013-04-14    01:00:28:260    1180    4f8    Agent    *********
2013-04-14    01:00:28:260    1180    4f8    Agent    **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
2013-04-14    01:00:28:260    1180    4f8    Agent    *************
2013-04-14    01:00:28:291    1180    3f0    AU    >>##  RESUMED  ## AU: Search for updates [CallId = {58A7FACD-FF0E-49B7-BDF1-656D17B98938}]
2013-04-14    01:00:28:291    1180    3f0    AU      # 1 updates detected
2013-04-14    01:00:28:291    1180    3f0    AU    #########
2013-04-14    01:00:28:291    1180    3f0    AU    ##  END  ##  AU: Search for updates [CallId = {58A7FACD-FF0E-49B7-BDF1-656D17B98938}]
2013-04-14    01:00:28:291    1180    3f0    AU    #############
2013-04-14    01:00:28:307    1180    3f0    AU    Successfully wrote event for AU health state:0
2013-04-14    01:00:28:307    1180    3f0    AU    Featured notifications is disabled.
2013-04-14    01:00:28:307    1180    3f0    AU    AU setting next detection timeout to 2013-04-15 03:52:00
2013-04-14    01:00:28:323    1180    3f0    AU    Successfully wrote event for AU health state:0
2013-04-14    01:00:33:229    1180    4f8    Report    REPORT EVENT: {94640381-460D-4C10-8325-77979804D8A8}    2013-04-14 01:00:28:229-0600    1   147    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Software Synchronization    Windows Update Client successfully detected 1 updates.
2013-04-14    01:00:33:229    1180    4f8    Report    REPORT EVENT: {FC1B6FAB-E6F1-40E2-B12C-8C3E192032BD}    2013-04-14 01:00:28:260-0600    1   156    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Pre-Deployment Check    Reporting client status.
2013-04-14    01:00:33:229    1180    4f8    Report    CWERReporter finishing event handling. (00000000)
2013-04-14    01:00:36:260    1180    a58    DnldMgr    Preparing update for install, updateId = {497DC29B-53B4-437B-81C1-92F0E5946E4B}.203.
2013-04-14    01:00:36:760     756    804    Misc    ===========  Logging initialized (build: 7.6.7600.256, tz: -0600)  ===========
2013-04-14    01:00:36:760     756    804    Misc      = Process: C:\Windows\system32\wuauclt.exe
2013-04-14    01:00:36:760     756    804    Misc      = Module: C:\Windows\system32\wuaueng.dll
2013-04-14    01:00:36:760     756    804    Handler    :::::::::::::
2013-04-14    01:00:36:760     756    804    Handler    :: START ::  Handler: Command Line Install
2013-04-14    01:00:36:760     756    804    Handler    :::::::::
2013-04-14    01:00:36:760     756    804    Handler      : Updates to install = 1
2013-04-14    01:00:42:338     756    804    Handler      : Command line install completed. Return code = 0x00000000, Result = Succeeded, Reboot required = false
2013-04-14    01:00:42:338     756    804    Handler    :::::::::
2013-04-14    01:00:42:338     756    804    Handler    ::  END  ::  Handler: Command Line Install
2013-04-14    01:00:42:338     756    804    Handler    :::::::::::::
2013-04-14    01:00:42:370    1180    a58    DnldMgr    Preparing update for install, updateId = {4A2D8132-7DA3-4B00-A37C-C004B77BA4CB}.203.
2013-04-14    01:00:42:635     756    804    Handler    :::::::::::::
2013-04-14    01:00:42:635     756    804    Handler    :: START ::  Handler: Command Line Install
2013-04-14    01:00:42:635     756    804    Handler    :::::::::
2013-04-14    01:00:42:635     756    804    Handler      : Updates to install = 1
2013-04-14    01:00:44:198     756    804    Handler      : Command line install completed. Return code = 0x00000000, Result = Succeeded, Reboot required = false
2013-04-14    01:00:44:198     756    804    Handler    :::::::::
2013-04-14    01:00:44:198     756    804    Handler    ::  END  ::  Handler: Command Line Install
2013-04-14    01:00:44:198     756    804    Handler    :::::::::::::
2013-04-14    01:00:44:198    1180    a58    DnldMgr    Preparing update for install, updateId = {F50DB706-BA83-4247-800D-89BFE2FBCBBF}.203.
2013-04-14    01:00:44:307     756    804    Handler    :::::::::::::
2013-04-14    01:00:44:307     756    804    Handler    :: START ::  Handler: Command Line Install
2013-04-14    01:00:44:307     756    804    Handler    :::::::::
2013-04-14    01:00:44:307     756    804    Handler      : Updates to install = 1
2013-04-14    01:00:45:229     756    804    Handler      : Command line install completed. Return code = 0x00000000, Result = Succeeded, Reboot required = false
2013-04-14    01:00:45:229     756    804    Handler    :::::::::
2013-04-14    01:00:45:229     756    804    Handler    ::  END  ::  Handler: Command Line Install
2013-04-14    01:00:45:229     756    804    Handler    :::::::::::::
2013-04-14    01:00:45:245    1180    a58    DnldMgr    Preparing update for install, updateId = {2C886B27-09D4-4DE3-8BBC-1EB5CD5BC76A}.203.
2013-04-14    01:00:45:276     756    804    Handler    :::::::::::::
2013-04-14    01:00:45:276     756    804    Handler    :: START ::  Handler: Command Line Install
2013-04-14    01:00:45:276     756    804    Handler    :::::::::
2013-04-14    01:00:45:276     756    804    Handler      : Updates to install = 1
2013-04-14    01:00:45:932     756    804    Handler      : Command line install completed. Return code = 0x00000000, Result = Succeeded, Reboot required = false
2013-04-14    01:00:45:932     756    804    Handler    :::::::::
2013-04-14    01:00:45:932     756    804    Handler    ::  END  ::  Handler: Command Line Install
2013-04-14    01:00:45:932     756    804    Handler    :::::::::::::
2013-04-14    01:00:45:948    1180    a58    DnldMgr    Preparing update for install, updateId = {516C5430-1639-460B-A8D8-53BA47211610}.203.
2013-04-14    01:00:45:963     756    804    Handler    :::::::::::::
2013-04-14    01:00:45:963     756    804    Handler    :: START ::  Handler: Command Line Install
2013-04-14    01:00:45:963     756    804    Handler    :::::::::
2013-04-14    01:00:45:963     756    804    Handler      : Updates to install = 1
2013-04-14    01:00:46:463     756    804    Handler      : Command line install completed. Return code = 0x00000000, Result = Succeeded, Reboot required = false
2013-04-14    01:00:46:463     756    804    Handler    :::::::::
2013-04-14    01:00:46:463     756    804    Handler    ::  END  ::  Handler: Command Line Install
2013-04-14    01:00:46:463     756    804    Handler    :::::::::::::
2013-04-14    01:00:46:463    1180    a58    DnldMgr    Preparing update for install, updateId = {822B837F-FFF0-44A8-9244-1AA8A0D77F7C}.203.
2013-04-14    01:00:47:416     756    804    Handler    :::::::::::::
2013-04-14    01:00:47:416     756    804    Handler    :: START ::  Handler: Command Line Install
2013-04-14    01:00:47:416     756    804    Handler    :::::::::
2013-04-14    01:00:47:416     756    804    Handler      : Updates to install = 1
2013-04-14    01:01:21:464     756    804    Handler      : WARNING: Command line install completed. Return code = 0x00009c47, Result = Failed, Reboot required = false
2013-04-14    01:01:21:464    1180    3f0    AU    >>##  RESUMED  ## AU: Installing update [UpdateId = {87E13ECB-C669-43BE-9E2A-01E567285031}]
2013-04-14    01:01:21:464     756    804    Handler      : WARNING: Exit code = 0x8024200B
2013-04-14    01:01:21:464    1180    3f0    AU      # WARNING: Install failed, error = 0x80070643 / 0x00009C47
2013-04-14    01:01:21:464     756    804    Handler    :::::::::
2013-04-14    01:01:21:464     756    804    Handler    ::  END  ::  Handler: Command Line Install
2013-04-14    01:01:21:464     756    804    Handler    :::::::::::::
2013-04-14    01:01:21:510    1180    a58    Agent    *********
2013-04-14    01:01:21:510    1180    3f0    AU    Install call completed.
2013-04-14    01:01:21:510    1180    a58    Agent    **  END  **  Agent: Installing updates [CallerId = AutomaticUpdates]
2013-04-14    01:01:21:510    1180    3f0    AU      # WARNING: Install call completed, reboot required = No, error = 0x00000000
2013-04-14    01:01:21:510    1180    a58    Agent    *************
2013-04-14    01:01:21:510    1180    3f0    AU    #########
2013-04-14    01:01:21:510    1180    3f0    AU    ##  END  ##  AU: Installing updates [CallId = {612023CC-6538-4722-9742-5FD88A9CB328}]
2013-04-14    01:01:21:510    1180    3f0    AU    #############
2013-04-14    01:01:21:510    1180    3f0    AU    Install complete for all calls, reboot NOT needed
2013-04-14    01:01:21:510    1180    3f0    AU    Setting AU scheduled install time to 2013-04-15 07:00:00
2013-04-14    01:01:21:510    1180    3f0    AU    Successfully wrote event for AU health state:0
2013-04-14    01:01:21:510    1180    3f0    AU    Successfully wrote event for AU health state:0
2013-04-14    01:01:21:510    1180    3f0    AU    Triggering Offline detection (non-interactive)
2013-04-14    01:01:21:510    1180    c90    AU    #############
2013-04-14    01:01:21:510    1180    c90    AU    ## START ##  AU: Search for updates
2013-04-14    01:01:21:510    1180    c90    AU    #########
2013-04-14    01:01:21:526    1180    c90    AU    <<## SUBMITTED ## AU: Search for updates [CallId = {4CC39288-6E0C-4F19-ADEC-FAC9B9B68424}]
2013-04-14    01:01:21:526    1180    4f8    Agent    *************
2013-04-14    01:01:21:526    1180    4f8    Agent    ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
2013-04-14    01:01:21:526    1180    4f8    Agent    *********
2013-04-14    01:01:21:526    1180    4f8    Agent      * Online = No; Ignore download priority = No
2013-04-14    01:01:21:526    1180    4f8    Agent      * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2013-04-14    01:01:21:526    1180    4f8    Agent      * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2013-04-14    01:01:21:526    1180    4f8    Agent      * Search Scope = {Machine}
2013-04-14    01:01:26:698    1180    4f8    Agent      * Added update {87E13ECB-C669-43BE-9E2A-01E567285031}.203 to search result
2013-04-14    01:01:26:698    1180    4f8    Agent      * Found 1 updates and 69 categories in search; evaluated appl. rules of 617 out of 1007 deployed entities
2013-04-14    01:01:26:698    1180    4f8    Agent    *********
2013-04-14    01:01:26:698    1180    4f8    Agent    **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
2013-04-14    01:01:26:698    1180    4f8    Agent    *************
2013-04-14    01:01:26:745    1180    3f0    AU    >>##  RESUMED  ## AU: Search for updates [CallId = {4CC39288-6E0C-4F19-ADEC-FAC9B9B68424}]
2013-04-14    01:01:26:745    1180    3f0    AU      # 1 updates detected
2013-04-14    01:01:26:745    1180    4f8    Report    REPORT EVENT: {F08F242D-B9C4-42EA-94A4-DD77F772F6BA}    2013-04-14 01:01:21:464-0600    1   195    101    {87E13ECB-C669-43BE-9E2A-01E567285031}    203    80070643    AutomaticUpdates    Failure    Content Install    Installation Failure: Windows failed to install the following update with error 0x80070643: Internet Explorer 10 for Windows 7.
2013-04-14    01:01:26:745    1180    3f0    AU    #########
2013-04-14    01:01:26:745    1180    3f0    AU    ##  END  ##  AU: Search for updates [CallId = {4CC39288-6E0C-4F19-ADEC-FAC9B9B68424}]
2013-04-14    01:01:26:745    1180    3f0    AU    #############

Does anyone know where the installation files should be located under the WSUS directory, or anything else I may be able to check?  I've found several other posts with the same problem no apparent solution found.

I am attempting to install updates from a WSUS server on a Windows 7 32-bit machine. Updates fail with error 80070006. I reviewed the WindowsUpdate.log and see the following lines each time I attempt to install updates from WSUS or Microsoft Update:

2013-05-07 02:22:50:466  956 17fc Setup SelfUpdate handler is not found.  It will be downloaded
2013-05-07 02:22:50:466  956 17fc Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.6.7600.256"
2013-05-07 02:22:52:182  956 17fc Setup WARNING: Cbs StartSession, error = 0x80070006
2013-05-07 02:22:52:182  956 17fc Setup FATAL: Applicability evaluation for setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.6.7600.256" failed, error = 0x80070006
2013-05-07 02:22:52:182  956 17fc Setup FATAL: SelfUpdate check failed, err = 0x80070006
2013-05-07 02:22:52:182  956 17fc Agent   * WARNING: Skipping scan, self-update check returned 0x80070006
2013-05-07 02:22:52:182  956 17fc Agent   * WARNING: Exit code = 0x80070006
2013-05-07 02:22:52:182  956 17fc Agent *********
2013-05-07 02:22:52:182  956 17fc Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
2013-05-07 02:22:52:182  956 17fc Agent *************
2013-05-07 02:22:52:182  956 17fc Agent WARNING: WU client failed Searching for update with error 0x80070006
2013-05-07 02:22:52:182  956 fb0 AU >>##  RESUMED  ## AU: Search for updates [CallId = {C9337618-089E-4D5C-98FD-7696A4FCEFB4}]
2013-05-07 02:22:52:182  956 fb0 AU   # WARNING: Search callback failed, result = 0x80070006
2013-05-07 02:22:52:182  956 fb0 AU   # WARNING: Failed to find updates with error code 80070006

I don't believe this is WSUS related since all other machines update fine. I have tried seveal things to remedy this issue including running the update repair tool, but have not had any luck. Does anyone have any ideas?

I recently deployed a WSUS server for one of our remote sites. This WSUS is a replica of an upstream server. The issue is that none of the clients are reporting to the WSUS server. The event log on the WSUS server shows an Event ID 13051 no client computers have ever contacted the server. Looking at one of the client's WindowsUpdate.log:

WARNING: Send failed with hr = 80072efd.
WARNING: SendRequest failed with hr = 80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
WARNING: WinHttp: SendRequestUsingProxy failed for <http://server.domain.com:8530/selfupdate/wuident.cab>. error 0x80072efd
WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072efd
WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072efd
WARNING: Send failed with hr = 80072efd.
WARNING: SendRequest failed with hr = 80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
WARNING: WinHttp: SendRequestUsingProxy failed for <http://server.domain.com:8530/selfupdate/wuident.cab>. error 0x80072efd
WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072efd
WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072efd
WARNING: Send failed with hr = 80072efd.
WARNING: SendRequest failed with hr = 80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
WARNING: WinHttp: SendRequestUsingProxy failed for <http://server.domain.com:8530/selfupdate/wuident.cab>. error 0x80072efd
WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072efd
WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072efd
WARNING: Send failed with hr = 80072efd.
WARNING: SendRequest failed with hr = 80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
WARNING: WinHttp: SendRequestUsingProxy failed for <http://server.domain.com:8530/selfupdate/wuident.cab>. error 0x80072efd
WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072efd
WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072efd
WARNING: DownloadFileInternal failed for http://server.domain.com:8530/selfupdate/wuident.cab: error 0x80072efd
WARNING: SelfUpdate check failed to download package information, error = 0x80072EFD
FATAL: SelfUpdate check failed, err = 0x80072EFD

Solarwinds WSUS client diagnostic:

WSUS Server Connectivity -- Unable to connect to the remote server
  clientwebservice/client.asmx:                      Error: ConnectFailure (Cannot Connect – caused by a network infrastructure fault making the Windows Update unavailable to the client system)
  simpleauthwebservice/simpleauth.asmx:              Error: ConnectFailure (Cannot Connect – caused by a network infrastructure fault making the Windows Update unavailable to the client system)
  content:                                           Error: ConnectFailure (Cannot Connect – caused by a network infrastructure fault making the Windows Update unavailable to the client system)
  selfupdate/iuident.cab:                            Error: ConnectFailure (Cannot Connect – caused by a network infrastructure fault making the Windows Update unavailable to the client system)
  iuident.cab:                                       Error: ConnectFailure (Cannot Connect – caused by a network infrastructure fault making the Windows Update unavailable to the client system)

Anything else I can try before uninstalling/reinstalling IIS & WSUS role?

I reinstalled our WSUS yesterday and used the default site settings. Now I realize I need a https site for SSL and should have used a custom https site instead. So I found a couple articles on how to add self signed certs to WSUS website in IIS7 and have now broken the WSUS server. I did the following,

Once I created a https and binded it, WSUS immediately broke and will not come back up. I deleted the https bind, restarted all services to no avail. Please help

Log Name:      Application
Source:        Windows Server Update Services
Date:          5/7/2013 12:02:40 PM
Event ID:      7032
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      CCS-RAS
Description:
The WSUS administration console was unable to connect to the WSUS Server via the remote API.

Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.

The WSUS administration console was unable to connect to the WSUS Server via the remote API.

Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.

System.Net.Sockets.SocketException -- No connection could be made because the target machine actively refused it 192.168.170.10:80

Source
System

Stack Trace:
   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)
** this exception was nested inside of the following exception **


System.Net.WebException -- Unable to connect to the remote server

Source
Microsoft.UpdateServices.Administration

Stack Trace:
   at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)
   at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer()
   at Microsoft.UpdateServices.UI.AdminApiAccess.AdminApiTools.GetUpdateServer()
   at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServer()
   at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServerAndPopulateNode(Boolean connectingServerToConsole)
   at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.OnExpand(AsyncStatus status)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Windows Server Update Services" />
    <EventID Qualifiers="0">7032</EventID>
    <Level>3</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-05-07T16:02:40.000000000Z" />
    <EventRecordID>137220</EventRecordID>
    <Channel>Application</Channel>
    <Computer>CCS-RAS</Computer>
    <Security />
  </System>
  <EventData>
    <Data>The WSUS administration console was unable to connect to the WSUS Server via the remote API.

Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.

The WSUS administration console was unable to connect to the WSUS Server via the remote API.

Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.

System.Net.Sockets.SocketException -- No connection could be made because the target machine actively refused it 192.168.170.10:80

Source
System

Stack Trace:
   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket&amp; socket, IPAddress&amp; address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception&amp; exception)
** this exception was nested inside of the following exception **


System.Net.WebException -- Unable to connect to the remote server

Source
Microsoft.UpdateServices.Administration

Stack Trace:
   at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)
   at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer()
   at Microsoft.UpdateServices.UI.AdminApiAccess.AdminApiTools.GetUpdateServer()
   at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServer()
   at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServerAndPopulateNode(Boolean connectingServerToConsole)
   at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.OnExpand(AsyncStatus status)</Data>
  </EventData>
</Event>

Hi -

I've spent a good number of hours going over this forum (and other forums) to solve my problem, but can't seem to find a definite solution for this situtation. For a number of years,  I've had WSUS running in my small business environment here in my office and had little or no problems. Over the last year or so WSUS has stopped functioning completely. Honestly, I can't recall now what the original problem/error was or what exactly started it. I believe it was something to do with a service pack or an update of some kind, but I can't be sure. The WSUS console would just blink on the screen and crash.

Anyway, I apologize for my description of the error being so vague. While trying to keep up with service calls and everything else involved with being a small business owner, I ended up just ignoring the problem for a while. A few months ago I decided to tackle the problem, spent a good amount of time researching it and made a few changes to no avail. Things got busy again and I haven't gone back to it till now. The problem has become really annoying at this point, so one way or another I'd really like it solved. As it stands now, the console will open, but won't connect to the WSUS server database at all. All I get is: "Error: Connection Error" and gives me the option to "Reset Server Node" or "Copy to Clipboard". I cannot remember what I did to cause this or what the original errors were before it got to this point. Digging a little further, I find in the event log: Event 18456 - source MSSQL$MICROSOFT##SSEE cannot be found... and goes on to say: The specified resource type cannot be found in the image file. Basically, I made the problem worse.

At this point since I cannot remember what I did, I'd like to "start over" with WSUS if possible. This is running on a SBS2008 Server (the only one) in my office. Is there any way I can get this off the system and do a clean installation of ONLY WSUS? WSUS didn't "come with" SBS. I installed it separate a few months later after I setup the network so I could learn WSUS. We also use the company web site, calendar, fax, remote access, etc... on a daily basis. Can this be removed without permanently effecting the other services or the data in them? I'm a little fuzzy on SQL Server and how that interacts with the other services on SBS.

Any Suggestions? Please let me know what other information you might need to help.

Thank you very much for your time.

Andy

Andy Gonzalez

Dear Microsoft

Here we go again... you issue an update to fix bugs / improve security.... we spend money and time downloading and installing those updates when themselves need debugging as they fail to install.

Just like many other cases:

• Windows .net4 updtes fail repeated on server 2008 R2
• KB2656351 Fails to install. Signature could not be verified - the certificate could not be checked
• .NET 4 Install Error - Generic Trust Failure
• KB2600217 error code 800B010B "Generic trust failure"

I'm sorry but there has been ample time and community reports to fix these .NET install / update issues delivered via WSUS. I simply cannot afford to spend hours trying to figure out what fix is required this time and then to go and apply that manually to the 40+ servers on which this is failing.

I'm not asking what the manual fix for the above issue is - I don't care anymore. I'm expecting the quality assurance team to pull out their finger and get to grips with these problems and work with your product teams to get these updates working properly through WSUS. Issue a revision to the updates and have them install successfully.

Surely the great Microsoft can handle that? It is your updates for your software delievered through your software into hardware running your software. We the public are getting tired of fixing the same problem over and over, some don't get paid for it and it is becoming an intellectually wasteful past time.

Rant over, but I'm serious about fixing the root cause instead of "plugging the hole" in each update on each computer.

I can see the above sus client is rebooting the system however the setting in SCCM is set as suppress the reboot and the same deployment is targetted to 20 odd servers all are showing the popup for the reboot i done some investigation and found that its because of notification not shown for the logged on user it has been rebooted by the SUS client

And the Updates deployment log not showing the visible update on the machine using that i found that its related to the Notification i still have the doubt with the Group policy and our server team is saying all the policy setting are same for the servers. this is happening on 4 servers and the reboot is happening nearly or exactly 25 hours after the scheduled of deployment @3 am

Regards,

Kamala kannan.c