locked
Item level restore failed for SharePoint2013 on DPM 2012 SP1 with Rollup2 RRS feed

  • Question

  • When trying to restore a document from SharePoint, DPM starts the recovery prosess but failed with error:
    object reference not set to an instance of an object..(ID 32017 Details: invalid pointer(0x80004003))

    We have 2 Web Front End servers running Server 2012 Standard and 1 SQL server running om Server 2012 with SQL2012
    ConfigureSharePoint -EnableSharePointProtection have been run only on one of the WFE servers.

    Backup is running without errors.

    Restore prosess:
    -Recover to orginale site
    -Recover without using a recovery farm
    - temp SQL (another SQL instanse on the same SQL server) Farm_admin is sysadmin
    - DB temp location ( Folder on orginal DB server) The group EVERYONE has "Full Control)
    - Folder on the web front end server (EVERYONE = Full Control

    Progress.
    Restore job starts
    - The DPM_xxxxx are generated on the temp SQL_instance
    - The .mdf and .ldf file are copied to the Temp folder under a GUID
    - Then the .mdf and .ldf files are gone
    There is an empty folder left on the web Front end server with the GUID from the job.

    The the restore job failed with error:
    DPM was unable to export the item https ://xxxxx.xxxx.xx/mysites/personal/bgrfol/Documents from  the content database xxxxx\xx\Tenant_Content_DMO.
    Exception Message = Object reference not set to an instance of an object..(ID 32017 Details: Invalid pointer (0x80004003))

    From the WssCmdletsWrapperCurr.errlog on the Web front end server:
    4F7C 6080 WARNING ASSERT: (FileName:WSSObjectModelHelper.cs; LineNumber:494)
    4F7C 6080 WARNING The parameter 'spSiteCollection' is null.
    4F7C 6080 WARNING ASSERT: (FileName:WssExportHelper.cs; LineNumber:270)
    4F7C 6080 WARNING spSite should not be null

    Hope someone can give me a solution.

    Tuesday, April 30, 2013 11:36 AM

All replies

  • Hi

    It looks like dpm has a problem extracting the document from the content database. You can try to manually to DPM's job and check whether the document is indeed in the database:

    Recover the full content database files to a temp folder on the sql server

    Attach the database to the sql server using sql server management studio, and using a temporary name

    get the contents of this db from a sharepoint perspective, without attaching the db to sharepoint. from a sharepoint powershell, run

    $db=Get-SPContentDatabase -ConnectAsUnattachedDatabase -DatabaseName <DatabaseName> -DatabaseServer <DatabaseServer>

    $db.sites|select url

    , and check that your site collection is there. (it should). If it is not, then that is your problem. look for the real db that is containing your site. can you post the result of this check?

    Friday, May 10, 2013 10:26 AM
  • Roberto is spot on..at least in my case.

    I ran into a similar issue and it was because all SharePoint content databases were in compatibility range because of SharePoint Security patches being pushed and the SharePoint Configuration Wizard was not ran after. Check in Central Admin > Upgrade and Migration > Review Database Status 


    Regards,

    Andrew J Billings

    Portal Systems Engineer//MCSA,MCSE

    Blog: http://www.andrewjbillings.com  Twitter:   LinkedIn:   

    Wednesday, October 21, 2015 4:31 PM