Cannot insert more than 1 WSUS update source with different unique ids WUAHandler

1      Cannot insert more than 1 WSUS update source with different unique ids  WUAHandler

Problem Statement:

Most of the times the reason for this behavior is: a previous installation or reinstallation of the site server, which left stale record or for some reason, the hierarchy between the site server has changed (uninstallation - new installation, attaching a site server to a different site), etc..

Symptoms:

WUAUHANDLER.log

Cannot insert more than 1 WSUS update source with different unique ids  WUAHandler

Failed to Add Update Source for WUAgent of type (2) and id ({##-##-##-####}). Error = 0x80040694.        WUAHandler

Its a WSUS Update Source type ({##-##-##-####}), adding it.  WUAHandler

Applies to: SCCM 2007

Troubleshooting Steps:

1.        According to the above log lines, there was a duplicate WSUS registration in the site’s database. TheCI_UpdateSources table in the site’s database, probably contains aged data – a stale record.In order to disable the inactive entry, we need to execute the following steps against the site database:

2.         select * from CI_UpdateSources

3.        The above query should ideally return 1 result. If you get two results, then you have an additional entry of the update source from a previous installation. 
Both the entries may have the IsTombstoned value = 0 which is not correct. 
You need to find the active id by: either comparing the DateCreated and Modified values in the table or the UpdateSource_UniqueID, which should be the same as the one that the client is trying to run the scan against, that we see in the log:

4.         Failed to Add Update Source for WUAgent of type (#) and id ({##-##-##-####}). Error =0x80040694.  WUAHandler        

5.          To disable the inactive entry, we need to run the following command :

6.          update CI_UpdateSources set IsTombstoned = 1 where UpdateSource_ID = '#'

7.         Run  select * from CI_UpdateSources again which results only one entry now

8.        SUP role alone should be uninstalled and install in-order to update wsus registration in SCCM database.

Root Cause Analysis:

According to the above log lines, there was a duplicate WSUS registration in the site’s database. TheCI_UpdateSources table in the site’s database probably contains aged data – a stale record. This needs to be removed manually.