WSUS 3.0 SP1 Admin Console

Using WSUS 3.0 SP1 on a 2003 server and having problems connecting the the
admin console. WSUS has been running on this server for 6 months without any
problems. Then two weeks ago after a power outage, in which the server was
shutdown properly and a disk failed with the RAID array (has since been
replaced), I can no longer connect to the admin console either on the server
or remotely. I'm using the Windows Internal Database for the SQL instance.
The Windows Internal Database service isn't started and I am unable to start
it manually. When I try and start it manually I get the following message:

Windows could not start the Windows Internal Database (MICROSOFT##SSEE) on
Local Computer. For more information, review the System Event Log. If this is
a non-Microsoft service, contact the service vendor, and refer to
service-specific error code 1814.

When I look at the System Event Log there are a few error messages. Those
errors are as follows:

Source: MSSQL$MICROSOFT## Event ID: 17207 FCB::Open: Operating system error
5(Access is denied.) occurred while creating or opening file
'C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\model.mdf'. Diagnose and
correct the operating system error, and retry the operation.

Source: MSSQL$MICROSOFT## EVent ID: 17204 FCB::Open failed: Could not open
file C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\model.mdf for file number
1. OS error: 5 (Access is denied.).

Source: MSSQL$MICROSOFT## Event ID: 17207 FCB::Open: Operating system error
5(Access is denied.) occurred while creating or opening file
'C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\modellog.ldf'. Diagnose and
correct the operating system error, and retry the operation.

Source: MSSQL$MICROSOFT## EVent ID: 17204 FCB::Open failed: Could not open
file C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\modellog.ldf for file
number 2. OS error: 5 (Access is denied.).

I am also seeing ASP.NET errors in the server Application Log which appear
to be occuring when clients are checking into the WSUS server. Those error
messages are as follows:

Event Type: Warning
Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID: 1309
Date: 8/18/2008
Time: 1:58:04 PM
User: N/A
Computer: IPN-APPS
Description:
Event code: 3001
Event message: The request has been aborted.
Event time: 8/18/2008 1:58:04 PM
Event time (UTC): 8/18/2008 6:58:04 PM
Event ID: 7abcfe464f64450597dc02b69813f5d9
Event sequence: 31
Event occurrence: 10
Event detail code: 0

Application information:
Application domain: /LM/W3SVC/1/ROOT/ClientWebService-2-128635492690436972
Trust level: Full
Application Virtual Path: /ClientWebService
Application Path: C:\Program Files\Update
Services\WebServices\ClientWebService\
Machine name: IPN-APPS

Process information:
Process ID: 2292
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE

Exception information:
Exception type: HttpException
Exception message: Request timed out.

Request information:
Request URL: http://IPN-APPS/ClientWebService/client.asmx
Request path: /ClientWebService/client.asmx
User host address: 10.45.1.11
User: NT AUTHORITY\SYSTEM
Is authenticated: True
Authentication Type: Negotiate
Thread account name: NT AUTHORITY\NETWORK SERVICE

Thread information:
Thread ID: 12
Thread account name: NT AUTHORITY\NETWORK SERVICE
Is impersonating: False
Stack trace:

Custom event details:

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

The ClientDiag.exe runs clean from the clients but when I perform a
"wuauclt.exe /detectnow" I get error code 0x8024400e or 0x80072ee2 in the
WindowsUpdate.log file, which suggests an issue with the SOAP communication.
I have already installed KB954960 on the server so I am not sure where those
errors are coming from.

I've tried uninstalling WSUS and reinstalling but the uninstall fails. Tried
migrating the SQL database to a SQL Server 2005 instance and the SQL Server
2005 installation failed.

I really don't want to start over on another server and I am sure that I am
just missing something that will fix the problem. Appears to be an issue with
SQL, IIS or a combination of the two.

Please help. Any suggestions will be greatly appreciated.

Thanks,
-Grant

Right pew, wrong church. Forwarded to WSUS newsgroup
(microsoft.public.windows.server.update_services) via crosspost as a
convenience to OP.

On the web:
http://www.microsoft.com/communities...pdate_services

In your newsreader:
news://msnews.microsoft.com/microsof...pdate_services

--
~PA Bear

Grant wrote:
> Using WSUS 3.0 SP1 on a 2003 server and having problems connecting the the
> admin console. WSUS has been running on this server for 6 months without
> any
> problems. Then two weeks ago after a power outage, in which the server was
> shutdown properly and a disk failed with the RAID array (has since been
> replaced), I can no longer connect to the admin console either on the
> server
> or remotely. I'm using the Windows Internal Database for the SQL instance.
> The Windows Internal Database service isn't started and I am unable to
> start
> it manually. When I try and start it manually I get the following message:
>
> Windows could not start the Windows Internal Database (MICROSOFT##SSEE) on
> Local Computer. For more information, review the System Event Log. If this
> is a non-Microsoft service, contact the service vendor, and refer to
> service-specific error code 1814.
>
> When I look at the System Event Log there are a few error messages. Those
> errors are as follows:
>
> Source: MSSQL$MICROSOFT## Event ID: 17207 FCB::Open: Operating system
> error
> 5(Access is denied.) occurred while creating or opening file
> 'C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\model.mdf'. Diagnose and
> correct the operating system error, and retry the operation.
>
> Source: MSSQL$MICROSOFT## EVent ID: 17204 FCB::Open failed: Could not open
> file C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\model.mdf for file
> number
> 1. OS error: 5 (Access is denied.).
>
> Source: MSSQL$MICROSOFT## Event ID: 17207 FCB::Open: Operating system
> error
> 5(Access is denied.) occurred while creating or opening file
> 'C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\modellog.ldf'. Diagnose and
> correct the operating system error, and retry the operation.
>
> Source: MSSQL$MICROSOFT## EVent ID: 17204 FCB::Open failed: Could not open
> file C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\modellog.ldf for file
> number 2. OS error: 5 (Access is denied.).
>
> I am also seeing ASP.NET errors in the server Application Log which appear
> to be occuring when clients are checking into the WSUS server. Those error
> messages are as follows:
>
> Event Type: Warning
> Event Source: ASP.NET 2.0.50727.0
> Event Category: Web Event
> Event ID: 1309
> Date: 8/18/2008
> Time: 1:58:04 PM
> User: N/A
> Computer: IPN-APPS
> Description:
> Event code: 3001
> Event message: The request has been aborted.
> Event time: 8/18/2008 1:58:04 PM
> Event time (UTC): 8/18/2008 6:58:04 PM
> Event ID: 7abcfe464f64450597dc02b69813f5d9
> Event sequence: 31
> Event occurrence: 10
> Event detail code: 0
>
> Application information:
> Application domain: /LM/W3SVC/1/ROOT/ClientWebService-2-128635492690436972
> Trust level: Full
> Application Virtual Path: /ClientWebService
> Application Path: C:\Program Files\Update
> Services\WebServices\ClientWebService\
> Machine name: IPN-APPS
>
> Process information:
> Process ID: 2292
> Process name: w3wp.exe
> Account name: NT AUTHORITY\NETWORK SERVICE
>
> Exception information:
> Exception type: HttpException
> Exception message: Request timed out.
>
> Request information:
> Request URL: http://IPN-APPS/ClientWebService/client.asmx
> Request path: /ClientWebService/client.asmx
> User host address: 10.45.1.11
> User: NT AUTHORITY\SYSTEM
> Is authenticated: True
> Authentication Type: Negotiate
> Thread account name: NT AUTHORITY\NETWORK SERVICE
>
> Thread information:
> Thread ID: 12
> Thread account name: NT AUTHORITY\NETWORK SERVICE
> Is impersonating: False
> Stack trace:
>
> Custom event details:
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
> The ClientDiag.exe runs clean from the clients but when I perform a
> "wuauclt.exe /detectnow" I get error code 0x8024400e or 0x80072ee2 in the
> WindowsUpdate.log file, which suggests an issue with the SOAP
> communication.
> I have already installed KB954960 on the server so I am not sure where
> those
> errors are coming from.
>
> I've tried uninstalling WSUS and reinstalling but the uninstall fails.
> Tried
> migrating the SQL database to a SQL Server 2005 instance and the SQL
> Server
> 2005 installation failed.
>
> I really don't want to start over on another server and I am sure that I
> am
> just missing something that will fix the problem. Appears to be an issue
> with SQL, IIS or a combination of the two.
>
> Please help. Any suggestions will be greatly appreciated.
>
> Thanks,
> -Grant

Lawrence,

Before I uninstalled I changed the login for the Windows Internal Database
Service from NT AUTHORITY\NetworkService to a domain admin account and the
service started fine. I then tried the WSUS Admin Console again and now it
works fine. Don't know why I didn't think of changing that before, but as
long as it's working I'll keep it as is. Thanks for your response

-Grant

"Lawrence Garvin" wrote:

> "PA Bear [MS MVP]" <PABearMVP@gmail.com> wrote in message
> news:OaC5S3aAJHA.1224@TK2MSFTNGP02.phx.gbl...
>
> >> problems. Then two weeks ago after a power outage, in which the server
> >> was
> >> shutdown properly and a disk failed with the RAID array (has since been
> >> replaced),
>
> >> When I look at the System Event Log there are a few error messages. Those
> >> errors are as follows:
>
> >> Source: MSSQL$MICROSOFT## EVent ID: 17204 FCB::Open failed: Could not
> >> open
> >> file C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\model.mdf for file
> >> number
> >> 1. OS error: 5 (Access is denied.).
>
>
> >> The ClientDiag.exe runs clean from the clients but when I perform a
> >> "wuauclt.exe /detectnow" I get error code 0x8024400e or 0x80072ee2 in the
> >> WindowsUpdate.log file, which suggests an issue with the SOAP
> >> communication.
>
> Or the WSUS Server isn't running because it can't start the database
> service!
>
> >> I've tried uninstalling WSUS and reinstalling but the uninstall fails.
>
> For the same reason.. uninstalling/reinstalling WSUS doesn't repair a
> corrupted database server.
>
> >> I really don't want to start over on another server and I am sure that I
> >> am
> >> just missing something that will fix the problem. Appears to be an issue
> >> with SQL, IIS or a combination of the two.
>
> It's exclusively an issue with the Windows Internal Database installation,
> specifically, as noted in the error message -- the file model.mdf is either
> missing or corrupted beyond use.
>
> The *correct* fix is to "repair the Model database" in that instance of SQL
> Server (WID).
>
> There are a number of ways this can be performed, but the *EASIST*, is to:
>
> 1. Uninstall WSUS -- keep the databases and content.
> 2. UNINSTALL the Windows Internal Database, and make sure the
> %windir%\SYSMIS\SSEE\MSSQL.2005 folder is removed.
> (The WSUS database should be in the ~\WSUS folder tree.)
> 3. Reboot.
> 4. Reinstall WSUS -- this should now trigger the reinstallation of the
> WID with clean system databases,
> and the reattachment of the databases from the original install.
>
>
>
> --
> Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
> 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/pro...awrence.Garvin
>

Lawrence,

I was unable to run the uninstall before because I couldn't start the WID
Service and the uninstall would fail everytime. Now that I am able to start
that service I can now run the uninstall/reinstall of WSUS and return it to
it's original state.

Thanks for your help.

-Grant

"Lawrence Garvin" wrote:

> "Grant" <Grant@discussions.microsoft.com> wrote in message
> news:492BD4C3-EDCD-4148-A7B1-38AD6440A92A@microsoft.com...
> > Lawrence,
> >
> > Before I uninstalled I changed the login for the Windows Internal Database
> > Service from NT AUTHORITY\NetworkService to a domain admin account
>
> Well, that certainly didn't help! Change it back!
>
> > and the service started fine.
>
> Yes.. the =service= will be able to start fine, but it's just not that
> simple.
>
> > I then tried the WSUS Admin Console again and now it
> > works fine. Don't know why I didn't think of changing that before,
>
> Because it's not the *correct* solution to the problem.
>
> > but as long as it's working I'll keep it as is.
>
> Until it breaks again, and now *this* misconfiguration will just confuse all
> of the troubleshooting on the next issue, since you won't remember that you
> changed the logon account for the database service.
>
> There's a =reason= the database service is configured to use the Network
> Service account. :-)
>
>
> --
> Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
> 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/pro...awrence.Garvin
>