You cannot protect a SharePoint Farm by using Data Protection Manager 2007 or Data Protection Manager 2010

Article translations Article translations
Article ID: 2751471 - View products that this article applies to.
Expand all | Collapse all

Symptoms

You may receive the following error message when you try to create a protection group in a Microsoft SharePoint 2007 or Microsoft SharePoint 2010 farm by using Microsoft System Center Data Protection Manager 2007 or Microsoft System Center Data Protection Manager 2010:
DPM is unable to protect your Windows Sharepoint Service farm until you install agent on the following server: Computername.domainname of the WFE. ID 956.
This issue can occur when the following conditions are true:
  • You use a named instance for the configuration and content databases for SharePoint.
  • You use SQL Aliases in SharePoint to connect to Microsoft SQL Server.
  • You installed SharePoint and SQL Server on an x64-based operating system.

Cause

There can be multiple causes of this issue:
  • DPM is not using the correct hive to check SQL aliases.
  • SharePoint does not request the correct WMI namespace to provide information about SQL aliases.

Resolution

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756 How to back up and restore the registry in Windows

Check and set registry subkeys correctly. To do this, follow these steps:
  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following registry subkey:
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MSSQLServer\Client\ConnectTo
  3. Check that you have the following string name and value:
    SQL_alias (without instance) together with the following value:
    DBMSSOCN,netbios_SQL_server\\instance
  4. Locate the following registry subkey:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectTo
  5. Check that you have the following string name and value:
    SQL_alias\instance together with the following value:
    DBMSSOCN,netbios_SQL_server\\mossbizapp
  6. Exit Registry Editor.
You can now create the Protection Group.

Example

You have to configure SharePoint by using the cliconfg.exe tool to configure the following alias, SQLAlias\instance1, to match the SQLNetbiosName\instance1.

In the registry, you must have the following subkeys:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MSSQLServer\Client\ConnectTo
REG_SZ Name: SQLAlias
Value: DBMSSOCN, SQLNetbiosName \\instance
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectTo
REG_SZ Name: SQLAlias\instance1
Value: DBMSSOCN, SQLNetbiosName \\instance

More information

For more information about how SQL uses the registry to handle the "ConnectTo" hive, see the following article:
936491 After you install a 64-bit version of SQL Server 2005 on a 64-bit version of Windows, the 32-bit entries for SQL Native Client Configuration and for SQL Server 2005 Network Configuration appear in SQL Server Configuration Manager


To correctly configure a SQL aliasing setup for both 64-bit and 32-bit aliases


64-bit SQL alias configuration

  1. Start cliconfg.exe from each WFE server in the farm.
  2. On the Alias tab, click Add.
  3. In the Server Alias text box, enter the name of the alias that you want to add.
  4. In the Server Name text box, under Connection parameters, enter the fully qualified domain name (FQDN) of the SQL Server.
  5. In the Network Libraries section, click the TCP/IP option.
  6. Click OK.


32-bit SQL alias configuration

  1. On all WFE servers, open Microsoft SQL Server Configuration Manager.

    Note The installation of SQL Server Configuration Manager is required unless it is already installed. For SharePoint 2007, install SQL 2005 Client Connectivity Tools. For SharePoint 2010, install SQL 2008 Client Connectivity Tools.
  2. From the SQL Server Configuration Manager, expand SQL Native Client 10.0 Configuration (32bit), and then click Aliases.
  3. In the panel on the right side, right-click and then select New Alias.
  4. In the Alias Name field, enter the name of the alias that is being used.
  5. In the Server field, enter the fully qualified domain name (FQDN) of the server to which the alias will resolve.


For more information about System Center Data Protection Manager, see the following article:
2543859 Unable to protect a SharePoint Farm with System Center Data Protection Manager 2010

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

Properties

Article ID: 2751471 - Last Review: November 7, 2012 - Revision: 2.0
Applies to
  • Microsoft Office SharePoint Server 2007
  • Microsoft SharePoint Server 2010
Keywords: 
KB2751471

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com