Description of the hotfix rollup package for System Center Data Protection Manager 2007: April 14, 2009

This article has been archived. It is offered "as is" and will no longer be updated.
This article describes the Microsoft System Center Data Protection Manager (DPM) 2007 issues that are fixed in the Data Protection Manager 2007 hotfix rollup package that is dated April 14, 2009.
Important The hotfix that is described here is included in the update that is described in the following Microsoft Knowledge Base article:
979970 Description of the latest hotfix rollup package for System Center Data Protection Manager 2007: March 29, 2010
We highly recommend that you install this update to resolve the problem described in this article and other DPM-related issues.

This rollup addresses the following issues:

Issue 1
If you are protecting Hyper-V servers by using both primary and secondary protection, the DPM Administrator console may crash if you try to protect additional data sources.

Issue 2
DPM fails to enumerate mailboxes when the Exchange users and the Exchange Servers are in different domains.

Issue 3
Creating or changing the disk allocation for a data source in a Protection Group may fail on a Data Protection Manager server that is running an x64-based version of Windows Server 2008. In this case, you receive the following error message:
Error 360: The operation failed due to a virtual disk service error
Error details: Unknown error (0x80042515)
Issue 4
If you select the "Recover to the original location" and "Apply security" settings of the recovery point version options when you restore a directory from backup, the NTFS file system permissions on the directory are not restored correctly.

Issue 5
When you try to protect data sources on a Windows Server 2003-based or Windows Server 2008-based cluster, the shared volumes on the cluster may be listed under the wrong resource groups.

Issue 6
If the
registry key on a protected server contains values that are longer than 260 characters or data that is longer than 8K, you receive the following error:
The replica of Volume G:\ on <server name> is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. You can recover data from existing recovery points, but new recovery points cannot be created until the replica is consistent (ID 3106) An unexpected error occurred during job execution. (ID 104 Details: More data is available (0x800700EA))
Issue 7
Restoring a Windows SharePoint Services-related content database that is detached from the server farm fails with a 0x80070003 error.

Issue 8
If Windows SharePoint Services 3.0 is configured to connect to the content database by using a Microsoft SQL Server alias and if SharePoint rollup package 957691 is installed on the SharePoint server, Data Protection Manager cannot protect the content databases. In this scenario, you receive the following error message:
This Windows SharePoint Services farm cannot be protected because DPM did not find any dependent databases and search indices to be protected. (ID: 32008)
Issue 9
SharePoint catalog generation fails with a "The number of WaitHandles must be less than or equal to 64" message.

Issue 10
The DpmDriveMappingTool.exe command-line tool cannot run in Windows Server 2008 and generates a 0x80070424 error.

Issue 11
If library sharing is enabled and the global database server is down, you cannot point to the local database using the SetSharedDpmDatabase.exe tool.

Issue 12
"Backup to tape failed" alerts disappear if the DPM Administrator console is closed and re-opened.

Issue 13
Secondary protection fails with the following error:
DPM could not start a recovery, consistency check, or initial replica creation job for <data source type> <data source name> on <server name> for following reason: (ID: 3170) The operation failed for <data source type> on <server name> because the data source is not available. (ID: 30169) DPM ID: 3|Unable to configure protection|
Issue 14
Synchronization job fails with "0x80070057" if the protected server has files or directories that are using reserved names.
More information

Update information

The following files are available for download from the Microsoft Download Center:

System Center Data Protection Manager 2007 hotfix package (32-bit and 64-bit versions)

DownloadDownload the 968579 package now.

Note The update package applies to all Data Protection Manager 2007 languages.


To apply this update, you must have Data Protection Manager 2007 Service Pack 1 installed on the computer.

Note You must install the rollup package in the following KB article for applying the rollup package of this article:
963102 Description of the hotfix rollup package for System Center Data Protection Manager 2007: February 16, 2009

Restart requirement

You must restart the Data Protection Manager server after you install this rollup package.

Update replacement information

This update does not replace any other updates.

File information

The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
For the 32-bit version
File nameFile versionFile sizeDateTimePlatform
Vssrequestorxp.dll 2.0.8836.0141,18414-Apr-200920:10x86
Wsscmdlets.dll 2.0.8836.0108,41614-Apr-200920:13x86
Wsscmdletswrapperproxy.dll 2.0.8836.018,81614-Apr-200920:10x86
Wsswriterhelperplugin.dll 2.0.8836.0207,23214-Apr-200920:10x86

For the 64-bit version
File nameFile versionFile sizeDateTimePlatform
Vssrequestorxp.dll 2.0.8836.0193,41614-Apr-200920:17x64
Wsscmdlets.dll 2.0.8836.0108,42414-Apr-200920:21x86
Wsscmdletswrapperproxy.dll 2.0.8836.019,32814-Apr-200920:17x64
Wsswriterhelperplugin.dll 2.0.8836.0268,68014-Apr-200920:17x64

Installation instructions

This Data Protection Manager 2007 rollup package consists of three separate updates. To install each update, follow these steps:
  1. Install the rollup package on the server that is running Data Protection Manager 2007 Service Pack 1. To do this, run the DataProtectionManager2007-KB968579.exe file on the server.

    Note You must restart the Data Protection Manager server after you install this rollup package.
  2. Update the remote Microsoft SQL Server installation that is hosting the DPMDB database. To do this, run the SqlPrep-KB968579.msp file on the computer that is running SQL Server.

    Note This step is not required if you are running a SQL Server DPMDB instance on the Data Protection Manager 2007 server.
  3. In the DPM Administrator Console, update the protection agents. To do this, use one of the following methods:
    • Method 1: Update the protection agents from the DPM Administrator Console
      1. Open the DPM Administrator Console.
      2. Click the Management tab, and then click the Agents tab.
      3. Select a computer from the Protected Computer list, and then click Update on the Action pane.
      4. Click Yes, and then click Update Agents.
      5. When you receive the Enter Credentials and Reboot option dialog box, enter your credentials, select the Manually restart the selected servers later option, and then click OK.

        Note You do not have to restart the computer to update the agent. This is why the Manually restart the selected servers later option was selected.
    • Method 2: Update the protection agents on the protected computers
      1. Obtain the update protection agent package from the "Data Protection Manager installation location\DPM\Agents\RA\2.0.8836.0" directory on the Data Protection Manager 2007 server.
        • x86 update
        • x64 update
        Note The DPMAgentInstaller.exe package applies to all languages.
      2. Run the appropriate DPMAgentInstaller.exe package on each protected computer.
      3. Open the DPM Administrator Console on the Data Protection Manager 2007 server.
      4. Click the Management tab, and then click the Agents tab.
      5. Select the protected computers, and then verify that the agent version is listed as 2.0.8836.0.
  4. Run the DPMManagementShell2007-KB968579.msp file.

    Note This step is not required if you are running the Data Protection Manager Management Shell on the Data Protection Manager 2007 server.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More information
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Article ID: 968579 - Last Review: 01/16/2015 03:06:43 - Revision: 5.0

Microsoft System Center Data Protection Manager 2007

  • kbnosurvey kbarchive atdownload kbexpertiseinter kbsurveynew kbbug kbqfe KB968579