Event-ID 18456 seit WSUS 3.0 SP1 Inst. auf W2k3

29/04/2009 - 13:51 von Josef Gartner | Report spam
Hallo,

wir betreiben seit Jahren einen W2k3 SP2 Memberserver in einer W2k3-Domàne
mit 2 DCs, mehreren Serven und ca. 150 Clients. Bisher problemlos.

Seit ich WSUS 3.0 SP1 auf dem Server laufen hab, tritt bei jedem Neustart
des Servers folgender Fehler im Anwendungslog auf:
Ereignistyp: Fehlerüberw.
Ereignisquelle: MSSQL$MICROSOFT##SSEE
Ereigniskategorie: (4)
Ereigniskennung: 18456
Datum: 28.04.2009
Zeit: 13:09:01
Benutzer: NT-AUTORITÄT\NETZWERKDIENST
Computer: XXX
Beschreibung:
Login failed for user 'NT-AUTORITÄT\NETZWERKDIENST'. [CLIENT: <named pipe>]

Info zum SQL:
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)

Das komplette SQL-Log:
2009-04-28 13:08:50.07 Server (c) 2005 Microsoft Corporation.
2009-04-28 13:08:50.07 Server All rights reserved.
2009-04-28 13:08:50.07 Server Server process ID is 1348.
2009-04-28 13:08:50.07 Server Authentication mode is WINDOWS-ONLY.
2009-04-28 13:08:50.10 Server Logging SQL Server messages in file
'c:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\LOG\ERRORLOG'.
2009-04-28 13:08:50.10 Server This instance of SQL Server last reported
using a process ID of 1312 at 28.04.2009 11:05:37 (local) 28.04.2009
09:05:37 (UTC). This is an informational message only; no user action is
required.
2009-04-28 13:08:50.10 Server Registry startup parameters:
2009-04-28 13:08:50.20 Server -d
c:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\master.mdf
2009-04-28 13:08:50.20 Server -e
c:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\LOG\ERRORLOG
2009-04-28 13:08:50.20 Server -l
c:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\mastlog.ldf
2009-04-28 13:08:50.48 Server SQL Server is starting at normal priority
base (=7). This is an informational message only. No user action is
required.
2009-04-28 13:08:50.48 Server Detected 2 CPUs. This is an informational
message; no user action is required.
2009-04-28 13:08:53.59 Server Using dynamic lock allocation. Initial
allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is
an informational message only. No user action is required.
2009-04-28 13:08:56.35 Server Database mirroring has been enabled on
this instance of SQL Server.
2009-04-28 13:08:56.82 spid5s Starting up database 'master'.
2009-04-28 13:08:57.34 spid5s Recovery is writing a checkpoint in
database 'master' (1). This is an informational message only. No user action
is required.
2009-04-28 13:08:57.77 spid5s SQL Trace ID 1 was started by login "sa".
2009-04-28 13:08:57.90 spid5s Starting up database
'mssqlsystemresource'.
2009-04-28 13:08:58.08 spid5s The resource database build version is
9.00.4035. This is an informational message only. No user action is
required.
2009-04-28 13:08:58.93 spid8s Starting up database 'model'.
2009-04-28 13:08:58.94 Server Server local connection provider is ready
to accept connection on [ \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query ].
2009-04-28 13:08:59.00 Server Dedicated administrator connection
support was not started because it is not available on this edition of SQL
Server. This is an informational message only. No user action is required.
2009-04-28 13:08:58.99 spid5s Server name is
'SERVERXXX\MICROSOFT##SSEE'. This is an informational message only. No user
action is required.
2009-04-28 13:08:59.01 spid5s Starting up database 'msdb'.
2009-04-28 13:08:59.05 Server SQL Server is now ready for client
connections. This is an informational message; no user action is required.
2009-04-28 13:09:01.29 Logon Error: 18456, Severity: 14, State: 16.
2009-04-28 13:09:01.29 Logon Login failed for user
'NT-AUTORITÄT\NETZWERKDIENST'. [CLIENT: <named pipe>]
2009-04-28 13:09:03.17 spid8s Clearing tempdb database.
2009-04-28 13:09:05.27 spid8s Starting up database 'tempdb'.
2009-04-28 13:09:06.24 spid5s Recovery is complete. This is an
informational message only. No user action is required.
2009-04-28 13:09:06.60 spid11s The Service Broker protocol transport is
disabled or not configured.
2009-04-28 13:09:06.71 spid11s The Database Mirroring protocol transport
is disabled or not configured.
2009-04-28 13:09:06.87 spid11s Service Broker manager has started.
2009-04-28 13:09:31.44 spid51 Starting up database 'SUSDB'.
2009-04-28 13:09:33.68 spid51 2 transactions rolled forward in database
'SUSDB' (5). This is an informational message only. No user action is
required.
2009-04-28 13:09:33.76 spid51 0 transactions rolled back in database
'SUSDB' (5). This is an informational message only. No user action is
required.
2009-04-28 13:09:33.76 spid51 Recovery is writing a checkpoint in
database 'SUSDB' (5). This is an informational message only. No user action
is required.

Probleme treten nicht auf. Was soll ich tun, bzw. soll ich überhaupt etwas
tun? Hab schon in der WSUS-NG gefragt, die haben mir hierhergeschickt.

Vielen Dank
Josef Gartner
 

Lesen sie die antworten

#1 Torsten Schuessler
29/04/2009 - 15:21 | Warnen spam
Hallo Josef,


"Josef Gartner" wrote:
tun? Hab schon in der WSUS-NG gefragt, die haben mir hierhergeschickt.



darf ich dich wieder zurückschicken :-)

Die Anmeldung für 'NT-AUTORITÄT\NETZWERKDIENST' wurde vom Server verweigert
(schau mal unter Sicherheit - Anmeldungen, dort müsste er stehen?), im WSUS
Blog gibt es dazu folgenden Eintrag:
"d. Verify that NT AUTHORITY\NETWORK SERVICE has login permissions to the
SQL Server instance and to the WSUS database. If it does not, you will need
to add it to both locations. This account should also be a member of the
webService role on the WSUS database.

i. Verify permissions on the SQL Server instance. In SQL Server Management
Studio, open the instance and select Security, then Logins. The NT
AUTHORITY\NETWORK SERVICE account should be listed as a login. If it is not,
it should be added.

ii. Verify permissions on the database. Right-click the database, select
Properties and then click Permissions. The NT AUTHORITY\NETWORK SERVICE
account should be listed as a login. If it is not, it should be added.

iii. Verify members of the webService role. Under the WSUS database, select
Roles, then right-click webService and select Properties. The NT
AUTHORITY\NETWORK SERVICE account should be listed as a member of this role.
If it is not, it should be added.
"

Ich wünsche Dir einen schönen Tag,


CU
tosc

InsideSQL.org: http://www.insidesql.de
Blog: http://www.insidesql.org/blogs/tosc

Ähnliche fragen