Unable to backup the SharePoint Portal Server SQL databases under SharePoint Farm.Failed to access Content DB (SERVERNAME\SQLDATABASENAME) Logon account: System Logon Account The directory or file was not found, or could not be accessed

Problem

Unable to backup the SharePoint Portal Server SQL databases under SharePoint Farm.Failed to access Content DB (SERVERNAME\SQLDATABASENAME) Logon account: System Logon Account The directory or file was not found, or could not be accessed

Error Message

Beremote of Media Server:

[4720] 2013-06-25T13:39:48.252 [ndmp\ndmpcomm]      - ERROR: 1a Error: The
specified object was not found
[4720] 2013-06-25T13:39:48.253 [dsss]               + rpcdssession.cpp (1101):
[4720] 2013-06-25T13:39:48.253 [dsss]               | ERROR: Begin failed!

Beremote of the SPS server:

[7784] 2013-06-20T12:23:43.235 [ndmp\ndmpsrvr]      | Enumerating: Device
name: 'Server Farm 1 (TEST1,TEST2)'; Path: ''.
[7784] 2013-06-20T12:23:43.235 [beutil]             - Input Error (e000fe23)
for Type: (43)
[7784] 2013-06-20T12:23:43.235 [fsys\ev]            - EVM_ResolveDeviceName:
Function Enter
[7784] 2013-06-20T12:23:43.235 [beutil]             - ApplyRegExp(): Invalid
pattern. InputString (Server Farm 1 (TEST1,TEST2)). RegEx (EVM::\\\\{.*?}
\\{.*}).
[7784] 2013-06-20T12:23:43.235 [fsys\ev]            - EVM_ResolveDeviceName:
Invalid device name (Server Farm 1 (TEST1,TEST2)). Parsing Failed.
[7784] 2013-06-20T12:23:43.235 [fsys\ev]            - EVM_ResolveDeviceName:
Function Exit
[7784] 2013-06-20T12:23:43.235 [fsys\ntfs]          - Not valid device name :
Server Farm 1 (TEST1,TEST2)
[7784] 2013-06-20T12:23:43.235 [dsss]               + dsserver.cpp (908):
[7784] 2013-06-20T12:23:43.235 [dsss]               | ERROR: resolve failed:
0xe00084af

SQL SERVER:

DSEnumerator failed with -536836945: The directory or file was not found, or
could not be accessed.

 

Cause

This issue will come up if hosts file on any of the SQL node has an entry for SQL cluster name pointing to IP address of the physical node

Solution

The issue is now fixed in Backup Exec Service Pack 2( www.symantec.com/docs/TECH203155)


Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)