I am aware that are a whole bunch of forum threads on this error however little bit of additional help would be of great help, as I have nearly tracked this 'pain' down.
Our environment: SCCM 2007 R3
1 Central
15 Primaries and a whole bunch of secondaries
Single WSUS server
OK, so we have just taken handover of this new account and still getting a hang of the creek and corners in the environment. We have about 1000 machines sitting in "Failed to download updates" state. Error = 0x80040694
WUAHandler.log:
Its a WSUS Update Source type ({A2762CA9-9739-4260-9C3A-DC4B36122E16}), adding it
Cannot insert more than 1 WSUS update source with different unique ids
Failed to Add Update Source for WUAgent of type (2) and id ({A2762CA9-9739-4260-9C3A-DC4B36122E16}). Error = 0x80040694.
Its a WSUS Update Source type ({BCB9D60B-2668-459B-BFFD-6DDD11AADC53}), adding it
Existing WUA Managed server was already set (http://WSUSServername:8530), skipping Group Policy registration.
Added Update Source ({BCB9D60B-2668-459B-BFFD-6DDD11AADC53}) of content type: 2WUAHandler
Async searching of updates using WUAgent started.
Checked the
CI_UpdateSources table and found 2 Update sources unique ids:
{BCB9D60B-2668-459B-BFFD-6DDD11AADC53} Date Created 2011-01-11 03:47:52.000/Date Modified 2011-01-11 03:47:52.000
and
{A2762CA9-9739-4260-9C3A-DC4B36122E16} Date Created 2014-07-09 02:48:46.000 / Date Modified 2014-07-09 02:48:46.000
My questions:
Can I rely on the last modified/created date for inactive update source and delete it off the database? in this case can I delete {BCB9D60B-2668-459B-BFFD-6DDD11AADC53}?
When i browsed to the registry location on the Central Server
HKLM\Software\Wow6432Node\Microsoft\SMS\Components\SMS_WSUS_SYNC_MANAGER i saw the update source as {BCB9D60B-2668-459B-BFFD-6DDD11AADC53}.Does it imply that a stale record?
Any help/guidance will be much appreciated :)