none
DPM restoration error for SharePoint RRS feed

  • Question

  • Hi,

    We've been running into the following error when restoring a SharePoint
    site. The problem occurs on the sharepoint recovery server and the DPM Error
    in the Job Log is as below:
    "DPM was unable to attach the content database to the recovery farm.
    Exception Message = DPM_115a4e5d_5ea4_4970_b6fa_491f3541dfred on
    AUNSTSTDPMV02 contains user-defined schema. Database mustb e empty befroe
    they can be used. Delete all of the tables, stored procedures ans other
    objects or use a different database. (ID 32002)"

    The WssCmdletwrapper log from the Recovery Farm Server also has thew
    following output.

    ACTIVITY Principal name HOST/AUNSTSTDPMV02.domain.com@domain.com
    NORMAL Attaching Content Database DPM_115a4e5d_5ea4_4970_b6fa_491f3541dfed
    of SQL Instance AUNSTSTDPMV02 to Farm
    WARNING Caught Exception while trying to attach the Content Database
    [AUNSTSTDPMV02\DPM_115a4e5d_5ea4_4970_b6fa_491f3541dfed to Web Application
    [DPMRecoveryWebApplication].
    WARNING --------------------------------------------------
    WARNING Exception Message =
    WARNING DPM_115a4e5d_5ea4_4970_b6fa_491f3541dfed on AUNSTSTDPMV02 contains
    user-defined schema. Databases must be empty before they can be used.
    Delete all of the tables, stored procedures and other objects or use a
    different database.
    WARNING Exception Stack =
    WARNING at
    Microsoft.SharePoint.Administration.SPDatabase.EnsureSqlDatabase(SqlConnectionStringBuilder connectionString)
    WARNING at
    Microsoft.SharePoint.Administration.SPDatabase.SetDatabaseOptions(SqlConnectionStringBuilder connectionString, Dictionary`2 options, Boolean wYukon)
    WARNING at
    Microsoft.SharePoint.Administration.SPDatabase.Provision(SqlConnectionStringBuilder
    connectionString, SqlFile sqlFileId, String sqlSignaturePath, Dictionary`2
    options)
    WARNING at
    Microsoft.SharePoint.Administration.SPContentDatabase.Provision()
    WARNING at
    Microsoft.SharePoint.Administration.SPContentDatabaseCollection.Add(SPContentDatabase
    database, Boolean provision, Boolean allowUpgrade, Boolean flushChangeLog)
    WARNING at
    Microsoft.SharePoint.Administration.SPContentDatabaseCollection.Add(Guid
    newDatabaseId, String strDatabaseServer, String strDatabaseName, String
    strDatabaseUsername, String strDatabasePassword, Int32 warningSiteCount,
    Int32 maximumSiteCount, Int32 status, Boolean provision, Boolean
    allowUpgrade, Boolean flushChangeLog, Boolean bSetDbId)
    WARNING at
    Microsoft.SharePoint.Administration.SPContentDatabaseCollection.Add(String
    strDatabaseServer, String strDatabaseName, String strDatabaseUsername, String
    strDatabasePassword, Int32 warningSiteCount, Int32 maximumSiteCount, Int32
    status)
    WARNING at WSSCmdlets.CWSSCmdlets.AttachContentDatabase(String
    sqlInstanceName, String databaseName, Int32& hr, String& exceptionMessage)
    WARNING Inner Exception =
    WARNING Exception String =
    WARNING Microsoft.SharePoint.Administration.SPUncleanDatabaseException:
    DPM_115a4e5d_5ea4_4970_b6fa_491f3541dfed on AUNSTSTDPMV02 contains
    user-defined schema. Databases must be empty before they can be used.
    Delete all of the tables, stored procedures and other objects or use a
    different database.
    WARNING at
    Microsoft.SharePoint.Administration.SPDatabase.EnsureSqlDatabase(SqlConnectionStringBuilder connectionString)
    WARNING at
    Microsoft.SharePoint.Administration.SPDatabase.SetDatabaseOptions(SqlConnectionStringBuilder connectionString, Dictionary`2 options, Boolean wYukon)
    WARNING at
    Microsoft.SharePoint.Administration.SPDatabase.Provision(SqlConnectionStringBuilder
    connectionString, SqlFile sqlFileId, String sqlSignaturePath, Dictionary`2
    options)
    WARNING at
    Microsoft.SharePoint.Administration.SPContentDatabase.Provision()
    WARNING at
    Microsoft.SharePoint.Administration.SPContentDatabaseCollection.Add(SPContentDatabase
    database, Boolean provision, Boolean allowUpgrade, Boolean flushChangeLog)
    WARNING at
    Microsoft.SharePoint.Administration.SPContentDatabaseCollection.Add(Guid
    newDatabaseId, String strDatabaseServer, String strDatabaseName, String
    strDatabaseUsername, String strDatabasePassword, Int32 warningSiteCount,
    Int32 maximumSiteCount, Int32 status, Boolean provision, Boolean
    allowUpgrade, Boolean flushChangeLog, Boolean bSetDbId)
    WARNING at
    Microsoft.SharePoint.Administration.SPContentDatabaseCollection.Add(String
    strDatabaseServer, String strDatabaseName, String strDatabaseUsername, String
    strDatabasePassword, Int32 warningSiteCount, Int32 maximumSiteCount, Int32
    status)
    WARNING at WSSCmdlets.CWSSCmdlets.AttachContentDatabase(String
    sqlInstanceName, String databaseName, Int32& hr, String& exceptionMessage)
    WARNING --------------------------------------------------

    we have done the following

    make sure Production server and retoration server are off having same OS version

    make sure firewall is off

    run the ConfigureSharePoint.exe with relevant parameters .

    Below i have mentioned the WSSCmdLedwrappercurr log initial lines

    02EC 0360 03/30 06:34:00.287 31 wsscmdletswrapperfactory.cpp(220)   ACTIVITY Principal name XXXXXXXXX
    02EC 0A8C 03/30 06:34:30.867 31 WSSCmdlets.cs(1067)   NORMAL Sql Instance Name = AUNSTSTDPMV02
    02EC 0A8C 03/30 06:34:30.867 31 WssSqlAliasHelper.cs(442)   NORMAL SqlAliasResolutionDisabled = False
    02EC 0A8C 03/30 06:34:31.535 31 WssSqlAliasHelper.cs(319)   NORMAL connecting to [wmiNamespace root\Microsoft\SqlServer\ComputerManagement]
    02EC 0A8C 03/30 06:34:31.551 31 WssSqlAliasHelper.cs(319)   NORMAL connecting to [wmiNamespace root\Microsoft\SqlServer\ComputerManagement10]
    02EC 0A8C 03/30 06:34:31.582 31 WssSqlAliasHelper.cs(344)   NORMAL WMI namespace not found
    02EC 0A8C 03/30 06:34:31.582 31 WssSqlAliasHelper.cs(495)   NORMAL count of the list of all aliases: 0
    02EC 0CDC 03/30 06:34:31.582 31 WssSqlAliasHelper.cs(179)   NORMAL Unable to get the server name for the [SqlAlias: AUNSTSTDPMV02]
    02EC 0A8C 03/30 06:34:31.582 31 WssSqlAliasHelper.cs(179)   NORMAL Unable to get the server name for the [SqlAlias: AUNSTSTDPMV02]
    02EC 01AC 03/30 06:34:31.582 31 WSSCmdlets.cs(1067)   NORMAL Sql Instance Name = AUNSTSTDPMV02
    02EC 01AC 03/30 06:34:31.582 31 WssSqlAliasHelper.cs(375)   NORMAL Getting SPDatabase for [databaseName: TRANSNET_REC_CONFIG_MOSS], [instanceName: AUNSTSTDPMV02]
    02EC 01AC 03/30 06:34:31.582 31 WssSqlAliasHelper.cs(406)   NORMAL Found corresponding SPDatabase object
    02EC 01AC 03/30 06:34:31.582 31 WssSqlAliasHelper.cs(375)   NORMAL Getting SPDatabase for [databaseName: TRANSNET_REC_CONFIG_MOSS], [instanceName: AUNSTSTDPMV02]
    02EC 01AC 03/30 06:34:31.582 31 WssSqlAliasHelper.cs(406)   NORMAL Found corresponding SPDatabase object
    02EC 0A8C 03/30 06:34:31.597 31 WssSqlAliasHelper.cs(179)   NORMAL Unable to get the server name for the [SqlAlias: AUNSTSTDPMV02]

     

    is this could be that , WMI name space not exist or corrupted ?

    Any ideas of how to resolve this .appreciate the prompt response.

    Regards

    • Moved by Praveen D [MSFT] Monday, July 19, 2010 7:12 AM Moving to DPM SharePoint Protection Forum (From:Data Protection Manager)
    Tuesday, June 29, 2010 11:52 PM

All replies

  • Hey,

    Is your recovery farm exactly the same as your production farm?  I'm not a sharepoint expert but it seems to me that you have customizations in your production farm which are not known by the recovery farm, causing it to give the schema error.

    Just my thoughts here

    Cheers,

    Mike Resseler


    Visit System Center User Group Belgium @ http://scug.be and http://scug.be/blogs/scdpm
    Wednesday, June 30, 2010 6:56 AM
    Moderator
  • I'm curious about a few items here.

    First, is this DPM 2007?  If so, what version (something like 2.0.8861.0)?  Is this SharePoint 2007 or SharePoint 2010?

    Are there any additional errors or detail codes with the error - most notably a hex code 0x8........)?

    There was a known issue with this that was fixed with SP1 for DPM 2007

    949783 After you use System Center Data Protection Manager 2007 to back up a SharePoint site, file recovery operations fail
    http://support.microsoft.com/default.aspx?scid=kb;EN-US;949783

    Outside of that, I think Mike is probably onto the most likely cause of this.  The recovery farm needs to have all of the same updates installed to it that the original farm has.  This would include any custom templates you may have installed on the original farm.

    ·         Microsoft Office SharePoint Server (MOSS) 2007 should be the same version number (or higher) as the original SharePoint Production Farm. Verify the same SharePoint service pack and SharePoint patches are installed. To verify the current version of the SharePoint Production Farm and the Recovery Farm you can open Programs/Administrative Tools/SharePoint 3.0 Central Administration console, on the Central Administration Home.  Click the Operations tab in the top left corner.  Click “Servers in Farm” under Topology and Services.  The version number should be listed for each Server in the Farm. You will notice a version similar to 12.0.0.6510. This particular version is the latest SP2 for WSS/MOSS + June CU updates. FYI – the build number you see in Central Admin is pulled from the WSS core file owssvr.dll.  FYI – SPS Reports gathers the DLL versions from WSS & MOSS if you need to compare against the different servers in the farm.

    ·         Custom Templates - Identical features and templates need to match. Many SharePoint installations use custom templates and custom code to enhance and make the user experience fit the work environment better. Any sites created with these custom templates and configurations that have to be manually implemented on a SharePoint server should also be implemented on the recovery farm. When restoring data, SharePoint will block the restore if the templates and other key format characteristics do not match up. Some custom templates can simply be copied to the Recovery farm at the location mentioned below, but other custom templates may have an installer. The SharePoint administrator will need to verify the correct method for installing each of the custom templates.

     

    Ø  The default path for custom site definitions and our out of the box site templates reside at “C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE”.

    Ø  Custom site templates normally reside at this path within the 12\TEMPLATE\SiteTemplates directory.

    Ø  Default log directory - C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\LOGS

    v  3 types of files exist within this directory – the first is upgrade.log which will show any successes or failures during the last upgrade attempt. (service pack / rollup/ update)

    v  The second is the pscdiagnostics type file which logs information every time the psconfig wizard is run.

    v  The third is the actual ULS (universal logging service) log which is named in the format of Server Name / Date.

     

     

     


    Thanks, Chris Bu - MSFT This posting is provided "AS IS" with no warranties, and confers no rights
    Thursday, July 1, 2010 2:56 PM
    Moderator