DPM 2010 (Domain A), Sharepoint 2010 (Domain A), SQL Server 2008 R2 (Domain B): Protection Group Problem SQL named is in wrong domain format. RRS feed

  • Question

  • Good Evening,

    So I have 3 Servers in all, with the following configurations:

    Server1: (Domain A)

    Server2: (Domain A)

    Server3: (Domain B)

    I have prepared appropriatly by installing the DPM Agent, running configuresharepoint.exe -enablesharepointprotection & ConfigureSharepoint.exe enableSPSearchProtection.

    I have prepared by installing the DPM agent to the server using the manual installation method and creating local user credentials and connecting to the agent through install > attach agent.

    In DPM all of agents are healthy so I go over to create the protection profile and I recieve the following error: DPM cannot protect your windows sharepoint services farm until you install agents on the following server: (ID: 956)

    I have already attempted creating an alias on the WFE server for and have it point to but this did not resolve my issue at all.

    Also please keep in mind that pinging is invalid as there is not a valid DNS entry of any kind, Im not even sure where this name is coming from other than some sort of a mashup. Also I am unable to domain join the SQL server to because of licensing costs.

    A resolution to this issue woudl be greatly appreciated.

    Saturday, March 10, 2012 1:58 AM

All replies

  • Couple of questions to start.

    1. Do the domains and have mutual two way trust between them?

    2. When you configured the sharepoint farm, how did you specify the SQL instance? Did you use the Fqdn of the sql server to connect to the instance?

    Regards, Deepan [This posting is provided "AS IS" with no warranties, and confers no rights.] [P.S. If the post answers your question or guides you about what you're looking for, please mark it as answered.]

    Monday, March 12, 2012 4:43 PM
  • 1. Yes, they do have a two way trust

    2. I didnt setup the sharepoint farm so I cant answer that question. If you know of a place that I can verify its configuration that would be awesome.

    Tuesday, March 13, 2012 8:00 PM
  • On the front end server can you do diskshadow list writers, dump the output to a text file. You'll find details about all the various Vss writers on the system in the text file. Please search the details about the SharePOint Services vss writer and share the first 20-30 lines. If we don't find enough info in the first few lines, you can share the whole file later. That would throw some light on what's happening.

    Regards, Deepan [This posting is provided "AS IS" with no warranties, and confers no rights.] [P.S. If the post answers your question or guides you about what you're looking for, please mark it as answered.]

    Wednesday, March 14, 2012 4:13 AM
  • Hi Deepan,

    I run into exactly the same problem with SharePoint 2013 and DPM 2012SP1. SharePoint servers run in domain a, sql 2012 in domain b. We use a SQL alias SharePoint_PROD that is configured with the fqdn of the sql server (, but DPM resolves it to when I try to configure SharePoint protection.  Is there any solution yet?

    Here's the details of the vsswriter:

     * WRITER "SharePoint Services Writer"
      - Writer ID   = {da452614-4858-5e53-a512-38aab25c61ad}
      - Writer instance ID = {6652aefc-be3f-48db-933c-5cc245c95fe1}
      - Supports restore events = TRUE
      - Writer restore conditions = VSS_WRE_ALWAYS
      - Requires reboot after restore = FALSE
      - Excluded files:
      + Component "SharePoint Services Writer:\SharePoint_PROD\PROD_SharePoint_Config"
       - Name: PROD_SharePoint_Config
       - Logical path: SharePoint_PROD
       - Full path: \SharePoint_PROD\PROD_SharePoint_Config
       - Caption: Configuration Database PROD_SharePoint_Config
       - Type: VSS_CT_DATABASE [1]
       - Is selectable: TRUE
       - Is top level: TRUE
       - Notify on backup complete: FALSE
       - Paths affected by this component:
       - Volumes affected by this component:
       - Component Dependencies:
        - Dependency to "{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}:\\SQL20\SQL20\SP2013PORTAL\PROD_SharePoint_Config"

    Thursday, October 31, 2013 10:52 AM
  • Hi,

    Same issue here with DPM 2012, is it possible to have SharePoint Protection when SQL server are in different domain ?




    Ingénieur systèmes - OPENHOST

    Si vous trouvez ma réponse utile, merci de voter ;)

    Thursday, April 24, 2014 8:30 AM