Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Trying to resolve event ID 24583

Posted on 2009-04-06
2
Medium Priority
?
6,657 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:udaya kumar laligondla
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

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

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

Ever needed a SQL 2008 Database replicated/mirrored/log shipped on another server but you can't take the downtime inflicted by initial snapshot or disconnect while T-logs are restored or mirror applied? You can use SQL Server Initialize from Backup…
This article shows gives you an overview on SQL Server 2016 row level security. You will also get to know the usages of row-level-security and how it works
Using examples as well as descriptions, and references to Books Online, show the documentation available for date manipulation functions and by using a select few of these functions, show how date based data can be manipulated with these functions.
Viewers will learn how to use the INSERT statement to insert data into their tables. It will also introduce the NULL statement, to show them what happens when no value is giving for any given column.

824 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