Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Secondary Site Server SUP unable to Sync with System Center Configuration Manager 2007


Source: Microsoft Support

↑ Back to the top


RAPID PUBLISHING

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

↑ Back to the top


Symptom



When you configure a Software Update Point (SUP) role on a Secondary Site you receive an error in the WCM.log and the SUP on secondary site is not functional.  The errors are similar to the following:


From the WCM.log:

 


Failed to create instance of Microsoft.SystemsManagementServer.WSUS.WSUSServer. error = Unspecified error~ 


 


From the WSUSctrl.log:

 


Failed to create instance of Microsoft.SystemsManagementServer.WSUS.WSUSServer. error = Unspecified error~


               Failed to set WSUS Local Configuration. Will retry configuration in 1 minutes~

↑ Back to the top


Resolution



To resolve this issue re-register the wsusmsp.dll and the wsyncact.dll files.  To do this follow these steps:


 


1.       Open a CMD window and navigate to c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\.


2.       Run the following command lines in the order listed:


 


·         RegAsm.exe C:\Program Files\Microsoft Configuration Manager\bin\i386\wsyncact.dll /unregister


·         RegAsm.exe C:\Program Files\Microsoft Configuration Manager\bin\i386\wsyncact.dll


·         c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\RegAsm.exe C:\Program Files\Microsoft Configuration Manager\bin\i386\wsusmsp.dll /unregister


·         c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\RegAsm.exe C:\Program Files\Microsoft Configuration Manager\bin\i386\wsusmsp.dll


 


 


The above commands register the Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WSyncAction.WSyncAction  class  and the Microsoft.SystemsManagementServer.WSUS.WSUSServer class successfully.


 


3.       Run regedit.exe and verify that the following registry keys exist:


·         HKEY_CLASSES_ROOT\Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WSyncAction.WSyncAction


 


·         HKEY_CLASSES_ROOT\CLSID\{E5272449-2083-4020-ACEE-18A145F79A75}


 


4.       Wait for the next Sync status to see if the sync is working now.


 


Note Uninstalling and reinstalling the SUP will not resolve this issue.


 


 

↑ Back to the top


DISCLAIMER

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.


TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

↑ Back to the top


Keywords: kbnoloc, kbnomt, kbrapidpub, kb

↑ Back to the top

Article Info
Article ID : 962224
Revision : 2
Created on : 4/12/2018
Published on : 4/12/2018
Exists online : False
Views : 104