Trying to resolve event ID 24583

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?
bllarsonAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
bllarsonConnect With a Mentor Author Commented:
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
 
udaya kumar laligondlaTechnical LeadCommented:
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
All Courses

From novice to tech pro — start learning today.