WSUS 33002 ERROR

Hello,
i have a probleme with my WSUS error 33002 fhis is the error in the event log which appears every 15 seconds.
OS: Widows server 2005
SQL server 2005
Type de l'événement : Erreur
Source de l'événement : MSSQL$MICROSOFT##SSEE
Catégorie de l'événement : (2)
ID de l'événement : 33002
Date : 28/11/2013
Heure : 09:12:43
Utilisateur : AUTORITE NT\SERVICE RÉSEAU
Ordinateur : SRVWSUS
Description :
Access to table dbo.tbDownstreamServerClientSummaryRollup is blocked because the signature is not valid.
Pour plus d'informations, consultez le centre Aide et support à l'adresse http://go.microsoft.com/fwlink/events.asp.
Any thoughts on this error?
thank you

thank you I've allready seen this solution, but it does not solve my problem
So, why does it not solve your problem? Because you actually do have the latest certificates installed, or because it did not provide you sufficient information to resolve the problem?
Please also note that there is a known issue with the Certificate Auto-Update functionality in Windows Server 2003 (and by extension SBS2003) that I was not aware of in August, 2010, when the cited thread was originally created.
You will need to identify the needed certificate(s) for that SQL2005 system -- Hint: They'll have been issued by Microsoft in the past eight years (since SQL2005 is that age) -- and EXPORT them from a Windows XP or Windows 7 system that has the latest
KB931125 installed.
Also, since this is a *WSUS* system and the error is actually in a stored proc of the *WSUS* database, and a lot has happened since August, 2010, relevant to this conversation:
Have you installed all of the appropriate WU/WSUS related updates from the past 2 years, including KB2718704, KB2720211, and then KB2661254? Note also, that it could be the installation of KB2661254, by itself without updated certificates, that
caused this error to occur.
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence R Garvin
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

Similar Messages

Clients cannot update from WSUS server - error 8024400E

Alright, so I'm troubleshooting our WSUS server and seem to be stuck. I am running WSUS 3.2.7600.226 on Server 2003. The client I have been using for testing is Windows 7 x64, but we have this issue on all clients (XP, 7 x86, and 7 x64). I started
with an error of 800B0001 and after googling installed KB2720211 to fix it. Now I am getting error 8024400E on clients when I attempt to update. I followed a technet walkthrough and verified that my WSUS settings are all correct (at least regarding iis,
registry, gpo settings, and file system permissions). I am able to download CAB files from the WSUS server by going to the proper address in a browser. Here is a snippet from my WindowsUpdate log on my client:
2013-12-20 10:27:29:784 972 23ac AU #############
2013-12-20 10:27:29:784 972 23ac AU ## START ## AU: Search for updates
2013-12-20 10:27:29:784 972 23ac AU #########
2013-12-20 10:27:29:785 972 23ac AU <<## SUBMITTED ## AU: Search for updates [CallId = {749E5CD5-F4DE-48FC-A691-3610EF622CE3}]
2013-12-20 10:27:29:785 972 2bcc Agent *************
2013-12-20 10:27:29:785 972 2bcc Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2013-12-20 10:27:29:785 972 2bcc Agent *********
2013-12-20 10:27:29:785 972 2bcc Agent * Online = Yes; Ignore download priority = No
2013-12-20 10:27:29:785 972 2bcc 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-12-20 10:27:29:785 972 2bcc Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2013-12-20 10:27:29:785 972 2bcc Agent * Search Scope = {Machine}
2013-12-20 10:27:29:785 972 2bcc Setup Checking for agent SelfUpdate
2013-12-20 10:27:29:785 972 2bcc Setup Client version: Core: 7.6.7600.256 Aux: 7.6.7600.256
2013-12-20 10:27:29:785 972 2bcc Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2013-12-20 10:27:29:789 972 2bcc Misc Microsoft signed: Yes
2013-12-20 10:27:29:794 972 2bcc Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2013-12-20 10:27:29:797 972 2bcc Misc Microsoft signed: Yes
2013-12-20 10:27:29:799 972 2bcc Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2013-12-20 10:27:29:803 972 2bcc Misc Microsoft signed: Yes
2013-12-20 10:27:29:808 972 2bcc Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2013-12-20 10:27:29:812 972 2bcc Misc Microsoft signed: Yes
2013-12-20 10:27:29:821 972 2bcc Setup Determining whether a new setup handler needs to be downloaded
2013-12-20 10:27:29:821 972 2bcc Setup SelfUpdate handler is not found. It will be downloaded
2013-12-20 10:27:29:821 972 2bcc Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
2013-12-20 10:27:29:823 972 2bcc Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2013-12-20 10:27:29:823 972 2bcc Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2013-12-20 10:27:29:835 972 2bcc Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2013-12-20 10:27:29:835 972 2bcc Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2013-12-20 10:27:29:852 972 2bcc Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2013-12-20 10:27:29:852 972 2bcc Setup SelfUpdate check completed. SelfUpdate is NOT required.
2013-12-20 10:27:29:884 972 2bcc PT +++++++++++ PT: Synchronizing server updates +++++++++++
2013-12-20 10:27:29:884 972 2bcc PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://wsusservername/ClientWebService/client.asmx
2013-12-20 10:27:29:896 972 2bcc PT WARNING: Cached cookie has expired or new PID is available
2013-12-20 10:27:29:896 972 2bcc PT Initializing simple targeting cookie, clientId = 488f3922-1a4e-4921-b015-25957eeb6500, target group = http://wsusservername, DNS name = mycomputer.domain.local
2013-12-20 10:27:29:896 972 2bcc PT Server URL = http://wsusservername/SimpleAuthWebService/SimpleAuth.asmx
2013-12-20 10:27:29:902 972 2bcc PT WARNING: GetAuthorizationCookie failure, error = 0x8024400E, soap client error = 7, soap error code = 400, HTTP status code = 200
2013-12-20 10:27:29:902 972 2bcc PT WARNING: SOAP Fault: 0x000190
2013-12-20 10:27:29:902 972 2bcc PT WARNING: faultstring:Fault occurred
2013-12-20 10:27:29:902 972 2bcc PT WARNING: ErrorCode:InternalServerError(5)
2013-12-20 10:27:29:902 972 2bcc PT WARNING: Message:(null)
2013-12-20 10:27:29:902 972 2bcc PT WARNING: Method:"http://www.microsoft.com/SoftwareDistribution/Server/SimpleAuthWebService/GetAuthorizationCookie";
2013-12-20 10:27:29:902 972 2bcc PT WARNING: ID:9d989bf6-04e3-44a9-8ffd-f20bb997b3f0
2013-12-20 10:27:29:902 972 2bcc PT WARNING: Failed to initialize Simple Targeting Cookie: 0x8024400e
2013-12-20 10:27:29:902 972 2bcc PT WARNING: PopulateAuthCookies failed: 0x8024400e
2013-12-20 10:27:29:902 972 2bcc PT WARNING: RefreshCookie failed: 0x8024400e
2013-12-20 10:27:29:902 972 2bcc PT WARNING: RefreshPTState failed: 0x8024400e
2013-12-20 10:27:29:902 972 2bcc PT WARNING: Sync of Updates: 0x8024400e
2013-12-20 10:27:29:902 972 2bcc PT WARNING: SyncServerUpdatesInternal failed: 0x8024400e
2013-12-20 10:27:29:902 972 2bcc Agent * WARNING: Failed to synchronize, error = 0x8024400E
2013-12-20 10:27:29:902 972 2bcc Agent * WARNING: Exit code = 0x8024400E
2013-12-20 10:27:29:902 972 2bcc Agent *********
2013-12-20 10:27:29:902 972 2bcc Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2013-12-20 10:27:29:902 972 2bcc Agent *************
2013-12-20 10:27:29:902 972 2bcc Agent WARNING: WU client failed Searching for update with error 0x8024400e
2013-12-20 10:27:29:902 972 1bc8 AU >>## RESUMED ## AU: Search for updates [CallId = {749E5CD5-F4DE-48FC-A691-3610EF622CE3}]
2013-12-20 10:27:29:902 972 1bc8 AU # WARNING: Search callback failed, result = 0x8024400E
2013-12-20 10:27:29:902 972 1bc8 AU # WARNING: Failed to find updates with error code 8024400E
2013-12-20 10:27:29:902 972 1bc8 AU #########
2013-12-20 10:27:29:902 972 1bc8 AU ## END ## AU: Search for updates [CallId = {749E5CD5-F4DE-48FC-A691-3610EF622CE3}]
2013-12-20 10:27:29:902 972 1bc8 AU #############
2013-12-20 10:27:29:903 972 1bc8 AU Successfully wrote event for AU health state:0
2013-12-20 10:27:29:903 972 1bc8 AU AU setting next detection timeout to 2013-12-20 21:27:29
2013-12-20 10:27:29:903 972 1bc8 AU Setting AU scheduled install time to 2013-12-21 10:00:00
2013-12-20 10:27:29:903 972 1bc8 AU Successfully wrote event for AU health state:0
2013-12-20 10:27:29:904 972 1bc8 AU Successfully wrote event for AU health state:0
2013-12-20 10:27:34:498 972 2bcc Report REPORT EVENT: {2519DC64-E7F9-499B-A2F8-B58DA4A0C08A} 2013-12-20 10:27:29:902-0600 1 148 101 {00000000-0000-0000-0000-000000000000} 0 8024400e AutomaticUpdates Failure Software Synchronization Windows Update Client failed
to detect with error 0x8024400e.
2013-12-20 10:27:34:502 972 2bcc Report CWERReporter::HandleEvents - WER report upload completed with status 0x8
2013-12-20 10:27:34:502 972 2bcc Report WER Report sent: 7.6.7600.256 0x8024400e 00000000-0000-0000-0000-000000000000 Scan 101 Managed
2013-12-20 10:27:34:502 972 2bcc Report CWERReporter finishing event handling. (00000000)
I focused in on "GetAuthorizationCookie failure, error = 0x8024400E, soap client error = 7, soap error code = 400, HTTP status code = 200" and did some googling which all points at Microsoft Office 2003 SP1 update as being the culprit, and I followed
the instructions on a technet site to disable the update and am still getting the same error. I'm stumped at this point, and I thought I would post here in the hope that someone can help me before I end up just wiping it out and reinstalling (which I'm worried
won't even solve it).

I focused in on "GetAuthorizationCookie failure, error = 0x8024400E, soap client error = 7, soap error code = 400, HTTP status code = 200" and did some googling which all points at Microsoft Office 2003 SP1 update as being the culprit, and I followed
the instructions on a technet site to disable the update and am still getting the same error.
While you're definitely on the right track, the Office2003SP1 update really has not been an issue since WSUS Service Pack 2 was released in October 2009 (and really, the Office2003SP1 update that was the cause of this was replaced long before that even,
so you probably don't even have the defective update on your server).
However, the error is generally associated with the presence of defective update(s) on the WSUS server, so the first thing to do is address any potential issues caused by a failed install of KB2720211.
If the error still persists after verifying that all other aspects of the server are fully operational, review the list of not-Declined updates on your WSUS server and make sure that:
All Expired updates are Declined (and then run the Server Cleanup Wizard and let it delete the expired updates).
All approvals for older revisions have been removed (and then run the Server Cleanup Wizard and let it delete the older revisions).
All approvals for superseded updates have been removed. (And then, when they report as 100% Not Applicable, decline them, and then run the Server Cleanup Wizard so that it can delete the files associated with those updates).
Once all of the potentially problematic updates have been removed from the view of the Windows Update Agent, and if this error then persists, we can evaluate it from a more focused perspective.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

No connection to new install of WSUS, 404 errors in log

I am attempting to move WSUS from a functional Windows 2008 R2 server to a Windows Server 2012 R2 environment. There are no connection problems to the old server. However, I cannot get clients - including the Win2012 server itself - to connect
to WSUS. The logs on the two machines I have been testing with show 404 errors, and the connection attempt ends with an error code of 80244019. I have set up WSUS in a test environment, as well, and receive the same errors. Any assistance
would be very welcome.
This is the log from the last connection attempt on a Win7 machine:
2014-12-26   15:08:02:273   1044   147c   PT   WARNING: GetConfig failure, error = 0x80244019, soap client error = 10, soap error code = 0, HTTP status code = 404
2014-12-26   15:08:02:273   1044   147c   PT   WARNING: PTError: 0x80244019
2014-12-26   15:08:02:273   1044   147c   PT   WARNING: GetConfig_WithRecovery failed: 0x80244019
2014-12-26   15:08:02:273   1044   147c   PT   WARNING: RefreshConfig failed: 0x80244019
2014-12-26   15:08:02:273   1044   147c   PT   WARNING: RefreshPTState failed: 0x80244019
2014-12-26   15:08:02:273   1044   147c   PT   WARNING: PTError: 0x80244019
2014-12-26   15:08:02:273   1044   147c   Report   WARNING: Reporter failed to upload events with hr = 80244019.
2014-12-26   15:10:48:475   1044   97c   AU   Triggering AU detection through DetectNow API
2014-12-26   15:10:48:475   1044   97c   AU   Triggering Online detection (interactive)
2014-12-26   15:10:48:475   1044   14ac   AU   #############
2014-12-26   15:10:48:475   1044   14ac   AU   ## START ## AU: Search for updates
2014-12-26   15:10:48:475   1044   14ac   AU   #########
2014-12-26   15:10:48:528   1044   14ac   AU   <<## SUBMITTED ## AU: Search for updates [CallId = {2C781D1E-B959-4D87-B53A-A3EC32523C92}]
2014-12-26   15:10:48:528   1044   147c   Agent   *************
2014-12-26   15:10:48:528   1044   147c   Agent   ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-12-26   15:10:48:528   1044   147c   Agent   *********
2014-12-26   15:10:48:528   1044   147c   Agent      * Online = Yes; Ignore download priority = No
2014-12-26   15:10:48:528   1044   147c   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"
2014-12-26   15:10:48:528   1044   147c   Agent      * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2014-12-26   15:10:48:528   1044   147c   Agent      * Search Scope = {Machine}
2014-12-26   15:10:48:528   1044   147c   Setup   Checking for agent SelfUpdate
2014-12-26   15:10:48:788   1044   147c   Setup   Client version: Core: 7.6.7600.320 Aux: 7.6.7600.256
2014-12-26   15:10:48:813   1044   147c   Misc   WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190194
2014-12-26   15:10:48:813   1044   147c   Misc   WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190194
2014-12-26   15:10:48:813   1044   147c   Misc   WARNING: DownloadFileInternal failed for http://hvdata02/selfupdate/wuident.cab: error 0x80190194
2014-12-26   15:10:48:813   1044   147c   Setup   FATAL: DownloadCab failed, err = 0x80190194
2014-12-26   15:10:48:813   1044   147c   Setup   WARNING: SelfUpdate check failed to download package information, error = 0x80244019
2014-12-26   15:10:48:813   1044   147c   Setup   FATAL: SelfUpdate check failed, err = 0x80244019
2014-12-26   15:10:48:814   1044   147c   Agent      * WARNING: Skipping scan, self-update check returned 0x80244019
2014-12-26   15:10:48:814   1044   147c   Agent      * WARNING: Exit code = 0x80244019
2014-12-26   15:10:48:814   1044   147c   Agent   *********
2014-12-26   15:10:48:814   1044   147c   Agent   ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-12-26   15:10:48:814   1044   147c   Agent   *************
Here is the log from last connection attempt on the Win12 server:
2014-12-26   15:22:57:162   952   271c   EP   Got WSUS Client/Server URL: "http://hvdata02/ClientWebService/client.asmx"
2014-12-26   15:22:57:162   952   271c   PT   WARNING: Cached cookie has expired or new PID is available
2014-12-26   15:22:57:162   952   271c   EP   Got WSUS SimpleTargeting URL: "http://hvdata02"
2014-12-26   15:22:57:162   952   271c   IdleTmr   WU operation (CAuthorizationCookieWrapper::InitializeSimpleTargetingCookie) started; operation # 58; does use network; is at
background priority
2014-12-26   15:22:57:162   952   271c   PT   Initializing simple targeting cookie, clientId = 0ac9539d-68db-4f07-a1f0-1b1e8afa245b, target group = , DNS name = hvdata02.hvmd.drdpools.com
2014-12-26   15:22:57:162   952   271c   PT      Server URL = http://hvdata02/SimpleAuthWebService/SimpleAuth.asmx
2014-12-26   15:22:57:178   952   271c   WS   WARNING: Nws Failure: errorCode=0x803d000d
2014-12-26   15:22:57:178   952   271c   WS   WARNING: There was an error communicating with the endpoint at 'http://hvdata02/SimpleAuthWebService/SimpleAuth.asmx'.
2014-12-26   15:22:57:178   952   271c   WS   WARNING: The server returned HTTP status code '404 (0x194)' with text 'Not Found'.
2014-12-26   15:22:57:178   952   271c   WS   WARNING: The requested resource was not found.
2014-12-26   15:22:57:178   952   271c   WS   WARNING: MapToSusHResult mapped Nws error 0x803d000d to 0x80244019
2014-12-26   15:22:57:178   952   271c   WS   WARNING: Web service call failed with hr = 80244019.
2014-12-26   15:22:57:178   952   271c   WS   WARNING: Current service auth scheme='None'.
2014-12-26   15:22:57:178   952   271c   WS   WARNING: Proxy List used: '(null)', Bypass List used: '(null)', Last Proxy used: '(null)', Last auth Schemes used: 'None'.
2014-12-26   15:22:57:178   952   271c   WS   FATAL: OnCallFailure failed with hr=0X80244019
2014-12-26   15:22:57:178   952   271c   WS   FATAL: NwsCallWithRetries<Functor>( Functor(_clientId, _targetGroupName, _dnsName, &_result)) failed with hr=0x80244019
2014-12-26   15:22:57:178   952   271c   IdleTmr   WU operation (CAuthorizationCookieWrapper::InitializeSimpleTargetingCookie, operation # 58) stopped; does use network; is at
background priority
2014-12-26   15:22:57:178   952   271c   PT   WARNING: Failed to initialize Simple Targeting Cookie: 0x80244019
2014-12-26   15:22:57:178   952   271c   PT   WARNING: PopulateAuthCookies failed: 0x80244019
2014-12-26   15:22:57:178   952   271c   PT   WARNING: RefreshCookie failed: 0x80244019
2014-12-26   15:22:57:178   952   271c   PT   WARNING: RefreshPTState failed: 0x80244019
2014-12-26   15:22:57:178   952   271c   PT   WARNING: PTError: 0x80244019
2014-12-26   15:22:57:178   952   271c   Report   WARNING: Reporter failed to upload events with hr = 80244019.
2014-12-26   15:30:57:211   952   271c   EP   Got WSUS Client/Server URL: "http://hvdata02/ClientWebService/client.asmx"
2014-12-26   15:30:57:305   952   271c   PT   WARNING: Cached cookie has expired or new PID is available
2014-12-26   15:30:57:368   952   271c   EP   Got WSUS SimpleTargeting URL: "http://hvdata02"
2014-12-26   15:30:57:368   952   271c   IdleTmr   WU operation (CAuthorizationCookieWrapper::InitializeSimpleTargetingCookie) started; operation # 59; does use network; is at
background priority
2014-12-26   15:30:57:368   952   271c   PT   Initializing simple targeting cookie, clientId = 0ac9539d-68db-4f07-a1f0-1b1e8afa245b, target group = , DNS name = hvdata02.hvmd.drdpools.com
2014-12-26   15:30:57:368   952   271c   PT      Server URL = http://hvdata02/SimpleAuthWebService/SimpleAuth.asmx
2014-12-26   15:30:58:876   952   271c   WS   WARNING: Nws Failure: errorCode=0x803d000d
2014-12-26   15:30:58:938   952   271c   WS   WARNING: There was an error communicating with the endpoint at 'http://hvdata02/SimpleAuthWebService/SimpleAuth.asmx'.
2014-12-26   15:30:58:938   952   271c   WS   WARNING: The server returned HTTP status code '404 (0x194)' with text 'Not Found'.
2014-12-26   15:30:58:938   952   271c   WS   WARNING: The requested resource was not found.
2014-12-26   15:30:58:938   952   271c   WS   WARNING: MapToSusHResult mapped Nws error 0x803d000d to 0x80244019
2014-12-26   15:30:58:938   952   271c   WS   WARNING: Web service call failed with hr = 80244019.
2014-12-26   15:30:58:938   952   271c   WS   WARNING: Current service auth scheme='None'.
2014-12-26   15:30:58:938   952   271c   WS   WARNING: Proxy List used: '(null)', Bypass List used: '(null)', Last Proxy used: '(null)', Last auth Schemes used: 'None'.
2014-12-26   15:30:58:938   952   271c   WS   FATAL: OnCallFailure failed with hr=0X80244019
2014-12-26   15:30:58:938   952   271c   WS   FATAL: NwsCallWithRetries<Functor>( Functor(_clientId, _targetGroupName, _dnsName, &_result)) failed with hr=0x80244019
2014-12-26   15:30:58:938   952   271c   IdleTmr   WU operation (CAuthorizationCookieWrapper::InitializeSimpleTargetingCookie, operation # 59) stopped; does use network; is at
background priority
2014-12-26   15:30:58:938   952   271c   PT   WARNING: Failed to initialize Simple Targeting Cookie: 0x80244019
2014-12-26   15:30:58:938   952   271c   PT   WARNING: PopulateAuthCookies failed: 0x80244019
2014-12-26   15:30:58:938   952   271c   PT   WARNING: RefreshCookie failed: 0x80244019
2014-12-26   15:30:58:938   952   271c   PT   WARNING: RefreshPTState failed: 0x80244019
2014-12-26   15:30:58:938   952   271c   PT   WARNING: PTError: 0x80244019
2014-12-26   15:30:58:938   952   271c   Report   WARNING: Reporter failed to upload events with hr = 80244019.
2014-12-26   15:30:58:938   952   271c   Report   WARNING: CSerializationHelper:: InitSerialize failed : 0x80070002

I am attempting to move WSUS from a functional Windows 2008 R2 server to a Windows Server 2012 R2 environment. There are no connection problems to the old server. However, I cannot get clients - including the Win2012 server itself - to connect
to WSUS. The logs on the two machines I have been testing with show 404 errors, and the connection attempt ends with an error code of 80244019. I have set up WSUS in a test environment, as well, and receive the same errors. Any assistance
would be very welcome.
This is the log from the last connection attempt on a Win7 machine:
2014-12-26   15:08:02:273   1044   147c   PT   WARNING: GetConfig failure, error = 0x80244019, soap client error = 10, soap error code = 0, HTTP status code = 404
2014-12-26   15:08:02:273   1044   147c   Report   WARNING: Reporter failed to upload events with hr = 80244019.
2014-12-26   15:10:48:475   1044   97c   AU   Triggering AU detection through DetectNow API
2014-12-26   15:10:48:475   1044   97c   AU   Triggering Online detection (interactive)
2014-12-26   15:10:48:813   1044   147c   Misc   WARNING: DownloadFileInternal failed for http://hvdata02/selfupdate/wuident.cab: error 0x80190194
Here is the log from last connection attempt on the Win12 server:
2014-12-26   15:22:57:162   952   271c   EP   Got WSUS Client/Server URL: "http://hvdata02/ClientWebService/client.asmx"
2014-12-26   15:22:57:162   952   271c   PT   WARNING: Cached cookie has expired or new PID is available
2014-12-26   15:22:57:162   952   271c   EP   Got WSUS SimpleTargeting URL: "http://hvdata02"
2014-12-26   15:22:57:162   952   271c   PT   Initializing simple targeting cookie, clientId = 0ac9539d-68db-4f07-a1f0-1b1e8afa245b, target group = , DNS name = hvdata02.hvmd.drdpools.com
2014-12-26   15:22:57:162   952   271c   PT      Server URL = http://hvdata02/SimpleAuthWebService/SimpleAuth.asmx
2014-12-26   15:22:57:178   952   271c   WS   WARNING: There was an error communicating with the endpoint at 'http://hvdata02/SimpleAuthWebService/SimpleAuth.asmx'.
2014-12-26   15:22:57:178   952   271c   WS   WARNING: The server returned HTTP status code '404 (0x194)' with text 'Not Found'.
2014-12-26   15:30:57:211   952   271c   EP   Got WSUS Client/Server URL: "http://hvdata02/ClientWebService/client.asmx"
2014-12-26   15:30:57:368   952   271c   EP   Got WSUS SimpleTargeting URL: "http://hvdata02"
consistent 404 errors...
I don't see the initial WUA service startup messages, so I'm guessing that based on the errors thrown, you haven't configured the WUServer correctly for WS2012R2 WSUS 6.3
WSUS used to use http/80, and http/8530 was optional, but, now http/8530 is the default, so if you aren't setting WUServer (through registry or GP) with the port specified, the client will default to port 80, and it won't get much on that port other than
constant 404's.....
If you are setting WUServer=http://hvdata02, you should be setting instead: WUServer=http://hvdata02:8530
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

SCCM 2012 R2 WSUS wsyncact error 0x8013141A

i have new servers with Server 2012 R2, SCCM 2012 R2, and SQL 2012 SP1 CU6. SCCM will not sync with WSUS. "Synchronize Software Updates" fails and no updates appear and the scheduled sync in "SUP Component Properties"\"Sync
Schedule" runs, the WSUS servers do not sync with their upstream servers. There are no errors in the WCM and WSUSCtrl logs. The wsyncmgr log has these errors:
Sync failed. Could not load file or assembly '5120 bytes loaded from wsyncact, Version 5.0.0.0, Culture=-neutral, PublicKeyToken=(alphanumeric string) or one of its dependencies. Strong name validation failed. ) Exception from HRESULT: )x8013141A). Source:
wsyncact
STATMSG; ID-6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=(servername) SITE=(site code) PID=2704 TID=5516 GMTDATE=(date/time) ISTR1="Could not load file or assembly 'updmgrclr, Version=5.0.7958.1000, Culture=neutral,
PublicKeyToken=(alphanumeric string)" or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A)" ITR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8=""
ISTR9="" NUMATTRS=0
Sync failed. Will retry in 60 minues.
Moving the servers to an OU with no policies does not help. Setting registry entries to turn off strong name validation does not help.
I did find one post that said the ports in IIS and in SCCM need to match. My do, IIS and SCCM both have 8530/8531.
Suggestions?
Ben JohnsonWY

SOLVED. FINALLY!
Do an internet search for "Keith McGuinness" and "Strong name Validation Failed (Exception from HRESULT 0x8013141A)"
You need to create these two registry keys:
[HKLM\Software\Microsoft\StrongName\Verification\*,123adf9123]
[HKLM\Software\Wow6432Node\Microsoft\StrongName\Verification\*,123adf9123]
You need to do this key pair for each 0x8013141A error you have that has a unique PublicKeyToken. Note that the "*,123adf9123" is a key, not a DWORD or anything else. Also, you have to change 123adf9123 to the PublicKeyToken(s) showing in your
error messages within WSUS. You can then force a new sync by setting a sync time a couple minutes in the future with configure SUP under Administration\Sites.
Note: I did this on the site server.
Ben JohnsonWY

WSUS Sync Error

Dears ,
my WSUS server ,when am trying to synchronizing, it display a HTTP error accrued and below is the error message :
WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected
host has failed to respond 10.xxx.xxx.5:8080
at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
at System.Net.HttpWebRequest.GetRequestStream()
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)
Please advise me .

connection failed because connected host has failed to respond 10.xxx.xxx.5:8080
I would venture a guess that your proxy server (or the proxy client settings of the WSUS server) are misconfigured.
If this masked out address on port 8080 is your proxy server, then that will be your root cause.
First, the WSUS Server needs to be able to communicate on port 80 AND port 443 *simultaneously* to different URLs, so your proxy server needs to be able to manage those separate communications. If the only port your proxy server is listening on is port 8080,
then it probably doesn't know how to properly route HTTP sessions vs HTTPS sessions.
Second... if at all possible... WSUS is *NOT* an appropriate candidate for using a proxy (caching) server. Among other things, the gigabytes of content downloaded by the WSUS server (which will be of ZERO use to any other proxy client) will clog up the proxy
cache, effectively rendering the proxy cache useless for the rest of the enterprise.
Best option: Allow the WSUS server to bypass the proxy server.
If that's NOT an option, then you'll likely need to configure a second listener port on the proxy server, or ensure that the proxy server is able to route traffic from the protocol level (HTTP vs HTTPS).
Bottom line... the communication is getting lost inside the proxy server because it's mishandling the traffic.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

SCCM 2012 R2 configure WSUS got error remote SQL Server 2012

Hi All,
I got question ask on when i want to configure the WSUS component it failed as per screenshot and my SCCM cant work with it.
SCCM Server : Windows Server 2012 R2 (WSUS featured installed)
SCCM Version: System Center Config Manager R2
Remote SQL Server : Windows Server 2012 R2
SQL Version: SQL Server 2012 SP1 -11.0.3153
WSUS Error:
SCCM Error:
Hope you all can provide me a good solution on it I had no clue on this.
Regards,
Sam

Sam,
Recommend you
Remove SUP
Remove WSUS role
Delete the SUSDB on the remote SQL server
Reboot the server
Reinstall WSUS feature
Reinstall SUP
Take a look at my blog on installing a SUP on 2012 from the section 'Install WSUS on the remote SUP server'
http://sccmentor.wordpress.com/2014/09/11/installing-a-remote-sup-in-sccm-2012-r2-on-windows-server-2012-r2/
Make sure you run the Post Install tasks as well.
Cheers
Paul | sccmentor.wordpress.com

Wsus installation error in server 2012

Hi
when i am choosing the content directory path in wsus i am geting this error
Log file is located at C:\Users\Administrator\AppData\Local\Temp\1\tmp9249.tmp
Post install is starting
Fatal Error: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Can any one help me to fix this issue

Hi,
could you please check if this is correct:
- is Named pipes/TCP enabled in SQL Server Configuration manager?
- Is Remote Connection Allowed?
- Is Windows Firewall on or off?
- If it is On, did you create an exception for port 1433 in Windows Firewall?
- Could WSUS contact SQL server?
Please click on Propose As Answer or to mark this post as and helpful for other people. This posting is provided AS-IS with no warranties, and confers no rights.

SCCM 2012 and WSUS Synchronization error. Message ID: 6703.

Hi,
I am facing issues with synchronising updates in WSUS server with SUP in SCCM 2012. I am using web proxy, which has full access to all microsoft update websites. I have configures SUP for both intranet and internet clinets. I am posting some logs below
that may help to resolve the issue:-
wsyncmgr.log-
Synchronizing WSUS server SCCMSERVER.domain.com SMS_WSUS_SYNC_MANAGER 11/1/2012 11:56:35 AM 3824 (0x0EF0)
sync: Starting WSUS synchronization SMS_WSUS_SYNC_MANAGER 11/1/2012 11:56:35 AM 6368 (0x18E0)
Sync failed: UssCommunicationError: WebException: The remote name could not be resolved: 'www.update.microsoft.com'~~at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context). Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS SMS_WSUS_SYNC_MANAGER 11/1/2012
11:58:04 AM 3824 (0x0EF0)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=CDCTIBCMSCCM.India.TCS.com SITE=I1P PID=2648 TID=3824 GMTDATE=Thu Nov 01 06:28:04.549 2012 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS"
ISTR1="UssCommunicationError: WebException: The remote name could not be resolved: 'www.update.microsoft.com'~~at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9=""
NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 11/1/2012 11:58:04 AM 3824 (0x0EF0)
Sync failed. Will retry in 60 minutes SMS_WSUS_SYNC_MANAGER 11/1/2012 11:58:04 AM 3824 (0x0EF0)
WCM.log-
Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.1.6001.1, Major Version = 0x30001, Minor Version = 0x17710001 SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:05 AM 4016 (0x0FB0)
The installed WSUS build has the valid and supported WSUS Administration DLL assembly version (3.1.7600.226) SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:05 AM 4016 (0x0FB0)
Successfully connected to server: SCCMSERVER.domain.com, port: 443, useSSL: True SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:05 AM 4016 (0x0FB0)
Verify Upstream Server settings on the Active WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:05 AM 4016 (0x0FB0)
WSUS Server settings are correctly configured and Upstream Server is set to Microsoft Update SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:05 AM 4016 (0x0FB0)
Successfully connected to server: SCCMSERVER.domain.com, port: 443, useSSL: True SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:05 AM 4016 (0x0FB0)
Successfully got update categories from WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:16 AM 4016 (0x0FB0)
Successfully connected to server: SCCMSERVER.domain.com, port: 443, useSSL: True SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:16 AM 4016 (0x0FB0)
Successfully got update classifications from WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:16 AM 4016 (0x0FB0)
Successfully connected to server: SCCMSERVER.domain.com, port: 443, useSSL: True SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:16 AM 4016 (0x0FB0)
Successfully got update languages from WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:16 AM 4016 (0x0FB0)
Successfully connected to server: SCCMSERVER.domain.com, port: 443, useSSL: True SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012 11:52:21 AM 4016 (0x0FB0)
Subscribed Update Categories <?xml version="1.0" ?>~~<Categories>~~ <Id>1403f223-a63f-f572-82ba-c92391218055</Id>~~ <Id>041e4f9f-3a3d-4f58-8b2f-5e6fe95c4591</Id>~~ <Id>84f5f325-30d7-41c4-81d1-87a0e6535b66</Id>~~ <Id>bfe5b177-a086-47a0-b102-097e4fa1f807</Id>~~ <Id>8c3fcc84-7410-4a95-8b89-a166a0190486</Id>~~ <Id>cb263e3f-6c5a-4b71-88fa-1706f9549f51</Id>~~ <Id>5312e4f1-6372-442d-aeb2-15f2132c9bd7</Id>~~ <Id>7f44c2a7-bc36-470b-be3b-c01b6dc5dd4e</Id>~~ <Id>dbf57a08-0d5a-46ff-b30c-7715eb9498e9</Id>~~ <Id>fdfe8200-9d98-44ba-a12a-772282bf60ef</Id>~~ <Id>ec9aaca2-f868-4f06-b201-fb8eefd84cef</Id>~~ <Id>ba0ae9cc-5f01-40b4-ac3f-50192b5d6aaf</Id>~~ <Id>90e135fb-ef48-4ad0-afb5-10c4ceb4ed16</Id>~~ <Id>26997d30-08ce-4f25-b2de-699c36a8033a</Id>~~ <Id>a4bedb1d-a809-4f63-9b49-3fe31967b6d0</Id>~~ <Id>4cb6ebd5-e38a-4826-9f76-1416a6f563b0</Id>~~ <Id>558f4bc3-4827-49e1-accf-ea79fd72d4c9</Id>~~ <Id>6964aab4-c5b5-43bd-a17d-ffb4346a8e1d</Id>~~</Categories> SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012
11:52:21 AM 4016 (0x0FB0)
Subscribed Update Classifications <?xml version="1.0" ?>~~<Classifications>~~ <Id>e6cf1350-c01b-414d-a61f-263d14d133b4</Id>~~ <Id>0fa1201d-4330-4fa8-8ae9-b877473b6441</Id>~~ <Id>28bc880e-0592-4cbf-8f95-c79b17911d5f</Id>~~ <Id>cd5ffd1e-e932-4e3a-bf74-18bf0b1bbd83</Id>~~</Classifications> SMS_WSUS_CONFIGURATION_MANAGER 11/1/2012
11:52:22 AM 4016 (0x0FB0)
WSUSCtrl.log-
WSUS registry key change notification triggered. SMS_WSUS_CONTROL_MANAGER 11/1/2012 11:51:55 AM 5516 (0x158C)
Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.0.6000.273, Major Version = 0x30000, Minor Version = 0x17700111 SMS_WSUS_CONTROL_MANAGER 11/1/2012 11:51:55 AM 5516 (0x158C)
Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.1.6001.1, Major Version = 0x30001, Minor Version = 0x17710001 SMS_WSUS_CONTROL_MANAGER 11/1/2012 11:51:55 AM 5516 (0x158C)
The installed WSUS build has the valid and supported WSUS Administration DLL assembly version (3.1.7600.226) SMS_WSUS_CONTROL_MANAGER 11/1/2012 11:51:55 AM 5516 (0x158C)
System.Net.WebException: The request failed with HTTP status 403: Forbidden.~~ at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~ at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer()~~
at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber) SMS_WSUS_CONTROL_MANAGER 11/1/2012 11:51:55 AM 5516 (0x158C)
Failed to set WSUS Local Configuration. Will retry configuration. SMS_WSUS_CONTROL_MANAGER 11/1/2012 11:51:55 AM 5516 (0x158C)
Waiting for changes for 57 minutes SMS_WSUS_CONTROL_MANAGER 11/1/2012 11:51:55 AM 5516 (0x158C)
Urgent Help Appreciated.
Thanks,
Deepak

STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=CDCTIBCMSCCM.India.TCS.com SITE=I1P PID=2648 TID=3824 GMTDATE=Thu Nov 01 06:28:04.549 2012 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS"
ISTR1="UssCommunicationError: WebException: The remote name could not be resolved: 'www.update.microsoft.com'~~at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7=""
ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 11/1/2012 11:58:04 AM 3824 (0x0EF0)
System.Net.WebException: The request failed with HTTP status 403: Forbidden.~~ at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~ at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer()~~
at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber) SMS_WSUS_CONTROL_MANAGER 11/1/2012 11:51:55 AM 5516 (0x158C)
Those errors are unrelated to ConfigMgr. The first one is a name resolution error; the second one tells that the servers is not allowed to connect to the proxy.
Torsten Meringer | http://www.mssccmfaq.de

WSUS Database error

Had a disk drive problem with the array the WSUS db is on. Got that corrected but cannot open Update services. I get the Update services screen with an error stating "Error: Database error". The options are to reset server node or copy to clipboard.
I tried resetting server node but get same error. Event viewer shows the following:
Event: 7042 - The WSUS administration console was unable to connect to the WSUS server database. Verify that SQL server is running on the WSUS server. Everything looks fine excpet for not being able to access the database.
Should I re-install WSUS? I can get out to the WSUS folder where the database sits and view contents. It seems like a disconnect. IIS is running and looks to have the correct settings.

Had a disk drive problem with the array the WSUS db is on. Got that corrected but cannot open Update services. I get the Update services screen with an error stating "Error: Database error". The options are to reset server node or copy to clipboard. I tried
resetting server node but get same error. Event viewer shows the following:
Event: 7042 - The WSUS administration console was unable to connect to the WSUS server database. Verify that SQL server is running on the WSUS server. Everything looks fine excpet for not being able to access the database.
Should I re-install WSUS?
You don't describe the nature of the "disk drive problem" you had on this array, but you should certainly consider the possibility that the database was corrupted in the process of that "disk drive problem". Restoring from a recent backup would be the first
recommended option; lacking a good backup to use, or any other diagnostics that can isolate an alternate cause, reinstalling WSUS is almost certainly to be the most expedient effort available.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

Windows Server 2012R2 fails to get update from WSUS with error code 80072ee6

Hi all,
I've deployed WSUS role on a Windows Server 2012R2 machine. WSUS listen on port 8530. Now I'm trying a test server (this machine runs WIndows Server 2012R2 too). I've configured a GPO but when I try to check for updates I get the errore in the subject.
I've checked windowsupdate.log and theese are the settings of the client:
AIR Mode is disabled
2014-02-05 12:59:00:357
776 fe0
AU # Policy Driven Provider: http://MyWSUS.MyDomain.local:8530
2014-02-05 12:59:00:357
776 fe0
AU # Detection frequency: 22
2014-02-05 12:59:00:357
776 fe0
AU # Target group: CSM Servers
2014-02-05 12:59:00:357
776 fe0
AU # Approval type: Pre-install notify (Policy)
2014-02-05 12:59:00:357
776 fe0
AU # Auto-install minor updates: No (User preference)
2014-02-05 12:59:00:357
776 fe0
AU # Will interact with non-admins (Non-admins are elevated (User preference))
I confirm that from the test server I can telnet to my wsus server on TCP port 8530

Hi,
This issue occurs if the URL under the Group Policy setting 'Specify intranet Microsoft update service location' is invalid.
You receive a "80072EE6" error code when you download an update from Windows Server Update Services in Windows 7-based or Windows Server 2008 R2-based
computer
http://support.microsoft.com/kb/2724184
Make sure that the URL is correct and the name can be resolved.
Hope this helps.

SCCM 2012 :::WSUS Getcookie error blocking SCEP definition Scan and updates

Please advise me what could be reasons for this issue and how to resolve it. because of this client is not able to scan and retreive updates against SUP and SCEP Defintion is not getting updated. a few set of servers are facing
this issue. Another set of servers( sccm client is working fine against same SUPs.

That does not cause any issues IMHO. There should be another error later in the log. Also examine U*.log in %windir%\ccm\logs)
Torsten Meringer | http://www.mssccmfaq.de

Wsus cleanup database error

I have win 2012 standart and to large base of updates (sql base - standalone server). Cleanup wizard don't work. I tried running each checkbox
of the cleanup wizard independently - it doesn't work too. Could you advice me script or something? Scripts that I found, did not give any results.
When i execute this line i get the following message :
Exception calling “PerformCleanup” with “1” argument(s): “Timeout expired. The timeout period elapsed prior to completion of the operation or the
server is not responding.
The statement has been terminated.”

I have win 2012 standart and to large base of updates (sql base - standalone server). Cleanup wizard don't work. I tried running each checkbox
of the cleanup wizard independently - it doesn't work too. Could you advice me script or something? Scripts that I found, did not give any results.
When i execute this line i get the following message :
Exception calling “PerformCleanup” with “1” argument(s): “Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not
responding.
The statement has been terminated.”
Start here:
WSUS Timeout Errors -- When? and Why? Eliminating and Avoiding
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

8.1core Client errors 80072EE2 against local WSUS; OK from Microsoft Server.

//alpha is our patched 2008R2 WSUS Server 3.0 SP2, its Registry says InstallType 1, VersionString 3.2.7600.226. It has Hotfixes installed: 2720211, 2734608, 2938066(3.2.7600.274). Serves updates fine for our domain-joined PCs.
We are in a remote South Pacific island and are very bandwidth constrained, so for 7HomePremium & 8.1core machines we run WSUS Client Manager for Workgroups ver 1,1 2012 https://wsusworkgroup.codeplex.com/ to set them to get Updates from our local WSUS.
This works (on all, I believe) except on brand new 8.1core laptops (ie they need lots of Updates), that can fail with error 80072EE2. I believe Ive seen this several times and with a new 8.1core laptop on the bench, I want to get to the bottom of it.
On the Client: "You receive updates managed by your System Admin." I go "Check for Updates" get "Checking for Updates" for 20? secs before the 80072EE2. Ran Microsoft FixIt / WSUS Client Troubleshooter, same. Avira Antivirus,
same if its realtime protection is disabled. No other antimalware running. Computer is not showing in any of the Computer Groups in WSUS Server. Ran Lawrence's Solarwinds Diagnostic Tool for WSUS Agent, Agent Config Settings "good" but Server Connectivity
fails with "WSUS Server Connectivity: unable to connect to the remote server" "connect failure caused by a network infrastructure fault making Windows Update unavailable to the client". 8.1 Desktop on same LAN switch gets updates from WSUS
fine.
Updates from Microsoft Servers work; I accepted 17, which is all the actual "Updates" incl the 8.1 Update (ie not Security Updates,NET,Office etc), retest & local WSUS still error 80072EE2. Turned off Windows Firewall, same. Many reboots.
If client webbrowses to http://alpha/selfupdate/wuident.cab it is offered this .cab.
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate - WUSServer, WUStatusServer with & without port #, these all error:
http://alpha:8530
http://alpha.domainname.local:8530
http://alpha.domainname.local:80
http://alpha.domainname.local <left it like this.
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate\AU UseWUServer 1
ControlPanel - WindowsUpdates - Install Updates Automatically.
wuauclt.exe /resetauthorization /detectnow waited 8 mins, same.
Regarding http://technet.microsoft.com/en-us/library/cc720439%28v=ws.10%29.aspx
In Server Manager - IIS Im not seeing any websites. (me not very good with IIS). If there is no site and WSUS uses one, how are all our other clients successfully updating? Must be, the webrowse to \Selfupdate works. Im wondering how the client
authenticates. Want to check IIS logs but C:\Windows\System32\LogFiles\W3SVC1 no exist; C:\inetpub\logs is empty; C:\Windows\System32\LogFiles\HTTPERR\httperr3.log has entries from yesterday but not today, & none for this clients IP address.
Server Manager - Roles - Web Server - Health & Diagnostics - not installed. explains lack of logs.
Roles - Security - Windows Authentication - installed, Basic Authentication not installed. Installed it, same, uninstalled it.
Not sure where to go from here. I want to look harder at the association between WSUS & IIS esp re authentication, but Im not seeing a way at it.

We are in a remote South Pacific island and are very bandwidth constrained
Timeout errors from the client are generally networking issues. By all rights, if you're on a bandwidth constrained site, then you probably should have a local (replica) WSUS server, so those clients don't have to make WSUS connections across your bandwidth-constrained
connection.
In Server Manager - IIS Im not seeing any websites. (me not very good with IIS). If there is no site and WSUS uses one, how are all our other clients successfully updating?
If client webbrowses to http://alpha/selfupdate/wuident.cab it is offered this .cab.
Well, if there's no v-root for "WSUS Administration", then the port 8530 suffix is incorrect, and possibly the WSUS resources are actually IN the Default Web Site. We know, factually, that there's a /selfupdate folder in the Default Web Site because
you successfully accessed it with a browser, but that's not necessarily significant, because on a WSUS v3 server there is always a /selfupdate v-dir in the Default Web Site. It does tell us, however, that the browser can at least get to the right server.
The question is: Where is *WSUS* installed. Your use of port 8530 implies that there should be a "WSUS Administration" v-root. If it's not there, you've probably found a root cause.
Another observation... in the browser you used the short name, which ostensibly resolved correctly within the domain.local DNS zone. However the WUA is configured to use the FQDN. You should check that the client is properly treating that as a FQDN, and
not trying to append another suffix.
I'd ask the more mundane question: Why aren't you using the simple hostname in the WUAgent configuration anyway? And if you do: Do the timeout errors go away? Usually when I see people using FQDNs to get to internal (local) resources, that suggests something
is not right with the DNS .. and a not right DNS can cause timeout issues trying to find inaccessible or non-locatable resources.
Do nslookup alpha and nslookup alpha.domain.local both return the same results when run on this client?
If the client was actually getting TO the WSUS server using an invalid port number, it should be receiving an HTTP 404 error from the WSUS Server. But it's not. It's timing out, either waiting for a response that might be that HTTP 404 never arriving,
or waiting for a response that's never going to come because the connection was never made.
I'd suggest (once you actually find the WSUS v-root), to inspect the IIS logs on the WSUS server and see if it's actually getting any inbound traffic from those clients.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

Failed to set Subscriptions on the WSUS Server

We are running SCCM 2012 R2; synchronization of updates is not working.
The SUP is running on a Windows 2008 R2 server and it is not the Site Server.
Below I have some log data. I have already tried uninstalling and reinstalling WSUS.
WCM.log
Starting WSUS category sync from upstream... SMS_WSUS_CONFIGURATION_MANAGER 1/6/2015 1:14:22 PM 4488 (0x1188)
Refreshing categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER 1/6/2015 1:14:27 PM 4488 (0x1188)
Attempting connection to WSUS server: cobalt.ad.northcentral.edu, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 1/6/2015 1:14:27 PM 4488 (0x1188)
Successfully connected to server: cobalt.ad.northcentral.edu, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 1/6/2015 1:14:27 PM 4488 (0x1188)
Successfully refreshed categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER 1/6/2015 1:14:53 PM 4488 (0x1188)
Attempting connection to WSUS server: cobalt.ad.northcentral.edu, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 1/6/2015 1:14:53 PM 4488 (0x1188)
Successfully connected to server: cobalt.ad.northcentral.edu, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 1/6/2015 1:14:53 PM 4488 (0x1188)
Category Company:94d731de-22a6-4458-dc4d-b5267de026fc (Adobe Systems, Inc.) not found on WSUS SMS_WSUS_CONFIGURATION_MANAGER 1/6/2015 1:14:53 PM 4488 (0x1188)
Subscription contains categories unknown to WSUS. SMS_WSUS_CONFIGURATION_MANAGER 1/6/2015 1:14:53 PM 4488 (0x1188)
Failed to set Subscriptions on the WSUS Server. Error:(-2147467259)Unspecified error SMS_WSUS_CONFIGURATION_MANAGER 1/6/2015 1:14:53 PM 4488 (0x1188)
STATMSG: ID=6603 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=ALGAE.ad.northcentral.edu SITE=NCU PID=1204 TID=4488 GMTDATE=Tue Jan 06 19:14:53.974 2015 ISTR0="cobalt.ad.northcentral.edu" ISTR1=""
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_CONFIGURATION_MANAGER 1/6/2015 1:14:53 PM 4488 (0x1188)
Waiting for changes for 59 minutes SMS_WSUS_CONFIGURATION_MANAGER 1/6/2015 1:14:53 PM 4488 (0x1188)
wsyncmgr.log
Found active SUP SUP.ad.domain.tld from SCF File.SMS_WSUS_SYNC_MANAGER
1/6/2015 1:10:45 PM    4576 (0x11E0)
Sync failed: WSUS update source not found on site NCU. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSourceSMS_WSUS_SYNC_MANAGER
1/6/2015 1:10:45 PM
4576 (0x11E0)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=Siteserver.ad.domain.tld SITE=NCU PID=1204 TID=4576 GMTDATE=Tue Jan 06 19:10:45.260 2015 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source
not found on site NCU. Please refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0SMS_WSUS_SYNC_MANAGER
1/6/2015 1:10:45 PM
4576 (0x11E0)
Sync failed. Will retry in 60 minutes
SMS_WSUS_SYNC_MANAGER 1/6/2015 1:10:45 PM
4576 (0x11E0)
Setting sync alert to active state on site NCU
SMS_WSUS_SYNC_MANAGER 1/6/2015 1:10:45 PM
4576 (0x11E0)
Sync time: 0d00h00m00s   SMS_WSUS_SYNC_MANAGER
1/6/2015 1:10:45 PM
4576 (0x11E0)
WSUSCtrl.log
Failed to create instance of Microsoft.SystemsManagementServer.WSUS.WSUSServer. error = Unspecified errorSMS_WSUS_CONTROL_MANAGER
1/6/2015 12:39:11 PM
4888 (0x1318)

Blank out/remove all of the categories you have configured in ConfigMgr on the Software Update Point. Then run a full synchronization from the console. This will synch up all available categories without trying to subscribe to any. Then, you can go back
re-select the categories that want (after the full synch completes) and perform another full synch.
Right now, you are trying to subscribe to a category that doesn't exist.
Jason | http://blog.configmgrftw.com | @jasonsandys

Error 80072f8f after installing Windows 8.1 / 2012 R2 "Update"

I just want to share my experience with the new Update.
We are using a WSUS (on Windows Server 2012) with a Wildcard certificate from Geotrust for some time now.
I manually installed the new "Windows 8.1 Update 1" on a Windows 8.1 and a Windows Server 2012 R2 System, both joined in the Domain and were able to update with the WSUS.
Right after the update both systems keeps failing to communicate with the WSUS with error 80072f8f.
After changing the ssl certificate on the WSUS Server to a internal PKI certificate the Systems could talk again with the wsus Server.
So keep in mind when you upgrade to check if the system still works with your wsus server.

I am also getting the same issue where the 80072f8f error occurs when attempting to scan for updates.
The client machines are Windows Server 2012 R2 (with Update 1 installed) and the WSUS server is also running Windows Server 2012 R2 Update 1.
You answers are not remotely helpful in this instance.
The OP has mentioned several times he is using a Windows Server 2012 WSUS box. Therefore the article you reference has no validity for this issue.
TLS 1.2 is enabled by default on 2012 so the linked article and advice unfortunately does not fix the issue.
Has anyone else had the 80072f8f error when using a Windows Server 2012 R2 WSUS box?
We see errors in the CAPI2 log for Verify Revocation Information
and Vertify Chain Policy. Althougjh browsing to our WSUS server in IE shows the correct validated certificate.
Any help would be appreciated.
Kind Regards
James Tighe
MCTS: Windows Server 2008 Active Directory, Configuring MCTS: Windows 7, Configuring

WSUS 33002 ERROR

Similar Messages

Maybe you are looking for