WSUS SUS .. Wiki Contributors .. I Love WSUS .. WSUS Wiki Diary .. Wiki Statistics .. To Do Page Miscellaneous Stuff .. Other Resources .. Do You Know? Terms of Use Trademarks Privacy Statement
|
SYMPTOMS
2005-04-01 13:03:27+0200 1012 768 SyncUpdates: 0x8024400d
CAUSE WORKAROUND Try running the following command on the WSUSserver from the CMD prompt: osql -E -S <SqlServerName> -Q "UPDATE SUSDB.dbo.tbComputerTarget SET where <SqlServerName> is the SQL server you are using. If you are using WMSDE, specify %computername%\wsus. Note that the client information will still show up as unknown in WSUS Administrator, but the clients are able to receive updates. STATUS This is a known issue that will be fixed in the final release. Track ID is: 675794672. Comments:From gbarr - 4/11/07 1:35 PM Last Modified 4/12/05 11:38 AM | Hide Tools |
I've got WSUS 3 RC running on a Windows 2003 SP2 server here and all my clients are getting this error. I cannot run the hotfix found in MS KB 898708 as my server is SP2. The fix above yields the following:
C:\Documents and Settings\GVSAdmin>osql -E -S \\GVSSERVER\wsus -Q "UPDATE SUSDB.dbo.tbComputerTarget SET IsRegistered=1 where IsRegistered = 0"
[DBNETLIB]SQL Server does not exist or access denied.
[DBNETLIB]ConnectionOpen (Connect()).
Looking at my SQL Manager I see the only database listed as \\GVSSERVER\MICROSOFT##SSEE
Running the above command against this db name yields the same error - "does not exist or access denied"
Additionally, I've tried to approach this from the WMI side following these recommendations and that didnt work either.
Any and all help would be appreciated. Thank you!