Re: WSUS Errors after System state restored
- From: "Cliff Galiher" <cgaliher@xxxxxxxxx>
- Date: Thu, 4 Jun 2009 19:23:19 -0600
You didn't mention what version of WSUS you are running (R2 ships with V2) but my first thought is to download v3 SP1 and run the installer. It should uninstall the old version, stopping the appropriate services and removing the database, and you can get a nice upgrade from there as well.
-Cliff
"Siv" <Siv@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:73F0045D-04A1-4A88-A812-415B93F63F3D@xxxxxxxxxxxxxxxx
Hi,
One of my clients had a major power outage and although the UPS saved the
day the first time another outage occurred and the UPS had not had time to
recover sufficiently and the server went off whilst running. When power
finally came back and the server was started up again we were getting all
sorts of Active Directory errors. I tried various things to repair it but to
no avail and in the end just restored system state from the backup.
I then had a few problems with MS Exchange but was able to successfully
restore that from backup as well and thought all was working only to discover
that WSUS was not working.
Checking the event logs I found the following errors:
Event Type: Error
Event Source: Windows Server Update Services
Event Category: Update Services Service
Event ID: 421
Date: 04/06/2009
Time: 17:23:10
User: N/A
Computer: ACMSERVER
Description:
Connection to database failed. Reason=Cannot open database "SUSDB" requested
by the login. The login failed.
Login failed for user 'NT AUTHORITY\SYSTEM'.. Connection string:
Net=dbnmpntw;Data Source=\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query;;Initial
Catalog=SUSDB;Connection Timeout=60;Application Name=WSUS SQL
Connection;Trusted_Connection=Yes;Pooling='true'; Max Pool Size = 100
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
=====================================
Event Type: Failure Audit
Event Source: MSSQL$MICROSOFT##SSEE
Event Category: (4)
Event ID: 18456
Date: 04/06/2009
Time: 17:23:10
User: NT AUTHORITY\SYSTEM
Computer: ACMSERVER
Description:
Login failed for user 'NT AUTHORITY\SYSTEM'. [CLIENT: <named pipe>]
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 18 48 00 00 0e 00 00 00 .H......
0008: 1a 00 00 00 41 00 43 00 ....A.C.
0010: 4d 00 53 00 45 00 52 00 M.S.E.R.
0018: 56 00 45 00 52 00 5c 00 V.E.R.\.
0020: 4d 00 49 00 43 00 52 00 M.I.C.R.
0028: 4f 00 53 00 4f 00 46 00 O.S.O.F.
0030: 54 00 23 00 23 00 53 00 T.#.#.S.
0038: 53 00 45 00 45 00 00 00 S.E.E...
0040: 07 00 00 00 6d 00 61 00 ....m.a.
0048: 73 00 74 00 65 00 72 00 s.t.e.r.
0050: 00 00 ..
===========================
Event Type: Error
Event Source: MSSQL$MICROSOFT##SSEE
Event Category: (2)
Event ID: 3414
Date: 04/06/2009
Time: 17:22:27
User: NT AUTHORITY\SYSTEM
Computer: ACMSERVER
Description:
An error occurred during recovery, preventing the database 'SUSDB' (database
ID 5) from restarting. Diagnose the recovery errors and fix them, or restore
from a known good backup. If errors are not corrected or expected, contact
Technical Support.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 56 0d 00 00 15 00 00 00 V.......
0008: 1a 00 00 00 41 00 43 00 ....A.C.
0010: 4d 00 53 00 45 00 52 00 M.S.E.R.
0018: 56 00 45 00 52 00 5c 00 V.E.R.\.
0020: 4d 00 49 00 43 00 52 00 M.I.C.R.
0028: 4f 00 53 00 4f 00 46 00 O.S.O.F.
0030: 54 00 23 00 23 00 53 00 T.#.#.S.
0038: 53 00 45 00 45 00 00 00 S.E.E...
0040: 07 00 00 00 6d 00 61 00 ....m.a.
0048: 73 00 74 00 65 00 72 00 s.t.e.r.
0050: 00 00 ..
============================
Event Type: Error
Event Source: MSSQL$MICROSOFT##SSEE
Event Category: (2)
Event ID: 9003
Date: 04/06/2009
Time: 17:22:27
User: NT AUTHORITY\SYSTEM
Computer: ACMSERVER
Description:
The log scan number (93122:315:1) passed to log scan in database 'SUSDB' is
not valid. This error may indicate data corruption or that the log file
(.ldf) does not match the data file (.mdf). If this error occurred during
replication, re-create the publication. Otherwise, restore from backup if the
problem results in a failure during startup.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 2b 23 00 00 14 00 00 00 +#......
0008: 1a 00 00 00 41 00 43 00 ....A.C.
0010: 4d 00 53 00 45 00 52 00 M.S.E.R.
0018: 56 00 45 00 52 00 5c 00 V.E.R.\.
0020: 4d 00 49 00 43 00 52 00 M.I.C.R.
0028: 4f 00 53 00 4f 00 46 00 O.S.O.F.
0030: 54 00 23 00 23 00 53 00 T.#.#.S.
0038: 53 00 45 00 45 00 00 00 S.E.E...
0040: 07 00 00 00 6d 00 61 00 ....m.a.
0048: 73 00 74 00 65 00 72 00 s.t.e.r.
0050: 00 00 ..
So basically things looked pretty screwed.
I decided to remove WSUS and re-install it as I do not backup the WSUS data
so couldn't recover that as well.
When I tried to remove it the removal failed with an error (it didn't quote
the error details) and then closed. It removed the WSUS entry from
Add/Remove programs, but the application is still on the server and still
generating errors.
Can anyone point me at a fix for this as I cannot find anything that seems
relevant at MS or on the net.
Server is Windows Small Business Server 2003 R2.
Cheers,
Siv
--
Martley, Near Worcester, UK
.
- Follow-Ups:
- References:
- WSUS Errors after System state restored
- From: Siv
- WSUS Errors after System state restored
- Prev by Date: Re: SBS 2003 User IDs and Mailboxes
- Next by Date: Re: IE6 vs IE& vs IE8 on SBS
- Previous by thread: WSUS Errors after System state restored
- Next by thread: Re: WSUS Errors after System state restored
- Index(es):
Relevant Pages
|
