WSUS Cleanup

1

Sign in to vote

Hi Dom,

You could have a look at the post below to see whether the solution provided there could be helpful.

WSUS Server Cleanup Wizard Hangs on “Deleting unused updates…”

Here's also a TechNet forum thread about this issues:

WSUS hangs on Cleanup wizard for Unused Updates, then disconnects from console

Best regards,
Leon

Blog: https://thesystemcenterblog.com LinkedIn:

Marked as answer by Felyjos Friday, December 14, 2018 3:30 AM

Monday, December 3, 2018 9:28 PM

0

Sign in to vote

Hello,

I have only 6 GB and 743 files...!

I did a reindex before starting the cleanup...

It is on F: drive with 600GB space and 492 GB free space...

Also I checked only the box for the cleanup of the unused updates all other boxes have been cleared.

I noticed it seems SQL is using full RAM …

After 4 hours

Thanks,

Dom

Security / System Center Configuration Manager Current Branch / SQL

Edited by Felyjos Monday, December 3, 2018 10:13 PM

Monday, December 3, 2018 9:38 PM

0

Sign in to vote

Now I am getting

Security / System Center Configuration Manager Current Branch / SQL

Monday, December 3, 2018 11:07 PM

1

Sign in to vote

You could try the workaround provided in this post:

1. Open a Command Prompt (Admin) and run the following command:

"C:\Program Files\Update Services\Tools\wsusutil.exe" postinstall /servicing

2. Restart the WSUS server.

Blog: https://thesystemcenterblog.com LinkedIn:

Marked as answer by Felyjos Friday, December 14, 2018 3:31 AM

Tuesday, December 4, 2018 12:31 AM

0

Sign in to vote

You could try the workaround provided in this post:

1. Open a Command Prompt (Admin) and run the following command:
"C:\Program Files\Update Services\Tools\wsusutil.exe" postinstall /servicing 
2. Restart the WSUS server.

Blog: https://thesystemcenterblog.com LinkedIn:

Hello,

What is it suppose to do? the run is 1 second and nothing is purged... If after the reboot I try the cleanup of the unused software updates again it is failing with the same error. As this task is supposedly automatically done monthly the issue is still here.

Still checking...

from the log when running this command:

2018-12-03 17:00:01  Postinstall started
2018-12-03 17:00:01  Detected role services: Api, Database, UI, Services
2018-12-03 17:00:01  Start: LoadSettingsForServicing
2018-12-03 17:00:01  Fetching SqlServerName from registry store
2018-12-03 17:00:01  Value is VRPSCCMSQL01.AD\ConfigMgr
2018-12-03 17:00:01  Instance name: VRPSCCMSQL01.AD\ConfigMgr
2018-12-03 17:00:01  End: LoadSettingsForServicing
2018-12-03 17:00:01  Stopping service WSUSService
2018-12-03 17:00:01  Stopping service W3SVC
2018-12-03 17:00:11  Servicing database...
2018-12-03 17:00:12  Servicing the database...
2018-12-03 17:00:12  Establishing DB connection...
2018-12-03 17:00:12  Checking to see if database exists...
2018-12-03 17:00:12  Database exists
2018-12-03 17:00:12  Switching database to single user mode...
2018-12-03 17:00:15  Loading install type query...
2018-12-03 17:00:15  DECLARE @currentDBVersion       int
DECLARE @scriptMajorVersion     int = (14393)
DECLARE @scriptMinorVersion     int = (0)
DECLARE @databaseMajorVersion   int 
DECLARE @databaseMinorVersion   int 
DECLARE @databaseBuildNumber    nvarchar(10)
IF NOT EXISTS(SELECT * FROM sys.databases WHERE name='SUSDB')
BEGIN
    SELECT 1
END
ELSE
BEGIN
    SET @currentDBVersion = (SELECT SchemaVersion FROM SUSDB.dbo.tbSchemaVersion WHERE ComponentName = 'CoreDB')
    SET @databaseBuildNumber = (SELECT BuildNumber FROM SUSDB.dbo.tbSchemaVersion WHERE ComponentName = 'CoreDB')
    DECLARE @delimiterPosition INT = CHARINDEX('.', @databaseBuildNumber)
    IF (@delimiterPosition = 0)
    BEGIN
        RAISERROR('Invalid schema version number', 16, 1) with nowait
        return 
    END 
    SET @databaseMajorVersion = SUBSTRING(@databaseBuildNumber, 1, @delimiterPosition - 1)
    SET @databaseMinorVersion = SUBSTRING(@databaseBuildNumber, (@delimiterPosition + 1), (10 - @delimiterPosition))
    IF @currentDBVersion < 926
    BEGIN
        SELECT 3
    END
    ELSE
    BEGIN
        IF (@scriptMajorVersion > @databaseMajorVersion OR
           (@scriptMajorVersion = @databaseMajorVersion AND @scriptMinorVersion > @databaseMinorVersion))
        BEGIN
            SELECT 2
        END
        ELSE IF (@scriptMajorVersion = @databaseMajorVersion AND
                 @scriptMinorVersion = @databaseMinorVersion)
        BEGIN
            SELECT 0
        END
        ELSE
        BEGIN
            SELECT 4
        END
    END
END

2018-12-03 17:00:15  Install type is: Reinstall
2018-12-03 17:00:15  Install type is Reinstall, but should be Upgrade.  Cannot service the database
2018-12-03 17:00:15  Swtching DB to multi-user mode......
2018-12-03 17:00:15  Finished setting multi-user mode
2018-12-03 17:00:15  Disposing Connection
2018-12-03 17:00:15  Clearing Connection Pools
2018-12-03 17:00:15  Starting service W3SVC
2018-12-03 17:00:15  Starting service WSUSService
2018-12-03 17:00:16  Postinstall completed

it seems there an issue with the message: " 2018-12-03 17:00:15 Install type is Reinstall, but should be Upgrade. Cannot service the database"

Thanks,

Dom

Security / System Center Configuration Manager Current Branch / SQL

Edited by Felyjos Tuesday, December 4, 2018 1:40 AM

Tuesday, December 4, 2018 1:36 AM

1

Sign in to vote

There was an issue with an update in Windows Server 2012/2012R2, the interesting part is that you have Windows Server 2016 and this issue still occurs...

Ensure first of all that your WSUS server has all the latest updates & rollups installed.

The post below describes this issue, but as mentioned earlier it was for 2012/2012R2..

https://www.urtech.ca/2016/08/solved-wsus-server-will-not-launch-after-august-patch-cycle-including-kb3159706/

You could also check the following steps mentioned in the post:

After running the command: "C:\Program Files\Update Services\Tools\wsusutil.exe postinstall /servicing"

Add the following roles from Server Manager:

Select HTTP Activation under .NET Framework 4.5 Features
Restart the WSUS service.

Blog: https://thesystemcenterblog.com LinkedIn:

Marked as answer by Felyjos Friday, December 14, 2018 3:31 AM

Tuesday, December 4, 2018 8:04 AM

1

Sign in to vote

Hello Dom,

How many updates and clients are there in your WSUS? And when was the last time you clean up the server? It does take lot's of time to complete the maintenance if there are too many updates and clients and you have not run the SCW periodically.

There are really two different options you can take here:

1. Reinstall WSUS with a fresh database.

2. Ensure you have a backup of the SUSDB then run a re-index. When that completes, run the following stored procedure in SQL Server Management Studio or SQL Server Management Studio Express. After this finishes, follow all of the above instructions for running maintenance. This last step is necessary because the stored procedure here only removes unused updates and update revisions.

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

Refer to the following article to get more detailed information.

The complete guide to Microsoft WSUS and Configuration Manager SUP maintenance
https://blogs.technet.microsoft.com/configurationmgr/2016/01/26/the-complete-guide-to-microsoft-wsus-and-configuration-manager-sup-maintenance/

And I also find another post for you, review the replies and I think it would be helpful.

https://social.technet.microsoft.com/Forums/ie/en-US/7b12f8b2-d0e6-4f63-a98a-019356183c29/getting-past-wsus-cleanup-wizard-time-out-removing-unnecessary-updates?forum=winserverwsus

Hope my answer could help you.

Best Regards,
Ray

Please remember to mark the replies as answers if they help.

If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

Marked as answer by Felyjos Friday, December 14, 2018 3:31 AM

Tuesday, December 4, 2018 10:02 AM

0

Sign in to vote

Hello Ray,

9,000+ updates and 25,000+ clients are there in our WSUS

There was no cleanup done since the installation in September 2017 (14 months)

What is the "normal" size / number of updates which should remain in the database?

Thanks,

Dom

Security / System Center Configuration Manager Current Branch / SQL

Edited by Felyjos Tuesday, December 4, 2018 6:42 PM

Tuesday, December 4, 2018 11:55 AM

0

Sign in to vote

There was an issue with an update in Windows Server 2012/2012R2, the interesting part is that you have Windows Server 2016 and this issue still occurs...

Ensure first of all that your WSUS server has all the latest updates & rollups installed.

The post below describes this issue, but as mentioned earlier it was for 2012/2012R2..

https://www.urtech.ca/2016/08/solved-wsus-server-will-not-launch-after-august-patch-cycle-including-kb3159706/

You could also check the following steps mentioned in the post:

After running the command: "C:\Program Files\Update Services\Tools\wsusutil.exe postinstall /servicing"

Add the following roles from Server Manager:

Select HTTP Activation under .NET Framework 4.5 Features

Restart the WSUS service.

Blog: https://thesystemcenterblog.com LinkedIn:

Hello,

The patches are up-to-date with the November cycle 11/13/2018

the command: "C:\Program Files\Update Services\Tools\wsusutil.exe postinstall /servicing" has already been run.

HTTP Activation under .NET Framework 4.6 Features is already set on 4.6 NOT 4.5

Thanks,

Dom

Security / System Center Configuration Manager Current Branch / SQL

Edited by Felyjos Tuesday, December 4, 2018 2:53 PM

Tuesday, December 4, 2018 2:53 PM

0

Sign in to vote

Hello Dom,

How many updates and clients are there in your WSUS? And when was the last time you clean up the server? It does take lot's of time to complete the maintenance if there are too many updates and clients and you have not run the SCW periodically.

There are really two different options you can take here:

1. Reinstall WSUS with a fresh database.

2. Ensure you have a backup of the SUSDB then run a re-index. When that completes, run the following stored procedure in SQL Server Management Studio or SQL Server Management Studio Express. After this finishes, follow all of the above instructions for running maintenance. This last step is necessary because the stored procedure here only removes unused updates and update revisions.
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
Refer to the following article to get more detailed information.

The complete guide to Microsoft WSUS and Configuration Manager SUP maintenance
https://blogs.technet.microsoft.com/configurationmgr/2016/01/26/the-complete-guide-to-microsoft-wsus-and-configuration-manager-sup-maintenance/

And I also find another post for you, review the replies and I think it would be helpful.

https://social.technet.microsoft.com/Forums/ie/en-US/7b12f8b2-d0e6-4f63-a98a-019356183c29/getting-past-wsus-cleanup-wizard-time-out-removing-unnecessary-updates?forum=winserverwsus

Hope my answer could help you.

Best Regards,
Ray

Please remember to mark the replies as answers if they help.

If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

Hello,

this is the URL I am following:

The complete guide to Microsoft WSUS and Configuration Manager SUP maintenance
https://blogs.technet.microsoft.com/configurationmgr/2016/01/26/the-complete-guide-to-microsoft-wsus-and-configuration-manager-sup-maintenance/

the SQL Query statement is running for the last two hours

Thanks,
Dom

Security / System Center Configuration Manager Current Branch / SQL

Edited by Felyjos Tuesday, December 4, 2018 5:45 PM

Tuesday, December 4, 2018 5:42 PM

0

Sign in to vote

Hello,

the SQL Query statement is running for the last five (5) hours now... still deleting... anything to check to see if it is going well..

six (6) hours now... still deleting...

seven (7) hours now... still deleting...

eight (8) hours now ... still deleting ...

What will be the next step(s) after the database is cleaned up. Any task(s) to run again on the WSUS?SUP servers?

Thanks,
Dom

Security / System Center Configuration Manager Current Branch / SQL

Edited by Felyjos Wednesday, December 5, 2018 12:20 AM

Tuesday, December 4, 2018 8:26 PM

1

Sign in to vote

Hello,

At this moment, I think we should wait until the deletion is complete. This script is used to remove unused updates and update revisions and when it is done check if you could run server cleanup wizard successfully. I think it should be OK then.

Then you could perform other WSUS maintenance job, such as backup the WSUS database, re-index the WSUS database, decline superseded updates, etc.

And don't forget to run WSUS maintenance regularly from now on.

Hope my answer could help you.

Best Regards,
Ray

Please remember to mark the replies as answers if they help.

If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

Marked as answer by Felyjos Friday, December 14, 2018 3:31 AM

Wednesday, December 5, 2018 5:08 AM

0

Sign in to vote

Hello,

It ids done after 14 hours

Deleting64739

Deleting64615

Deleting64613

Deleting64460

Deleting64333

Deleting64331

Deleting64221

Deleting64213

Deleting64091

Deleting64089

Deleting64087

Deleting59077

Deleting40322

Deleting40316

Deleting29258

these were the last ones...

Starting the WSUS Clean up tasks...

Thanks,

Dom

Security / System Center Configuration Manager Current Branch / SQL

Edited by Felyjos Wednesday, December 5, 2018 2:45 PM

Wednesday, December 5, 2018 2:39 PM

0

Sign in to vote

Hello,

1. connection failure again...

I did the cleanup option by option and only one is failing with the above error: unneeded update files.

2. why I have 5 connections to the same server in the console?

Thank,

Dom

Security / System Center Configuration Manager Current Branch / SQL

Edited by Felyjos Wednesday, December 5, 2018 8:40 PM

Wednesday, December 5, 2018 7:52 PM

1

Sign in to vote

There's more to WSUS maintenance than just the SCW. What about sync logs, what about the SQL indexing scripts, what about drivers, what about compressing update revisions, the obsolete update removals that you're currently doing (super slowly). Here's part 8 of my blog series that deals with WSUS maintenance.

https://www.ajtek.ca/wsus/how-to-setup-manage-and-maintain-wsus-part-8-wsus-server-maintenance/

The spGetObsoleteUpdatesToCleanup that you're running can take a very long time... be patient with it. Don't worry about the MMC console while it's happening.

Adam Marshall, MCSE: Security
https://www.ajtek.ca
Microsoft MVP - Windows and Devices for IT

Wednesday, December 5, 2018 9:27 PM

1

Sign in to vote

And to answer your question about the 5 servers - remove all of them but 1. How they got there, we don't know. Probably added manually for SSL/port changes or something along the lines of that.

Adam Marshall, MCSE: Security
https://www.ajtek.ca
Microsoft MVP - Windows and Devices for IT

Edited by AJTek.caMVP Wednesday, December 5, 2018 9:30 PM

Wednesday, December 5, 2018 9:29 PM

0

Sign in to vote

I removed all of them but 1

Thanks,

Dom

Security / System Center Configuration Manager Current Branch / SQL

Thursday, December 6, 2018 8:03 PM

0

Sign in to vote

After the cleanup on the downstream servers (2) it was okay I could reconnect the WSUS local server but on the upstream I have an error:

Nothing different done on the three servers but this one is having issue to reconnect...

The port is correct 8531

SSL is correct.

in ISS the port 8531 is configured

but I am getting an error when click on it to browse it...

Service Unavailable

HTTP Error 503. The service is unavailable.

Checking the logs now

Thanks,

Dom

Security / System Center Configuration Manager Current Branch / SQL

Edited by Felyjos Thursday, December 6, 2018 8:41 PM

Thursday, December 6, 2018 8:07 PM

0

Sign in to vote

I restarted the WSUS Pool and the connection is working now...

for few seconds and then again

Service is running

I did all of them one by one three went through and two remains, the ones which are checked.

The top one will go half way green during its steps then failed

The third one will failed after sometime but never show any green ...

Thanks,

Dom

Security / System Center Configuration Manager Current Branch / SQL

Edited by Felyjos Thursday, December 6, 2018 9:27 PM

Thursday, December 6, 2018 8:48 PM

0

Sign in to vote

only one remaining after multiple retries

Security / System Center Configuration Manager Current Branch / SQL

Thursday, December 6, 2018 11:46 PM

1

Sign in to vote

Hello,

Thanks for your feedback.

Considering it has not been maintained for such a long time, it makes sense that it needs to run several times and it takes a long time to complete.

If there is any update, feel free to feedback.

Best Regards,
Ray

Please remember to mark the replies as answers if they help.

If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

Marked as answer by Felyjos Friday, December 14, 2018 3:32 AM

Friday, December 7, 2018 9:03 AM

0

Sign in to vote

Hello Ray,

After several attempts (15) it seems I am in a loop...

Application Logs:

Log Name:      Application
Source:        Windows Server Update Services
Date:          12/7/2018 7:43:16 AM
Event ID:      501
Task Category: 1
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      VRPSCCMSU01.ad.medctr.ucla.edu
Description:
Update Services Service Started
============================================================================================================================================================================
Log Name:      Application
Source:        Windows Server Update Services
Date:          12/7/2018 7:43:17 AM
Event ID:      7032
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      VRPSCCMSU01.ad.medctr.ucla.edu
Description:
The 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.

System.Net.Sockets.SocketException -- An existing connection was forcibly closed by the remote host

Source
System.Windows.Forms

Stack Trace:
   at System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous)
   at System.Windows.Forms.Control.Invoke(Delegate method, Object[] args)
   at Microsoft.UpdateServices.UI.SnapIn.Wizards.ServerCleanup.ServerCleanupWizard.OnCleanupComplete(Object sender, PerformCleanupCompletedEventArgs e)
============================================================================================================================================================================
Log Name:      Application
Source:        Windows Server Update Services
Date:          12/7/2018 7:43:27 AM
Event ID:      10021
Task Category: 7
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      VRPSCCMSU01.ad.medctr.ucla.edu
Description:
The catalog was last synchronized successfully 1 or more days ago.
============================================================================================================================================================================
Log Name:      Application
Source:        Windows Server Update Services
Date:          12/7/2018 7:43:27 AM
Event ID:      10032
Task Category: 7
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      VRPSCCMSU01.ad.medctr.ucla.edu
Description:
The server is failing to download some updates.
============================================================================================================================================================================
Log Name:      Application
Source:        Windows Server Update Services
Date:          12/7/2018 7:44:35 AM
Event ID:      502
Task Category: 1
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      VRPSCCMSU01.ad.medctr.ucla.edu
Description:
Update Services Service Has Stopped
============================================================================================================================================================================

All this series of errors are showing in the event log, if I restart the Update Services , then I Start the WSUSPool , then I start the "Delete Unneeded Update Files" then after 3 minutes

it is happening again and again... anything else to check, to do?

Thanks,
Dom

Security / System Center Configuration Manager Current Branch / SQL

Friday, December 7, 2018 3:56 PM

0

Sign in to vote

from this article...

https://www.dell.com/support/article/mk/en/mkdhs1/sln286548/windows-server-wsus-administration-console-is-unable-to-connect-to-wsus-server-via-remote-api?lang=en

I noticed "The Update Orchestrator Service for Windows Update service stopped ... " almost immediately after I start it ... within 60 seconds, is it expected?

I checked the ISAPI Filters

They look good... but still failing

The 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.

System.Net.Sockets.SocketException -- An existing connection was forcibly closed by the remote host

Source
System.Windows.Forms

Stack Trace:
   at System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous)
   at System.Windows.Forms.Control.Invoke(Delegate method, Object[] args)
   at Microsoft.UpdateServices.UI.SnapIn.Wizards.ServerCleanup.ServerCleanupWizard.OnCleanupComplete(Object sender, PerformCleanupCompletedEventArgs e)

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.

System.Net.Sockets.SocketException -- An existing connection was forcibly closed by the remote host

Source
System.Windows.Forms

Stack Trace:
   at System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous)
   at System.Windows.Forms.Control.Invoke(Delegate method, Object[] args)
   at Microsoft.UpdateServices.UI.SnapIn.Wizards.ServerCleanup.ServerCleanupWizard.OnCleanupComplete(Object sender, PerformCleanupCompletedEventArgs e)

So the steps which worked for other options were:

Start Update Orchestrator for Windows Update service

Start WSUSPool

Start the WSUS Console

Start the WSUS Cleanup wizard

but for this last option it did not work after 20 attempts!!

Thanks,

Dom

Security / System Center Configuration Manager Current Branch / SQL

Edited by Felyjos Friday, December 7, 2018 11:56 PM

Friday, December 7, 2018 11:06 PM

1

Sign in to vote

Hello Dom,

It seems that this database issue is bigger than we thought before.

Well, at this moment, we could recreate the SUSDB and WSUS Content folder. With that, we could start over in WSUS with a fresh database. Refer to the following article.

Recreating the SUSDB and WSUS Content folder for a Windows Server 2012 based WSUS computer
https://blogs.technet.microsoft.com/sus/2016/10/18/recreating-the-susdb-and-wsus-content-folder-for-a-windows-server-2012-based-wsus-computer/

This is almost the same as re-install the WSUS. However, re-installing the WSUS is also worth considering. This won't take too much time and effort, except for the first sync that would take some time. If all goes well, the clients will not be affected much.

Best Regards,
Ray

Please remember to mark the replies as answers if they help.

If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

Marked as answer by Felyjos Friday, December 14, 2018 3:32 AM

Monday, December 10, 2018 10:02 AM

0

Sign in to vote

Hello Dom,

It seems that this database issue is bigger than we thought before.

Well, at this moment, we could recreate the SUSDB and WSUS Content folder. With that, we could start over in WSUS with a fresh database. Refer to the following article.

Recreating the SUSDB and WSUS Content folder for a Windows Server 2012 based WSUS computer
https://blogs.technet.microsoft.com/sus/2016/10/18/recreating-the-susdb-and-wsus-content-folder-for-a-windows-server-2012-based-wsus-computer/

This is almost the same as re-install the WSUS. However, re-installing the WSUS is also worth considering. This won't take too much time and effort, except for the first sync that would take some time. If all goes well, the clients will not be affected much.

Best Regards,
Ray

Please remember to mark the replies as answers if they help.

If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

Hello Ray,

1. let me try a recreation of SUSDB. As I have three Software Update Points I have to repeat the tasks at least when common on the three servers, isn't it?

(Stop the WSUS service and IIS Service)

2. Should I have a unique WSUSUpdates folder? or should I have three WSUSUpdates folders one per SUP server?

\\ServerName\WSUSUpdates?

3. when reinstalling SUSDB using the command

.\Wsusutil.exe postinstall SQL_INSTANCE_NAME=”VRPSCCMSQL01\ConfigMgr” CONTENT_DIR=”F:\WSUS”

on the VRPSCMSU01 I do not see the port allocation which should be 8531 not 8530 or 80...?

Apparently I need also to uninstall the SUP from SCCM?

Thanks,
Dom

Security / System Center Configuration Manager Current Branch / SQL

Edited by Felyjos Monday, December 10, 2018 6:12 PM

Monday, December 10, 2018 3:04 PM

0

Sign in to vote

Hello,

I am getting an error on IIS:

2018-12-10 10:12:51  Postinstall started
2018-12-10 10:12:51  Detected role services: Api, Database, UI, Services
2018-12-10 10:12:51  Start: LoadSettingsFromParameters
2018-12-10 10:12:51  Content local is: True
2018-12-10 10:12:51  Content directory is: F:\WSUSUpdates
2018-12-10 10:12:51  SQL instname is: VRPSCCMSQL01\ConfigMgr
2018-12-10 10:12:51  End: LoadSettingsFromParameters
2018-12-10 10:12:51  Start: Run
2018-12-10 10:12:51  Fetching WsusAdministratorsSid from registry store
2018-12-10 10:12:51  Value is S-1-5-21-3958249549-1187530241-1261074650-1006
2018-12-10 10:12:51  Fetching WsusReportersSid from registry store
2018-12-10 10:12:51  Value is S-1-5-21-3958249549-1187530241-1261074650-1007
2018-12-10 10:13:01  Configuring content directory...
2018-12-10 10:13:01  Configuring groups...
2018-12-10 10:13:01  Starting group configuration for WSUS Administrators...
2018-12-10 10:13:01  Found group in regsitry, attempting to use it...
2018-12-10 10:13:03  Writing group to registry...
2018-12-10 10:13:03  Finished group creation
2018-12-10 10:13:03  Starting group configuration for WSUS Reporters...
2018-12-10 10:13:03  Found group in regsitry, attempting to use it...
2018-12-10 10:13:03  Writing group to registry...
2018-12-10 10:13:03  Finished group creation
2018-12-10 10:13:03  Configuring permissions...
2018-12-10 10:13:03  Fetching content directory...
2018-12-10 10:13:03  Fetching ContentDir from registry store
2018-12-10 10:13:03  Value is F:\WSUSUpdates
2018-12-10 10:13:03  Fetching group SIDs...
2018-12-10 10:13:03  Fetching WsusAdministratorsSid from registry store
2018-12-10 10:13:03  Value is S-1-5-21-3958249549-1187530241-1261074650-1006
2018-12-10 10:13:03  Fetching WsusReportersSid from registry store
2018-12-10 10:13:03  Value is S-1-5-21-3958249549-1187530241-1261074650-1007
2018-12-10 10:13:03  Creating group principals...
2018-12-10 10:13:03  Granting directory permissions...
2018-12-10 10:13:03  Granting permissions on content directory...
2018-12-10 10:13:03  Granting registry permissions...
2018-12-10 10:13:03  Granting registry permissions...
2018-12-10 10:13:03  Granting registry permissions...
2018-12-10 10:13:03  Configuring shares...
2018-12-10 10:13:03  Configuring network shares...
2018-12-10 10:13:03  Fetching content directory...
2018-12-10 10:13:03  Fetching ContentDir from registry store
2018-12-10 10:13:03  Value is F:\WSUSUpdates
2018-12-10 10:13:03  Fetching WSUS admin SID...
2018-12-10 10:13:03  Fetching WsusAdministratorsSid from registry store
2018-12-10 10:13:03  Value is S-1-5-21-3958249549-1187530241-1261074650-1006
2018-12-10 10:13:03  Content directory is local, creating content shares...
2018-12-10 10:13:03  Creating share "UpdateServicesPackages" with path "F:\WSUSUpdates\UpdateServicesPackages" and description "A network share to be used by client systems for collecting all software packages (usually applications) published on this WSUS system."
2018-12-10 10:13:03  Deleting existing share...
2018-12-10 10:13:03  Creating share...
2018-12-10 10:13:03  Share successfully created
2018-12-10 10:13:03  Creating share "WsusContent" with path "F:\WSUSUpdates\WsusContent" and description "A network share to be used by Local Publishing to place published content on this WSUS system."
2018-12-10 10:13:03  Deleting existing share...
2018-12-10 10:13:03  Creating share...
2018-12-10 10:13:03  Share successfully created
2018-12-10 10:13:03  Creating share "WSUSTemp" with path "C:\Program Files\Update Services\LogFiles\WSUSTemp" and description "A network share used by Local Publishing from a Remote WSUS Console Instance."
2018-12-10 10:13:03  Deleting existing share...
2018-12-10 10:13:03  Creating share...
2018-12-10 10:13:04  Share successfully created
2018-12-10 10:13:04  Finished creating content shares
2018-12-10 10:13:04  Stopping service WSUSService
2018-12-10 10:13:04  Stopping service W3SVC
2018-12-10 10:13:04  Configuring database...
2018-12-10 10:13:04  Configuring the database...
2018-12-10 10:13:04  Establishing DB connection...
2018-12-10 10:13:04  Checking to see if database exists...
2018-12-10 10:13:04  Database does not exist
2018-12-10 10:13:04  Loading install type query...
2018-12-10 10:13:04  DECLARE @currentDBVersion       int
DECLARE @scriptMajorVersion     int = (14393)
DECLARE @scriptMinorVersion     int = (0)
DECLARE @databaseMajorVersion   int 
DECLARE @databaseMinorVersion   int 
DECLARE @databaseBuildNumber    nvarchar(10)
IF NOT EXISTS(SELECT * FROM sys.databases WHERE name='SUSDB')
BEGIN
    SELECT 1
END
ELSE
BEGIN
    SET @currentDBVersion = (SELECT SchemaVersion FROM SUSDB.dbo.tbSchemaVersion WHERE ComponentName = 'CoreDB')
    SET @databaseBuildNumber = (SELECT BuildNumber FROM SUSDB.dbo.tbSchemaVersion WHERE ComponentName = 'CoreDB')
    DECLARE @delimiterPosition INT = CHARINDEX('.', @databaseBuildNumber)
    IF (@delimiterPosition = 0)
    BEGIN
        RAISERROR('Invalid schema version number', 16, 1) with nowait
        return 
    END 
    SET @databaseMajorVersion = SUBSTRING(@databaseBuildNumber, 1, @delimiterPosition - 1)
    SET @databaseMinorVersion = SUBSTRING(@databaseBuildNumber, (@delimiterPosition + 1), (10 - @delimiterPosition))
    IF @currentDBVersion < 926
    BEGIN
        SELECT 3
    END
    ELSE
    BEGIN
        IF (@scriptMajorVersion > @databaseMajorVersion OR
           (@scriptMajorVersion = @databaseMajorVersion AND @scriptMinorVersion > @databaseMinorVersion))
        BEGIN
            SELECT 2
        END
        ELSE IF (@scriptMajorVersion = @databaseMajorVersion AND
                 @scriptMinorVersion = @databaseMinorVersion)
        BEGIN
            SELECT 0
        END
        ELSE
        BEGIN
            SELECT 4
        END
    END
END

2018-12-10 10:13:04  Install type is: Fresh
2018-12-10 10:13:04  Creating database...
2018-12-10 10:13:04  Disposing Connection
2018-12-10 10:13:04  Clearing Connection Pools
2018-12-10 10:13:07  Nonqualified transactions are being rolled back. Estimated rollback completion: 0%.
2018-12-10 10:13:07  Nonqualified transactions are being rolled back. Estimated rollback completion: 100%.
2018-12-10 10:13:07  Changed database context to 'SUSDB'.
2018-12-10 10:13:08  Changed database context to 'SUSDB'.
2018-12-10 10:13:08  Creating Procedures spDropForeignKeyConstraint
2018-12-10 10:13:08  Adding function spDropTableColumnIfExists
2018-12-10 10:13:08  Adding function spAddTableColumnIfNotExists
2018-12-10 10:13:08  Adding function spDropPrimaryKeyConstraint
2018-12-10 10:13:08  Creating table dbo.tbPrerequisiteDependency
2018-12-10 10:13:08  Creating table dbo.tbBundleDependency
2018-12-10 10:13:08  Creating table tbUpdateStatusPerComputer
2018-12-10 10:13:08  Creating table tbUpdateSummaryForAllComputers
2018-12-10 10:13:08  Creating table tbComputerSummaryForMicrosoftUpdates
2018-12-10 10:13:08  Creating table dbo.tbRequestedTargetGroup
2018-12-10 10:13:08  Creating table dbo.tbRequestedTargetGroupsForTarget
2018-12-10 10:13:08  Creating table tbDeletedComputer
2018-12-10 10:13:08  Creating table dbo.tbComputerTargetDetail
2018-12-10 10:13:08  Creating table dbo.tbComputerTarget
2018-12-10 10:13:08  Creating table dbo.tbClientWithRecentNameChange
2018-12-10 10:13:08  Creating table dbo.tbDownstreamServerTarget
2018-12-10 10:13:08  Creating table dbo.tbDownstreamServerSummaryRollup
2018-12-10 10:13:08  Creating table dbo.tbDownstreamServerClientSummaryRollup
2018-12-10 10:13:08  Creating table dbo.tbDownstreamServerClientActivityRollup
2018-12-10 10:13:08  Creating table dbo.tbTarget
2018-12-10 10:13:08  Creating table dbo.tbTargetType
2018-12-10 10:13:08  Creating table dbo.tbDeployment
2018-12-10 10:13:08  tbDeployment does not exist, creating it now
2018-12-10 10:13:08  Creating table dbo.tbDeadDeployment
2018-12-10 10:13:08  Creating table dbo.tbRevisionLanguage
2018-12-10 10:13:08  Creating table dbo.tbProperty
2018-12-10 10:13:08  Creating table dbo.tbRevisionExtendedProperty
2018-12-10 10:13:08  Creating table dbo.tbKBArticleForRevision
2018-12-10 10:13:08  Creating table dbo.tbMoreInfoURLForRevision
2018-12-10 10:13:08  Creating table dbo.tbSecurityBulletinForRevision
2018-12-10 10:13:08  Creating table dbo.tbLocalizedPropertyForRevision
2018-12-10 10:13:08  Creating table dbo.tbFileForRevision
2018-12-10 10:13:08  Creating table dbo.tbFileHash
2018-12-10 10:13:08  Creating table dbo.tbRevisionSupersedesUpdate
2018-12-10 10:13:08  Creating table dbo.tbInstalledUpdateSufficientForPrerequisite
2018-12-10 10:13:08  Creating table dbo.tbBundleAtLeastOne
2018-12-10 10:13:08  Creating table dbo.tbBundleAll
2018-12-10 10:13:08  Creating table dbo.tbPrerequisite
2018-12-10 10:13:08  Creating table dbo.tbDriver
2018-12-10 10:13:08  Creating table dbo.tbCompatiblePrinterProvider
2018-12-10 10:13:08  Creating table dbo.tbDriverClass
2018-12-10 10:13:09  Creating table dbo.tbTargetGroup
2018-12-10 10:13:09  Creating table dbo.tbFlattenedTargetGroup
2018-12-10 10:13:10  Creating table dbo.tbTargetGroupType
2018-12-10 10:13:10  Creating table dbo.tbExpandedTargetInTargetGroup
2018-12-10 10:13:11  Creating table dbo.tbTargetInTargetGroup
2018-12-10 10:13:11  Creating table dbo.tbEulaProperty
2018-12-10 10:13:11  Creating table dbo.tbEulaAcceptance
2018-12-10 10:13:11  Creating table dbo.tbLocalizedProperty
2018-12-10 10:13:11  Creating table dbo.tbFile
2018-12-10 10:13:11  Creating table dbo.tbXml
2018-12-10 10:13:11  Creating table dbo.tbGroupAuthorization
2018-12-10 10:13:11  Creating table dbo.tbAuthorization
2018-12-10 10:13:11  Creating table dbo.tbFileOnServer
2018-12-10 10:13:11  Creating table dbo.tbFileDownloadProgress
2018-12-10 10:13:11  Creating table dbo.tbSingletonData
2018-12-10 10:13:11  Creating table dbo.tbReference
2018-12-10 10:13:11  Creating table dbo.tbFrontEndServersHealth
2018-12-10 10:13:11  Creating table dbo.tbConfigurationC
2018-12-10 10:13:11  Creating table dbo.tbConfigurationB
2018-12-10 10:13:11  Creating table dbo.tbConfigurationA
2018-12-10 10:13:11  Creating table dbo.tbConfiguration
2018-12-10 10:13:11  Creating table dbo.tbImplicitCategory
2018-12-10 10:13:11  Creating table dbo.tbCategoryInSubscription
2018-12-10 10:13:11  Creating table dbo.tbLanguageInSubscription
2018-12-10 10:13:11  Creating table dbo.tbSchedule
2018-12-10 10:13:11  Creating table dbo.tbEmailNotificationRecipient
2018-12-10 10:13:11  Creating table dbo.tbRevisionInCategory
2018-12-10 10:13:11  Creating table dbo.tbCategory
2018-12-10 10:13:11  Creating table dbo.tbRevision
2018-12-10 10:13:11  Creating table dbo.tbRevisionExtendedLanguageMask
2018-12-10 10:13:11  Creating table dbo.tbUpdate
2018-12-10 10:13:11  Creating table dbo.tbUpdateType
2018-12-10 10:13:11  Creating table dbo.tbUpdateFlag
2018-12-10 10:13:11  Creating table dbo.tbHandler
2018-12-10 10:13:11  Creating table dbo.tbLanguage
2018-12-10 10:13:11  Creating table dbo.tbCategoryType
2018-12-10 10:13:11  Creating table dbo.tbStateMachine
2018-12-10 10:13:11  Creating table dbo.tbStateMachineState
2018-12-10 10:13:11  Creating table dbo.tbStateMachineEvent
2018-12-10 10:13:11  Creating table dbo.tbStateMachineTransition
2018-12-10 10:13:11  Creating table dbo.tbStateMachineEventTransitionLog
2018-12-10 10:13:11  Adding View vwStateMachineEventTransitionLog
2018-12-10 10:13:11  Creating table dbo.tbNotificationEvent
2018-12-10 10:13:11  Creating table dbo.tbChangeTracking
2018-12-10 10:13:11  Creating table dbo.tbFlattenedRevisionInCategory
2018-12-10 10:13:11  Creating table dbo.tbServerSyncResult
2018-12-10 10:13:11  Creating table dbo.tbAutoDeploymentRule
2018-12-10 10:13:11  Creating table dbo.tbUpdateClassificationInAutoDeploymentRule
2018-12-10 10:13:11  Creating table dbo.tbCategoryInAutoDeploymentRule
2018-12-10 10:13:11  Creating table dbo.tbTargetGroupInAutoDeploymentRule
2018-12-10 10:13:11  Creating table dbo.tbSchemaVersion
2018-12-10 10:13:11  Creating table dbo.tbSchemaVersionHistory
2018-12-10 10:13:12  Creating table dbo.tbServerHealth
2018-12-10 10:13:12  Creating table dbo.tbProgramKeys
2018-12-10 10:13:12  Creating table tbComputersThatNeedDetailedRollup
2018-12-10 10:13:12  Creating table dbo.tbDriverTargetingGroup
2018-12-10 10:13:12  Creating table dbo.tbDriverTargetingGroupPrerequisite
2018-12-10 10:13:12  Creating table dbo.tbTargetedDriverHwid
2018-12-10 10:13:12  Creating table dbo.tbDriverFeatureScore
2018-12-10 10:13:12  Creating table dbo.tbDistributionComputerHardwareId
2018-12-10 10:13:12  Creating table dbo.tbTargetComputerHardwareId
2018-12-10 10:13:12  Creating type GuidListType
2018-12-10 10:13:12  Adding indexed view ivwApiUpdateRevision
2018-12-10 10:13:12  Creating Procedure spAddConstraint
2018-12-10 10:13:12  executing stored PROCEDURE spAddConstraint
2018-12-10 10:13:12  Adding FUNCTION fn_GetGrade 
2018-12-10 10:13:12  Adding FUNCTION fnGetOnlineSummaryFlags
2018-12-10 10:13:12  Adding PROCEDURE spUpdateChangeTrackingNumber
2018-12-10 10:13:12  Creating PROCEDURE spUpdateChangeTrackingNumber
2018-12-10 10:13:12  Adding Trigger trOnUpdatingConfiguration
2018-12-10 10:13:12  Adding Trigger trOnInsertingUpdateStatus
2018-12-10 10:13:12  Adding Trigger trOnDeletingUpdateStatus
2018-12-10 10:13:12  Adding Trigger trOnUpdatingUpdateStatus
2018-12-10 10:13:12  Adding FUNCTION fn_GetBestRevisionForEvaluateDeployment
2018-12-10 10:13:13  Adding PROCEDURE spMoveEvaluateDeploymentsAsNeeded
2018-12-10 10:13:13  Adding PROCEDURE spDeleteUneededPrerequisiteDeployments
2018-12-10 10:13:13  Adding PROCEDURE spDeleteUneededBundleDeployments
2018-12-10 10:13:13  Adding PROCEDURE spProcessPrerequisitesForRevision
2018-12-10 10:13:13  Adding PROCEDURE spRefreshDriverTargetingDeployments
2018-12-10 10:13:13  Adding TRIGGER trOnUpdatingRevision
2018-12-10 10:13:13  Adding TRIGGER trOnUpdatingDeployment
2018-12-10 10:13:13  Adding TRIGGER trOnAddingDeployment
2018-12-10 10:13:13  The module 'trOnAddingDeployment' depends on the missing object 'dbo.spGetUpdateThrottlingSettings'. The module will still be created; however, it cannot run successfully until the object exists.
2018-12-10 10:13:13  The module 'trOnAddingDeployment' depends on the missing object 'dbo.spFireStateMachineEventEx'. The module will still be created; however, it cannot run successfully until the object exists.
2018-12-10 10:13:13  Adding PROCEDURE spGetUpdateThrottlingSettings
2018-12-10 10:13:13  Creating PROCEDURE spGetUpdateThrottlingSettings
2018-12-10 10:13:13  Adding Trigger trOnDeletingDeployment
2018-12-10 10:13:13  The module 'trOnDeletingDeployment' depends on the missing object 'dbo.spGetStringFromContextInfo'. The module will still be created; however, it cannot run successfully until the object exists.
2018-12-10 10:13:13  Adding trigger trAdjustIsLeaf_reduce 
2018-12-10 10:13:13  Adding trigger trAdjustPrerequisite 
2018-12-10 10:13:13  Adding triggers trExpandRevisionInCategory 
2018-12-10 10:13:13  Adding triggers trExpandFlattenedRevisionInCategory 
2018-12-10 10:13:13  Adding triggers trExpandRevisionLanguage 
2018-12-10 10:13:13  Adding triggers trAdjustIsLeaf_increase 
2018-12-10 10:13:13  Adding trigger trOnAddingUpdatingGroupAuthorization
2018-12-10 10:13:13  Adding trigger trOnDeletingGroupAuthorization
2018-12-10 10:13:13  Adding trigger trOnAddingUpdatingAuthorization
2018-12-10 10:13:13  Adding trigger trOnDeletingAuthorization
2018-12-10 10:13:13  Adding trigger trOnAddingLanguage
2018-12-10 10:13:13  Adding trigger trOnChangingLanguage
2018-12-10 10:13:13  Adding trigger trOnDeletingLanguage
2018-12-10 10:13:13  Adding trigger trOnAddingDriver
2018-12-10 10:13:13  Adding trigger trOnDeletingDriver
2018-12-10 10:13:13  Adding trigger tr_insert_ExpandedTargetInTargetGroup
2018-12-10 10:13:13  Adding trigger tr_delete_ExpandedTargetInTargetGroup
2018-12-10 10:13:13  Adding FUNCTION fn_later_date 
2018-12-10 10:13:13  Adding PROCEDURE spSaveXmlFragment 
2018-12-10 10:13:13  Creating Procedure spSaveXmlFragment
2018-12-10 10:13:13  Adding PROCEDURE spGetChildCategories 
2018-12-10 10:13:13  Creating Procedure spGetChildCategories
2018-12-10 10:13:13  Adding PROCEDURE spGetUssDeployments 
2018-12-10 10:13:13  Creating Procedure spGetUssDeployments
2018-12-10 10:13:13  Adding PROCEDURE spUpdateSubTimestamp 
2018-12-10 10:13:13  Creating Procedure spUpdateSubTimestamp
2018-12-10 10:13:13  Adding PROCEDURE spPopulateLanguageInSubscription 
2018-12-10 10:13:13  Creating Procedure spPopulateLanguageInSubscription
2018-12-10 10:13:13  Adding PROCEDURE spAddNewLanguage 
2018-12-10 10:13:13  Creating Procedure spAddNewLanguage
2018-12-10 10:13:13  Adding PROCEDURE spCheckRevisionExists 
2018-12-10 10:13:13  Creating Procedure spCheckRevisionExists
2018-12-10 10:13:13  Adding PROCEDURE spCheckUpdateExists 
2018-12-10 10:13:13  Creating Procedure spCheckUpdateExists
2018-12-10 10:13:13  Adding PROCEDURE spGetFilter 
2018-12-10 10:13:13  Creating procedure spUpdateOnlineSummaryTablesForUpdateVisible
2018-12-10 10:13:13  Creating procedure spUpdateOnlineSummaryTablesForUpdateNotVisible
2018-12-10 10:13:13  Creating Procedure spImportUpdate
2018-12-10 10:13:13  The module 'spImportUpdate' depends on the missing object 'dbo.spFireStateMachineEventEx'. The module will still be created; however, it cannot run successfully until the object exists.
2018-12-10 10:13:13  The module 'spImportUpdate' depends on the missing object 'dbo.spPopulateMissingExpandedUpdateContentThrottlingInfo'. The module will still be created; however, it cannot run successfully until the object exists.
2018-12-10 10:13:13  Creating Procedure spDeploymentAutomation
2018-12-10 10:13:13  The module 'spDeploymentAutomation' depends on the missing object 'spDeployUpdate'. The module will still be created; however, it cannot run successfully until the object exists.
2018-12-10 10:13:13  The module 'spDeploymentAutomation' depends on the missing object 'dbo.spAddReportingEventInternal'. The module will still be created; however, it cannot run successfully until the object exists.
2018-12-10 10:13:13  The module 'spDeploymentAutomation' depends on the missing object 'spDeployUpdate'. The module will still be created; however, it cannot run successfully until the object exists.
2018-12-10 10:13:13  The module 'spDeploymentAutomation' depends on the missing object 'dbo.spAddReportingEventInternal'. The module will still be created; however, it cannot run successfully until the object exists.
2018-12-10 10:13:13  The module 'spDeploymentAutomation' depends on the missing object 'dbo.spDeclineUpdate'. The module will still be created; however, it cannot run successfully until the object exists.
2018-12-10 10:13:13  The module 'spDeploymentAutomation' depends on the missing object 'dbo.spRefreshDeployments'. The module will still be created; however, it cannot run successfully until the object exists.
2018-12-10 10:13:13  Creating Procedure spSetInitialDeploymentStatus
2018-12-10 10:13:13  Creating Procedure spImportUpdateForServerSync
2018-12-10 10:13:13  Adding FUNCTION fn_FormatError 
2018-12-10 10:13:13  Adding FUNCTION fn_FormatLog 
2018-12-10 10:13:13  Adding FUNCTION fn_BuildDeploymentMessage
2018-12-10 10:13:13  Creating Procedure spSelectProcFortbNotificationEvent
2018-12-10 10:13:13  Creating Procedure spUpdateProcFortbNotificationEvent
2018-12-10 10:13:13  Creating Procedure spSelectProcFortbSubscription
2018-12-10 10:13:13  Creating Procedure spUpdateProcFortbSubscription
2018-12-10 10:13:13  Creating Procedure spSelectProcFortbRevision
2018-12-10 10:13:13  Creating Procedure spUpdateProcFortbRevision
2018-12-10 10:13:13  Creating Procedure spSelectProcFortbFileOnServerDesired
2018-12-10 10:13:13  Creating Procedure spUpdateProcFortbFileOnServerDesired
2018-12-10 10:13:13  Creating Procedure spSelectProcFortbFileOnServerActual
2018-12-10 10:13:13  Creating Procedure spUpdateProcFortbFileOnServerActual
2018-12-10 10:13:13  Creating Procedure spFireStateMachineEventEx
2018-12-10 10:13:13  Creating Procedure spFireStateMachineEvent
2018-12-10 10:13:13  Adding PROCEDURE spGetNotificationEventItem
2018-12-10 10:13:13  Creating Procedure spGetNotificationEventItem
2018-12-10 10:13:13  Adding PROCEDURE spGetNotificationEventNamesToWakeUp
2018-12-10 10:13:13  Creating PROCEDURE spGetNotificationEventNamesToWakeUp
2018-12-10 10:13:13  The module 'spGetNotificationEventNamesToWakeUp' depends on the missing object 'dbo.spStartCatalogSync'. The module will still be created; however, it cannot run successfully until the object exists.
2018-12-10 10:13:13  The module 'spGetNotificationEventNamesToWakeUp' depends on the missing object 'dbo.spWakeUpEmailNotificationAgent'. The module will still be created; however, it cannot run successfully until the object exists.
2018-12-10 10:13:13  Adding PROCEDURE spGetNotificationEventNamesToWakeUpOnStartup
2018-12-10 10:13:13  Creating PROCEDURE spGetNotificationEventNamesToWakeUpOnStartup
2018-12-10 10:13:13  Adding PROCEDURE spCleanupIntermediateFileStatesOnStartup
2018-12-10 10:13:13  Creating PROCEDURE spCleanupIntermediateFileStatesOnStartup
2018-12-10 10:13:13  Adding PROCEDURE spStartCatalogSync
2018-12-10 10:13:13  Creating Procedure spStartCatalogSync
2018-12-10 10:13:13  Adding PROCEDURE spCancelCatalogSync
2018-12-10 10:13:13  Creating Procedure spCancelCatalogSync
2018-12-10 10:13:13  Adding PROCEDURE spSetHandshakeAnchor
2018-12-10 10:13:13  Creating Procedure spSetHandshakeAnchor
2018-12-10 10:13:14  Adding PROCEDURE spResetNotificationState
2018-12-10 10:13:14  Creating Procedure spResetNotificationState
2018-12-10 10:13:14  Adding PROCEDURE spGetLocalIdList 
2018-12-10 10:13:14  Creating Procedure spGetLocalIdList
2018-12-10 10:13:14  Adding PROCEDURE spQueueCatalogSyncRequest
2018-12-10 10:13:14  Creating Procedure spQueueCatalogSyncRequest
2018-12-10 10:13:14  The module 'spQueueCatalogSyncRequest' depends on the missing object 'dbo.spSetSubscriptionProgress'. The module will still be created; however, it cannot run successfully until the object exists.
2018-12-10 10:13:14  Adding PROCEDURE spGetSubscriptionProgress
2018-12-10 10:13:14  Creating Procedure spGetSubscriptionProgress
2018-12-10 10:13:14  Adding PROCEDURE spSetSubscriptionProgress
2018-12-10 10:13:14  Creating Procedure spSetSubscriptionProgress
2018-12-10 10:13:14  Adding PROCEDURE spSetCatalogSyncFail
2018-12-10 10:13:14  Creating Procedure spSetCatalogSyncFail
2018-12-10 10:13:14  Adding PROCEDURE spNotifySyncCancel
2018-12-10 10:13:14  Creating Procedure spNotifySyncCancel
2018-12-10 10:13:14  Adding PROCEDURE spSyncWorkDone
2018-12-10 10:13:14  Creating Procedure spSyncWorkDone
2018-12-10 10:13:14  Adding PROCEDURE spGetNextQueuedSubscription
2018-12-10 10:13:14  Creating Procedure spGetNextQueuedSubscription
2018-12-10 10:13:14  Adding PROCEDURE spGetSubscriptionState
2018-12-10 10:13:14  Creating Procedure spGetSubscriptionState
2018-12-10 10:13:14  Adding PROCEDURE spFixCatalogSyncStates
2018-12-10 10:13:14  Creating Procedure spFixCatalogSyncStates
2018-12-10 10:13:14  Creating Procedure spCancelFilesAndRelatedRevisions
2018-12-10 10:13:14  Creating Procedure spDeactivateDeploymentsAndNotifyParentRevisionsChildNotReady
2018-12-10 10:13:14  Creating Procedure spCheckRevisionsNeedingFile
2018-12-10 10:13:14  The module 'spCheckRevisionsNeedingFile' depends on the missing object 'dbo.spNotifyFileActualStateImportNeeded'. The module will still be created; however, it cannot run successfully until the object exists.
2018-12-10 10:13:14  Creating Procedure spNotifyFileActualStateMUUrlNeeded
2018-12-10 10:13:14  Creating Procedure spNotifyFileActualStateDownloadNeeded
2018-12-10 10:13:14  Creating Procedure spNotifyFileActualStateImportNeeded
2018-12-10 10:13:14  Creating Procedure spNotifyFileActualStateNotNeeded
2018-12-10 10:13:14  Creating Procedure spNotifyActualStateAndRevisionsFileCancelled
2018-12-10 10:13:14  Creating Procedure spWakeUpContentAgent
2018-12-10 10:13:14  Creating Procedure spRemoveFileFromProgress
2018-12-10 10:13:14  Creating Procedure spRemoveFileFromProgressAndWakeUpContentAgent
2018-12-10 10:13:14  Creating Procedure spNotifyRevisionsFileReady
2018-12-10 10:13:14  Creating Procedure spNotifyRevisionsFileFailed
2018-12-10 10:13:14  Creating Procedure spCheckFileDesiredState
2018-12-10 10:13:14  Creating Procedure spCheckFileDownloadQueue
2018-12-10 10:13:14  Creating Procedure spCheckDesiredStateAndNotifyRevisionsFileReady
2018-12-10 10:13:14  Creating Procedure spCheckFileDownloadQueueAndNotifyRevisionsFileFailed
2018-12-10 10:13:14  Creating Procedure spCheckDesiredStateAndNotifyRevisionsFileFailed
2018-12-10 10:13:14  Creating Procedure spNotifyRevisionsFileNotReadyAndCheckDesiredState
2018-12-10 10:13:14  Creating Procedure spCheckFileDownloadQueueAndRemoveFileFromProgress
2018-12-10 10:13:14  Creating Procedure spCheckFileDownloadQueueAndDesiredState
2018-12-10 10:13:14  Creating Procedure spUpdateQueueEntryTimeAndCheckFileDownloadQueue
2018-12-10 10:13:14  Creating Procedure spNotifyContentSyncNotificationEventWorking
2018-12-10 10:13:14  Creating Procedure spGetNextContentSyncWorkItem
2018-12-10 10:13:14  Creating Procedure spGetNextContentSyncWorkItemOnStartup
2018-12-10 10:13:14  Creating PROCEDURE spUpdateFileDownloadProgress
2018-12-10 10:13:16  Creating Procedure spSetFileMUUrl
2018-12-10 10:13:16  Creating Procedure spGetUpdatesForFile
2018-12-10 10:13:16  Creating Procedure spRetrieveFileDigestFromRowID
2018-12-10 10:13:16  Creating Procedure spNotifyEulaFilesNeeded
2018-12-10 10:13:16  The module 'spNotifyEulaFilesNeeded' depends on the missing object 'dbo.spCheckEulasAndChildRevisionsReady'. The module will still be created; however, it cannot run successfully until the object exists.
2018-12-10 10:13:16  Creating Procedure spCheckRevisionInstallationPossibility
2018-12-10 10:13:16  Creating Procedure spNotifyParentsEulasReadyAndCheckRevisionInstallationPossibility
2018-12-10 10:13:16  Creating Procedure spCheckRevisionNeededAndNotifyParentsChildInstallationPossible
2018-12-10 10:13:16  Adding procedure spAddDownstreamServerToTargetGroup
2018-12-10 10:13:16  The module 'spAddDownstreamServerToTargetGroup' depends on the missing object 'dbo.spDeployRevisionToDss'. The module will still be created; however, it cannot run successfully until the object exists.
2018-12-10 10:13:16  The module 'spAddDownstreamServerToTargetGroup' depends on the missing object 'dbo.spAddTargetToTargetGroup'. The module will still be created; however, it cannot run successfully until the object exists.
2018-12-10 10:13:16  Adding procedure spPreregisterDownstreamServer
2018-12-10 10:13:16  The module 'spPreregisterDownstreamServer' depends on the missing object 'dbo.spCreateTargetEntry'. The module will still be created; however, it cannot run successfully until the object exists.
2018-12-10 10:13:16  Adding PROCEDURE spGetDssTargetGroup 
2018-12-10 10:13:16  Adding PROCEDURE spUpdateDownstreamServerID 
2018-12-10 10:13:16  Adding PROCEDURE spReturnStateMachineTransitionEventLogEntriesFromError
2018-12-10 10:13:16  Creating Procedure spReturnStateMachineTransitionEventLogEntriesFromError
2018-12-10 10:13:16  Creating Procedure spCheckFilesAndChildRevisionsReady
2018-12-10 10:13:16  Creating Procedure spNotifyFilesAndChildRevisionsNeeded
2018-12-10 10:13:16  Creating Procedure spActivateDeploymentsAndNotifyParentRevisionsChildReady
2018-12-10 10:13:16  Creating Procedure spFailParentRevisions
2018-12-10 10:13:16  Creating Procedure spCheckEulasAndChildRevisionsReady
2018-12-10 10:13:16  Creating Procedure spDeactivateDeploymentsNotifyFilesNotNeeded
2018-12-10 10:13:16  Creating Procedure spResetStateMachineAndReEvaluate
2018-12-10 10:13:16  Creating Procedures spCancelAllNotReadyRevisions
2018-12-10 10:13:16  Creating Procedures spDownloadAllNotNeededRevisions
2018-12-10 10:13:16  Creating Procedures spWakeUpResetAgent
2018-12-10 10:13:16  Creating Procedures spWakeUpEmailNotificationAgent
2018-12-10 10:13:16  Creating Procedures spNotifyResetAgentNotificationEventWorking
2018-12-10 10:13:16  Creating Procedures spNotifyResetAgentNotificationEventDone
2018-12-10 10:13:16  Creating Procedures spWakeUpRollupAgent
2018-12-10 10:13:16  Creating Procedures spNotifyRollupAgentNotificationEventWorking
2018-12-10 10:13:16  Creating Procedures spNotifyRollupAgentNotificationEventDone
2018-12-10 10:13:16  Creating Procedures spNotifyEmailNotificationAgentNotificationEventWorking
2018-12-10 10:13:16  Creating Procedures spNotifyEmailNotificationAgentNotificationEventDone
2018-12-10 10:13:16  Creating Procedure spSaveUssHostOnMU
2018-12-10 10:13:16  Creating Procedure spRetrieveUssHostOnMU
2018-12-10 10:13:16  Creating Procedure spGetLastServerSyncCookie 
2018-12-10 10:13:16  Creating Procedure spSetLastServerSyncCookie 
2018-12-10 10:13:16  Creating Procedure spResetServer 
2018-12-10 10:13:16  Creating Procedure spGetLastSyncTime 
2018-12-10 10:13:16  Creating Procedure spSetLastSyncTime 
2018-12-10 10:13:16  The module 'spSetLastSyncTime' depends on the missing object 'dbo.spMarkComputerAsNeedingDetailedRollup'. The module will still be created; however, it cannot run successfully until the object exists.
2018-12-10 10:13:16  The module 'spSetLastSyncTime' depends on the missing object 'spIsRegistrationRequired'. The module will still be created; however, it cannot run successfully until the object exists.
2018-12-10 10:13:16  Creating Procedure spIsRegistrationRequired 
2018-12-10 10:13:16  Creating Procedure spGetComputerTargetGroup 
2018-12-10 10:13:16  The module 'spGetComputerTargetGroup' depends on the missing object 'dbo.spMarkComputerAsNeedingDetailedRollup'. The module will still be created; however, it cannot run successfully until the object exists.
2018-12-10 10:13:16  The module 'spGetComputerTargetGroup' depends on the missing object 'dbo.spMarkComputerAsNeedingDetailedRollup'. The module will still be created; however, it cannot run successfully until the object exists.
2018-12-10 10:13:16  Creating Procedure spCheckForClientNameChange 
2018-12-10 10:13:16  Creating Procedure spGetFrontEndServers 
2018-12-10 10:13:16  Creating Procedure spRemoveFrontEndServer 
2018-12-10 10:13:16  Creating Procedure spGetClientsWithRecentNameChange 
2018-12-10 10:13:16  Creating Procedure spGetComputerTargetGroupEx 
2018-12-10 10:13:16  The module 'spGetComputerTargetGroupEx' depends on the missing object 'dbo.spDeleteComputer'. The module will still be created; however, it cannot run successfully until the object exists.
2018-12-10 10:13:16  The module 'spGetComputerTargetGroupEx' depends on the missing object 'dbo.spMarkComputerAsNeedingDetailedRollup'. The module will still be created; however, it cannot run successfully until the object exists.
2018-12-10 10:13:16  The module 'spGetComputerTargetGroupEx' depends on the missing object 'dbo.spMarkComputerAsNeedingDetailedRollup'. The module will still be created; however, it cannot run successfully until the object exists.
2018-12-10 10:13:16  Adding PROCEDURE spRegisterComputer 
2018-12-10 10:13:16  The module 'spRegisterComputer' depends on the missing object 'dbo.spMarkComputerAsNeedingDetailedRollup'. The module will still be created; however, it cannot run successfully until the object exists.
2018-12-10 10:13:16  Creating Procedure spSetBatchURL
2018-12-10 10:13:16  Creating Procedure spUpdateServerHealthStatus
2018-12-10 10:13:16  Creating PROCEDURE spGetExportData
2018-12-10 10:13:16  Creating Procedure spGetExportUpdateData
2018-12-10 10:13:16  Adding PROCEDURE spGetDataForSyncPackage
2018-12-10 10:13:16  Creating Procedure spGetDataForSyncPackage
2018-12-10 10:13:16  Creating Procedure spGetBundedByDataForSyncPackage
2018-12-10 10:13:16  Creating Procedure spGetUpdateDataForSyncPackage
2018-12-10 10:13:16  Creating Procedure spGetUpdateTypeByRevisionID
2018-12-10 10:13:16  Creating Procedure spEnableReplica
2018-12-10 10:13:17  Creating Procedure spGetAllExplicitComputerDeployments
2018-12-10 10:13:17  Adding procedure spGetUpdatesForBulkHideInReplicaSync
2018-12-10 10:13:17  Adding Procedure spDeleteRevision
2018-12-10 10:13:17  Creating Procedure spGetCompressionThesholds
2018-12-10 10:13:17  Adding Procedure spGetUpdatesWithPermanantlyInactiveDeployments
2018-12-10 10:13:17  Adding Procedure spDeleteDeploymentsForUpdatesWithPermanantlyInactiveDeployments
2018-12-10 10:13:17  The module 'spDeleteDeploymentsForUpdatesWithPermanantlyInactiveDeployments' depends on the missing object 'dbo.spSetStringInContextInfo'. The module will still be created; however, it cannot run successfully until the object exists.
2018-12-10 10:13:17  Adding Procedure spSetUpdateFlagCatalogSite
2018-12-10 10:13:17  Adding Procedure spGetUpdatesWithCatalogSiteFlag
2018-12-10 10:13:17  Adding Procedure spMarkComputerAsNeedingDetailedRollup
2018-12-10 10:13:17  Adding Procedure spMarkComputerAsDeletedForDss
2018-12-10 10:13:17  Adding Procedure spUpdateDownstreamServerTarget
2018-12-10 10:13:17  The module 'spUpdateDownstreamServerTarget' depends on the missing object 'dbo.spCreateTargetEntry'. The module will still be created; however, it cannot run successfully until the object exists.
2018-12-10 10:13:17  Adding Procedure spUpdateDownstreamServerSummaryRollup
2018-12-10 10:13:17  Adding Procedure spUpdateDownstreamServerClientSummaryRollup
2018-12-10 10:13:17  Adding Procedure spUpdateDownstreamServerClientActivityRollup
2018-12-10 10:13:17  Adding Procedure spGetDownstreamServerClientSummaries
2018-12-10 10:13:17  Adding Procedure spClearAllClientActivityCounts
2018-12-10 10:13:17  Adding Procedure spGetClientSummaryForAllServers
2018-12-10 10:13:17  Adding Procedure spGetClientActivityForAllServers
2018-12-10 10:13:17  Adding Procedure spSetLastTimeReportToMU
2018-12-10 10:13:17  Adding Procedure spGetLastTimeReportToMU
2018-12-10 10:13:17  Adding PROCEDURE spGetTempContentCache
2018-12-10 10:13:17  Creating PROCEDURE spGetTempContentCache
2018-12-10 10:13:17  Creating PROCEDURE spPopulateMissingExpandedUpdateContentThrottlingInfo
2018-12-10 10:13:17  Creating PROCEDURE spSetStringInContextInfo
2018-12-10 10:13:17  Creating PROCEDURE spGetStringFromContextInfo
2018-12-10 10:13:17  Creating PROCEDURE spSetOfflineSyncExclusionList
2018-12-10 10:13:17  Creating PROCEDURE spGetEncryptedProxyPasswordFromDatabaseForUpgrade
2018-12-10 10:13:17  Creating PROCEDURE spResetDssRequestedStateForFiles
2018-12-10 10:13:17  Creating PROCEDURE spAllowComputersWithDuplicateNames
2018-12-10 10:13:17  Creating PROCEDURE spGetAllUpdateUrls
2018-12-10 10:13:17  Creating PROCEDURE spGetStartServerInitializationStatus
2018-12-10 10:13:17  Creating PROCEDURE spSetStartServerInitializationStatus
2018-12-10 10:13:17  Changed database context to 'SUSDB'.
2018-12-10 10:13:17  Adding function fnGetConfigurationValue
2018-12-10 10:13:17  Adding view vwConfiguration 
2018-12-10 10:13:17  Adding PROCEDURE spConfiguration 
2018-12-10 10:13:17  Creating Procedure spConfiguration
2018-12-10 10:13:17  Creating Procedure spGetUpstreamServerInfo
2018-12-10 10:13:17  Adding PROCEDURE spGetUpdateXmlFromRevision 
2018-12-10 10:13:17  Creating Procedure spGetUpdateXmlFromRevision
2018-12-10 10:13:17  Adding PROCEDURE spGetChangeTrackingInformation
2018-12-10 10:13:17  Creating PROCEDURE spGetChangeTrackingInformation
2018-12-10 10:13:17  Adding PROCEDURE spGetChangeTrackingNumber
2018-12-10 10:13:17  Creating PROCEDURE spGetChangeTrackingNumber
2018-12-10 10:13:17  Adding procedure spGetAllLanguagesWithEnabledState
2018-12-10 10:13:17  Adding procedure spCheckConnection
2018-12-10 10:13:17  Adding procedure spGetChangeTrackingNumbersForCache
2018-12-10 10:13:17  Adding procedure spGetLanguageListForCache
2018-12-10 10:13:17  Adding procedure spGetRevisionIdListForCache
2018-12-10 10:13:17  Adding Procedure spGetRelatedRevisionsForUpdateID
2018-12-10 10:13:17  Adding Procedure spGetAllUpdateIDs
2018-12-10 10:13:17  Adding procedure spGetProgramKeys
2018-12-10 10:13:17  Creating type UpdateIdentityListType
2018-12-10 10:13:17  Adding procedure spGetMissingDrivers
2018-12-10 10:13:17  Adding procedure spGetMissingDriverSets
2018-12-10 10:13:17  Adding procedure spGetPublishedXmlForUpdate
2018-12-10 10:13:17  Creating Procedure spGetUpdateDecryptionData
2018-12-10 10:13:17  Creating Procedure spSetUpdateDecryptionData
2018-12-10 10:13:17  Changed database context to 'SUSDB'.
2018-12-10 10:13:17  Creating Function fnCsvToInt
2018-12-10 10:13:17  Creating Function fnCsvToUniqueID
2018-12-10 10:13:17  Creating Procedure spGetCoreUpdateXml
2018-12-10 10:13:17  Creating Procedure spGetLocalizedUpdateXml
2018-12-10 10:13:17  Creating Procedure spGetLocaleNames
2018-12-10 10:13:17  Creating Procedure spGetGlobalUpdates
2018-12-10 10:13:17  Creating Procedure spGetHardwareDrivers
2018-12-10 10:13:17  Creating Procedure spGetMonitorableStatus
2018-12-10 10:13:17  Creating Procedure spGetFileLocations
2018-12-10 10:13:17  Adding procedure spGetAllTargetGroups
2018-12-10 10:13:17  Creating Procedure spGetFrontEndServerInfo
2018-12-10 10:13:17  Creating Procedure spSetFrontEndServerInfo
2018-12-10 10:13:17  Creating Procedure spSetFileLocationChange
2018-12-10 10:13:17  Creating Procedure spGetRevisionInfo
2018-12-10 10:13:17  Creating Procedure spGetDeltaRevisionInfo
2018-12-10 10:13:17  Adding procedure spGetConfigurationValue
2018-12-10 10:13:17  Adding procedure spSetConfigurationValue
2018-12-10 10:13:17  Changed database context to 'SUSDB'.
2018-12-10 10:13:17  Adding procedure spAdduser
2018-12-10 10:13:17  Adding procedure spGrantAsp 
2018-12-10 10:13:17  Adding procedure spSetupLogin
2018-12-10 10:13:17  Adding procedure spSetContentCacheLocation
2018-12-10 10:13:17  Adding procedure spSetDefaults
2018-12-10 10:13:17  Adding database version 
2018-12-10 10:13:17  Changed database context to 'SUSDB'.
2018-12-10 10:13:17  Creating table tbEventMessageTemplate
2018-12-10 10:13:17  Creating table tbEventInstance
2018-12-10 10:13:17  Creating table tbEvent
2018-12-10 10:13:18  Creating table tbEventSource
2018-12-10 10:13:18  Creating table tbEventNamespace
2018-12-10 10:13:18  Alter table tbEvent with foreign key
2018-12-10 10:13:18  Alter table tbEventSource with foreign key
2018-12-10 10:13:18  Alter table tbEventMessageTemplate with foreign key
2018-12-10 10:13:18  Alter table tbEventInstance with foreign keys
2018-12-10 10:13:18  Adding procedure spImportEventNamespaceDescriptor
2018-12-10 10:13:18  Adding procedure spAutoPurgeReportingEvents 
2018-12-10 10:13:18  Adding procedure spLoadReportingEventAttributes
2018-12-10 10:13:18  Changed database context to 'SUSDB'.
2018-12-10 10:13:18  Creating table tbLocaleMap
2018-12-10 10:13:18  Creating table tbOSMap
2018-12-10 10:13:18  Creating table tbDownstreamServerRollupConfiguration
2018-12-10 10:13:18  Creating table tbEventRollupCounters
2018-12-10 10:13:18  Adding function fnFindOsID 
2018-12-10 10:13:18  Adding function fnGetSummarizationState 
2018-12-10 10:13:18  Adding function fnGetEffectiveDeployment 
2018-12-10 10:13:18  Adding function fnGetTargetGroupIDForComputer
2018-12-10 10:13:18  Adding procedure spAddReportingEventBatch 
2018-12-10 10:13:20  Adding procedure spProcessActivityEvents 
2018-12-10 10:13:20  Adding procedure spAddReportingEventInternal 
2018-12-10 10:13:20  Adding procedure spAddUpdateStatusEventBatch 
2018-12-10 10:13:20  Adding procedure spHandleClientRebootedEvent 
2018-12-10 10:13:20  Adding procedure spUpdateLatestRollupEventTime
2018-12-10 10:13:20  Adding procedure spGetCurrentSqlServerTime
2018-12-10 10:13:20  Adding procedure spGetLatestRollupEventTime
2018-12-10 10:13:20  Adding procedure spUpdateCurrentRollupState
2018-12-10 10:13:20  Adding procedure spGetCurrentRollupState
2018-12-10 10:13:20  Adding procedure spGetRollupCounter
2018-12-10 10:13:20  Adding procedure spUpdateRollupCounter
2018-12-10 10:13:20  Adding procedure spSetLastRollupInfo
2018-12-10 10:13:20  Adding procedure spGetLastRollupInfo
2018-12-10 10:13:20  Adding procedure spResetOnlineSummaryTables
2018-12-10 10:13:20  Changed database context to 'SUSDB'.
2018-12-10 10:13:20  Adding procedure spGetComputersToRollup
2018-12-10 10:13:20  Adding procedure spMarkComputersAsNeedingFullComputerRollup
2018-12-10 10:13:20  Adding procedure spUpdateComputersAfterRollup
2018-12-10 10:13:20  Adding procedure spAddRollupComputers
2018-12-10 10:13:20  Adding procedure spGetComputerLastRollupNumbers
2018-12-10 10:13:20  Adding procedure spGetOutOfSyncComputers
2018-12-10 10:13:20  Adding procedure spMarkComputersAsNeedingFullStatusRollup
2018-12-10 10:13:20  Adding procedure spGetComputerStatusToRollup
2018-12-10 10:13:20  Adding procedure spUpdateComputerStatusAfterRollup
2018-12-10 10:13:20  Adding procedure spAddRollupStatus
2018-12-10 10:13:20  Adding procedure spAddRollupStatusNoStatus
2018-12-10 10:13:20  Adding procedure spMarkDataForFullRollup
2018-12-10 10:13:20  Changed database context to 'SUSDB'.
2018-12-10 10:13:20  Adding function fnMapLocalUpdateIDToGlobal 
2018-12-10 10:13:20  Adding function fnMapGlobalToLocalUpdateID 
2018-12-10 10:13:20  Adding function fnHasStaleDeployments
2018-12-10 10:13:20  Adding function fnHasSupersededUpdates
2018-12-10 10:13:20  Adding function fnIsEulaAcceptanceRequired
2018-12-10 10:13:20  Adding function fnGetTargetGroupTypeID
2018-12-10 10:13:20  Adding function fnGetComputerTargetID 
2018-12-10 10:13:20  Adding function fnGetLatestRevisionNumber
2018-12-10 10:13:20  Adding function fnIsInReplicaMode
2018-12-10 10:13:20  Adding function fnComputeAutoApprovalDeadline
2018-12-10 10:13:20  Adding view vwUpdatesToReport
2018-12-10 10:13:20  Adding view vwUpdateInCategory
2018-12-10 10:13:20  Adding view vwApiUpdateType
2018-12-10 10:13:20  Adding view vwMinimalUpdate 
2018-12-10 10:13:20  Adding view vwUpdateLanguage 
2018-12-10 10:13:20  Adding view vwDefaultLocalizedProperty 
2018-12-10 10:13:20  Adding view vwUpdateLocalizedProperties 
2018-12-10 10:13:20  Adding view vwCategoryProperties 
2018-12-10 10:13:20  Adding view vwEventHistory 
2018-12-10 10:13:20  Adding function fnTbUpdateTypeNamesToGet
2018-12-10 10:13:20  Adding function fnTbComputersInTargetGroup
2018-12-10 10:13:20  Adding procedure spFilterUpdatesByScopeInternal
2018-12-10 10:13:20  Adding procedure spGetCategories
2018-12-10 10:13:20  Adding procedure spGetTopLevelCategories
2018-12-10 10:13:20  Adding procedure spGetCategoryPropertiesByID
2018-12-10 10:13:20  Adding procedure spGetSubCategoriesByUpdateID
2018-12-10 10:13:20  Adding procedure spGetUpdatesUnderACategory
2018-12-10 10:13:20  Adding procedure spGetTotalSummary
2018-12-10 10:13:21  Adding procedure spGetSummariesPerComputer
2018-12-10 10:13:21  Adding procedure spGetSummariesPerUpdate
2018-12-10 10:13:21  Adding procedure spGetTotalUpdateSummaryForTargetGroup
2018-12-10 10:13:21  Adding procedure spGetUpdateSummariesForTargetGroup
2018-12-10 10:13:21  Adding procedure spGetTotalSummaryForComputer
2018-12-10 10:13:21  Adding procedure spGetComputerSummariesForTargetGroup
2018-12-10 10:13:21  Adding procedure spGetTargetGroupSummariesForUpdate
2018-12-10 10:13:21  Adding procedure spGetUpdateSummaryForSingleTargetGroup
2018-12-10 10:13:21  Adding procedure spGetTotalSummaryForCategory
2018-12-10 10:13:21  Adding procedure spGetUpdateSummariesForCategory
2018-12-10 10:13:21  Adding procedure spGetComputerSummariesForCategory
2018-12-10 10:13:21  Adding procedure spGetUpdateInstallationInfoForUpdate
2018-12-10 10:13:21  Adding procedure spGetUpdateInstallationInfoForComputer 
2018-12-10 10:13:21  Adding procedure spGetUpdateInstallationInfoForTargetGroup
2018-12-10 10:13:21  Adding procedure spDeployRevisionToDss
2018-12-10 10:13:21  Adding procedure spGetAutoDeploymentRuleByID
2018-12-10 10:13:21  Adding procedure spSaveParsedExtendedProperties
2018-12-10 10:13:21  Adding procedure spGetUpdatesAndDeployments
2018-12-10 10:13:21  Adding procedure spSetAutoDeploymentRule
2018-12-10 10:13:21  Adding procedure spGetAutoDeploymentRuleIDs
2018-12-10 10:13:21  Adding procedure spCreateAutoDeploymentRule
2018-12-10 10:13:21  Adding procedure spDeleteAutoDeploymentRuleByID
2018-12-10 10:13:21  Adding procedure spGetUpdateListToApproveForAutoDeploymentRule
2018-12-10 10:13:21  Adding procedure spGetComputersNotContactedSinceCount
2018-12-10 10:13:21  Adding procedure spDeclineUpdate
2018-12-10 10:13:21  Adding procedure spGetParentCategories
2018-12-10 10:13:21  Adding procedure spSearchUpdates 
2018-12-10 10:13:21  Adding procedure spGetAllUpdates 
2018-12-10 10:13:21  Adding procedure spGetUpdateCount
2018-12-10 10:13:21  Adding procedure spGetRevisions
2018-12-10 10:13:21  Adding procedure spGetComputerTargetByName
2018-12-10 10:13:21  Adding procedure spSimpleSearchComputers
2018-12-10 10:13:21  Adding procedure spSimpleSearchUpdates 
2018-12-10 10:13:21  Adding procedure spGetEulaFiles
2018-12-10 10:13:21  Adding procedure spGetShortLanguage
2018-12-10 10:13:21  Adding procedure spGetEulaAcceptances
2018-12-10 10:13:21  Adding procedure spAcceptEula
2018-12-10 10:13:21  Adding procedure spAcceptEulaForReplicaDSS
2018-12-10 10:13:21  Adding procedure spRecurseInsertCategoriesIntoFlatTable
2018-12-10 10:13:21  Adding procedure spInsertCategoriesIntoFlatTable
2018-12-10 10:13:21  Adding procedure spRepairPrecomputedTables
2018-12-10 10:13:21  Adding procedure spGetInstallableItems
2018-12-10 10:13:21  Adding PROCEDURE spGetApprovedUpdateMetadata 
2018-12-10 10:13:21  Creating Procedure spGetApprovedUpdateMetadata
2018-12-10 10:13:21  Adding procedure spHasApprovalsChanged
2018-12-10 10:13:21  Adding procedure spGetUpdateByID
2018-12-10 10:13:21  Adding procedure spGetUpdatesBundledByUpdate
2018-12-10 10:13:21  Adding procedure spGetUpdatesThatBundleUpdate
2018-12-10 10:13:21  Adding procedure spGetUpdatesSupersededByUpdate
2018-12-10 10:13:21  Adding procedure spGetUpdatesThatSupersedeUpdate
2018-12-10 10:13:22  Adding procedure spGetUpdatesRequiredByUpdate
2018-12-10 10:13:22  Adding procedure spGetUpdatesThatRequireUpdate
2018-12-10 10:13:22  Adding procedure spGetLanguagesForUpdate
2018-12-10 10:13:22  Adding procedure spGetContentDownloadProgress
2018-12-10 10:13:22  Adding procedure spCancelDownload
2018-12-10 10:13:22  Adding procedure spCancelAllDownloads
2018-12-10 10:13:22  Adding procedure spResumeDownload
2018-12-10 10:13:22  Adding procedure spResumeAllDownloads
2018-12-10 10:13:22  Adding procedure spSetConfiguration 
2018-12-10 10:13:22  Adding Procedure spSetRollupConfiguration
2018-12-10 10:13:22  Adding procedure spGetResetStateMachineNeededFlag
2018-12-10 10:13:22  Adding procedure spDeleteDeployment
2018-12-10 10:13:22  Adding procedure spCreateImplicitDeployment
2018-12-10 10:13:22  Adding procedure spCreateDriverTargetingDeployments
2018-12-10 10:13:22  Adding procedure spUndeclineUpdate
2018-12-10 10:13:22  Adding procedure spDeployUpdate
2018-12-10 10:13:22  Adding procedure spGetDeploymentByID 
2018-12-10 10:13:22  Adding procedure spGetDeploymentsForAnUpdate
2018-12-10 10:13:22  Adding procedure spGetDeployments
2018-12-10 10:13:22  Adding procedure spRefreshDeployments
2018-12-10 10:13:22  Adding procedure spGetSubscription
2018-12-10 10:13:22  Adding procedure spGetSubscriptionCategories
2018-12-10 10:13:22  Adding procedure spGetSubscriptionNextSynchronizationTime
2018-12-10 10:13:22  Adding procedure spSetSubscription
2018-12-10 10:13:22  Adding procedure spSetSubscriptionLastRunTime
2018-12-10 10:13:23  Adding procedure spSetScheduleFrequency
2018-12-10 10:13:23  Adding procedure spSetSubscriptionDeploymentAnchor
2018-12-10 10:13:23  Adding procedure spSetSubscriptionAnchor
2018-12-10 10:13:23  Adding procedure spGetTargetGroupByID
2018-12-10 10:13:23  Adding procedure spGetTargetGroupForComputer
2018-12-10 10:13:23  Adding procedure spGetTargetGroupsForComputer
2018-12-10 10:13:23  Adding procedure spGetChildTargetGroups
2018-12-10 10:13:23  Adding procedure spGetParentTargetGroup
2018-12-10 10:13:23  Adding procedure spCreateTargetGroup
2018-12-10 10:13:23  Adding procedure spDeleteTargetGroup
2018-12-10 10:13:23  Adding procedure spAddTargetToTargetGroup
2018-12-10 10:13:23  Adding procedure spRemoveTargetFromTargetGroup
2018-12-10 10:13:23  Adding procedure spGetAllComputers
2018-12-10 10:13:23  Adding procedure spSearchComputers
2018-12-10 10:13:23  Adding procedure spGetComputerCount
2018-12-10 10:13:23  Adding procedure spGetAllDownstreamServers
2018-12-10 10:13:23  Adding procedure spGetInventoryItemsForComputer
2018-12-10 10:13:23  Adding procedure spGetInventorySummary
2018-12-10 10:13:23  Adding procedure spGetComputersHavingInventoryItem
2018-12-10 10:13:23  Adding procedure spGetComputersInTargetGroup
2018-12-10 10:13:23  Adding procedure spAddComputerToTargetGroup
2018-12-10 10:13:23  Adding procedure spAddComputerToTargetGroupAllowMultipleGroups
2018-12-10 10:13:23  Adding procedure spRemoveComputerFromTargetGroup
2018-12-10 10:13:23  Adding procedure spGetDownstreamServersInTargetGroup
2018-12-10 10:13:23  Adding procedure spCreateTargetEntry
2018-12-10 10:13:23  Adding procedure spPreregisterComputer
2018-12-10 10:13:23  Adding procedure spGetComputerByID
2018-12-10 10:13:23  Adding procedure spGetDownstreamServer
2018-12-10 10:13:23  Adding procedure spDeleteComputer
2018-12-10 10:13:23  Adding procedure spDeleteDownstreamServer
2018-12-10 10:13:23  Adding procedure spSearchEventHistory  
2018-12-10 10:13:23  Adding procedure spPurgeReportingEvents 
2018-12-10 10:13:23  Adding procedure spGetComponentsWithErrors
2018-12-10 10:13:23  Adding procedure spGetUpdateServerStatus
2018-12-10 10:13:23  Adding Procedure spGetDownstreamServerRollupSummary
2018-12-10 10:13:23  Creating Procedure spGetXmlForUpdate
2018-12-10 10:13:23  Creating Procedure spGetPreviousRevision
2018-12-10 10:13:23  Adding Procedure spGetLatestRevisionNumberForUpdate
2018-12-10 10:13:23  Adding Procedure spGetSdpXmlForUpdate
2018-12-10 10:13:23  Adding PROCEDURE spGetEmailNotificationConfiguration
2018-12-10 10:13:23  Adding PROCEDURE spSetEmailNotificationConfiguration
2018-12-10 10:13:23  Adding procedure spGetEmailNotificationStatus
2018-12-10 10:13:23  Adding procedure spSetEmailNotificationStatus
2018-12-10 10:13:23  Adding PROCEDURE spScheduleEmailNotification
2018-12-10 10:13:23  Adding PROCEDURE spGetEmailsToNotify
2018-12-10 10:13:23  Adding PROCEDURE spGetEmailNotificationRecipients
2018-12-10 10:13:23  Adding PROCEDURE spAddEmailNotificationRecipient
2018-12-10 10:13:23  Adding PROCEDURE spDeclineSupersededUpdates
2018-12-10 10:13:23  Adding PROCEDURE spDeclineExpiredUpdates
2018-12-10 10:13:23  Adding PROCEDURE spCountObsoleteUpdatesToCleanup
2018-12-10 10:13:23  Adding PROCEDURE spGetObsoleteUpdatesToCleanup
2018-12-10 10:13:23  Adding PROCEDURE spDeleteUpdate
2018-12-10 10:13:23  Adding PROCEDURE spDeleteUpdateByUpdateID
2018-12-10 10:13:23  Adding PROCEDURE spCountUpdatesToCompress
2018-12-10 10:13:23  Adding PROCEDURE spGetUpdatesToCompress
2018-12-10 10:13:23  Adding PROCEDURE spCompressUpdate
2018-12-10 10:13:23  Adding PROCEDURE spCleanupObsoleteComputers
2018-12-10 10:13:23  Adding PROCEDURE spCleanupUnneededContentFiles
2018-12-10 10:13:23  Adding procedure spGetFailedToDownloadUpdatesCount
2018-12-10 10:13:23  Changed database context to 'SUSDB'.
2018-12-10 10:13:24  Populating the database with basic configuration information
2018-12-10 10:13:24  Creating the pre-defined target groups 
2018-12-10 10:13:24  Populating Auto Deployment Rules
2018-12-10 10:13:24  Populating System Subscription
2018-12-10 10:13:24  Populating Email Notification Configuration
2018-12-10 10:13:24  Populating Email Notification Status
2018-12-10 10:13:24  Populating Languages
2018-12-10 10:13:24  Populating tbLanguageInSubscription for default subscription
2018-12-10 10:13:24  Populating Categories
2018-12-10 10:13:24  Populating Driver classes
2018-12-10 10:13:24  Adding Firmware Driver Class
2018-12-10 10:13:24  Populating handlers
2018-12-10 10:13:24  Populating driver types
2018-12-10 10:13:24  Populating state machine
2018-12-10 10:13:24  Changed database context to 'SUSDB'.
2018-12-10 10:13:25  Changed database context to 'SUSDB'.
2018-12-10 10:13:25  Creating PROCEDURE spUpdateInventoryRulesXml
2018-12-10 10:13:25  Creating PROCEDURE spAddDetailedInventoryRules
2018-12-10 10:13:25  Creating PROCEDURE spGetInventoryVersion
2018-12-10 10:13:25  Creating PROCEDURE spAddInventoryXml
2018-12-10 10:13:25  Creating PROCEDURE spAddDetailedInventoryInformation
2018-12-10 10:13:25  Changed database context to 'SUSDB'.
2018-12-10 10:13:25  Creating PublicViewAccess Database role
2018-12-10 10:13:25  Creating view PUBLIC_VIEWS.vUpdate
2018-12-10 10:13:25  Creating view PUBLIC_VIEWS.vCategory
2018-12-10 10:13:25  Creating view PUBLIC_VIEWS.vClassification
2018-12-10 10:13:25  Creating view PUBLIC_VIEWS.vUpdateInCategory
2018-12-10 10:13:25  Creating view PUBLIC_VIEWS.vLanguage
2018-12-10 10:13:25  Creating view PUBLIC_VIEWS.vUpdateText
2018-12-10 10:13:25  Creating view PUBLIC_VIEWS.vUpdateAdditionalInfoUrl
2018-12-10 10:13:25  Creating view PUBLIC_VIEWS.vCategoryText
2018-12-10 10:13:25  Creating view PUBLIC_VIEWS.vClassificationText
2018-12-10 10:13:25  Creating view PUBLIC_VIEWS.vDownstreamServer
2018-12-10 10:13:25  Creating view PUBLIC_VIEWS.vComputerTarget
2018-12-10 10:13:25  Creating view PUBLIC_VIEWS.vComputerTargetGroup
2018-12-10 10:13:25  Creating view PUBLIC_VIEWS.vComputerGroupMembership
2018-12-10 10:13:25  Creating view PUBLIC_VIEWS.vUpdateApproval
2018-12-10 10:13:25  Creating view PUBLIC_VIEWS.vUpdateInstallationInfoBasic
2018-12-10 10:13:25  Creating view PUBLIC_VIEWS.vUpdateInstallationInfo
2018-12-10 10:13:25  Creating view PUBLIC_VIEWS.vUpdateEffectiveApprovalPerComputer
2018-12-10 10:13:25  Creating view PUBLIC_VIEWS.vSupportedInventory
2018-12-10 10:13:25  Creating view PUBLIC_VIEWS.vComputerInventory
2018-12-10 10:13:25  Creating TVF PUBLIC_VIEWS.fnUpdateInstallationStateMap
2018-12-10 10:13:25  Changed database context to 'SUSDB'.
2018-12-10 10:13:25  Adding table tbDynamicCategory
2018-12-10 10:13:25  Adding trigger trDynamicCategoryDeleted
2018-12-10 10:13:25  Adding trigger trDynamicCategoryCreated
2018-12-10 10:13:25  Adding table tbMapping_Target_DynamicCategory
2018-12-10 10:13:25  Adding trigger trDynamicCategoryCleanup
2018-12-10 10:13:25  Adding table tbDcRollupStatus
2018-12-10 10:13:25  Adding table tbDeletedDynamicCategory
2018-12-10 10:13:25  Creating type DynamicCategoryTableType
2018-12-10 10:13:25  Adding procedure spDcAddCategory
2018-12-10 10:13:25  Adding procedure spDcAddCategories
2018-12-10 10:13:25  Adding procedure spDcGetCategoryById
2018-12-10 10:13:25  Adding procedure spDcGetCategoryByName
2018-12-10 10:13:25  Adding procedure spDcGetCategories
2018-12-10 10:13:25  Adding procedure spDcSetSyncStatus
2018-12-10 10:13:25  Adding procedure spDcDeleteCategory
2018-12-10 10:13:25  Adding procedure spDcGetTargetIdForComputer
2018-12-10 10:13:25  Reestablishing database connection...
2018-12-10 10:13:25  Configuring database...
2018-12-10 10:13:25  Writing settings...
2018-12-10 10:13:25  Settings set
2018-12-10 10:13:25  Creating logins...
2018-12-10 10:13:25  Fetching machine account info
2018-12-10 10:13:26  Found principal
2018-12-10 10:13:26  Found account
2018-12-10 10:13:26  Got binary SID
2018-12-10 10:13:26  Setting content location...
2018-12-10 10:13:26  Fetching ContentDir from registry store
2018-12-10 10:13:26  Value is F:\WSUSUpdates
2018-12-10 10:13:26  Swtching DB to multi-user mode......
2018-12-10 10:13:27  Finished setting multi-user mode
2018-12-10 10:13:27  Writing DB settings to registry...
2018-12-10 10:13:27  Disposing Connection
2018-12-10 10:13:27  Clearing Connection Pools
2018-12-10 10:13:27  Marking PostInstall done for UpdateServices-Database in the registry...
2018-12-10 10:13:27  Starting service W3SVC
2018-12-10 10:13:28  Configuring IIS...
2018-12-10 10:13:28  Start: ConfigureWebsite
2018-12-10 10:13:28  Configuring website on port 8530
2018-12-10 10:14:03  System.Runtime.InteropServices.COMException (0x800710D8): The object identifier does not represent a valid object. (Exception from HRESULT: 0x800710D8)
   at Microsoft.Web.Administration.Interop.IAppHostMethodInstance.Execute()
   at Microsoft.Web.Administration.ConfigurationElement.ExecuteMethod(String methodName)
   at Microsoft.Web.Administration.ApplicationPool.Recycle()
   at Microsoft.UpdateServices.Administration.UseCustomWebSite.CreateWebsite(Int32 newPortNumber)
   at Microsoft.UpdateServices.Administration.PostInstall.ConfigureWebsite(Int32 portNumber)
   at Microsoft.UpdateServices.Administration.PostInstall.Run()
   at Microsoft.UpdateServices.Administration.PostInstall.Execute(String[] arguments)

in progress, any idea?

Thanks,

Dom

Security / System Center Configuration Manager Current Branch / SQL

Monday, December 10, 2018 6:17 PM

0

Sign in to vote

Hello,

I started manually the WsusPool in IIS Manager then rerun the PostInstall..

PS C:\Program Files\Update Services\Tools> .\Wsusutil.exe postinstall SQL_INSTANCE_NAME=”VRPSCCMSQL01\ConfigMgr” CONTENT_DIR=”F:\WSUSUpdates”
Log file is located at C:\Users\rmppqx\AppData\Local\Temp\tmp78DE.tmp
Post install is starting
Post install has successfully completed

2018-12-10 10:32:52  Postinstall started
2018-12-10 10:32:52  Detected role services: Api, Database, UI, Services
2018-12-10 10:32:52  Start: LoadSettingsFromParameters
2018-12-10 10:32:52  Content local is: True
2018-12-10 10:32:52  Content directory is: F:\WSUSUpdates
2018-12-10 10:32:52  SQL instname is: VRPSCCMSQL01\ConfigMgr
2018-12-10 10:32:52  End: LoadSettingsFromParameters
2018-12-10 10:32:52  Start: Run
2018-12-10 10:32:52  Fetching WsusAdministratorsSid from registry store
2018-12-10 10:32:52  Value is S-1-5-21-3958249549-1187530241-1261074650-1006
2018-12-10 10:32:52  Fetching WsusReportersSid from registry store
2018-12-10 10:32:52  Value is S-1-5-21-3958249549-1187530241-1261074650-1007
2018-12-10 10:32:52  Configuring content directory...
2018-12-10 10:32:52  Configuring groups...
2018-12-10 10:32:52  Starting group configuration for WSUS Administrators...
2018-12-10 10:32:52  Found group in regsitry, attempting to use it...
2018-12-10 10:32:55  Writing group to registry...
2018-12-10 10:32:55  Finished group creation
2018-12-10 10:32:55  Starting group configuration for WSUS Reporters...
2018-12-10 10:32:55  Found group in regsitry, attempting to use it...
2018-12-10 10:32:55  Writing group to registry...
2018-12-10 10:32:55  Finished group creation
2018-12-10 10:32:55  Configuring permissions...
2018-12-10 10:32:55  Fetching content directory...
2018-12-10 10:32:55  Fetching ContentDir from registry store
2018-12-10 10:32:55  Value is F:\WSUSUpdates
2018-12-10 10:32:55  Fetching group SIDs...
2018-12-10 10:32:55  Fetching WsusAdministratorsSid from registry store
2018-12-10 10:32:55  Value is S-1-5-21-3958249549-1187530241-1261074650-1006
2018-12-10 10:32:55  Fetching WsusReportersSid from registry store
2018-12-10 10:32:55  Value is S-1-5-21-3958249549-1187530241-1261074650-1007
2018-12-10 10:32:55  Creating group principals...
2018-12-10 10:32:55  Granting directory permissions...
2018-12-10 10:32:55  Granting permissions on content directory...
2018-12-10 10:32:55  Granting registry permissions...
2018-12-10 10:32:55  Granting registry permissions...
2018-12-10 10:32:55  Granting registry permissions...
2018-12-10 10:32:55  Configuring shares...
2018-12-10 10:32:55  Configuring network shares...
2018-12-10 10:32:55  Fetching content directory...
2018-12-10 10:32:55  Fetching ContentDir from registry store
2018-12-10 10:32:55  Value is F:\WSUSUpdates
2018-12-10 10:32:55  Fetching WSUS admin SID...
2018-12-10 10:32:55  Fetching WsusAdministratorsSid from registry store
2018-12-10 10:32:55  Value is S-1-5-21-3958249549-1187530241-1261074650-1006
2018-12-10 10:32:55  Content directory is local, creating content shares...
2018-12-10 10:32:55  Creating share "UpdateServicesPackages" with path "F:\WSUSUpdates\UpdateServicesPackages" and description "A network share to be used by client systems for collecting all software packages (usually applications) published on this WSUS system."
2018-12-10 10:32:55  Deleting existing share...
2018-12-10 10:32:55  Creating share...
2018-12-10 10:32:55  Share successfully created
2018-12-10 10:32:55  Creating share "WsusContent" with path "F:\WSUSUpdates\WsusContent" and description "A network share to be used by Local Publishing to place published content on this WSUS system."
2018-12-10 10:32:55  Deleting existing share...
2018-12-10 10:32:55  Creating share...
2018-12-10 10:32:55  Share successfully created
2018-12-10 10:32:55  Creating share "WSUSTemp" with path "C:\Program Files\Update Services\LogFiles\WSUSTemp" and description "A network share used by Local Publishing from a Remote WSUS Console Instance."
2018-12-10 10:32:55  Deleting existing share...
2018-12-10 10:32:55  Creating share...
2018-12-10 10:32:55  Share successfully created
2018-12-10 10:32:55  Finished creating content shares
2018-12-10 10:32:55  Stopping service WSUSService
2018-12-10 10:32:55  Stopping service W3SVC
2018-12-10 10:34:27  Configuring database...
2018-12-10 10:34:27  Configuring the database...
2018-12-10 10:34:27  Establishing DB connection...
2018-12-10 10:34:27  Checking to see if database exists...
2018-12-10 10:34:27  Database exists
2018-12-10 10:34:27  Switching database to single user mode...
2018-12-10 10:34:30  Loading install type query...
2018-12-10 10:34:30  DECLARE @currentDBVersion       int
DECLARE @scriptMajorVersion     int = (14393)
DECLARE @scriptMinorVersion     int = (0)
DECLARE @databaseMajorVersion   int 
DECLARE @databaseMinorVersion   int 
DECLARE @databaseBuildNumber    nvarchar(10)
IF NOT EXISTS(SELECT * FROM sys.databases WHERE name='SUSDB')
BEGIN
    SELECT 1
END
ELSE
BEGIN
    SET @currentDBVersion = (SELECT SchemaVersion FROM SUSDB.dbo.tbSchemaVersion WHERE ComponentName = 'CoreDB')
    SET @databaseBuildNumber = (SELECT BuildNumber FROM SUSDB.dbo.tbSchemaVersion WHERE ComponentName = 'CoreDB')
    DECLARE @delimiterPosition INT = CHARINDEX('.', @databaseBuildNumber)
    IF (@delimiterPosition = 0)
    BEGIN
        RAISERROR('Invalid schema version number', 16, 1) with nowait
        return 
    END 
    SET @databaseMajorVersion = SUBSTRING(@databaseBuildNumber, 1, @delimiterPosition - 1)
    SET @databaseMinorVersion = SUBSTRING(@databaseBuildNumber, (@delimiterPosition + 1), (10 - @delimiterPosition))
    IF @currentDBVersion < 926
    BEGIN
        SELECT 3
    END
    ELSE
    BEGIN
        IF (@scriptMajorVersion > @databaseMajorVersion OR
           (@scriptMajorVersion = @databaseMajorVersion AND @scriptMinorVersion > @databaseMinorVersion))
        BEGIN
            SELECT 2
        END
        ELSE IF (@scriptMajorVersion = @databaseMajorVersion AND
                 @scriptMinorVersion = @databaseMinorVersion)
        BEGIN
            SELECT 0
        END
        ELSE
        BEGIN
            SELECT 4
        END
    END
END

2018-12-10 10:34:30  Install type is: Reinstall
2018-12-10 10:34:30  Creating logins...
2018-12-10 10:34:30  Fetching machine account info
2018-12-10 10:34:30  Found principal
2018-12-10 10:34:30  Found account
2018-12-10 10:34:30  Got binary SID
2018-12-10 10:34:30  Setting content location...
2018-12-10 10:34:30  Fetching ContentDir from registry store
2018-12-10 10:34:30  Value is F:\WSUSUpdates
2018-12-10 10:34:30  Swtching DB to multi-user mode......
2018-12-10 10:34:30  Finished setting multi-user mode
2018-12-10 10:34:30  Writing DB settings to registry...
2018-12-10 10:34:30  Disposing Connection
2018-12-10 10:34:30  Clearing Connection Pools
2018-12-10 10:34:30  Marking PostInstall done for UpdateServices-Database in the registry...
2018-12-10 10:34:30  Starting service W3SVC
2018-12-10 10:34:30  Configuring IIS...
2018-12-10 10:34:30  Start: ConfigureWebsite
2018-12-10 10:34:31  Configuring website on port 8530
2018-12-10 10:35:05  2018-12-10 10:13:39  Info      IISCustomAction    Performing Setup Action, Command /Install 
2018-12-10 10:14:02  Info      IISCustomAction    Command /Install Succeeded
2018-12-10 10:34:41  Info      IISCustomAction    Performing Setup Action, Command /Install 
2018-12-10 10:35:04  Info      IISCustomAction    Command /Install Succeeded

2018-12-10 10:35:05  End: ConfigureWebsite
2018-12-10 10:35:05  Configuring performance counters...
2018-12-10 10:35:05  Configuring Stats.NET perf counter...
2018-12-10 10:35:05  Configuring reporting perf counter...
2018-12-10 10:35:05  Configuring client webservice perf counter...
2018-12-10 10:35:05  Configuring server sync webservice perf counter...
2018-12-10 10:35:05  Configuring API remoting perf counter...
2018-12-10 10:35:05  Bringing services online...
2018-12-10 10:35:05  Checking initialization status... 
2018-12-10 10:35:05  Database needs initialization.
2018-12-10 10:35:05  StartServer starting...
2018-12-10 10:35:05  Generating encryption key to write to the registry...
2018-12-10 10:35:05  Generating encryption key to write to the database...
2018-12-10 10:35:05  Generating encryption key succeeded...
2018-12-10 10:35:05  Setting WSUSService to autostart...
2018-12-10 10:35:05  WSUSService is set to autostart.
2018-12-10 10:35:05  Starting WSUSService...
2018-12-10 10:35:05  WSUSService is now started.
2018-12-10 10:35:05  Importing default detectoids.
2018-12-10 10:35:05  Importing CriticalUpdates.xml...
2018-12-10 10:35:06  Importing Drivers.xml...
2018-12-10 10:35:06  Importing DriverSets.xml...
2018-12-10 10:35:06  Importing FeaturePacks.xml...
2018-12-10 10:35:06  Importing MicrosoftCorporation.xml...
2018-12-10 10:35:06  Importing SecurityUpdates.xml...
2018-12-10 10:35:06  Importing ServicePacks.xml...
2018-12-10 10:35:07  Importing Tools.xml...
2018-12-10 10:35:07  Importing UpdateRollups.xml...
2018-12-10 10:35:07  Importing Updates.xml...
2018-12-10 10:35:07  Importing Windows.xml...
2018-12-10 10:35:07  Importing Windows2000family.xml...
2018-12-10 10:35:07  Importing WindowsServer2003DatacenterEdition.xml...
2018-12-10 10:35:07  Importing WindowsServer2003Family.xml...
2018-12-10 10:35:07  Importing WindowsXPfamily.xml...
2018-12-10 10:35:07  Importing LocalPublisher.xml...
2018-12-10 10:35:07  Importing LocallyPublishedPackages.xml...
2018-12-10 10:35:07  Importing Applications.xml...
2018-12-10 10:35:07  Importing Exchange.xml...
2018-12-10 10:35:07  Importing Office.xml...
2018-12-10 10:35:07  Importing SQL.xml...
2018-12-10 10:35:07  Importing Exchange2000Server.xml...
2018-12-10 10:35:07  Importing ExchangeServer2003.xml...
2018-12-10 10:35:07  Importing OfficeXP.xml...
2018-12-10 10:35:07  Importing Office2003.xml...
2018-12-10 10:35:07  Importing SQLServer.xml...
2018-12-10 10:35:07  Importing WindowsXP64BitEditionVersion2003.xml...
2018-12-10 10:35:07  Importing DefinitionUpdateSusXml.xml...
2018-12-10 10:35:08  Importing ClientServicingApiDetectoid.xml...
2018-12-10 10:35:08  Importing default detectoids succeeded.
2018-12-10 10:35:08  Creating default subscription.
2018-12-10 10:35:08  Instantiating UpdateServer
2018-12-10 10:35:10  Calling GetConfiguration
2018-12-10 10:35:14  Instantiating Subscription
2018-12-10 10:35:14  Instantiating UpdateCategoryCollection
2018-12-10 10:35:14  Adding Windows Category
2018-12-10 10:35:14  Instantiating UpdateClassificationCollection
2018-12-10 10:35:14  Adding Critical Updates classification
2018-12-10 10:35:14  Adding Security Updates classification
2018-12-10 10:35:14  Adding Definition Updates classification
2018-12-10 10:35:14  Set subscription values
2018-12-10 10:35:14  Saving Subscription
2018-12-10 10:35:14  Creating default subscription succeeded.
2018-12-10 10:35:14  Populating Auto-Approval Rules.
2018-12-10 10:35:15  Populating Auto-Approval Rules Succeeded.
2018-12-10 10:35:15  StartServer completed successfully.
2018-12-10 10:35:15  Marking PostInstall done for UpdateServices-Services in the registry...
2018-12-10 10:35:15  Mark initialization done in database...
2018-12-10 10:35:15  End: Run
2018-12-10 10:35:15  Postinstall completed

It works...

Thanks,
Dom

Security / System Center Configuration Manager Current Branch / SQL

Edited by Felyjos Monday, December 10, 2018 6:43 PM

Monday, December 10, 2018 6:39 PM

0

Sign in to vote

Hello,

So now that WSUS has been reinstalled what should I verify/confirm?

Checking the registries for each WSU/SUP server and there are discrepancies...

- Wrong ContentDir need to rerun postinstall to change it. Rerun the PostInstall and the ContentDir is fixed...

- wrong portnumber, it should be 8531? not sure how to change it as IIS is already set to 8531

- wrong UseSSL, it should be 1?
Are these changes to be done in WSUS or SCCM?

I removed then add the SUP role with ports (8530,8531) in SCCM and Use SSL checked but the registry did not change...

Also the SCUP is not communicating anymore with WSUS...!!!

==================== Exception Detail Start =======================	TestWSUSConnectionCommand	12/10/2018 6:17:06 PM	2056 (0x0808)
Exception type: WebException	TestWSUSConnectionCommand	12/10/2018 6:17:06 PM	2056 (0x0808)
Exception HRESULT: -2146233079	TestWSUSConnectionCommand	12/10/2018 6:17:06 PM	2056 (0x0808)
Exception Message: The underlying connection was closed: An unexpected error occurred on a receive.	TestWSUSConnectionCommand	12/10/2018 6:17:06 PM	2056 (0x0808)
Exception source Microsoft.UpdateServices.Administration 	TestWSUSConnectionCommand	12/10/2018 6:17:06 PM	2056 (0x0808)
Exception TargetSite Microsoft.UpdateServices.Administration.IUpdateServer CreateUpdateServer(System.Object[])	TestWSUSConnectionCommand	12/10/2018 6:17:06 PM	2056 (0x0808)
Stack:    at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)
   at Microsoft.UpdatesPublisher.BaseServices.WSUS.UpdateServicesWrapper.Connect()
   at Microsoft.UpdatesPublisher.UI.Settings.TestWSUSConnectionCommand.GetConnection(IWSUSServerConnectionInfo connectionInfo)
   at Microsoft.UpdatesPublisher.UI.Settings.TestWSUSConnectionCommand.<TestConnectionAsync>d__6.MoveNext()	TestWSUSConnectionCommand	12/10/2018 6:17:06 PM	2056 (0x0808)
===================== Exception Detail End ========================	TestWSUSConnectionCommand	12/10/2018 6:17:06 PM	2056 (0x0808)
Test of wsus connection completed, result = Failed.	SettingsWindowViewModel	12/10/2018 6:17:28 PM	6788 (0x1A84)
Testing update server connection.	TestWSUSConnectionCommand	12/10/2018 6:17:42 PM	4724 (0x1274)
Verifying current update server settings...	TestWSUSConnectionCommand	12/10/2018 6:17:42 PM	4724 (0x1274)
Connecting to the update server localhost using port 8531. SSL enabled = True	UpdateServicesWrapper	12/10/2018 6:17:42 PM	4724 (0x1274)
Connecting to update server failed	UpdateServicesWrapper	12/10/2018 6:17:42 PM	4724 (0x1274)
==================== Exception Detail Start =======================	UpdateServicesWrapper	12/10/2018 6:17:42 PM	4724 (0x1274)
Exception type: WebException	UpdateServicesWrapper	12/10/2018 6:17:42 PM	4724 (0x1274)
Exception HRESULT: -2146233079	UpdateServicesWrapper	12/10/2018 6:17:42 PM	4724 (0x1274)
Exception Message: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.	UpdateServicesWrapper	12/10/2018 6:17:42 PM	4724 (0x1274)
Exception source Microsoft.UpdateServices.Administration 	UpdateServicesWrapper	12/10/2018 6:17:42 PM	4724 (0x1274)
Exception TargetSite Microsoft.UpdateServices.Administration.IUpdateServer CreateUpdateServer(System.Object[])	UpdateServicesWrapper	12/10/2018 6:17:42 PM	4724 (0x1274)
Stack:    at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)
   at Microsoft.UpdatesPublisher.BaseServices.WSUS.UpdateServicesWrapper.Connect()	UpdateServicesWrapper	12/10/2018 6:17:42 PM	4724 (0x1274)
===================== Exception Detail End ========================	UpdateServicesWrapper	12/10/2018 6:17:42 PM	4724 (0x1274)
Failed to connect to the update server using the configuration data provided.	TestWSUSConnectionCommand	12/10/2018 6:17:42 PM	4724 (0x1274)
==================== Exception Detail Start =======================	TestWSUSConnectionCommand	12/10/2018 6:17:42 PM	4724 (0x1274)
Exception type: WebException	TestWSUSConnectionCommand	12/10/2018 6:17:42 PM	4724 (0x1274)
Exception HRESULT: -2146233079	TestWSUSConnectionCommand	12/10/2018 6:17:42 PM	4724 (0x1274)
Exception Message: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.	TestWSUSConnectionCommand	12/10/2018 6:17:42 PM	4724 (0x1274)
Exception source Microsoft.UpdateServices.Administration 	TestWSUSConnectionCommand	12/10/2018 6:17:42 PM	4724 (0x1274)
Exception TargetSite Microsoft.UpdateServices.Administration.IUpdateServer CreateUpdateServer(System.Object[])	TestWSUSConnectionCommand	12/10/2018 6:17:42 PM	4724 (0x1274)
Stack:    at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)
   at Microsoft.UpdatesPublisher.BaseServices.WSUS.UpdateServicesWrapper.Connect()
   at Microsoft.UpdatesPublisher.UI.Settings.TestWSUSConnectionCommand.GetConnection(IWSUSServerConnectionInfo connectionInfo)
   at Microsoft.UpdatesPublisher.UI.Settings.TestWSUSConnectionCommand.<TestConnectionAsync>d__6.MoveNext()	TestWSUSConnectionCommand	12/10/2018 6:17:42 PM	4724 (0x1274)
===================== Exception Detail End ========================	TestWSUSConnectionCommand	12/10/2018 6:17:42 PM	4724 (0x1274)
Test of wsus connection completed, result = Failed.	SettingsWindowViewModel	12/10/2018 6:17:47 PM	6788 (0x1A84)
FinishInteraction is closing the window.	DialogService	12/10/2018 6:18:00 PM	6788 (0x1A84)
Settings dialog has closed.	OpenSettingsCommand	12/10/2018 6:18:00 PM	6788 (0x1A84)

============================================================

- Cleanup to be in place for a monthly run?

- Software Update Point to be reinstalled?

- Launch Synchronization in SCCM?

Thanks,
Dom

Security / System Center Configuration Manager Current Branch / SQL

Edited by Felyjos Tuesday, December 11, 2018 2:29 AM

Monday, December 10, 2018 6:57 PM

1

Sign in to vote

Hello,

1> SSL

SSL should be configured in WSUS and then SUP. In WSUS, we need to import the cert, bind the port, and enable SSL. Refer to the following article.

How to configure a Software Update Point to use SSL for communicating with WSUS
https://www.petervanderwoude.nl/post/how-to-configure-a-software-update-point-to-use-ssl-for-communicating-with-wsus/

2> Then check if SUP works with WSUS. Normally, we should remove SUP before recreating SUSDB. If SUP not works, reinstall it and check the result.

Best Regards,
Ray

Please remember to mark the replies as answers if they help.

If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

Marked as answer by Felyjos Friday, December 14, 2018 3:32 AM

Tuesday, December 11, 2018 11:25 AM

0

Sign in to vote

Thank you again Ray.

The SUPs have been removed during the clean up (it is taking so long!!!)...

I will do SSL in WSUS to get the correct for the first server ISS-SU01.

When you say "If SUP does not work" is it through the synchronization process or only the installation of the SUP?

WCM.log looks good for the connection… failed on third party category not sure why as they should be coming from the ISS-SU01 site server through SCUP.

Attempting connection to WSUS server: VRPSCCMSU01.ad.xxxxxxx.xxxx.xxx, port: 8531, useSSL: True		SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 8:08:09 AM	15252 (0x3B94)
Successfully connected to server: VRPSCCMSU01.ad.xxxxxx.xxxx.xxx, port: 8531, useSSL: True		SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 8:08:09 AM	15252 (0x3B94)
Category Company:65d2506b-799c-4ff4-408d-d4ee00ff7d41 (Mozilla) not found on WSUS			SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 8:08:09 AM	15252 (0x3B94)
Category Company:94d731de-22a6-4458-dc4d-b5267de026fc (Adobe Systems, Inc.) not found on WSUS	SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 8:08:09 AM	15252 (0x3B94)
Category Company:a9309775-437e-f373-a0ee-12805db065e3 (Google) not found on WSUS		SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 8:08:09 AM	15252 (0x3B94)
Category Company:b6641343-0f45-7cc4-cdbf-6a2205dfdb1b (Oracle) not found on WSUS			SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 8:08:09 AM	15252 (0x3B94)
Category Product:b34fd66d-1621-881c-2a7f-784ee9ee16eb (Software) not found on WSUS		SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 8:08:09 AM	15252 (0x3B94)
Category Product:bafa339f-057c-c714-477f-666e03578cb1 (Firmware) not found on WSUS		SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 8:08:09 AM	15252 (0x3B94)
Subscription contains categories unknown to WSUS.						SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 8:08:10 AM	15252 (0x3B94)
Failed to set Subscriptions on the WSUS Server. Error:(-2147467259)Unspecified error			SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 8:08:10 AM	15252 (0x3B94)

Still looking for the other log WSUSCtrl.log...

..\SMS\LogsOn the WSUS/SUP Site System Server

Attempting connection to local WSUS server							SMS_WSUS_CONTROL_MANAGER	12/11/2018 8:56:53 AM	4556 (0x11CC)
Successfully connected to local WSUS server							SMS_WSUS_CONTROL_MANAGER	12/11/2018 8:56:53 AM	4556 (0x11CC)
There are no unhealthy WSUS Server components on WSUS Server VRPSCCMSU01.AD.XXXXXX.XXXX.XXX	SMS_WSUS_CONTROL_MANAGER	12/11/2018 8:56:53 AM	4556 (0x11CC)
Successfully checked database connection on WSUS server VRPSCCMSU01.AD.XXXXXX.XXXX.XXX		SMS_WSUS_CONTROL_MANAGER	12/11/2018 8:56:53 AM	4556 (0x11CC)

So the first WSUS/SUP looks fine!

Now IBCM01

WCM.log

Attempting connection to WSUS server: VRPSCCMIBCM01.ad.xxxxxx.xxxx.xxx, port: 8531, useSSL: True	SMS_WSUS_CONFIGURATION_MANAGER	12/10/2018 3:28:09 PM	15472 (0x3C70)
Successfully connected to server: VRPSCCMIBCM01.ad.xxxxxx.xxxx.xxx, port: 8531, useSSL: True	SMS_WSUS_CONFIGURATION_MANAGER	12/10/2018 3:28:09 PM	15472 (0x3C70)

WSUSCtrl.log

Attempting connection to local WSUS server	SMS_WSUS_CONTROL_MANAGER	12/10/2018 2:58:51 PM	4920 (0x1338)
Successfully connected to local WSUS server	SMS_WSUS_CONTROL_MANAGER	12/10/2018 2:58:51 PM	4920 (0x1338)
There are no unhealthy WSUS Server components on WSUS Server VRPSCCMIBCM01.AD.XXXXXX.XXXX.XXX	SMS_WSUS_CONTROL_MANAGER	12/10/2018 2:58:51 PM	4920 (0x1338)
Successfully checked database connection on WSUS server VRPSCCMIBCM01.AD.XXXXXX.XXXX.XXX	SMS_WSUS_CONTROL_MANAGER	12/10/2018 2:58:51 PM	4920 (0x1338)

Should I try a Synchronization or do the downstream WSUS/SUP Servers?

SCUP is not working well as I could not publish the Third Party patches anymore... I was waiting for this before synchronizing as the sync might take awhile to complete.

Thanks,
Dom

Security / System Center Configuration Manager Current Branch / SQL

Edited by Felyjos Tuesday, December 11, 2018 7:25 PM

Tuesday, December 11, 2018 3:35 PM

0

Sign in to vote

Hello,

Clearing the classifications as recommended ...

Launching the first synchronization...

Found local sync request file SMS_WSUS_SYNC_MANAGER 12/11/2018 12:18:09 PM 13008 (0x32D0) Starting Sync SMS_WSUS_SYNC_MANAGER 12/11/2018 12:18:09 PM 13008 (0x32D0) Performing sync on local request SMS_WSUS_S YNC_MANAGER 12/11/2018 12:18:09 PM 13008 (0x32D0) Full sync required due to changes in category subscriptions. SMS_WSUS_SYNC_MANAGER 12/11/2018 12:18:09 PM 13008 (0x32D0) Read SUPs from SCF for VRPSCCMPR01.ad.xxxxxx.xxxx.xxx SMS_WSUS_SYNC_MANAGER 12/11/2018 12:18:09 PM 13008 (0x32D0) Found 1 SUPs SMS_WSUS_SYNC_MANAGER 12/11/2018 12:18:09 PM 13008 (0x32D0) Found active SUP VRPSCCMSU01.ad.xxxxxx.xxxx.xxx from SCF File. SMS_WSUS_SYNC_MANAGER 12/11/2018 12:18:09 PM 13008 (0x32D0) Sync failed: WSUS update source not found on site UCP.

Please refer to WCM.log for configuration error details..

Source: getSiteUpdateSource SMS_WSUS_SYNC_MANAGER 12/11/2018 12:18:09 PM 13008 (0x32D0) STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server"

COMP="SMS_WSUS_SYNC_MANAGER"

SYS=VRPSCCMPR01.AD.XXXXXX.XXXX.XXX SITE=UCP PID=652 TID=13008

GMTDATE=Tue Dec 11 20:18:09.875 2018

ISTR0="getSiteUpdateSource"

ISTR1="WSUS update source not found on site UCP. Please refer

to WCM.log for configuration error details." ISTR2="" ISTR3=""

ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9=""

NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 12/11/2018 12:18:09 PM 13008 (0x32D0) Sync failed. Will retry in 60 minutes SMS_WSUS_SYNC_MANAGER 12/11/2018 12:18:09 PM 13008 (0x32D0)

I am checking WCM.log now

Trigger event array index 1 ended.								SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 12:15:39 PM	15252 (0x3B94)
File notification triggered.									SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 12:15:39 PM	15252 (0x3B94)
File notification triggered WCM Inbox.								SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 12:15:44 PM	15252 (0x3B94)
Attempting connection to WSUS server: VRPSCCMSU01.ad.xxxxxx.xxxx.xxx, port: 8531, useSSL: True	SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 12:15:44 PM	15252 (0x3B94)
Successfully connected to server: VRPSCCMSU01.ad.xxxxxx.xxxx.xxx, port: 8531, useSSL: True	SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 12:15:44 PM	15252 (0x3B94)
Category Company:65d2506b-799c-4ff4-408d-d4ee00ff7d41 (Mozilla) not found on WSUS		SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 12:15:44 PM	15252 (0x3B94)
Category Company:a9309775-437e-f373-a0ee-12805db065e3 (Google) not found on WSUS		SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 12:15:44 PM	15252 (0x3B94)
Category Company:b6641343-0f45-7cc4-cdbf-6a2205dfdb1b (Oracle) not found on WSUS		SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 12:15:44 PM	15252 (0x3B94)
Category Product:b34fd66d-1621-881c-2a7f-784ee9ee16eb (Software) not found on WSUS		SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 12:15:44 PM	15252 (0x3B94)
Category Product:bafa339f-057c-c714-477f-666e03578cb1 (Firmware) not found on WSUS		SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 12:15:44 PM	15252 (0x3B94)
Starting WSUS category sync from upstream...							SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 12:15:44 PM	15252 (0x3B94)
Refreshing categories from WSUS server								SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 12:15:49 PM	15252 (0x3B94)
Attempting connection to WSUS server: VRPSCCMSU01.ad.xxxxxx.xxxx.xxx, port: 8531, useSSL: True	SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 12:15:49 PM	15252 (0x3B94)
Successfully connected to server: VRPSCCMSU01.ad.xxxxxx.xxxx.xxx, port: 8531, useSSL: True	SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 12:15:49 PM	15252 (0x3B94)
Successfully refreshed categories from WSUS server						SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 12:16:04 PM	15252 (0x3B94)
Attempting connection to WSUS server: VRPSCCMSU01.ad.xxxxxx.xxxx.xxx, port: 8531, useSSL: True	SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 12:16:04 PM	15252 (0x3B94)
Successfully connected to server: VRPSCCMSU01.ad.xxxxxx.xxxx.xxx, port: 8531, useSSL: True	SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 12:16:04 PM	15252 (0x3B94)
Category Company:65d2506b-799c-4ff4-408d-d4ee00ff7d41 (Mozilla) not found on WSUS		SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 12:16:04 PM	15252 (0x3B94)
Category Company:a9309775-437e-f373-a0ee-12805db065e3 (Google) not found on WSUS		SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 12:16:04 PM	15252 (0x3B94)
Category Company:b6641343-0f45-7cc4-cdbf-6a2205dfdb1b (Oracle) not found on WSUS		SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 12:16:04 PM	15252 (0x3B94)
Category Product:b34fd66d-1621-881c-2a7f-784ee9ee16eb (Software) not found on WSUS		SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 12:16:04 PM	15252 (0x3B94)
Category Product:bafa339f-057c-c714-477f-666e03578cb1 (Firmware) not found on WSUS		SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 12:16:04 PM	15252 (0x3B94)
Subscription contains categories unknown to WSUS.						SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 12:16:04 PM	15252 (0x3B94)
Failed to set Subscriptions on the WSUS Server. Error:(-2147467259)Unspecified error		SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 12:16:04 PM	15252 (0x3B94)
STATMSG: ID=6603 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" 
SYS=VRPSCCMPR01.AD.xxxxxx.xxxx.xxx SITE=UCP PID=652 TID=15252 GMTDATE=Tue Dec 11 20:16:04.828 
2018 ISTR0="VRPSCCMSU01.ad.xxxxxx.xxxx.xxx" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" 
ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0							SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 12:16:04 PM	15252 (0x3B94)
Waiting for changes for 51 minutes								SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 12:16:04 PM	15252 (0x3B94)

Any idea?

Thanks,

Dom

Security / System Center Configuration Manager Current Branch / SQL

Edited by Felyjos Tuesday, December 11, 2018 8:35 PM

Tuesday, December 11, 2018 8:26 PM

0

Sign in to vote

Hello,

I unchecked all Classifications and Products and still two errors:

Wait timed out after 5 minutes while waiting for at least one trigger event.				SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 2:07:20 PM	15252 (0x3B94)
Timed Out...										SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 2:07:30 PM	15252 (0x3B94)
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)			SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 2:07:30 PM	15252 (0x3B94)
Checking runtime v4.0.30319...								SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 2:07:30 PM	15252 (0x3B94)
Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.2.14393.0	SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 2:07:30 PM	15252 (0x3B94)
Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.2.14393.2608	SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 2:07:30 PM	15252 (0x3B94)
Supported WSUS version found								SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 2:07:30 PM	15252 (0x3B94)
Attempting connection to WSUS server: VRPSCCMSU01.ad.xxxxxx.xxxx.xxx, port: 8531, useSSL: True		SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 2:07:30 PM	15252 (0x3B94)
Successfully connected to server: VRPSCCMSU01.ad.xxxxxx.xxxx.xxx, port: 8531, useSSL: True		SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 2:07:30 PM	15252 (0x3B94)
Verify Upstream Server settings on the Active WSUS Server						SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 2:07:30 PM	15252 (0x3B94)
No changes - WSUS Server settings are correctly configured and Upstream Server is set to Microsoft Update	SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 2:07:30 PM	15252 (0x3B94)
WSUS Server configuration has been updated. Updating Group Info.					SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 2:07:30 PM	15252 (0x3B94)
Updating Group Info for WSUS.								SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 2:07:30 PM	15252 (0x3B94)
Refreshing categories from WSUS server							SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 2:07:30 PM	15252 (0x3B94)
Attempting connection to WSUS server: VRPSCCMSU01.ad.xxxxxx.xxxx.xxx, port: 8531, useSSL: True		SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 2:07:30 PM	15252 (0x3B94)
Successfully connected to server: VRPSCCMSU01.ad.xxxxxx.xxxx.xxx, port: 8531, useSSL: True		SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 2:07:30 PM	15252 (0x3B94)
Successfully refreshed categories from WSUS server						SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 2:07:47 PM	15252 (0x3B94)
Attempting connection to WSUS server: VRPSCCMSU01.ad.xxxxxx.xxxx.xxx, port: 8531, useSSL: True		SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 2:07:52 PM	15252 (0x3B94)
Successfully connected to server: VRPSCCMSU01.ad.xxxxxx.xxxx.xxx, port: 8531, useSSL: True		SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 2:07:52 PM	15252 (0x3B94)
Category Product:b34fd66d-1621-881c-2a7f-784ee9ee16eb (Software) not found on WSUS		SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 2:07:52 PM	15252 (0x3B94)
Category Product:bafa339f-057c-c714-477f-666e03578cb1 (Firmware) not found on WSUS		SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 2:07:52 PM	15252 (0x3B94)
Starting WSUS category sync from upstream...							SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 2:07:52 PM	15252 (0x3B94)
Refreshing categories from WSUS server							SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 2:07:57 PM	15252 (0x3B94)
Attempting connection to WSUS server: VRPSCCMSU01.ad.xxxxxx.xxxx.xxx, port: 8531, useSSL: True		SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 2:07:57 PM	15252 (0x3B94)
Successfully connected to server: VRPSCCMSU01.ad.xxxxxx.xxxx.xxx, port: 8531, useSSL: True		SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 2:07:57 PM	15252 (0x3B94)
Successfully refreshed categories from WSUS server						SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 2:08:16 PM	15252 (0x3B94)
Attempting connection to WSUS server: VRPSCCMSU01.ad.xxxxxx.xxxx.xxx, port: 8531, useSSL: True		SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 2:08:16 PM	15252 (0x3B94)
Successfully connected to server: VRPSCCMSU01.ad.xxxxxx.xxxx.xxx, port: 8531, useSSL: True		SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 2:08:16 PM	15252 (0x3B94)
Category Product:b34fd66d-1621-881c-2a7f-784ee9ee16eb (Software) not found on WSUS		SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 2:08:16 PM	15252 (0x3B94)
Category Product:bafa339f-057c-c714-477f-666e03578cb1 (Firmware) not found on WSUS		SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 2:08:16 PM	15252 (0x3B94)
Subscription contains categories unknown to WSUS.						SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 2:08:16 PM	15252 (0x3B94)
Failed to set Subscriptions on the WSUS Server. Error:(-2147467259)Unspecified error			SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 2:08:16 PM	15252 (0x3B94)
STATMSG: ID=6603 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER"
 SYS=VRPSCCMPR01.AD.xxxxxx.xxxx.xxx SITE=UCP PID=652 TID=15252 GMTDATE=Tue Dec 11 22:08:16.359 2018
 ISTR0="VRPSCCMSU01.ad.xxxxxx.xxxx.xxx" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" 
ISTR8="" ISTR9="" NUMATTRS=0								SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 2:08:16 PM	15252 (0x3B94)
Waiting for changes for 59 minutes								SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 2:08:16 PM	15252 (0x3B94)

looking for these categories...

How to remove them?

Category Product:b34fd66d-1621-881c-2a7f-784ee9ee16eb (Software) not found on WSUS

Category Product:bafa339f-057c-c714-477f-666e03578cb1 (Firmware) not found on WSUS

Apparently this is due to SCUP there are discrepancies between the new SUSDB database (reinstall afresh) and the old SCUP database (active previously).

How to cleanup SCUP?

Should I uncheck the "Enable Configuration Manager integration"?

or Update Server?

Then check it again? Any specific tasks to be done in between?

or

How to populate WSUS with the content of SCUP?

I found the two items in the database:

select CategoryInstance_UniqueID, CategoryInstanceName
from fn_ListUpdateCategoryInstances(9) cat
where cat.AllowSubscription=1 and cat.IsSubscribed=1 and cat.IsParentSubscribed=0
order by cat.CategoryInstance_UniqueID

CategoryInstance_UniqueID	                CategoryInstanceName
Product:b34fd66d-1621-881c-2a7f-784ee9ee16eb	Software
Product:bafa339f-057c-c714-477f-666e03578cb1	Firmware

How to remove them? Could I unsubscribe them in the database? These are the only ones subscribed... IsSubscribed=1

Should I change it to 0? Any way to change it from a GUI or somewhere else than the table itself?

Select * from v_UpdateCategoryInstances
Where IsSubscribed = '1'

UPDATE CI_UpdateCategorySubscription
SET IsSubscribed = '0'
WHERE
CategoryInstanceID='16777686'
or
CategoryInstanceID='16777688'

Thanks,

Dom

Security / System Center Configuration Manager Current Branch / SQL

Edited by Felyjos Wednesday, December 12, 2018 3:18 AM

Tuesday, December 11, 2018 10:20 PM

0

Sign in to vote

Hello,

First synchronization with empty classification, product, and no SCUP

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Wakeup by inbox drop									SMS_WSUS_SYNC_MANAGER	12/11/2018 9:02:11 PM	6280 (0x1888)
Found local sync request file									SMS_WSUS_SYNC_MANAGER	12/11/2018 9:02:16 PM	6280 (0x1888)
Starting Sync										SMS_WSUS_SYNC_MANAGER	12/11/2018 9:02:16 PM	6280 (0x1888)
Performing sync on local request								SMS_WSUS_SYNC_MANAGER	12/11/2018 9:02:16 PM	6280 (0x1888)
Read SUPs from SCF for VRPSCCMPR01.ad.XXXXXX.XXXX.XXX					SMS_WSUS_SYNC_MANAGER	12/11/2018 9:02:16 PM	6280 (0x1888)
Found 1 SUPs										SMS_WSUS_SYNC_MANAGER	12/11/2018 9:02:16 PM	6280 (0x1888)
Found active SUP VRPSCCMSU01.ad.XXXXXX.XXXX.XXX from SCF File.					SMS_WSUS_SYNC_MANAGER	12/11/2018 9:02:16 PM	6280 (0x1888)
STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" 
SYS=VRPSCCMPR01.AD.XXXXXX.XXXX.XXX SITE=UCP PID=2932 TID=6280 GMTDATE=Wed Dec 12 05:02:16.081 
2018 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
											SMS_WSUS_SYNC_MANAGER	12/11/2018 9:02:16 PM	6280 (0x1888)
Sync Surface Drivers option is not set								SMS_WSUS_SYNC_MANAGER	12/11/2018 9:02:17 PM	6280 (0x1888)
Synchronizing WSUS server VRPSCCMSU01.ad.XXXXXX.XXXX.XXX					SMS_WSUS_SYNC_MANAGER	12/11/2018 9:02:17 PM	6280 (0x1888)
STATMSG: ID=6704 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" 
SYS=VRPSCCMPR01.AD.XXXXXX.XXXX.XXX SITE=UCP PID=2932 TID=6280 GMTDATE=Wed Dec 12 05:02:17.105
 2018 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
											SMS_WSUS_SYNC_MANAGER	12/11/2018 9:02:17 PM	6280 (0x1888)
https://VRPSCCMSU01.ad.XXXXXX.XXXX.XXX:8531							SMS_WSUS_SYNC_MANAGER	12/11/2018 9:02:17 PM	6980 (0x1B44)
Synchronizing WSUS server vrpsccmsu01.ad.XXXXXX.XXXX.XXX ...					SMS_WSUS_SYNC_MANAGER	12/11/2018 9:02:17 PM	6980 (0x1B44)
sync: Starting WSUS synchronization								SMS_WSUS_SYNC_MANAGER	12/11/2018 9:02:17 PM	6980 (0x1B44)
sync: WSUS synchronizing categories								SMS_WSUS_SYNC_MANAGER	12/11/2018 9:02:21 PM	6980 (0x1B44)
Done synchronizing WSUS Server vrpsccmsu01.ad.XXXXXX.XXXX.XXX					SMS_WSUS_SYNC_MANAGER	12/11/2018 9:02:23 PM	6980 (0x1B44)
Sync Catalog Drivers SCF value is set to : 0							SMS_WSUS_SYNC_MANAGER	12/11/2018 9:02:23 PM	6980 (0x1B44)
SyncGracePeriod not set, use default 120000							SMS_WSUS_SYNC_MANAGER	12/11/2018 9:02:23 PM	6980 (0x1B44)
Sleeping 120 more seconds for WSUS server sync results to become available				SMS_WSUS_SYNC_MANAGER	12/11/2018 9:02:23 PM	6980 (0x1B44)
Set content version of update source {67BB9074-421B-4166-A053-A8090F9523EF} for site UCP to 335	SMS_WSUS_SYNC_MANAGER	12/11/2018 9:04:24 PM	6280 (0x1888)
Resetting MaxInstall RunTime for Cumulative updates.						SMS_WSUS_SYNC_MANAGER	12/11/2018 9:04:24 PM	6280 (0x1888)
Synchronizing SMS database with WSUS server VRPSCCMSU01.ad.XXXXXX.XXXX.XXX			SMS_WSUS_SYNC_MANAGER	12/11/2018 9:04:26 PM	6280 (0x1888)
STATMSG: ID=6705 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" 
SYS=VRPSCCMPR01.AD.XXXXXX.XXXX.XXX SITE=UCP PID=2932 TID=6280 GMTDATE=Wed Dec 12 05:04:26.220
 2018 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
											SMS_WSUS_SYNC_MANAGER	12/11/2018 9:04:26 PM	6280 (0x1888)
https://VRPSCCMSU01.ad.XXXXXX.XXXX.XXX:8531							SMS_WSUS_SYNC_MANAGER	12/11/2018 9:04:26 PM	5792 (0x16A0)
Synchronizing SMS database with WSUS server vrpsccmsu01.ad.XXXXXX.XXXX.XXX ...			SMS_WSUS_SYNC_MANAGER	12/11/2018 9:04:26 PM	5792 (0x16A0)
sync: Starting SMS database synchronization							SMS_WSUS_SYNC_MANAGER	12/11/2018 9:04:26 PM	5792 (0x16A0)
requested localization languages: en								SMS_WSUS_SYNC_MANAGER	12/11/2018 9:04:26 PM	5792 (0x16A0)
Syncing all updates										SMS_WSUS_SYNC_MANAGER	12/11/2018 9:04:26 PM	5792 (0x16A0)
Requested categories:									SMS_WSUS_SYNC_MANAGER	12/11/2018 9:04:26 PM	5792 (0x16A0)
Third-party software updates is not enabled.							SMS_WSUS_SYNC_MANAGER	12/11/2018 9:04:26 PM	5792 (0x16A0)
sync: SMS synchronizing categories								SMS_WSUS_SYNC_MANAGER	12/11/2018 9:04:26 PM	5792 (0x16A0)
sync: SMS synchronizing categories, processed 0 out of 331 items (0%)				SMS_WSUS_SYNC_MANAGER	12/11/2018 9:04:26 PM	5792 (0x16A0)
sync: SMS synchronizing categories, processed 331 out of 331 items (100%)				SMS_WSUS_SYNC_MANAGER	12/11/2018 9:04:29 PM	5792 (0x16A0)
sync: SMS synchronizing categories, processed 331 out of 331 items (100%)				SMS_WSUS_SYNC_MANAGER	12/11/2018 9:04:29 PM	5792 (0x16A0)
Removed 1 categories									SMS_WSUS_SYNC_MANAGER	12/11/2018 9:04:29 PM	5792 (0x16A0)
WARNING: Request filter does not contain any known classifications. Sync will do nothing.			SMS_WSUS_SYNC_MANAGER	12/11/2018 9:04:29 PM	5792 (0x16A0)
WARNING: Request filter does not contain any known categories. Sync will do nothing.			SMS_WSUS_SYNC_MANAGER	12/11/2018 9:04:29 PM	5792 (0x16A0)
Done synchronizing SMS with WSUS Server vrpsccmsu01.ad.XXXXXX.XXXX.XXX				SMS_WSUS_SYNC_MANAGER	12/11/2018 9:04:29 PM	5792 (0x16A0)
Set content version of update source {67BB9074-421B-4166-A053-A8090F9523EF} for site UCP to 335	SMS_WSUS_SYNC_MANAGER	12/11/2018 9:04:30 PM	6280 (0x1888)
Resetting MaxInstall RunTime for Cumulative updates.						SMS_WSUS_SYNC_MANAGER	12/11/2018 9:04:30 PM	6280 (0x1888)
Starting cleanup on WSUS server VRPSCCMSU01.ad.XXXXXX.XXXX.XXX					SMS_WSUS_SYNC_MANAGER	12/11/2018 9:04:30 PM	6280 (0x1888)
https://VRPSCCMSU01.ad.XXXXXX.XXXX.XXX:8531							SMS_WSUS_SYNC_MANAGER	12/11/2018 9:04:30 PM	3552 (0x0DE0)
Cleaning up WSUS server vrpsccmsu01.ad.XXXXXX.XXXX.XXX ..	.				SMS_WSUS_SYNC_MANAGER	12/11/2018 9:04:30 PM	3552 (0x0DE0)
sync: Starting SMS database synchronization							SMS_WSUS_SYNC_MANAGER	12/11/2018 9:04:30 PM	3552 (0x0DE0)
requested localization languages: en								SMS_WSUS_SYNC_MANAGER	12/11/2018 9:04:30 PM	3552 (0x0DE0)
Syncing updates arrived after 12/11/2018 21:04:26						SMS_WSUS_SYNC_MANAGER	12/11/2018 9:04:30 PM	3552 (0x0DE0)
Requested categories:									SMS_WSUS_SYNC_MANAGER	12/11/2018 9:04:30 PM	3552 (0x0DE0)
WARNING: Request filter does not contain any known classifications. Sync will do nothing.			SMS_WSUS_SYNC_MANAGER	12/11/2018 9:04:30 PM	3552 (0x0DE0)
WARNING: Request filter does not contain any known categories. Sync will do nothing.			SMS_WSUS_SYNC_MANAGER	12/11/2018 9:04:30 PM	3552 (0x0DE0)
Done cleaning up WSUS Server vrpsccmsu01.ad.XXXXXX.XXXX.XXX					SMS_WSUS_SYNC_MANAGER	12/11/2018 9:04:30 PM	3552 (0x0DE0)
Set content version of update source {67BB9074-421B-4166-A053-A8090F9523EF} for site UCP to 335	SMS_WSUS_SYNC_MANAGER	12/11/2018 9:04:31 PM	6280 (0x1888)
Resetting MaxInstall RunTime for Cumulative updates.						SMS_WSUS_SYNC_MANAGER	12/11/2018 9:04:31 PM	6280 (0x1888)
STATMSG: ID=6702 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" 
SYS=VRPSCCMPR01.AD.XXXXXX.XXXX.XXX SITE=UCP PID=2932 TID=6280 GMTDATE=Wed Dec 12 05:04:31.555
 2018 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
											SMS_WSUS_SYNC_MANAGER	12/11/2018 9:04:31 PM	6280 (0x1888)
Sync succeeded. Setting sync alert to canceled state on site UCP					SMS_WSUS_SYNC_MANAGER	12/11/2018 9:04:31 PM	6280 (0x1888)
No changes made to the SMS database, content version remains 335					SMS_WSUS_SYNC_MANAGER	12/11/2018 9:04:31 PM	6280 (0x1888)
Sync time: 0d00h02m15s									SMS_WSUS_SYNC_MANAGER	12/11/2018 9:04:31 PM	6280 (0x1888)
Skipping Delete Expired Update relations since this is not a scheduled sync.				SMS_WSUS_SYNC_MANAGER	12/11/2018 9:04:31 PM	6280 (0x1888)
Inbox source is local on VRPSCCMPR01.ad.XXXXXX.XXXX.XXX						SMS_WSUS_SYNC_MANAGER	12/11/2018 9:04:32 PM	6280 (0x1888)
============================================================================================================================================================
WCM.log
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Waiting for changes for 37 minutes								SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 8:59:52 PM	6272 (0x1880)
Trigger event array index 1 ended.								SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 8:59:52 PM	6272 (0x1880)
File notification triggered.									SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 8:59:52 PM	6272 (0x1880)
File notification triggered WCM Inbox.								SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 8:59:57 PM	6272 (0x1880)
Waiting for changes for 37 minutes								SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 8:59:57 PM	6272 (0x1880)
Trigger event array index 1 ended.								SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:00:03 PM	6272 (0x1880)
File notification triggered.									SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:00:03 PM	6272 (0x1880)
File notification triggered WCM Inbox.								SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:00:08 PM	6272 (0x1880)
Attempting connection to WSUS server: VRPSCCMSU01.ad.xxxxxx.xxxx.xxx, port: 8531, useSSL: True		SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:00:08 PM	6272 (0x1880)
Successfully connected to server: VRPSCCMSU01.ad.xxxxxx.xxxx.xxx, port: 8531, useSSL: True		SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:00:08 PM	6272 (0x1880)
Subscribed Update Categories <?xml version="1.0" ?>~~<Categories>~~</Categories>			SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:00:09 PM	6272 (0x1880)
Successfully inserted WSUS Enterprise Update Source object {67BB9074-421B-4166-A053-A8090F9523EF}	SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:00:10 PM	6272 (0x1880)
Configuration successful. Will wait for 1 minute for any subscription or proxy changes			SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:00:10 PM	6272 (0x1880)
Setting new configuration state to 2 (WSUS_CONFIG_SUCCESS)					SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:01:10 PM	6272 (0x1880)
Waiting for changes for 36 minutes								SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:01:10 PM	6272 (0x1880)
Trigger event array index 1 ended.								SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:01:10 PM	6272 (0x1880)
File notification triggered.									SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:01:10 PM	6272 (0x1880)
File notification triggered WCM Inbox.								SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:01:15 PM	6272 (0x1880)
Setting new configuration state to 4 (WSUS_CONFIG_SUBSCRIPTION_PENDING)				SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:01:15 PM	6272 (0x1880)
Attempting connection to WSUS server: VRPSCCMSU01.ad.xxxxxx.xxxx.xxx, port: 8531, useSSL: True		SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:01:15 PM	6272 (0x1880)
Successfully connected to server: VRPSCCMSU01.ad.xxxxxx.xxxx.xxx, port: 8531, useSSL: True		SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:01:15 PM	6272 (0x1880)
Configuration successful. Will wait for 1 minute for any subscription or proxy changes			SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:01:15 PM	6272 (0x1880)
Setting new configuration state to 2 (WSUS_CONFIG_SUCCESS)					SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:02:15 PM	6272 (0x1880)
Waiting for changes for 35 minutes								SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:02:15 PM	6272 (0x1880)
Trigger event array index 1 ended.								SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:02:15 PM	6272 (0x1880)
File notification triggered.									SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:02:15 PM	6272 (0x1880)
File notification triggered WCM Inbox.								SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:02:20 PM	6272 (0x1880)
Waiting for changes for 35 minutes								SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:02:20 PM	6272 (0x1880)
Trigger event array index 1 ended.								SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:02:20 PM	6272 (0x1880)
File notification triggered.									SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:02:20 PM	6272 (0x1880)
File notification triggered WCM Inbox.								SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:02:25 PM	6272 (0x1880)
Waiting for changes for 35 minutes								SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:02:25 PM	6272 (0x1880)
Wait timed out after 35 minutes while waiting for at least one trigger event.				SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:37:04 PM	6272 (0x1880)
Timed Out...										SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:37:14 PM	6272 (0x1880)
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)			SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:37:14 PM	6272 (0x1880)
Checking runtime v4.0.30319...								SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:37:14 PM	6272 (0x1880)
Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.2.14393.0	SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:37:14 PM	6272 (0x1880)
Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.2.14393.2636	SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:37:14 PM	6272 (0x1880)
Supported WSUS version found								SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:37:14 PM	6272 (0x1880)
Attempting connection to WSUS server: VRPSCCMSU01.ad.xxxxxx.xxxx.xxx, port: 8531, useSSL: True		SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:37:14 PM	6272 (0x1880)
Successfully connected to server: VRPSCCMSU01.ad.xxxxxx.xxxx.xxx, port: 8531, useSSL: True		SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:37:14 PM	6272 (0x1880)
Verify Upstream Server settings on the Active WSUS Server						SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:37:14 PM	6272 (0x1880)
No changes - WSUS Server settings are correctly configured and Upstream Server is set to Microsoft Update	SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:37:14 PM	6272 (0x1880)
WSUS Server configuration has been updated. Updating Group Info.					SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:37:14 PM	6272 (0x1880)
pdating Group Info for WSUS.									SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:37:14 PM	6272 (0x1880)
Refreshing categories from WSUS server							SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:37:14 PM	6272 (0x1880)
Attempting connection to WSUS server: VRPSCCMSU01.ad.xxxxxx.xxxx.xxx, port: 8531, useSSL: True		SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:37:14 PM	6272 (0x1880)
Successfully connected to server: VRPSCCMSU01.ad.xxxxxx.xxxx.xxx, port: 8531, useSSL: True		SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:37:14 PM	6272 (0x1880)
Successfully refreshed categories from WSUS server						SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:37:29 PM	6272 (0x1880)
Attempting connection to WSUS server: VRPSCCMSU01.ad.xxxxxx.xxxx.xxx, port: 8531, useSSL: True		SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:37:34 PM	6272 (0x1880)
Successfully connected to server: VRPSCCMSU01.ad.xxxxxx.xxxx.xxx, port: 8531, useSSL: True		SMS_WSUS_CONFIGURATION_MANAGER	12/11/2018 9:37:34 PM	6272 (0x1880)
============================================================================================================================================================

Next steps:

- link scup

- add classification and products

- new synchronization

Thanks,

Dom

Security / System Center Configuration Manager Current Branch / SQL

Edited by Felyjos Wednesday, December 12, 2018 6:05 AM

Wednesday, December 12, 2018 6:04 AM

1

Sign in to vote

Hello,

Thanks for your update.

It looks that the rest main job is SCUP. Look forward to your feedback of it.

One thing should be noted is that, when you use WSUS in the SCCM environment, the sync setting such as Products/Classifications should be configured in the CM, not in the WSUS.

Best Regards,
Ray

Please remember to mark the replies as answers if they help.

If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

Marked as answer by Felyjos Friday, December 14, 2018 3:32 AM

Wednesday, December 12, 2018 10:01 AM

0

Sign in to vote

Hello,

Yes I am adding now the Product and Classifications in SCCM. Should I do SCUP at the same time or do a new synchronization only with Microsoft patches then add SCUP after and redo another one...?

Thanks,

Dom

Security / System Center Configuration Manager Current Branch / SQL

Wednesday, December 12, 2018 2:21 PM

0

Sign in to vote

Hello,

Only on Microsoft patching it is failing... is it due to the volume?

this set starts with 112580 items, when I launched again after failures it is 12,265 items then another time it is 29,123 items why it is changing ?

sync: WSUS synchronizing updates, processed 49364 out of 112580 items (43%), ETA in 01:41:24	SMS_WSUS_SYNC_MANAGER	12/12/2018 8:25:45 AM	7496 (0x1D48)
sync: WSUS synchronizing updates, processed 49649 out of 112580 items (44%), ETA in 01:41:39	SMS_WSUS_SYNC_MANAGER	12/12/2018 8:26:46 AM	7496 (0x1D48)
sync: WSUS synchronizing updates, processed 49714 out of 112580 items (44%), ETA in 01:42:42	SMS_WSUS_SYNC_MANAGER	12/12/2018 8:27:46 AM	7496 (0x1D48)
Sync failed: The request failed with HTTP status 503: Service Unavailable. Source: Microsoft.UpdateServices.Internal.ApiRemoting.GetSubscriptionState	SMS_WSUS_SYNC_MANAGER	12/12/2018 8:28:41 AM	8868 (0x22A4)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=VRPSCCMPR01.AD.xxxxxx.xxxx.xxx SITE=UCP PID=3384 TID=8868 GMTDATE=Wed Dec 12 16:28:41.216 2018 ISTR0="Microsoft.UpdateServices.Internal.ApiRemoting.GetSubscriptionState" ISTR1="The request failed with HTTP status 503: Service Unavailable" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_WSUS_SYNC_MANAGER	12/12/2018 8:28:41 AM	8868 (0x22A4)
Sync failed. Will retry in 60 minutes	SMS_WSUS_SYNC_MANAGER	12/12/2018 8:28:41 AM	8868 (0x22A4)
Setting sync alert to active state on site UCP	SMS_WSUS_SYNC_MANAGER	12/12/2018 8:28:41 AM	8868 (0x22A4)
Sync time: 0d01h22m16s	SMS_WSUS_SYNC_MANAGER	12/12/2018 8:28:41 AM	8868 (0x22A4)
Skipping Delete Expired Update relations since this is not a scheduled sync.	SMS_WSUS_SYNC_MANAGER	12/12/2018 8:28:41 AM	8868 (0x22A4)
Inbox source is local on VRPSCCMPR01.ad.xxxxxx.xxxx.xxx	SMS_WSUS_SYNC_MANAGER	12/12/2018 8:28:44 AM	8868 (0x22A4)

I rebooted VRPSCCMSU01 still the same error...

Inbox source is local on VRPSCCMPR01.ad.xxxxxx.xxxx.xxx	SMS_WSUS_SYNC_MANAGER	12/12/2018 8:38:28 AM	8868 (0x22A4)
Wakeup by inbox drop	SMS_WSUS_SYNC_MANAGER	12/12/2018 8:58:32 AM	8868 (0x22A4)
Found local sync request file	SMS_WSUS_SYNC_MANAGER	12/12/2018 8:58:37 AM	8868 (0x22A4)
Starting Sync	SMS_WSUS_SYNC_MANAGER	12/12/2018 8:58:37 AM	8868 (0x22A4)
Performing sync on local request	SMS_WSUS_SYNC_MANAGER	12/12/2018 8:58:37 AM	8868 (0x22A4)
Read SUPs from SCF for VRPSCCMPR01.ad.xxxxxx.xxxx.xxx	SMS_WSUS_SYNC_MANAGER	12/12/2018 8:58:37 AM	8868 (0x22A4)
Found 1 SUPs	SMS_WSUS_SYNC_MANAGER	12/12/2018 8:58:37 AM	8868 (0x22A4)
Found active SUP VRPSCCMSU01.ad.xxxxxx.xxxx.xxx from SCF File.	SMS_WSUS_SYNC_MANAGER	12/12/2018 8:58:37 AM	8868 (0x22A4)
STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=VRPSCCMPR01.AD.xxxxxx.xxxx.xxx SITE=UCP PID=3384 TID=8868 GMTDATE=Wed Dec 12 16:58:37.234 2018 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_WSUS_SYNC_MANAGER	12/12/2018 8:58:37 AM	8868 (0x22A4)
Sync Surface Drivers option is not set	SMS_WSUS_SYNC_MANAGER	12/12/2018 8:58:38 AM	8868 (0x22A4)
Synchronizing WSUS server VRPSCCMSU01.ad.xxxxxx.xxxx.xxx	SMS_WSUS_SYNC_MANAGER	12/12/2018 8:58:38 AM	8868 (0x22A4)
STATMSG: ID=6704 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=VRPSCCMPR01.AD.xxxxxx.xxxx.xxx SITE=UCP PID=3384 TID=8868 GMTDATE=Wed Dec 12 16:58:38.241 2018 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_WSUS_SYNC_MANAGER	12/12/2018 8:58:38 AM	8868 (0x22A4)
https://VRPSCCMSU01.ad.xxxxxx.xxxx.xxx:8531	SMS_WSUS_SYNC_MANAGER	12/12/2018 8:58:38 AM	5596 (0x15DC)
Sync failed: The request failed with HTTP status 503: Service Unavailable. Source: Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer	SMS_WSUS_SYNC_MANAGER	12/12/2018 8:58:39 AM	8868 (0x22A4)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=VRPSCCMPR01.AD.xxxxxx.xxxx.xxx SITE=UCP PID=3384 TID=8868 GMTDATE=Wed Dec 12 16:58:39.247 2018 ISTR0="Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer" ISTR1="The request failed with HTTP status 503: Service Unavailable" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_WSUS_SYNC_MANAGER	12/12/2018 8:58:39 AM	8868 (0x22A4)
Sync failed. Will retry in 60 minutes	SMS_WSUS_SYNC_MANAGER	12/12/2018 8:58:39 AM	8868 (0x22A4)
Setting sync alert to active state on site UCP	SMS_WSUS_SYNC_MANAGER	12/12/2018 8:58:39 AM	8868 (0x22A4)
Sync time: 0d00h00m02s	SMS_WSUS_SYNC_MANAGER	12/12/2018 8:58:39 AM	8868 (0x22A4)
Skipping Delete Expired Update relations since this is not a scheduled sync.	SMS_WSUS_SYNC_MANAGER	12/12/2018 8:58:39 AM	8868 (0x22A4)
Inbox source is local on VRPSCCMPR01.ad.xxxxxx.xxxx.xxx	SMS_WSUS_SYNC_MANAGER	12/12/2018 8:58:40 AM	8868 (0x22A4)

Trying this:

https://blogs.technet.microsoft.com/configurationmgr/2015/03/23/configmgr-2012-support-tip-wsus-sync-fails-with-http-503-errors/

Still failing with 4Gb even 8Gb!!!

Now running with 16 GB

Inbox source is local on VRPSCCMPR01.ad.xxxxxx.xxxx.xxx	SMS_WSUS_SYNC_MANAGER	12/12/2018 9:51:16 AM	6500 (0x1964)
Wakeup by inbox drop	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:11:37 AM	6500 (0x1964)
Found local sync request file	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:11:42 AM	6500 (0x1964)
Starting Sync	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:11:42 AM	6500 (0x1964)
Performing sync on local request	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:11:42 AM	6500 (0x1964)
Read SUPs from SCF for VRPSCCMPR01.ad.xxxxxx.xxxx.xxx	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:11:42 AM	6500 (0x1964)
Found 1 SUPs	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:11:42 AM	6500 (0x1964)
Found active SUP VRPSCCMSU01.ad.xxxxxx.xxxx.xxx from SCF File.	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:11:42 AM	6500 (0x1964)
STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=VRPSCCMPR01.AD.xxxxxx.xxxx.xxx SITE=UCP PID=3032 TID=6500 GMTDATE=Wed Dec 12 18:11:42.253 2018 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:11:42 AM	6500 (0x1964)
Sync Surface Drivers option is not set	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:13:37 AM	6500 (0x1964)
Synchronizing WSUS server VRPSCCMSU01.ad.xxxxxx.xxxx.xxx	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:13:37 AM	6500 (0x1964)
STATMSG: ID=6704 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=VRPSCCMPR01.AD.xxxxxx.xxxx.xxx SITE=UCP PID=3032 TID=6500 GMTDATE=Wed Dec 12 18:13:37.844 2018 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:13:37 AM	6500 (0x1964)
https://VRPSCCMSU01.ad.xxxxxx.xxxx.xxx:8531	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:13:37 AM	5496 (0x1578)
Synchronizing WSUS server vrpsccmsu01.ad.xxxxxx.xxxx.xxx ...	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:13:38 AM	5496 (0x1578)
sync: Starting WSUS synchronization	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:13:38 AM	5496 (0x1578)
Waiting for WSUS server to finish another sync operation.	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:13:38 AM	5496 (0x1578)
Set content version of update source {67BB9074-421B-4166-A053-A8090F9523EF} for site UCP to 335	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:28:39 AM	6500 (0x1964)
Resetting MaxInstall RunTime for Cumulative updates.	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:28:39 AM	6500 (0x1964)
Synchronizing SMS database with WSUS server VRPSCCMSU01.ad.xxxxxx.xxxx.xxx	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:28:40 AM	6500 (0x1964)
STATMSG: ID=6705 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=VRPSCCMPR01.AD.xxxxxx.xxxx.xxx SITE=UCP PID=3032 TID=6500 GMTDATE=Wed Dec 12 18:28:40.836 2018 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:28:40 AM	6500 (0x1964)
https://VRPSCCMSU01.ad.xxxxxx.xxxx.xxx:8531	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:28:40 AM	7700 (0x1E14)
Synchronizing SMS database with WSUS server vrpsccmsu01.ad.xxxxxx.xxxx.xxx ...	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:28:43 AM	7700 (0x1E14)
sync: Starting SMS database synchronization	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:28:43 AM	7700 (0x1E14)
requested localization languages: en	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:28:43 AM	7700 (0x1E14)
Syncing all updates	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:28:44 AM	7700 (0x1E14)
Requested categories: Product=Windows 10 and later drivers, Product=Visual Studio 2015, Product=Office 2016, Product=Windows 8, Product=Office 365 Client, Product=Windows Server Drivers, Product=Windows 10 and later upgrade & servicing drivers, Product=Windows Server 2016 and Later Servicing Drivers, Product=Microsoft SQL Server 2012, Product=Windows Server 2016, Product=Windows 8.1, Product=Office 2019, Product=Office 2013, Product=Windows Server 2003, Datacenter Edition, Product=Office 2010, Product=Windows Defender, Product=Microsoft SQL Server 2016, Product=Windows Server 2012, Product=Windows 10, Product=Visual Studio 2012, Product=Windows Server 2008, Product=SQL Server 2008 R2, Product=Windows Server 2012 R2 Drivers, Product=Windows 7, Product=SQL Server 2008, Product=SQL Server Feature Pack, Product=Microsoft SQL Server 2017, Product=Microsoft SQL Server 2014, Product=Visual Studio 2013, Product=Windows 10 LTSB, Product=Windows Server 2012 R2, Product=Windows Server 2003, Product=Windows Server 2012 R2  and later drivers, Product=Windows Server 2019, Product=Report Viewer 2010, Product=Windows Server 2008 R2, ProductFamily=Skype for Business, ProductFamily=Silverlight, UpdateClassification=Security Updates, UpdateClassification=Update Rollups, UpdateClassification=Upgrades, UpdateClassification=Service Packs, UpdateClassification=Tools, UpdateClassification=Feature Packs, UpdateClassification=Updates, UpdateClassification=Definition Updates, UpdateClassification=Critical Updates	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:28:58 AM	7700 (0x1E14)
Third-party software updates is not enabled.	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:28:58 AM	7700 (0x1E14)
sync: SMS synchronizing categories	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:28:58 AM	7700 (0x1E14)
sync: SMS synchronizing categories, processed 0 out of 331 items (0%)	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:28:59 AM	7700 (0x1E14)
sync: SMS synchronizing categories, processed 331 out of 331 items (100%)	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:29:25 AM	7700 (0x1E14)
sync: SMS synchronizing categories, processed 331 out of 331 items (100%)	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:29:25 AM	7700 (0x1E14)
sync: SMS synchronizing updates	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:29:25 AM	7700 (0x1E14)
SyncBatchCount not set, using default 1	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:29:25 AM	7700 (0x1E14)
SyncBatchMinCreationDate not set, using default 01/01/2001 00:00:00	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:29:25 AM	7700 (0x1E14)
Collecting existing updates...	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:30:09 AM	7700 (0x1E14)
sync: SMS synchronizing updates, processed 0 out of 12265 items (0%)	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:30:09 AM	7700 (0x1E14)
Skipped update 862b36ee-9748-492e-bfd3-53f9d14c1956 - Flaw In Windows Media Player May Allow Media Library Access (819639) because it was superseded.	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:30:09 AM	7700 (0x1E14)
Skipped update 4beb6ee7-4b39-471a-9b2a-4a1212b3407a - Cumulative Patch for SQL Server 2000 Desktop Engine (Windows) because it was superseded.	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:30:09 AM	7700 (0x1E14)
Skipped update 3abbf4bd-9ced-4d98-b7c5-3654aae3d9ec - 823559: Security Update for Microsoft Windows because it was superseded.	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:30:09 AM	7700 (0x1E14)
Skipped update d07d1e4c-f4f7-4cc4-b5fd-4a99c196829f - MS03-026: Security Update for Windows Server 2003 (823980) because it was superseded.	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:30:09 AM	7700 (0x1E14)
Skipped update 78fedc95-792b-4600-977e-60de8feb3522 - Security Update for Microsoft Windows (KB824141) because it was superseded.	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:30:09 AM	7700 (0x1E14)
Skipped update 6a083d59-71bc-4942-a16f-58d0f44cbc4d - Security Update for Windows Server 2003 (KB823182) because it was superseded.	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:30:10 AM	7700 (0x1E14)
Skipped update 902adae3-e34b-4ef0-b7c8-d91020685901 - Security Update for Microsoft Windows (KB824105) because it was superseded.	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:30:10 AM	7700 (0x1E14)
Skipped update 574012e0-b292-4e5a-af35-d6a815003ab9 - Security Update for Microsoft Windows Server 2003 (KB825119) because it was superseded.	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:30:10 AM	7700 (0x1E14)
Skipped update 6dba0924-ac9f-4449-9672-405976297297 - Security Update for Microsoft Windows Server 2003 (KB828035) because it was superseded.	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:30:10 AM	7700 (0x1E14)
Synchronizing update aec3fee6-e956-41ff-b444-e3630eaee400 - Critical Update for Windows Small Business Server 2003 (KB832880)	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:30:10 AM	7700 (0x1E14)
Failed to sync update aec3fee6-e956-41ff-b444-e3630eaee400. Error: The underlying connection was closed: A connection that was expected to be kept alive was closed by the server. Source: Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:33:39 AM	7700 (0x1E14)
sync: SMS synchronizing updates, processed 10 out of 12265 items (0%), ETA in 3.14:07:31	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:33:39 AM	7700 (0x1E14)
Failed to sync update 8d1f6795-726f-4870-b246-7ad5ba9ac8c8. Error: The request failed with HTTP status 503: Service Unavailable. Source: Microsoft.UpdateServices.Internal.ApiRemoting.ExecuteSPGetUpdatesThatSupersedeUpdate	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:33:39 AM	7700 (0x1E14)
Failed to sync update fa2a089d-7ce8-41b6-992e-ae8aab363a61. Error: The request failed with HTTP status 503: Service Unavailable. Source: Microsoft.UpdateServices.Internal.ApiRemoting.ExecuteSPGetUpdatesThatSupersedeUpdate	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:33:39 AM	7700 (0x1E14)
Failed to sync update b2cf791b-250f-4559-8e26-c424c7cc8fba. Error: The request failed with HTTP status 503: Service Unavailable. Source: Microsoft.UpdateServices.Internal.ApiRemoting.ExecuteSPGetUpdatesThatSupersedeUpdate	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:33:39 AM	7700 (0x1E14)
Failed to sync update bc75ddbe-7bab-4255-999f-a36447dfe92f. Error: The request failed with HTTP status 503: Service Unavailable. Source: Microsoft.UpdateServices.Internal.ApiRemoting.ExecuteSPGetUpdatesThatSupersedeUpdate	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:33:40 AM	7700 (0x1E14)
Too many consecutive failures. Aborting sync.	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:33:40 AM	7700 (0x1E14)
Sync failures summary:	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:33:40 AM	7700 (0x1E14)
Failed to sync update fa2a089d-7ce8-41b6-992e-ae8aab363a61. Error: The request failed with HTTP status 503: Service Unavailable. Source: Microsoft.UpdateServices.Internal.ApiRemoting.ExecuteSPGetUpdatesThatSupersedeUpdate	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:33:40 AM	7700 (0x1E14)
Failed to sync update bc75ddbe-7bab-4255-999f-a36447dfe92f. Error: The request failed with HTTP status 503: Service Unavailable. Source: Microsoft.UpdateServices.Internal.ApiRemoting.ExecuteSPGetUpdatesThatSupersedeUpdate	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:33:40 AM	7700 (0x1E14)
Failed to sync update aec3fee6-e956-41ff-b444-e3630eaee400. Error: The underlying connection was closed: A connection that was expected to be kept alive was closed by the server. Source: Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:33:40 AM	7700 (0x1E14)
Failed to sync update b2cf791b-250f-4559-8e26-c424c7cc8fba. Error: The request failed with HTTP status 503: Service Unavailable. Source: Microsoft.UpdateServices.Internal.ApiRemoting.ExecuteSPGetUpdatesThatSupersedeUpdate	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:33:40 AM	7700 (0x1E14)
Failed to sync update 8d1f6795-726f-4870-b246-7ad5ba9ac8c8. Error: The request failed with HTTP status 503: Service Unavailable. Source: Microsoft.UpdateServices.Internal.ApiRemoting.ExecuteSPGetUpdatesThatSupersedeUpdate	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:33:40 AM	7700 (0x1E14)
Sync failed: Failed to sync some of the updates. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncUpdates	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:33:40 AM	6500 (0x1964)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=VRPSCCMPR01.AD.xxxxxx.xxxx.xxx SITE=UCP PID=3032 TID=6500 GMTDATE=Wed Dec 12 18:33:40.359 2018 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncUpdates" ISTR1="Failed to sync some of the updates" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:33:40 AM	6500 (0x1964)
Sync failed. Will retry in 60 minutes	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:33:40 AM	6500 (0x1964)
Setting sync alert to active state on site UCP	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:33:40 AM	6500 (0x1964)
Updated 1 items in SMS database, new update source content version is 336	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:33:40 AM	6500 (0x1964)
Sync time: 0d00h21m58s	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:33:40 AM	6500 (0x1964)
Skipping Delete Expired Update relations since this is not a scheduled sync.	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:33:40 AM	6500 (0x1964)
Inbox source is local on VRPSCCMPR01.ad.xxxxxx.xxxx.xxx	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:33:41 AM	6500 (0x1964)

it restarted but failed...

I noticed that the KB832880 was skipped previously...

Skipped update aec3fee6-e956-41ff-b444-e3630eaee400 - Critical Update for Windows Small Business Server 2003 (KB832880) because it is up to date.

and this time it is trying to synchronize it this is inconsistent...

Synchronizing update aec3fee6-e956-41ff-b444-e3630eaee400 - Critical Update for Windows Small Business Server 2003 (KB832880)	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:30:10 AM	7700 (0x1E14)

not sure what is going on!!!

Wakeup by inbox drop	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:44:38 AM	6500 (0x1964)
Found local sync request file	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:44:43 AM	6500 (0x1964)
Starting Sync	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:44:43 AM	6500 (0x1964)
Performing sync on local request	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:44:43 AM	6500 (0x1964)
Read SUPs from SCF for VRPSCCMPR01.ad.xxxxxx.xxxx.xxx	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:44:43 AM	6500 (0x1964)
Found 1 SUPs	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:44:43 AM	6500 (0x1964)
Found active SUP VRPSCCMSU01.ad.xxxxxx.xxxx.xxx from SCF File.	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:44:43 AM	6500 (0x1964)
STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=VRPSCCMPR01.AD.xxxxxx.xxxx.xxx SITE=UCP PID=3032 TID=6500 GMTDATE=Wed Dec 12 18:44:43.955 2018 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:44:43 AM	6500 (0x1964)
Sync Surface Drivers option is not set	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:44:44 AM	6500 (0x1964)
Synchronizing WSUS server VRPSCCMSU01.ad.xxxxxx.xxxx.xxx	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:44:44 AM	6500 (0x1964)
STATMSG: ID=6704 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=VRPSCCMPR01.AD.xxxxxx.xxxx.xxx SITE=UCP PID=3032 TID=6500 GMTDATE=Wed Dec 12 18:44:44.970 2018 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:44:44 AM	6500 (0x1964)
https://VRPSCCMSU01.ad.xxxxxx.xxxx.xxx:8531	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:44:44 AM	352 (0x0160)
Synchronizing WSUS server vrpsccmsu01.ad.xxxxxx.xxxx.xxx ...	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:45:07 AM	352 (0x0160)
sync: Starting WSUS synchronization	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:45:07 AM	352 (0x0160)
sync: WSUS synchronizing categories	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:45:17 AM	352 (0x0160)
sync: WSUS synchronizing updates	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:45:22 AM	352 (0x0160)
sync: WSUS synchronizing updates, processed 825 out of 40780 items (2%), ETA in 01:10:13	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:46:49 AM	352 (0x0160)
sync: WSUS synchronizing updates, processed 1099 out of 40780 items (2%), ETA in 01:28:27	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:47:49 AM	352 (0x0160)
sync: WSUS synchronizing updates, processed 1346 out of 40780 items (3%), ETA in 01:55:43	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:49:19 AM	352 (0x0160)
Sync failed: The operation has timed out. Source: Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:55:23 AM	6500 (0x1964)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=VRPSCCMPR01.AD.xxxxxx.xxxx.xxx SITE=UCP PID=3032 TID=6500 GMTDATE=Wed Dec 12 18:55:23.359 2018 ISTR0="Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse" ISTR1="The operation has timed out" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:55:23 AM	6500 (0x1964)
Sync failed. Will retry in 60 minutes	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:55:23 AM	6500 (0x1964)
Setting sync alert to active state on site UCP	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:55:23 AM	6500 (0x1964)
Sync time: 0d00h10m39s	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:55:23 AM	6500 (0x1964)
Skipping Delete Expired Update relations since this is not a scheduled sync.	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:55:23 AM	6500 (0x1964)
Inbox source is local on VRPSCCMPR01.ad.xxxxxx.xxxx.xxx	SMS_WSUS_SYNC_MANAGER	12/12/2018 10:55:26 AM	6500 (0x1964)

Next Sync another error time out!!

It seems the CPU of the SU01 server is overloaded!!!

Thanks,

Dom

Security / System Center Configuration Manager Current Branch / SQL

Edited by Felyjos Thursday, December 13, 2018 12:51 AM

Wednesday, December 12, 2018 4:37 PM

0

Sign in to vote

Hello,

I am looping now...

Reboot SU01 (Software Update Point Server/WSUS/SCUP)

Start the Application Pool when needed

Start the synchronization on PR01 (Primary Server - SCCM Console)

Then after hours 1, 2, or 4 hours it failed...

etc ...

Thanks,

Dom

Security / System Center Configuration Manager Current Branch / SQL

Thursday, December 13, 2018 3:16 AM

1

Sign in to vote

I'm confident that WSUS Automated Maintenance (WAM) © would fix this, and I've been quiet for a while, but you guys have one heck of a long thread and it seems like you're getting frustrated and I just want to help. By all means keep going at it if you'd like - I just hate seeing people not getting results. Full disclosure - WAM is my product.

Adam Marshall, MCSE: Security
https://www.ajtek.ca
Microsoft MVP - Windows and Devices for IT

Thursday, December 13, 2018 4:52 AM

0

Sign in to vote

Hello,

Some progress overnight ….

After several failures during the cleanup and the synchronization went through after 14 days !!!

WSYNCMGR.log
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Synchronizing update a122b315-4bd3-446b-b62c-5d388f6fb38f - Windows SharePoint Services 2.0 Service Pack 3 (KB923643)						SMS_WSUS_SYNC_MANAGER	12/12/2018 4:00:12 PM	9376 (0x24A0)
Failed to sync update a122b315-4bd3-446b-b62c-5d388f6fb38f. Error: The underlying connection was closed: A connection that was expected to be kept alive was 
closed by the server. Source: Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse					SMS_WSUS_SYNC_MANAGER	12/12/2018 4:12:22 PM	9376 (0x24A0)
sync: SMS synchronizing updates, processed 494 out of 15069 items (3%), ETA in 4.20:02:27									SMS_WSUS_SYNC_MANAGER	12/12/2018 4:12:22 PM	9376 (0x24A0)
Failed to sync update bcc9517e-1767-409d-8612-869903beed9d. Error: The request failed with HTTP status 503: 
Service Unavailable. Source: Microsoft.UpdateServices.Internal.ApiRemoting.ExecuteSPGetParentUpdateClassification									SMS_WSUS_SYNC_MANAGER	12/12/2018 4:12:23 PM	9376 (0x24A0)
Failed to sync update f7fb7d58-712a-403e-b541-5fe8ab34e5ed. Error: The request failed with HTTP status 503: 				
Service Unavailable. Source: Microsoft.UpdateServices.Internal.ApiRemoting.ExecuteSPGetParentUpdateClassification						SMS_WSUS_SYNC_MANAGER	12/12/2018 4:12:23 PM	9376 (0x24A0)
Failed to sync update 9779b252-3437-4784-9ba1-eef8872fd672. Error: The request failed with HTTP status 503: 
Service Unavailable. Source: Microsoft.UpdateServices.Internal.ApiRemoting.ExecuteSPGetUpdatesThatSupersedeUpdate						SMS_WSUS_SYNC_MANAGER	12/12/2018 4:12:23 PM	9376 (0x24A0)
Failed to sync update 5bda2c87-0ab0-49ba-bc0f-a1f62b979878. Error: The request failed with HTTP status 503: 
Service Unavailable. Source: Microsoft.UpdateServices.Internal.ApiRemoting.ExecuteSPGetParentUpdateClassification						SMS_WSUS_SYNC_MANAGER	12/12/2018 4:12:23 PM	9376 (0x24A0)
Too many consecutive failures. Aborting sync.															SMS_WSUS_SYNC_MANAGER	12/12/2018 4:12:23 PM	9376 (0x24A0)
Sync failures summary:																		SMS_WSUS_SYNC_MANAGER	12/12/2018 4:12:23 PM	9376 (0x24A0)
Failed to sync update bcc9517e-1767-409d-8612-869903beed9d. Error: The request failed with HTTP status 503: 
Service Unavailable. Source: Microsoft.UpdateServices.Internal.ApiRemoting.ExecuteSPGetParentUpdateClassification						SMS_WSUS_SYNC_MANAGER	12/12/2018 4:12:23 PM	9376 (0x24A0)
Failed to sync update 9779b252-3437-4784-9ba1-eef8872fd672. Error: The request failed with HTTP status 503: 
Service Unavailable. Source: Microsoft.UpdateServices.Internal.ApiRemoting.ExecuteSPGetUpdatesThatSupersedeUpdate						SMS_WSUS_SYNC_MANAGER	12/12/2018 4:12:23 PM	9376 (0x24A0)
Failed to sync update 5bda2c87-0ab0-49ba-bc0f-a1f62b979878. Error: The request failed with HTTP status 503: 
Service Unavailable. Source: Microsoft.UpdateServices.Internal.ApiRemoting.ExecuteSPGetParentUpdateClassification						SMS_WSUS_SYNC_MANAGER	12/12/2018 4:12:23 PM	9376 (0x24A0)
Failed to sync update a122b315-4bd3-446b-b62c-5d388f6fb38f. Error: The underlying connection was closed: A connection that was expected to be kept alive was 
closed by the server. Source: Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse					SMS_WSUS_SYNC_MANAGER	12/12/2018 4:12:23 PM	9376 (0x24A0)
Failed to sync update f7fb7d58-712a-403e-b541-5fe8ab34e5ed. Error: The request failed with HTTP status 503: 
Service Unavailable. Source: Microsoft.UpdateServices.Internal.ApiRemoting.ExecuteSPGetParentUpdateClassification						SMS_WSUS_SYNC_MANAGER	12/12/2018 4:12:23 PM	9376 (0x24A0)
Sync failed: Failed to sync some of the updates. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncUpdates	SMS_WSUS_SYNC_MANAGER	12/12/2018 4:12:23 PM	6196 (0x1834)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=VRPSCCMPR01.ad.xxxxxx.xxxx.xxx SITE=UCP PID=2484 TID=6196 
GMTDATE=Thu Dec 13 00:12:23.152 2018 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncUpdates" 
ISTR1="Failed to sync some of the updates" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0					SMS_WSUS_SYNC_MANAGER	12/12/2018 4:12:23 PM	6196 (0x1834)
Sync failed. Will retry in 60 minutes																SMS_WSUS_SYNC_MANAGER	12/12/2018 4:12:23 PM	6196 (0x1834)
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Sync failed: WSUS server not configured. Please refer to WCM.log for configuration error details.. Source: CWSyncMgr::DoSync					SMS_WSUS_SYNC_MANAGER	12/12/2018 11:26:58 PM	5380 (0x1504)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=VRPSCCMPR01.ad.xxxxxx.xxxx.xxx SITE=UCP 
PID=8272 TID=5380 GMTDATE=Thu Dec 13 07:26:58.115 2018 ISTR0="CWSyncMgr::DoSync" ISTR1="WSUS server not configured. 
Please refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" 
ISTR9="" NUMATTRS=0																		SMS_WSUS_SYNC_MANAGER	12/12/2018 11:26:58 PM	5380 (0x1504)
Sync failed. Will retry in 60 minutes																SMS_WSUS_SYNC_MANAGER	12/12/2018 11:26:58 PM	5380 (0x1504)
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
==============================================================================================================================================================================================================
Synchronizing update 68dca8d0-dee0-4b72-b5c5-bd0d08c9c8dc - Security Update for Windows Server 2003 x64 Edition (KB2929961)					SMS_WSUS_SYNC_MANAGER	12/13/2018 2:06:11 AM	9056 (0x2360)
Failed to sync update 68dca8d0-dee0-4b72-b5c5-bd0d08c9c8dc. Error: Thread was being aborted. 
Source: Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse								SMS_WSUS_SYNC_MANAGER	12/13/2018 2:06:15 AM	9056 (0x2360)
Sync failed: Thread was being aborted. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncUpdates		SMS_WSUS_SYNC_MANAGER	12/13/2018 2:06:15 AM	5380 (0x1504)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=VRPSCCMPR01.ad.xxxxxx.xxxx.xxx SITE=UCP PID=8272 TID=5380 
GMTDATE=Thu Dec 13 10:06:15.275 2018 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncUpdates" 
ISTR1="Thread was being aborted" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0						SMS_WSUS_SYNC_MANAGER	12/13/2018 2:06:15 AM	5380 (0x1504)
Sync failed. Will retry in 60 minutes																SMS_WSUS_SYNC_MANAGER	12/13/2018 2:06:15 AM	5380 (0x1504)
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
==============================================================================================================================================================================================================
Sync failed: UssInternalError: SoapException: Fault occurred~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, 
WebResponse response, Stream responseStream, Boolean asyncCall). 
Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS								SMS_WSUS_SYNC_MANAGER	12/13/2018 3:07:38 AM	12984 (0x32B8)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=VRPSCCMPR01.ad.xxxxxx.xxxx.xxx SITE=UCP PID=8312 TID=12984 
GMTDATE=Thu Dec 13 11:07:38.400 2018 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS" 
ISTR1="UssInternalError: SoapException: Fault occurred~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, 
WebResponse response, Stream responseStream, Boolean asyncCall)" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0		SMS_WSUS_SYNC_MANAGER	12/13/2018 3:07:38 AM	12984 (0x32B8)
Sync failed. Will retry in 60 minutes																SMS_WSUS_SYNC_MANAGER	12/13/2018 3:07:38 AM	12984 (0x32B8)
	5380 (0x1504)
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
==============================================================================================================================================================================================================

Wakeup for a polling cycle																	SMS_WSUS_SYNC_MANAGER	12/13/2018 4:07:38 AM	12984 (0x32B8)
Starting Sync																			SMS_WSUS_SYNC_MANAGER	12/13/2018 4:07:38 AM	12984 (0x32B8)
Performing sync on retry schedule																SMS_WSUS_SYNC_MANAGER	12/13/2018 4:07:38 AM	12984 (0x32B8)
Full sync required due to changes in main WSUS server location.													SMS_WSUS_SYNC_MANAGER	12/13/2018 4:07:38 AM	12984 (0x32B8)
Read SUPs from SCF for VRPSCCMPR01.ad.xxxxxx.xxxx.xxx														SMS_WSUS_SYNC_MANAGER	12/13/2018 4:07:38 AM	12984 (0x32B8)
Found 1 SUPs																			SMS_WSUS_SYNC_MANAGER	12/13/2018 4:07:38 AM	12984 (0x32B8)
Found active SUP VRPSCCMSU01.ad.xxxxxx.xxxx.xxx from SCF File.													SMS_WSUS_SYNC_MANAGER	12/13/2018 4:07:38 AM	12984 (0x32B8)
STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=VRPSCCMPR01.ad.xxxxxx.xxxx.xxx SITE=UCP PID=8312 TID=12984 
GMTDATE=Thu Dec 13 12:07:38.122 2018 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0			SMS_WSUS_SYNC_MANAGER	12/13/2018 4:07:38 AM	12984 (0x32B8)
Sync Surface Drivers option is not set																SMS_WSUS_SYNC_MANAGER	12/13/2018 4:07:39 AM	12984 (0x32B8)
Synchronizing WSUS server VRPSCCMSU01.ad.xxxxxx.xxxx.xxx													SMS_WSUS_SYNC_MANAGER	12/13/2018 4:07:39 AM	12984 (0x32B8)
STATMSG: ID=6704 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=VRPSCCMPR01.ad.xxxxxx.xxxx.xxx SITE=UCP PID=8312 TID=12984 
GMTDATE=Thu Dec 13 12:07:39.263 2018 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0			SMS_WSUS_SYNC_MANAGER	12/13/2018 4:07:39 AM	12984 (0x32B8)
https://VRPSCCMSU01.ad.xxxxxx.xxxx.xxx:8531															SMS_WSUS_SYNC_MANAGER	12/13/2018 4:07:39 AM	9940 (0x26D4)
Synchronizing WSUS server vrpsccmsu01.ad.xxxxxx.xxxx.xxx ...													SMS_WSUS_SYNC_MANAGER	12/13/2018 4:07:39 AM	9940 (0x26D4)
sync: Starting WSUS synchronization																SMS_WSUS_SYNC_MANAGER	12/13/2018 4:07:39 AM	9940 (0x26D4)
sync: WSUS synchronizing categories																SMS_WSUS_SYNC_MANAGER	12/13/2018 4:07:45 AM	9940 (0x26D4)
sync: WSUS synchronizing updates																SMS_WSUS_SYNC_MANAGER	12/13/2018 4:07:47 AM	9940 (0x26D4)
sync: WSUS synchronizing updates, processed 208 out of 208 items (100%)												SMS_WSUS_SYNC_MANAGER	12/13/2018 4:08:01 AM	9940 (0x26D4)
Done synchronizing WSUS Server vrpsccmsu01.ad.xxxxxx.xxxx.xxx													SMS_WSUS_SYNC_MANAGER	12/13/2018 4:08:01 AM	9940 (0x26D4)
Sync Catalog Drivers SCF value is set to : 0															SMS_WSUS_SYNC_MANAGER	12/13/2018 4:08:01 AM	9940 (0x26D4)
SyncGracePeriod not set, use default 120000															SMS_WSUS_SYNC_MANAGER	12/13/2018 4:08:01 AM	9940 (0x26D4)
Sleeping 120 more seconds for WSUS server sync results to become available											SMS_WSUS_SYNC_MANAGER	12/13/2018 4:08:01 AM	9940 (0x26D4)
Set content version of update source {67BB9074-421B-4166-A053-A8090F9523EF} for site UCP to 337									SMS_WSUS_SYNC_MANAGER	12/13/2018 4:10:02 AM	12984 (0x32B8)
Resetting MaxInstall RunTime for Cumulative updates.														SMS_WSUS_SYNC_MANAGER	12/13/2018 4:10:02 AM	12984 (0x32B8)
Synchronizing SMS database with WSUS server VRPSCCMSU01.ad.xxxxxx.xxxx.xxx											SMS_WSUS_SYNC_MANAGER	12/13/2018 4:10:05 AM	12984 (0x32B8)
STATMSG: ID=6705 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=VRPSCCMPR01.ad.xxxxxx.xxxx.xxx SITE=UCP PID=8312 TID=12984 
GMTDATE=Thu Dec 13 12:10:05.199 2018 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0			SMS_WSUS_SYNC_MANAGER	12/13/2018 4:10:05 AM	12984 (0x32B8)
https://VRPSCCMSU01.ad.xxxxxx.xxxx.xxx:8531															SMS_WSUS_SYNC_MANAGER	12/13/2018 4:10:05 AM	11384 (0x2C78)
Synchronizing SMS database with WSUS server vrpsccmsu01.ad.xxxxxx.xxxx.xxx ...											SMS_WSUS_SYNC_MANAGER	12/13/2018 4:10:05 AM	11384 (0x2C78)
sync: Starting SMS database synchronization															SMS_WSUS_SYNC_MANAGER	12/13/2018 4:10:05 AM	11384 (0x2C78)
requested localization languages: en																SMS_WSUS_SYNC_MANAGER	12/13/2018 4:10:05 AM	11384 (0x2C78)
Syncing all updates																		SMS_WSUS_SYNC_MANAGER	12/13/2018 4:10:05 AM	11384 (0x2C78)
Requested categories: Product=Windows 10 and later drivers, Product=Visual Studio 2015, Product=Office 2016, Product=Windows 8, Product=Office 365 Client, 
Product=Windows Server Drivers, Product=Windows 10 and later upgrade & servicing drivers, Product=Windows Server 2016 and Later Servicing Drivers, 
Product=Microsoft SQL Server 2012, Product=Windows Server 2016, Product=Windows 8.1, Product=Office 2019, Product=Office 2013, Product=Windows Server 2003, 
Datacenter Edition, Product=Office 2010, Product=Windows Defender, Product=Microsoft SQL Server 2016, Product=Windows Server 2012, Product=Windows 10, 
Product=Visual Studio 2012, Product=Windows Server 2008, Product=SQL Server 2008 R2, Product=Windows Server 2012 R2 Drivers, Product=Windows 7, 
Product=SQL Server 2008, Product=SQL Server Feature Pack, Product=Microsoft SQL Server 2017, Product=Microsoft SQL Server 2014, Product=Visual Studio 2013, 
Product=Windows 10 LTSB, Product=Windows Server 2012 R2, Product=Windows Server 2003, Product=Windows Server 2012 R2  and later drivers, 
Product=Windows Server 2019, Product=Report Viewer 2010, Product=Windows Server 2008 R2, ProductFamily=Skype for Business, ProductFamily=Silverlight, 
UpdateClassification=Security Updates, UpdateClassification=Update Rollups, UpdateClassification=Upgrades, UpdateClassification=Service Packs, 
UpdateClassification=Tools, UpdateClassification=Feature Packs, UpdateClassification=Updates, UpdateClassification=Definition Updates, 
UpdateClassification=Critical Updates																SMS_WSUS_SYNC_MANAGER	12/13/2018 4:10:08 AM	11384 (0x2C78)
Third-party software updates is not enabled.															SMS_WSUS_SYNC_MANAGER	12/13/2018 4:10:08 AM	11384 (0x2C78)
sync: SMS synchronizing categories																SMS_WSUS_SYNC_MANAGER	12/13/2018 4:10:08 AM	11384 (0x2C78)
sync: SMS synchronizing categories, processed 0 out of 331 items (0%)												SMS_WSUS_SYNC_MANAGER	12/13/2018 4:10:08 AM	11384 (0x2C78)
sync: SMS synchronizing categories, processed 114 out of 331 items (34%), ETA in 00:01:54									SMS_WSUS_SYNC_MANAGER	12/13/2018 4:11:09 AM	11384 (0x2C78)
sync: SMS synchronizing categories, processed 181 out of 331 items (54%), ETA in 00:01:41									SMS_WSUS_SYNC_MANAGER	12/13/2018 4:12:10 AM	11384 (0x2C78)
sync: SMS synchronizing categories, processed 208 out of 331 items (62%), ETA in 00:01:56									SMS_WSUS_SYNC_MANAGER	12/13/2018 4:13:25 AM	11384 (0x2C78)
sync: SMS synchronizing categories, processed 242 out of 331 items (73%), ETA in 00:01:34									SMS_WSUS_SYNC_MANAGER	12/13/2018 4:14:25 AM	11384 (0x2C78)
sync: SMS synchronizing categories, processed 331 out of 331 items (100%)											SMS_WSUS_SYNC_MANAGER	12/13/2018 4:14:53 AM	11384 (0x2C78)
sync: SMS synchronizing categories, processed 331 out of 331 items (100%)											SMS_WSUS_SYNC_MANAGER	12/13/2018 4:14:53 AM	11384 (0x2C78)
sync: SMS synchronizing updates																	SMS_WSUS_SYNC_MANAGER	12/13/2018 4:14:53 AM	11384 (0x2C78)
SyncBatchCount not set, using default 1																SMS_WSUS_SYNC_MANAGER	12/13/2018 4:14:53 AM	11384 (0x2C78)
SyncBatchMinCreationDate not set, using default 01/01/2001 00:00:00												SMS_WSUS_SYNC_MANAGER	12/13/2018 4:14:53 AM	11384 (0x2C78)
Collecting existing updates...																	SMS_WSUS_SYNC_MANAGER	12/13/2018 4:16:01 AM	11384 (0x2C78)
sync: SMS synchronizing updates, processed 0 out of 12604 items (0%)												SMS_WSUS_SYNC_MANAGER	12/13/2018 4:16:02 AM	11384 (0x2C78)
Skipped update 862b36ee-9748-492e-bfd3-53f9d14c1956 - Flaw In Windows Media Player May Allow Media Library Access (819639) because it was superseded.		SMS_WSUS_SYNC_MANAGER	12/13/2018 4:16:02 AM	11384 (0x2C78)
Skipped update 4beb6ee7-4b39-471a-9b2a-4a1212b3407a - Cumulative Patch for SQL Server 2000 Desktop Engine (Windows) because it was superseded.			SMS_WSUS_SYNC_MANAGER	12/13/2018 4:16:02 AM	11384 (0x2C78)

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
..............................................................................................................................................................................................................

Synchronizing update de4a9921-1be8-4f85-a12a-9cb72e2c7f4d - Office 365 Client Update - 
Monthly Channel (Targeted) Version 1812 for x64 based Edition (Build 11126.20074)										SMS_WSUS_SYNC_MANAGER	12/13/2018 7:27:27 AM	11384 (0x2C78)
sync: SMS synchronizing updates, processed 12598 out of 12604 items (99%), ETA in 00:00:05									SMS_WSUS_SYNC_MANAGER	12/13/2018 7:27:41 AM	11384 (0x2C78)
Synchronizing update 33bbd380-28f3-43ae-a2e4-a1c81b608489 - Office 365 Client Update - 
Monthly Channel (Targeted) Version 1812 for x86 based Edition (Build 11126.20074)										SMS_WSUS_SYNC_MANAGER	12/13/2018 7:27:41 AM	11384 (0x2C78)
Synchronizing update 9fdf1c7d-5c0c-46f3-9f4e-63eb359ffe58 - SQL Server 2014 Service Pack 2 Cumulative Update (CU) 15 KB4469137					SMS_WSUS_SYNC_MANAGER	12/13/2018 7:27:59 AM	11384 (0x2C78)
Synchronizing update 6ca6ed6a-d6fe-44b8-9caf-8ca8848c365b - Definition Update for Windows Defender Antivirus - KB915597 (Definition 1.283.465.0)		SMS_WSUS_SYNC_MANAGER	12/13/2018 7:28:02 AM	11384 (0x2C78)
Synchronizing update bb647886-f707-478f-b837-65b3e82bc11c - Definition Update for Windows Defender Antivirus - KB2267602 (Definition 1.283.483.0)		SMS_WSUS_SYNC_MANAGER	12/13/2018 7:28:15 AM	11384 (0x2C78)
sync: SMS synchronizing updates, processed 12602 out of 12604 items (99%), ETA in 00:00:01									SMS_WSUS_SYNC_MANAGER	12/13/2018 7:29:51 AM	11384 (0x2C78)
Synchronizing update 0c1bcd3d-a11d-46d0-9880-9f28845c3a2e - Definition Update for Windows Defender Antivirus - KB2267602 (Definition 1.283.488.0)		SMS_WSUS_SYNC_MANAGER	12/13/2018 7:29:51 AM	11384 (0x2C78)
sync: SMS synchronizing updates, processed 12603 out of 12604 items (99%), ETA in 00:00:00									SMS_WSUS_SYNC_MANAGER	12/13/2018 7:31:04 AM	11384 (0x2C78)
Synchronizing update 8df9ccad-5b0b-4913-91c8-533b16197551 - Definition Update for Windows Defender Antivirus - KB2267602 (Definition 1.283.495.0)		SMS_WSUS_SYNC_MANAGER	12/13/2018 7:31:04 AM	11384 (0x2C78)
sync: SMS synchronizing updates, processed 12604 out of 12604 items (100%)											SMS_WSUS_SYNC_MANAGER	12/13/2018 7:32:08 AM	11384 (0x2C78)
sync: SMS performing cleanup																	SMS_WSUS_SYNC_MANAGER	12/13/2018 7:32:08 AM	11384 (0x2C78)
Removed 62 unreferenced updates																	SMS_WSUS_SYNC_MANAGER	12/13/2018 7:32:09 AM	11384 (0x2C78)
Done synchronizing SMS with WSUS Server vrpsccmsu01.ad.xxxxxx.xxxx.xxx												SMS_WSUS_SYNC_MANAGER	12/13/2018 7:32:09 AM	11384 (0x2C78)
Set content version of update source {67BB9074-421B-4166-A053-A8090F9523EF} for site UCP to 340									SMS_WSUS_SYNC_MANAGER	12/13/2018 7:32:09 AM	12984 (0x32B8)
Resetting MaxInstall RunTime for Cumulative updates.														SMS_WSUS_SYNC_MANAGER	12/13/2018 7:32:09 AM	12984 (0x32B8)
Starting cleanup on WSUS server VRPSCCMSU01.ad.xxxxxx.xxxx.xxx													SMS_WSUS_SYNC_MANAGER	12/13/2018 7:32:14 AM	12984 (0x32B8)
https://VRPSCCMSU01.ad.xxxxxx.xxxx.xxx:8531															SMS_WSUS_SYNC_MANAGER	12/13/2018 7:32:14 AM	47996 (0xBB7C)
Cleaning up WSUS server vrpsccmsu01.ad.xxxxxx.xxxx.xxx ...													SMS_WSUS_SYNC_MANAGER	12/13/2018 7:32:14 AM	47996 (0xBB7C)
sync: Starting SMS database synchronization															SMS_WSUS_SYNC_MANAGER	12/13/2018 7:32:14 AM	47996 (0xBB7C)
requested localization languages: en																SMS_WSUS_SYNC_MANAGER	12/13/2018 7:32:14 AM	47996 (0xBB7C)
Syncing updates arrived after 12/13/2018 04:10:05														SMS_WSUS_SYNC_MANAGER	12/13/2018 7:32:14 AM	47996 (0xBB7C)
Requested categories: Product=Windows 10 and later drivers, Product=Visual Studio 2015, Product=Office 2016, Product=Windows 8, Product=Office 365 Client, 
Product=Windows Server Drivers, Product=Windows 10 and later upgrade & servicing drivers, Product=Windows Server 2016 and Later Servicing Drivers, 
Product=Microsoft SQL Server 2012, Product=Windows Server 2016, Product=Windows 8.1, Product=Office 2019, Product=Office 2013, Product=Windows Server 2003, 
Datacenter Edition, Product=Office 2010, Product=Windows Defender, Product=Microsoft SQL Server 2016, Product=Windows Server 2012, Product=Windows 10, 
Product=Visual Studio 2012, Product=Windows Server 2008, Product=SQL Server 2008 R2, Product=Windows Server 2012 R2 Drivers, Product=Windows 7, 
Product=SQL Server 2008, Product=SQL Server Feature Pack, Product=Microsoft SQL Server 2017, Product=Microsoft SQL Server 2014, Product=Visual Studio 2013, 
Product=Windows 10 LTSB, Product=Windows Server 2012 R2, Product=Windows Server 2003, Product=Windows Server 2012 R2  and later drivers, 
Product=Windows Server 2019, Product=Report Viewer 2010, Product=Windows Server 2008 R2, ProductFamily=Skype for Business, ProductFamily=Silverlight, 
UpdateClassification=Security Updates, UpdateClassification=Update Rollups, UpdateClassification=Upgrades, UpdateClassification=Service Packs, 
UpdateClassification=Tools, UpdateClassification=Feature Packs, UpdateClassification=Updates, UpdateClassification=Definition Updates, 
UpdateClassification=Critical Updates																SMS_WSUS_SYNC_MANAGER	12/13/2018 7:32:14 AM	47996 (0xBB7C)
sync: SMS performing cleanup																	SMS_WSUS_SYNC_MANAGER	12/13/2018 7:32:14 AM	47996 (0xBB7C)
... (104 times)
sync: SMS performing cleanup SMS_WSUS_SYNC_MANAGER 12/13/2018 9:53:54 AM 47996 (0xBB7C)
Failed to check cleanup needed on update c22881b7-80f7-4acf-83f2-c2af7cabeee0. Error: The underlying connection was closed: A connection that was expected to be kept alive was closed by the server. Source: Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse SMS_WSUS_SYNC_MANAGER 12/13/2018 9:56:01 AM 47996 (0xBB7C)
sync: SMS performing cleanup SMS_WSUS_SYNC_MANAGER 12/13/2018 9:56:01 AM 47996 (0xBB7C)

still waiting the SMS Performing cleanup !!! over 104 times and 2 hours 26 mn!!! and an error...

Failed to check cleanup needed on update c22881b7-80f7-4acf-83f2-c2af7cabeee0. Error: The underlying

still in progress... it seems to continue...

sync: SMS performing cleanup	SMS_WSUS_SYNC_MANAGER	12/13/2018 9:53:54 AM	47996 (0xBB7C)
Failed to check cleanup needed on update c22881b7-80f7-4acf-83f2-c2af7cabeee0. Error: The underlying connection was closed: A connection that was expected to be kept alive was closed by the server. Source: Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse	SMS_WSUS_SYNC_MANAGER	12/13/2018 9:56:01 AM	47996 (0xBB7C)
sync: SMS performing cleanup	SMS_WSUS_SYNC_MANAGER	12/13/2018 9:56:01 AM	47996 (0xBB7C)
sync: SMS performing cleanup	SMS_WSUS_SYNC_MANAGER	12/13/2018 9:58:43 AM	47996 (0xBB7C)
sync: SMS performing cleanup	SMS_WSUS_SYNC_MANAGER	12/13/2018 10:01:49 AM	47996 (0xBB7C)

... (138 times) by 12/13/2018 10:45 AM

So finally after 235 times

sync: SMS performing cleanup	SMS_WSUS_SYNC_MANAGER	12/13/2018 12:25	47996 (0xBB7C)
sync: SMS performing cleanup	SMS_WSUS_SYNC_MANAGER	12/13/2018 12:26	47996 (0xBB7C)
Cleanup processed 14090 total updates and declined 6645	SMS_WSUS_SYNC_MANAGER	12/13/2018 12:27	47996 (0xBB7C)
Done cleaning up WSUS Server vrpsccmsu01.ad.xxxxxx.xxxx.xxx	SMS_WSUS_SYNC_MANAGER	12/13/2018 12:27	47996 (0xBB7C)
Set content version of update source {67BB9074-421B-4166-A053-A8090F9523EF} for site UCP to 340	SMS_WSUS_SYNC_MANAGER	12/13/2018 12:27	12984 (0x32B8)
Resetting MaxInstall RunTime for Cumulative updates.	SMS_WSUS_SYNC_MANAGER	12/13/2018 12:27	12984 (0x32B8)
STATMSG: ID=6702 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=VRPSCCMPR01.ad.xxxxxx.xxxx.xxx SITE=UCP PID=8312 TID=12984 GMTDATE=Thu Dec 13 20:27:12.066 2018 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_WSUS_SYNC_MANAGER	12/13/2018 12:27	12984 (0x32B8)
Sync succeeded. Setting sync alert to canceled state on site UCP	SMS_WSUS_SYNC_MANAGER	12/13/2018 12:27	12984 (0x32B8)
Updated 18859 items in SMS database, new update source content version is 340	SMS_WSUS_SYNC_MANAGER	12/13/2018 12:27	12984 (0x32B8)
Sync time: 0d08h19m34s	SMS_WSUS_SYNC_MANAGER	12/13/2018 12:27	12984 (0x32B8)
Skipping Delete Expired Update relations since this is not a scheduled sync.	SMS_WSUS_SYNC_MANAGER	12/13/2018 12:27	12984 (0x32B8)
Inbox source is local on VRPSCCMPR01.ad.xxxxxx.xxxx.xxx	SMS_WSUS_SYNC_MANAGER	12/13/2018 12:27	12984 (0x32B8)

Thanks,
Dom

Security / System Center Configuration Manager Current Branch / SQL

Edited by Felyjos Thursday, December 13, 2018 8:54 PM

Thursday, December 13, 2018 5:34 PM

Products

Resources

Solutions

Updates

Trials

Related Sites

Training

Certifications

Other resources

Support options

More support

Not an IT pro?

Answered by:

WSUS Cleanup

Question

Answers

All replies

Service Unavailable