Snapshot provider error occurs when attempting to backup SQL Database

Article:TECH194053  |  Created: 2012-07-30  |  Updated: 2013-12-19  |  Article URL http://www.symantec.com/docs/TECH194053
Article Type
Technical Solution


Issue



When backing up a SQL database the job fails with the error below, even though test credentials are successful:


Error



V-79-57344-893

Snapshot provider error (0xE000037D): An attempt to connect to SQL Server has failed. The logon account may have invalid credentials, or the logon account may have been applied to the wrong resource.

 


Cause



This occurs because the logon credentials being used are applied at the database level and not the server level.

FROM BEREMOTE LOGS ON MEDIA SERVER:

BEREMOTE: [07/27/12 10:59:12] [3716]     2012-07-27T10:59:10.668 [fsys\sql2]          - SQL attach called
BEREMOTE: [07/27/12 10:59:12] [3716]     2012-07-27T10:59:10.668 [fsys\sql2]          -
BEREMOTE: [07/27/12 10:59:12] [3716]     2012-07-27T10:59:10.668 [fsys\sql2]          -  >>>> The SQL Agent was passed NT Credentials for user name: domain\username'
BEREMOTE: [07/27/12 10:59:12] [3716]     2012-07-27T10:59:10.669 [fsys\sql2]          -  >>>> the agent will ignore these credentials.  NT credentials
BEREMOTE: [07/27/12 10:59:12] [3716]     2012-07-27T10:59:10.669 [fsys\sql2]          -  >>>> need to be applied at the parent server level instead.
BEREMOTE: [07/27/12 10:59:12] [3716]     2012-07-27T10:59:10.669 [fsys\sql2]          -  >>>> Only SQL credentials should be applied to the SQL resource.


Solution



Change the logon account used at the parent server level to the account being used to backup the SQL database if other than the System Logon Account.

 


Supplemental Materials

SourceUMI
ValueV-79-57344-893
Description

Snapshot provider error (0xE000037D): An attempt to connect to SQL Server has failed. The logon account may have invalid credentials, or the logon account may have been applied to the wrong resource.

 



Article URL http://www.symantec.com/docs/TECH194053


Terms of use for this information are found in Legal Notices