Solved

Trying to resolve event ID 24583

Posted on 2009-04-06
2
5,679 Views
Last Modified: 2012-08-13
I've discovered that my SQL 2005 server is getting the following error whenever it runs a backup.

Event Type:      Error
Event Source:      SQLWRITER
Event Category:      None
Event ID:      24583
Date:            4/6/2009
Time:            1:14:50 PM
User:            N/A
Computer:      <computer name>
Description:
Sqllib error: OLEDB Error encountered calling IDBInitialize::Initialize. hr = 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: <computer name>\<database>
DBPROP_INIT_CATALOG: master
DBPROP_AUTH_INTEGRATED: SSPI

With the help of MS KB919023 http://support.microsoft.com/kb/919023 I am able to consistently replicate the issue by running the command: 'vssadmin list writers'
When I run the vssadmin command, it does not have an entry for SqlServerWriter at all.  I believe that this may be a permissions issue, and that what I need to to is explictly add the NT AUTHORITY\SYSTEM account to the SQL Server.

However... while I'm comfortable with servers, I am not comfortable with SQL 2005.  I don't know how to explictly add the NT AUTHORITY\ SYSTEM account to the SQL server.  This is also a sensitive production server, so I'm trying to tread as lightly as possible.

Does this course of action sound correct?  Can someone please explain how to add an account to SQL Server?
0
Comment
Question by:bllarson
2 Comments
 
LVL 12

Expert Comment

by:udayakumarlm
ID: 24083819
found this
Because of strict security requirements, SQL Server installations may have removed the BUILTIN\Administrators group from the SQL Server logins. If this issue occurs, you have to make sure that the NT AUTHORITY\SYSTEM account is granted access to SQL Server. To do this, you must add it as an explicit login. Additionally, because of the types of operations that the writer must perform, we recommend that you do not remove the NT AUTHORITY\SYSTEM login from the sysadmin server role.
at
http://support.microsoft.com/kb/919023
try
0
 

Accepted Solution

by:
bllarson earned 0 total points
ID: 24217365
In the end I discovered the SQL database in question had a proprietary backup solution supplied by the vendor.  The SQL database was setup in a manner so that it would be impossible to use a 3rd party solution to back it up.
0

Featured Post

Zoho SalesIQ

Hassle-free live chat software re-imagined for business growth. 2 users, always free.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this article I will describe the Backup & Restore method as one possible migration process and I will add the extra tasks needed for an upgrade when and where is applied so it will cover all.
I have a large data set and a SSIS package. How can I load this file in multi threading?
Familiarize people with the process of utilizing SQL Server functions from within Microsoft Access. Microsoft Access is a very powerful client/server development tool. One of the SQL Server objects that you can interact with from within Microsoft Ac…
This video shows how to set up a shell script to accept a positional parameter when called, pass that to a SQL script, accept the output from the statement back and then manipulate it in the Shell.

920 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

13 Experts available now in Live!

Get 1:1 Help Now