Running WSUS 3.0 and getting database error in console
Iowascooterb
updates and Security updates. I approved an update for only our test group
and now want to be able to approve it for all computers but am unable to as I
get the database error each time I try and see approved updates.
I just took over this server so I am not familiar with the build and we do
not have a databse backup. It is our primary WSUS server with 9 downstream
replica servers.
The logs refer to running database maintenance but I am not very versed in
SQL so any suggestions on repairing the database would be appreciated.
Can this database be repaired or would I be better planning to rebuild this
server?
Can the configuration of the server be backed up and restored to a new
server?
Looking in the event log I have the following error.
Event Type: Error
Event Source: MSSQL$MICROSOFT##SSEE
Event Category: (2)
Event ID: 824
Date: 1/5/2008
Time: 1:24:10 AM
User: NT AUTHORITY\NETWORK SERVICE
Computer: TDNAV03
Description:
SQL Server detected a logical consistency-based I/O error: torn page
(expected signature: 0x55555555; actual signature: 0xd65e37c1). It occurred
during a read of page (1:74080) in database ID 5 at offset 0x000000242c0000
in file 'E:\WsusDatabase\SUSDB.mdf'. Additional messages in the SQL Server
error log or system event log may provide more detail. This is a severe error
condition that threatens database integrity and must be corrected
immediately. Complete a full database consistency check (DBCC CHECKDB). This
error can be caused by many factors; for more information, see SQL Server
Books Online.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 38 03 00 00 18 00 00 00 8.......
0008: 18 00 00 00 54 00 44 00 ....T.D.
0010: 4e 00 41 00 56 00 30 00 N.A.V.0.
0018: 33 00 5c 00 4d 00 49 00 3.\.M.I.
0020: 43 00 52 00 4f 00 53 00 C.R.O.S.
0028: 4f 00 46 00 54 00 23 00 O.F.T.#.
0030: 23 00 53 00 53 00 45 00 #.S.S.E.
0038: 45 00 00 00 06 00 00 00 E.......
0040: 53 00 55 00 53 00 44 00 S.U.S.D.
0048: 42 00 00 00 B...
Lawrence Garvin [MVP]
news:F4536804-0FD0-40DE...@microsoft.com...
>I am getting this error when I try to view approved updates under Critical
> updates and Security updates.
> Event Source: MSSQL$MICROSOFT##SSEE
> SQL Server detected a logical consistency-based I/O error: torn page
> (expected signature: 0x55555555; actual signature: 0xd65e37c1).
Ouch. We don't see too many of these anymore, but it's definitely a serious
issue.
> Complete a full database consistency check (DBCC CHECKDB). This
> error can be caused by many factors; for more information, see SQL Server
> Books Online.
This is *exactly* what you should do. Also, you'll probably have to get
familiar with SQLCMD as well, so that you can run the DBCC commands on the
Windows Internal Database. You might also search the Microsoft Knowledge
Base and SQL Server website for any KB articles or white papers that talk
about how to do advanced database maintenance using the Windows Internal
Database.
Another option is to install SQL Server Management Studio, and configure it
to use Named Pipes, which should give you full access to the SUSDB database
in the WID installation.
There is also relevant documentation in the WSUS3 Operations Guide
concerning management of the WID in the WSUS environment. That may be the
best place to start.
Appendix I: Database Maintenance
http://technet2.microsoft.com/windowsserver/en/library/81545a18-2d30-444a-8a1e-846e065bd04b1033.mspx?mfr=true
--
Lawrence Garvin, M.S., MCBMSP, MCTS, MCP
Senior Data Architect, APQC, Houston, Texas
Microsoft MVP - Software Distribution (2005-2008)
MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
Iowascooterb
I attempted to do these repairs but was not able to login to database to
successful run them.
So considering the database beyond repair I uninstalled WSUS 3.0 and
reinstalled it. Which was also a challenge. It did not want to fully
uninstall and thus reinstall. Tried all the tricks in the newsgroups with no
sucess. finally ran the Windows Install Cleanup and was able to reinstall.
I have another question now that I have it sucessfully reinstalled and
client computers are checking in and downstream servers showed up.
I resynched the wsus server and now have 1300 unapproved Security and 200
unapproved critical.
Will i now have to try and figure out which ones to re approve so any new
clients if not fully patched will receive the correct updates?
I would guess so
![Harry Johnston [MVP]'s profile photo](http://lh3.googleusercontent.com/a-/ALV-UjWpkBAPqvc839nzAtvH7xG03OwcxExyoyKpBgg3G7rKJeLEHQ=s40-c)
Harry Johnston [MVP]
> Will i now have to try and figure out which ones to re approve so any new
> clients if not fully patched will receive the correct updates?
This depends on the circumstances under which new clients may be added to your
network, and on how quickly you expect them to be patched.
If all new clients are fresh installs, there shouldn't be a problem provided
your install procedure is reasonably methodical; all fresh installs will need
the same set of patches (plus newly released patches of course) so you only need
to check one of them.
If some new clients aren't fresh installs, but you are always aware when a new
client is added, you can wait for each such client to report in and then check
the updates view (filtered for unapproved and needed updates) to see if any
additional updates need to be approved. Or, preferably, you could use Microsoft
Update to make sure clients are patched /before/ they are connected to your
internal network. :-)
If you don't always know when a new client is added (or, equivalently, don't
know whether or not all your existing clients have reported in) but aren't in
too much of a hurry to get them patched, you could just check periodically.
Harry.
Lawrence Garvin [MVP]
> Great information and I did download sqlcmd and SQL Server Management
> Studio.
> I attempted to do these repairs but was not able to login to database to
> successful run them.
With the Windows Internal Database is it *required* that you manually
configure the client tools to use Named Pipes (which is not enabled by
default). Otherwise, by default, the tools will try to use TCP/IP, which
won't work with Windows Internal Database.
> I have another question now that I have it sucessfully reinstalled and
> client computers are checking in and downstream servers showed up.
>
> I resynched the wsus server and now have 1300 unapproved Security and 200
> unapproved critical.
>
> Will i now have to try and figure out which ones to re approve so any new
> clients if not fully patched will receive the correct updates?
No... I would recommend you first let the clients report in, execute a
detection, and report to the WSUS Server which updates are "Needed". Then,
approve the updates that are "Needed" (and any others that you definitively
want to have immediately/always available.)
This is easily done by doing a filter on the All Updates screen for "Not
Approved" and "Needed", and then approving the listed updates for the
appropriate groups.