none
SBS 2008 WSUS-Problem - Moving repositories - ID 10022, 12032, 1309 RRS feed

  • Frage

  • Dear colleagues,

    we have two different SBS2008 (V6.0, SP2) in different domains, runs (ran) for longer times without major problems. Since our WSUS update repositories has grown very large, we have moved the data repository via the SBS Console to another local drive. After rebooting the machine WSUS no longer works. The SBS Console crashes when queried about WSUS, status of the client computer is no longer displayed. The Windows Server Update Services Console obviously can not connect to the the database. The following errors are found in the event log:

    Event ID: 10022 The last attempt to synchronize the catalog failed.
    Event ID: 12032 The Server Synchronization Web Service is not working.
    Event ID: 1309 ASP.NET 2.0.50727.0 error


    ****************************************************************************************************************************

    Extract from WindowsUpdate.log:

    2013-01-29 09:53:45:861 1392 b14 AU #############
    2013-01-29 09:53:45:861 1392 b14 AU ## START ##  AU: Search for updates
    2013-01-29 09:53:45:861 1392 b14 AU #########
    2013-01-29 09:53:45:884 1392 b14 AU <<## SUBMITTED ## AU: Search for updates [CallId = {84EF6BD6-BFBD-4827-94B7-11CF01F82C21}]
    2013-01-29 09:53:45:884 1392 2364 Agent *************
    2013-01-29 09:53:45:884 1392 2364 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2013-01-29 09:53:45:884 1392 2364 Agent *********
    2013-01-29 09:53:45:884 1392 2364 Agent   * Online = Yes; Ignore download priority = No
    2013-01-29 09:53:45:884 1392 2364 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-01-29 09:53:45:884 1392 2364 Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2013-01-29 09:53:45:884 1392 2364 Agent   * Search Scope = {Machine}
    2013-01-29 09:53:45:884 1392 2364 Setup Checking for agent SelfUpdate
    2013-01-29 09:53:46:053 1392 2364 Setup Client version: Core: 7.6.7600.256  Aux: 7.6.7600.256
    2013-01-29 09:53:46:053 1392 2364 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2013-01-29 09:53:46:075 1392 2364 Misc  Microsoft signed: Yes
    2013-01-29 09:53:46:085 1392 2364 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2013-01-29 09:53:46:091 1392 2364 Misc  Microsoft signed: Yes
    2013-01-29 09:53:46:097 1392 2364 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2013-01-29 09:53:46:122 1392 2364 Misc  Microsoft signed: Yes
    2013-01-29 09:53:46:126 1392 2364 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2013-01-29 09:53:46:133 1392 2364 Misc  Microsoft signed: Yes
    2013-01-29 09:53:46:163 1392 2364 Setup Determining whether a new setup handler needs to be downloaded
    2013-01-29 09:53:46:163 1392 2364 Setup SelfUpdate handler is not found.  It will be downloaded
    2013-01-29 09:53:46:164 1392 2364 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
    2013-01-29 09:53:46:169 1392 2364 Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2013-01-29 09:53:46:169 1392 2364 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
    2013-01-29 09:53:46:207 1392 2364 Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2013-01-29 09:53:46:208 1392 2364 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
    2013-01-29 09:53:46:259 1392 2364 Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2013-01-29 09:53:46:259 1392 2364 Setup SelfUpdate check completed.  SelfUpdate is NOT required.
    2013-01-29 09:54:01:418 1392 2364 PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2013-01-29 09:54:01:418 1392 2364 PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://COMPANYSERVER:8530/ClientWebService/client.asmx
    2013-01-29 09:54:01:473 1392 2364 PT WARNING: Cached cookie has expired or new PID is available
    2013-01-29 09:54:01:473 1392 2364 PT Initializing simple targeting cookie, clientId = 745eeab2-6d7e-46c5-8a49-6f50d5a6bc8f, target group = , DNS name = companyserver.companydom.local
    2013-01-29 09:54:01:473 1392 2364 PT   Server URL = http://COMPANYSERVER:8530/SimpleAuthWebService/SimpleAuth.asmx
    2013-01-29 09:55:01:999 1392 2364 Misc WARNING: Send failed with hr = 80072ee2.
    2013-01-29 09:55:01:999 1392 2364 Misc WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
    2013-01-29 09:55:01:999 1392 2364 PT   + Last proxy send request failed with hr = 0x80072EE2, HTTP status code = 0
    2013-01-29 09:55:01:999 1392 2364 PT   + Caller provided credentials = No
    2013-01-29 09:55:01:999 1392 2364 PT   + Impersonate flags = 0
    2013-01-29 09:55:01:999 1392 2364 PT   + Possible authorization schemes used =
    2013-01-29 09:55:01:999 1392 2364 PT WARNING: GetCookie failure, error = 0x80072EE2, soap client error = 5, soap error code = 0, HTTP status code = 200
    2013-01-29 09:55:01:999 1392 2364 PT WARNING: PTError: 0x80072ee2
    2013-01-29 09:55:01:999 1392 2364 PT WARNING: GetCookie_WithRecovery failed : 0x80072ee2
    2013-01-29 09:55:01:999 1392 2364 PT WARNING: RefreshCookie failed: 0x80072ee2
    2013-01-29 09:55:01:999 1392 2364 PT WARNING: RefreshPTState failed: 0x80072ee2
    2013-01-29 09:55:01:999 1392 2364 PT WARNING: Sync of Updates: 0x80072ee2
    2013-01-29 09:55:01:999 1392 2364 PT WARNING: SyncServerUpdatesInternal failed: 0x80072ee2
    2013-01-29 09:55:01:999 1392 2364 Agent   * WARNING: Failed to synchronize, error = 0x80072EE2
    2013-01-29 09:55:02:386 1392 2364 Agent   * WARNING: Exit code = 0x80072EE2
    2013-01-29 09:55:02:386 1392 2364 Agent *********
    2013-01-29 09:55:02:386 1392 2364 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2013-01-29 09:55:02:386 1392 2364 Agent *************
    2013-01-29 09:55:02:386 1392 2364 Agent WARNING: WU client failed Searching for update with error 0x80072ee2
    2013-01-29 09:55:02:403 1392 2bec AU >>##  RESUMED  ## AU: Search for updates [CallId = {84EF6BD6-BFBD-4827-94B7-11CF01F82C21}]
    2013-01-29 09:55:02:403 1392 2bec AU   # WARNING: Search callback failed, result = 0x80072EE2
    2013-01-29 09:55:02:403 1392 2bec AU   # WARNING: Failed to find updates with error code 80072EE2
    2013-01-29 09:55:02:403 1392 2bec AU #########
    2013-01-29 09:55:02:403 1392 2bec AU ##  END  ##  AU: Search for updates [CallId = {84EF6BD6-BFBD-4827-94B7-11CF01F82C21}]
    2013-01-29 09:55:02:403 1392 2bec AU #############
    2013-01-29 09:55:02:403 1392 2bec AU AU setting next detection timeout to 2013-01-29 09:45:16
    2013-01-29 09:55:07:385 1392 2364 Report REPORT EVENT: {F0F9A532-3B57-428A-A333-97752DF4EE7C} 2013-01-29 09:55:02:386+0100 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80072ee2 AutomaticUpdates Failure Software Synchronization Windows Update Client failed to detect with error 0x80072ee2.
    2013-01-29 09:55:07:436 1392 2364 Report CWERReporter::HandleEvents - WER report upload completed with status 0x8
    2013-01-29 09:55:07:436 1392 2364 Report WER Report sent: 7.6.7600.256 0x80072ee2 00000000-0000-0000-0000-000000000000 Scan 101 Managed
    2013-01-29 09:55:07:436 1392 2364 Report CWERReporter finishing event handling. (00000000)

    ***************************************************************************************************************************


    The links to http://blogs.technet.com/b/sus/archive/2008/09/25/troubleshooting-wsus.aspx and

    http://blogs.technet.com/b/sus/archive/2008/07/10/troubleshooting-wsus-clients.aspx are informative, but could not help.


    Thanks for your help.

    Best regards

    Ron

    Mittwoch, 30. Januar 2013 18:01

Alle Antworten