locked
SUP fails to Synchronize - Failed to create assembly 0x80131701. RRS feed

  • Question

  • Hi

    i recently performed a Site Restore of my primary site. (I migrated from 2008 - 2012R2)
    I rebuild the Site with a restored SQL DB and manually copied Sources Files.
    It seemed that everyhting works fine - except my SUP. 

    I keep getting this in my WSUSCtrl.log and Synchronization of SUP keeps failing.

    Checking runtime v4.0.30319...
    Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.3.9600.16384
    Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.3.9600.16384
    Supported WSUS version found
    Attempting connection to local WSUS server
    Successfully connected to local WSUS server
    No changes - local WSUS Server Proxy settings are correctly configured as Proxy Name  and Proxy Port 80
    Attempting connection to local WSUS server
    Successfully connected to local WSUS server
    There are no unhealthy WSUS Server components on WSUS Server myprimarysite.fqdn.local
    Successfully checked database connection on WSUS server myprimarysite.fqdn.local
    Waiting for changes for 57 minutes
    Timed Out...
    Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)
    Checking runtime v2.0.50727...
    Failed to create assembly name object for Microsoft.UpdateServices.Administration. Error = 0x80131701.

    i removed the SUP Role, removed WSUS, rebooted, reinstalled everything keeps the same. Any ideas what this could be?

    Monday, June 1, 2015 6:46 AM

All replies

  • Hi,

    Can you share the migration process you have followed?

    Is SUSDB installed on a remote SQL instance?

    Can you open WSUS console successfully?


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, June 2, 2015 6:23 AM
  • Hi,

    sure. I did a SQL Backup of CM and SQL DB,of Source Files and SCCMContentLIB
    I stopped all services, and renamed the old server in case i forgot something.
    I installed the new Server, Installed SQL, attached the DB setup everything.
    Started ConfigMgr Setup and Choose Recover a Site
    Reinstall the Site Server, Use a site DB that has been manually recovery.

    My SQL is running on the Primary Site System.
    Yes i can open the WSUS Console without issues.
    I'm also able to synchronize manually from WSUS Console without issues.

    I already removed the WSUS and reinstalled a new, fresh one with a empty DB, same problem...

    Tuesday, June 2, 2015 7:03 AM
  • Hi,

    I can confirm there is a problem after SP1 is applied, you may have to wai for a fix.

    In the meantime, if the issue is critical to you. I recommend to open a ticket with CSS support.


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Proposed as answer by gnatokulus Friday, June 5, 2015 7:53 AM
    Thursday, June 4, 2015 5:26 AM
  • Hi Daniel,

    thanks for getting back to me. I'll rise a ticket at CSS

    Friday, June 5, 2015 7:53 AM
  • Well for me I resolved it by running the following on the SUP with:
    Net stop wuauserv
    rd /s %windir%\softwaredistribution\
    Net start wuauserv
    After running the above I was able to run synchronization successfully and this is on a New CM 2012 R2 SP1 environment running on Server 2012 R2 with a remote SUP

    Thanks,

    James
    Wednesday, June 17, 2015 12:20 AM
  • Hi James,

    i've already tried that, but it did not help :(


    Regards
    Ben

    Tuesday, June 23, 2015 1:39 PM
  • Having the same issue here, did you get a resolution?

    Jonathan W Topping

    Saturday, June 27, 2015 7:26 PM
  • Hi Jonathan,

    Info from my Ticket, right now i try to deploy updates and see what's going on:

    I have received update from my Senior Specialist :

    SUP related  logs : WCM.log, WSUSCtrl.log and WSyncMgr.log
    Interesting to see is that although we see the “Failed to create assembly name object for Microsoft.UpdateServices.Administration. Error = 0x80131701” error in WCM.log and WSUSCtrl.log, it looks like WSyncmgr.log is working correctly.
     
    Failed to create assembly name object for Microsoft.UpdateServices.Administration. Error = 0x80131701.                SMS_WSUS_CONFIGURATION_MANAGER      12-Jun-15 09:20:43            9492 (0x2514)
     
    Failed to create assembly name object for Microsoft.UpdateServices.Administration. Error = 0x80131701.                SMS_WSUS_CONTROL_MANAGER   12-Jun-15 09:33:01            9504 (0x2520)
     
    Done synchronizing SMS with WSUS Server MYSUP.FQDN.local              SMS_WSUS_SYNC_MANAGER           12-Jun-15 10:00:13                19008 (0x4A40)
    Set content version of update source {6D952BC5-E644-492E-9E0D-5C1AE0B4E97F} for site RFG to 6                SMS_WSUS_SYNC_MANAGER           12-Jun-15 10:00:14            9508 (0x2524)
    ..
    Sync succeeded. Setting sync alert to canceled state on site MYS               SMS_WSUS_SYNC_MANAGER           12-Jun-15 10:00:14                9508 (0x2524)

    i'll keep this thread posted.

    Monday, June 29, 2015 10:30 AM
  • Is there any update on this?  I am also receiving the same error in SCCM 2012 R2 SP1
    Monday, July 6, 2015 1:22 AM
  • Likewise,

    Any updates?

    Tuesday, July 21, 2015 11:03 AM
  • Is sync working at all? Or are you just worried about that line in the log (Failed to create assembly name object for Microsoft.UpdateServices.Administration. Error = 0x80131701.)?

    Torsten Meringer | http://www.mssccmfaq.de

    Tuesday, July 21, 2015 11:52 AM
  • Sync has completely failed.

    A few lines after the assembly name object error, I get this:

    System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.TypeInitializationException: The type initializer for 'Microsoft.UpdateServices.Internal.ApiRemoting' threw an exception. ---> System.UnauthorizedAccessException: Access to the path 'Update Services' is denied.~   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)~   at System.IO.Directory.InternalCreateDirectory(String fullPath, String path, Object dirSecurityObj, Boolean checkHost)~   at System.IO.Directory.InternalCreateDirectoryHelper(String path, Boolean checkHost)~   at Microsoft.UpdateServices.Log.GetUsableLogFileName(String fileName, LogFileLocation& actualLogLocation)~   at Microsoft.UpdateServices.Log.InitializeFromConfig()~   at Microsoft.UpdateServices.Log.InitializeIfNeeded()~   at Microsoft.UpdateServices.Internal.ApiRemoting..cctor()~   --- End of inner exception stack trace ---~   at Microsoft.UpdateServices.Internal.ApiRemoting..ctor()~   --- End of inner exception stack trace ---~~   at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber)

    Tuesday, July 21, 2015 12:07 PM
  • HI together,

    Sync is working perfectly for me, no issues - but don't ask me why.. I tried to sync via WSUS console and it worked, afterwards configmgr was also able to sync..

    CSS told me that this is just a cosmetic problem, and has no impact on WSUS / SUP functionality.


    • Edited by gnatkopf Tuesday, August 4, 2015 12:22 PM
    Tuesday, August 4, 2015 12:21 PM
  • We had the same issue after 2012 R2 SP1 upgrade and we solved is by registering ASP.NET 2.0 :

    Stop the Web Server

    From an elevated command prompt run this command :   C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe

    Start the Web Server

    Sunday, November 15, 2015 7:34 AM
  • Hi,

    i am also getting the same error in WCM.log and WSUSCtrl.log files (Failed to create assembly name object for Microsoft.UpdateServices.Administration. Error = 0x80131701.)

    But synchronization is working fine and able to see all software updates.

    Friday, November 30, 2018 9:21 AM