Link to home
Start Free TrialLog in
Avatar of jyarbrough_rc
jyarbrough_rcFlag for United States of America

asked on

WSUS 3 SP1 Event ID:18456 Login failed for user 'NT AUTHORITY\NETWORK SERVICE'

I am running WSUS 3 SP1 and have no issues until just yesterday.  I noticed yesterday that I could not open the WSUS admin console (MMC).  It errored out with the following informaiton:

---------------------------------------------------------------------------------------

The WSUS administration console was unable to connect to the WSUS Server Database.
   
Verify that SQL server is running on the WSUS Server. If the problem persists, try restarting SQL.
   
System.Data.SqlClient.SqlException -- Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.

Source
.Net SqlClient Data Provider

Stack Trace:
   at Microsoft.UpdateServices.Internal.BaseApi.SoapExceptionProcessor.DeserializeAndThrow(SoapException soapException)
   at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccessProxy.ExecuteSPGetUpdateServerStatus(UpdateSources updateSources, Boolean includeDownstreamComputers, String updateScopeXml, String computerTargetScopeXml, String preferredCulture, ExtendedPublicationState publicationState, UpdateServerStatusPropertiesToGet propertiesToGet)
   at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetStatus(UpdateSources updateSources, Boolean includeDownstreamComputers, UpdateScope updatesToInclude, ComputerTargetScope computersToInclude, UpdateServerStatusPropertiesToGet propertiesToGet)
   at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetReplicaStatus(UpdateSources updateSources)
   at Microsoft.UpdateServices.UI.SnapIn.Common.CachedUpdateServerStatus.GetFreshObjectForCache()
   at Microsoft.UpdateServices.UI.AdminApiAccess.CachedObject.RefreshCache()
   at Microsoft.UpdateServices.UI.AdminApiAccess.CachedObject.GetFromCache()
   at Microsoft.UpdateServices.UI.SnapIn.Pages.ServerSummaryPage.backgroundWorker_DoWork(Object sender, DoWorkEventArgs e)

---------------------------------------------------------------------------------------

Research pointed to restarting the SQL database, which in my case is the Windows Internal Database.  I restarted the service and had no further issues the rest of the day.  I came back in the office the next day and had the same issue.  I restarted the SQL database as I had done the day before, but the issue was not resolved.  Upon further investigation I have found that this seems to be a permissions issue for the user that is tryin to log into the database.  Following is information from the event logs on the server:

-------------------------------------------------------------------------------------------

Source: MSSQL$MICROSOFT##
User: NT AUTHORITY\NETWORK SERVICE
Event ID: 18456
Description:
Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. [CLIENT: <named pipe>]

-------------------------------------------------------------------------------------------
Information regarding SQL version gathered from event log just after a system start up:

Microsoft SQL Server 2005 - 9.00.4035.00 (Intel X86)
      Nov 24 2008 13:01:59
      Copyright (c) 1988-2005 Microsoft Corporation
      Windows Internal Database on Windows NT 5.2 (Build 3790: Service Pack 2)

Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query ].
--------------------------------------------------------------------------------------------

I am not a SQL (or even a DB) admin so this may be a easy fix, but I have been unable to find a resolution after a day's worth of searching for an answer.  I have done the obvious (as suggested in many online posts) which is giving the 'NT AUTHORITY\NETWORK SERVICE' user full security permissions to the directory on my server that holds the SUSDB, this has not fixed the issue.   Any assistance would be greatly appreciated.  
Avatar of ajkreddy
ajkreddy
Flag of United States of America image

Hi,

Are you using SQL database or embedded database?

Did you modified any permissions in IIS?

If so please open the command prompt and type iisreset.

Avatar of Don
Firstly, you should update WSUS to sp2

Also there is a "Windows Internal Database" update to sp4
Avatar of jyarbrough_rc

ASKER

No changes to the system at all, with the exception of one windows update (KB2419635) applied on Wednesday at 1:00am which has since been removed to verify it was not the root cause of the issue.  The database was installed with WSUS 3, which as I understand is a stripped down version of SQL 2005 known as Windows Internal Database so I guess embedded?

Thanks.
@dstewartjr

I know there is a update for WSUS to SP2, I was not aware of the update to Windows Internal Database.  There have been no changes to the system to cause this issue.  I would like to know what happened, and how to fix it.  Not sure the updates will resolve the root cause.
As dstewartjr stated please upgrade to Sp2 and did you tried iisreset?
There are many reasons for this error arising

http://www.eventid.net/display.asp?eventid=18456&eventno=8175&source=MSSQLSERVER&phase=1


I stand by updating to resolve


be sure to go over pre-requisites
@ dstewartjr

From the link you provided:
http://www.eventid.net/display.asp?ventid=18456&eventno=8175&source=MSSQLSERVER&phase=1

This problem may appear because the NT AUTHORITY\NETWORK SERVICE account does not have login permissions to master database in the SQL 2005 instance. Add the NT AUTHORITY\NETWORK SERVICE account to the master database permissions list, restart the SQL server, restart the IIS service, and then restart the Update Services service.

I have restarted all services noted, but I don't know how to modify login permissions for Windows Internal Database.  Not working still.  Thanks.
if you dont mind please reboot your server
I saw this earlier today as well:

http://support.microsoft.com/default.aspx?scid=kb;en-us;947378 

Not my issue...
The server has been rebooted three times today.
Update, Update, Update....then we can troubleshoot if need be



can I have the details to troubleshoot your server?
ASKER CERTIFIED SOLUTION
Avatar of jyarbrough_rc
jyarbrough_rc
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
updating would have also reindexed the database
Wsus 3.0 sp1 is outdated as is the internal database(sp2-now on sp4)

Updating would have also resolved this issue
Updating the database was not the resolution to the issue.   As such I can not verify a update of the database as the fix.  I do however know that reindexing the database resolved the issue.  
----------------------------------------------
Information on SQL version on my server:

Microsoft SQL Server 2005 - 9.00.4035.00 (Intel X86)
      Nov 24 2008 13:01:59
      Copyright (c) 1988-2005 Microsoft Corporation
      Windows Internal Database on Windows NT 5.2 (Build 3790: Service Pack 2)

The above says that the OS on our server is at SP2, not that SQL is at SP2.  Build 3790: SP2 is the latest version of Server 2003 (i.e Windows NT 5.2).  You are correct that there is a update to the version of SQL and Windows Internal Database as 9.00.4035 is SP3.  
I just realized that the command I submitted to re-index the DB called a sql query.  That query is attached to this post.

"C:\Program Files\Microsoft SQL Server\90\Tools\binn\sqlcmd" -S \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query -i C:\Maintenance\WsusDBMaintenance.sql -o C:\Maintenance\WsusDbMaint.log
WsusDBMaintenance.sql