Anmelden
 
HomeLibraryDownloadsSupportWebcasts & EventsCommunityForenBlogs
Ressourcen für IT-Professionals >
> 
> 
SOAP Fault: 0x00012c Error

Beantwortet SOAP Fault: 0x00012c Error

  • Montag, 7. Januar 2013 05:22
     
     
    Anmelden
    0

    I have this weird error that is only affecting some Windows XP machines. I have 85 workstations, 42 Windows XP sp 3 and 43 Windows 7. All of these machines have office 2003 SP3 installed. I have only 1 2008 Enterprise WSUS server. I have 14 Windows XP machines that will not report. I have built a fresh from scratch WSUS server and I still get the same error. I have searched the web and found several ideas for a fix but nothing has been sucessfull. I have reinstalled the Windows Update Agent, Dial-A-Fix, 2 different MSFixit's, I have Approved Office 2003 SP1 and Declined it . Nothing seems to work. Any help would be great.

    Here is the client error:

    WARNING: GetCookie failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
    2013-01-06 19:54:21:925  192 7c0 PT WARNING: SOAP Fault: 0x00012c
    2013-01-06 19:54:21:925  192 7c0 PT WARNING:     faultstring:Fault occurred
    2013-01-06 19:54:21:925  192 7c0 PT WARNING:     ErrorCode:InvalidCookie(1)
    2013-01-06 19:54:21:925  192 7c0 PT WARNING:     Message:(null)
    2013-01-06 19:54:21:925  192 7c0 PT WARNING:     Method:
    2013-01-06 19:54:21:925  192 7c0 PT WARNING:     ID:d95d3d97-060a-42ab-9631-022eee9c5756
    2013-01-06 19:54:21:925  192 7c0 PT WARNING: PTError: 0x80244015
    2013-01-06 19:54:21:925  192 7c0 PT WARNING: GetCookie_WithRecovery failed : 0x80244015
    2013-01-06 19:54:21:925  192 7c0 PT WARNING: RefreshCookie failed: 0x80244015
    2013-01-06 19:54:21:925  192 7c0 PT WARNING: RefreshPTState failed: 0x80244015
    2013-01-06 19:54:22:081  192 7c0 PT WARNING: Cached cookie has expired or new PID is available

     

Alle Antworten

  • Montag, 7. Januar 2013 10:17
     
     
    Anmelden
    0

    try this:

    http://blogs.technet.com/b/sus/archive/2008/10/29/wsus-clients-fail-synchronization-with-0x80244015-and-0x8024400d-errors.aspx

    (not the blog post, but from the comments)

    1) Place the following lines in a .REG file and merge it at the WSUS client:

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate]

    "AccountDomainSid"=-

    "PingID"=-

    "SusClientId"=-

    "SusClientIdValidation"=-

    2) Perform the following in CMD prompt:

    WUAUCLT /resetauthorization  /detectnow

    WUAUCLT /r  /reportnow [this one seems wierd and likely irrelevant...Don]

    3) Monitor  %windir%\windowsupdate.log   for additional issues ... but this should correct the issue discussed in this post.

    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!)


     
  • Montag, 7. Januar 2013 14:24
     
     Beantwortet
    Anmelden
    0
    Thanks Don, I think I have the issue resolved. I rebuilt the WSUS server for the second time but this time I approved every update. Now all machines are reporting back to the WSUS server. I will keep you posted.