+ Post New Thread
Results 1 to 4 of 4
Windows Server 2012 Thread, WSUS failing in Technical; Since the holidays, when I try to run WSUS it tries to add a snap-in and then errors. Can anyone ...
  1. #1


    Join Date
    Sep 2007
    Location
    UK
    Posts
    5,449
    Thank Post
    1,447
    Thanked 889 Times in 570 Posts
    Rep Power
    647

    WSUS failing

    Since the holidays, when I try to run WSUS it tries to add a snap-in and then errors. Can anyone offer any suggestions please?

    I've tried all of the suggestions in the first paragraph.



    he 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 has encountered an unexpected error. This may be a transient error; try restarting the administration console. If this error persists,
    Try removing the persisted preferences for the console by deleting the wsus file under %appdata%\Microsoft\MMC\.

    System.IO.IOException -- The handshake failed due to an unexpected packet format.
    Source
    System
    Stack Trace:
    at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.ForceAuthentication(B oolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.ProcessAuthentication (LazyAsyncResult lazyResult)
    at System.Threading.ExecutionContext.RunInternal(Exec utionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
    at System.Threading.ExecutionContext.Run(ExecutionCon text executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
    at System.Threading.ExecutionContext.Run(ExecutionCon text executionContext, ContextCallback callback, Object state)
    at System.Net.TlsStream.ProcessAuthentication(LazyAsy ncResult result)
    at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
    at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)
    at System.Net.ConnectStream.WriteHeaders(Boolean async)
    ** this exception was nested inside of the following exception **

    System.Net.WebException -- The underlying connection was closed: An unexpected error occurred on a send.
    Source
    Microsoft.UpdateServices.Administration
    Stack Trace:
    at Microsoft.UpdateServices.Administration.AdminProxy .CreateUpdateServer(Object[] args)
    at Microsoft.UpdateServices.UI.AdminApiAccess.AdminAp iTools.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
    at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSum maryScopeNode.ConnectToServer()
    at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSum maryScopeNode.get_Ser

  2. #2

    sparkeh's Avatar
    Join Date
    May 2007
    Posts
    6,794
    Thank Post
    1,290
    Thanked 1,656 Times in 1,110 Posts
    Blog Entries
    22
    Rep Power
    507
    The error matches the one in this article: Issues with the WSUS 3.0 Administration Console

    This error is probably due to the WWW Publishing service being configured to allow interaction with the desktop. To solve this problem, take the following steps:
    • Open the Services snap-in (click Start, click Run, and then type services.msc).
    • Right-click the World Wide Web Publishing service and select Properties.
    • On the LogOn tab, clear the Allow service to interact with desktop check box.
    • Click OK, and then dismiss the Services snap-in.
    • From a command shell, type iisreset.
    • At this point you should be able to access the WSUS server from the console again.

    This error is caused by the issue described in KB919085 (Error message when you browse an .aspx page and the World Wide Web Publishing Service is configured to interact with the desktop: "The compiler failed with error code 128").

  3. Thanks to sparkeh from:

    laserblazer (12th September 2013)

  4. #3


    Join Date
    Sep 2007
    Location
    UK
    Posts
    5,449
    Thank Post
    1,447
    Thanked 889 Times in 570 Posts
    Rep Power
    647
    The box wasn't checked. I tried the iisreset anyway but the problem's still there.

  5. #4

    Join Date
    Jun 2008
    Posts
    719
    Thank Post
    118
    Thanked 64 Times in 52 Posts
    Rep Power
    31
    I experienced this a few times on a Windows 2003 box and the only way I resolved it was to reinstall WSUS.

  6. Thanks to Chuckster from:

    laserblazer (12th September 2013)

SHARE:
+ Post New Thread

Similar Threads

  1. GPO Automatic updates direct to MS (not WSUS) fails.
    By edutech4schools in forum Windows Server 2000/2003
    Replies: 0
    Last Post: 31st January 2011, 09:43 AM
  2. WSUS fails regularly with eventid 13042
    By mcginnr in forum Windows Server 2000/2003
    Replies: 0
    Last Post: 30th September 2009, 09:56 AM
  3. SMS WSUS Synchronization failed
    By imiddleton25 in forum Windows
    Replies: 2
    Last Post: 4th June 2009, 05:25 AM
  4. Problems with WSUS failing to download updates
    By srochford in forum Windows
    Replies: 0
    Last Post: 2nd July 2008, 10:00 PM
  5. WSUS Failing
    By m1ddy in forum Windows
    Replies: 12
    Last Post: 6th March 2008, 06:41 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •