When attempting a backup of a Microsoft SQL Database the Backup Exec Remote Agent terminates on the SQL Server.

Article:TECH203118  |  Created: 2013-02-22  |  Updated: 2013-02-22  |  Article URL http://www.symantec.com/docs/TECH203118
NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.
Article Type
Technical Solution


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

Crash Dump:

bedssql2!DispErrorInfo+2c4 [r:\honshu\1798r\engine\fsys\sql2\sql2oledb.cpp @
00000000`5fabefc4 488b01 mov rax,qword ptr [rcx]

Debug Log:
[fsys\sql2]          - SQL attach called
[fsys\sql2]          -
[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]          -
[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.


Workaround: Enable TCP/IP in SQL Configuration Manager for the Database instance that is selected for backup.

Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec Corporation is committed to product quality and satisfied customers.

This issue is currently under investigation by Symantec Corporation. Pending the outcome of the investigation, this issue may be resolved by way of a patch or hotfix in current or future revisions of the software. However, this particular issue is not currently scheduled for any release. If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Symantec Sales representative or the Symantec Sales group to discuss these concerns. For information on how to contact Symantec Sales, please see http://www.symantec.com
Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.

Supplemental Materials


SQL: beremote crashes during credentials check on bedssql2 when TCP/IP is disabled in SQL Configuration Manager

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

Terms of use for this information are found in Legal Notices