Migrated WSUS from 2008R2 to 2012R2 - WID errors and Win7/2008R2 machines don't connect

Question

Recently migrated from 2008R2 WSUS to 2012R2 WSUS via a very troublesome migration (see this thread for details:  http://community.spiceworks.com/topic/535378-wsus-replica-no-computers-updates-listed?page=1#entry-3541584 ).  But I was finally able
to get the migration to work, db moved and set up, sync'd w/MS, etc.  Yet for some reason none of my 2008R2 servers or Win7 machines connect to the new WSUS server.  Also, which is puzzling, is the actual WSUS server itself doesn't connect in to
itself.
This is what I see on my PC's WindowsUpdate.log file:
2014-07-14 05:48:12:681 1112 2448 AU #############
2014-07-14 05:48:12:681 1112 2448 AU ## START ## AU: Search for updates
2014-07-14 05:48:12:681 1112 2448 AU #########
2014-07-14 05:48:12:683 1112 2448 AU <<## SUBMITTED ## AU: Search for updates [CallId = {E426BB1C-410A-4B3C-B37F-CAD668BA88CF}]
2014-07-14 05:48:12:683 1112 20fc Agent *************
2014-07-14 05:48:12:683 1112 20fc Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-07-14 05:48:12:683 1112 20fc Agent *********
2014-07-14 05:48:12:683 1112 20fc Agent * Online = Yes; Ignore download priority = No
2014-07-14 05:48:12:684 1112 20fc Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and
DeploymentAction='Uninstallation' and RebootRequired=1"
2014-07-14 05:48:12:684 1112 20fc Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2014-07-14 05:48:12:684 1112 20fc Agent * Search Scope = {Machine}
2014-07-14 05:48:12:758 1112 20fc Setup Checking for agent SelfUpdate
2014-07-14 05:48:12:759 1112 20fc Setup Client version: Core: 7.6.7600.256 Aux: 7.6.7600.256
2014-07-14 05:48:12:759 1112 20fc Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2014-07-14 05:48:12:789 1112 20fc Misc Microsoft signed: Yes
2014-07-14 05:48:15:056 1112 20fc Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2014-07-14 05:48:15:063 1112 20fc Misc Microsoft signed: Yes
2014-07-14 05:48:15:067 1112 20fc Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2014-07-14 05:48:15:082 1112 20fc Misc Microsoft signed: Yes
2014-07-14 05:48:15:085 1112 20fc Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190194
2014-07-14 05:48:15:085 1112 20fc Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190194
2014-07-14 05:48:15:085 1112 20fc Misc WARNING: DownloadFileInternal failed for
http://ServerName-01:8530/selfupdate/WSUS3/x64/Win7SP1/wsus3setup.cab: error 0x80190194
2014-07-14 05:48:15:085 1112 20fc Setup WARNING: SelfUpdate check failed to download package information, error = 0x80244019
2014-07-14 05:48:15:085 1112 20fc Setup FATAL: SelfUpdate check failed, err = 0x80244019
2014-07-14 05:48:15:085 1112 20fc Agent * WARNING: Skipping scan, self-update check returned 0x80244019
2014-07-14 05:48:15:115 1112 20fc Agent * WARNING: Exit code = 0x80244019
2014-07-14 05:48:15:115 1112 20fc Agent *********
2014-07-14 05:48:15:115 1112 20fc Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2014-07-14 05:48:15:115 1112 20fc Agent *************
2014-07-14 05:48:15:115 1112 20fc Agent WARNING: WU client failed Searching for update with error 0x80244019
2014-07-14 05:48:15:116 1112 1658 AU >>## RESUMED ## AU: Search for updates [CallId = {E426BB1C-410A-4B3C-B37F-CAD668BA88CF}]
2014-07-14 05:48:15:116 1112 1658 AU # WARNING: Search callback failed, result = 0x80244019
2014-07-14 05:48:15:116 1112 1658 AU # WARNING: Failed to find updates with error code 80244019
2014-07-14 05:48:15:116 1112 1658 AU #########
2014-07-14 05:48:15:116 1112 1658 AU ## END ## AU: Search for updates [CallId = {E426BB1C-410A-4B3C-B37F-CAD668BA88CF}]
2014-07-14 05:48:15:116 1112 1658 AU #############
2014-07-14 05:48:15:116 1112 1658 AU Successfully wrote event for AU health state:0
2014-07-14 05:48:15:117 1112 1658 AU AU setting next detection timeout to 2014-07-14 17:48:15
2014-07-14 05:48:15:117 1112 1658 AU Successfully wrote event for AU health state:0
2014-07-14 05:48:15:131 1112 1658 AU Successfully wrote event for AU health state:0
2014-07-14 05:48:20:085 1112 20fc Report REPORT EVENT: {46204AF0-1316-4901-8710-817B9064F3D9} 2014-07-14 05:48:15:085-0700 1 148 101 {D67661EB-2423-451D-BF5D-13199E37DF28} 1 80244019 SelfUpdate Failure Software Synchronization Windows Update Client failed
to detect with error 0x80244019.
2014-07-14 05:48:20:107 1112 20fc Report CWERReporter::HandleEvents - WER report upload completed with status 0x8
2014-07-14 05:48:20:107 1112 20fc Report WER Report sent: 7.6.7600.256 0x80244019 D67661EB-2423-451D-BF5D-13199E37DF28 Scan 101 Managed
2014-07-14 05:48:20:107 1112 20fc Report CWERReporter finishing event handling. (00000000)
2014-07-14 05:59:19:092 1112 20fc PT WARNING: Cached cookie has expired or new PID is available
2014-07-14 05:59:19:092 1112 20fc PT Initializing simple targeting cookie, clientId = be5336c9-d649-431a-91b6-d4f8ac2cbbe5, target group = , DNS name = ComputerName.domain.local
2014-07-14 05:59:19:092 1112 20fc PT Server URL =
http://ServerName-01:8530/SimpleAuthWebService/SimpleAuth.asmx
2014-07-14 05:59:19:104 1112 20fc Report Uploading 1 events using cached cookie, reporting URL =
http://ServerName-01:8530/ReportingWebService/ReportingWebService.asmx
2014-07-14 05:59:19:106 1112 20fc Report Reporter successfully uploaded 1 events.
I'm also seeing a bunch of MSSQL$MICROSOFT##WID errors in event viewer.  They all are talking about the susdb file that
WAS initially associated with the WSUS install.  That was prior to my changing over to SQL2014express to get things to work...it looks as if it never fully cleared itself out.  That file is no longer in the Windows\WID folder,
yet there are still other files in there...is there a way to remove MSSQL$MICROSOFT##WID and this association with susdb file?
I think this is also the reason my SBE backup jobs are failing on my Hyper-V server...because there are backup job errors on this server referencing the SQL##WID account...
errors 18210; 3041; 1 WIDVDI; 8229 VSS; 2 vmicvss; 17204
Any and all help is greatly appreciated.
Thanks

Answer 1

Hi,
DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation'
and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
RebootRequired=1 this means the server is pending restart.
errors 18210; 3041; 1 WIDVDI; 8229 VSS; 2 vmicvss; 17204
Is VSS enabled on the drive which WID stored? Run “vssadmin list writers”, check if there is any errors under wid writer. Or you can disable WID vss writer service.
is there a way to remove MSSQL$MICROSOFT##WID and this association with susdb file?
When you removed WID feature, delete the susdb and susdb_log files and then reinstall.
In addition, the method referred in my last reply is also worth trying. And I forgot we should patch WSUS 3.2 with
http://support.microsoft.com/kb/2734608
Hope this helps.