Unable to select the SharePoint Portal Server SQL databases under SharePoint Farm.

Problem

Unable to select the SharePoint Portal Server SQL databases under SharePoint Farm.

Error Message

Failed to access Content
DB (SERVERNAME\SQLDATABASENAME) Logon account: System Logon Account
The directory or file was not found, or could not be accessed.


In creating a backup job to back up SharePoint database resources, the resources cannot be added to backup selections.  When trying to select them, the 'Logon Account Selection' window pops up with the message 'The directory or file was not found, or could not be accessed'.  This issue may occur with either SharePoint Portal Server 2003 (SPS) or Microsoft Office SharePoint Server 2007 (MOSS).  The SharePoint SQL databases can be selected and backed up using the SQL icon on the SQL server, but an attempt to select the SharePoint SQL databases under the SharePoint Farm icon fails with the error in Figure 1:

Figure 1


 


Viewing a debug of the Remote Agent on the Backup Exec media server and the back end SQL server will show the following:

SQL Server:

[4456] 04/23/08 08:38:44 DSEnumerator failed with -536836945: The directory or file was not found, or could not be accessed.

Backup Exec Media Server:
[4840] 04/23/08 08:38:44 ERROR: 1a Error: The specified object was not found

Solution

 
Workaround:
In some environment if SharePoint databases reside on a Microsoft SQL Server which is separate from the Microsoft SharePoint Web Server then ensure that Backup Exec Remote Agent service is running on a same NDMP port on both the servers.
 
In some environments, Backup Exec will be using an account with insufficient rights to add a required entry in the registry on the SharePoint farm server(s).  In other situations, there is a communication issue between the SharePoint web server and back end SQL server preventing the registry information from being transferred.  In both these scenarios, manually adding the entry will allow Backup Exec to enumerate and back up the SharePoint resources.
 
Warning: Incorrect use of the Windows Registry Editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry Modifications should only be carried out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and server be made prior to making any registry changes.
 
Look at the location in the registry on each of the SharePoint farm servers at the 'HKLM\Software\Symantec\Backup Exec for Windows\Backup Exec\Engine\SharePoint\Farms' key. Normally when a farm is added and browsed via the SharePoint Farms icon an entry for the farm is added in this location on both the SharePoint web server and the back end SQL server (if applicable). The entry for any given farm is a REG_SZ value name that matches the 'SQLSERVER\INSTANCE\ConfigDB_Name' for the farm, and the data contains the names of the front end web servers in parentheses - e.g. "(WEBSRVR1)". If this entry is missing, it can be added manually using the following procedure:
 
1) Open the registry editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec for Windows\Backup Exec\Engine\SharePoint\Farms
 
2) Right click in the right side pane and select New | String Value
 
3) Enter the full name of the SharePoint configuration database as the name; Example SQLSERVER\INSTANCENAME\SharePoint_Config_db then click OK.
 
NOTE: If the SQL Instance is using the default name like MSSQLSERVER for Windows 2008, then the INSTANCENAME in the middle may not be neccessary.
 
4) Double click on the newly created value name and in the 'Value Data' block enter the name of the share point web server(s) in parentheses.
 
NOTE: The web server name must be entered in parentheses or this setting will not work.
 
5) The registry entry should appear as in Figure 2 below.
 
Figure 2
 
 
 


6) Close the Registry

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)