System Center 2012 Data Protection Manager SP1 error codes

Summary
This article describes the error codes that may occur in Microsoft System Center 2012 Data Protection Manager.

Note Some errors have additional troubleshooting information.


Contents


More information

Error codes 0-100

Error CodeMessageAdditional Information
7 Unable to connect to the Active Directory Domain Services database.Make sure that the DPM server is a member of a domain and that a domain controller
11 DPM cannot browse <ServerName> because the host is unreachable. Verify that <ServerName> is online and is remotely accessible from the DPM server. If a firewall is enabled on <ServerName>, verify that it is not blocking requests from the DPM server.
12 DPM cannot browse <ServerName> because access was denied. Verify that the computer that is running DPM has DCOM launch and access permissions for <ServerName> and that the system time on the DPM server and <ServerName> is synchronized with the system time on the domain controller.
13 DPM cannot browse <ServerName> because the protection agent is not responding. Check the recent records from the DPMRA source in the Application log on <ServerName> to find out why the agent failed to respond.
  1. Verify that the DPM server is remotely accessible from <ServerName>.
  2. If a firewall is enabled on the DPM server, verify that it is not blocking requests from <ServerName>.
  3. Restart the DPM Protection Agent (DPMRA) service on <ServerName>. If the service does not start, reinstall the protection agent.
14 DPM cannot browse <ServerName> because of a communication error between DPM and the protection agent on the computer.
  1. Verify that <ServerName> is remotely accessible from the DPM server.
  2. If a firewall is enabled on <ServerName>, verify that it is not blocking requests from the DPM server.
  3. Restart the DPM Protection Agent (DPMRA) service on <ServerName>. If the service does not start, reinstall the protection agent.
15 DPM cannot browse <ServerName> because a protection agent is not installed on <ServerName>or the computer is restarting. Install the protection agent.
16 DPM cannot access the path <FileName> because part of the path has been deleted or renamed. Check the path, and then enter it again.
30 DPM cannot contact <ServerName> until you complete the protection agent installation by restarting the computer.Restart the server, and then try the operation again.
31 DPM cannot browse <ServerName> because the host is unreachable.
  1. Make sure that <ServerName> is online and is remotely accessible from the DPM server.
  2. If a firewall is enabled on <ServerName>, make sure that it is not blocking requests from the DPM server.
32 DPM cannot browse <ServerName> because access is denied. On the Agents tab, in the Management task area, check the status of the agent. Also, verify that the system times on the DPM server and the protected computer are synchronized with the system time on the domain controller.
33 DPM cannot browse <ServerName> because the agent is not responding. If you just installed an agent on <ServerName>, the computer might be restarting. Wait a few minutes after Windows starts for the agent to become available. Otherwise, to troubleshoot this error, follow these steps:
  1. Check recent records from the DPMRA source in the Application Event Log on < ServerName> to find out why the agent failed to respond.
  2. Make sure that the DPM server is remotely accessible from <ServerName>.
  3. If a firewall is enabled on the DPM server, make sure that it is not blocking requests from <ServerName>.
  4. Restart the DPM Protection Agent service on <ServerName>. If the service does not start, reinstall the protection agent.
34 DPM cannot browse <ServerName> because of a communication error with the agent. If you just installed an agent on <ServerName>, the computer might be restarting. Wait a few minutes after Windows starts for the agent to become available. Otherwise, to troubleshoot this error, do the following:
  1. Make sure that the DPM server is remotely accessible from <ServerName>.
  2. If a firewall is enabled on the DPM server, make sure that it is not blocking requests from <ServerName>.
  3. Restart the DPM Protection Agent service on <ServerName>. If the service does not start, reinstall the protection agent.
35 DPM cannot browse <ServerName>, either because no agent is installed on <ServerName> or because the computer is rebooting. Install the protection agent.
36 DPM cannot access the path <Component> because part of the path has been deleted or renamed. Check the path, and then enter it again.
37 DPM cannot access <FileName> because an element has been exclusively locked by another process.Try the selection later or check to see if the object is locked by another process.
38 DPM is unable to enumerate contents in<Component> on the protected computer <ServerName>. Recycle Bin, System Volume Information folder, non-NTFS volumes, DFS links, CDs, Quorum Disk (for cluster) and other removable media cannot be protected.None.
39 DPM failed to access the path<FileName>. Verify the path exists and is accessible.
41 DPM failed to communicate with<ServerName> because the computer is unreachable.
  1. Make sure that <ServerName> is online and remotely accessible from the DPM server.
  2. If a firewall is enabled on <ServerName>, make sure that it is not blocking requests from the DPM server.
  3. If you are using a backup LAN, make sure that the backup LAN settings are valid.
  4. If you are using clustered remote SMB storage, you may see this error when a backup job tries to start just after the primary cluster owner is switched. If this is the case, wait for some time and retry the operation.
42 DPM failed to communicate with the protection agent on<ServerName> because access is denied.
  1. Verify that the DPM server has DCOM launch and access permissions for <ServerName>and that the system time on the DPM server and the protected computer is synchronized with the system time on the domain controller.
  2. If this computer does not have to be protected any longer, you may want to remove the record for this computer from the database. To remove the record, in the Management task area, on the Agents tab, select the computer name. In the Details pane, click Remove Record.
  3. Make sure that your domain controller can be reached from the DPM server and the protected computer.
  4. If you are still having communication issues between DPM and the protected computer, review the event log on the DPM server and the protected computer for events related to communication issues.
43 DPM failed to communicate with the protection agent on<ServerName> because the agent is not responding.
  1. Check recent records from the DPMRA source in the Application Event log on < ServerName> to find out why the agent failed to respond.
  2. Make sure that the DPM server is remotely accessible from <ServerName>.
  3. If a firewall is enabled on the DPM server, make sure that it is not blocking requests from<ServerName>.
  4. Restart the DPM Protection Agent service on <ServerName>. If the service does not start, reinstall the protection agent.

If the steps above do not resolve the issue, please see the following KB article for additional troubleshooting steps:

3082409 - Troubleshooting Error ID 43 in System Center Data Protection Manager (https://support.microsoft.com/en-us/kb/30382409)
45 DPM failed to communicate with the protection agent on<ServerName> because the agent is not installed or the computer is restarting.Install the protection agent. If the computer is in the process of restarting, allow some time for the computer to come online.
46 DPM failed to perform the operation because too many objects are selected. Select fewer objects, and then retry the operation.
  • If you are trying to protect a large number of data sources on a volume, consider protecting the whole volume instead of individual data sources.
  • If you are trying to recover a large number of folders or files from a volume, consider recovering the parent folder, or divide the recovery into multiple operations.
47 Some components of the protection agent on<PSServerName> were not installed or configured properly.
  1. Verify that the targeted computer <PSServerName> is not running an unsupported version of the operating system.
  2. Restart the computer <PSServerName>. If the problem persists, on <PSServerName>, uninstall the DPM protection agent by using Add or Remove Programs. Then, on the DPM server, in the Management task area, on the Agents tab, reinstall the protection agent on<PSServerName>.
48 <ServerName> needs to be restarted. This might be because the computer has not been restarted since the protection agent was installed.Restart the server. If you have protected data on this server, synchronize the data by performing a consistency check after the restart.
49 The protection agent timed out while trying to access the file<FileName> for volume <PSVolumeName> on <PSServerName>. Make sure that the file is accessible. Synchronize the data with a consistency check.
50 The DPM protection agent on<PSServerName> failed to perform a consistency check for file <FileName>on volume <PSVolumeName>. Make sure that the file is available and rerun the consistency check.
51 Root directories were added to or removed from protection for volume<PSVolumeName> on <PSServerName>. No action required.
52 The DPM service was unable to communicate with the protection agent on<ServerName>. Restart the DPM Replication Agent (DPMRA) service on<ServerName>.
53 DPM failed to communicate with<ServerName> because of a communication error with the protection agent.
  1. Make sure that <ServerName> is remotely accessible from the DPM server.
  2. If a firewall is enabled on <ServerName>, make sure that it is not blocking requests from the DPM server.
  3. Restart the DPM Replication Agent service on <ServerName>. If the service does not start, reinstall the protection agent.
55 The protected volume<VolumeName> on <ServerName> could not be accessed. The volume might have been removed or dismounted, or another process might be exclusively using it.To resolve this error, make sure that volume<VolumeName> can be accessed.

If a new volume <VolumeName> was created to replace a previously protected volume with the same name, and you want to protect the new volume, you must remove the original volume from its protection group, and then add the new volume to the protection group. You can retain the replica for future recoveries.

If you no longer want to protect any data sources on the computer, you can uninstall the protection agent from the computer. If the volume has been permanently removed or deleted, remove the volume from its protection group (optionally choosing to retain the replica for future recoveries), and then inactivate the alert by clicking Inactive alert.
56 DPM failed to move data because it did not receive the completion status from the protection agent.Retry the operation.
57 DPM cannot continue to protect the data on<TargetServerName> because there is not enough disk space available on one or more of its volumes.Free up disk space and retry.
58 DPM is out of disk space for the replica.Make sure that there are no pending disk threshold alerts active for this data source, and then rerun the job. DPM might have automatically grown the volume and resolved the alerts.
59 DPM was used to initiate the recovery for<DatasourceType><DatasourceName> on <ServerName>. After this operation is complete, DPM must synchronize its replica with the data recovered on the protected computer in order to continue protection. The replica is being marked inconsistent to enable DPM to run a consistency check to synchronize the replica. No action required.
60 The protection agent on<ServerName> was temporarily unable to respond because it was in an unexpected state.Retry the operation. If the problem remains it may be because there is an open file on the server being protected. In this scenario there are three potential workarounds:

1. Stop the Application and then manually run the DPM replica or Consistency Checks.

2. Develop a process that copies the data to be protected to a separate folder, then configure DPM to protect that folder.

3. Configure pre and post backup scripts on the protected server that utilize .CMD batch files to stop the application that is holding the file open, then let the DPM backup run, then restart the application after the backup is complete. Be aware that this option means that the application will be unavailable during the time that the backup is running. For more information on pre and post scripting see https://technet.microsoft.com/en-us/library/bb808870.aspx.
62 Cannot find the volume<VolumeName> on the computer running DPM. Make sure that the storage pool disk is accessible. If it is not, reallocate disk space, and then re-protect the data.
63 DPM cannot protect<FileName> because there is no virtual name configured for the Resource Group to which the file belongs.Make sure that the Resource Group has a virtual name configured. Also, check that the dependencies between cluster resources are configured correctly.
64 Volume <VolumeName> is offline on the DPM server. On the DPM server, open Server Manager, expand Diagnostics, expand Event Viewer, expand Windows Logs, and then take the recommended action in the Application log.
65 The DPM service was unable to communicate with the protection agent on<ServerName>. Restart the DPM Replication Agent service on the server.
77 The consistency check job failed due to an internal error.Rerun the consistency check job.
78 DPM is unable to continue protection for data sources on the protected computer<ServerName> because DPM has detected an incompatible filter installed on this computer.To resolve, see Incompatible filter driver errors.
91 The replica of <DatasourceType><DatasourceName> on <ServerName> is not consistent with the protected data source.No action required.
92 Cannot access volume on the replica of <DatasourceType><DatasourceName> on <ServerName>. Stop protection of<DatasourceName>, and then reconfigure protection for this data source.
93 The replica of <DatasourceType><DatasourceName> on <ServerName> is being created. If the replica creation is scheduled for a later time, no action is required. If you have chosen to manually create the replica, copy the data, and then synchronize with consistency check.
94 The data source <DatasourceType><DatasourceName> on <ServerName> is no longer protected, and DPM no longer has a replica of it. The replica was probably deleted because the Stop Protection without retaining replica task was run for this data source.Wait for the replica creation operation to complete. Then, retry the job. No action is required. Wait for the DPM database to be updated to reflect that this data source is no longer protected.
95 Job failure on replica of<DatasourceName> on <ServerName> was caused by an ongoing synchronization operation.Cancel the ongoing synchronization operation, or wait for it to complete. Then retry the operation.
96 Job failure on replica of<DatasourceName> on <ServerName> was caused by an ongoing replica creation.Cancel the consistency check operation, or wait for it to complete. Then retry the job.
97 Job failure on replica of<DatasourceName> on <ServerName> was caused by an ongoing consistency check operation.Cancel the consistency check operation, or wait for it to complete. Then retry the job.
98 Job failure on replica of<DatasourceName> on <ServerName> was caused by a recovery operation currently in progress.Cancel the recovery operation, or wait for it to complete. Then retry the job.
99 Job failure on replica of<DatasourceName> on <ServerName> was caused by an ongoing stop-protection job.Cancel the stop-protection operation, or wait for it to complete. Then retry the job.
100 Job failure on replica of<DatasourceName> on <ServerName> was caused by an ongoing recovery point creation.Cancel the recovery point operation, or wait for it to complete. Then retry the operation.

back to Contents

Error codes 101-200

Error CodeMessageAdditional Information
101The job failed because the replica for this data source is being deleted, probably because the Stop Protection without retaining replica task was run for this data source.No action is required. Wait for the DPM database to update to reflect that this data source is no longer protected.
104 An unexpected error occurred while the job was running.

or

Unknown error (0x80041010)
This error can appear if you are trying to protect a SQL Server database that has files on a remote share. This is not supported by DPM.

This can also occur if you are attempting to backup a Hyper-V VM on a host running Windows Server 2012 R2. DPM 2012 SP1 does not support this scenario. To backup a Hyper-V VM on a host running Windows Server 2012 R2 or later, upgrade DPM 2012 SP1 to DPM 2012 R2.
107 The DPM protection agent is no longer tracking changes on<PSVolumeName> on <PSServerName>.
  1. Check recent records from the FSRecord source in the System Event log on <PSServerName> to find out why the problem occurred.
  2. Synchronize with consistency check.
109 The replica on the DPM server for<DatasourceType><DatasourceName> on <ServerName> is inconsistent with the protected data source. Changes cannot be applied.No action required.
111 <ServerName>has been restarted without being properly shut down. No action required.
112 Changes for <DatasourceType><DatasourceName> on <ServerName> cannot be applied to<FileName>. No action required.
113 Job failure for <DatasourceType><DatasourceName> on <ServerName> was caused by an ongoing conflicting operation on<ServerName>. Cancel the ongoing operation, or wait for it to complete. Then retry the job.
114 Job failure on <DatasourceName> on <ServerName> was caused by ongoing backup operation.Cancel the operation, or wait for it to complete. Then retry the operation.
115 Job failure on <DatasourceName> on <ServerName> was caused by ongoing recovery from tape operation.Cancel the operation, or wait for it to complete. Then retry the operation.
116 Job failure on <ServerName> was caused by other ongoing conflicting operations on that computer. Note that some applications do not allow parallel recovery and backup operations on the same data source.Cancel the operations, or wait for them to complete. Then retry the operation.
117 The synchronization job failed due to an internal error.
  • For SQL Server, Exchange, or Windows SharePoint Services data, create a recovery point, enable short-term disk protection, and select Create a recovery point by using express full backup.
  • For other types of data, create a recovery point, and then select Create a recovery point after synchronizing.
118 The selected data cannot be recovered to the DPM server<ServerName> because the replica is not in the Replica creation pending state. Make sure that the replica is in Replica creation pending state before recovering.
130 You cannot add more recovery points because the maximum number of recovery points for the entire retention range is<MaxLimit>. To increase the recovery points per day, you must either decrease the retention range or select fewer days of week.
131 File name extensions must begin with a '.' and cannot contain any of the following characters: /, \, :, *, ?, ", <, >, |No action required.
132 Remove duplicate file name extensions.Remove the extensions.
133 You cannot choose this recovery point because the time difference between it and a previous recovery point is less than your specified synchronization frequency.

Specified synchronization frequency: <ValueEntered>
Choose a recovery point that has a time difference with a previous recovery point that is equal to or greater than the specified synchronization frequency.
135 Cannot protect this folder because data on other mount points of this volume have been selected for protection.No action required.
136 Unable to create protection group because no disks or tape libraries available.Configure a tape library or add a disk to the storage pool.
137 The protection group name entered already exists.Specify a different name.
138 You have enabled protection of data on the system volume<ObjectName>. If you also want to protect the system state of this computer, you must add the System State as a member of the protection group separately.No action required.
140 The network bandwidth usage throttling rate must be between 1 and 10000 Mbps.Specify a valid value.
141 Cannot perform < InputParameterTag> because the replica is not idle. Wait for the ongoing job to complete or cancel the job.
143 If you use DPM to protect data on NETLOGON or SYSVOL shares on a domain controller, restoring the data using DPM will corrupt the domain controller's copy of the Active Directory Domain Services database. No action required.
144 The backup frequency for long-term protection needs to be equal to or greater than the backup frequency for short-term protection.

Backup frequency for short-term protection: <InputParameterTag>
No action required.
145 You cannot reduce the express full backup schedule because this would affect the long-term recovery goals of this protection group.Before you can reduce the express full backup schedule of this protection group, you must modify the protection group properties to specify a backup frequency that is equal to or greater than weekly.
146 The specified protection group name is not valid. A protection group name must be between 1 and 64 characters, with at least one alphabet letter.Specify a valid name.
147 To view the protected computers, you need to enable protection of these computers.Enable protection.
148 You have chosen to protect replicas on another DPM server (primary DPM server).We recommend that you protect the DPM database (DPMDB) of the primary DPM server along with the replicas. Without protecting the DPMDB, you will not be able to recover the replicas of the primary DPM server in case of a disaster where the DPMDB and the replicas are lost.
149 You have specified the change journal size on volume<VolumeName> for <ServerName> to be set to <ValueEntered>. However, this is greater than the available space on the selected computer. Free space on the volume on the protected computer, and then retry the task.
150 You are trying to protect replicas on a primary DPM server.

File exclusions will not apply to these replicas, but they will apply to all other protection group members.
No action required.
151 The size and used disk space information forVolumeName on ServerName could not be retrieved. Disk space cannot be allocated to protect data on this volume until this information is retrieved. Do you want to retry?Retry the action.
152 DPM data source cannot be added to the protection group because of existing settings.Create a new protection group.
156 The ability to add members to this protection group is temporarily disabled while initial synchronization of one or more members occurs.Either cancel the initial synchronization jobs for the members or wait until they complete.
157 DatasourceName cannot be added to protection because it is already a member of a protection group.No action required.
158 ValueEntered is not a valid value. The maximum is MaximumSizeUnit. Specify a valid value.
159 <ValueEntered> is not a valid value. Specify a valid value.
160 <ValueEntered> does not meet the minimum allocation value of <OriginallyCalculatedValue> <Unit>.Specify a valid value.
162 DPM can optimize its disk allocation recommendation by calculating the size of the selected data onVolumeName on ServerName. Do you want to proceed? Proceed to optimize.
164 <VolumeName> on <ServerName> does not meet the minimum size requirement of 1 GB.Don't select the volume.
168 The replicas for one or more of the volumes being protected are missing. This may be a result of one or more disks in the DPM storage pool being offline or the deletion of volumes created by DPM to store the replicas. You cannot modify disk allocation or configure protection for any members on these volumes until the replicas have been reallocated.Click Review Pending Members in the protection group, and allocate disk space for protection.
169 Although you chose to retain the replica for this previously protected volume, the replica is now missing from the DPM server. Either the volume used to store the replica has been deleted from the storage pool, or the disk on which the replica was stored cannot be detected. You cannot protect this previously protected volume until you delete the record of this replica from DPM.Select the relevant member in the protection group and click Remove inactive protection. Make sure that the setting Delete replica on disk is selected.
171 There is insufficient space on the storage pool disks to allocate the replica and recovery point volumes.This error can occur when you attempt to stop bare metal recovery (BMR) for a protection group. By default, when you stop only BMR, DPM tries to convert BMR protection to System State protection, which requires more space for system backup than BMR. If available space is not sufficient to convert to System State protection, you will receive this error.

If you stop BMR protection to gain more disk space, select Stop protection of member for both Bare Metal Recovery and System State
172 The inputs are not valid for custom scheme.No action required.
173 You cannot protect the selected database now. This database is already selected for protection as part of Windows SharePoint Services protection to which the database belongs.If you want to protect only this database, then you have to remove the Windows SharePoint Services farm from protection.
174 You cannot protect the selected Windows SharePoint Services data now. Some of the databases which are components of the Windows SharePoint Services farm have already been selected for protection.If you want to protect this Windows SharePoint Services data, then you have to remove the databases from protection.
175 Existing volumes do not meet the size requirements for replica and recovery point volumes for<DatasourceType><DatasourceName> on <ServerName>. Either use the DPM storage pool disks for protection or create volumes that are adequately sized. DPM will not use any volumes in which either operating system or DPM component are installed.
176 DPM failed to use the volume<VolumeLabel> to create the replica because it is not adequately sized. Volumes to be used for the replica should be greater than<MinimumSize> GB.
177 DPM failed to use the volume<VolumeLabel> to create the recovery point volume because it is not adequately sized.Volumes to be used for storing recovery points should be greater than<MinimumSize> GB.
178 DPM failed to use volume<VolumeLabel> since this has already been selected to protect <DatasourceType><DatasourceName> on <ServerName>. No action required.
179 DPM cannot resize volumes<VolumeLabel> and <VolumeLabel>, which are being used to protect<DatasourceType><DatasourceName> on <ServerName> because these are custom volumes.Use Disk Management to resize your volumes.
180 Failure to allocate disk space to the storage pool for storing the replica and the recovery points for<VolumeName> on <ServerName>. No protection will be initiated for<VolumeName> on <ServerName> until disk space has been allocated to the storage pool. Select Review Pending Members for a protection group, and allocate disk space for protection.
181 DPM could not create<ProtectedGroup> because of failed disk allocations. Refer to the allocation errors listed below, and then try to create the protection group again.
182 Eseutil consistency check cannot be performed for this protection group, because Eseutil.exe is not present on the DPM server. Copy the Ese.dll and Eseutil.exe files from the Exchange Server installation folder to<FolderPath> on the DPM server.

You can also choose not to run an Eseutil consistency check for this protection group by clearing the Run Eseutil Consistency check option. However, we do not recommend this because it does not make sure of the recoverability of the protected data.
183 Select a single item for creating a recovery point on disk. You have currently selected multiple items in the list view.No action required.
184 Cannot create a recovery point for the application data source because protection is stopped.No action required.
185 There was a failure during recovery point consolidation.Locate the relevant alert and resolve the issue. Then retry recovery.
192 The requested operation could not be completed because the replica was in an inconsistent state.Run a consistency check, and then retry the operation.
195 Your changes cannot be applied because the protection group properties have changed. The protection group properties could have changed due to either of the following reasons:
  • An auto discovery job ran and modified the properties of this protection group.
  • Another user is using DPM Administrator Console to modify the properties of this protection group.
Retry the operation.
199 DPM was unable to protect the members in the resource group<ObjectName>. This resource group contains resources that have dependencies that are not part of this resource group.
  1. Check your cluster configuration to make sure that the shares and the hard disks on which the shares reside are part of the same resource group.
  2. Check your cluster configuration to make sure that the application and the hard disks that it requires are part of the same resource group.
200 DPM could not perform the requested action on the selected items. This might be because one or more of the selected items or a property associated with the selected items has changed, which prevents the requested action.Retry the operation.

back to Contents

Error codes 201-300

Error codeMessageMore information
296Failed to update protection agent, error: Data Protection Manager Error ID: 296Update the protection agent to a version that is compatible with the DPM server. From the DPM Administrator Console, click the Agents tab in the Management task area. Select the computer on which the protection agent is installed, and then click Update in the Actions pane.

back to Contents

Error codes 301-400

Error codeMessageAdditional information
301 The protection agent upgrade failed because the protection agent is not installed on<ServerName>.
  1. In DPM Administrator Console, in the Management task area, on the Agents tab, select the computer on which the protection agent is installed, and then in the Actions pane, click Uninstall to remove the protection agent record.
  2. On the Agents tab, click Install to reinstall the agent on <ServerName>.
302 The protection agent operation failed because it could not access the protection agent on<ServerName>. <ServerName> may be running DPM, or the DPM protection agent may have been installed by another DPM server.Uninstall DPM or the DPM protection agent from <ServerName> and install the DPM protection agent again from the computer that you want to use to protect the computer.
303 The protection agent operation failed on<ServerName>.
  • Another installation is running on the specified server.

    Resolution Wait for the installation to complete, and then retry the operation.

  • The boot volume on the server is formatted as file allocation table (FAT).

    Resolution Convert the boot volume to NTFS file system if you have sufficient space.
304 The protection agent operation failed because another agent operation was running on<ServerName>. Wait for the protection agent operation on <ServerName> to finish, and then try reinstalling the protection agent again.
305 The agent operation failed because the operating system on<ServerName> is not supported. Verify that the operating system is Windows Server 2003 Service Pack 1 (SP1) or later on the selected computers. If the operating system has been recently updated, Active Directory updates may be pending. In this case, wait until Active Directory is finished updating, and then try installing the protection agent again. The time required for Active Directory updates depends on your domain Active Directory replication policy.

For more information about software requirements, see the DPM 2010 System Requirements.
306 The protection agent installation failed because another version of the protection agent is already installed on<ServerName>. The protection agent installation failed because another version of the protection agent is already installed on the DPM server.

Resolution Use Add or Remove Programs in Control Panel to uninstall the protection agent from the DPM server, and then try reinstalling the protection agent.
307 The protection agent operation failed because DPM detected an unknown DPM protection agent on<ServerName>. Use Add or Remove Programs in Control Panel to uninstall the protection agent from <ServerName>, then reinstall the protection agent and perform the operation again.
308 The protection agent operation failed because DPM could not communicate with the Protection Agent service on<ServerName>. If you recently installed a protection agent on <ServerName>, the computer may be restarting. Wait a few minutes after restarting the computer for the protection agent to become available.

If the problem persists, do the following:
  1. Verify that <ServerName> is remotely accessible from the DPM server.
  2. If a firewall is enabled on <ServerName>, verify that it is not blocking requests from the DPM server.
  3. If <ServerName> is a workgroup server the password for the DPM user accounts may have changed or expired. To resolve this error, run SetDpmServer with the -UpdatePassword flag on the protected computer and Update-NonDomainServerInfo.ps1 on the DPM server.
  4. Restart the DPM Protection Agent service on <ServerName>. If the service does not start, uninstall the protection agent by using Add or Remove Programs in Control Panel on <ServerName>. Then in the Management task area, on the Agents tab, in the Actions pane, click Install to reinstall the protection agent on<ServerName>.
309 The agent operation failed because the ADMIN$ share on<ServerName> does not exist. Verify that the system root is shared as ADMIN$ on <ServerName>.
310 The agent operation failed because it could not access the ADMIN$ share on<ServerName>. Verify that you have ADMIN$ share permissions on <ServerName>, and that the system time on the DPM server and <ServerName> is synchronized with the system time on the domain controller.
311 The DPM protection agent on <ServerName> is not working properly. To resolve this error, do the following:
  • If the agent is not installed on <ServerName>, run DpmAgentInstaller.exe with this DPM computer as a parameter. For details, see the DPM Deployment Guide.
  • In DPM Administrator Console, uninstall the DPM protection agent. In the Management task area, on the Agents tab, select the protection agent, and then in the Actions pane, click Uninstall.
312 The agent operation failed because the DPM Agent Coordinator service is not responding.Restart the DPM Agent Coordinator service on <ServerName>.
313 The agent operation failed because an error occurred while running the installation program on<ServerName>. Review the log files on <ServerName> : [windir]\temp\msdpm*.log, and then take appropriate action. Retry the operation, and if the error persists, restart the computer, and then retry the operation again.
314 The agent operation failed because an installation is already in progress on <ServerName>. Wait for the installation to complete, and then retry the agent operation.
315 The agent operation failed because server <ServerName> is part of a cluster. DPM does not support protection of clustered servers.No user action is required.
316 The protection agent operation on <ServerName> failed because the service did not respond.If you recently installed a protection agent on <ServerName>, the computer may be restarting. Wait a few minutes after restarting the computer for the protection agent to become available.

Otherwise, to resolve this error, do the following:
  1. Check the recent records from the DPMRA source in the Application Event Log on<ServerName> to find out why the agent failed to respond.
  2. Verify that the DPM server is remotely accessible from <ServerName>.
  3. If a firewall is enabled on the DPM server, verify that it is not blocking requests from <ServerName>.
  4. If <ServerName> is a workgroup computer configured to use NETBIOS, make sure that the NETBIOS name of the DPM server is accessible from <ServerName>. Otherwise verify that the DNS name is remotely accessible.
  5. If <ServerName> is a workgroup server, make sure that the DPM server has an IPSEC exception to allow communication from workgroup servers.
  6. If <ServerName> is a workgroup server the password for the DPM user accounts could have been changed or may have expired. To resolve this error, run SetDpmServer with the -UpdatePassword flag on the protected computer and Update-NonDomainServerInfo.ps1 on the DPM server.
  7. Restart the DPM Protection Agent service on <ServerName>. If the service does not start, reinstall the DPM protection agent.

For additional information please see the following:

Data Protection Manager Agent Network Troubleshooting
317 The protection agent installation failed because the files needed to install the protection agent (version<AgentVersion>) are missing from the <ServerName> DPM server. Reinstall the missing files by running DPM Setup and DPM updates.
318 The agent operation failed because DPM was unable to identify the computer account for<ServerName>. Verify that both <ServerName> and the domain controller are responding. Then, in Microsoft Management Console (MMC), open the Group Policy Object Editor snap-in for the local computer, and verify the local DNS client settings in Local Computer Policy\Computer Configuration\Administrative Templates\Network\DNS Client.
319 The agent operation failed because of a communication error with the DPM Agent Coordinator service on<ServerName>. To resolve this error, do the following:
  1. If the protected computer is running a localized version of Windows Server 2003 SP1, first upgrade the operating system to Windows Server 2003 SP2.
  2. On the protected computer, download and install the appropriate localized hotfix in article 975759 in the Microsoft Knowledge Base, and then try the upgrade again.

Note The Hotfix Download Available form displays the languages for which the hotfix is available.
320 The agent upgrade failed because the protection agent is not installed on <ServerName>. In DPM Administrator Console, in the Management task area, on the Agents tab, click Uninstall to remove the agent record from DPM. Then click Install to reinstall the agent on <ServerName>.
321 The selected servers will reboot immediately after the agents have been installed.

Are you sure that you want to install agents on these servers?
No user action is required.
322 The following computers <ListofServers> were not found in Active Directory Domain Services, or they do not have a Windows Server operating system installed.To resolve this error, do the following:
  1. Check the spelling of the computer name.
  2. Verify that Windows Server 2003 with Service Pack 1 or later is installed on the computer.
  3. Verify that you entered the fully qualified domain name for the computer.
  4. If the computer has recently been added to the domain, you may need to wait for Active Directory to update.
  5. If the computer was recently restarted, wait a few moments and then retry the agent operation again.
  6. Verify that a two-way trust is enabled between the domain that the selected computer belongs to and the DPM server's domain, and that the trust is of type forest.
323 Upgrading the protection agents will cause the backup jobs that are running on the protected computers to fail. Upgrading the protection agents may also cause the replicas of the protected data to become inconsistent. You may need to schedule a consistency check after the upgrade is complete. Click Yes to continue. No user action is required.
324 The agent operation failed because the DPM Agent Coordinator service on <ComputerName>did not respond. To troubleshoot this issue, do the following:
  1. Check the recent DPMAC source records in the application event log on <ComputerName>.
  2. Verify that the DPM server is remotely accessible from <ComputerName>.
  3. If a firewall is enabled on the DPM server, verify that it is not blocking requests from <ComputerName>.
  4. Verify that the time on the DPM server and the selected computer is synchronized with the domain controller. At a command prompt, type net time /set to synchronize the time with the domain controller.

Then take the following actions based on which agent operation you were performing before you received the error.

If you were installing an agent by using DPM Management Console

On the targeted computer, install the protection agent manually, and then add the computer to the DPM server. For step-by-step instructions, see Installing Protection Agents Manually.

If you were uninstalling an agent by using DPM Management Console
  1. On the targeted computer, in Control Panel, navigate to Programs and Features.
  2. In the programs list, right-click Microsoft Data Protection Manager 2010 Agent, and then click Uninstall.
  3. On the DPM server, open DPM Management Shell.
  4. At the command line, type RemoveProductionServer.ps1, and then press Enter to remove the targeted computer from the DPM server.
  5. When prompted, type the DPM server name, press Enter, type the name of the computer that you want to remove, and then press Enter again.

If you were upgrading an agent by using DPM Management Console
  1. Copy the 32-bit or 64-bit version of the DPMAgentInstaller.exe file to a network share that is accessible from the computer on which you want to upgrade the agent.
  2. On the targeted computer, navigate to the network share, right-click DPMAgentInstaller.exe, and then click Run as administrator.
  3. On the DPM server, open DPM Administrator Console, on the navigation bar, click Management, and then click the Agents tab.
  4. In the Details pane, select the targeted computer, and then, in the Actions pane, click Refresh information.
325 The agent operation failed because the protection agent is not active until you restart the selected computers.Restart the selected computers.
326 The protection agent operation failed because access was denied to the <ServerName>DPM server. To resolve this error, do the following:
  1. If <ServerName> is protected by another DPM server, you cannot install the protection agent on it.
  2. If the DPM Agent Coordinator service is installed on <ServerName>, use Add or Remove Programs in Control Panel on <ServerName> to uninstall it.
  3. If another protection agent management job is running on <ServerName>, wait for it to complete, and then retry the operation.
328 The agent operation failed because the Remote Registry service is not running on<ServerName>. Start the Remote Registry service on <ServerName>. On the Administrative Tools menu, select Services. In the right pane, right-click Remote Registry, and then click Start.

Note You can disable the Remote Registry service after the agent operation is complete.
329 The agent operation failed because an incompatible version of <Name> is installed on <ServerName>. Install <Name> version <Version> or later, or uninstall <Name> from the computer. If <Name> was installed by your original equipment manufacturer (OEM), contact your OEM support for instructions.
330 The agent operation failed because the Windows Installer service on <ServerName> is disabled. Start the Windows Installer service on <ServerName>. On the Administrative Tools menu, select Services. In the right pane, right-click Windows Installer, and then click Start.

You can disable the Windows Installer service after the agent operation has completed.
331 The agent operation was skipped because similar operation is already running on <ServerName>. Wait for the other operation to finish and then retry the operation.
333 A protection agent is already installed on <ServerName>. No user action is required.
334 You cannot install the protection agent on <ServerName> because it is the DPM server. No user action is required.
335 Installing a protection agent on a computer that is running Windows 2003 Server causes the computer to briefly lose network connectivity.No user action is required.
336 The protection agent uninstall is unavailable because the DPM server is currently communicating with the protection agent on the following protected computers: <ListofServers>. Wait a few moments and then try uninstalling the protection agent again.
337 You cannot install the protection agent on <ServerName> because access to the computer has been denied.To resolve this error, do the following:
  1. If another DPM server is currently protecting <ServerName> use that DPM server to uninstall the protection agent from <ServerName>. Then, use this DPM server to install the protection agent on <ServerName>.
  2. Verify that the time on the DPM server and the selected computer is synchronized with the domain controller. At a command prompt, type net time /set to synchronize the time with the domain controller.
  3. If the computer is a domain controller, verify that the primary domain controller (the PDC Emulator) is running Windows Server 2003 with Service Pack 1 (SP1), and that Active Directory has completed replication between the domain controllers since the Windows Server 2003 SP1 installation.
338 You can only select <MaxInstallServers> computers to install at a time.Select less than <MaxInstallServers> computers to add to the Selected Computers list.
340 The protection agent upgrade failed because <ServerName> has a more recent version of the protection agent (version<AgentVersion>) installed.Uninstall the existing DPM protection agent from <ServerName> using Add or Remove Programs in Control Panel. Then, in DPM Administrator Console, reinstall the DPM protection agent version that you want. In the Management task area, on the Agents tab, click Install in the Actions pane.
341 The agent operation failed because the credentials you provided do not have sufficient user rights on<ServerName>. Possible Issue 1

The account that is used does not have sufficient user rights and permissions on the server.

Resolution: Retry the agent operation and provide credentials that have administrator user rights on the DPM server.

Possible Issue 2

The system times of the DPM server, the server on which you are installing the agent, and the domain controller are not synchronized; therefore the Kerberos authentication fails.

Resolution: Verify that system times on the DPM server and the server on which you are installing the agent are synchronized with the system time on the domain controller.

Possible Issue 3

The DNS setting on the DPM server or the computer on which you are installing the protection agent is incorrect.

Resolution: Verify that the DNS settings are correct.
342 The agent operation failed because the DPM server could not communicate with <ServerName>. To resolve this error, do the following:
  1. Verify that <ServerName> is online and remotely accessible from the DPM server.
  2. If a firewall is enabled on <ServerName>, verify that it is not blocking requests from the DPM server.
  3. Verify that the Remote Registry service on <ServerName> is running during the protection agent operation. If the Remote Registry service is not started, on the Administrative Tools menu, select Services. In the right pane, right-click Remote Registry, and then click Start.

Note You can disable the service after the protection agent operation is complete.
343 The agent operation failed because ServerName is not a 32-bit x86-based computer or a 64-bit x64-based computer.No user action is required.
344 DPM could not find the correct version of the DPM protection agent on the selected computer.To resolve this error, do the following:
  1. Make sure that the correct version of the agent is installed on the selected computer.
  2. If the protection agent has been recently upgraded, in DPM Management Shell, run Attach-ProductionServer.ps1 <Computer Name>, and then refresh the agent status again.
345 The agent operation failed because of a communication error with the DPM Agent Coordinator service on<ServerName>. Restart the DPM Agent Coordinator service on <ServerName>, and then try to reinstall the protection agent.
346 DPM is unable to retrieve the configuration information from <ServerName>. Make sure that the Windows Management Instrumentation (WMI) service is started. If the firewall is turned on, on <ServerName> make sure that an exception for WMI is created.
347 An error occurred when the agent operation attempted to create the DPM Agent Coordinator service on<Server Name>. To resolve this issue, do the following:
  • Verify that the DPM Agent Coordinator service on <Server Name> is responding, if it is present. Review the error details, take the appropriate action, and then retry the agent installation operation.
  • Try installing the protection agent manually on the targeted computer. For more information, in the DPM Deployment Guide, see Installing Protection Agents Manually in the DPM 2010 Technical Library.
  • If the targeted computer is running Windows Server 2008, on the targeted computer, do the following:
    1. Download and manually install the hotfix described in article 975759 in the Microsoft Knowledge Base.
    2. Resolve any errors that you receive during the installation of the hotfix. If you receive the error, "The service cannot be started, either because it is disabled or because it has no enabled devices associated with it," do the following:
      1. In Service Manager, expand Configuration, and then click Services.
      2. In the Services pane, right-click Windows Update, and then click Properties.
      3. In the Windows Update Properties dialog box, in the Start-Up type list, click Manual, click Apply, and then, in the Service status area, click Start.
      4. Retry the agent installation operation.
348 An error occurred when the agent operation attempted to communicate with the DPM Agent Coordinator service on<ServerName>. Possible Issue 1

An error occurred when the agent operation attempted to communicate with the DPM Agent Coordinator service on the DPM server.

Resolution: Verify that the Agent Coordinator service on the DPM server is responding, if it is present. Review the error details, take the appropriate action, and then retry the agent operation.

Possible Issue 2

Incorrect security settings for the COM object on the computer.

Resolution: Verify COM permissions on the server. Verify that the DCOM configuration settings are set as follows:

COM Security Default Access Permissions
  • Local Access and Remote Access permitted to Self
  • Local Access permitted to System

COM Security Machine Access Restriction (Security Limits)
  • Local and Remote Access permitted to NT AUTHORITY\ANONYMOUS LOGON
  • Local and Remote Access permitted to BUILTIN\Distributed COM Users
  • Local and Remote Access permitted to \Everyone

COM Security Default Launch Permissions
  • Launch permitted to NT AUTHORITY\SYSTEM
  • Launch permitted to NT AUTHORITY\INTERACTIVE
  • Launch permitted to BUILTIN\Administrators

COM Security Machine Launch Restriction (Security Limits)
  • Local Launch and Activate permitted to \Everyone
  • Local and Remote Launch, Local and Remote Activate permitted to BUILTIN\Administrators
  • Local and Remote Launch, Local and Remote Activate permitted to BUILTIN\Distributed COM Users
349 An error occurred when the agent operation attempted to transfer agent installation files to<ServerName>. Review the error details, take the appropriate action, and then retry the agent operation.
350 Disk <NTDiskNumber> is already in the storage pool. Select a different disk to add to the storage pool.
351 Disk <NTDiskNumber> cannot be added to the storage pool. Make sure that the disks being added to the storage pool do not contain any of the following: system volume, boot volume, OEM or other special volumes, DPM software, or SQL Server databases.
352 Disk <NTDiskNumber> cannot be added to the storage pool because the disk either failed or is missing.Check Disk Management to see whether the disk is online. If the disk is offline, check the hardware configuration and then rescan. If the disk is greater than 2 TB in size, make sure that it is a GUID Partition Table (GPT) disk.
354 Disk <NTDiskNumber> is not listed in the storage pool. In the Management task area, on the Disks tab, click Rescan to refresh all disks that are in the DPM storage pool.
355 Disk <NTDiskNumber> cannot be removed from the storage pool because it contains storage pool volumes.No user action is required.
356 The folder on which the <VolumeUsage> volumes must be mounted already exists.Clear all unmounted directories from the <DlsVolumesRoot> directory, and then retry the operation.
358 The allocation of disk space for storage pool volumes failed because there is not enough unallocated disk space in the storage pool.Add more disks to the storage pool or reduce the volume size requirement.
360 The operation failed due to a virtual disk service error. Retry the operation.
361 Disk <NTDiskNumber> was not added to the storage pool because it could not be converted to a dynamic disk.For more information about supported disk types, see the DPM 2010 Deployment Guide.
362 The replica cannot be increased because the replica volume is missing. Reallocate the replicas before trying to increase them.
364 DPM encountered an unexpected error while performing a disk related operation.Make sure that the Virtual Disk Service is running correctly, and then retry the operation.
365 DPM is currently shutting down and cannot complete the requested operation. After DPM shuts down, restart DPM and then retry this operation.
366 The computer running DPM has deleted volume [<VolumeGuid>, <VolumeLabel>] from DPM disk <NTDiskNumber> because it was not a volume in the DPM storage pool.In the Management task area, on the Disks tab, review all disks that are in the DPM storage pool.
367 DpmSync has completed with the following errors: <DPSSyncSummary>. On the DPM server, use Event Viewer to view details for this event. The details are available in the application event log.
368 DPM has deleted volume [<VolumeGuid>, <VolumeLabel>] because the size of the volume was modified externally by using system tools.Do not use system tools to change the size of volumes on disks that are in the DPM storage pool.
369 A protection agent is not installed on <Node> in the <Cluster> server cluster. Protection may fail if a failover occurs to <Node>. Install a protection agent on each node of the server cluster.
370 Agent operation failed. No user action is required.
371 All protection and recovery jobs on ServerName will fail until the agent is re-enabled.

Do you want to proceed?
No user action is required.
372 The agent operation failed because DPM detected a more recent version of the DPM protection agent (version<AgentVersion>) on <ServerName>. Upgrade the DPM server to <AgentVersion> or install the protection agent of <LocalDPMVersion> on <ServerName>.
373 The computer <ServerName> hosts the SQL Server database for this DPM computer. If the operating system of <ServerName> is Windows Server 2003, installing the agent may require you to reboot the computer. The DPM Engine and DPM Administrator Console will not work until the reboot completes. Do you want to install the protection agent?No user action is required.
400 The DPM server was unable to retrieve information about the remote system using the Windows Management Instrumentation (WMI) service on<ServerName>. To resolve this error, do one of the following:
  • From the command prompt, type DPMAgentInstaller.exe <dpmservername> to install the protection agent on the protected computer. Then attach the protection agent to the DPM server by using the Protection Agent Installation Wizard. Verify the following:
    • <ServerName> is online and remotely accessible from the DPM server.
    • If a firewall is enabled on <ServerName>, that it is not blocking WMI requests from the DPM server.
    • The WMI service on <ServerName> is running.

back to Contents


Error codes 401-500

Error CodeMessageAdditional Information
401 The agent installation failed while trying to install the Agent Coordinator service.To resolve this error, verify the following:
  • The share \\<ServerName>\ADMIN$ is accessible.
  • Remote calls from the DPM server to the Service Control Manager (SCM) on <ServerName> are not blocked by a firewall.
402When trying to retrieve information from the Windows Management Instrumentation (WMI) service on<ServerName>, access was denied.To resolve this error, follow these steps.

Caution

Serious problems can occur if you modify the registry incorrectly. These problems could require you to reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk. Always make sure that you back up the registry before you modify it, and that you know how to restore the registry if a problem occurs.

  1. On the target computer, click Start, click Run, type regedit, and then click OK.
  2. Locate the following registry subkey, and then delete it:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MicrosoftFirewall\DomainProfile\RemoteAdminSettings
  3. Restart the target computer, and then try to add the target computer to the DPM server again.
403 Access was denied when trying to create the lock file in \\<ServerName<ServerName> \Admin$. Verify that you have permissions to create the lock file in \\<ServerName>\Admin$<ServerName>\Admin$.
404 The agent operation failed when trying to install the Agent Coordinator service.To resolve this error, verify the following:
  • The share \\<ServerName>\ADMIN$ is accessible.
  • The remote calls from the DPM server to the Service Control Manager (SCM) on <ServerName> are not being blocked by a firewall.
405 DPM could not detect if computer <ServerName> is clustered. Agent installation on <ServerName> can continue. To protect clustered resources, you must install a DPM protection agent on all nodes of the cluster. Review the error details, and make sure that the Windows Management Instrumentation service is running and can be accessed remotely from the DPM server.
406 DPM detected that server <ChosenServerName> is clustered, but could not identify the fully qualified domain name of<ServerName>. Agent installation on <ChosenServerName> can continue. To protect clustered resources, you must install a DPM protection agent on all nodes of the cluster. Make sure that the cluster state is correctly configured and verify that all nodes are joined to the domain.
407 You have selected basic disks. DPM will convert to dynamic disks and any existing volumes on these disks will be converted to simple volumes. Do you want to continue?No user action is required.
408 Are you sure that you want to remove the selected disk from the storage pool? No user action is required.
409 The missing disk contains protection group members. To continue protecting these members, you must allocate them to another disk. Do you want to continue?No user action is required.
419 DPM could not set security permissions on the replica or recovery point volume that was created.Review the error details, take appropriate action and retry the operation.
420 DPM could not obtain security permissions on the replica or recovery point volume.Review the error details, take the appropriate action, and then retry the operation.
450 An invalid path name was specified for the DPM database location. Specify the correct path of the .mdf or .bak file, and then try again.
451 The path name specified for the DPM Report database location is not valid. No user action is required.
452 The DPM service failed to stop. Check the application and system event logs for information on the error.
453 The DPM service failed to start. Check the application and system event logs for information on the error.
454 DpmSync failed to connect to the specified SQL Server instance. Make sure that you have specified a valid instance of SQL Server associated with DPM and that you are logged on as a user with administrator privileges.
455 Failed to attach database [<DatabaseName>] at location [<DatabaseLocation>] to SQL Server. Make sure that the SQL Server services are running and that you are restoring a valid DPM database backup.
456 There were failures in the synchronization operation. For more detail, review the Application event log.
457 The command line arguments specified are not valid. For help about DpmSync, in DPM Management Shell, at the command prompt, type DpmSync -?.
458 The DPM database on the DPM server <ServerName> has been restored from a backup. As a result, the alerts that were generated before<DBRestoreTime> do not reflect the current state of alerts on the DPM server.To synchronize the Operations Manager view with the current state on the DPM server, do the following:
  1. In the Operations Manager Operator console, resolve all alerts for <ServerName>, and the computers that it protects: In Alerts view, display all alerts for System Center Data Protection Manager (DPM), sort the alerts by Source, and then select the alerts for <ServerName>. To remove the selected alerts, right-click the alerts, click Set Alert Resolution State, and then click Resolved.
  2. On the DPM server, in DPM Administrator Console, in the Actions pane, click Options, and then, on the Alert Publishing tab, click Publish Active Alerts. This publishes all existing alerts that may require a user action to Operations Manager.
460 The command syntax is not valid. For help about DpmSync, in DPM Management Shell, at the command prompt, type DpmSync -? .
461 The instance name specified could not be found. Specify the correct name for the instance of SQL Server.
462 Unable to retrieve DPM database file path. Specify the correct path, and then try the operation again.
464 Path not found: <FileName>. Make sure that the database backup exists at the specified path.
465 Unable to close all connections for detaching the database. Review the error details, and then try again.
466 Unable to copy database files to <FileName>. Review the error details, and then try the operation again.
467 The specified action can be performed only on a computer with DPM installed. Run the tool on the DPM server to complete these steps.
469 Unable to detach the database. Make sure that you have the appropriate permission to detach the DPM database.
470 The DPM database was not found in the specified instance of SQL Server. Make sure that the DPM database is present in the specified instance of SQL Server.
471 Unable to attach the database.Make sure that the DPM database backup is valid.

back to Contents


Error codes 501-600

Error CodeMessageAdditional Information
517 The message cannot be sent to the SMTP server. Check the SMTP server settings.
518 An authentication error occurred when trying to connect to the SMTP server. You typed an incorrect user name, password, or SMTP server name. Type the correct user name or password to enable e-mail delivery of reports and alert notifications.
519 The SMTP server has rejected one or more of the recipient addresses. Confirm the recipient addresses.
520 The SMTP server port number must be between 1 and 65535. Enter a valid port number.
521 Cannot resolve the SMTP server host name. Verify the SMTP server host name.
522 Cannot connect to the SMTP server. Verify the SMTP server name and port number.
523 The passwords entered do not match. Reenter the passwords.
524 The protection agent TCP port number must be between 1 and 65535. Enter a valid port number.
525 The protection agent TCP port number must be between 1 and 65535. Enter a valid port number.
526 The protection agent TCP port number must be different from the protection agent port number.Reenter the port numbers.
527 The SMTP server reports that the From address is not valid. Make sure that the appropriate permissions exist to send e-mail to the specified server by using SMTP.
529 An e-mail message has been successfully sent to the specified recipients. No user action is required.
530 A blank password is not allowed. Enter a non-blank password.
531 The DPM alerts have been published to the DPM Alerts event log. No user action is required.
532 Changes to end-user recovery settings do not fully take effect for each protection group until the next successful synchronization is complete.No user action is required.

back to Contents

Error codes 800-899

Error CodeMessageAdditional Information
800 DPM must be installed on a computer running Windows Server 2003 Service Pack 1 (SP1).Install DPM on a computer running Windows Server 2003 Service Pack 1 (SP1). The Windows Server 2003 SP1 redistributable package is available at http://go.microsoft.com/fwlink/?linkid=45556 .
801 To install DPM, you must be logged on as an administrator or a member of the local administrators group.Log on to the computer as an administrator or member of the local administrators group, and then run Setup again.
802 The computer processor speed does not meet the DPM minimum configuration requirements. The minimum required processor speed is<ClockSpeed>. Upgrade the computer hardware to meet the DPM minimum configuration requirements, or install DPM on a different computer. For information about DPM system requirements, see the DPM 2010 System Requirements (http://go.microsoft.com/fwlink/?LinkID=179661).
803 The available memory on the computer is less than the DPM minimum memory requirement. The minimum memory requirement is<MinimumMemoryRequired> MB, and the recommended memory requirement is 2 GB.Upgrade the computer hardware to meet the DPM minimum configuration requirements, or install DPM on a different computer. For information about DPM system requirements, see the DPM 2010 System Requirements (http://go.microsoft.com/fwlink/?LinkID=179661).
805 There is not enough disk space for <InstallItem>. Free up additional disk space on this disk, and then retry the operation.
806 Setup failure - Active Directory not found. No user action is required.
807 Setup failure - Target not configured correctly. No user action is required.
809 DPM cannot load the file <FileName>. The file may be missing or corrupt. Run DPM Setup from the DPM product DVD. If you ran Setup from the DVD, the DVD is corrupt.
810 The DPM installation failed. Review the error details, take appropriate action, and then run DPM Setup again.
811 The DPM database was not created. Use Add or Remove Programs in Control Panel to remove the DPM files and registry entries that were created during Setup. Verify that SQL Server is properly installed and that it is running, and then run Setup again.
812 Report configuration failed. Verify that SQL Server Reporting Services is installed properly and that it is running.

For additional information please see the following:

SQL Installation and Reporting Issues with Data Protection Manager
813 The DPM uninstall failed. Review the error details, take appropriate action, and then try uninstalling DPM again.
814 The configuration data for this product is corrupt.Troubleshoot your Windows Installer installation. Contact your support personnel for further help.
817 The Setup log file path <FileName> is too long after being fully qualified. Verify that the Application Data folder path has fewer than 260 characters, and then run DPM Setup again.
818 The Setup log file path <FileName> is not valid. Specify a valid Application Data folder path.
820 Setup cannot query the system configuration. If you encountered this error while you were on the Installation page of the DPM Setup Wizard, to resolve the error, do the following:
  1. On the DPM server, click Start, click All Programs, click Microsoft SQL Server 2008, click Configuration Tools, and then click SQL Server Configuration Manager.
  2. In SQL Server Configuration Manager, click SQL Server Services, and then in the Details pane, make sure that the SQL Server and SQL Server Agent services that are related to the DPM 2010 database are running.
  3. If either service is stopped, in the Details pane, right-click the service, and then click Start.
  4. If the services do not start, change the logon account for both services to the Local system account by doing the following:
    1. In the Details pane, right-click the service, and then click Properties.
    2. On the Log On tab, click Built-in account, in the Built-in account list, click Local system, and then click OK.
    3. In the Details pane, right-click the service, and then click Start.


  5. Now change the logon account for both services back to the MICROSOFT$DPM$Acct account by doing the following:
    1. In the Details pane, right-click the service, and then click Properties.
    2. On the Log On tab, click This account, in the Account name box, type .\MICROSOFT$DPM$Acct, in the Password and Confirm password boxes, type the same password that you used during DPM 2010 RTM setup, and then click OK.
    3. In the Details pane, right-click the service, and then click Start.


  6. Install or upgrade to DPM 2010 RTM again.

822 DPM Setup could not access the SQL Server Reporting Services configuration. Verify that the Windows Management Instrumentation (WMI) service is running. If the WMI service is not running, in Control Panel, click Administrative Tools, and then click Services. Right-click Windows Management Instrumentation, and then click Start.
823 DPM Setup cannot access registry key <RegistryKey>. Verify that the registry key <RegistryKey> exists, and then run DPM Setup again.
828 DPM cannot connect to the Service Control Manager (SCM). To troubleshoot this issue, review the recent errors in the Windows event log.
829 DPM cannot open the handle to the <SetupServiceName> service. To troubleshoot this issue, review the recent errors in the Windows event log.
830 DPM cannot read the service <ServiceName> configuration. On <ServerName>, review the recent errors in the Windows event log.
832 Setup cannot grant the <UserName> account access to the DPM database.Verify that SQL Server is properly installed and that it is running.
833 Setup could not delete the <UserName> user account. To delete the <UserName> user account, on the Administrative Tools menu, click Computer Management, expand Local Users and Groups, and then click Users. Right-click <UserName>, and then click Delete.
834 Setup cannot remove the deployed reports. To delete the reports manually, go to http://<MachineName>/ReportServer$<InstanceName>.
836 The DPM repair failed. Verify that the DPM server meets the software requirements. Uninstall DPM, and then run DPM Setup again.
841 Setup cannot calculate the disk space for the specified location. Specify a different installation location.
842 Setup cannot access the <RegistryKey> registry key for the <SqlInstance>instance of SQL Server. Verify that SQL Server 2008 is properly installed.
843 The physical location of the existing DPM database cannot be found. Verify that the instance of SQL Server is properly installed, and that the <ServiceName> SQL Server service is running.

Upgrading from a DPM evaluation version where SQL Server has expired

Before uninstalling DPM
  1. If you are using a remote instance of SQL Server, upgrade the DPM server. If you are using a local instance of SQL Server, backup DPM database.
  2. Uninstall SQL Server.
  3. From the DPM installation media, run the SQL Server installer and install an evaluation edition of SQL Server with the same name (MSDPM2012EVAL).
  4. Attach the database to this instance.
  5. Run System Center 2012 – Data Protection Manager (DPM) setup.

Warning

If you have already uninstalled the evaluation version of DPM, then you must reimage the computer.
845 DPM Setup could not delete the DPMDB database. To delete the DPMDB database, in SQL Server Management Studio, connect to server <DPM server name>\<InstanceName>. Expand the <InstanceName> instance of SQL Server, expand Databases, right-click the DPMDB database, and then click Delete.
846 DPM cannot locate SqlCmd.exe. Verify that the SQL Client Tools are installed. If they are not installed, you must install the SQL Client Tools, and then run DPM Setup again.
847 DPM cannot create the <SetupServiceName> service. Failure to create the service may be due to a pending restart.Restart the computer, uninstall DPM, and then run Setup again.
848 Setup is unable to copy the files from <SourceLocation> to <InstallLocation>. Verify that Setup has access to the installation location.
849 Setup is unable to delete the folder <InstallLocation>. Delete the folder manually.
850 Setup is unable to mark files at <FolderPath> for deletion. After DPM setup is complete, delete the files manually.
851 Cannot start Setup. Run the Setup program from the DPM product DVD. If you ran Setup from the DVD, the DVD is corrupt.
853 Setup is unable to register DPM in Add or Remove Programs. No user action is required.
854 Another instance of DPM Setup is running. Verify that no other instance of DPM Setup is running, and then proceed with DPM Setup.
855 Setup was unable to delete the scheduled jobs. Open SQL Server Management Studio, and then connect to the DPM instance of SQL Server. Expand the instance of SQL Server, expand SQL Server Agent, expand Jobs, and then delete the <ScheduleCategory> category.
856 DPM could not access the existing DPM database, or the DPM database is corrupt.Verify that the SQL Server service is running. If the SQL Server service is running, restore the DPM database, and then run DPM Setup again.
857 DPM cannot enumerate the list of computers on which protection agents are installed because it cannot gain access to the DPM database.Protection agents may be installed on some of the computers. Uninstall the agents on the protected computers by using Add or Remove Programs in Control Panel.
858 The DPM product key is invalid. Enter a valid DPM product key. The product key is located on the back cover of the Data Protection Manager product DVD.
859 Setup cannot parse the SQL Server 2008 Reporting Services configuration file <FileName> for the SMTP server address and the address of the sender. Verify that SQL Server is properly installed.
860 DPM cannot stop service <SetupServiceName>. Review the error details, take the appropriate action, and then try installing DPM again.
861 DPM cannot read the installation path registry key. Some of the folders will not be deleted.Manually delete the folders after completing DPM Setup.
862 Setup cannot start the <SetupServiceName> service. Review the error details, take the appropriate action, and then try installing DPM again.
863 You cannot use the selected location <DirectoryPath> to install DPM. DPM can only be installed on the local drive of the computer. DPM cannot be installed to read-only folders, hidden folders, folders within mount points, root volumes, or directly to local system folders such as <FolderPath>. Select a different location on which to install DPM.
864 You cannot install DPM on removable media or a network share. The location <DriveName> cannot be used as an installation location. Select a location on a local hard drive to install DPM.
865 Setup could not enumerate the information about volumes allocated to DPM. On the Administrative Tools menu, click Computer Management, and then click Disk Management. Delete the volumes allocated to DPM from the disks that were added to the storage pool.
866 The Windows account that was created in DPM Administrator Console in the Recovery task area could not be removed.On the Administrative Tools menu, click Computer Management. Expand Local Users and Groups, click Users, right-click the Windows account, and then click Delete.
868 DPM cannot query the volume information for directory <DirectoryPath>. Select another installation location on a local hard drive to install DPM.
869 The <DirectoryPath> directory is not on an NTFS volume. Install the prerequisite software and DPM on a volume formatted with NTFS.
870 DPM cannot query the attributes of directory <DirectoryPath>. Select another installation location on a local hard drive to install DPM.
871 DPM Setup has detected an existing installation of DPM on this computer. The existing installation is a later version than the version you are trying to install.To install the earlier version of DPM, you must first uninstall the existing version.
876 DPM Setup cannot create the folder <FolderPath>. If the folder already exists, delete the folder, and then run DPM Setup again.
877 DPM Setup cannot write to file <FileName>. If the file already exists, delete the file, and then run Setup again.
878 Setup cannot create the protection job schedules. Open SQL Server Management Studio, and then connect to the DPM instance of SQL Server. Expand the instance of SQL Server, expand SQL Server Agent, expand Jobs, and then delete the <ScheduleCategory> category.
879 DPM Setup could not delete service <SetupServiceName>. To delete the service manually, at the command prompt, type sc delete <SetupServiceName>.
880 The DPM protection agent configuration failed. Review the error details, take the appropriate action, and then try installing DPM again.
881 The required local group could not be created. Try installing DPM again.
882 DPM Setup could not create a required service. This computer may be protected by another computer running DPM. You cannot install DPM on a computer on which a protection agent is installed.If the DPM protection agent is installed on this computer, use Add or Remove Programs in Control Panel to uninstall it, and then run DPM Setup again.
883 DPM Setup cannot read the <FileName> file. Verify that the current user has permissions to read the file.
884 DPM Setup cannot delete folder <FolderPath>. Manually delete the folder <FolderPath> after completing DPM Setup.
885 DPM Setup cannot create the <FileName> file. Verify that the current user has permissions to create the file.
886 This program is for internal DPM use only. To launch the DPM Setup program, double-click Setup.exe in the root folder of the product DVD.
887 An error occurred while trying to configure DPM. Uninstall DPM by using Add or Remove Programs in Control Panel, and then run DPM Setup again.
888 DPM Setup could not create the DPM shortcut on your desktop. To start using DPM, click Start, point to All Programs, and then click Microsoft System Center Data Protection Manager 2010.
889 The database files from a previous DPM installation were found at <Location>. Delete the existing files at <Location>, or select an alternative location for your database.
890 An older version of DPM is installed on this computer. Please uninstall it and launch setup again.No user action is required.
892 The computer <MachineName> could not be removed from the intranet security zone settings in Internet Explorer.In Internet Explorer, on the Tools menu, click Internet Options. In the Internet Options dialog box, on the Security tab, click Local intranet, click Sites, then click Advanced, and then remove computer <MachineName> from the intranet zone.
893 Setup cannot delete the volumes that are allocated to DPM. On the Administrative Tools menu, click Computer Management, and then click Disk Management. Delete the volumes allocated to DPM from the disks that were added to the storage pool.
894 DPM Setup could not delete the DPM shortcut on your desktop. Manually delete the DPM shortcut from your desktop.
895 The service <SetupServiceName> was not deleted from the computer. Restart the computer to delete the service <SetupServiceName>.
896 DPM could not connect to database <DatabaseName>. Verify that the SQL Server service <ServiceName> is started and that you have permissions to query SQL Server.
897 DPM could not delete database <DatabaseName>. In SQL Server Management Studio, delete the following databases: <DatabaseName>, <TempDatabaseName>.
898 DPM Setup cannot query the SQL Server Reporting Services configuration. Verify that the Windows Management Instrumentation (WMI) service is running, and that your SQL Server Reporting Services installation is not corrupt.
899 DPM Setup could not delete the MSDPMTrustedMachines local group. Manually delete the MSDPMTrustedMachines group. On the Administrative Tools menu, click Computer Management. Expand Local Users and Groups, and then click Groups. Right-click MSDPMTrustedMachines, and then click Delete.

back to Contents

Error codes 900-999

Error CodeMessageAdditional Information
900 DPM Setup could not delete all the registry keys that DPM uses. No user action is required.
901 DPM Setup could not delete the DPM Agent Coordinator service. Manually delete the DPM Agent Coordinator service. On the Administrative Tools menu, click Services. Right-click DPM Agent Coordinator, and then click Delete.
902 The job encountered an internal fatal error. Contact Microsoft Customer Support.
904 The protection agent on <ServerName> is not compatible with the DPM version. The protection agent version is<AgentVersion>, and the DPM version is <EngineVersion>. Update the protection agent on <ServerName>.
905 The protection agent on <ServerName> is not compatible with the DPM version. The protection agent version is<AgentVersion>, and the DPM version is <EngineVersion>. Verify that all required DPM updates are applied to this computer.
907 The job encountered an internal database error. Retry the operation.
908 The job was canceled. The user either canceled the job or modified the associated protection group.Retry the operation.
909 DPM has received an improperly formed message and was unable to interpret it. Retry the operation. If the problem persists, contact Microsoft Customer Service and Support.
910 The DPM service terminated unexpectedly during completion of the job. The termination may have been caused by a system restart.Retry the operation.
911 DPM was not able to complete this job within the allotted time. In the Monitoring task area, group jobs by type and review the job details. If the next scheduled occurrence of this job is currently running, no action is required. If the job is not currently running, retry the job.
912 The job has been canceled because of the failure of another job on which it depended.Retry the operation.
913 The job was canceled because it was scheduled during the inactivity timeframe.Retry the operation.
914 The job failed because of an unexpected error. Make sure that the DPMRA service is running on the selected computer.
915 The operation failed because the data source VSS component <Component> is missing. Make sure that the protected data source is installed properly and that the VSS writer service is running.
916 Cannot connect to the DPM service because it is running in recovery mode, which was initiated by the DpmSync tool.Please wait for DpmSync to complete its operation. If DpmSync is not running and the DPM service is still in recovery mode, run DpmSync again.
917 Connection to the DPM service has been lost. Review the application event log for information about a possible service shutdown. Make sure that the following services are enabled:
  • DPM
  • DPM Replication Agent
  • SQLAgent$ <InstanceName>
  • MSSQL$ <InstanceName>
  • Virtual Disk Service
  • Volume Shadow Copy


918 Connection to the DPM service has been lost. Make sure that the DPM service is running, and review the Application event log for information about a possible service shutdown.
920 DPM failed to write events to the DPM Alerts event log. Either the DPM Alerts event log has been deleted or the permissions have been changed.Uninstall DPM, and then reinstall DPM to recreate the DPM Alerts event log.
921 The operation failed because an error occurred while enumerating the data source for<Component>. Make sure that the data source specified in the error message is online and accessible.
929 DPM Management Shell is not connected to any DPM server or the previous connection was lost.Use the Connect-DPMServer command to connect to a DPM server. If you are already connected to a DPM server and still seeing this error, make sure that the DPM service is running and review the application event log for any errors.
939 The DPM Administrator Console version <Version> is incompatible with the DPM server version.Make sure that the version is between <MinimumUIVersion> and <MaximumUIVersion>.
940 Unable to connect to the database because of a fatal database error. It is unlikely that the database has been damaged.Review the event log and take appropriate action. Make sure that SQL Server is running.
941 Unable to connect to the DPM database. Make sure that SQL Server is running and configured correctly, and then retry the operation.
942 The integrity of the database is questionable because of a hardware or software problem.Contact your SQL Server administrator. Review the Windows event log. Run DBCC CHECKDB to determine the extent of the damage. It is possible that the problem is in the cache only and not on the disk itself. If so, restarting SQL Server corrects the problem. Otherwise, use DBCC to repair the problem. In some cases, it may be necessary to restore the DPM database.
943 Unable to connect to the DPM database because the database is in an inconsistent state.Contact your SQL Server administrator. In some cases, it may be necessary to restore the DPM database. If the problem persists, contact Microsoft Customer Service and Support.
944 Database operation failed. Make sure that SQL Server is running and that it is configured correctly, and then retry the operation.
945 Unable to connect to the DPM database because of a general database failure. Make sure that SQL Server is running and configured correctly.
946 Another instance of DPM is currently running. Restart the computer, and then retry the operation again.
948 Unable to connect to <ServerName>. To resolve this error, do the following:

Restart the DPM Services

  1. On the DPM server, open Service Manager, expand Configuration, and then click Services.
  2. In the Services pane, restart the following DPM services:
    • DPM (MSDPM)
    • DPM Access Manager Service (DPMAMService)
    • DPM Writer (DpmWriter)
    • DPMLA (DPM Library Agent)
    • DPMRA (DPM Replication Agent)


  3. If you cannot restart the services, do the following:
    1. In Service Manager, expand Diagnostics, expand Event Viewer, and then expand Windows Logs.
    2. Check the logs for errors, resolve any errors that you find, and then try to open DPM Administrator Console again.


Rerun the DPMSync –Sync Command

  1. On the DPM server, click Start, click All Programs, click Microsoft SQL Server 2008, and then click SQL Manager Management Studio.
  2. In the Connect to Server dialog box, in the Server name box, type the computer name and the name of the instance of SQL Server that is used for the DPM database in the following format: <ComputerName\InstanceName>.
  3. In SQL Manager Management Studio, expand Databases, right-click DPMDB, and then click New Query.
  4. In the SQLQuery pane, type the following, and then click Execute.
  5. Select * from Tbl_dls_globalsetting where PropertyName='DBRecovery'.
  6. If the PropertyValue returned is 1, a DPMSync -Sync operation ended or was canceled before it was completed. Rerun DPMSync -Sync, let the operation finish completely, and then try to open the DPM Administrator Console again.
951 No schedules found for the job definition. No user action is required.
955 The consistency check resulted in the following changes to SQL Server Agent schedules: Schedules added: <SchedulesAdded>
Schedules removed: <SchedulesRemoved>
Schedules updated: <SchedulesUpdated>.
No user action is required.
956 DPM cannot protect your Windows SharePoint Services farm until you install DPM protection agents on the following computers: <ServerName>. To resolve this error, do the following:
  1. To install agents on these computers, in the Management task area, click the Agents tab, and then, in the Action pane, click Install.
  2. If any of the computers are a node of a cluster or a mirror, you must install a DPM protection agent on all physical nodes of that cluster or mirror.
  3. If SQL aliasing is used in the SharePoint farm, make sure that SQL Client Connectivity components are installed on the SharePoint front-end web server.
  4. If SQL aliasing is used in the SharePoint farm, you can run the ConfigureSharePoint.exe -ResolveAllSqlAliases command on the SharePoint front-end web server to identify the SQL aliases that cannot be resolved by DPM.
957 DPM is unable to protect your mirrored SQL Server databases <Component> until you install DPM protection agents on the following computers: <ServerName>. To install protection agents on these computers, in the Management task area, click the Agents tab, and then, in the Action pane, click Install. If any of the computers are a node of a cluster, you must install a DPM protection agent on all physical nodes of the cluster.
958 DPM cannot browse the contents of the virtual machine on the protected computer<protected computer>. Perform a full restore of the virtual machine.

If none of the conditions listed in the Explanation section are present, and you still get this error, try the workaround explained in Microsoft Knowledge Base article 2013544.
959 DPM could not enumerate one or more volumes on protected computer <ServerName>. Make sure that the disks are fixed and that volumes are formatted with the NTFS file system.
960 DPM could not enumerate one or more VSS applications on the protected computer<ServerName>. Please make sure that all VSS writers are in a good state by checking the Event Viewer for errors from VSS.
961 DPM could not enumerate one or more non-VSS applications on protected computer<ServerName>. Make sure that all VSS writers are in a good state by checking the Event Viewer for errors from VSS. Also make sure that the PSDataSourceConfig.xml file is configured properly.
962 DPM could not enumerate one or more SharePoint search writers on protected computer<ServerName>. Make sure that all SharePoint search writers are in a good state.
963 DPM could not enumerate one or more components for application <Component>on protected computer <ServerName>. Make sure that the application writer is in a good state.
964 DPM could not enumerate application component <Component> on protected computer<ServerName>. Make sure that the writer is in a good state.
965 DPM could not enumerate instances of SQL Server by using Windows Management Instrumentation on the protected computer<ServerName>. Make sure that Windows Management Instrumentation for SQL Server is in a good state.
966 DPM could not connect to the instance of SQL Server <Component> on the protected computer<ServerName>. Make sure that the instance of SQL Server is in a good state.
967 DPM could not enumerate SharePoint data sources on the protected computer <ServerName>.To resolve this error, do the following:
  1. Make sure that the front-end Web server of the SharePoint farm has been configured for protection by using ConfigureSharePoint.exe -EnableSharePointProtection.
  2. If you are protecting SharePoint Search, also run ConfigureSharePoint.exe -EnableSPSearchProtection on the front-end Web server.
968 The current selections will be reset, and you must select them again. Click Yes to reset or No to keep the current selection.
975 The arguments for the job definition are not valid. Retry the operation with the correct argument syntax.
976 The DPM job failed because it could not contact the DPM engine. Restart the DPM service.
997 A non-fatal failure instance has been detected for process <DpmProcessName>. This will be reported to Microsoft. No user action is required.
998 The operation failed because of a protection agent failure. Retry the operation.
999 An unexpected error caused a failure for process <DpmProcessName>. Restart the DPM process <DpmProcessName>.

back to Contents

Error codes 1000-1999

Error CodeMessageAdditional Information
1000 Login failure caused by incorrect user name or password. Verify the user name and password, and then try again.
1002 You cannot cancel the selected job at this time. No user action is required.
1100 DPM: Information alert: ServerName. No user action is required.
1101 DPM: Warning alert: ServerName. No user action is required.
1102 DPM: Critical alert: ServerName. No user action is required.
1103 DPM: Recovery alert: ServerName. No user action is required.
1104 DPM: Resolved information alert: ServerName No user action is required.
1105 DPM: Resolved warning alert: ServerName No user action is required.
1106 DPM: Resolved critical alert: ServerName No user action is required.
1107 The following alert became inactive at ResolvedTime. No user action is required.
1109 For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.No user action is required.
1200 Status: <AlertStatus>

Volume: <VolumeName>

Computer: <ServerName>

Description: Used disk space on replica volume exceeds threshold of <ThresholdValue>%.
For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1201 Status: <AlertStatus>

Data source type: <DatasourceType>

Data source: <DatasourceName>

Computer: <ServerName>

Protection group: <ProtectedGroup>

Description: Replica volume cannot be detected.
For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1202 Status: <AlertStatus>

Protection Group: <ProtectedGroup>

Description: DPM discovered one of the following changes:
  • New shares or volumes
  • Deleted volumes or shares
  • Shares have been remapped


For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1204 The replica for <DatasourceName> on <ServerName> is currently being synchronized with consistency check. A consistency check can be started automatically or manually. To configure automatic consistency check options, change this protection group by using the Modify Protection Group Wizard. To start a manual consistency check, in the Protection task area, on the Actions pane, click Perform Consistency Check. For more information, open the DPM Administrator Console and review the alert details in the Monitoring task area.
1205 Status: <AlertStatus>

Data source type: <DatasourceType>

Data source: <DatasourceName>

Computer: <ServerName>

Description: Replica is being created.
For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1206 The replica of <DatasourceName> on <ServerName> is inconsistent with the protected data source. All protection activities for this data source will fail until the replica is synchronized with consistency check.For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1209 Status: <AlertStatus>

Computer: <ServerName>

Description: Recovery jobs started at <StartDateTime>.
For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1210 Status: <AlertStatus>

Computer: <ServerName>

Description: Recovery jobs started at <StartDateTime> completed with failures.
For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1211 Recovery to <TargetServerName> that started at <StartDateTime> completed. Some jobs have successfully recovered data and some jobs have failed. For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1212 Status: <AlertStatus>

Computer: <ServerName>

Description: Recovery jobs started at <StartDateTime> completed successfully.
For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1214 Status: <AlertStatus>

Data source type: <DatasourceType>

Data source: <DatasourceName>

Computer: <ServerName>

Description: Last <FailureCount> recovery points were not created.
For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1215 Status: <AlertStatus>

Data source type: <DatasourceType>

Data source: <DatasourceName>

Computer: <ServerName>

Description: Synchronization jobs failing.
For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1216 Status: <AlertStatus>

Data source type: <DatasourceType>

Data source: <DatasourceName>

Computer: <ServerName>

Description: DPM failed to stop protection.
For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1217 Status: <AlertStatus>

Description: New protectable computers found.
For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1218 The replica for <DatasourceType> <DatasourceName> on <ServerName>is not created. You have chosen to create the replica manually. All subsequent protection activities for this data source will fail until the replica is created and synchronized with consistency check.For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1219 The replica for <DatasourceType> <DatasourceName> on <ServerName>is not created. Replica creation job is scheduled to run at a later time. Data protection will not start until replica creation is complete.For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1220 Status: <AlertStatus>

Description: The disk <DiskName> cannot be detected or has stopped responding. All subsequent protection activities that use this disk will fail until the disk is brought back online.
For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1221 Status: <AlertStatus>

Computer: <ServerName>

Description: Incompatible DPM protection agent.
For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1222 Status: <AlertStatus>

Computer: <ServerName>

Description: Unable to contact DPM protection agent.
For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1223 Status: <AlertStatus>

Computer: <ServerName>

Description: Failed to update end-user recovery permissions.
For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1224 Status: <AlertStatus>

Volume: <VolumeName>

Computer: <ServerName>

Description: Network bandwidth usage throttling not working.
For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1225 Unsupported data found. For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1226 Status: <AlertStatus>

<LibraryType> : <Library>

Description: <LibraryType> : <Library> is not available, and all jobs for this library will fail until the connection is established.
For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1227 Status: <AlertStatus>

<LibraryType> : <Library>

Description: Library is not functioning efficiently.
For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1228 Status: <AlertStatus>

<LibraryType> : <Library>

Drive: <LibraryDrive>

Description: Tape is decommissioned and should be removed from the library.
For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1229 Status: <AlertStatus>

<LibraryType> : <Library>

Description: Number of free tapes is less than or equals the threshold value.
For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1230 Status: <AlertStatus>

<LibraryType> : <Library>

Tape: <MediaLabel>

Description: Tape erase job failed.
For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1231 Status: <AlertStatus>

<LibraryType> : <Library>

Tape: <MediaLabel>

Description: Tape verification job couldn't start or failed.
For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1232 Status: <AlertStatus>

Description: Data copy job failed.
For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1233 Status: <AlertStatus>

Description: Library catalog for backup job was not built correctly.
For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1234 Status: <AlertStatus>

Description: Backup to tape failed.
For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1237 Status: <AlertStatus>

<LibraryType> : <Library>

Drive: <LibraryDrive>

Description: A drive in the library is not functioning.
For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1238 Status: <AlertStatus>

<LibraryType> : <Library>

Tape: <MediaLabel>

Description: Tape has been verified.
For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1240 Status: <AlertStatus>

<LibraryType> : <Library>

Description: Job requires tape that is not available in the library.
For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1243 Detailed inventory failed. To resolve this error, do the following:
  • Perform a fast inventory after each tape operation.
  • Make sure that the tape specified for a detailed inventory is not in a drive and being backed up.
  • To reduce the number of detailed inventory failure alerts, create the following registry key. To open the Registry Editor, click Start, click Run, and then type regedit.

    Registry location:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\1.0\Alert

    DWORD name: DetailedInventoryFailed
    Value data: 0

Caution

Serious problems can occur if you modify the registry incorrectly. These problems could require you to reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk. Always make sure that you back up the registry before you modify it, and that you know how to restore the registry if a problem occurs.

Note

After you have created the registry key, you can check whether detailed inventory jobs fail or succeed by using the Jobs tab in the Monitoring view.
1244 Database size on DPM server has exceeded the threshold value. For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1245 Status: <AlertStatus>

<LibraryType> : <Library>

Tape: <MediaLabel>

Description: Data integrity verification failed.
For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1246 Status: <AlertStatus>

Volume: <VolumeName>

Computer: <ServerName>

Description: Used disk space for recovery point volume exceeds threshold of <ThresholdValue> %.
For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1247 Status: <AlertStatus>

Data source type: <DatasourceType>

Data source: <DatasourceName>

Computer: <ServerName>

Description: DPM failed to configure protection.
For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1248 Status: <AlertStatus>

Data source type: <DatasourceType>

Data source: <DatasourceName>

Computer: <ServerName>

Description: Consolidation of recovery points failed.
For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1249 Status: <AlertStatus>

Description: DPM detected multiple disks with the same disk identification number (DiskID). None of these disks will be added to the DPM Storage Pool.
For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1250 Status: <AlertStatus>

Data source type: <DatasourceType>

Data source: <DatasourceName>

Computer: <ServerName>

Description: Data corruption detected.
For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1251 Status: <AlertStatus>

Computer: <PSServerName>

Description: Agent ownership is required to run backup/recovery jobs on <PSServerName>.
For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1255 The share <Share Name> that was previously mapped to <OldFolderPath> has changed to <NewFolderPath>. DPM will continue to protect <Old FolderPath, but recommends you modify protection as suggested in Recommended Action. For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.

back to Contents

Error codes 2000-3999

Error CodeMessageAdditional Information
2000 DPM failed to run the operation because another conflicting operation is in progress.Retry the operation later.
2009 DPM protection agent on<AgentTargetServer> could not complete the operation due to insufficient resources on the computer.To resolve this error, do the following:
  1. For computers that are running Windows Server 2003, make sure that KB 942486 is installed.
  2. Make sure that the page file size is set correctly. For additional information on page file size requirements, go to the DPM and Memory topic on the Microsoft TechNet website.
  3. For 32-bit computers other than those hosting Exchange Server 2003, make sure that the /3GB switch is not set in the boot.ini file.
  4. If the protected volume is highly fragmented, run Disk Defragmenter on the volume, and then run a consistency check.
  5. Create the registry key ForceFixup under HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Data Protection Manager\Agents\2.0 with a value of 1, and then retry the operation.

2013 Host authentication failed. Retry authentication.
2031 The specified destination path is not valid. Restore to an alternate location.
2032 The specified path does not exist. Select a valid path.
2033 DPM encountered an error while performing an operation for <FileName> on <AgentTargetServer>. To resolve this error, do the following:
  1. Refer to the detailed error code in the description above. Retry the operation after the issue has been fixed.
  2. If the error was caused by insufficient resources, it could be a transient failure, and you should retry the operation later.
  3. If error is because of privileges with SMB share, wait for some time or reboot the file server, and then retry the operation.

2034 The specified path does not reside on an NTFS volume. Restore to an NTFS volume.
2035 The operation failed because of insufficient disk space. Increase the amount of free disk space on volume <VolumeName> on the destination computer, and then retry the operation, or recover to an alternate destination that has sufficient free disk space.
2036 The operation failed because DPM was unable to access the file or folder <FileName> on <AgentTargetServer>. This could be because the file or folder is corrupt, or the file system on the volume is corrupt.To resolve this error, do the following:
  1. Run chkdsk on the affected volume, and then run synchronization with consistency check.
  2. If running chkdsk does not solve the problem, and the computer indicated above is a protected computer (and not the DPM server), consider deleting this file or folder from the source, and then running synchronization with consistency check.

2037 DPM could not detect the selected volume <VolumeName> on <ServerName>. Make sure that <VolumeName> on <ServerName> exists. If the volume exists, retry the operation.
2038 Some items were not recovered because recovering items across a reparse point is not permitted. The folder<ReparsePtPath> under the recovery destination is a reparse point. Retry the recovery to a destination that does not contain a reparse point.
2039 DPM failed to run the operation because it could not retrieve the ownership information for the targeted computer.Retry the operation later.
2040 DPM failed to access the volume <VolumeName> on <AgentTargetServer>. This could be caused by cluster failover during backup or insufficient disk space on the volume.If cluster failover has happened during backup, retry the operation. Otherwise, increase the amount of free disk space on volume<VolumeName> on the targeted computer, and then retry the operation.
3000 The requested report history could not be found in SQL Server Reporting Services.No user action is required.
3001 The Reporting Services Server cannot connect to the DPM database. To repair the configuration, follow the steps for repairing DPM in the DPM 2010 Deployment Guide.
3002 DPM could not generate the report. A parameter is missing or was incorrectly specified.No user action is required.
3003 The SQL Server Reporting Services service is not running. Start the service on the computer on which the DPM database was created. On the Administrative Tools menu, click Services. Right-click SQL Server Reporting Services, and then click Start.
3004 You do not have sufficient permissions to perform this action on the report. Make sure that you are a member of the local Administrators group on the DPM server. If the DPM database is on a remote computer, make sure that you are a member of the DPM Administrators group on the remote computer.
3005 DPM could not generate the report. A parameter is missing or was incorrectly specified.No user action is required.
3006 The report you requested could not be found on the SQL Server Reporting Services server.Repair your DPM installation using the steps described in the DPM 2010 Deployment Guide.
3007 The report cannot be displayed because the report property settings are incorrect.Repair your DPM installation using the steps described in the DPM 2010 Deployment Guide.
3008 The SQL Server Agent service <InstanceName> is not responding. Restart the SQL Server Agent service <InstanceName>.
3009 DPM could not set up a schedule for this report. The information is either missing or it is incorrectly specified.No user action is required.
3010 DPM cannot set up an e-mail subscription for this report. The information may be missing or incorrect.In the Actions pane, click Options, and then, on the SMTP Server tab, provide the correct SMTP server name and email address.
3011 There is not enough content to generate a report for this time period.

The number of days of available data must be at least <DaysCount> before DPM can generate this report.
To generate this report, specify at least <DaysCount> days.
3012 DPM cannot perform this action because no valid property settings have been detected for this report.Repair your DPM installation using the steps described in the DPM 2010 Deployment Guide.
3013 DPM could not connect to SQL Server Reporting Services. Restart SQL Server Reporting Services, and then try the operation again.
3014 An error occurred causing the reporting job on <ServerName> to fail. The system files may be corrupt.Retry the reporting task. If the problem persists, repair your DPM installation by using the steps described in the DPM 2010 Deployment Guide.
3015 DPM is unable to change the e-mail settings. Log on to <ServerName>. On the Start menu, point to All Programs, point to Microsoft SQL Server 2008, point to Configuration Tools, and then click Reporting Services Configuration. In Configure Report Server, update the email settings.
3016 A Windows account is required to view DPM reports. To create the account, reinstall DPM using the steps described in DPM Setup Help.
3017 The user account that DPM Reporting created is not enabled. To re-enable the account, in DPM Administrator Console, on the Navigation bar, click Reporting. In the Actions pane, click Options, and then, on the Reporting Password tab, enter a valid password.
3018 The reporting password for the Windows account has expired. Change the password for account <AccountName>. On the Administrative Tools menu, click Computer Management. Expand Local Users and Groups, and then click Users. Right-click <AccountName>, and then click Set Password.
3020 Unable to configure local Windows account in the system. The operation is allowed only on the primary domain controller for the domain.Review the error details, take appropriate action, and then retry the operation.
3021 DPM is unable to create the Windows account group because the group already exists.Delete the Windows account group, and then retry the operation.
3022 DPM is unable to create the Windows account because the account already exists.Delete the Windows account, and then retry the operation.
3023 DPM is unable to configure the Windows account because the password you entered does not meet the Group Policy requirements.Enter another password for the account.
3024 DPM cannot grant the DPM database access to the <UserName> account. Make sure that SQL Server is running and configured correctly.
3025 You are unable to add the local computer to the intranet security zone in Internet Explorer because of insufficient permissions.Log on as an administrator or backup operator, and then try the operation again.
3026 You cannot view the selected report because the Web site HttpMachine is not in a trusted site zone. Do you want to add the site and view the report? No user action is required.
3027 The report schedule has expired and will be reset. Check the DPM report settings.
3028 You cannot add the computer to the trusted zone. We recommend that you reinstall Internet Explorer Enhanced Security Configuration. Use Add or Remove Programs in Control Panel. Click Add/Remove Windows Components, and then check Internet Explorer Enhanced Security Configuration. However, you can proceed to the report by specifying your user name and password in subsequent steps.
3029 DPM has detected incorrect property settings for certain reports. Repair your DPM installation by using the steps described in the DPM 2010 Deployment Guide.
3030 DPM is unable to create the report schedule because the date specified has already passed.Specify today or a later date.
3031 Specify today or a later date. Specify a future date.
3032 The report file does not contain an entry for the description. Repair your DPM installation by using the steps described in the DPM 2010 Deployment Guide.
3033 The report file contains an incorrect description value. Repair your DPM installation by using the steps described in the DPM 2010 Deployment Guide.
3034 DPM reporting requires ASP.NET 2.0, which is not found or installed on this computer.Install ASP.NET 2.0. Use Add or Remove Programs in Control Panel. Click Add/Remove Windows Components, check Applications Server, and then click Details. Check ASP.Net and Internet Information Services (IIS), and then click OK.
3035 DPM is unable to read the registry to retrieve report settings because of insufficient permissions.Log on as an administrator, and then retry the operation.
3036 DPM reporting cannot query the IIS configuration. Connect to the computer on which the DPM database was created. Make sure that the Windows Management Instrumentation service is running.
3038 SQL Server Reporting Services is not installed or is not configured properly. Make sure that SQL Server Reporting Services is properly installed and is running.
3039 DPM reporting is not yet activated because the required security settings could not be applied to the DPMReport local account.On the Administrative Tools menu, click Local Security Policy. Expand Local Policies, and then click User Rights Assignment. Right-click Allow log on locally policy, and then click Properties. Click Add User or Groups, and then add the DPMReport account. If the DPMReport account is listed in the Deny log on locally policy, remove it.
3040 DPM Setup is unable to update the report server configuration to configure e-mail settings.Log on to <ServerName>. On the Start menu, point to All Programs, point to Microsoft SQL Server 2008, point to Configuration Tools, and then click Reporting Services Configuration Manager. In Reporting Services Configuration Manager, update the email settings.
3041 DPM is unable to generate reports. This may be because the web.config file for the SQL Server Reporting Services is not valid or is inaccessible.To resolve this error, do the following:
  1. Make sure that the SQL Server Reporting Services is properly installed and running.
  2. Make sure that the web.config file is valid.

3042 The report might be incorrect because the co-location of data on tape is enabled.No user action is required.
3050 Unable to update shares or share permissions. Rerun synchronization or wait for the next synchronization to occur. If the problem persists, check your domain configuration.
3051 Unable to update the Active Directory Domain Services database. Either run a synchronization, or wait for the next scheduled synchronization to occur. If the problem persists, check your domain configuration.
3052 Active Directory Domain Services schema is not configured properly. Redo the schema extension operation.
3053 No nodes have been detected for cluster <Cluster>. To resolve this error, do the following:
  1. On the Agents tab in the Management task area, make sure that the cluster nodes are accessible.
  2. Use the cluster administrative console to make sure that the cluster is still clustered.

3054 One or more volumes are missing for the following applications: <ListOfDataSources>. Make sure that the dependent volumes for the data sources are online.
3055 DPM is unable to enumerate<Component> on computer <ServerName>. Make sure that <Component> is accessible to the protection agent.
3100 The used disk space on the computer running DPM for the replica of <DatasourceType><DatasourceName> has exceeded the threshold value of <ThresholdValue>%, or there is not enough disk space to accommodate the changed data. If you do not allocate more disk space, synchronization jobs may fail.Allocate more disk space for the replica. If no free disk space is available in the storage pool, you may need to add physical disks to the computer running DPM.
3101 Recovery data for <DatasourceType> <DatasourceName> on <ServerName> in protection group <ProtectedGroup> resides on a volume that cannot be detected. All subsequent protection activities relating to<DatasourceName> will fail until this volume is brought back online or the replica is re-created.Make sure that the disk containing the replica volume and the recovery point volume appears in Disk Management. If you are unable to locate the volumes in Disk Management, try following:
  1. In the Management task area in DPM Administrator Console, on the Disks tab, rescan the disk containing the replica volume and the recovery point volume, and then make sure that the volume is back online.
  2. In the Protection task area in DPM Administrator Console, stop protection of the data source by using the Stop protection of member option, and then add the data source to a protection group again.

3103 DPM failed to obtain catalog information as part of the backup for <DatasourceType><DatasourceName> on <ServerName>. Your recovery point is valid, but you cannot perform item-level recoveries by using this recovery point.If you do not expect to perform item-level recoveries by using this recovery point, dismiss this alert; otherwise, take the recommended actions:
  1. If the operation failed for a short-term backup to disk, in the Protection task area, select the data source, and then click Create recovery point to restart the backup.
  2. If the operation failed for a short-term backup to tape, in the Protection task area, select all the failed data sources that belong to the same protection group, and then click Create recovery point – tape. This will make sure that the tape backups are located on the same tape.
  3. Dismiss this alert immediately after starting your backup.

3104 The replica for <DatasourceType> <DatasourceName> is currently being synchronized with consistency check. A consistency check can be started automatically or manually. To configure automatic consistency check options, modify this protection group using the Modify Protection Group Wizard. To start a manual consistency check, in the Protection task area, in the Actions pane, click Perform Consistency Check. No user action is required.
3105 The replica of <DatasourceType> <DatasourceName> on <ServerName> is being created. After the initial replica is created, only incremental changes are synchronized.No user action is required.
3106 The replica of <DatasourceType> <DatasourceName> on <ServerName> 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.

For SharePoint farm, recovery points will continue getting created with the databases that are consistent. To backup inconsistent databases, run a consistency check on the farm.
To resolve this error, synchronize with consistency check.
3107 DPM cannot run a backup/recovery job on <PSServerName> because it is managed by the DPM server %<ServerName>. To have this DPM server manage <PSServerName>, click the recommended action link below. This will cause backup/recovery jobs for<PSServerName> to fail on DPM server <ServerName>.
3109 The recovery jobs for <DatasourceType> <DatasourceName> that started at<StartDateTime>, with the destination of <ServerName>, are in progress.No user action is required.
3110 The recovery jobs for <DatasourceType> <DatasourceName> that started at<StartDateTime>, with the destination of <ServerName>, have completed. Some jobs successfully recovered data and some jobs failed.

The following items could not be recovered: <TempListOfFiles>.
Make sure that the file is not already present and in use on the destination computer, and that there is sufficient disk space for the files.
3111 The recovery jobs for <DatasourceType> <DatasourceName> that started at<StartDateTime>, with the destination of <TargetServerName>, have completed. Most or all jobs failed to recover the requested data.Possible solutions

  • In the Monitoring task area, on the Jobs tab, click Type to group the jobs by type to view details of the recovery jobs.
  • You may see this error if the VMMS service is down. Retry the action after you start the service.
  • If you are seeing this error because of SMB share privileges, you should wait for some time or restart the server and then try the operation again.
3112 The recovery jobs for <DatasourceType> <DatasourceName> that started at<StartDateTime>, with the destination of <ServerName>, have successfully completed.No user action is required.
3113 Exchange recovery If you are recovering to Exchange server that is cluster continuous replication (CCR) or local continuous replication (LCR), perform following steps:
  1. Reseed the replica of the recovered storage group.
  2. Resume the storage group copy for the recovered storage group.

3114 Recovery point creation jobs for <DatasourceType> <DatasourceName>on <ServerName> have been failing. The number of failed recovery point creation jobs =<FailureCount>.

If the data source being protected is SharePoint, click Error Details to view the list of databases for which recovery point creation failed.
No user action is required.
3115 Since <OccurredSince>, synchronization jobs for <DatasourceName> on <ServerName> have failed. The total number of failed jobs = <FailureCount>. The last job failed for the following reason: No user action is required.
3116 DPM failed to stop protection for <DatasourceType> <DatasourceName>on <ServerName>. If you no longer want to protect any data sources on the computer, you can uninstall the protection agent from the computer. You can also retry the stop protection job.
3117 DPM discovered new computers that you may want to protect. To view a list of the new computers, click Details.
3118 The replica for <DatasourceType> <DatasourceName> on <ServerName> is not created. You have chosen to create the replica manually. All subsequent protection activities for this data source will fail until the replica is created and synchronized with consistency check.To resolve this error, do the following:
  1. Manually copy data to the replica path as specified in the details for this data source in the Protection task area.
  2. After you copy the data, click the link below to synchronize with consistency check.
3119 The replica for <DatasourceType> <DatasourceName> on <ServerName> is not created. A replica creation job is scheduled to run at a later time. Data protection will not start until the replica creation is complete.No user action is required.
3120 The disk <DiskName> cannot be detected or has stopped responding. All subsequent protection activities that use this disk will fail until the disk is brought back online.In the Management task area, on the Disks tab, check the status of the disks. If a disk is missing, rescan the disk configuration to detect the disk. If the disk is still missing, verify physical disk connections, and then scan the disk again. If the disk is no longer available, you can remove the disk from the storage pool. To continue protecting the affected data, stop protection of the data sources by using the Stop protection of member option, and then add the data sources to a protection group again.
3121 The DPM protection agent on <ServerName> is incompatible with this version of DPM. All subsequent protection and recovery activities for<ServerName> will fail until the correct version of the agent is installed.In the Management task area, On the Agents tab, check the status of the agent and update it to the correct version.
3122 The DPM protection agent on <ServerName> could not be contacted. Subsequent protection activities for this computer may fail if the connection is not established. The attempted contact failed for the following reason: <reason> In the Management task area, on the Agents tab, check the status of the agent.
3123 Failed to update permissions used for end-user recovery on <ServerName>. Permissions update failed for the following reason: <reason> No user action is required.
3124 DPM network bandwidth usage throttling is not working because the Windows Quality of Service (QoS) Packet Scheduler is not enabled on <ServerName>. Either stop the DPM protection agent service on <ServerName>, and then make sure that the QoS Packet Scheduler is enabled, or disable network bandwidth usage throttling for the computer. To install the QoS Packet Scheduler:

In Control Panel, point to Network Connections, right-click the appropriate connection, and then click Properties. On the General tab, click Install, click Service, click Add, click QoS Packet Scheduler, and then click OK.
3125 DPM has discovered new unsupported files or folders on one or more protected volumes. DPM will continue to protect the supported data on these volumes, but will not protect the unsupported data.No user action is required.
3126 The share <ShareName> that previously mapped to <OldFolderPath> has changed to <NewFolderPath>. DPM will continue to protect <OldFolderPath>, but we recommend that you modify protection as suggested in the Recommended Action.To start protecting <NewFolderPath>, in the Protection task area, perform the following steps:
  1. Stop protection for this share.
  2. Re-protect the same share.

3127 DPM detected multiple disks with the same disk identification number (DiskID). None of these disks will be added to the DPM Storage Pool.To resolve this error, do the following:
  1. Check to see that multipath software is running on the DPM server.
  2. In the Management task area, on the Disks tab, click Rescan.

3128 DPM detected an inconsistent replica of the data source for <ListOfDataSources>. Attempts to fix this may not have been successful. Older recovery points may not be recoverable because of hardware issues on the protected computer or DPM server.To resolve this error, do the following:
  1. Review the System Event logs for hardware related errors on the protected computers and the DPM servers.
  2. Perform test recoveries of the last recovery point on the volume and the older recovery points that may have issues.
  3. Manually create new recovery points for the data sources that are indicated in the error.
  4. Run more frequent integrity checks.
3129 DPM has detected an inconsistent replica of the data source during the backup of<ListOfDataSources>. This is because of an IO error on a protected server with possible hardware issues.To resolve this error, do the following:
  1. Review the System Event log for any hardware-related errors on the protected computer.
  2. Run hardware diagnostic tools to verify the health of the hardware.
  3. Run application-specific integrity checks to make sure of logical consistency of the data. In case of a failure, recover the data from latest recovery point, and then perform an application-specific integrity check. Repeat this process with previous recovery points until you recover a logical consistent recovery point.
  4. Manually create new recovery points for the data source indicated in the error.
  5. Run more frequent integrity checks.


3130 DPM failed to fixup VHD parent locator post backup for <DatasourceType> <DatasourceName> on <ComputerName>. Your recovery point is valid, but you will be unable to perform item-level recoveries using this recovery point.To resolve this error, do one or more of the following:

If you do not expect to be performing item-level restores using this recovery point, then dismiss this alert; otherwise, take the following recommended actions:
  1. Install the Hyper-V role on the DPM server.
  2. In the Protection task area, select the data source, and then click Create recovery point to restart the backup.

3131 DPM failed to obtain active virtual hard disk information as part of the backup for<DatasourceType> <DatasourceName> on <ServerName>. Your recovery point is valid, but you will not be able to perform item-level recoveries by using this recovery point.If you do not expect to perform item-level recoveries by using this recovery point, dismiss this alert; otherwise, take the following recommended actions:
  1. Make sure that the Hyper-V WMI provider call succeeds on the Hyper-V host.
  2. In the Protection task area, select the data source, and then click Create recovery point to restart the backup.


3132 DPM failed to fixup the VHD parent locator after the backup for <DatasourceType><DatasourceName> on <ServerName>, because the operation was canceled. Your recovery point is valid, but you will not be able to perform item-level recoveries by using this recovery point.If you do not expect to perform item-level recoveries by using this recovery point, dismiss this alert; otherwise, in the Protection task area, select the data source, and then click Create recovery point to restart the backup.
3133 DPM failed to gather item level catalog for <x> databases of the SharePoint Farm <Farm Name>. Some of the recovery points for these databases in the farm would be associated with an earlier successful catalog.Restart the catalog job for the SharePoint farm by running the Start-CreateCatalog cmdlet in DPM Management Shell.
3134 DPM could not obtain backup metadata information for <DatasourceType> <DatasourceName> on <ServerName>. If the data source is a SharePoint farm, a valid recovery point was created. However, content databases from this recovery point can be recovered only by using the alternate location option.If the data source is a SharePoint farm, make sure of the following:
  1. That "ConfigureSharePoint.exe -EnabledSharePointProtection" has been run on the front-end Web server with the current SharePoint farm administrator credentials.
  2. That the SharePoint VSS writer is running on the front-end Web server.

3135 Cannot run the catalog job for the data source <DatasourceName> because it is not a SharePoint farm.Rerun the cmdlet by providing a data source that is a SharePoint farm.
3136 DPM failed to provide the Windows Group %GroupName; read permissions on the replica for %DatasourceType; %DatasourceName; on %ServerName. Your recovery point is valid, but you may not be able to perform item-level recoveries in an optimized manner using this recovery point. You may choose to perform unoptimized item-level restores using this recovery point, then dismiss this alert; otherwise in the Protection task area, select the data source and click Create recovery point to restart the backup.
3137 Cannot find the group GroupName>. DPM will automatically recreate this group but optimized item level recovery will fail for older recovery points.Please perform un-optimized item level recovery for older recovery points. This will take more time than it normally takes. Detailed steps to perform this are provided in the documentation.
3151 DPM was unable to complete this job within the time allocated. In the Monitoring task area, group jobs by type, and then review the job details. If the next scheduled occurrence of this job is currently running, no action is required. If the job is not currently running, retry the job.

If you retry a synchronization job and it fails again, consider enabling on-the-wire compression. For more information, see "How to Enable On-the-Wire Compression" in DPM Help.
3152 Choose to send Microsoft anonymous feedback automatically about your hardware and software configurations, and feature usage patterns.Opt in or opt out of the Customer Experience Improvement Program.
3154 Description: New data source found. For more information, in DPM Administrator Console, in the Monitoring task area, review the alert details.
3155 Description: Data source is missing. For more information, in DPM Administrator Console, in the Monitoring task area, review the alert details.
3159 Creation of recovery points for <DatasourceName> on <ServerName> have failed. The last recovery point creation failed for the following reason: <reason> No user action is required.
3160 Synchronization jobs for <DatasourceName> on <ServerName> have failed.No user action is required.
3161 Recovery data for <DatasourceName> on <ServerName> in protection group<ProtectedGroup> resides on a volume that cannot be detected. All subsequent protection activities relating to<DatasourceName> will fail until this volume is brought back online or the replica is recreated.Make sure that the disk containing the replica volume appears in Disk Management. Or, in the Protection task area in DPM Administrator Console, use the Modify disk allocation action to allocate replica space.
3162 The replica of <DatasourceName> on <ServerName> is being created. After the initial copy is made, only incremental changes are synchronized.No user action is required.
3163 The replica of <DatasourceName> on <ServerName> is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check.No user action is required.
3164 The recovery jobs for <DatasourceName> that started at <StartDateTime>, with the destination of <ServerName>, are in progress. No user action is required.
3165 The recovery jobs for <DatasourceName> that started at <StartDateTime>, with the destination of <ServerName>, have completed. Some jobs have successfully recovered data and some jobs have failed.In the Monitoring task area, on the Jobs tab, sort the jobs by type to view the details of the recovery jobs.
3166 The recovery jobs for <DatasourceName> that started at <StartDateTime>, with the destination of <TargetServerName>, have completed. Most or all jobs failed to recover the requested data.On the Jobs tab in the Monitoring tasks area, filter the jobs by type to view details of the recovery jobs.
3167 The recovery jobs for <DatasourceName> that started at <StartDateTime>, with the destination of <ServerName>, have successfully completed.No user action is required.
3168 The DPM database (DPMDB) size has exceeded the threshold limit.

DPM database size: <DPMDBSize> GB

DPM database location: <DPMDBLocation> on <ServerName>.
The DPM database (DPMDB) size cannot be reduced. To resolve this alert, you need to increase the free space in the DPMDB volume, or increase the alert threshold value in the tape catalog retention dialog. If the tape catalog is very large, reducing the size of the tape catalog may make sure that DPM database does not grow any further.

SharePoint

You may see this warning if you are protecting a large SharePoint farm with millions of items in it. Make sure that you have enough disk space on the DPM database volume for the database to grow.
3169 The used disk space on the computer running DPM for the recovery point volume of<DatasourceType> <DatasourceName> has exceeded the threshold value of<ThresholdValue> % (DPM requires 600 MB of internal usage in addition to free space available). If you do not allocate more disk space, synchronization jobs may fail due to insufficient disk space.Allocate more disk space for the recovery point volume by using the Modify disk allocation action in the Protection task area. If no free disk space is available in the storage pool, you may need to add physical disks to the computer that is running DPM.
3170 DPM could not start a recovery, consistency check, or initial replica creation job for<DatasourceType> <DatasourceName> on <ServerName> for following reason: <reason> No user action is required.
3171 The start time is greater or equal to the end time. Correct the filter definition.
3172 At least one library must be selected in the filter definition. No user action is required.
3173 At least one data source must be selected in the filter definition. No user action is required.
3174 At least one job type and job status must be specified in the filter definition.No user action is required.
3175 Data transferred and time elapsed must be an integer, and greater than or equal to zero, and less than the maximum number size.No user action is required.
3176 Date not entered in the correct format. No user action is required.
3177 The default filter cannot be updated or deleted. No user action is required.
3178 Consolidation of recovery points of the replica failed for <DatasourceType><DatasourceName> on <ServerName> when one of the following operations was being performed:
  1. Express full backup
  2. Consistency check
  3. Recovery
If you are seeing this error, the following are a list of possible solutions:
  • In the Monitoring task area, check the Alerts tab to locate the specific alert for one of the operations indicated above. Follow the recommended action for that alert. If you do not find any active alerts for the operations indicated above, click the link below to inactivate this alert.
  • Run consistency check and retry the operation again.
3179 A filter with the specified name already exists. Specify a different filter name.
3180 DPM could not run the backup/recovery job on <PSServerName> because it is managed by the DPM server<ServerName>. To resolve this error, do the following:
  1. Resolve any active Agent ownership required alert for the computer.
  2. Click the link below to rerun the failed job.

3181 Some computers in the protection group have not been synchronized for <ThresholdValue> days. To review the list of computers that DPM has not backed up, click View Error Details, and then take the appropriate action. To modify the number of days after which DPM should display an alert for client computers that are not being backed up, modify the protection group properties.
3182 The recovery jobs for <DatasourceType> <DatasourceName> that started at <StartDateTime>, with the destination of <ServerName>, have successfully completed.

Virtual machine recovery to alternate host is complete.
Verify the virtual machine configuration before starting it. You may need to reconfigure the network adapter for the virtual machine on the alternate host before starting it.
3183 The backup SLA is not being met for the following computers:

<ServerName>
No user action is required.
3188Creation of online recovery points for <ServerName> have failed. The last online recovery point creation failed for the following reason: (ID: 3188)

Windows Azure Backup Agent was unable to create a snapshot of the selected volume. (ID: 100034)
This can occur if the DPMWriter service isn't running. To resolve the issue, set the DPMWriter service to Automatic, and make sure that the service is started.
3200 Could not access end-user recovery-specific information in Active Directory Domain Services.Check the domain configuration to make sure that the DPM schema extension has been successfully applied to the Active Directory. Also verify that DPM has permissions to access the data in the extended schema.
3201 DPM failed to log in with the specified user name and password. Check your user name and password, and then retry the operation.
3202 Could not access end-user recovery-specific content in Active Directory Domain Services.Re-run synchronization or wait for the next synchronization to occur. If the problem persists, check your domain configuration.
3210 The wizard was interrupted before <ProductName> could complete successfully.The system has not been modified. To install this program at a later time, please run the installation again.
3211 Your system has not been modified. To install this program at a later time, please run the installation again.No user action is required.
3212 Data Protection Manager Active Directory Domain Services update error. No user action is required.
3213 Active Directory Domain Services could not be configured. No user action is required.
3214 Configuration failed because the account used is not a member of the Schema Admins group.Try again, using an account that is a member of the Schema Admins group.
3215 Active Directory Domain Services could not be configured because the domain could not be found.Make sure that the domain name is properly constructed. The following example shows a properly constructed domain name: city.corp.company.com.
3216 Active Directory Domain Services could not be configured because the DPM computer with the specified name could not be found.No user action is required.
3217 The computer name you entered is not valid. Enter the name of the DPM computer that should be given access to the end-user recovery data in Active Directory Domain Services.
3218 Not a valid DPM computer name. No user action is required.
3219 Configuration failed because this computer is not in the given domain, the domain cannot be found, or the account used does not have Active Directory Domain Services update privileges.No user action is required.
3220 The domain controller on which the schema is to be modified is running Windows 2000 Server. On Windows 2000 Server-based domain controllers, Active Directory schema modification is disabled by default.If the schema update for end-user recovery fails, you may need to enable schema modification on your domain controller. For instructions, see the Microsoft Help and Support article Schema Updates Require Write Access to Schema in Active Directory.
3221 DPM was unable to configure Active Directory Domain Services for end-user recovery because a recent change to Active Directory Domain Services has not yet been replicated between domain controllers.Make sure that the schema master replicates the latest changes to at least one domain controller, and then retry the operation. For information about synchronization requirements for domain controllers, see Microsoft Knowledge Base article 305476.
3222 Invalid domain name. Provide the complete domain name in FQDN format.
3223 The DNS domain name you entered is not valid. Specify the DNS domain name of the DPM server to which you want to grant access to end-user recovery data in Active Directory Domain Services.
3301 <LibraryType> <Library> could not be contacted. All jobs for<LibraryType> <Library> will fail if the connection is not established.No user action is required.
3302 <LibraryType> <Library> is not functioning efficiently for the following reason:

The drive information for <LibraryType> <Library> is incorrect and needs to be refreshed.
The number of drives reported for this library is different from the number of drives detected by DPM. If any drives are out of the library for servicing, ignore this alert; otherwise, remap the drives within the library manually. For information about remapping tape library drives see the following:

Remap a tape drive
3303 Library drive <LibraryDrive> in <Library> is not functioning and library jobs may fail until the drive is repaired. The drive is not functioning for the following reason: <reason> No user action is required.
3304 DPM has marked the <MediaLabel> tape as decommissioned, which means that data cannot be written to this tape in the future. You may be able to recover data from this tape.This tape is decommissioned and should be removed from the library. You may be able to recover data from this tape. If recovery from this tape fails, check for a duplicate or older copy of the data.
3305 The number of free tapes in the <LibraryType> <Library> is less than or equals the threshold value of<ThresholdValue>. You must add tape to the library and mark it as free in order to prevent future backups from failing.Add tape to the library and mark it as free.
3308 <MediaLabel> could not be erased for the following reason: <reason> No user action is required.
3309 Data on the tapes <MediaList> cannot be verified for the following reason: <reason> No user action is required.
3310 The data copy job failed for the following reason: <reason> No user action is required.
3311 The back up to tape job failed for the following reason: <reason> Look at the sub-error and take appropriate action.
3312 The backup to tape job completed, but the catalog was not built correctly for <DatasourceType> <DatasourceName> on <ServerName>. Although no data is lost, you must rebuild the catalog to access the data of the backup job.No user action is required.
3313 Verification is complete for the following tapes in <LibraryType> <Library>: <MediaList> No user action is required.
3314 The recovery job is paused because the required tape is not available in <LibraryType><Library>. Insert the required tape in the library through the I/E port or by unlocking the library door. If you insert the required tape without using the Add tape (I/E port) or Unlock Door actions on the Libraries tab in the Management task area, click Continue Job in the Details section of this alert.
3315 <TaskName> is paused because the required tape <MediaLabel> is not available in the library <LibraryType> <Library>. Insert the tape with label <MediaLabel> in the library through the I/E port or by unlocking the library door. If you insert the required tape without using the Add tape (I/E port) or Unlock Door actions on the Libraries tab in the Management task area, click Continue Job in the Details section of this alert.
3316 The detailed inventory of tape failed for the following reason: <reason> No user action is required.
3317 Data verification of <DatasourceName> on tape <MediaList> in<LibraryType> <Library> found data integrity issues on the following files:

<TempListOfFiles>
No user action is required.
3500 Your search returned more than 250 results. Only 250 results can be displayed.Use the search controls to refine your search.
3598 This action will set this DPM's ownership on PSServerName>. This will result in the backup or recovery jobs for <PSServerName> on the DPM server ServerName> to fail.

Do you want to set ownership?
No user action is required.
3599 This action will set this DPM's ownership on PSServerName>. This will result in:
  1. Backup or recovery jobs for PSSeverName> on the DPM server ServerName> to fail.
  2. Backup or recovery jobs currently running on <PSSeverName> to be canceled.

Do you want to set ownership?
No user action is required.
3600 This action will rerun the selected job. Do you want to run this job again? No user action is required.
3601 This action will cancel the selected job. Do you want to cancel this job? No user action is required.
3602 This action will start a new recovery job for the failed recoveries. Do you want to continue?No user action is required.
3603 To cancel pending replica creation for <VolumeName> on <ServerName>, remove all members from the protection group <ProtectedGroup> that reside on this volume.To reschedule replica creation, add the members back to the protection group.
3604 The protection group configuration has changed and therefore this job cannot be rerun.In the Monitoring task area, on the Jobs tab, rerun this job.
3605 This job cannot be rerun because the data is not valid. To retry, in the Recovery task area, copy the data to tape by using the Recovery Wizard.
3606 This job cannot be rerun because the data is not valid. To retry, in the Recovery task area, in the Actions pane, click Verify data.
3607 This job cannot be rerun because the data is not valid. To retry, in the Recovery task area, re-catalog the tape's contents.
3608 Rerunning this job will back up this data source to a new tape. If you want all data sources in this protection group to be backed up to the same tape, click the Alerts tab, select one of the backup to tape failure alerts for this protection group, and then in the Details section of this alert, click Rerun backup to tape job.

Do you want to back up this data source to a new tape?
No user action is required.
3609 This job cannot be rerun because the protection group associated with it has been modified.No user action is required.
3610 Inactivating these alerts will also change protection status to OK in the Protection task area and the alerts will be resolved in Operations Manager. Do you want to inactivate the selected alerts?No user action is required.
3611 The job cannot be rerun because a dependent job is still running for a data source that is a part of this Windows SharePoint Services data source.Retry the operation when the dependent jobs have completed for all dependent data sources.
3700 An incompatible version of the database was detected. DPM cannot open DPM Administrator Console.Restore a valid database by using the steps described in the DPM 2010 Operations Guide, and then retry the operation.
3750 Version <DatabaseVersion> of the DPM database and version <BinariesVersion>of the DPM application are not compatible. Restore a valid database using the steps described in the DPM 2010 Operations Guide, and then retry the operation.
3751 The evaluation copy of DPM has expired. You must purchase a DPM license. For details about obtaining a DPM license, see the Announcing the Data Protection Manager (DPM) Evaluation VHD topic on the Microsoft System Center Data Protection Manager website.
3752 DPM could not find the MSDPMTrustedMachines security group. Either this group has been deleted or the entry is corrupt.Uninstall DPM, and then re-install DPM to recreate the security group.
3753 The version of the DPM database installed on this computer is later than the version of the DPM application.To continue using DPM, you must install any service packs or hotfixes that were part of your previous DPM installation.
3754 DPM Administrator Console can be opened only by a user belonging to a domain. Log on using a domain user account, and then try again.

back to Contents

Error codes 4000-5999

Error CodeMessageAdditional Information
4001 There is insufficient disk space on system volume SystemDrive to complete the installation.To continue with the installation, free up SystemDiskSpaceRequired MB of disk space on the system volume.
4002 The SQL Server Reporting Services installation is not valid because it is installed on a computer on which Internet Information Services (IIS) or ASP.Net is not installed.Uninstall SQL Server 2008, and then run DPM Setup again to install the prerequisite software.
4003 The installation of Reporting Services is not correctly configured or no instance of Reporting Services is linked to InstanceName of SQL Server.
  1. To use the local dedicated InstanceName instance with DPM, uninstall SQL Server and run the program again.
  2. To use the option of installing DPM with an existing instance of SQL Server, make sure that the Reporting Services instance is also installed and linked correctly. For details, refer to DPM Setup Help.
4005 DPM found the following databases that were created by an earlier installation of SQL Server Reporting Services: CommaSeparatedDatabaseName. Setup will delete these databases.
4006 Service Name is running under Credentials credentials. Name must run under local user credentials. DPM Setup will change the credentials to a local user account.
4007 Service Name is not installed. The Prerequisite installation is not valid.Uninstall Prerequisite and then run the program again.
4012 The Name service is running under Credentials credentials. We recommend that the service run under the NT Authority\NETWORK SERVICE account.In the Reporting Services Configuration tool, choose 'Service account', and then change the settings to the built-in Network Service account for %SqlInstance; instance of SQL Server 2008.
4015 You installed DPM protection agents on several computers. We recommend that you uninstall them before proceeding.In DPM Administrator Console, click Management on the Navigation bar. On the Agents tab, select the agents, and then click Uninstall.
4017 DPM database DpsDb is missing or corrupt. If you are performing a clean installation of DPM, you must delete the DPM database before you run Setup. If you are upgrading or repairing an existing installation of DPM, you must restore a valid DPM database, and then proceed with Setup.
4019 There is an existing DPM database in the SqlInstance instance of SQL Server. DPM cannot be installed on an existing database.In SQL Server Management Studio, delete the DpsDb database, and then run the program again. If you need to reuse an older DPM database, back up the database and restore it after completing the DPM installation.
4020 DPM Setup detected several existing protection groups. In DPM Administrator Console, in the Protection task area, remove the groups from protection, and then run DPM Setup again.
4021 You cannot proceed because Active Directory Domain Service is not accessible. Verify that the computer is joined to a domain, that DNS is correctly configured, and that you are logged on as a domain user with administrator privileges and run the program again.
4023 The Prerequisite installation failed. All changes made by the %Prerequisite; installation to the system were rolled back.Manually install Prerequisite. For instructions, see Manually Installing Prerequisite Software in the DPM 2012 Deployment Guide.
4024 The Prerequisite installation failed. All changes made by the Prerequisite installation to the system were rolled back. Manually install Prerequisite. For instructions, see Manually Installing Prerequisite Software in the DPM 2012 Deployment Guide.
4025 The Prerequisite configuration failed. Use Add or Remove programs in Control Panel to uninstall Prerequisite. After uninstalling Prerequisite run DPM Setup again.
4026 DPM Setup failed to configure the service ServiceName. Use Add or Remove Programs in Control Panel to uninstall DPM. After uninstalling, run DPM Setup again.
4027 DPM Setup was unable to collect information about volumes in the storage pool because access to the database was denied.Manually delete the volumes allocated to the storage pool or format the disks.
4028 Setup was unable to delete the DbName database. Manually delete the database using SQL Server Management Studio.
4029 Setup was unable to delete the schedules from the master database. Open SQL Server Management Studio, and connect to the DPM instance of SQL Server. Expand the instance of SQL Server, browse to SQL Server Agent, and then in Jobs, delete the ScheduleCategory category.
4030 Setup was unable to remove reports deployed with SQL Server Reporting Services.If you are reinstalling DPM on this computer, no action is necessary. If you are not reinstalling DPM, you must uninstall SQL Server 2008 to remove the reports.
4031 The computer MachineName could not be removed from the intranet security zone settings in Internet Explorer.In Internet Explorer, on the Tools menu, click Internet Options. In the Internet Options dialog box, on the Security tab, click Local intranet, click Sites, then click Advanced, and then remove computer MachineName from the intranet zone.
4032 DPM could not delete the AccountName user account. Manually delete account AccountName.
4033 DPM Setup could not remove the DPM Administrator Console shortcuts from: CommaSeparatedShortcutLocations. Manually delete the DPM Administrator Console shortcuts.
4034 DPM Setup could not delete service ServiceName. Manually delete service ServiceName. On the Administrative Tools menu, click Services.
4035 DPM Setup could not delete the GroupName group on computer MachineName. Delete the group manually. On the Administrative Tools menu, click Computer Management. Expand Local Users and Groups, and then click Groups. Right-click GroupName, and then click Delete.
4036 The DPM database was removed; however, DPM could not remove database files DataFilesCompleteLocation. Delete the database files manually.
4037 To finish deleting service ServiceName, you must restart the computer.Restart your computer.
4038 DPM Setup was unable to unmount the volumes from VolumesDir. Manually unmount the volumes using Disk Management.
4039 This computer has less than the recommended amount of memory for optimal performance of DPM. The recommended amount of memory is 2 GB.Add more memory to this computer or install DPM on a different computer.
4040 DPM Setup has detected that this computer is a domain controller. Make sure that you have followed the steps given in the link below before proceeding with the DPM Setup.
4041 The instance provided is not a SQL Server 2008 instance. Please provide a SQL Server 2008 SP1 instance.No user action is required.
4042 ValueEntered is not a valid value. The maximum is MaximumSize Unit. Install SQL Server 2008 Service Pack 1 or higher and try again.
4045 DPM Setup was unable to set permissions on folder DirectoryPath. Verify that the folder DirectoryPath is a valid location and that the current user has access to the location.
4046 DPM cannot delete FileName. Verify that the current user has permissions to delete the file.
4047 DPM Setup was unable to configure service SetupServiceName. Review the error details, take the appropriate action, and then try running DPM Setup again.
4049 The message text as it is given in the event log; do not add to or edit the message content.This section discusses how the user can fix the problem. If no user action is needed (for example, as with success messages), use the following standard phrase:

No user action is required.
4050 The message text as it is given in the event log; do not add to or edit the message content.This section discusses how the user can fix the problem. If no user action is needed (for example, as with success messages), use the following standard phrase:

No user action is required.
4051 There is insufficient disk space on the program files volume BinaryDrive to complete the installation. To continue with the DPM installation, free up BinaryDiskSpaceRequired MB of disk space on the volume.
4052 You cannot install DPM on a server if a DPM protection agent has been installed it.No user action is required.
4053 DPM Setup was unable to remove the protected computers from the DComUsersGroup group. Delete the protected computers from the group. On the Administrative Tools menu, click Computer Management. Expand Local Users and Groups, and then click Groups. Click Distributed COM users in the right pane and remove the entries for the protected computers from this group.
4055 DPM Setup was unable to remove DPM and the protection agent from the Windows Firewall exceptions list.If Windows Firewall is enabled, remove DPM and the protection agent from the exceptions list. In Control Panel, click Windows Firewall, click the Exceptions tab, and then delete Microsoft System Center Data Protection Manager 2010 and the Microsoft System Center Data Protection Manager 2010 Replication Agent from the list of exceptions.
4056 DPM Setup was unable to add DPM to the Windows Firewall Exceptions. Review the error details. In Control Panel, click Windows Firewall, and on the General tab, verify that the Don't allow exceptions option is unchecked. Use Add or Remove Programs in Control Panel to uninstall DPM and then run DPM Setup again.
4057 There is insufficient disk space on the database volume DatabaseDrive to complete the installation. To continue with the installation, free up DatabaseDiskSpaceRequired MB of disk space on the volume.
4058 DPM requires the Microsoft$DPM$ instance of SQL Server. None of the existing SQL Server installations have the name Microsoft$DPM$. Setup will install the Evaluation Edition of SQL Server 2008, which will expire in 180 days.To avoid expiration of SQL Server 2008, exit Setup and install the SQL Server 2008 licensed retail copy, or upgrade to SQL Server 2008 within 180 days. To properly configure the SQL Server 2008 settings, see Manually Installing Prerequisite Software in the DPM 2012 Deployment Guide.
4059 DPM Setup installs the Evaluation Edition of SQL Server 2008 which expires 180 days after installation.To avoid expiration of SQL Server 2008, exit Setup and install the SQL Server 2008 licensed retail copy, or upgrade to SQL Server 2008 within 180 days. To properly configure the SQL Server 2008 settings, see Manually Installing Prerequisite Software in the DPM 2012 Deployment Guide.
4060 Please install SQL Server Reporting Services SP1 manually. For instructions, see Troubleshooting Setup in the DPM Setup Help.
4061 Setup could not automatically install SQL Server 2000 Reporting Services. All changes made by the SQL Server 2000 Reporting Services installation to the system were rolled back.From Control Panel, uninstall DPM by using the Add or Remove Programs item. Then, manually install Reporting Services and Reporting Services SP1. For instructions, see Troubleshooting Setup in the DPM Setup Help.
4062 Setup could not automatically install SQL Server 2000 Reporting Services. All changes made by the SQL Server 2000 Reporting Services installation to the system were rolled back.From Control Panel, uninstall DPM by using Add or Remove Programs. Next, manually install Reporting Services and Reporting Services SP1. For instructions, see Troubleshooting Setup in the DPM Setup Help.
4065 You did not specify the user name. Specify a user name.
4066 You did not specify a company name. Specify a company name.
4067 The number of DPM licenses must be greater than or equal to zero. Specify a number for the DPM licenses greater than or equal to zero.
4068 Installation source Folderpath for installing prerequisites either does not exist or cannot be accessed or Setup cannot find one or more prerequisites at the location.Make sure that the DPM installation DVD is copied correctly and re-run Setup.
4069 The input InputParameterTag is mandatory. Specify a valid input InputParameterTag.
4070 The prerequisite check failed with errors. Review the errors in the DPM setup log file SetupLogFile. Resolve the errors, and then run DPM Setup again.
4071 DPM Setup could not delete the DPM Administrator Console shortcut from: CommaSeparatedShortcutLocations. Please delete the shortcuts manually.
4072 The specified path FileName is invalid. Specify a valid path and verify that the path is accessible.
4073 The command line argument CommandlineArgument is invalid. See Installing DPM in DPM Setup Help.
4074 The path FileName exceeds MaxLimit characters. Choose a path with a shorter length.
4075 The command line argument CommandlineArgument is already specified.See Installing DPM in DPM Setup Help.
4076 The value for CommandlineArgument was not specified. See Installing DPM in the DPM Setup Help.
4077 DPM is not installed on this computer. Run DPM Setup from the DPM product DVD.
4078 DPM is already installed on this computer. To uninstall DPM, use Add or Remove Programs in Control Panel.
4079 DPM is not installed on this computer. To install DPM, see Installing DPM in DPM Setup Help.
4080 No IN file is specified in the command line. See Installing DPM in DPM Setup Help.
4081 DPM configuration failed. Refer to the Troubleshooting section of DPM Setup Help.
4082 DPM cannot start service SetupServiceName. Start the service manually. On the Administrative Tools menu, click Services. Right-click SetupServiceName, and then click Start.
4083 DPM setup could not configure agents. Refer to Troubleshooting section of DPM help.
4084 DPM setup could not configure SQL Server 2008 Reporting Services. Refer to Troubleshooting section of DPM help.
4085 DPM setup could not extract the prerequisites. Refer to Troubleshooting section of DPM help.
4086 DPM has been successfully installed. However, DPM Setup could not delete the extracted folder FolderPath. Delete folder FolderPath manually.
4087 DPM Setup could not delete the extracted folder Folderpath. Delete folder FolderPath manually.
4091 DPM Setup could not determine the edition of SQL Server used in the current installation of DPM.If the current installation of DPM uses an expired instance of the Evaluation Edition of SQL Server 2008, you must manually upgrade to the retail edition of SQL Server 2008. For instructions, see the DPM 2012 Deployment Guide. For more information about this error, see the application event log.
4093 DPM Setup has detected that the current installation of DPM uses the Evaluation Edition of SQL Server 2000 Reporting Services. Setup will upgrade to the retail edition of SQL Server 2000 Reporting Services as part of the upgrade of DPM.No user action is required.
4094 DPM Setup could not determine the edition of SQL Server 2008 Reporting Services used in the current installation of DPM.Verify that the Report Server and World Wide Web Publishing services are running: In Control Panel, click Administrative Tools, click Services, and check the Status column for each service.
4095 DPM Setup has detected that the current installation of DPM uses an expired instance of the Evaluation Edition of SQL Server 2000 Reporting Services.Manually upgrade to the retail edition of SQL Server 2000 Reporting Services, and then run DPM Setup again. For instructions for upgrading Reporting Services, see the DPM 2012 Deployment Guide.
4097 DPM Setup was unable to remove the following registry keys: CommaSeparatedRegKeys. Delete the registry keys using Microsoft Registry Editor.
4300 DPM Setup could not delete the DPMRA service. Delete the DPMRA service manually. At the command prompt, type "sc delete DPMRA".
4306 DPM Setup is unable to use the credentials provided to log on as <UserName>. Review the error log for details. Verify that the Remote SQL Server administrator credentials you provided are correct and that they have logon permissions on the local computer.
4307 DPM Setup is unable to connect to the specified instance of SQL Server. Possible Cause

Remote connection to the computer running SQL Server is disabled.

Resolution

To enable the remote instance of SQL Server, do the following:
  1. From the Start menu, point to All Programs, point to Microsoft SQL Server 2008, point to Configuration Tools, and then click SQL Server Configuration Manager.
  2. In SQL Server Configuration Manager, in the console pane, expand SQL Server Network Configuration, and then select the network protocol for the DPM named instance.
  3. In the Details pane, if TCP/IP is disabled, right-click TCP/IP and click Enable.


Possible Cause

The SQL Server Browser service is disabled.

Resolution

To start the SQL Server Browser service, do the following:
  1. In SQL Server Configuration Manager, in the console pane, click SQL Server Services.
  2. In the Details pane, right-click SQL Server Browser, and then click Properties.
  3. In the SQL Server Browser Properties dialog box, on the Service tab, select Automatic from the Start Mode drop-down list, and then click OK.

Note

By default, Microsoft SQL Server sets the SQL Server Browser service to start automatically.

Possible Cause

Make sure that the remote instance of SQL Server is in the following format:

<Computer name>\<Instance name>

Note

Only use <Computer name> for the default instance.

Possible Cause

There is no network connectivity between the DPM server and the computer running SQL Server.

Resolution

Make sure there is a connection between the DPM server and the computer running SQL Server.
4309 The SQL Server 2008 installation failed. All changes made by the SQL Server 2008 installation to the system were rolled back.Manually install SQL Server 2008. For instructions, see "Manually Installing Prerequisite Software" in the DPM 2010 Deployment Guide.
4310 The SQL Server 2008 installation failed. Review the SQL Server installation log file for failures, and then take the appropriate action.
4323Error: DPM Setup failed to add a user to the local group. Review the error details, take the appropriate action, and then run DPM Setup again.

ID: 4323. Details: A member could not be added to or removed from the local group because the member does not exist.
This issue can occur if the environment has a disjointed namespace (that is, if the domain has different NetBIOS and DNS names). For more information about how to resolve this issue, please see the following:

System Center 2012 R2 Data Protection Manager install fails and generates ID: 4323: "A member could not be added"
4324 You cannot choose the instance <InstanceName> on the local machine. Specify a different instance to install DPM or choose the option to let DPM install its own SQL Server instance. If DPM's SQL Server instance already exists, it will be reused.
4350 DPM upgrade marked replicas as invalid. No user action is required.
4376 You cannot install the DPM Management Shell on a DPM server. No user action is required.
4386 The SQL Server installation failed because a restart was pending on this computer.Restart the computer and then start DPM Setup again.

back to Contents

Error codes 6000-7999

Error CodeMessageAdditional Information
6002 Set the permissions for the SYSTEM account to allow Full Control of the item. Set the permissions for the SYSTEM account to allow Full Control of the item.
6003 DPM cannot access the path FileName because the SYSTEM account has been denied permission.Set the permissions for the SYSTEM account to allow Full Control of the item.
6012 DPM cannot access mount points under the path FileName because the SYSTEM account has been denied permission.Set the permissions for the SYSTEM account to allow List Folder Contents and Read for items in the specified path.
6013 DPM cannot access mount points under the path FileName because the SYSTEM account has been denied permission.Set the permissions for the SYSTEM account to allow List Folder Contents and Read for items in the specified path.
7001 The operating system on target computer is not a valid client operating system.No user action is required.
7002 The computer could not be found in Active Directory Domain Services. No user action is required.
7003 The selected data sources cannot be added to the same protection group. A protection group must have either client data sources or other data sources.No user action is required.
7004 The option Name is not supported for client computers. To specify the folders that need to be backed up, use Name. For more details, run get-help Name.
7005 The parameter Name cannot be used while configuring protection of client computers.Refer to cmdlet help for more details.
7006 The parameter Name cannot be used while configuring protection of the selected data source.Refer to cmdlet help for more details.
7007 Synchronization frequency specified is invalid. You can only set synchronization frequency to 1, 2, 4, 6, 12 or 24 hours.No user action is required.
7009 Immediate or scheduled initial replication for client computers is not supported. The initial replication will happen as and when the client computers connect to the DPM server's network.No user action is required.
7010 The computer Name is being protected as server. It cannot be protected as client simultaneously.No user action is required.
7011 The option Name is not supported for computers protected as clients. No user action is required.
7012 The computer Name is being protected as client. It cannot be protected as server simultaneously.No user action is required.
7013 Some of the selected computers could not be added. To view the list of computers that could not be added, click the "Failed to add machines" link below the list of selectable computers.No user action is required.

back to Contents

Error codes 23000+

Error CodeMessageAdditional Information
23043 DPM has unexpectedly reached the end of the tape MediaLabel. This could be because the tape was tampered with.If you have another copy of this tape, then retry recovery using the copy.
23044 Rescan cannot be performed because DPM is currently performing other operations on the server.Wait for the other operations to complete, and then retry this operation.
23045 DPM failed to move one or more tapes to the I/E port slots.
  1. Check to see that the library door is locked and that the I/E port is retracted.
  2. Check to see that there are sufficient free I/E port slots in the library.
24003 The tape is managed by another DPM server. No user action is required.
24007 Tape <MediaLabel> cannot be marked as a cleaning tape because it is not a cleaning tape.No user action is required.
24008 DPM cannot complete the requested operation on tape <MediaLabel> because this tape is being used by another job.Retry the operation later.
24014 The library lacks power or the cables are not connected properly. To resolve this error, do the following:
  1. Make sure that the library is turned on.
  2. Make sure that data connection and power cables are connected properly.
  3. Open Computer Management and, in Device Manager, verify that the library is displayed.
24015 The tape is stuck in the library autoloader. Remove the tape from the library autoloader. Consult the documentation for your hardware for instructions on troubleshooting tape errors. When the tape is repaired, run the library job again.
24017 The <LibraryType> <Library> drive information needs to be refreshed.In the Management task area, On the Libraries tab, select the library, and then, in the Actions pane, click Rescan.
24018 The drive cleaning failed or timed out. Change the cleaning tape, and in the Management task area, on the Libraries tab, in the Actions pane, select the drive, and then click Clean.
24019 Drive <DriveName> in <LibraryType> <Library> needs servicing.Contact product support for your hardware to have the drive serviced. You should also review all protection groups to identify if the absence of this drive requires changes to drive allocations.
24021 DPM attempted to move a tape to <ElementType> <ElementName> but this <ElementType> was in use. DPM may not be in synch with the current state of the library<Library>. To resolve this error, do the following:
  1. In the Management task area, on the Libraries tab, select the library <Library>, and then, in the Actions pane, click Inventory.
  2. If the <ElementType> contains a tape, remove this tape by using the front panel of your library.
24022 The <ElementType> <ElementName> did not contain a tape when DPM expected it to. DPM might not be in synch with the state of the<LibraryType> <Library>. In the Management task area, click the Libraries tab select the <LibraryType> <Library>, and then, in the Actions pane, click Inventory library.
24023 The library <Library> mandates that when a tape is dismounted, it should be moved back to the slot it was originally mounted from. However, slot<SlotName> is not empty. To resolve this error, do the following:
  1. Remove the tape in slot <SlotName> by using the front panel of your library.
  2. In the Management task area, click the Libraries tab, and then, in the Actions pane, click Inventory library run an inventory
24024 A library with the same name is already attached to this server. Choose a different name for the library.
24025 The operation cannot be performed on <LibraryType> <Library> because it does not have any I/E ports. No user action is required.
24026 Operation cannot be performed because DPM Administrator Console is not synchronized with the actual state of the library.Close and then reopen DPM Administrator Console to synchronize it with the actual state of the library.
24027 The operation failed because the slot <SlotName> in library <Library>was empty. This tape is currently located in <MediaLocationType> <MediaLocationInfo>. Use the front panel of your library to move the tape from its current location to the slot specified above.
24029 Tape erase operation was skipped because <LibraryType> <Library> does not support tape erase. No user action is required.
24031 DPM was unable to re-catalog the tape in <MediaLocationType> <MediaLocationInfo>in <LibraryType> <Library> because this tape has not been identified.In the Management task area, click the Libraries tab, and then, in the Actions pane, click Inventory library. Then, select the tape <MediaLabel>, and then click Identify unknown tape.
24033 A detailed inventory is not performed on the tape <MediaLabel> because it is already known to this DPM server.No user action is required.
24034 DPM could not reserve the I/E port resource because one of required resources is not accessible.Make sure that there are no pending alerts for the library. Also make sure that no I/E port slots have been left open; and if so, close the I/E port slots.
24036 The operation failed because the I/E port is currently in use. Retry this operation after the I/E port is free.
24037 DPM failed to erase the selected tape because the state of the <LibraryType><Library> as seen by DPM is inconsistent with the actual state of the library.Run a detailed inventory and a fast inventory.
24038 The barcode on the tape <MediaLabel> in <MediaLocationType> <MediaLocationInfo> appears to have changed since the last time it was inventoried in DPM.To resolve this error, refresh the tape bar code.
24039 Duplicate barcodes detected on tapes with labels <MediaLabel> and <MediaLabel>. To resolve this error, do the following:
  1. Remove the tapes from the library.
  2. Clear duplicate barcode information from DPM.
  3. Replace the barcodes on the tapes and then insert them back into the library.
  4. Inventory the library.
24040 DPM failed to re-catalog the imported tape <MediaLabel> because it has not been inventoried.In the Management task area, on the Libraries tab, click Inventory library, and then select the option to perform a detailed inventory.
24041 DPM failed to re-catalog the imported tape <MediaLabel> because the tape is blank.DPM can only re-catalog a tape that has valid data on it.
24042 DPM failed to re-catalog the imported tapes because they do not contain the catalog information.It is likely that your data spans multiple tapes and the catalog information is present on another tape. Insert all tapes associated with the backup, and then retry the operation.
24050 Failed to perform the operation since the tape < Media Label > is not available in <Library Type > < Library >. To resolve this error, do the following:
  1. In the DPM Administrator Console, click Monitoring on the navigation bar, and then click the Alerts tab. Check for any Free tape threshold reached alerts generated by the libraries. If such alerts are present, proceed to step 3.
  2. In the DPM Administrator Console, click Management on the navigation bar, click the Libraries tab, and then do the following:
    • Expand all library slots and check for any free or expired tapes. If there are none, proceed to step 3.
    • Check for any suspect tapes in the library. If suspect tapes are present, see the “Managing Suspect Tapes” section of How to Identify Tapes (http://go.microsoft.com/fwlink/?LinkId=185319).

  3. Insert new tapes into the library, and then run a Fast inventory action followed by an Identify unknown tapes action. In DPM Administrator Console, click Management on the navigation bar, click the Libraries tab, and make sure that the new tapes appear as free. Then, click Monitoring on the navigation bar, click the Alerts tab, and restart the failed jobs.
24051 Required tape resource <MediaLabel> is reserved by another task. Wait for the other task to complete, or cancel the ongoing operation. Retry the operation.
24052 DPM could not reserve the drive resource because one of required drive resources is not online or it needs cleaning or servicing.To resolve this error, do the following:
  1. View and resolve all alerts for the library and its drive(s). After resolving the alerts, retry the operation.
  2. In the Management task area, click the Libraries tab, and then, in the Actions pane, click Rescan. After the rescan operation has completed successfully, retry the operation.
24053 The required drive resource is reserved by another task. View and resolve all alerts for the library and drive, or wait for the other operations to complete. Retry the operation after resolving the alerts.
24054 Operation cannot be performed on the tape in <MediaLocationType> <MediaLocationInfo> because it is a cleaning tape. No user action is required.
24055 Operation failed because no usable drives were available in <LibraryType> <Library>. Either there is no drive online or all the drives need cleaning or servicing.To resolve this error, do the following:
  1. In the Monitoring task area, on the Alerts tab, resolve all alerts for this library and its drive. After resolving the alerts, retry this operation.
  2. If you have drives that are functioning correctly but that are currently being used, wait for the other operations to complete, and then retry this operation.
24056 <LibraryType> <Library> has been disabled by the DPM administrator.To resolve this error, do the following:
  1. If this library is associated with an active protection group, modify the protection group to associate it with another library to prevent tape-related jobs from failing.
  2. If you want to use this library for your tape-related jobs, in the Management task area, on the Libraries tab, select this library, and then, in the Actions pane, click Enable library.
24057 DPM failed to create a copy of the tape backup for <DatasourceType> <DatasourceName> on <ServerName> because the tape backup failed or did not run. To resolve this error, do the following:
  1. Retry the failed tape backup job by using the alert in the Monitoring task area.
  2. If your copy failed because the tape backup job did not run at all, in the Protection task area, click Create recovery point - tape to create a short-term tape backup.
  3. After successfully running the tape backup, retry the failed copy job by using the alert in the Monitoring task area.
24058 The certificate <CertificateName> with serial number <CertificateSerialNumber> issued by <CertificateIssuer> will expire by <ExpiryDate>. All encrypted backup jobs will fail after this time. To resolve this error, do the following:
  1. If this certificate contains a private key, move this certificate to the DPM recovery certificates collection for recovering data in the future, and replace this certificate with a valid certificate in the DPM backup certificates collection to continue further backups.
  2. If this certificate does not contain a private key, replace this certificate with a valid certificate in the DPM backup certificates collection to continue further backups.
24059 The certificate <CertificateName> with serial number <CertificateSerialNumber>issued by <CertificateIssuer> will expire by <ExpiryDate>. All encrypted backup jobs will fail after this time. To resolve this error, do the following:
  1. If this certificate contains a private key, move this certificate to the DPM recovery certificates collection for recovering data in future, and replace this certificate with a valid certificate in the DPM backup certificates collection to continue further backups.
  2. If this certificate does not contain a private key, replace this certificate with a valid certificate in the DPM backup certificates collection to continue further backups.

See "How to Encrypt Data in a Protection Group" in DPM Help for more information about certificates.
24060 Some certificates under DPMBackupStore have changed since the start of the job.Retry the job.
24061 Unexpected tape detected in <MediaLocationType> <MediaLocationInfo>in <LibraryType> <Library>. Check to see if there are any active alerts indicating suspect tapes. If such an alert exists, take the appropriate recommended action, and then retry this job.
24070 Some of the certificates under DPMBackupStore have expired. To resolve this error, do the following:
  1. If this certificate contains a private key, move this certificate to the DPM recovery certificates collection for recovering data in future, and replace this certificate with a valid certificate in the DPM backup certificates collection to continue further backups.
  2. If this certificate does not contain a private key, replace this certificate with a valid certificate in the DPM backup certificates collection to continue further backups.

See "How to Encrypt Data in a Protection Group" in DPM Help for more information about certificates.
24071 This DPM server is not authorized to read or write to this encrypted tape because there is no valid certificate in DPMBackupStore and DPMRestoreStore that can decrypt data.To resolve this error, do the following:
  1. Make sure that DPMBackupStore has the certificate to decrypt this tape.
  2. Use this tape on a DPM server that is authorized to read this tape.

See "How to Encrypt Data in a Protection Group" in DPM Help for more information about certificates.
24072 DPMBackupStore or DPMRestoreStore is not present. Use the Certificate Management console to recreate the DPMBackupStore and DPMRestoreStore Certificate stores.
24073 No certificate is present under DPMBackupStore. Add certificates to the DPM backup certificates collection.

See "How to Encrypt Data in a Protection Group" in DPM Help for more information about certificates.
24074 Failed to encrypt data on tape. Retry the job.
24075 Certificates on this tape are corrupt. Data on this tape cannot be recovered. No user action is required.
24076 The command sent by DPM to the library agent timed out. Retry the operation.
24077 DPM failed to mount the tape <MediaLabel> in drive <DriveName> for the library <Library>. This is because DPM is not synchronized with the current state of the library.In the Management task area, on the Libraries tab, select the library, and then click Inventory library. If enabled, select the Fast inventory option; otherwise, select the Detailed inventory option.
24078 No certificate with private key is present in DPMBackupStore. In the Certificate Management console, open certificate stores for the Computer account on the DPM server. Add a certificate that has the private key to the DPMBackupStore certificates collection.

See "How to Encrypt Data in a Protection Group" in DPM Help for more information about certificates.
24079 DPM encountered an error while attempting to parse the tape catalog information for tape<MediaLabel>. Retry the operation.
24080 DPM encountered a critical error while trying to parse the contents of the tape<MediaLabel>. This may be because the data on this tape is corrupt. To resolve this error, do the following:
  1. If you have another copy of this tape, use that to retry the recovery.
  2. If you do not have another copy of this tape, in the Recovery task area, select all required individual recoverable items, and then perform the recovery.

24082 DPM could not perform the operation because the specified recovery point does not exist.No user action is required.
24083 Recovery failed for <DatasourceType> <DatasourceName> on <ServerName>. Hardware snapshots of the DPM replica and recovery point volumes are not mounted on the protected computer for SAN recovery.Use your SAN software to take hardware snapshots of the DPM replica and recovery point volumes, and to mount them on the protected computer.
24084 The tape in <LibraryType> <Library> at <MediaLocationType><MediaLocationInfo> has been written to by another tape backup application using an unsupported physical block size.To resolve this error, do the following to erase the contents of the tape:
  • In DPM Administrator Console, in the Management task area, click the Libraries tab, select the tape, and then click Erase tape. After erasing the tape, DPM can use it for backups.

Note

If you have a stand-alone tape drive, you might have to erase the tape by using a tool other than DPM.
24085 DPM cannot start a new thread. Check the system memory and CPU utilization.
24086 DPM failed to dismount the tape <MediaLabel> in drive <DriveName> for the library <Library>. This is because DPM is not synchronized with the current state of the library.In the Management task area, on the Libraries tab, select the library, and then, in the Actions pane, click Inventory library. If enabled, select the Fast inventory option; otherwise, select the Detailed inventory option.
24088 Drive <DriveName> in <LibraryType> <Library> is not zoned properly.Make sure that only drives of the <LibraryType> <Library> are visible to the DPM server and not the changer.
24089 <LibraryType> <Library> connected to <MachineName> is offline because none of its drives are available. To resolve this error, do the following:
  1. Make sure that drives of this library are zoned properly.
  2. Make sure that all drive related alerts for this library are resolved.

24090 The global DPMDB database is not accessible. To resolve this error, do the following:
  1. Make sure that the global DPMDB database is accessible.
  2. Make sure that the instance of SQL Server of the global DPMDB database is running.
  3. Make sure that the network connection to the computer hosting the global DPMDB database is properly configured.
  4. Make sure that the SQL Browser service is running on the global DPMDB database computer.
  5. Make sure that the MSDTC service is running on this DPM server and the global DPMDB database computer.

24091 The global DPMDB database is not accessible. To resolve this error, do the following:
  1. Make sure that the global DPMDB database is accessible.
  2. Make sure that the instance of SQL Server of the global DPMDB database is running.
  3. Make sure that the network connection to the computer hosting the global DPMDB database is properly configured.
  4. Make sure that the SQL Browser service is running on the global DPMDB database computer.
  5. Make sure that the MSDTC service is running on this DPM server and the global DPMDB database computer.

25001 Rescan cannot be performed at this moment because DPM is performing other operations on the<LibraryType> <Library>. Wait for the current library operations to complete, and then retry this operation.
25002 The tape in <LibraryType> <Library> at <MediaLocationType><MediaLocationInfo> appears to be a cleaning tape. However, this tape is not marked as a cleaning tape.In the Management task area, on the Libraries tab, select this tape, and then click Mark as cleaning tape.
25005 The cleaning operation for drive <DriveName> on library <Library> took longer than expected. The cleaning operation may have failed. To resolve this error, do the following:
  1. If supported, check the front panel of your library to verify that this cleaning operation completed successfully.
  2. If the cleaning operation failed, try changing the cleaning tape, and then run the cleaning job again.

25009 DPM is not synchronized with the current state of your library. Jobs running on the<LibraryType> <Library> can potentially fail. In the Management task area, on the Libraries tab, click Inventory library. If available, select the Fast Inventory option, otherwise, select the Detailed Inventory option.
25010 DPM tried to access <ElementType> <ElementName> on library <Library>. This <ElementType> does not exist. To resolve this error, do the following:
  1. In the Management task area, on the Libraries tab, click Inventory library to run inventory. If enabled, select the Fast inventory option; otherwise select the Detailed inventory option. This will update the library state as seen by DPM.
  2. Retry the operation after DPM has completed the inventory successfully.

25011 DPM failed to inventory the <LibraryType> <Library>. This is possibly due to a hardware issue.Refer to your hardware manual for troubleshooting steps.
25012 DPM is not synchronized with the current state of your library. Jobs running on the<LibraryType> <Library> can potentially fail. In the Management task area, on the Libraries tab, click Inventory library. If available, select the option to perform a fast inventory, otherwise, perform a detailed inventory.
25013 DPM detected that the drive <DriveName> does not appear to be installed correctly.Check the SCSI and bus mappings of the drive to make sure that the drive is mapped correctly. If you change any of the mappings, in the Management task area, on the Libraries tab, and then click Rescan.
25014 <LibraryType> <Library> is not ready. To resolve this error, do the following:
  1. Make sure that the library is turned on.
  2. Check for loose connections of data or power channels.
  3. Make sure that the library appears in Device Manager.
  4. Make sure that the door on the library is closed.
  5. Refer to your hardware manual for other troubleshooting steps.

25015 DPM detected that drive <DriveName> is not ready. To resolve this error, do the following:
  1. If the drive is being serviced, you can ignore this alert.
  2. Make sure that the drive is powered on.
  3. Make sure that the drive is connected properly.
  4. In Device Manager, if the drive is not enabled or is not visible, refer to your hardware manual for other troubleshooting steps.

25016 DPM failed to use the tape in <MediaLocationType> <MediaLocationInfo> because it appears to be a cleaning tape that is identified incorrectly as a backup tape.Verify if the tape in slot <MediaLocationType> <MediaLocationInfo> is a cleaning tape. If it is, in the Management task area, click the Libraries tab, select this tape, and then, in the Actions pane, click Mark as cleaning tape.
25017 DPM could not access drive <DriveName> because another application is currently using it.Wait until the other application to finish using the drive, or stop the other application.
25018 The cleaner media in <MediaLocationType> <MediaLocationInfo> has expired. Change the cleaning tape, and then run the cleaning job again.
30089 Operation failed on <TargetedServerName> as an unsupported Single Instance Store (SIS) file<FileName> was found on the source volume. To resolve this error, either change the file attributes or recover the entire virtual machine.
30101 DPM encountered a critical error while performing an I/O operation on the tape <Media Label> (Barcode - <Media Barcode>) in <Media Location Type><Media Location Info>. To resolve this error, do the following:
  1. Download and install the latest driver and firmware updates from the tape drive vendor.
  2. Many tape drive vendors also offer utilities that you can use to diagnose hardware problems.
  3. Clean and service the tape drive.


Modify the TapeSize registry value to match your tape size

When a tape reaches the end, some drivers incorrectly return a Device I/O error code instead of an End of tape reached code. To resolve this error, modify the value of the following registry subkey to match your tape size:

Registry location:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\Agent

DWORD name: TapeSize
Value data (in MBs): 00030000



Reduce the number of parallel write buffers

An errant driver might not handle multiple parallel write requests. To resolve this error, create and modify the following registry subkey to reduce the number of parallel write buffers that DPM uses:

Registry location:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\Agent

DWORD name: BufferQueueSize
Value data: 00000001


Caution

Serious problems can occur if you modify the registry incorrectly. These problems could require you to reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk. Always make sure that you back up the registry before you modify it, and that you know how to restore the registry if a problem occurs.
30111 The VSS application writer or the VSS provider is in a bad state. Either it was already in a bad state or it entered a bad state during the current operation.Make sure that the required licenses are installed on the server, and then retry the backup.

This can also occur if you are attempting to backup a virtual machine and the VHD file is located in the root of a CSV. To work around this issue, create a folder and move the VHD inside the folder.
30112 DPM encountered a retryable VSS error. Depending on which situation you were in when you encountered this error, the following sections describe how to resolve this error.

Volume Shadow Copy Service (VSS) error on a virtual machine

To resolve this error in this situation, take one or more of the following actions:
  • Make sure that the version of the Integration Components package on the virtual machine is up-to-date. On the host for the virtual machine, open Server Manager, expand Roles, click Hyper-V, and then in the Events list in the Summary area, look for a warning that the Integration Components package must be updated.
  • Make sure that all the writers on the virtual machine are in a stable state. On the virtual machine, open an elevated Command Prompt window, type vssadmin list writers, and then press Enter.
  • Make sure that there are no unresolved VSS errors on the virtual machine. On the virtual machine, open Server Manager, expand Diagnostics, expand Event Viewer, expand Windows Logs, and then click Application. Resolve any VSS errors that you find.
    • Expand Diagnostics, expand Windows Logs, and then review the Application and System events for resolution steps.
    • Expand Roles, click Hyper-V, and then, in the Summary area, review the Events list for resolution steps.



Creating a recovery point by using incremental backup for a computer that is running Exchange 2010, Exchange 2007, or Exchange 2003

Circular logging might be enabled on this data source. DPM 2010 does not support incremental backups for a computer that is running Exchange 2010, Exchange 2007, or Exchange 2003 on which Circular Logging is enabled.

To resolve this error in this situation, clear the Circular Logging check box, and then try to create the recovery point again.

The next incremental backup fails when an incremental backup is performed after you run ntbackup on the storage group.

Create a DPM full recovery point before performing an incremental backup.
30140 DPM tried to do a SQL log backup, either as part of a backup job or a recovery to latest point in time job. The SQL log backup job has detected a discontinuity in the SQL log chain for <DatasourceType> database <DatasourceName> since the last backup. All incremental backup jobs will fail until an express full backup runs. For backup failures

If you see this failure as part of a backup job, in the Protection task area, select the SQL Server database, click Create recovery point, and then run an express full backup. Alternately, you can wait for the next scheduled express full backup to run.

For recovery failures

If this failure occurs as part of a recovery job, then try to recover from another point in time. Review the Application Event Viewer logs on the computer running SQL Server for more details. Make sure that this database is not already protected by another backup application.
30146 Data consistency verification check failed for <ObjectName> of <DatasourceType> <DatasourceName> on <ServerName>.If you recently upgraded your Exchange server, copy them from that server to the DPM server. Contact your Exchange server administrator, and then verify the issue. You can recover the last known good backup to address the corrupted state.
30169 The operation failed for <DatasourceType> <DatasourceName> on <ServerName> because the data source is not available.To troubleshoot this issue, verify the following:
  1. The data source is online.
  2. The data source is not in a restoring state.
  3. The application VSS writer is running.
  4. The data source is accessible.
  5. The data source is not missing.
  6. If the data source is a member of a SharePoint farm, verify that it still exists in the SharePoint farm configuration. For more information on this error, go to Hyper-V Protection Issues.

30172The DPM job failed for SQL Server 2012 database <DBName> on <AGName> because the SQL Server instance refused a connection to the protection agent (ID 30172 Details: Internal error code: 0x80990F75).To resolve this issue, open the SQL Server management console, navigate to Properties -> General -> Readable Secondary for the Availability Group, and set both the primary and secondary server to 'Yes.'
30173 Execution of SQL command failed for <DatasourceType> <DatasourceName> on <ServerName> with reason: <Reason>.Check the Application Event Viewer logs on the instance of SQL Server for entries that were posted by the SQL Server service to find out why the SQL command may have failed. For more information, look at the SQL Server error logs.
30184 DPM cannot continue protection for <DatasourceType> <DatasourceName> on <ServerName>.In the Monitoring task area, resolve the "Unable to configure protection" alert for this data source, and then click the link that follows to retry the job.
30195 DPM has run out of free space on the recovery point volume and will fail synchronization for <DatasourceName> on <ServerName> in order to prevent existing recovery points from being deleted.Make sure that there are no pending recovery point volume threshold alerts that are active for this data source, and then rerun the job. DPM may have automatically grown the volume and resolved the alerts.
30214 DPM failed to create the backup. If you are backing up only System State, verify if there is enough free space on the protected computer to store the System State backup. On protected computers that are running Windows Server 2008, verify that Windows Server Backup (WSB) is installed and that it is not performing any other backup or recovery task.You can see the errors reported by WSB in the event log on the protected computer. For resolution actions and more information on these errors, go to Backup Operations.
30216 Windows Server Backup can truncate Exchange Server and SQL Server logs being protected by DPM.To resolve this error, do the following:
  • If you use Windows Server Backup to back up a volume, do this only by using the Backup Once Wizard.
  • If you use the Backup Schedule Wizard to perform scheduled backups, make sure that the volumes that are being protected by DPM do not contain application data such as Exchange Server mailbox stores or SQL Server databases.
  • Reconfigure Windows Server Backup. Then, in DPM Administrator Console, in the Protection task area, select the volume, click Create recovery point, and then, in the Actions pane, click Express full backup.

30229 DPM cannot create a backup because Windows Server Backup (WSB) on the protected computer encountered an error (WSB Event ID: <WindowsBackupEventID>, WSB Error Code: <WindowsBackupErrorCode>).For resolution actions and more information about the WSB error, go to Backup Operations.
30290 Failure occurred while adding one or more of the volumes involved in backup operation to snapshot set. Please check the event log on<ServerName> to troubleshoot the issue. To resolve this error, make sure that the Challenge-Handshake Authentication Protocol (CHAP) credentials that are needed to create hardware snapshots are correctly configured on the host computer that is running Hyper-V. For more information, refer to the documentation from your VSS hardware provider vendor.
32500There is insufficient disk space in the cache volume.To change the scratch location of the MABAgent service, follow these steps:
  1. Stop the Microsoft Azure Recovery Services Agent by running the following command at an elevated command prompt:
    Net stop obengine
  2. Copy the scratch folder to a different drive that has sufficient space.

    Note Required scratch space is at least 10 percent of the size of the data that is being backed up. (For example, backing up 100 gigabytes [GB] of data requires a minimum of 10 GB of free space in the scratch location.)
  3. Update the following registry entries with the new path of the scratch folder:
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Azure Backup\Config]<ScratchLocation>

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Azure Backup\Config\CloudBackupProvider]<ScratchLocation>
  4. Start the Microsoft Azure Recovery Services Agent by running the following command at an elevated command prompt:
    Net start obengine
For more information about scratch space size, please refer to the following document:

back to Contents

Properties

Article ID: 3041344 - Last Review: 08/28/2015 21:14:00 - Revision: 6.0

Microsoft System Center 2012 Data Protection Manager Service Pack 1

  • kbexpertiseinter kbinfo KB3041344
Feedback