September 16, 2008 at 4:33 pm
I have an "inherited server", by the looks it has a LIvestate Recovery running on it and when NT\Authority account attempts to log into sql server...this happens (below).
SQLWriter looks like a non-critical component so I'm now too worried, The service runs under the local system account and has been started the sql server NT Authority account has been removed for secuity reasons.
has anyone seen this before? and could anyone add anything?
/*--------------------------------------------------------------------
Event Type:Error
Event Source:SQLWRITER
Event Category:None
Event ID:24583
Date:17/09/2008
Time:9:20:24 a.m.
User:N/A
Computer:
Description:
The description for Event ID ( 24583 ) in Source ( SQLWRITER ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: IDBInitialize::Initialize, 0x80040e4d, SQLSTATE: 28000, Native Error: 18456
Error state: 1, Severity: 14
Source: Microsoft SQL Native Client
Error message: Login failed for user 'NT AUTHORITY\SYSTEM'.
DBPROP_INIT_DATASOURCE:
DBPROP_INIT_CATALOG: master
DBPROP_AUTH_INTEGRATED: SSPI
.
Data:
0000: 53 51 4c 43 4f 4e 4e 43 SQLCONNC
0008: 36 30 36 00 00 00 00 00 606.....
0010: 53 51 4c 43 4f 4e 4e 43 SQLCONNC
0018: 34 33 38 00 00 00 00 00 438.....
November 6, 2008 at 9:32 pm
August 30, 2011 at 7:34 am
http://support.microsoft.com/kb/919023
This post was a wild goose chase.
The KB article has NOTHING to do with the actually error noted in this request for help. It has the same eventID, but the similarities stop at that. The KB article focuses on OLEDB connectivity issues, not missing components.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply