SQL Server Performance Forum – Threads Archive
Please help troublshooting
The complete error in the event log is as follows: Event Type: ErrorEvent Source: VSS
Event Category: None
Event ID: 6013
Date: 4/30/2006
Time: 11:38:44 AM
User: N/A
Description: Sqllib error: OLEDB Error encountered calling IDBInitialize::Initialize. hr = 0x80040e4d. SQLSTATE: 42000, Native Error: 18456
Error state: 1, Severity: 14
Source: Microsoft OLE DB Provider for SQL Server ——————
Bug explorer/finder/seeker/locator
——————
that hresult is DB_SEC_E_AUTH_FAILED. looks like you have a failed login attempt.
www.elsasoft.org
If it is failed login issue, you can enable FAILEDLOGIN auditing in SSMS or you can check with profiler.
Mohammed U.
Hi, folks, You are right, this is an authentication error. Netbackup team scheduled the tape backup nightly. It seems tape backup used the Volumn shadow copying service (VSS), by default, VSS will use the local account/NT AUTHORITY to connect SQL Server. For security, we revoked this account. The weird thing is nightly tape backup succeeds every day, but the sql error log and windows event log had a series of such kind of errors. Any one here had same experiences before? we don’t want to grant the local account, also don’t want these errors. Thanks. ——————
Bug explorer/finder/seeker/locator
——————
Are you sure tape backup using VSS?
Check the VSS service account, what it is using?
If it is using NT AUTHORITY then change it different account which has the sql access…or you can disable VSS service… Mohammed U.
Try to allocate one of the fixed database role for that NT Authority account to backup the database, if security is a problem.
Satya SKJ
Microsoft SQL Server MVP
Contributing Editor & Forums Moderator
http://www.SQL-Server-Performance.Com
This posting is provided AS IS with no rights for the sake of knowledge sharing.
Folks, Thank you for your insights. I really need more information about the VSS. My company uses the Veritas NetBack, I had no idea about that tape backup.
The account for VSS is local account NT AUTHORITYSystem. Actually, this service was set to ‘manual’, not even started before. Actually I found a KBA article exactually describe this problem, http://support.microsoft.com/kb/919023/en-us But I still felt very confused,
1. VSS is only a windows component to assist the backup application, why it needs to connect SQL Instance when Veritas backed up the entire volume to tape? What’s more, It seems the account for VSS needs the SA privilege? 2. This error only happens to the SQL 2005 instance? Tape backup team also scheduled the backup for SQL 2000 instance, there are no errors. Why this error only apply to 2005 instance? ——————
Bug explorer/finder/seeker/locator
——————
http://support.microsoft.com/kb/904801
http://blogs.msdn.com/sql_protocols/archive/2005/12/19/505372.aspx Satya SKJ
Microsoft SQL Server MVP
Contributing Editor & Forums Moderator
http://www.SQL-Server-Performance.Com
This posting is provided AS IS with no rights for the sake of knowledge sharing.
]]>