none
SMS_WSUS_SYNC_MANAGER 6703 Error Since Moving WSUS DB to a new MSSQL Server RRS feed

  • Question

  • Ever since I moved our WSUS DB SUSDB to a new MSSQL server, I'm seeing the following error in SCCM each time WSUS syncs, but no sync errors in WSUS. 

    I see no evidence that updates aren't syncing into SCCM, even though 'synchronizing site database' is failing.  I assume, however, that there is some kind of problem with syncing the site DB after syncing WSUS.  How do I fix this please ?

    Severity	Type	Site code	Date / Time	System	Component	Message ID	Description
    Error	Milestone	SCM	21/11/2019 17:16:40	TLK-SC-01.TRANSLINK.CO.UK	SMS_WSUS_SYNC_MANAGER	6703	 WSUS Synchronization failed.   Message: The operation has timed out.   Source: Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse.   
    Information	Milestone	SCM	21/11/2019 17:13:33	TLK-SC-01.TRANSLINK.CO.UK	SMS_WSUS_SYNC_MANAGER	6705	 WSUS Synchronization in progress. Current phase: Synchronizing site database.   
    Information	Milestone	SCM	21/11/2019 17:11:17	TLK-SC-01.TRANSLINK.CO.UK	SMS_WSUS_SYNC_MANAGER	6704	 WSUS Synchronization in progress. Current phase: Synchronizing WSUS Server.   
    Information	Milestone	SCM	21/11/2019 17:11:16	TLK-SC-01.TRANSLINK.CO.UK	SMS_WSUS_SYNC_MANAGER	6701	 WSUS Synchronization started.


    -- huddie71 ~~If you~re not seeking help or offering it, you probably shouldn~t be here.~~

    Thursday, November 21, 2019 6:59 PM

Answers

  • The following T-SQL queries resolved the issue for me and WSUS / site sync are working fine now.  Many thanks to MS Prem Support for this.  The Delete Obsolete Updates query took about 3 days to finish.  I stopped the WSUS Pool in IIS on the Software Update Point server, ran the indexing query first, then Delete Obsolete Updates, then indexing again, then started the WSUS Pool.  I then run the WSUS Cleanup Tool.  All good now.

    -- Delete Obsolete Updates
    
    USE SUSDB
    DECLARE @var1 INT
    DECLARE @msg nvarchar(100)
    CREATE TABLE #results (Col1 INT) INSERT INTO #results(Col1)
    EXEC spGetObsoleteUpdatesToCleanup
    DECLARE WC Cursor FOR SELECT Col1 FROM #results
    OPEN WC
    FETCH NEXT FROM WC INTO @var1 WHILE (@@FETCH_STATUS > -1)
    BEGIN SET @msg = 'Deleting ' + CONVERT(varchar(10), @var1) RAISERROR(@msg,0,1) WITH NOWAIT
    EXEC spDeleteUpdate @localUpdateID=@var1
    FETCH NEXT FROM WC INTO @var1
    END
    CLOSE WC
    DEALLOCATE WC
    DROP TABLE #results

    /****************************************************************************** 
    This sample T-SQL script performs basic maintenance tasks on SUSDB 
    1. Identifies indexes that are fragmented and defragments them. For certain 
       tables, a fill-factor is set in order to improve insert performance. 
       Based on MSDN sample at http://msdn2.microsoft.com/en-us/library/ms188917.aspx 
       and tailored for SUSDB requirements 
    2. Updates potentially out-of-date table statistics. 
    ******************************************************************************/ 
     
    USE SUSDB; 
    GO 
    SET NOCOUNT ON; 
     
    -- Rebuild or reorganize indexes based on their fragmentation levels 
    DECLARE @work_to_do TABLE ( 
        objectid int 
        , indexid int 
        , pagedensity float 
        , fragmentation float 
        , numrows int 
    ) 
     
    DECLARE @objectid int; 
    DECLARE @indexid int; 
    DECLARE @schemaname nvarchar(130);  
    DECLARE @objectname nvarchar(130);  
    DECLARE @indexname nvarchar(130);  
    DECLARE @numrows int 
    DECLARE @density float; 
    DECLARE @fragmentation float; 
    DECLARE @command nvarchar(4000);  
    DECLARE @fillfactorset bit 
    DECLARE @numpages int 
     
    -- Select indexes that need to be defragmented based on the following 
    -- * Page density is low 
    -- * External fragmentation is high in relation to index size 
    PRINT 'Estimating fragmentation: Begin. ' + convert(nvarchar, getdate(), 121)  
    INSERT @work_to_do 
    SELECT 
        f.object_id 
        , index_id 
        , avg_page_space_used_in_percent 
        , avg_fragmentation_in_percent 
        , record_count 
    FROM  
        sys.dm_db_index_physical_stats (DB_ID(), NULL, NULL , NULL, 'SAMPLED') AS f 
    WHERE 
        (f.avg_page_space_used_in_percent < 85.0 and f.avg_page_space_used_in_percent/100.0 * page_count < page_count - 1) 
        or (f.page_count > 50 and f.avg_fragmentation_in_percent > 15.0) 
        or (f.page_count > 10 and f.avg_fragmentation_in_percent > 80.0) 
     
    PRINT 'Number of indexes to rebuild: ' + cast(@@ROWCOUNT as nvarchar(20)) 
     
    PRINT 'Estimating fragmentation: End. ' + convert(nvarchar, getdate(), 121) 
     
    SELECT @numpages = sum(ps.used_page_count) 
    FROM 
        @work_to_do AS fi 
        INNER JOIN sys.indexes AS i ON fi.objectid = i.object_id and fi.indexid = i.index_id 
        INNER JOIN sys.dm_db_partition_stats AS ps on i.object_id = ps.object_id and i.index_id = ps.index_id 
     
    -- Declare the cursor for the list of indexes to be processed. 
    DECLARE curIndexes CURSOR FOR SELECT * FROM @work_to_do 
     
    -- Open the cursor. 
    OPEN curIndexes 
     
    -- Loop through the indexes 
    WHILE (1=1) 
    BEGIN 
        FETCH NEXT FROM curIndexes 
        INTO @objectid, @indexid, @density, @fragmentation, @numrows; 
        IF @@FETCH_STATUS < 0 BREAK; 
     
        SELECT  
            @objectname = QUOTENAME(o.name) 
            , @schemaname = QUOTENAME(s.name) 
        FROM  
            sys.objects AS o 
            INNER JOIN sys.schemas as s ON s.schema_id = o.schema_id 
        WHERE  
            o.object_id = @objectid; 
     
        SELECT  
            @indexname = QUOTENAME(name) 
            , @fillfactorset = CASE fill_factor WHEN 0 THEN 0 ELSE 1 END 
        FROM  
            sys.indexes 
        WHERE 
            object_id = @objectid AND index_id = @indexid; 
     
        IF ((@density BETWEEN 75.0 AND 85.0) AND @fillfactorset = 1) OR (@fragmentation < 30.0) 
            SET @command = N'ALTER INDEX ' + @indexname + N' ON ' + @schemaname + N'.' + @objectname + N' REORGANIZE'; 
        ELSE IF @numrows >= 5000 AND @fillfactorset = 0 
            SET @command = N'ALTER INDEX ' + @indexname + N' ON ' + @schemaname + N'.' + @objectname + N' REBUILD WITH (FILLFACTOR = 90)'; 
        ELSE 
            SET @command = N'ALTER INDEX ' + @indexname + N' ON ' + @schemaname + N'.' + @objectname + N' REBUILD'; 
        PRINT convert(nvarchar, getdate(), 121) + N' Executing: ' + @command; 
        EXEC (@command); 
        PRINT convert(nvarchar, getdate(), 121) + N' Done.'; 
    END 
     
    -- Close and deallocate the cursor. 
    CLOSE curIndexes; 
    DEALLOCATE curIndexes; 
     
     
    IF EXISTS (SELECT * FROM @work_to_do) 
    BEGIN 
        PRINT 'Estimated number of pages in fragmented indexes: ' + cast(@numpages as nvarchar(20)) 
        SELECT @numpages = @numpages - sum(ps.used_page_count) 
        FROM 
            @work_to_do AS fi 
            INNER JOIN sys.indexes AS i ON fi.objectid = i.object_id and fi.indexid = i.index_id 
            INNER JOIN sys.dm_db_partition_stats AS ps on i.object_id = ps.object_id and i.index_id = ps.index_id 
     
        PRINT 'Estimated number of pages freed: ' + cast(@numpages as nvarchar(20)) 
    END 
    GO 
     
     
    --Update all statistics 
    PRINT 'Updating all statistics.' + convert(nvarchar, getdate(), 121)  
    EXEC sp_updatestats 
    PRINT 'Done updating statistics.' + convert(nvarchar, getdate(), 121)  
    GO 
    


    -- huddie71 ~~If you~re not seeking help or offering it, you probably shouldn~t be here.~~


    • Marked as answer by huddie71 Monday, December 2, 2019 10:55 AM
    • Edited by huddie71 Monday, December 2, 2019 10:57 AM
    Monday, December 2, 2019 10:54 AM

All replies

  • This is indicative of ConfigMgr not being able to connect to or communicate with the WSUS DB.

    If you open the WSUS console on the site server, can you connect to WSUS from there?


    Jason | https://home.configmgrftw.com | @jasonsandys

    Thursday, November 21, 2019 11:50 PM
  • Hi,

    According to the error message, we can first try to run a WSUS cleanup and re-index of WSUS, here is complete WSUS & SUP Maintenance guide.

    https://support.microsoft.com/en-us/help/4490644/complete-guide-to-microsoft-wsus-and-configuration-manager-sup-maint

    If that doesn’t work, try removing WSUS database and recreating it. If you get a lot of errors while syncing the updates, then try the following steps:

    1) unselect all Classifications in SUP
    2) Perform wsusutil reset
    3) Perform sync
    4) Re add the Classifications.

    Hope above information helps.


    Best Regards,
    Tina


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

    Friday, November 22, 2019 2:29 AM
  • This is indicative of ConfigMgr not being able to connect to or communicate with the WSUS DB.

    If you open the WSUS console on the site server, can you connect to WSUS from there?


    Jason | https://home.configmgrftw.com | @jasonsandys

    Yeah, and all syncs look fine.  As you can see in the errors, WSUS seems to sync ok but SMS_WSUS_SYNC_MANAGER seems to then try to sync the site DB and fails.

    -- huddie71 ~~If you~re not seeking help or offering it, you probably shouldn~t be here.~~

    Friday, November 22, 2019 9:46 AM
  • Hi,

    According to the error message, we can first try to run a WSUS cleanup and re-index of WSUS, here is complete WSUS & SUP Maintenance guide.

    https://support.microsoft.com/en-us/help/4490644/complete-guide-to-microsoft-wsus-and-configuration-manager-sup-maint

    If that doesn’t work, try removing WSUS database and recreating it. If you get a lot of errors while syncing the updates, then try the following steps:

    1) unselect all Classifications in SUP
    2) Perform wsusutil reset
    3) Perform sync
    4) Re add the Classifications.

    Hope above information helps.



    Best Regards,
    Tina


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

    Thanks Tina.  I'm running through that Microsoft maintenance guide now, currently running the WSUS Server Cleanup Wizard.  I looked again at what I did to check security ACLs on the DB after moving it and I think I might have missed something - adding NT Authority \ Network Service.  I've added this and will test again once the Cleanup Wizard finishes and let you know how it goes.  Thanks for your helpful post.

    -- huddie71 ~~If you~re not seeking help or offering it, you probably shouldn~t be here.~~

    Friday, November 22, 2019 11:59 AM
  • It's not about the WSUS sync, it's about the communication from the site server to the WSUS instance. Also, the log doesn't show the Sync completing successfully, just starting.

    To be clear, you can open the WSUS console on the primary site server itself and connect to the WSUS instance, correct?

    Have you cleaned up the WSUS DB and optimized WSUS per https://support.microsoft.com/en-gb/help/4490644/complete-guide-to-microsoft-wsus-and-configuration-manager-sup-maint?


    Jason | https://home.configmgrftw.com | @jasonsandys

    Friday, November 22, 2019 2:40 PM
  • It's not about the WSUS sync, it's about the communication from the site server to the WSUS instance. Also, the log doesn't show the Sync completing successfully, just starting.

    To be clear, you can open the WSUS console on the primary site server itself and connect to the WSUS instance, correct?

    Have you cleaned up the WSUS DB and optimized WSUS per https://support.microsoft.com/en-gb/help/4490644/complete-guide-to-microsoft-wsus-and-configuration-manager-sup-maint?


    Jason | https://home.configmgrftw.com | @jasonsandys

    Yes to both questions, as per my previous comments.  Connectivity is not very stable from the WSUS console on my PC.  I've done all the cleanup stuff except for the WSUS Server Cleanup Wizard, which takes too long and the console gets disconnected. 

    The problem still isn't resolved, so I'm restarting the entire SCCM farm, WSUS, MSSQL and all.  Failing that this will have to go out to Microsoft Support as I've done everything recommended here.


    -- huddie71 ~~If you~re not seeking help or offering it, you probably shouldn~t be here.~~

    Friday, November 22, 2019 6:03 PM
  • Hi,

    According to the error message, we can first try to run a WSUS cleanup and re-index of WSUS, here is complete WSUS & SUP Maintenance guide.

    https://support.microsoft.com/en-us/help/4490644/complete-guide-to-microsoft-wsus-and-configuration-manager-sup-maint

    If that doesn’t work, try removing WSUS database and recreating it. If you get a lot of errors while syncing the updates, then try the following steps:

    1) unselect all Classifications in SUP
    2) Perform wsusutil reset
    3) Perform sync
    4) Re add the Classifications.

    Hope above information helps.



    Best Regards,
    Tina


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

    Thanks Tina.  I'm running through that Microsoft maintenance guide now, currently running the WSUS Server Cleanup Wizard.  I looked again at what I did to check security ACLs on the DB after moving it and I think I might have missed something - adding NT Authority \ Network Service.  I've added this and will test again once the Cleanup Wizard finishes and let you know how it goes.  Thanks for your helpful post.

    -- huddie71 ~~If you~re not seeking help or offering it, you probably shouldn~t be here.~~

    NT Authority \ Network Service and <domain>\<server hostname> for all SCCM site servers and the WSUS server are all added to accounts and ACLs in MSSQL Server.  I've run the Cleanup Wizard and all the steps in the maintenance guide.  I've cleared, resynced and added the product classifications.  Nothing works.  Any ideas ?

    -- huddie71 ~~If you~re not seeking help or offering it, you probably shouldn~t be here.~~

    Monday, November 25, 2019 12:45 PM
  • Hi,

    Considering that you have tried many methods but still doesn’t work and the resources of the forum are limited, it is recommended that you can contact Microsoft Customer Support Services (CSS) for a dedicated support.

    Here is a link for your reference: 
    https://support.microsoft.com/en-us/help/13948/global-customer-service-phone-numbers

    Best Regards,
    Tina

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

    Tuesday, November 26, 2019 8:22 AM
  • Hi,

    Considering that you have tried many methods but still doesn’t work and the resources of the forum are limited, it is recommended that you can contact Microsoft Customer Support Services (CSS) for a dedicated support.

    Here is a link for your reference: 
    https://support.microsoft.com/en-us/help/13948/global-customer-service-phone-numbers

    Best Regards,
    Tina

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

    Already have, Tina. Thanks. I'll post again once the matter is resolved. 

    I suspect that access to SUSDB is irreversibly broken and MS Premier Support will walk me through setting up a new DB and maintenance. I had no automatic maintenance set up. 


    -- huddie71 ~~If you~re not seeking help or offering it, you probably shouldn~t be here.~~

    Tuesday, November 26, 2019 9:22 AM
  • Hi,

    Thanks for your reply.

    Well noted and hope the issue will be solved soon.

    Have a nice day.

    Best Regards,
    Tina

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

    Thursday, November 28, 2019 9:18 AM
  • Hi,

    Thanks for your reply.

    Well noted and hope the issue will be solved soon.

    Have a nice day.

    Best Regards,
    Tina

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

    Microsoft have me running a T-SQL query to remove the obsolete updates. It has been running on the SUSDB for 1d 22hrs and is has only deleted 74% of the updates, so it's going to take a long time.

    -- huddie71 ~~If you~re not seeking help or offering it, you probably shouldn~t be here.~~

    Thursday, November 28, 2019 10:14 AM
  • Hi,

    Thank you for your update, any question please feel free to feedback.

    Best Regards,
    Tina


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

    Friday, November 29, 2019 7:53 AM
  • The following T-SQL queries resolved the issue for me and WSUS / site sync are working fine now.  Many thanks to MS Prem Support for this.  The Delete Obsolete Updates query took about 3 days to finish.  I stopped the WSUS Pool in IIS on the Software Update Point server, ran the indexing query first, then Delete Obsolete Updates, then indexing again, then started the WSUS Pool.  I then run the WSUS Cleanup Tool.  All good now.

    -- Delete Obsolete Updates
    
    USE SUSDB
    DECLARE @var1 INT
    DECLARE @msg nvarchar(100)
    CREATE TABLE #results (Col1 INT) INSERT INTO #results(Col1)
    EXEC spGetObsoleteUpdatesToCleanup
    DECLARE WC Cursor FOR SELECT Col1 FROM #results
    OPEN WC
    FETCH NEXT FROM WC INTO @var1 WHILE (@@FETCH_STATUS > -1)
    BEGIN SET @msg = 'Deleting ' + CONVERT(varchar(10), @var1) RAISERROR(@msg,0,1) WITH NOWAIT
    EXEC spDeleteUpdate @localUpdateID=@var1
    FETCH NEXT FROM WC INTO @var1
    END
    CLOSE WC
    DEALLOCATE WC
    DROP TABLE #results

    /****************************************************************************** 
    This sample T-SQL script performs basic maintenance tasks on SUSDB 
    1. Identifies indexes that are fragmented and defragments them. For certain 
       tables, a fill-factor is set in order to improve insert performance. 
       Based on MSDN sample at http://msdn2.microsoft.com/en-us/library/ms188917.aspx 
       and tailored for SUSDB requirements 
    2. Updates potentially out-of-date table statistics. 
    ******************************************************************************/ 
     
    USE SUSDB; 
    GO 
    SET NOCOUNT ON; 
     
    -- Rebuild or reorganize indexes based on their fragmentation levels 
    DECLARE @work_to_do TABLE ( 
        objectid int 
        , indexid int 
        , pagedensity float 
        , fragmentation float 
        , numrows int 
    ) 
     
    DECLARE @objectid int; 
    DECLARE @indexid int; 
    DECLARE @schemaname nvarchar(130);  
    DECLARE @objectname nvarchar(130);  
    DECLARE @indexname nvarchar(130);  
    DECLARE @numrows int 
    DECLARE @density float; 
    DECLARE @fragmentation float; 
    DECLARE @command nvarchar(4000);  
    DECLARE @fillfactorset bit 
    DECLARE @numpages int 
     
    -- Select indexes that need to be defragmented based on the following 
    -- * Page density is low 
    -- * External fragmentation is high in relation to index size 
    PRINT 'Estimating fragmentation: Begin. ' + convert(nvarchar, getdate(), 121)  
    INSERT @work_to_do 
    SELECT 
        f.object_id 
        , index_id 
        , avg_page_space_used_in_percent 
        , avg_fragmentation_in_percent 
        , record_count 
    FROM  
        sys.dm_db_index_physical_stats (DB_ID(), NULL, NULL , NULL, 'SAMPLED') AS f 
    WHERE 
        (f.avg_page_space_used_in_percent < 85.0 and f.avg_page_space_used_in_percent/100.0 * page_count < page_count - 1) 
        or (f.page_count > 50 and f.avg_fragmentation_in_percent > 15.0) 
        or (f.page_count > 10 and f.avg_fragmentation_in_percent > 80.0) 
     
    PRINT 'Number of indexes to rebuild: ' + cast(@@ROWCOUNT as nvarchar(20)) 
     
    PRINT 'Estimating fragmentation: End. ' + convert(nvarchar, getdate(), 121) 
     
    SELECT @numpages = sum(ps.used_page_count) 
    FROM 
        @work_to_do AS fi 
        INNER JOIN sys.indexes AS i ON fi.objectid = i.object_id and fi.indexid = i.index_id 
        INNER JOIN sys.dm_db_partition_stats AS ps on i.object_id = ps.object_id and i.index_id = ps.index_id 
     
    -- Declare the cursor for the list of indexes to be processed. 
    DECLARE curIndexes CURSOR FOR SELECT * FROM @work_to_do 
     
    -- Open the cursor. 
    OPEN curIndexes 
     
    -- Loop through the indexes 
    WHILE (1=1) 
    BEGIN 
        FETCH NEXT FROM curIndexes 
        INTO @objectid, @indexid, @density, @fragmentation, @numrows; 
        IF @@FETCH_STATUS < 0 BREAK; 
     
        SELECT  
            @objectname = QUOTENAME(o.name) 
            , @schemaname = QUOTENAME(s.name) 
        FROM  
            sys.objects AS o 
            INNER JOIN sys.schemas as s ON s.schema_id = o.schema_id 
        WHERE  
            o.object_id = @objectid; 
     
        SELECT  
            @indexname = QUOTENAME(name) 
            , @fillfactorset = CASE fill_factor WHEN 0 THEN 0 ELSE 1 END 
        FROM  
            sys.indexes 
        WHERE 
            object_id = @objectid AND index_id = @indexid; 
     
        IF ((@density BETWEEN 75.0 AND 85.0) AND @fillfactorset = 1) OR (@fragmentation < 30.0) 
            SET @command = N'ALTER INDEX ' + @indexname + N' ON ' + @schemaname + N'.' + @objectname + N' REORGANIZE'; 
        ELSE IF @numrows >= 5000 AND @fillfactorset = 0 
            SET @command = N'ALTER INDEX ' + @indexname + N' ON ' + @schemaname + N'.' + @objectname + N' REBUILD WITH (FILLFACTOR = 90)'; 
        ELSE 
            SET @command = N'ALTER INDEX ' + @indexname + N' ON ' + @schemaname + N'.' + @objectname + N' REBUILD'; 
        PRINT convert(nvarchar, getdate(), 121) + N' Executing: ' + @command; 
        EXEC (@command); 
        PRINT convert(nvarchar, getdate(), 121) + N' Done.'; 
    END 
     
    -- Close and deallocate the cursor. 
    CLOSE curIndexes; 
    DEALLOCATE curIndexes; 
     
     
    IF EXISTS (SELECT * FROM @work_to_do) 
    BEGIN 
        PRINT 'Estimated number of pages in fragmented indexes: ' + cast(@numpages as nvarchar(20)) 
        SELECT @numpages = @numpages - sum(ps.used_page_count) 
        FROM 
            @work_to_do AS fi 
            INNER JOIN sys.indexes AS i ON fi.objectid = i.object_id and fi.indexid = i.index_id 
            INNER JOIN sys.dm_db_partition_stats AS ps on i.object_id = ps.object_id and i.index_id = ps.index_id 
     
        PRINT 'Estimated number of pages freed: ' + cast(@numpages as nvarchar(20)) 
    END 
    GO 
     
     
    --Update all statistics 
    PRINT 'Updating all statistics.' + convert(nvarchar, getdate(), 121)  
    EXEC sp_updatestats 
    PRINT 'Done updating statistics.' + convert(nvarchar, getdate(), 121)  
    GO 
    


    -- huddie71 ~~If you~re not seeking help or offering it, you probably shouldn~t be here.~~


    • Marked as answer by huddie71 Monday, December 2, 2019 10:55 AM
    • Edited by huddie71 Monday, December 2, 2019 10:57 AM
    Monday, December 2, 2019 10:54 AM
  • Hi huddie71,

    Thanks for your sharing and glad the issue has been solved. To make our thread clear to read, here is a short summary for it.
     
    Problem/Symptom:
    ===================
    When moving WSUS DB to a new MSSQL Server, SCCM sync failed and encountered error SMS_WSUS_SYNC_MANAGER 6703.
     
    Solution:
    ===================
    Stopped the WSUS Pool in IIS on the Software Update Point server, ran the indexing query first, then ran Delete Obsolete Updates query, then indexing again, then started the WSUS Pool.  After then run the WSUS Cleanup Tool, the issue was solved.


    Best Regards,
    Tina

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

    Tuesday, December 3, 2019 2:06 AM