During a backup or credentials check of a Microsoft SQL database, the Backup Exec Remote Agent crashes on the server hosting the SQL Databases with the errors below.
Event Log Error:
Faulting application name: beremote.exe, version: 14.0.1798.0, time stamp: 0x4f1e02d7
Faulting module name: bedssql2.dll, version: 14.0.1798.111, time stamp: 0x50ab5d54
Exception code: 0xc0000005
Fault offset: 0x000000000005efc4
Faulting process id: 0x2284
Faulting application start time: 0x01cdee90e7d45127
Faulting application path: C:\Program Files\Symantec\Backup Exec\RAWS\beremote.exe
Faulting module path: C:\Program Files\Symantec\Backup Exec\RAWS\bedssql2.dll
Report Id: a318ff7d-5a86-11e2-b9c4-000c2931d43e
bedssql2!DispErrorInfo+2c4 [r:\honshu\1798r\engine\fsys\sql2\sql2oledb.cpp @
00000000`5fabefc4 488b01 mov rax,qword ptr [rcx]
[fsys\sql2] - SQL attach called
[fsys\sql2] - >>>> The SQL Agent was passed NT Credentials for user name:
[fsys\sql2] - >>>> the agent will ignore these credentials. NT credentials
[fsys\sql2] - >>>> need to be applied at the parent server level instead.
[fsys\sql2] - >>>> Only SQL credentials should be applied to the SQL resource.
[fsys\sql2] - Attempting attach with inherited credentials
[fsys\sql2] - SQL Error GUID: 518db30
[fsys\sql2] - SQL Error Source: Microsoft OLE DB Provider for SQL Server
[fsys\sql2] - SQL Error Description: Unspecified error
This issue is caused by not having any protocols enabled in SQL Configuration Manager for the Database Instance being backed up.
A hotfix is now available for this issue in the current version(s) of the product(s) mentioned in this article. Refer to the Hotfix link under Related Documents at the end of this article to obtain the hotfix needed to resolve the issue.
Backup Exec 2014 Rev 1786 Service Pack 2 (TECH225093).
This issue is resolved in Backup Exec 2014 or later versions.
To resolve this issue and receive the new Backup Exec improvements please upgrade to the current version of Backup Exec.
NOTE: Symantec continues to focus on the current release and future releases; there are no plans to address this issue by way of a patch or hotfix in earlier versions of the software at the present time. Please contact your Symantec Sales representative or the Symantec Partner for upgrade information including upgrade eligibility to the release containing the resolution for this issue. For information on how to contact Symantec Sales, please see http://www.symantec.com.
Workaround: Enable TCP/IP in SQL Configuration Manager for the Database instance that is selected for backup.