none
Backup metadata enumeration failed RRS feed

  • Question

  • Hi,

    I Installing SCDPM2012 SP1 but DPM show Warning:

     

    Affected area: Sharepoint Farm\ZEUS\ACCSP_Config
    Occurred since: 16/01/2013 11:22:21
    Description: DPM could not obtain backup metadata information for SharePoint Farm Sharepoint Farm\ZEUS\ACCSP_Config on nyx.int.accelera.com.br. If the data source is a SharePoint farm then a valid recovery point has been created. However, content databases from this recovery point can be recovered using the alternate location option only. (ID 3134)
     More information
    Recommended action: 
     If the data source is a SharePoint farm, then
    1) Ensure that "ConfigureSharePoint.exe -EnabledSharePointProtection" has been run on the front-end web server with the current SharePoint farm administrator credentials.
    2)Ensure that the SharePoint VSS writer is running on the front-end web server.
    Resolution: DPM automatically changes this alert's status to inactive 10 days after it is issued.To dismiss the alert, click below
     Inactivate

    I changed "HKLM\SOFTWARE\Microsoft\CCM\CcmEval\NotifyOnly" to TRUE


    Diego Riera | Linkedin | Twitter | diegoriera.wordpress.com

    Por favor, lembre-se de clicar em "Marcar como Resposta" no post que o ajuda, e clique em "Desmarcar como resposta" se um post marcado na verdade não responder a sua pergunta. Isto pode ser benéfico para outros membros da comunidade. Esta postagem é fornecida, sem garantias e sem direitos.

    Wednesday, January 16, 2013 1:52 PM

Answers

  • Hi,

    On the Sharepoint Web Front End (WFE) server, open a command prompt and CD to the directory: C:\Program Files\Microsoft Data Protection Manager\DPM\Temp

    Then run this find command.

    C:\Program Files\Microsoft Data Protection Manager\DPM\Temp>Find /I "System.Management.ManagementException: Invalid class"  *.errlog

    If it finds that string, open up the wsscmdletswrappercurr.errlog (or the file it found it in) and see what SQL Server was effected.

    <snip>
    02/13 20:46:29.895 31 wsscmdletswrapperfactory.cpp(235) ACTIVITY Principal name HOST/SQLBE.Domain.com
    1264 0FF0 02/13 20:46:32.364 31 WssSqlAliasHelper.cs(442) NORMAL SqlAliasResolutionDisabled = False
    1264 0FF0 02/13 20:46:36.474 31 WssSqlAliasHelper.cs(319) NORMAL connecting to [wmiNamespace root\Microsoft\SqlServer\ComputerManagement]
    1264 0FF0 02/13 20:46:36.599 31 WssSqlAliasHelper.cs(344) NORMAL WMI namespace not found
    1264 0FF0 02/13 20:46:36.599 31 WssSqlAliasHelper.cs(319) NORMAL connecting to [wmiNamespace root\Microsoft\SqlServer\ComputerManagement10]
    1264 0FF0 02/13 20:46:36.599 31 WSSCmdlets.cs(1030) WARNING Caught Exception while resolving SqlAlias [SQL02], Database [ConfigDB]
    1264 0FF0 02/13 20:46:36.615 31 WSSCmdlets.cs(1281) WARNING --------------------------------------------------
    1264 0FF0 02/13 20:46:36.615 31 WSSCmdlets.cs(1282) WARNING Exception Message =
    1264 0FF0 02/13 20:46:36.615 31 WSSCmdlets.cs(1282) WARNING The type initializer for 'WSSCmdlets.WssSqlAliasHelper' threw an exception.
    1264 0FF0 02/13 20:46:36.615 31 WSSCmdlets.cs(1283) WARNING Exception Stack =
    1264 0FF0 02/13 20:46:36.615 31 WSSCmdlets.cs(1283) WARNING at WSSCmdlets.WssSqlAliasHelper.ResolveSqlServerAliasNameEx(String aliasName, String databaseName, String& serverName, String& fullInstanceName, String& uniqueLogicalPath, Boolean& isServerNameFound)
    1264 0FF0 02/13 20:46:36.615 31 WSSCmdlets.cs(1283) WARNING at WSSCmdlets.CWSSCmdlets.ResolveSqlAliasEx(String aliasName, String databaseName, String& serverName, String& fullInstanceName, String& uniqueLogicalPath, Boolean& isServerNameFound)
    1264 0FF0 02/13 20:46:36.615 31 WSSCmdlets.cs(1284) WARNING Inner Exception =
    1264 0FF0 02/13 20:46:36.615 31 WSSCmdlets.cs(1284) WARNING System.Management.ManagementException: Invalid class
    1264 0FF0 02/13 20:46:36.615 31 WSSCmdlets.cs(1284) WARNING at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
    >snip<

    Re-register the WMI classes by running the Mofcomp command on that SQL Server.

    C:\>mofcomp "C:\Program Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof"


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    • Marked as answer by DIEGO RIERA Friday, February 22, 2013 7:32 PM
    Friday, February 22, 2013 5:43 PM
    Moderator

All replies

  • Hi,

    You need to fix WMI on the SharePoint backend SQL server.

    On the SQL server, from an administrative command prompt run the following command:

    C:\>mofcomp "C:\Program Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof"

    Then future DPM jobs should complete and not post that alert.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Friday, January 25, 2013 8:51 PM
    Moderator
  • Hi,

    This fix not solved.


    Diego Riera | Linkedin | Twitter | diegoriera.wordpress.com

    Por favor, lembre-se de clicar em "Marcar como Resposta" no post que o ajuda, e clique em "Desmarcar como resposta" se um post marcado na verdade não responder a sua pergunta. Isto pode ser benéfico para outros membros da comunidade. Esta postagem é fornecida, sem garantias e sem direitos.

    Tuesday, January 29, 2013 4:48 PM
  • HI,

    Here is a list of other possible causes:

    • SharePoint VSS Writer is in failed state
    • SharePoint VSS Writer isn’t running
    • SharePoint farm administrator don’t have SQL Permissions
    • Account used by configuresharepoint –enablesharepointprotection doesn’t have SQL Permissions
                The account used needs to be SharePoint Farm administrator and hold sysadmin role on the SQL Server that is hosting SharePoint Farm databases.
    • SQL alias is used, the alias can’t be ‘translated’ to <SQLServerName>\<InstanceName>
    • SQL alias can be translated to <SQLServerName>\<InstanceName> but SQL Browser on the SQL Server side can’t redirect that string to the port used by that SQL named instance


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Tuesday, January 29, 2013 9:07 PM
    Moderator
  • Hi,

    That did not solve. All is Ok.

    How do I do to verify the cause?


    Diego Riera | Linkedin | Twitter | diegoriera.wordpress.com

    Por favor, lembre-se de clicar em "Marcar como Resposta" no post que o ajuda, e clique em "Desmarcar como resposta" se um post marcado na verdade não responder a sua pergunta. Isto pode ser benéfico para outros membros da comunidade. Esta postagem é fornecida, sem garantias e sem direitos.


    • Edited by DIEGO RIERA Friday, February 22, 2013 3:48 PM
    Friday, February 22, 2013 3:47 PM
  • Hi,

    On the Sharepoint Web Front End (WFE) server, open a command prompt and CD to the directory: C:\Program Files\Microsoft Data Protection Manager\DPM\Temp

    Then run this find command.

    C:\Program Files\Microsoft Data Protection Manager\DPM\Temp>Find /I "System.Management.ManagementException: Invalid class"  *.errlog

    If it finds that string, open up the wsscmdletswrappercurr.errlog (or the file it found it in) and see what SQL Server was effected.

    <snip>
    02/13 20:46:29.895 31 wsscmdletswrapperfactory.cpp(235) ACTIVITY Principal name HOST/SQLBE.Domain.com
    1264 0FF0 02/13 20:46:32.364 31 WssSqlAliasHelper.cs(442) NORMAL SqlAliasResolutionDisabled = False
    1264 0FF0 02/13 20:46:36.474 31 WssSqlAliasHelper.cs(319) NORMAL connecting to [wmiNamespace root\Microsoft\SqlServer\ComputerManagement]
    1264 0FF0 02/13 20:46:36.599 31 WssSqlAliasHelper.cs(344) NORMAL WMI namespace not found
    1264 0FF0 02/13 20:46:36.599 31 WssSqlAliasHelper.cs(319) NORMAL connecting to [wmiNamespace root\Microsoft\SqlServer\ComputerManagement10]
    1264 0FF0 02/13 20:46:36.599 31 WSSCmdlets.cs(1030) WARNING Caught Exception while resolving SqlAlias [SQL02], Database [ConfigDB]
    1264 0FF0 02/13 20:46:36.615 31 WSSCmdlets.cs(1281) WARNING --------------------------------------------------
    1264 0FF0 02/13 20:46:36.615 31 WSSCmdlets.cs(1282) WARNING Exception Message =
    1264 0FF0 02/13 20:46:36.615 31 WSSCmdlets.cs(1282) WARNING The type initializer for 'WSSCmdlets.WssSqlAliasHelper' threw an exception.
    1264 0FF0 02/13 20:46:36.615 31 WSSCmdlets.cs(1283) WARNING Exception Stack =
    1264 0FF0 02/13 20:46:36.615 31 WSSCmdlets.cs(1283) WARNING at WSSCmdlets.WssSqlAliasHelper.ResolveSqlServerAliasNameEx(String aliasName, String databaseName, String& serverName, String& fullInstanceName, String& uniqueLogicalPath, Boolean& isServerNameFound)
    1264 0FF0 02/13 20:46:36.615 31 WSSCmdlets.cs(1283) WARNING at WSSCmdlets.CWSSCmdlets.ResolveSqlAliasEx(String aliasName, String databaseName, String& serverName, String& fullInstanceName, String& uniqueLogicalPath, Boolean& isServerNameFound)
    1264 0FF0 02/13 20:46:36.615 31 WSSCmdlets.cs(1284) WARNING Inner Exception =
    1264 0FF0 02/13 20:46:36.615 31 WSSCmdlets.cs(1284) WARNING System.Management.ManagementException: Invalid class
    1264 0FF0 02/13 20:46:36.615 31 WSSCmdlets.cs(1284) WARNING at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
    >snip<

    Re-register the WMI classes by running the Mofcomp command on that SQL Server.

    C:\>mofcomp "C:\Program Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof"


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    • Marked as answer by DIEGO RIERA Friday, February 22, 2013 7:32 PM
    Friday, February 22, 2013 5:43 PM
    Moderator
  • Adding the server farm account to dbcreator and securityadmin SQL server roles fixed the issue for me

    http://technet.microsoft.com/en-us/library/cc263445.aspx

    Server farm account

    • Domain user account.

    Additional permissions are automatically granted for this account on web servers and application servers that are joined to a server farm.

    This account is automatically added as a SQL Server login on the computer running SQL Server and added to the following SQL Server security roles:

    • dbcreator fixed server role

    • securityadmin fixed server role

    • db_owner fixed database role for all databases in the server farm

    • Proposed as answer by uzit Thursday, April 16, 2015 9:09 AM
    Thursday, August 8, 2013 4:19 AM