System Center Data Protection Manager 2010 Troubleshooting Guide

System Center Data Protection Manager 2010
Troubleshooting Guide
Microsoft Corporation
Published: July 2010
Feedback
Send suggestions and comments about this document to dpmfdbk@microsoft.com.
This document is provided “as-is”. Information and views expressed in this document, including
URL and other Internet Web site references, may change without notice. You bear the risk of
using it.
Some examples depicted herein are provided for illustration only and are fictitious. No real
association or connection is intended or should be inferred.
This document does not provide you with any legal rights to any intellectual property in any
Microsoft product. You may copy and use this document for your internal, reference purposes.
You may modify this document for your internal, reference purposes.
© 2010 Microsoft Corporation. All rights reserved.
Microsoft, Active Directory, Hyper-V, SQL Server, Windows, Windows PowerShell, Windows
Server, and Windows Vista are trademarks of the Microsoft group of companies.
All other trademarks are property of their respective owners.
Contents
DPM 2010 Troubleshooting Guide.................................................................................................. 8
In This Section............................................................................................................................. 8
Diagnostic Process for Request Tracking and Error Tracing...........................................................8

Request Tracking......................................................................................................................... 8
Request Tracking Tuning Feature............................................................................................ 9
Error Tracing................................................................................................................................ 9
Error Tracing Tuning Feature................................................................................................... 9
Standard Troubleshooting Procedures.......................................................................................... 10

In This Section........................................................................................................................... 10
Verifying Status of the DPM Service.............................................................................................10
Checking Name Resolution........................................................................................................... 11
Identifying DNS Errors.................................................................................................................. 12

Additional Resources................................................................................................................. 13
Tools.......................................................................................................................................... 13
Resolving "Access Denied" Errors................................................................................................13
Troubleshooting DPM Installation Issues......................................................................................14

In This Section........................................................................................................................... 14
Troubleshooting Installation Issues...............................................................................................14
Troubleshooting Protection Agent Installation Issues....................................................................17
Troubleshooting Remote SQL Server Issues................................................................................23

Troubleshooting Error ID 4307.................................................................................................. 23
Troubleshooting Data Protection Issues.......................................................................................25

In This Section........................................................................................................................... 25
General Data Protection Issues.................................................................................................... 25
File Server Protection Issues........................................................................................................ 31
Exchange Server Protection Issues..............................................................................................32
SQL Server Protection Issues....................................................................................................... 38
Windows SharePoint Protection Issues........................................................................................44

Windows Server Backup Issues................................................................................................... 46
System Protection Issues............................................................................................................. 47
Mirrored Databases Issues........................................................................................................... 48
Virtual Server Protection Issues.................................................................................................... 49
Manual Replica Creation Issues................................................................................................... 50
Incompatible Filter Driver Errors................................................................................................... 52
Client Computer Protection Issues............................................................................................... 53
Hyper-V Protection Issues............................................................................................................ 54

Hyper-V Virtual Machine Protection Issues...............................................................................54
Troubleshooting Data Recovery Issues........................................................................................ 56

In This Section........................................................................................................................... 56
General Data Recovery Issues..................................................................................................... 56
Exchange Server Recovery Issues...............................................................................................57
SQL Server Recovery Issues........................................................................................................ 60
Windows SharePoint Recovery Issues......................................................................................... 61
Tape Library Recovery Issues....................................................................................................... 63
End-User Recovery Issues........................................................................................................... 63
Computers in Workgroups and Untrusted Domains Recovery Issues..........................................64

Computers in Workgroups and Untrusted Domains Recovery Issues.......................................64
Troubleshooting Tape Library Management Issues......................................................................65
Troubleshooting Reporting Issues................................................................................................ 68
Troubleshooting Performance Issues........................................................................................... 74

In This Section........................................................................................................................... 74
Network Bandwidth Issues............................................................................................................ 74
Troubleshooting Database Issues.................................................................................................74

Additional Resources for Troubleshooting Database Issues.....................................................79
Troubleshooting Job Status Issues............................................................................................... 80
Troubleshooting the DPM System Recovery Tool.........................................................................80
Troubleshooting Disaster Recovery Issues...................................................................................82

Troubleshooting General DPM Issues..........................................................................................82
DPM 2010 Error Code Catalog..................................................................................................... 86

Error Messages......................................................................................................................... 87
DPM Error Codes....................................................................................................................... 237

In This Section......................................................................................................................... 237
Reference................................................................................................................................ 238
Error ID: 319............................................................................................................................... 238

Error #319 — Data Protection Manager..................................................................................238
Explanation.............................................................................................................................. 239
User Action.............................................................................................................................. 239
Error ID: 324............................................................................................................................... 239

Explanation.............................................................................................................................. 240
User Action.............................................................................................................................. 240
Installing an agent by using DPM Management Shell:.........................................................240
Uninstalling an agent by using DPM Management Shell:.....................................................240
Upgrading an agent by using DPM Management Shell:.......................................................240
Error ID: 347............................................................................................................................... 241

Explanation.............................................................................................................................. 241
User Action.............................................................................................................................. 241
Error ID: 958............................................................................................................................... 242

Explanation.............................................................................................................................. 242
User Action.............................................................................................................................. 242
Error ID: 1243............................................................................................................................. 242

Error #1243 — Data Protection Manager................................................................................242
Explanation.............................................................................................................................. 243
User Action.............................................................................................................................. 243
Error ID: 3133............................................................................................................................. 244

Error #3133 — Data Protection Manager................................................................................244
Explanation.............................................................................................................................. 244
User Action.............................................................................................................................. 244
Error ID: 24050........................................................................................................................... 245

Error #24050 — Data Protection Manager..............................................................................245
Explanation.............................................................................................................................. 245
User Action.............................................................................................................................. 245
Error ID: 24084........................................................................................................................... 246
Explanation.............................................................................................................................. 246
User Action.............................................................................................................................. 246
Error ID: 30101........................................................................................................................... 247

Explanation.............................................................................................................................. 247
User Action.............................................................................................................................. 248
Modify the TapeSize registry value to match your tape size.................................................248
Reduce the number of parallel write buffers.........................................................................248
Error ID: 30111............................................................................................................................ 249

Error #30111 — Data Protection Manager...............................................................................249
Explanation.............................................................................................................................. 249
User Action.............................................................................................................................. 249
Error ID: 30300........................................................................................................................... 250

Explanation.............................................................................................................................. 250
User Action.............................................................................................................................. 250
DPM writer was unable to snapshot the replica of <data source>, because the replica is not
in a valid state (Validity: <Validity State>:..........................................................................251
DPM Writer has timed out waiting for replica to be free and available for snapshot.............251
DPM has run out of free recovery point space and will fail snapshots for <data source> in
order to prevent existing recovery points from getting recycled........................................251
DPM writer was unable to snapshot the replica of <data source>........................................251
Error ID: 30216........................................................................................................................... 251

Explanation.............................................................................................................................. 252
User Action.............................................................................................................................. 252
Error ID: 31224........................................................................................................................... 252

Explanation.............................................................................................................................. 253
User Action.............................................................................................................................. 253
Error ID: 32061........................................................................................................................... 253

Explanation.............................................................................................................................. 254
User Action.............................................................................................................................. 254
Error ID: 32062........................................................................................................................... 254

Explanation.............................................................................................................................. 255
User Action.............................................................................................................................. 255
Error ID: 32064........................................................................................................................... 255

Explanation.............................................................................................................................. 256
User Action.............................................................................................................................. 256
Error ID: 32065........................................................................................................................... 256

Explanation.............................................................................................................................. 257
User Action.............................................................................................................................. 257
Error ID: 32612........................................................................................................................... 257

Error #32612— Data Protection Manager...............................................................................257
Explanation.............................................................................................................................. 257
User Action.............................................................................................................................. 258
DPM 2010 Troubleshooting Guide
This content provides guidance for troubleshooting System Center Data Protection Manager
(DPM) 2010 issues.
In This Section
Diagnostic Process for Request Tracking and Error Tracing
Standard Troubleshooting Procedures
Troubleshooting DPM Installation Issues
Troubleshooting Protection Agent Installation Issues
Troubleshooting Data Protection Issues
Troubleshooting Data Recovery Issues
Troubleshooting Tape Library Management Issues
Troubleshooting Reporting Issues
Troubleshooting Performance Issues
Troubleshooting Database Issues
Troubleshooting Job Status Issues
Troubleshooting the DPM System Recovery Tool
Troubleshooting Disaster Recovery Issues
Troubleshooting General DPM Issues
DPM 2010 Error Code Catalog
DPM Error Codes
Diagnostic Process for Request Tracking and

Error Tracing
This topic explains the process for diagnosing request tracking and error tracing for System
Center Data Protection Manager (DPM) 2010.
Request Tracking
Every trace statement has a log task ID that DPM logs in the agent traces. The log task ID is a
globally unique identifier (GUID) that DPM generates for every task in the DPM engine. The log
task ID is sent as a parameter in every command to the agent. There is full tracking for each task
in the traces, which helps isolate traces for the job you want to trace. This is especially helpful
when there are many data sources that you are protecting.
8
Request Tracking Tuning Feature
The request tracking tuning feature is available in the DPM engine, the DpmRA service, and other
agent binaries. The feature is built into the binaries and it is always ON.
Error Tracing
Log error traces are put into a log file. These fixed sized error logs are retained for a specific
amount of time. The log file is written in normal text and is readable by the administrator. The
diagnostic information from these files is logged and can be collected by the Microsoft Platform
Support Reporting utility (MPSRPT) from the user's computer.
The log file helps administrators and Customer Service and Support (CSS) with firsthand
information instead of the error code that appears in DPM Administrator Console. This helps
categorize the failures more efficiently, and therefore reduces turnaround time.
Additionally, since DPM logs as much diagnostic information as possible along with the API that
has failed, the diagnostics and investigation can start before the user returns with a verbose log.
Error Tracing Tuning Feature

The error tracing tuning feature is built into the DPM engine, the DpmRA, DPMLA, DPMAC,
DpmBackup, and DpmWriter services. It is always ON and collects TRACE_ERROR level traces
into the log file by default.
The following table shows how to tune the various parameters that drive the tuning feature.
Parameter Overriding Registry Key Default Value Possible Values
Trace level TraceLogLevel TRACE_ERROR All valid trace level

flag combinations
Location TraceLogPath DPM install Path A valid existing
folder path
Max size of <binary>TraceLogMaxSize 5 MB A file size (total
each file disk space
consumed for this
binary’s log = size *
number of files to
retain)
Max number of <binary>TraceLogMaxNum 30 Any non-negative
files to retain number
<binary> = MSDPM (for engine), DPMRA (for RA), DPMLA (for LA), DPMAC (for AC),
DpmBackup (for DPM backup), DpmWriter (for DPM writer).
Note the following:
 The root path for the registry keys is HKLM\Software\Microsoft\Microsoft Data Protection
Manager.
 The trace level and trace log location setting is global across all binaries.
9
 The current log file number is tracked in the registry key HKLM\Software\Microsoft\Microsoft
Data Protection Manager: <binary>TraceLogNextNum (DWORD). This is an internal registry
key and we recommend that you do not manually modify it.
Standard Troubleshooting Procedures

The procedures in this section are basic troubleshooting procedures that are referenced in other
troubleshooting topics that appear in the DPM 2010 Troubleshooting Guide.
In This Section
Verifying Status of the DPM Service
Checking Name Resolution
Identifying DNS Errors
Resolving "Access Denied" Errors
Verifying Status of the DPM Service

The DPM service runs only when DPM jobs are being processed, and it stops automatically after
a job is completed. If the instructions for troubleshooting an issue direct you to verify the status of
the DPM service, follow these steps.
To verify status of the DPM service

1. On the DPM server, in Administrative Tools, open Services.
2. In Services, right-click the DPM service in the Details pane, and then click
Properties.
3. On the General tab, ensure that Startup type is set to Automatic.
4. To start the service, on the General tab, click Start.
If the DPM service starts successfully, the General tab displays the service status as
Started. If the DPM service is running normally, scheduled protection jobs and other
DPM jobs should start.
5. If the DPM service does not start, use Windows Event Viewer to look for possible
shutdowns of services on which DPM depends. The following services are of interest:
 DPM File Agent
 SQLAgent$MICROSOFT$DPM$ (SQL Agent)
 MSSQL$MICROSOFT$DPM$ (SQL Server)
 Virtual Disk Service (VDS)
 Volume Shadow Copy (VSS)
6. If you see a service shutdown event for any of these services, start the service and
10
ensure that the Startup type is set to Automatic.
7. If you cannot resolve the problem by enabling any disabled services listed in step 5, try
restarting the individual services:
a. Shut down individual services in the following order: VDS, VSS, SQL Agent,
SQL Server. The DPM service shuts down automatically.
b. Start the VSS service.
c. Start the DPM service. If the DPM service starts successfully, all dependent
services—VDS, SQL Agent, and SQL Server—will also restart.
8. If the DPM service still does not start, restart the Windows Server operating system.
If restarting the server does not fix the problem, a database failure might be causing
the DPM service to shut down. For information on troubleshooting database failures,
see Troubleshooting Database Issues.
9. If none of these solutions resolves the problem, contact Microsoft Product Support
Services for help. For information, see Microsoft Help and Support
(http://go.microsoft.com/fwlink/?linkid=45276).
Checking Name Resolution

Follow this procedure if the instructions for troubleshooting an issue direct you to check name
resolution.
To check name resolution

1. On the file server, run the ipconfig command. Note the Domain Name System (DNS)
suffix and Internet protocol (IP) address.
2. On the DPM server, ping the file server name to verify that the server name resolves to
the correct fully qualified domain name (FQDN) and IP address.
3. On the DPM server, run the ipconfig command. Note the DNS suffix and IP address.
4. On the file server, ping the DPM server name to verify that the server name resolves to
the correct FQDN and IP address.
If the information obtained by ping and by ipconfig for either the file server or the
DPM server is not correct, check the DNS client settings on that server.
Note
For instructions on using ping, see Using the ping command
(http://go.microsoft.com/fwlink/?LinkId=50821) in Windows Server 2003 Help.
For instructions on using ipconfig, see Ipconfig (http://go.microsoft.com/fwlink/?
LinkId=50823) in Windows Server 2003 Help.
11
Identifying DNS Errors
The DPM server and its protected computers cannot communicate reliably unless the Domain
Name System (DNS) is functioning properly. Use the following procedures to identify and resolve
DNS problems on either the DPM server or a protected computer:
 In the Services console, review the status of the following services and start them if they are
not already started:
 DNS Client
 TCP/IP NetBIOS Helper (if the intranet is NetBIOS-enabled)
 Verify that the Hosts file exists and that the correct path to the Hosts file is configured.
 Verify that
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\
REG_EXPAND_SZ: DataBasePath is set to %SystemRoot%\System32\drivers\*
 Verify that the Hosts file is located at %SystemRoot%\System32\drivers\*\hosts.
 Empty the following caches:
 To empty the DNS cache, run ipconfig /flushdns
 To empty the NetBIOS cache, run nbtstat -R and nbtstat -RR
 To empty the Address Resolution Protocol (ARP) cache, run arp –d *
 Verify the IP addresses of the DNS servers and Windows Internet Name Service (WINS)
server:
 Run ipconfig /ALL to obtain the IP addresses.
 Use the Ping and Tracert commands to check network connectivity to each IP address.
 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.
 Verify DNS Suffix Search List by running ipconfig /ALL.
 Check related settings by using Network Connections in Control Panel.
 Right-click the appropriate network connection for the LAN, and then click Properties.
 Select Internet Protocol (TCP/IP), and then click Properties.
 On the Internet Protocol (TCP/IP) Properties dialog box, click the Advanced button.
 Verify the settings on DNS and WINS tabs.
 Run nslookup using the debug and verbose options to see more detail related to the DNS
queries.
 Use Network Monitor to determine whether the correct DNS server responds to ping.
Additional Resources
For more information on troubleshooting DNS, see the following:
 Domain Name System Center (http://go.microsoft.com/fwlink/?LinkId=50838)
 How DNS Works (http://go.microsoft.com/fwlink/?LinkId=50839)
 Troubleshooting DNS (http://go.microsoft.com/fwlink/?LinkId=50840)
12
Tools
For more information on the following tools, see TCP/IP Tools and Settings
(http://go.microsoft.com/fwlink/?LinkId=50841).
 Arp: View and manage the ARP cache on the interfaces of the local computer.
 Ipconfig: Display current TCP/IP network configuration values, update or release Dynamic
Host Configuration Protocol (DHCP) allocated leases, and display, register, or flush DNS
names.
 Nbtstat: Check the state of current NetBIOS over TCP/IP (NetBT) connections, view and
update the NetBIOS name cache, and determine the names registered with WINS.
 Nslookup: Check records, domain host aliases, domain host services, and operating system
information by querying DNS servers.
 Ping: Send Internet Control Message Protocol (ICMP) Echo messages to verify IP
connectivity. Windows Server 2003 adds IPv6 parameters to the ping command.
 Tracert: Trace a path to a destination. Windows Server 2003 adds IPv6 parameters to the
tracert command.
Resolving "Access Denied" Errors

"Access Denied" errors that occur while DPM is performing a task that involves communication
with a protected computer often indicate a configuration problem on the computer. If you
experience an "Access Denied" error in a task that involves communication with the computers,
do the following:
 Verify that the system time on the DPM server and the protected computer is synchronized
with the system time on the domain controller.
 On a computer running Windows Server 2003 SP2, verify that the DPM server is a member
of the Distributed COM Users group and that the group has Distributed COM (DCOM) Launch
and Access permissions for the file server.
To verify group membership on the file server

1. In Computer Management, expand System Tools, expand Local Users and
Groups, and then click Groups.
2. In the Details pane, double-click the Distributed COM Users group.
3. Verify that the computer account for the DPM server is a member of the group.
To verify DCOM Launch and Access permission on the file server

1. In Administrative Tools, open Component Services.
2. Expand Component Services, expand Computers, right-click My Computer, and
then click Properties.
3. On the COM Security tab, under Access Permissions, click Edit Limits.
4. Verify that the Distributed COM Users group is allowed both Local Access and Remote
Access permissions.
13
5. On the COM Security tab, under Launch and Activation Permissions, click Edit
Limits.
6. Verify that the Distributed COM Users groups is allowed the following permissions:
 Local Launch
 Remote Launch
 Local Activation
 Remote Activation
Troubleshooting DPM Installation Issues

This section provides troubleshooting guidance on installation issues for installing and configuring
System Center Data Protection Manager (DPM) 2010.
In This Section
Troubleshooting Installation Issues
Troubleshooting Protection Agent Installation Issues
Troubleshooting Remote SQL Server Issues
Troubleshooting Installation Issues

The following table provides guidance for troubleshooting issues that may occur when you are
installing System Center Data Protection Manager (DPM).
DPM Installation Issues
Issue Possible Cause Resolution
Computer 1. Uninstall DPM 2010 using the

stops “Retain data” option.
working
2. Delete the DPM database.
when you
uninstall 3. Use Disk Management to delete
DPM 2010 the volumes created by DPM.
with the
“Remove
data”
option.
Windows Run Windows Installer Setup from
Installer 4. the \DPM2010\setup\redist folder.
5
installation
14
fails.
SQL Serve Summary.txt file contains the following: If the SQL Server Native Client is
r A network error occurred while installed on the computer, remove it,
installation attempting to read from the file: and then retry the DPM installation.
fails. C:\SQLSVR2008\x64\setup\x64\sqlncli10
_x64.ms
A DPM During DPM installation, Setup restarts To prevent an interruption, shut down
installation the Windows Management all other applications before you run
interrupts Instrumentation (WMI) service. If you are DPM Setup.
non-DPM running applications other than DPM and
application its prerequisite software on the DPM
s. server, you may experience an
interruption in the operation of those
applications while the WMI service is
restarted.
Error 810 If the DPM server is unable to connect to Verify that the DPM server can
or ID: the domain controller during installation, communicate with the domain
4315. The the DPM installation fails. controller. In addition, verify that the
trust DNS entries are for the domain
relationshi controller and that they are correctly
p between configured.
this
workstatio
n and the
primary
domain
failed.
Error 812. This problem occurs when both To resolve this issue, perform one of
Configurati SQL Server Reporting Services and the following tasks:
on of Windows SharePoint Services are  Uninstall Windows SharePoint
reports installed in the same Internet Information Services by using Add or Remove
failed. Services (IIS) application pool.
Programs, uninstall DPM, and
then install DPM again.
-Or-
 Configure a side-by-side
installation of SQL Server
Reporting Services and Windows
SharePoint Services. For
instructions, see Troubleshooting a
Side-by-Side Installation of
Reporting Services and Windows
SharePoint Services
(http://go.microsoft.com/fwlink/?
LinkId=50877).
Error 820. This issue occurs if the WMI repository is To resolve this issue, verify that the
Setup inconsistent. WMI repository is consistent by
15
cannot running Winmgmt /verifyrepository at the
query the command prompt. If it is inconsistent,
system resolve the issue and try the
configurati installation again.
on while
performing
the
prerequisit
e check on
Windows
Server
2008
operating
system.
DPM is The custom password filter software is Disable the custom password filter
unable to installed on the domain controllers. before you install DPM.
configure
the
Windows
Server
account
because
the
password
you
entered
does not
meet the
Group
Policy
requireme
nts.
Troubleshooting Protection Agent

Installation Issues
The following table provides troubleshooting guidance that supplements the specific error
messages that you may encounter during protection agent installation.
Before beginning the troubleshooting process, we recommend that you first try to manually install
the protection agents. For detailed instructions for installing the protection agents manually, see
Installing Protection Agents Manually (http://go.microsoft.com/fwlink/?LinkID=179676).
Protection Agent Installation Issues
16
SetDPMServer fails A DPM 2010 agent 1. Install the new protection agent.

with error code was installed on this 2. Perform SetDPMServer on the old agent.
0x80070534 and computer earlier, but
error message “No a SetDPMServer 3. Uninstall the old protection agent.
mapping between action was not 4. Do an agent upgrade.
account names and performed.
security IDs was
done.”
Protection agent  If there is an entry for DPM Protection Agent
upgrade fails. in the installed programs list, try upgrading the
agent by using DPMAgentInstaller.exe.
 If the previous step fails, uninstall the agent
from Programs and Features and install it
again by running DPMAgentInstaller
<DPMServerName>.
Error 300: The  Incorrect firewall To resolve this issue, do the following:
agent operation configuration  For firewall configuration requirements, in the
failed because it requirements on DPM Operations Guide, see Managing DPM
could not the DPM server. Servers (http://go.microsoft.com/fwlink/?
communicate with
the specified server.  The Remote LinkId=187199).
Procedure Call  For an unavailable RPC server, see Microsoft
(RPC) server is Knowledge Base article 224370,
unavailable. "Troubleshooting RPC Server is Unavailable
in Windows" (http://go.microsoft.com/fwlink/?
LinkId=45817).
Error 303: Agent  Another  Wait for the installation to complete, and then
operation with installation is retry the operation.
specified server running on the  Convert the boot volume to NTFS file system
failed. specified server. if you have sufficient space.
 The boot volume For more information about using the Convert
on the server is command for converting FAT volumes to
formatted as file NTFS, see Microsoft TechNet article Convert
allocation table (http://go.microsoft.com/fwlink/?
(FAT). LinkId=50882).
Review Microsoft Knowledge Base
article 156560, "Free Space Required to
Convert FAT to NTFS"
LinkId=50883).
 If neither of these actions resolves the
problem, restart the specified server and then
retry the operation.
Error 306: Agent This issue occurs Perform the following steps to reinstall the
installation failed when the protection protection agent:
17
because the agent has already 1. Locally uninstall the protection agent from the
specified server been installed on a server.
already has a server, but the DPM
2. On the DPM server, in DPM Administrator
different version of database does not
Console, in the Management task area, on
the protection agent have a record of the
installed. protection agent the Agents tab, select the server. In the
being installed. Actions section, click Refresh information.
The agent status will change to Error.
3. In the Details section, click Remove the
record of the server from this DPM
computer.
4. Reinstall the protection agent on the server.
Error 308:  Incorrect firewall  For firewall configuration requirements, in the
The agent operation configuration DPM Operations Guide, see Managing DPM
failed because of a requirements on Servers (http://go.microsoft.com/fwlink/?
communication error the DPM server. LinkId=187199).
with the DPM  Internet Protocol  IPsec may be configured to block particular IP
Protection Agent
Security (IPsec) traffic, such as on a particular port or to
service on the
configuration. particular addresses. For assistance in
specified server.
 The RPC server troubleshooting IPsec, see IPsec
is unavailable. Troubleshooting
LinkId=50885).
 See Microsoft Knowledge Base article
224370, "Troubleshooting RPC Server is
Unavailable in Windows"
Error 316: The Incorrect firewall For firewall configuration requirements, in the
agent operation configuration DPM Deployment Guide, see Installing Protection
failed because the requirements on the Agents behind a Firewall
DPM Protection DPM server. (http://go.microsoft.com/fwlink/?LinkId=190239).
Agent service on the
specified server did
not respond.
agent operation configuration DPM Operations Guide, see Managing DPM
failed because of a requirements on the Servers (http://go.microsoft.com/fwlink/?
communication error DPM server. LinkId=187199).
with the DPM Agent
Coordinator service
on the specified
server.
agent operation configuration DPM Operations Guide, see Managing DPM
failed because the requirements on the Servers (http://go.microsoft.com/fwlink/?
DPM Agent DPM server. LinkId=187199).
18
Coordinator service
on the specified
server did not
respond.
Error 341:  The account  Retry the operation with an account that has
Agent operation used does not administrator privileges on the specified
failed because the have sufficient server.
credentials provided privileges on the  Verify that system times on the DPM server
have insufficient server. and the server on which you are installing the
privileges on the
 The system agent are synchronized with the system time
specified server.
times of the on the domain controller.
DPM server, the  Verify that the DNS settings are correct.
server on which
you are installing
the agent, and
the domain
controller are not
synchronized,
and therefore
the Kerberos
authentication
fails.
 The DNS setting
on the DPM
server or the
computer on
which you are
installing the
protection agent
is not correct.
Error 342: Incorrect firewall For firewall configuration requirements, in the
The agent operation configuration DPM Operations Guide, see Managing DPM
failed because the requirements on the Servers (http://go.microsoft.com/fwlink/?
DPM server could DPM server. LinkId=187199).
not communicate
with the specified
server.
Error 347: The production
An error occurred server requires a Install the protection agents manually. For more
when the agent restart to install the information about manually installing protection
operation attempted protection agent. agents, see Installing Protection Agents Manually
to create the DPM (http://go.microsoft.com/fwlink/?LinkID=179676).
Agent Coordinator
service on <server
name>.
Error 348: Incorrect security Verify COM permissions on the server.
19
An error occurred settings for the COM
when the agent object on the Verify that the DCOM configuration settings are
operation attempted computer. set as follows:
to communicate with
COM Security Default Access Permissions
the DPM Agent
Coordinator service  Local Access and Remote Access permitted
on the specified to Self
server.  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
\Everyone
COM Security Default Launch Permissions
 Launch permitted to NT
AUTHORITY\SYSTEM
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
Activate permitted to BUILTIN\Distributed
COM Users
Error 271: The DCOM Verify that DCOM is enabled. If DCOM is enabled,
The user does not configuration verify that the DCOM configuration settings are
have administrator settings did not meet set as follows:
access. the minimum COM Security Default Access Permissions
requirements.
- Or -  Local Access and Remote Access permitted
Error 377: to Self
The agent operation  Local Access permitted to System
failed because the COM Security Machine Access Restriction
minimum (Security Limits)
requirements in the
 Local and Remote Access permitted to NT
DCOM configuration
were not met. AUTHORITY\ANONYMOUS LOGON
20
BUILTIN\Distributed COM Users
\Everyone
COM Security Default Launch Permissions
AUTHORITY\SYSTEM
AUTHORITY\INTERACTIVE
 Launch permitted to BUILTIN\Administrators
COM Security Machine Launch Restriction
(Security Limits)
 Local Launch and Activate permitted to
\Everyone
Activate permitted to BUILTIN\Administrators
Activate permitted to BUILTIN\Distributed
COM Users
System Error 1130: The configuration We recommend that you increase the value of this
Not enough server parameter parameter. See Microsoft Knowledge Base article
storage is available "IRPStackSize" of 177078, "Antivirus software may cause Event ID
to process this the server is too 2011" (http://go.microsoft.com/fwlink/?
command. small for the server LinkId=73102).
to use a local
- OR -
device.
Event ID 2011: Not
enough memory to
complete the
transaction. Close
some applications
and retry.
The RPC server is A firewall is enabled If a firewall is enabled on the remote computer on
unavailable. on the remote which you are installing the protection agents,
computer. before installation you must run the
DPMAgentInstaller.exe executable file. For more
information, see Installing Protection Agents
behind a Firewall (http://go.microsoft.com/fwlink/?
LinkId=190239).
The Windows After you install a No action is required. DPM protects the back-end
SharePoint Services protection agent on servers internally if the Windows SharePoint
farm back-end a back-end server to Services farm has data on the server.
server does not protect a Windows
appear as protected SharePoint Services
in DPM farm, the server
Administrator does not appear as
Console. protected in the
21
Management task
area on the Agents
tab.
The protection agent If the Primary To resolve this issue, upgrade the forest root PDC
installation fails if Domain Controller emulator operations master role holder to
you are installing it (PDC) is running Windows Server 2003, and then perform the
on a non-primary Windows protection agent installation again.
domain controller Server 2000, the For more information, see Knowledge Base article
running Windows required Distributed 827016, "Local service and other well-known
Server 2003. COM Users group security principals do not appear on your
will be missing. Windows Server 2003 domain controller"
The application has The software Install the .NET Framework 3.5 with Service
failed to start requirements must Pack 1 (SP1), and then try the protection agent
because the be met on the installation again.
application protected computer.
configuration is
incorrect.
Troubleshooting Remote SQL Server Issues
Troubleshooting Error ID 4307

The following table provides guidance for troubleshooting Error ID 4307. This error occurs when
you are attempting to connect to a remote SQL Server database when installing System Center
Data Protection Manager (DPM) 2010.
Troubleshooting Error ID 4307
Possible Cause Resolution
Remote connection to the computer running To enable the remote instance of SQL Server,
SQL Server is disabled. 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,
22
right-click TCP/IP and click enable.
The SQL Server Browser service is disabled. 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.
The name of the remote instance of SQL Make sure that the remote instance of SQL
Server is in the incorrect format. Server is in the following format:
<Computer name>\<Instance name>
Note
Only use <Computer name> for the
default instance.
There is no network connectivity between the Make sure there is a connection between the
DPM server and the computer running SQL DPM server and the computer running SQL
Server. Server.
Troubleshooting Data Protection Issues

This section includes troubleshooting assistance for data protection issues.
In This Section
General Data Protection Issues
File Server Protection Issues
Exchange Server Protection Issues
SQL Server Protection Issues
Windows SharePoint Protection Issues
Windows Server Backup Issues
System Protection Issues
23
Mirrored Databases Issues
Virtual Server Protection Issues
Manual Replica Creation Issues
Incompatible Filter Driver Errors
Client Computer Protection Issues
Hyper-V Protection Issues
General Data Protection Issues

The following table provides troubleshooting guidance on general protection issues.
Data Protection Issues
Issue Possible cause Resolution
Backup of data The protection agent Upgrade the protection agent on all members
sources fail with agent on some members of of the cluster.
upgrade error. the cluster has not
been upgraded.
Inconsistent drive If you change a To display the correct drive letters in the New
letter references in the volume drive letter Protection Group Wizard, you must refresh the
DPM New Protection and then do not drive letters in SQL by performing the following
Group Wizard. restart the computer steps:
before creating a 1. Remove the volume from the protection
protection group for group, retaining the replicas.
that volume,
inconsistent drive 2. Read the volume to the protection group.
letter references may
appear in the DPM
New Protection
Group Wizard.
DPM is no longer able The DPM computer To restore communication and resume data
to communicate with may have been protection activities, do the following:
its protected temporarily disjoined 1. Locally uninstall the protection agent from
computers. from the the protected computer.
Active Directory
domain to which it 2. On the DPM server, in DPM Administrator
previously belonged. Console, in the Management task area, on
For example, the the Agents tab, select the protected
DPM computer could computer. In the Actions pane, click
have been disjoined Refresh information.
because of a broken The agent status changes to Error.
workstation-domain
trust relationship. 3. In the Details section, click Remove the
When the DPM record of the server from this DPM
computer is restarted, computer.
it is rejoined to the
24
domain with the same Reinstall the protection agent on the computer.
name but is assigned For instructions, in the Operations Guide, see
a new Security Managing DPM Servers
Identifier (SID). All (http://go.microsoft.com/fwlink/?LinkId=91853).
servers that are being
protected by this
DPM computer have
an agent registry
DCOM security
setting that contains
the obsolete SID.
Therefore, the
servers are unable to
either launch the
DPM protection agent
or resume
communication with
the DPM computer.
After you install a When you install a Wait 20 minutes after the computer restarts
protection agent on protection agent, after and then run the DPM New Protection Group
the computer and then the computer restarts Wizard again, or try the following:
create a protection and is responsive to  In DPM Administrator Console, in the
group, you cannot the ping command, it Management task area, on the Agents
access any data can take up to
tab, in the Actions pane, click Refresh
sources on the 20 minutes for the
information until the agent status changes
computer. protection agent to
respond to requests to OK.
from the DPM New
Protection Group
Wizard.
The recovery point When a recovery No action is required.
time is not consistent point is created, it
with synchronization reflects the time of
time. the most recent
change to the
protected volume.
For example, if a
recovery point is
scheduled to be
created at 11:00 A.M.
and the most recent
change to the
protected volume
occurred at
8:30 A.M., the
recovery point that
was created at
11:00 A.M. will
display a time stamp
of 8:30 A.M.
25
Synchronization jobs The DPM server may To troubleshoot this issue, do the following:
fail and the details in not have access  Retry the operation.
the application event rights to update
log include "Unable to Active Directory.  Check for network connectivity between
connect to the DPM server and the domain controller.
Active Directory."  Verify that DPM is a member of the domain
and that the domain controller is running.
 Verify that the DPM server has access
rights to update Active Directory:
a. Open the Active Directory Users and
Computers snap-in and verify that
Advanced Features is selected in the
View menu.
b. Expand the domain, and then expand
System.
c. Right-click MS-
ShareMapConfiguration, and then
click Properties.
 On the Security tab, verify that the DPM
server name is listed.
Auto discovery does If a share on a No “pending members” will be discovered by
not discover changes computer is protected auto discovery for a computer with a protected
to shares. and the computer share if the computer also contains a share that
also contains an points to a destination in the following list of
unsupported share, unsupported shares:
then auto discovery  FAT volume.
will fail to discover
changes to shares on  CD-ROM drive.
that computer, such  USB drive.
as new shares,  Mount point located inside another mount
removed shares, and point.
share remappings.
 Special folders: System Volume
Information folder, RECYCLER folder.
 Unsupported reparse point (that is, any
reparse point other than a mount point).
 On a case-sensitive system, a folder that
has the same name as another folder
inside that folder’s parent, differing only in
case (for example, “F:\MarketingDocs” and
“F:\marketingdocs”).
 On a computer containing a share from the
list of unsupported shares, we recommend
that you protect only volumes and folders
for auto discovery to work correctly.
The tape backup size Your tape hardware If your tape backup size increases after
26
increases after may not allow the selecting the Compress Data tape option in
choosing to compress tape backup the DPM New Protection Group Wizard, check
data for the protection application to turn off your protection group configuration for the
group. compression. following:
 Encrypt data. If encryption is enabled,
check with your tape hardware vendor to
ensure that your tape hardware allows the
tape backup application to turn off
compression.
 Compress data. If compression is
enabled, check to see if you have files that
are compressed that you expect to
increase in size, such as media files or
encrypted files.
Your long-term tape If you are using tape To resolve this issue, when you create your
backup fails because for both short-term protection group, we recommend that you
your full tape backup and long-term schedule your short-term protection full backup
is not available. protection, DPM to run a day prior to your long-term protection.
- Or - creates copies of the This enables your long-term tape backup to
latest short-term tape leverage the short-term tape backup that was
Your long-term
full backup to most recently created.
backup does not
generate your long- If you schedule the long-term tape backup to
leverage the latest
term tape backup. run prior to the short-term tape backup, the
tape backup that was
most recently created. long-term backup will use the short-term full
backup of the previous week.
Data protection fails If you are protecting To restart protection, do the following:
when you are data on two domain 1. On the protected server, from the
protecting two domain controllers and then command prompt, change the directory
controllers. uninstall the
(CD) to <drive letter>:\Program
protection agent from
Files\Microsoft Data Protection
one of the domain
controllers, protection Manager\DPM\bin\.
will fail. 2. Type SetDpmServer.exe
-dpmServerName <DPM server name>.
Creating or modifying If the number of To view the number of existing recovery points,
a protection group recovery points do the following:
fails. exceeds the number From the DPM Management Shell prompt, type
that DPM has $dpm = Connect-DPMServer dpmoffice02
provisioned, creating $dpm.CurrentShadowCopyProvision.
or modifying a
protection group will
fail. In addition, you
cannot view the
number of recovery
points in DPM
Administrator
Console.
27
Replicas are marked Once a volume is You must perform a manual consistency check.
as inconsistent. marked as Missing, For information about performing a consistency
DPM only brings the check, in DPM 2010 Help, see How to
volume back online Synchronize a Replica
during the next disk (http://go.microsoft.com/fwlink/?
modification LinkId=196901).
operation, such as
Allocate disk space,
or after restarting the
computer. DPM then
marks the replica as
inconsistent.
Creating a protection The software You must install the software prerequisites on
group fails when prerequisites may not all nodes on the cluster that you are protecting.
protecting several be present on all For information about DPM prerequisite
nodes in a cluster, and nodes in the cluster. software and the servers it protects, see
the following error is Protected Computer Requirements
displayed: (http://go.microsoft.com/fwlink/?
"This item cannot be LinkId=100473).
protected because
some prerequisite
software is missing.
Ensure that all
prerequisite software
is installed and then
protect this item."
Adding a DPM server The name given to Rename the protection group.
to a protection group the protection group
on the secondary on the primary DPM
DPM server causes server contains
DPMRA service to fail special characters.
on the primary DPM
server.
Unable to see
protected data
sources on the
secondary DPM
server.
“DPMRA service has
terminated” error in
the Event Viewer log
on the primary DPM
server.
28
File Server Protection Issues
The following table provides troubleshooting guidance on file server data protection issues.
File Server Data Protection Issues
A Volume Missing The DPM server Perform the following steps to remove the
error occurs for some cannot identify the Volume Missing status.
of your protected volumes. 1. In DPM Administrator Console, click
server volumes. Management on the navigation bar, and
then select the Disks tab.
2. In the Actions pane, for each disk in the
storage pool, click Rescan. The current
disk data is displayed.
3. Close DPM Administrator Console, and
then restart it. Check for any missing
volume alerts in the details pane, and
address them.
4. In the Protection task area, verify that
DPM removed the Volume Missing status.
Inconsistent drive letter If you change a To display the correct drive letters in the New
references in the DPM volume drive letter Protection Group Wizard, you must refresh the
New Protection Group and then do not drive letters in SQL by performing the following
Wizard. restart the computer steps:
before creating a 1. Remove the volume from the protection
protection group for group, retaining the replicas.
that volume,
inconsistent drive 2. Read the volume to the protection group.
letter references
may appear in the
DPM New Protection
Group Wizard.
The recovery point When a recovery No action is required.
time is not consistent point is created, it
with synchronization reflects the time of
time. the most recent
change to the
protected volume.
For example, if a
recovery point is
scheduled to be
created at
11:00 A.M. and the
most recent change
to the protected
volume occurred at
29
8:30 A.M., the
recovery point that
was created at
11:00 A.M. will
display a time stamp
of 8:30 A.M.
Replicas are marked Once a volume is You must perform a manual consistency check.
as inconsistent. marked as Missing, For information about performing a consistency
DPM only brings the check, in DPM 2010 Help, see How to
volume back online Synchronize a Replica
during the next disk (http://go.microsoft.com/fwlink/?
modification LinkId=196901).
operation, such as
Allocate disk
space, or after
restarting the
computer. DPM then
marks the replica as
inconsistent.

The following table provides troubleshooting guidance on protection issues for computers running
Exchange Server.
Issue Possible Cause Details
Exchan Before you can protect The following versions of Exchange Server must be
ge Exchange Server 2007 installed on the computer that you want to protect:
Server data, you must install  Exchange Server 2003 with Service Pack 2 (SP2)
data is hotfix 940006. For more
- Or -
unavaila details, see Knowledge
ble for Base article 940006,  Exchange Server 2007
protectio "Description of Update Important
n. Rollup 4 for Exchange
2007" To protect Exchange Server data, the Exchange
(http://go.microsoft.com/ Server databases must be mounted within each
fwlink/?LinkId=99291). storage group.
DPM The eseutil.exe and You must update eseutil.exe and ese.dll on the DPM
cannot ese.dll versions that are server if they are updated on a computer running
protect installed on the most Exchange Server after applying an upgrade or an update.
Exchan recent edition of For more information about updating eseutil.exe and
ge Exchange Server must ese.dll, in the DPM 2010 Deployment Guide, see
Server be the same versions Protected Computer Software Requirements.
data. that are installed on the
30
DPM server.
After If you use the original After you rename an Exchange Server storage group, you
you storage group name, must restart the Microsoft Exchange Information Store
rename data recovery fails when service before you create a new protection group.
an trying to dismount the To start the Microsoft Exchange Information Store
Exchan database. service
ge
1. Click Start, point to Administrative Tools, and then
Server
storage click Services.
group, 2. On the Services screen, scroll down and right-click
the new Microsoft Exchange Information Store, and then
name click Restart.
does not
appear
in the
DPM
New
Protecti
on
Group
Wizard.
DPM 20 You cannot enable For successful incremental backups, we recommend that
10 does circular logging if you you disable circular logging for the protected storage
not want incremental group. After you disable circular logging, restart the
support backups for Exchange Microsoft Exchange Information Store service
increme Server storage groups. (MSExchangeIS).
ntal To disable circular logging
backups
1. Click Start, point to Programs, point to Microsoft
if
circular Exchange, and then click System Manager.
logging 2. If the Administrative Groups branch exists in the left
is pane, expand it, expand the appropriate administrative
enabled group's branch, expand the Servers branch, and then
for expand the appropriate server's branch.
Exchan
If the Administrative Groups branch does not exist,
ge
expand the Servers branch in the left pane, and then
Server
expand the appropriate server's branch. To expand a
storage
branch, double-click the branch or click the plus sign
groups.
(+) to the left of the branch.
3. Right-click the storage group for which you want to
disable circular logging, and then click Properties.
4. Clear the Enable Circular Logging check box, and
then click OK.
5. Restart the Microsoft Exchange Information Store
service (MSExchangeIS).
To restart MSExchangeIS
1. Click Start, click Run, and then type services.msc to
31
start the Services snap-in.
2. Right-click Microsoft Exchange Information Store,
and then click Start.
Note
If you do not want to disable circular logging, you
can modify the protection group properties so that
synchronizations occur just before creating the
recovery point.
To change the synchronization frequency
 In the New Protection Group Wizard, on the Specify
Short-Term Protection Policy page, select Just
before a recovery point.
Replica When you are protecting To protect data on a computer running Exchange Server,
initializat data on a computer perform the following steps:
ion and running a version of 1. On the computer running Exchange Server, copy
express Exchange Server, the Ese.dll and eseutil.exe located in the Exchange
full DPM server must
Server installation location to the DPM server
backup include the Ese.dll and
installation location. The default installation location on
operatio eseutil.exe files that are
ns stop located in the Exchange the DPM server is <drive>:\Program Files\Microsoft
prior to Server installation Data Protection Manager\DPM\bin.
completi location. 2. Cancel the replica initialization and express full
on. backup jobs that did not complete.
3. Restart the canceled express full backup jobs.
4. Run a synchronization with consistency check for
canceled replica initialization jobs.
Note
We recommend that you use the same processor
architecture for the DPM server and the computer
running Exchange Server.
If your processor architecture is different, you must do the
following:
1. Install the version of Exchange Server that you are
protecting on a test server that is consistent with the
hardware of the DPM server.
2. From the test server, copy Ese.dll and eseutil.exe
located in the Exchange Server installation location to
the DPM server installation location. The default
installation location on the DPM server is
<drive:>\Program Files\Microsoft Data Protection
Manager\DPM\bin.
The In Exchange To recycle the VSS writer for:
VSS Server 2007 RTM and Event ID 2024 A: Restart the Microsoft Exchange
writer Exchange Server 2003 Information Store service to recycle the VSS writer.
does not RTM, if you cancel the
32
clear backup on a storage Event ID 2024 B: Restart the Exchange Server
Backup group within a particular Replication service (Exssrv.exe) to recycle the VSS writer.
in interval (between
progres PrepareForBackup and
s state DoSnapshot), the VSS
for the writer does not clear
storage Backup in progress
group. state for the storage
group.
The If the Exchange Local To display the Exchange LCR-enabled storage groups in
Microsof Continuous Replication the DPM New Protection Group Wizard, use the following
t (LCR) VSS replica writer set key command to disable the (LCR) VSS replica writer:
Exchan is enabled, the Microsoft set key EnableVssWriter under
ge Exchange Information HKLM\Software\Microsoft\Exchange\Replay\Parameters
Informat Store service will not to 0
ion appear on the Select
DWORD type
Store Group Members page
service of the New Protection Note
does not Group Wizard. After setting the registry key, you must restart the
appear Microsoft Exchange Server Replication service.
on the
Select
Group
Member
s page
of the
New
Protecti
on
Group
Wizard.
All data If the versions of The eseutil.exe and ese.dll versions that are installed on
replicati Exchange Server the most recent edition of Exchange Server must be the
on jobs Database Utilities same versions that are installed on the DPM server. For
fail. (eseutil.exe) and ese.dll example, if you are protecting Exchange Server 2003
that are installed on the SP2, Exchange Server 2007, and Exchange Server 2007
most recent edition of SP1, you must copy eseutil.exe and ese.dll from the
the protected Exchange server running Exchange Server 2007 SP1 to the DPM
Server are different from server.
the versions that are The following scenarios show the versions of eseutil.exe
installed on the DPM and ese.dll that you must install on the DPM server:
server, all data
 32-bit operating system
replication jobs will fail.
 If DPM is protecting only computers running
Exchange Server 2003 on a 32-bit operating
system, copy eseutil.exe and ese.dll from the
computer running Exchange Server 2003.
 If DPM is protecting computers running Exchange
Server 2007, the 32-bit versions of eseutil.exe and
33
ese.dll are required from Exchange Server 2007.
You can obtain these versions from the Exchange
Server 2007 Setup DVD.
 64-bit operating system
 If DPM is protecting only computers running
Exchange Server 2003 on a 32-bit operating
system, copy eseutil.exe and ese.dll from the
computer running Exchange Server 2003.
 If DPM is protecting Exchange Server 2007, copy
eseutil.exe and ese.dll from the computer running
Exchange Server 2007.
Exchan If the Exchange writer is By default, the Setup program for Windows Small
ge turned off for the Volume Business Server 2003 turns off the Microsoft Exchange
Server Shadow Copy service in Server 2003 writer for the Volume Shadow Copy service.
protectio Windows Small To protect data using DPM 2010, the Exchange
n fails. Business Server 2003, Server 2003 writer must be turned on.
protection will fail. For more information about this issue, see Knowledge
Base article 838183 "How to turn on the Exchange writer
for the Volume Shadow Copy service in Windows Small
Business Server 2003" (http://go.microsoft.com/fwlink/?
LinkId=77040).
To turn on the Exchange writer
1. Click Start, click Run, type regedit, and then click
OK.
2. Locate and then double-click the following registry
subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControl
Set\Services\MSExchangeIS\ParametersSystem
3. Double-click the Disable Exchange Writer value.
4. In the Value data text box, change the value from 1 to
0, and then click OK.
5. Quit Registry Editor.
6. Click Start, point to Administrative Tools, and then
click Services.
7. Stop and then restart the Microsoft Exchange
Information Store service.
Local If the Exchange Server Restart the replication service after updating the registry
continuo replication service is not key.
us restarted after the
replicati registry key is set, LCR
on fails for the storage
(LCR) group.
protectio
n fails
with a
34
VSS
error.
Setting The preferred server Provide the topology as PT_CCR_ACTIVE_ONLY along
and may not have been with the RunEseUtilConsistencyCheck option.
unsettin specified.
g the
eseutil
flag
through
the
comman
d line
interface
(CLI)
fails.
ID The next incremental Create a DPM full recovery point before performing an
30112: backup fails when an incremental backup.
DPM incremental backup is
encount performed after you run
ered a ntbackup on the storage
retryabl group.
e VSS
error
(0x8004
23F3).
The The consistency check To resolve this issue, disable indexing, encryption, and
consiste will fail if indexing, SIS for the folder containing the .edb file.
ncy encryption, or Single
check Instance Storage (SIS)
fails with is enabled for the folder
RMGen containing the .edb file.
ericError
.

SQL Server.
Sched Resources on the protected computer are Restart the computer.

uled unavailable and hence SQL Server agent
SQL is not able to start.
Serve
35
r
protec
tion
jobs
not
startin
g.
DPM You must have the required software The following versions of SQL Server must
is installed to protect a computer running be installed on the instance of SQL Server
unabl SQL Server. that is hosting the database that you want
e to to protect:
protec  SQL Server 2000 with Service Pack 4
ta (SP4)
SQL
Serve - OR -
r  SQL Server 2005 with Service Pack 2
datab (SP2)
ase.
Note
DPM supports Standard,
Enterprise, Workgroup, and
Express Editions of SQL Server.
Important
You must start the SQL Server
VSS Writer Service on the SQL
Server. By default, the SQL Server
VSS Writer Service is turned off
when you install SQL
Server 2005.
To start the SQL Server VSS Writer
Service
1. Click Start, point to Administrative
Tools, and then click Services.
2. On the Services screen, scroll down
and right-click SQL Server VSS
writer, and then click Start.
Caution
After you start the SQL Server
VSS Writer Service, we
recommend that you do not stop
the service. If your backups begin
to fail, check to ensure that the
SQL Server VSS Writer Service is
started.
The If you are protecting SQL Server 2005 on For information about running editions of
SQL a Windows Server 2008 operating system, SQL Server on Windows Server 2008, see
Serve you must install SQL Server 2005 SP2. Running SQL Server on Windows Server
r VSS 2008 R2 or Windows Vista
36
Writer (http://go.microsoft.com/fwlink/?
servic LinkId=130555).
e fails
during
protec
tion.
The If you physically delete one of the Delete the database log files using the
SQL database files from the SQL Server and do following query:
Serve not remove it from the database, the SQL ALTER DATABASE <file name>.mdf
r Server VSS Writer Service will continue to
REMOVE FILE <file name>_log.ldf
datab report the deleted file and DPM will not be
ase able to locate it while performing backups. Note that you will not be able to restore to
backu the original location from the backups that
p fails. existed before you deleted the log files
because the file does not exist. To resolve
this issue, you must restore the database
files, and then attach the database to the
instance of SQL Server.
When This can occur in the following scenario, To resolve this issue, you must set the
you where you have two SQL Server VSS value of the
perfor writers: SqlServerWriter and MSDEWriter. HKEY_LOCAL_MACHINE\SYSTEM\Curre
m an  You install an instance of SQL ntControlSet\Services\VSS\Settings\MSD
inquir Server 2005. (The SQL Server VSS EVersionChecking registry key to 1 (a non-
y job zero value), so the MSDEWriter is the only
Writer Service is turned off by default)
in the writer that enumerates the SQL
DPM  Because the SQL Server VSS Writer Server 2005 databases.
New Service is turned off, the MSDEWriter
Protec writer enumerates the SQL
tion Server 2005 databases.
Group  You turn on the SQL Server VSS
Wizar
Writer Service in the Service Control
d,
Manager, which sets the
such
as HKEY_LOCAL_MACHINE\SYSTEM\C
viewin urrentControlSet\Services\VSS\Setting
g a list s\MSDEVersionChecking registry key
of value to 1.
data  After the registry key value is set to 1,
sourc the MSDEWriter writer stops
es, if enumerating the SQL Server 2005
two
databases, and the SQLServerWriter
differe
writer starts enumerating them.
nt
SQL You then set the value of the registry key
Serve to zero (0), which causes both the
r VSS MSDEwriter and SQLServerWriter writers
Writer to start enumerating the SQL Server 2005
s are databases.
enum
eratin
37
g the
same
data
sourc
e, the
DPM
server
will
crash.
Datab If you are protecting a database on an After you upgrade to SQL Server 2005
ase instance of SQL Server 2000 and then and then restart the SQL Server VSS
protec upgrade to SQL Server 2005, database Writer service, DPM will not map the
tion protection on the instance of SQL existing replica to the protected database.
on an Server 2005 will fail. This is because the new VSS writer
instan enumerates the new database, and
ce of therefore DPM recognizes it as a new data
SQL source.
Serve If this issue occurs, we recommend that
r 2005 you stop protection for the database that is
fails. hosted on the upgraded instance of SQL
Server 2005, and then use the Create
New Protection Wizard to reconfigure
protection.
Note
After you reconfigure protection,
DPM Administrator Console
displays the protected database
as two separate nodes. The
protection status in the Protection
task area appears as Inactive
replica for one of the database
nodes, and the DPM Recovery
user interface displays two
database nodes with the same
name.
No data loss occurs with this issue.
SQL Replica creation jobs may fail on a SQL If a replica creation job fails on a SQL
Serve Server 2000 database running on a 64-bit Server 2000 database running on a 64-bit
r 2000 computer in Windows in Windows (WOW) computer in Windows (WOW) mode,
datab mode. check the event viewer on the SQL Server
ase computer for Event ID 20 "Volume
replic Shadow Copy Service error."
a For information about a supported hotfix to
creati correct this issue, see Event ID 20
on job (http://go.microsoft.com/fwlink/?
fails LinkId=73718).
runnin
g on a
64 bit
38
comp
uter.
SQL If the database transaction log For information about how to resolve this
Serve unexpectedly becomes full on a computer problem, see Microsoft Knowledge Base
r full that is running SQL Server, your article 317375, "A transaction log grows
transa synchronization jobs will start to fail. unexpectedly or becomes full on computer
ction that is running SQL Server
log "(http://go.microsoft.com/fwlink/?
cause LinkId=72730).
s
synch
roniza
tion
job
failure
s.
DPM If DPM is protecting a SQL Server If you plan to fail-back to the primary
protec database that is using mirroring or log database, do the following:
tion shipping, after a failover the protected  After your protection jobs start to fail
jobs primary database will no longer be online and the replica is no longer valid,
start and your DPM protection jobs will start to
perform a consistency check.
to fail. fail.
Note
If you fail-back to the primary
database in a short period of
time and the replica remains
valid, then you do not have to
perform a consistency check.
 If there is a delay in the fail-back to the
primary database, you must create a
protection group using the New
Protection Group Wizard to protect
the new active database.
Note
After the failover, you can stop
protection on the new
protection group.
If you do not plan to fail-back to the
primary database, we recommend that you
remove it from protection and then
configure protection for the new database.
To remove the primary database, do the
following:
1. In DPM Administrator Console, click
Protection on the navigation bar.
2. In the Protection task area, select the
database that you want to remove,
39
and then in the Actions pane, select
Remove from protection.
3. In the Stop Protection - <Protection
Group name> dialog box, select the
Retain Protected Data option, and
then click Stop Protection.
After you remove the primary database,
configure protection for the new database
using the New Protection Group Wizard.
Incre DPM does not support configuring DPM allows log backups for databases
menta incremental synchronizations for SQL configured in the full and bulk-logged
l Server master databases. recovery models. However, log backups
synch cannot run against the SQL Server master
roniza database.
tions Additionally, do not set the synchronization
fail for frequency for the master database to "just
the before a recovery point," because there
SQL are no backup logs to obtain from the
Serve protected server during the recovery.
r
maste
r
datab
ase.
DPM SQL Server 2005 includes database You can view database snapshots in the
is not snapshots that appear in the New Microsoft SQL Server Management Studio
protec Protection Group Wizard as regular in the Database Snapshots folder.
ting databases. However, DPM does not
SQL support protecting database snapshots for
Serve recovery.
r 2005
datab
ases.

Windows SharePoint Services.
The SQL Server alias The Windows You must reconfigure the SQL Server alias by
did not resolve on the SharePoint Services using the SQL Server Configuration Manager.
SQL Server Agent and farm is unable to use
40
protection for the a SQL Server alias
Windows SharePoint that was created by
Services farm fails. using cliconfg.exe.
Not all the SQL Check the list of servers on the Central Admin
Server aliases are page of the SharePoint farm. Identify the SQL
configured on the Server aliases from the list of SQL Server
front-end Web computers. Verify if all the SQL Server aliases
server. have been configured on the SharePoint front-
end Web server (the one that communicates
with the DPM server).
The SQL Server DPM supports only TCP/IP SQL Server aliases.
alias is not of type Reconfigure the aliases to type TCP/IP.
TCP/IP.
SQL Server client Install the SQL Server client connectivity
connectivity components on the front-end Web server.
components are not
installed on the front-
end Web server.
For Windows Irrespective of the version of SQL Server on
SharePoint Services the back-end servers, for MOSS 2007 and
3.0/MOSS 2007 Windows SharePoint Services 3.0, you should
farms, SQL Server install the SQL Server 2005 client connectivity
2005 client components on the front-end Web server. Also,
connectivity ensure that all the aliases are configured using
components are not this version of the client connectivity
installed on the front- components.
end Web server.
Windows SharePoint If the path to any We recommend running periodic scripts to
Services database log Windows SharePoint truncate your Windows SharePoint Services
files are not truncated. Services database database log files.
log file exceeds 150
characters, DPM
cannot truncate the
log file.
The Copy-Only This registry entry needs to be deleted. It can
registry value has be found under the following path on the DPM
been set for the Server: “HKLM\Software\Microsoft\Microsoft
specific SharePoint Data Protection Manager\CopyBackups” with
farm on the DPM the name equivalent to the name of the Config
server. database of the farm.
The “Do not truncate This can be reset by using the following
logs” setting has Windows PowerShell command: Set-
been enabled for the DPMGlobalProperty -Dpmserver $DPMMachineName
SQL Server -TruncateSharePointDbLogs $true.
computer on which
the SharePoint
databases reside.
41
The server process If the password is From the command prompt, run
could not be started reset for the ConfigureSharePoint.exe to reset the
because the Windows SharePoint password.
configured identity is Services farm, For more information about how to manage
incorrect. Check the protection will fail. password changes, see How to change service
username and accounts and service account passwords in
password SharePoint Server 2007 and in Windows
(0x8000401A). SharePoint Services 3.0
LinkId=126982).
Replica Inconsistent DPM retains the Resolve the alert by clicking Inactivate the
alerts for one or more existing recovery alert.
SQL Server databases points of the
that were earlier a part databases that have
of the SharePoint farm been removed from
appear in the the SharePoint farm.
Monitoring pane. This can happen if
the removed
database is
recovered by using
DPM or if DPM has
been upgraded.
Some of the The consistency Cancel the consistency check job and restart
SharePoint farm’s check was triggered the consistency check for the farm from the
consistency check jobs while recovery of one Protection pane.
appear to have of the farm’s
stopped (no data components was in
transfer has occurred progress.
for a long time).
The SharePoint There is a network Rerun the catalog job by using Windows
catalog task fails with connectivity issue PowerShell.
HR 0x80004003 between the
(Invalid Pointer) SharePoint front-end
Web server and the
back-end server.

The following table provides troubleshooting guidance for Windows Server Backup (WSB) issues.
When using WSB, the following Performing backups using If you are using WSB, do the
errors might occur: WSB on a server which DPM following:
is protecting can interfere
42
 DPM has detected a with the backups DPM uses.  Ensure that WSB always
discontinuity in the log chain takes a COPY backup
for <DatasourceType> using the WSB Backup
<DatasourceName> on Once Wizard.
<ServerName> since the last  If you are using WSB
synchronization. Scheduled Backups,
 The recovery to the latest ensure that the volumes
point in time failed. During a you are backing up do
recovery to the latest point not contain any
in time, DPM attempts to application data such as
perform a SQL Server Exchange Server data or
transaction log backup to SQL Server data.
receive the latest changes  After you reconfigure
from the SQL Server WSB, on the DPM
database <DatasourceName> server, run a new
on <ServerName> before express full backup.
starting the recovery. This
transaction log backup has
failed.
 DPM attempted to perform a
SQL Server log backup,
either as part of a backup
job or a recovery to latest
point in time job. The SQL
Server log backup job has
detected a discontinuity in
the SQL Server log chain for
<DatasourceType> database
<DatasourceName> since the
last backup. All incremental
backup jobs will fail until an
express full backup runs.

The following table provides troubleshooting guidance for system state protection issues.
Bare Metal Recovery (BMR) You have just migrated 1. Remove BMR protection.
backups fail with “Access from System State 2. Modify protection group and
Denied” error. protection to BMR
include BMR protection.
protection.
43
One or more prerequisites This error occurs if the To resolve this issue, do the
for protecting this data Windows Server Backup following:
source is missing on your utility is not installed on the 1. To install the Windows Server
Windows Server 2008 protected server. Backup utility, open a command
operating system.
prompt with administrator
privileges, and then type
Start /wait ocsetup
WindowsServerBackup /quiet
/norestart.
Note
To open a command
prompt with
administrator privileges,
click Start, point to All
Programs, click
Accessories, right-click
Command Prompt,
and then click Run as
administrator.
Mirrored Databases Issues

The following table provides troubleshooting guidance on protection issues for mirrored
databases.
Mirrored Databases Protection Issues
The server process If the password is From the command prompt, run
could not be started reset for the ConfigureSharePoint.exe to reset the
because the configured Windows SharePoint password.
identity is incorrect. Services farm, For more information about how to manage
Check the username protection will fail. password changes, see How to change service
and password accounts and service account passwords in
(0x8000401A). SharePoint Server 2007 and in Windows
SharePoint Services 3.0
LinkId=126982).
44
Microsoft Virtual Server.
You may see the For Virtual Provide a drive letter mount point for the volumes on
error One or Server 2005 R2, which the VHD files exist and attempt to select for
more volumes DPM does not backup with DPM again.
are missing for support backing
the following up virtual
application: machines hosted
<Virtual on a volume that
machine does not have a
name>. Ensure drive letter.
that the
Note
dependent
volumes for the This
data sources problem
are online. does not
when you select apply to
a Virtual Hyper-V
Server 2005 R2 virtual
based virtual machine
machine. s.
Data on the Virtual Install Virtual Server 2005 R2 Service Pack 1 (SP1) on

virtual machine Server 2005 R2 the server that you want to protect.
is unavailable for Service Pack 1
protection. (SP1) may not be
installed on the
server you want
to protect.
Backup fails on The Virtual Use Windows Event Viewer on the Virtual Server
the virtual Server VSS machine to find if Event ID 1044 exists. If this event
machine with Writer service exists, the virtual machine cannot perform online
unknown does not support backups.
error 0x800423f online backup for You can perform offline backups by updating the
3. the client virtual following registry key:
machine.
Set
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Virtu
al Server\1.0\Backup\BackupType\<VMNAME> to 0.
Online backup Online backups Install Knowledge Base article 940349 “Availability of a
fails. fails if the virtual Volume Shadow Copy Service (VSS) update rollup
machine contains package for Windows Server 2003 to resolve some VSS
volumes that do snapshot issues”
not support (http://support.microsoft.com/kb/940349) on the virtual
45
shadow copies machine.
(FAT 32 file Ensure that the virtual machine is running before
systems). configuring the backup, and then delete the entries for
Additionally, if the the virtual machines for which the online backup is failing.
shadow copies Set
exist on different HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Virtu
virtual machine al Server\1.0\Backup\BackupType.
volumes, the
backup fails.

When you create a manual replica, it is critical that you retain the same directory structure and
properties (time stamps and security permissions) as those for the data that you are protecting.
For guidance in selecting the specific settings, consult your backup software documentation and
the white papers included in the Featured Technical Content area of the DPM product site
(http://go.microsoft.com/fwlink?linkid=33686).
If the replica is created correctly, the directory structure of the ReplicaDir folder of the replica on
the DPM server will map to the directory structure of the volume being protected.
The following table provides troubleshooting guidance on issues for manual replica creation.
Transferring data to an The replica must be created in If you have already started
incorrect directory creates an the location that is specified in synchronization with
incorrect replica hierarchy. the Properties pane in DPM consistency check, you need
Administrator Console when to do the following:
you select manual replica  Remove the protected
creation. If you transfer the volume or share from the
data to an incorrect location,
protection group and
you can use FsPathMerge to
choose to delete the
move the data or you can
delete the replica data and replica.
create the replica again.  Add the volume or share
to the protection group.
 Manually create the
replica again.
In the case of an incorrect
replica hierarchy,
synchronization with
consistency check can
potentially synchronize the
entire replica over the network
from the file server,
46
consuming valuable network
bandwidth and CPU
resources.
Re-creating junction points This issue occurs when you If this occurs, manually delete
rather than using existing use a tape backup that was the data and the path, and
junction points. created from a DPM server. If then manually create the
you do not choose to use replica again.
existing junction points during
the restore operation, data
may be restored to the
incorrect path.
Failing to restore security The backup of the data Wait until synchronization with
settings when you restore the includes the security settings consistency check completes
data. of the source data. If you successfully. Incorrect replica
restore the data from the data security settings can
backup without restoring the allow nonprivileged users to
security settings, the correct have access to the data.
access control lists (ACLs) will Failure to restore the security
not be configured on the files settings also means that
and folders. synchronization with
consistency check will take
longer to complete and
transfer more data over the
network.
Incorrect time stamps cause Changing the file and folder Do not set the time stamp of
synchronization with time stamps because of user restored files and folders to
consistency check to take error or by-design behavior of the restore time. We
longer to complete. the backup software causes recommend that you use the
synchronization with time stamp that the files and
consistency check to take a folders had at the time of
long time to complete. For backup.
example, backup software
might set the time stamp of
the restored files and folders
to the restore time rather than
using the time stamp that the
files and folders had at the
time of backup.
Incompatible Filter Driver Errors

The following table provides troubleshooting guidance for incompatible filter errors.
Data Protection Issues
47
Possible Cause Resolution
If the WIM FS Filter driver Perform the following steps to continue protection.
(Wimfltr.sys) is installed on the 1. On the protected server, browse to the registry path
protected server, an HKLM\Software\Microsoft\Microsoft Data Protection
incompatible filter error occurs.
Manager\Agents\2.0.
2. Add wimfltr to the ExcludedFilters value, which
contains the luafv value.
3. Restart the DPMRA service on the protected server.
4. On the DPM server, run a consistency check, and then
run a synchronization job.
DPM is unable to continue Perform the following steps to continue protection:
protection for data sources on 1. On the protected server, browse to the application event
the protected server because it log to check for events from the DPMRA service that
has detected an incompatible
indicate the name of the incompatible filter.
filter.
2. If there are no incompatible filters listed in the event log,
check to see if any file system filters were recently
installed on the protected server.
3. After you identify the incompatible filter, we recommend
that you uninstall the filter.
Note
If you do not want to uninstall the incompatible filter,
DPM can protect the data using a consistency check
mechanism instead of volume filter tracking. This will
degradate performance; however, you will be able to
continue protection.
Perform the steps in the following procedure to protect the
data using the consistency check mechanism.
1. On the protected server, browse to the registry path
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Micr
osoft Data Protection Manager\Agent\2.0.
2. Create a DWORD registry value named ForceFixup and
set it to 1.
3. Stop and then restart the DPMRA service.

The following table provides troubleshooting guidance on protection issues for client computers.
48
Issue Possible Cause Solution
Missing recovery points If a scheduled recovery point To avoid losing a recovery

creation and a point for such clients, schedule
synchronization/consistency check additional recovery point
from a client run concurrently, the creation at low usage times so
recovery point will get skipped. that client computers that
missed the recovery point
creation will get a recovery
point later.
Backups of client Edge traversal is blocked in the 1. Launch the Windows
computers connected to firewall settings. Firewall console (Start ->
corporate network Run -> firewall.cpl).
through DirectAccess fail
2. Click Advanced settings
with RPC server
unavailable error. on the left pane.
3. Select Inbound rules, and
scroll down to DPMRA and
DPMRA_DCOM_135.
4. Double click the rule and
navigate to the Advanced
tab.
5. In the Edge traversal
group item, select Allow
edge traversal.
Hyper-V Protection Issues

The following table provides troubleshooting guidance on protection issues for Hyper-V virtual
machines.
Hyper-V Virtual Machine Protection Issues

Issue Reason Workaround
DPM error: DPM failed to Insufficien Verify that the SAN has enough available storage
synchronize changes for t storage to create hardware snapshots.
Microsoft Hyper-V \Backup in
Using Child Partition snapshot
Snapshot\<<VM Name>> on pool.
<<Resource Group>>
because the snapshot volume
did not have sufficient storage
space to hold the churn on
the protected computer (ID
49
30115 Details: Unknown error
(0x8004231f) (0x8004231F))
DPM error: The VSS Auto- Enable auto-mounting by using the following
application writer or the VSS mounting command: Mountvol /E
provider is in a bad state. of
Either it was already in a bad volumes
state or it entered a bad state might not
during the current operation. be
(ID 30111 Details: Unknown enabled
error (0x800423f4) on the
(0x800423F4)) protected
VMMS event: No snapshots computer.
to revert were found for virtual
machine 'CSVVM02'. (Virtual
machine ID 4774EF60-F4B6-
47D6-A0B9-60452C6B7FE8)
DPM error: The VSS The This is potentially a configuration issue. Check the
application writer or the VSS hardware application event logs for VSS hardware provider
provider is in a bad state. provider events and validate the storage configuration with
Either it was already in a bad has your SAN vendor.
state or it entered a bad state vetoed
during the current operation. snapshot
(ID 30111 Details: Unknown creation.
error (0x80042306)
(0x80042306))
The operation failed for Live 1. Rerun the backup job.
Microsoft Hyper-V \Backup migration 2. Diagnose the storage volume for the virtual
Using Child Partition caused
machine.
Snapshot\Win7.01 on the virtual
Win7.01.dpmcsv1.DC505.LA machine For information about how to back up virtual
B because the data source is to move machines on CSV, in the DPM 2010
not available. (ID 30169 to another Operations Guide, see Considerations for
Details: Unknown error node Backing Up Virtual Machines on CSV with the
(0x80042308) (0x80042308)) while the System VSS Provider
backup (http://go.microsoft.com/fwlink/?
was in LinkId=196939).
progress.
Cluster
disks are
in a bad
state.
Data
source
was
deleted.
DPM error: Failed to prepare Too many For information about how to enforce serial
a Cluster Shared Volume parallel backups, in the DPM 2010 Operations Guide, see
(CSV) for backup as another backups Considerations for Backing Up Virtual Machines on
50
backup using the same CSV are CSV with the System VSS Provider
is in progress. (ID 32612 competing (http://go.microsoft.com/fwlink/?LinkId=196939).
Details: Unknown error for the
(0x8007173d) (0x8007173D)) same
CSV LUN.
DPM error: An unexpected There Repair or remove the failed disk in the cluster.
error occurred during job might be
execution. (ID 104 Details: a failed
Element not found disk in the
(0x80070490)) cluster.
Backup of Hyper-V virtual TCP Run netsh int tcp set global chimney=disabled to disable
machines are stalled and no Chimney TCP Chimney Offloading.
data transfer is happening. Offloading
maybe
active.
Troubleshooting Data Recovery Issues

This section includes troubleshooting assistance for data recovery issues.
In This Section
General Data Recovery Issues
Exchange Server Recovery Issues
SQL Server Recovery Issues
Windows SharePoint Recovery Issues
Tape Library Recovery Issues
End-User Recovery Issues

The following table provides troubleshooting guidance for general data recovery issues.
Issue Possible Cause Details
The Recovery Wizard If you selected data to restore Item details will not appear on
Summary page does not at the item level, the Recovery the Recovery Wizard
display the details of the Wizard Summary page will Summary page for the
recoverable items. not display the details of the following:
recoverable items.  Windows SharePoint
51
Services sites and items
 Exchange Server
mailboxes
The Summary page will
display recovery details such
as recovery points, media, and
notifications.
The recovery job fails. If you perform a recovery at DPM will cancel a D2T short-
the same time a disk-to-tape term protection job if it is
(D2T) short-term protection running at the same time you
job is scheduled to run, the are performing a recovery.
recovery will fail. You can complete the steps in
the Recovery Wizard;
however, the recovery job will
fail. You must either cancel the
D2T short-term protection job
or wait for it to complete before
performing the recovery.

The following table provides troubleshooting guidance that supplements the specific error
messages that you may encounter during recovery of Exchange Server data.
Recovery fails If you rename The caption of the Exchange Server storage group is
when trying to an Exchange used to mount and dismount the Exchange Server
mount or dismount Server storage databases. If you rename the storage group, the caption
the Exchange group after stored in the protected object will be different from the
Server database. protecting it, actual caption and the mount and dismount operations
when DPM will fail. If this occurs, we recommend that you do the
performs a following:
recovery  Rename the storage group back to the original
operation, the storage group name.
recovery will
fail when trying  When you detect a name change, update the
to mount or caption name in the protected object.
dismount the  You can use the component name to identify a
database. storage group to mount and dismount the databases
under it instead of the caption name.
ID 104: An Exchange Perform the following steps to provide the user with the
unexpected error Server 2007 Exchange Server Administrator privileges:
occurred during job requires 1. From the command prompt, type dcomcnfg, and
52
execution. credentials of then click OK.
an Exchange 2. On the Component Services screen, expand
Server
Component Services, expand Computers, expand
administrator
My Computer, and then click DCOM Config.
for dismounting
or mounting the 3. Right-click ExchangeCmdletsWrapper, and then
database. click Properties.
The DPM 4. In the Properties dialog box, on the Identity tab,
replication select This user.
agent requires
5. Provide the credentials for the account that has
Local System
Exchange Server Administrator privileges, and then
account
privileges, and click OK.
therefore,
recovery fails
when trying to
recover data on
an Exchange
Server 2007
server that is
configured for
clustered
continuous
replication
(CCR).
Recovery to the If the Dismount and remount the databases, and then retry the
latest embedded recovery. If you cannot dismount and remount the
Programmable database databases, restore the files and then copy them with a
Interval Timer (PIT) (.edb) and the clean shutdown. Then move the files to the original
fails. streaming location and mount the database.
(.stm) files are
renamed and
then the
databases are
not dismounted
and then
remounted, the
recovery fails.
Mailbox recovery The restore After the recovery fails, go to the Exchange Server
fails with a flag was not set Management Console, set the recovery flag, and then
catastrophic error when mount the database.
when recovering to attempting to
an alternate recover a
Exchange mailbox to an
Server 2003 alternate
database. Exchange
Server 2003
database.
The Recover- If you specify The –TargetServer attribute should be
53
RecoverableItem the active ResourceGroupName.ClusterServerName.DomainName
cmdlet fails server name .
specifying that the when
specified recovery recovering a
options were not storage group
valid. or database for
Exchange
Server
Clustered
Continuous
Replication
(CCR) through
the command-
line interface
(CLI), the
recovery fails.
eseutil execution This error To bring the database to a Clean Shutdown state, move
fails with error occurs if the the .stm file to the same folder as the .edb file, and then
code 0xfffff764 in .stm and .edb run eseutil with the appropriate parameters.
the Application log. files that are
associated with
a database are
not in the same
folder. When
this occurs, the
database is not
brought to a
Clean
Shutdown
state.

The following table provides troubleshooting guidance on recovery issues for computers running
SQL Server.
The database recovery fails. If you recover a SQL Server When you recover a SQL Server
database by selecting the database using the latest
latest recovery point and then recovery point, DPM performs
perform another recovery the recovery using the SQL
using the latest recovery Server logs that are available on
point, the database recovery the protected server. After you
will fail. recover the database, you
cannot perform another
54
recovery using the latest
recovery point until you perform
a synchronization with
consistency check.
However, you can recover to a
recovery point listed just prior to
the latest recovery point. In this
case, you will recover the
database to the latest available
recovery point on the DPM
server; however, the logs on the
SQL Server will not be utilized.
This is because the logs on the
SQL Server were already used
as part of the latest point
recovery that you performed
earlier.
Windows SharePoint Recovery Issues

The following table provides troubleshooting guidance on recovery issues for computers running
Windows SharePoint Services.
Windows SharePoint Services Recovery Issues
Microsoft Office The item may still be in We recommend that you recover the item
SharePoint the site or site from the site or site administrator’s Recycle
Server 2007 – Unable administrator’s Recycle Bin, if it is the same version of the file that
to see recovered list Bin. you are looking for, rather than recover it from
item. the replica. Alternatively, clear both the
Recycle Bins in SharePoint and then retry the
recovery.
Microsoft Office The item already exists If you are recovering an item that already
SharePoint in the list, or is in either exists in either the user’s or the site
Server 2010 – the user’s Recycle Bin administrator’s Recycle Bin, DPM will restore
Recovering list item or the site a duplicate item and apply the parent folder’s
does not recover its administrator’s Recycle permissions. However, if the item has been
permissions. Bin. deleted from all Recycle Bins, then it will be
restored along with the permissions.
Recovery points are DPM backs up the Run the catalog task.
not displayed for sites databases and then
or documents in DPM performs a catalog task
Administrator Console to get a list of all the
in the Recovery task URLs in the content
area. (If you double- databases. By default,
55
click the content this process runs three
databases, the sites hours after the first
do not appear.) scheduled backup job
of the day. If the
catalog task has not
completed, you will not
be able to expand the
content database in the
DPM Recovery UI.
After recovering a If you recover a To resolve this issue, do the following:
Windows SharePoint Windows SharePoint  Delete the config cache on the front-end
Services farm, you Services farm that had Web server that was not used for the
cannot attach a a detached database
recovery.
content database. prior to recovery, you
cannot attach the The cache is a set of XML files located in
database after the the following folder: <drive
recovery if the front- letter>:\Documents and Settings\All
end Web server was Users\Application
different than the Data\Microsoft\SharePoint\Config\<config
database DPM used database ID>.
for the recovery. Caution
Do not delete the folder. Delete
only the XML files in the folder.
 The cache will automatically rebuild,
enabling you to attach the database.
Recovery of the If a Quick Fix To resolve this issue, do the following:
Windows SharePoint Engineering (QFE) is 1. Recover the Windows SharePoint
Services farm fails. installed after the Services farm by using the Recovery
Windows SharePoint
Wizard.
Services farm is
protected, the recovery 2. On the front-end Web server, from the
will fail. command prompt, type psconfig -cmd
upgrade -wait -force -inplace b2b.
Consistency check If you perform a You must stop protection, and then use the
fails with "Data source recovery after the New Protection Group Wizard to reprotect the
not found". content database is Windows SharePoint Services farm.
deleted from SQL
Server Management
Studio, and not through
the Sharepoint
Console, the
consistency check will
fail.
Permissions or ACLs The document or list DPM recovers the permissions or ACLs only
for the document or item is being restored if the item is being restored to the original
list item have not been to an alternative URL location.
restored. within the same farm.
56
Recovering a The recovery point is Recover the database by using the “Recover
SharePoint content located on the tape and to any SQL Instance” option.
database to its original the database has been
location fails. removed from the
SharePoint farm.

The following table provides troubleshooting guidance on tape library recovery issues.
Tape read errors occur when File server data source If tape read errors occur, do the
attempting to recover a file recovery from tape will fail if following:
server volume from tape. there are corrupt files on the 1. Select the contents of the
tape. volume for recovery rather
than the entire volume. For
example, select all of the files
and folders on <drive
letter>:\ instead of selecting
the entire <drive letter>:\
<volume>.
2. Retry the recovery.
DPM will attempt to skip over
the corrupt files on tape.
Caution
Because of serious tape
corruption, DPM may not
be able to find the files
that are not corrupt.
Therefore, DPM may not
succeed in recovering
the selected individual
files.

The following table provides troubleshooting guidance on end-user recovery issues.
57
End-user Try either one of the following solutions:

recovery (EUR)  Copy DPMADSchemaExtension.exe from
configuration fails on DPM install folder to the active directory
Windows Server 2008.
and run it from there.
 In Server Manager, click Add roles. Select
Active Directory Domain Services role and
install it. Launch DPM again and configure
EUR.
If you enable end-user This issue occurs if To resolve this issue, you must download
recovery functionality the computer is Microsoft Knowledge Base article 903234 to
on your DPM server secured by DPM or update the Timewarp client on the client
and then try to recover if there are no local computer. To download article 903234, see An
an earlier version of a shadow copies of update is available to the way that the Shadow
file or folder from your the file or folder on Copy Client accesses shadow copies in
computer, your the computer. Windows Server 2003 and in Windows XP
computer automatically (http://go.microsoft.com/fwlink/?
tries to recover the file LinkId=189625).
or folder from the DPM
server.
Computers in Workgroups and Untrusted

Domains Recovery Issues
Computers in Workgroups and Untrusted

Domains Recovery Issues
Protection agent Password set for Reset the password.

refresh fails after protection was For more information, in the DPM 2010
system state recovery updated after the Operations Guide, see Updating Password for
of protected system state of the Workgroup or Untrusted Computers
computer. protected machine (http://go.microsoft.com/fwlink/?
was backed up. LinkId=196942).
58
Troubleshooting Tape Library Management
Issues
The following table provides troubleshooting guidance on tape library issues.
Tape Library Issues
Error Message Possible Cause Resolution
SetDPMSharedDatabase fails. Exceptions have not been Add the following exceptions to
added to the firewall. the firewall on the DPM server:
 SqlBrowser
 SqlServer
 Windows Management
Instrumentation
Tape is written by a non-DPM DPM only supports To resolve this issue, do the
application using a physical block reading a physical block following to erase the contents
size either less than 1024 bytes size between 1024 bytes of the tape:
or more than 65536 bytes.The and 65536 bytes.  In DPM Administrator
tape in <LibraryType> <Library> Therefore DPM cannot Console, in the
at <MediaLocationType> read or overwrite the
Management pane, on the
<MediaLocationInfo> has been contents of this tape.
Libraries tab, select the
written to by another tape backup If the tape was used by
application using an unsupported tape, and then click Erase
any other backup
physical block size. tape
application with an
unsupported block size, After erasing the tape, DPM
the block size information will be able to use it for
will persist with the tape. backups.
Note
If you have a
standalone tape
drive, you might
have to erase the
tape using a tool
other than DPM.
A new tape library or stand-alone After performing the After you install a new tape
tape drive does not appear in Rescan operation, DPM library and then perform the
DPM Administrator Console. Administrator Console Rescan operation, if the tape
cannot identify a new tape library does not appear on the
library or stand-alone tape Libraries tab in the
drive on the DPM server. Management task area of DPM
Administrator Console, do the
following:
 Ensure that the tape library
and drives are properly
59
connected.
 For SCSI connections,
ensure that the logical unit
number (LUN) for each
device is unique.
 Ensure that Device
Manager lists all tape
libraries and stand-alone
tape drives attached to the
DPM server. If they do not
appear in Device Manager,
do the following:
a. In Control Panel,
double-click System.
b. In the System
Properties dialog box,
on the Hardware tab,
click Device Manager.
c. In Device Manager,
expand Tape drives,
and if you added a tape
library, expand Medium
Changers.
d. Right-click the tape
drives and medium
changers if you added a
tape library, and then
click Scan for
hardware changes.
e. After the devices
appear in Device
Manager, return to the
Libraries tab in the
Management task
area, and then click
Rescan.
 Ensure the proper drivers
are installed for each
device.
Library jobs start to fail after The library jobs fail To update the DPM library
removing a tape that was stuck in because Media Manager information, do the following:
the tape library. continues to report the 1. Properly remove the tape
nonexisting tape in the from the drive by following
drive.
the recommended
procedures of the tape
60
library vendor.
2. Power down and then
restart the tape library.
3. In DPM Administrator
Console, on the Libraries
tab in the Management
task area, click Inventory
library.
4. In the Inventory dialog box,
select Detailed inventory,
and then click Start.
DPM Library Management If you are using the We recommend that you run
cannot find the Quantum tape incorrect drivers for the Ltotape.sys for the Quantum
drive in the Qualstar tape library. Quantum tape drive, DPM LTO drives.
Library Management
cannot find it because the
drive was not initialized
and configured.
A new tape does not appear in After you add a new tape To display the new tape, do the
DPM Administrator Console. to your tape library following:
without using Unlock 1. In DPM Administrator
library door or Add tape Console, click
(IEPort), the new tape
Management on the
might not appear in the
taskbar.
DPM Library
Management task area. 2. On the Libraries tab, in the
Actions pane, click
Inventory library.
select Fast inventory, and
then click Start.
A tape does not appear in the If you run a detailed To display the tape in the
Library Management task area. inventory on the tape Library Management task area,
library after inserting a insert the tape in the tape library
tape, the tape does not and then do the following:
appear in the Library 1. In DPM Administrator
Management task area. Console, click
Management on the
navigation bar.
2. On the Libraries tab, select
the tape library.
3. In the Actions pane, click
Inventory.
select Fast inventory, and
61
then click Start.
5. After the fast inventory is
complete, in the Inventory
dialog box, select Detailed
inventory, and then click
Start.
DPM does not detect a newly In DPM Administrator You must first run a fast
inserted tape. Console, if you run a inventory, which detects any
detailed inventory, it will tape (with or without a bar code)
not detect inserted tapes in any library.
that are new. After you run a fast inventory,
the detailed inventory will detect
the new tape.
Troubleshooting Reporting Issues

The following table provides guidance for troubleshooting issues that may occur when
configuring, viewing, exporting, or subscribing to DPM reports.
General Reporting Issues
Issue Possible cause Resolution
E-mail functionality 1. The Reporting Services Service Account

for reports is not should be changed to run under a domain
working. account.
a. Open Reporting Service Configuration
Manager from Start Menu->SQL
Server 2008->Configuration Tools.
b. Select the service account to be a
domain account having permissions to
send mail from SMTP server.
2. Set the SMTP settings from the DPM
Administrator Console or the Reporting
Service Configuration Manager.
a. Enter the SMTP server as SMTPHost.
b. Ensure that the account is the same as
the service account.
3. Set the SQL Service to run under any
domain account from SQL Server
Configuration Manager
4. Open reporting configuration file. By default
it will be at C:\Program Files\Microsoft
62
DPM\SQL\MSRS10.MSDPM2010\Reportin
g
Services\ReportServer\rsreportserver.config
. Change the SMTP Authenticate tab to 2.
You subscribe to five If you schedule all five When a DPM server is protecting a large
reports for e-mail reports to be sent at number of file servers, we recommend that you
delivery, but not all the same time, the stagger the delivery schedule for reports sent by
reports are memory limitations of e-mail.
delivered. SQL Server Reporting
Services may prevent
some reports from
being sent.
Reports are not This issue is most Depending on the cause of the issue, there are
received by commonly caused several solutions you can try:
designated e-mail when the security  Verify that the e-mail addresses used for
recipients and DPM settings of the subscribing to reports are valid.
does not generate recipient e-mail
any errors. address restrict e-mail  Verify that the security settings on the e-
delivery. This could mail alias or distribution group do not
happen, for example, if restrict e-mail notifications from being
the recipient e-mail delivered to the intended addressee(s).
address is a  Verify that the From address, which is
distribution group specified on the SMTP Server tab for use in
whose properties are
e-mail messages, contains a valid e-mail
set to only receive e-
address.
mail from authorized
senders. For more information, in Deploying DPM 2010,
see Configuring the SMTP Server
This issue may also
occur when:
 The e-mail
address of the
recipient is not
valid.
 The From
address for e-mail
messages on the
SMTP Server tab
is an invalid or
unmonitored e-
mail address.
When exporting If you try to export an This is an issue with Internet Explorer, and
HTML reports to HTML report to Web occurs only the first time you export a report.
MHTML, charts do Archive (MHTML Subsequent exported reports will display
not display correctly. format) on a DPM correctly.
server running
Windows Server 2003
Service Pack 2 (SP2),
63
the charts on the
report will not display.
When you try to The proxy server To display reports in Internet Explorer, the proxy
view a DPM report, settings in Internet server for local connections needs to be
you see a “Cannot Explorer may not be bypassed.
find server” or “DNS set correctly. To bypass the proxy server for local
error” error connections:
message, or the
1. In Internet Explorer, on the Tools menu,
report is not
displayed in Internet click Internet Options.
Explorer. 2. In the Internet Options dialog box, on the
Connections tab, click LAN Settings.
3. In the LAN Settings dialog box, ensure that
the correct proxy server name is entered
and the Bypass proxy server for local
connections check box is selected.
4. If the proxy server setting is correct but you
cannot select the Bypass proxy server for
local connection check box because of
company policy, then select Advanced
Options and add Http://DPM <server
name> to Exceptions.
One or more of the An administrator has To restore the missing DPM report types, do the
DPM report types manually deleted one following:
are missing from the or more of the DPM 1. Ensure that no DPM jobs are running.
Reporting task area report templates from
of DPM the DPM computer. 2. Close DPM Administrator Console.
Administrator 3. In Add or Remove Programs, uninstall
Console. DPM with the Retain data option enabled. If
you do not enable the Retain data option,
your existing data protection configuration
will be deleted, including the protection
schedule, replicas, and shadow copies.
4. After uninstallation has completed
successfully, reinstall DPM.
DPM does not If both Internet To export reports to MHTML, Excel, or PDF
export reports to Explorer Enhanced formats, you must disable Internet Explorer
MHTML, Excel, or Security and Secure Enhanced Security.
PDF formats. Socket Layer (SSL) To disable Internet Explorer Enhanced
options are enabled, Security:
DPM cannot export
1. In Add or Remove Programs, click
reports to MHTML,
Microsoft Excel, or Add/Remove Windows Components.
PDF formats. 2. In the Windows Components Wizard
dialog box, clear the Internet Enhanced
Security Configurations check box.
64
A report has no data One of the following When a report fails, the report is run again as
in it when you view it problems might have soon as the DPM computer is back online or at
from DPM prevented the report the next regularly scheduled time. This resolves
Administrator from running at the the problem of not being able to view the report
Console or in an e- scheduled time: from DPM Administrator Console.
mail attachment.  Reporting could To ensure that e-mail subscribers receive
not connect to the the corrected report:
DPM database. 1. Select the report type in the Reporting task
 The DPM area of DPM Administrator Console.
computer was 2. In the Actions pane, click Schedule.
down for 3. In the Frequency drop-down list, click
maintenance. Once.
 The DPM 4. In the Date and Time drop-down lists,
computer was select the next available schedule.
being restarted.
5. After the "run once" report is generated, it
will be sent to all subscribers. After the
report has been successfully sent, set the
reports back to their regular schedules.
The administrator is DPM Setup To restore the default setting, manually remove
always prompted for automatically adds the the DPM computer name from the Trusted
user credentials to name of the DPM Sites zone and add it to the Local Intranet
access DPM computer to the Local zone.
reports. Intranet security zone For more information on Internet Explorer
in Internet Explorer to security zones, in the Internet Explorer 6.0
permit access to DPM Resource Kit see Security Zones
reports without having (http://go.microsoft.com/fwlink/?LinkId=52308).
to provide additional
credentials. If you
manually add the
name of the DPM
computer to the
Trusted Sites zone,
you will overwrite this
default setting, and
Internet Explorer will
prompt for credentials
before granting access
to DPM reports.
When you try to The To resolve this error, you must ensure that the
view reports, you DPMR$<MachineNam DPMR$<MachineName> account has the Allow
receive the following e> account may not log on locally user right.
error message: have the required user To assign the Allow log on locally user right
An error has occurred rights. to the DPMR$<MachineName> account:
during report processing. 1. In Administrative Tools, open Local
(rsProcessingAborted)
Security Policy.
Get Online Help
2. Under Security Settings, expand Local
Policies, and then click User Rights
65
Logon failed. Management.
(rsLogonFailed) Get
3. In the details pane, right-click Allow log on
Online Help
locally, and then right-click Properties.
4. In the Allow log on locally Properties
Logon failure: the user
dialog box, click Add User or Group.
has not been granted the
requested logon type at 5. In the Select Users, Computers, or
this computer. Groups dialog box, click Locations, click
the name of the DPM server, and then click
OK.
6. In the Select Users, Computers, or
Groups dialog box, enter DPMReport, and
then click OK.
7. In the Allow log on locally Properties
dialog box, click OK.
8. In the details pane, right-click Deny log on
locally, and then right-click Properties.
9. If the DPMR$<MachineName> account is
listed, select DPMReport, and then click
Remove.
Disk utilization for For existing protection Disk utilization for these replicas will be correct
inactive replicas is groups or file servers, in reports generated at least a day after the
not reported current storage pool change is made.
correctly in the Disk details do not display
Utilization Report. the current information
(for example, up to the
minute) for replicas
that were removed,
added, or removed
from protection on the
day that the report is
generated.
Notification Your notification To enter the correct user name for
deliveries for reports deliveries will fail if you authentication, in the Options dialog box, on
and alerts fail. enter the incorrect the SMTP Server tab, in the User name box,
user name for type the domain name of the user that appears
authentication on the in the "From" address box. For example, if the
SMTP server. user name in the "From" address box is
Terry@AdventureWorks.com, in the User
name box type <domain name>\Terry.
Logon failure This error occurs when To add a domain user account, perform the
(0x80070569): The your security policy following steps:
user has not been settings prevent the 1. Remove the DPMR$DPMMACHINENAME
granted the user from logging on account from the
requested logon using a local user
DPMDBReaders$DPMMACHINENAME
type at this account.
group.
computer.
66
2. Delete the DPMR$DPMMACHINENAME
account.
3. Add a domain user account (not an
administrator account) to the
DPMDBReaders$DPMMACHINENAME
group.
4. Perform the following steps to modify the
DPMReporterDataSource account to use
this domain user account.
For more information about modifying the
Report Manager, see Data Sources
Properties Page (Report Manager)
LinkId=190211).
5. Edit the Allow log on locally Group Policy
setting and add the domain user account.
Troubleshooting Performance Issues

This section includes troubleshooting assistance for performance issues.
In This Section
Network Bandwidth Issues

The following table provides guidance for troubleshooting network bandwidth issues.
Network bandwidth usage is The quality of service (QoS) If you enabled network
not being throttled. may not be enabled on the bandwidth usage throttling in
production server and the DPM Administrator Console
DPM server. and the network bandwidth
usage is not being throttled,
verify that QoS is enabled on
the production server and the
DPM server.
67
Troubleshooting Database Issues
System Center Data Protection Manager (DPM) 2010 processes rely on a database created in an
instance of SQL Server 2008 SP1.
The DPM database (DPMDB) stores all DPM settings, configuration, and reporting information for
DPM.
A database failure can cause DPM jobs to fail, interfere with the use of DPM Administrator
Console, prevent DPM reporting, and stop the DPM service. A backlog of requests caused by low
memory or high CPU usage also can cause client timeouts (when DPM processes take a long
time to establish a connection to SQL Server or run a SQL query).
Possible causes of DPM database failures include the following:
 An unusually high number of protection jobs being processed on the DPM server at one time,
and SQL Server is unable to handle the volume of requests in a timely manner. This is the
most common cause of client timeouts and general network errors.
 A database or transaction log that DPM uses has run out of disk space.
 The DPM database enters an inconsistent state or becomes corrupted.
 The SQL Server service is not running or is not configured correctly.
Some database failures in DPM are caused by transitory problems that may resolve themselves.
Examples include insufficient resources, client timeouts, insufficient disk space for transaction
logs, deadlocks in SQL Server, recoverable database errors, and timing issues.
Before you run diagnostics for this type of database failure, perform the following steps on the
DPM server to ensure that the problem is not transitory.
To resolve issues that might cause a transitory database failure

1. Verify that the SQL Server service is running. In Administrative Tools, open
Services, and verify that the status of the SQL Server (MSDPM2010) service is
Started. If it is not, right-click the service, and then click Start or Resume, as
appropriate.
2. If this does not fix the problem, close and reopen DPM Administrator Console.
3. If this does not fix the problem, stop and restart both the DPM service and the SQL
Server (MSDPM2010) service. (In most cases, restarting the DPM service will resolve
the issue.) For instructions, see Verifying Status of the DPM Service.
If you experience database failures in DPM that are not transitory in nature, the issues can be
complex. You will need to work with your SQL Server administrator to diagnose and resolve the
related issues. The following Database Errors table provides a starting point for resolving
specific database errors. The Database Exceptions table later in this topic provides information
about how to troubleshoot database exceptions.
Database Errors
Error To troubleshoot this error
Error 940: Unable to connect to the database Ensure that the DPM instance of SQL Server
68
because of a fatal database error. It is unlikely (MSDPM2010) service is running. Then use
that the database itself has been damaged. Windows Event Viewer to find information about
related events.
Error 941: Unable to connect to the DPM To resolve issues related to database
database. connection failures
1. Ensure that the DPM service is running.
2. Resolve transient issues that might be
temporary database connection failures.
3. Make sure that SQL Server is configured
correctly. For information about configuring
SQL Server for use with DPM 2010, see
Manually Installing Prerequisite Software
LinkId=100602).
Error 942: Database integrity is in question If the integrity of the DPM database is in
because of a hardware or software problem. question, contact your SQL Server
administrator. You might need to repair or
restore the database in SQL Server from
backup media.
Inform the administrator every time this error is
encountered. Look at Windows Event Log for
SQL Server/media failures. 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. In some cases, it may be
necessary to restore the database.
To resolve issues related to a database that
may be corrupt
1. Use Event Viewer on the DPM server to
check for I/O problems at the time of the
alert. I/O failures in the event log might
explain why the database was corrupted. If
that is the case, you might want to repair or
replace the hard disk before restoring the
database.
2. To determine the extent of the database
problem, perform a database check on the
database for which integrity is in question.
In SQL Query Analyzer, enter the following
command:
dbcc checkdbdatabasename
3. Depending on the nature of the problem,
you might need to repair or restore the
DPM database. Some problems, such as
indexing and caching problems, can be
resolved by repairing the database or
69
restarting SQL Server. Work with your SQL
Server administrator to determine the best
course of action.
Error 943: Unable to connect to the DPM If DPM finds that the database is in an
database because the database is in an inconsistent state, the problem is unlikely to
inconsistent state. resolve itself. For help with troubleshooting the
problem, contact Microsoft product support. For
more information, see Microsoft Help and
Support (http://go.microsoft.com/fwlink/?
linkid=45276).
Error 944: Database operation failed.  If you are experiencing client timeouts and
general network errors that are possibly
related to SQL Server being unable to
handle the volume of requests, modify
protection schedules for protection groups
to stagger protection jobs.
 A high incidence of client timeouts may be
a sign that the volume that stores your
database files and transaction logs is highly
fragmented. If needed, use Disk
Defragmenter to defragment the volume.
 A shortage of disk space for a SQL Server
database file or transaction log generates a
warning or error in SQL Server, depending
on how critical the shortage has become. If
transaction logs overflow, the DPM service
probably will shut down after one or more
failed attempts to access the database.
To resolve issues caused by a shortage
of disk space for databases or
transaction logs
a. Use Windows Event Viewer to get
additional information about the
problem.
b. Use SQL Query Analyzer to get
information about the size of the
databases and the use of transaction
log space by entering the following
commands:
sp_helpdb — Reports the size of each
database file.
dbcc sqlperf (logspace) — Reports
the current sizes of transaction logs.
c. Shrink the database and transaction
logs. In SQL Query Analyzer, enter the
70
following commands:
dbcc shrinkfile
(databasenamelog.dat) — Shrinks the
transaction logs for the specified
database.
dbcc shrinkfile (databasename_dat)
— Shrinks the specified database file.
If disk space is still insufficient, extend the
volume that contains the files to ensure
sufficient disk space for the transaction log
during peak performance.
 This error can also occur if the SQL Server
administrator has deleted the database,
taken the database offline, or detached the
database for maintenance. If the database
is offline or detached for maintenance, retry
the operation after the database is brought
online. If the database was deleted, restore
the database from tape backup, and then
run DpmSync.
Error 945: Unable to connect to the DPM For general database failures, ensure that the
database because of a general database DPM service is running on the DPM server.
failure. Then use Windows Event Viewer to find
information about related events. On a new
DPM server, ensure that SQL Server is
configured correctly.
To resolve issues related to general
database failures
1. Ensure that the SQL Server (MSDPM2010)
service is running.
2. Resolve transient issues that might be
temporary database connection failures.
3. Make sure that SQL Server is configured
correctly. For information about configuring
SQL Server for use with DPM, in the
DPM 2010 Deployment Guide, see
Configuring DPM 2010
LinkID=179157).
4. If general database failures persist, contact
Microsoft product support for help with
troubleshooting the problem. For
information, see Microsoft Help and
Support (http://go.microsoft.com/fwlink/?
linkid=45276).
71
Database Exceptions
Exception To troubleshoot this exception
Exception 5168: Login failed for user <user DpmSync fails when trying to restore the
name>. DPMDB database because it cannot open the
DPMDB database requested by the login.
Verify that the DPM installation contains a new
DPMDB database and that it is online before
trying to restore an older database. If a new
database does not exist on the DPM
installation, uninstall and then reinstall DPM.
After the installation is complete, run DpmSync
again.
Additional Resources for Troubleshooting

Database Issues
This following is a list of additional resources you might use to help diagnose and resolve DPM
database issues.
 Configuring SQL Server for use with DPM, see Installing DPM 2010
 Using the sp_helpdb system stored procedure for SQL Server in the Transact-SQL Reference
 Using the Database Console Commands (DBCC), DBCC SQLPERF and DBCC
SHRINKFILE for SQL Server located in the “DBCC” section of the Transact-SQL Reference
 Using the Windows Server 2008 event logs to identify problems.
 Configuring and maintaining physical storage components in SQL Server 2008 to meet
capacity, throughput, and performance requirements. For more information, in the DPM 2010
Operations Guide, see Managing Performance (http://go.microsoft.com/fwlink/?
linkid=189733).
Troubleshooting Job Status Issues

The following table provides troubleshooting guidance on job status issues.
Job Status Issues
DPM Administrator Console The DPM jobs are still in While DPM jobs are in
displays an error for jobs that progress and have not progress, DPM continually
are in progress and have not finished running. retries the job until it is
completed. finished running. After the job
72
is complete, DPM will display
the correct job status.
File synchronization or recovery DPM may be perpetually Verify that DPM is not
point creation jobs continue to attempting to cancel the job. transferring data, and then
run, even when DPM is not cancel the job. If the job
transferring data. continues to run, restart the
DPM server.
Troubleshooting the DPM System Recovery

Tool
The following table provides troubleshooting guidance on DPM System Recovery Tool (SRT)
issues.
DPM System Recovery Tool Issues
On the computer that you are This issue occurs when there To resolve this issue, close
recovering, the Recovery are communication problems and then restart the Recovery
Center Rollback Wizard between the DPM SRT server Center Rollback Wizard.
suspends during the and the protected server.
progressing state. After you
restart the computer, it
remains suspended.
The restore operation fails. When you replace a disk that Replace the disk that has
has crashed with a disk that crashed with one that does
contains partitions, the restore not contain any partitions.
operation may fail.
Volume attributes and access This issue may be due to the If the recovery fails, we
control lists (ACLs) do not following: recommend that you restart
restore properly.  Compressed volumes are the computer with a Boot
restored as expected; Client CD, and then delete
the contents in the temporary
however, you must set
folder at the root of the
compression attributes
volume.
manually.
 DPM does not restore the
security attribute of the root
of a volume.
The recovery sets included in During a restore, the recovery If this issue occurs, you must
a recovery point appear as sets included in a recovery close the user interface,
unspecified in the user point are not populated in the restart the DPM System
interface. user interface and appear as Recovery Tool Data Store
unspecified. service, and then restart the
73
restore operation.
After you create a new If the schedule console is To resolve this issue, refresh
recovery set, it does not already open, the new recovery the user interface. If the new
appear in the user interface. set may not appear. recovery set still does not
appear, close and then restart
the user interface.
Application data is not in a DPM SRT backs up FAT32 No resolution for this issue.
consistent state on FAT32 volumes as live volumes and
volumes. cannot guarantee an
application consistent state of
data, or provide a single point
for all files in the volume.
DPM SRT does not work A previous version of Recovery Uninstall any previous
correctly. Manager may have been versions of Recovery
installed before installing the Manager before installing the
DPM SRT. DPM SRT.
Troubleshooting Disaster Recovery Issues

The following table provides troubleshooting guidance on DPM disaster recovery issues.
Disaster Recovery Issues
Error ID: 31008 appears If a protected domain controller For disaster recovery
because DPM only refreshes or secondary server becomes scenarios, in DPM
protection agents every 30 unavailable, the protection Administrator Console you
minutes. agents are not automatically must wait for the scheduled
refreshed in DPM installation list refresh, which is
Administration Console. a maximum of 30 minutes.
To manually refresh the
protection agents, in the
Management task area, click
the Agents tab, select the
computer, and then in the
Actions pane, click Refresh
information.
Troubleshooting General DPM Issues

The following table provides troubleshooting guidance on general System Center Data Protection
Manager (DPM) 2010 issues.
74
General DPM Issues
Issue Possible Resolution

Cause
DPM stops working when master DB is recovered. If the master DB was

protected from the same
instance as DPMDB, DPM
will stop working when the
master DB is recovered.
Scheduled jobs not getting triggered when DPM Ensure that the SQL Server
uses a remote SQL instance services are running as
inbuilt accounts (local
system network service) or
domain accounts. Running
the SQL Server services
under the "Managed service
account" is not supported.
Some of the DPM Management Shell cmdlets do not If the NETBIOS name of the
work on DPM servers that have NETBIOS names DPM server is longer than
longer than 15 characters. 15 characters, use the
clipped name within the
cmdlets.
Unable to add GUID Partition Table (GPT) disk to To resolve this issue, either
storage pool. retry the operation or wait
30 sec.
After switching back protection, jobs for some data A new 1. Attach agent from
sources start failing with Access Denied errors. backend/ primary DPM to the
physical newly added computer.
node was
2. Run SetDPMServer
added to
-DPMServerName
a
SharePoi <primaryDPM.domain.com>
nt farm or on the newly added
cluster computer.
after 3. Make sure the primary
switch protection is green.
protection
. This 4. Now run modify
node was protection group on the
protected secondary DPM server
directly by for the protection group
the containing affected data
secondar source.
y server. a. Expand the primary
The
DPM server node in
primary
the Modify
DPM did
not know Protection Wizard.
75
about this b. Expand the
new node SharePoint front-
until end/resource group
protection to which the new
was computer was
switched
added.
back.
5. Save the protection
group.
DPM engine on secondary server stops working Lack of Change the name resolution
after it is denied access to a file on the primary permissio order.
server with the following stack: ns to a For more information see
Access to the path share or a How to change name
'\\dpmserver.contoso.com\MTATempStore$\PSInfo\78b18367- name resolution order on Windows
eb4e-4e1d-8cfd-a7e41cb48d6b.xml' is resolution 95 and Windows NT
denied.</ExceptionMessage><ExceptionDetails>System.Unauth conflict. (http://go.microsoft.com/fwlin
orizedAccessException: Access to the path k/?LinkId=187186).
'\\dpmserver.contoso.com\MTATempStore$\PSInfo\78b18367-
eb4e-4e1d-8cfd-a7e41cb48d6b.xml' is denied.
at System.IO.__Error.WinIOError(Int32 errorCode, String
maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode,
FileAccess access, Int32 rights, Boolean useRights, FileShare
share, Int32 bufferSize, FileOptions options,
SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean
bFromProxy)
at System.IO.FileStream..ctor(String path, FileMode mode,
FileAccess access, FileShare share, Int32 bufferSize, FileOptions
options, String msgPath, Boolean bFromProxy)
The user cannot open DPM Administrator Console. If the user You must add the user to the
is a Administrators group.
member
of a group
other than
the
Administr
ators
group,
such as
Backup
Operator,
they will
not have
access to
DPM
Administr
ator
Console.
Error 30115: DPM failed to synchronize changes for The Retry the operation at a later
76
<Datasource Type> <Datasource Name> on shadow point when the churn is
<Server Name>. copy expected to be lower.
storage
area did
not have
sufficient
storage
space to
hold the
churn on
the
protected
computer.
Error 30116: VSS has deleted a shadow copy. The Increase the space allocated
shadow for the shadow copy storage
copy area for protected volumes
storage on this computer.
area To change the settings for
might shadow copies, do the
have run following:
out of
1. Click Start, click Control
disk
space on Panel, double-click
the server Administrative Tools,
<server and then double-click
name>. Computer Management
to open Computer
Management.
2. In the console tree,
expand the node to
Computer
Management/System
Tools/Shared Folders.
3. Right-click Shared
Folders, select All
Tasks, and click
Configure Shadow
Copies.
4. Click the volume where
you want to make
changes, and then click
Settings.
5. In the Settings dialog
box, change the settings
as appropriate.
Note the following:
 To perform this
77
procedure, you must be
a member of the
Administrators group on
the local computer, or
you must have been
delegated the
appropriate authority. If
the computer is joined to
a domain, members of
the Domain
Administration group
might be able to perform
this procedure.
 There is a limit of 64
shadow copies per
volume that can be
stored. When this limit is
reached, the oldest
shadow copy will be
deleted and cannot be
retrieved.
DPM 2010 Error Code Catalog

DPM error codes are generated by a state or action, and display a message that provides
information or notifies you of a problem. When appropriate, the error message includes a
recommended action.
Some error messages refer you to the DPM 2010 Operations Guide or other DPM
documentation. For more information about resolving DPM errors, see the DPM Troubleshooting
Guide (http://go.microsoft.com/fwlink/?LinkId=66740).
User interface messages that are informational or instructional are not included in this catalog.
For example, the message associated with error code 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?” is not listed in this catalog.
Some error messages contain placeholder text, such as <specified server>. The placeholder text
indicates a value that DPM provides in the actual error message.
Error Messages
78
Error Error Message Recommended Action
Code
7 Unable to connect to the Make sure that the DPM server is a member of a
Active Directory Domain domain and that a domain controller is running. Also
Services database. verify that there is network connectivity between the
DPM server and the domain controller.
16 DPM cannot access the path Check the path and enter it again.
<file name> because part of
the path has been deleted or
renamed.
11 DPM cannot browse <server 1) Verify that <server name> is online and remotely
name> because the host is accessible from the DPM server.
unreachable. 2) If a firewall is enabled on <server name>, verify that
it is not blocking requests from the DPM server.
12 DPM cannot browse <server Verify that the computer running DPM has DCOM
name> because access was launch and access permissions for <server name>, and
denied. that the system time on the DPM server and <server
name> is synchronized with the system time on the
domain controller.
13 DPM cannot browse <server
name> because the protection
agent is not responding.
14 DPM cannot browse <server To troubleshoot this error:
name> because of a 1) Verify that <server name> is remotely accessible
communication error between from the DPM server.
DPM and the protection agent
2) If a firewall is enabled on <server name>, verify that
on the computer
3) Restart the DPM Protection Agent (DPMRA) service
on <server name>. If the service fails to start, reinstall
the protection agent.
15 DPM cannot browse <server To install a protection agent on <server name>, in the
name> because a protection Management task area, on the Agents tab, click Install
agent is not installed on in the Actions pane.
<server name> or the
computer is restarting.
30 DPM cannot contact <server Restart <server name> and then try the operation
name> until you complete the again.
protection agent installation by
restarting the computer.
31 DPM cannot browse <server 1) Make sure that <server name> is online and
name> because the host is remotely accessible from the DPM server.
unreachable. 2) If a firewall is enabled on <server name>, make sure
that it is not blocking requests from the DPM server.
32 DPM cannot browse <server On the Agents tab in the Management task area, check
79
name> because access is the status of the agent. Also, verify that the system
denied. times on the DPM server and the protected computer
are synchronized with the system time on the domain
controller.
33 DPM cannot browse <server If you just installed an agent on <server name>, the
name> because the agent is computer might be restarting. Wait a few minutes after
not responding. Windows starts for the agent to become available.
Otherwise, troubleshoot the problem as follows:
1) Check recent records from the DPMRA source in the
Application Event Log on <server name> to find out
why the agent failed to respond.
2) Make sure that the DPM server is remotely
accessible from <server name>.
3) If a firewall is enabled on the DPM server, make sure
that it is not blocking requests from <server name>.
4) Restart the DPM Protection Agent service on
<server name>. If the service fails to start, re-install the
protection agent.
34 DPM cannot browse <server If you just installed an agent on <server name>, the
name> because of a server might be restarting. Wait a few minutes after
communication error with the Windows starts for the agent to become available.
agent. Otherwise, troubleshoot the problem as follows:
1) Make sure that <server name> is remotely
accessible from the DPM server.
2) If a firewall is enabled on <server name>, make sure
protection agent.
60 The protection agent on Retry the operation.
<server name> was
temporarily unable to respond
because it was in an
unexpected state.
62 Cannot find the volume Make sure that the storage pool disk is accessible. If it
<volume name> on the is not, reallocate disk space and then reprotect the
computer running DPM. data.
64 Volume <volume name> is Please take the recommended action in Event Viewer
offline on the computer on the DPM server.
running DPM.
name>, either because no Management task area, on the Agents tab, click Install
agent is installed on <server in the Actions pane.
name> or because the
computer is rebooting.
80
36 DPM cannot access the path Check the path and enter it again.
<file name> because part of
the path has been deleted or
renamed.
37 DPM cannot access <file Try the selection later or check to see if the object is
name> because an element locked by another process.
has been exclusively locked
by another process.
38 DPM cannot protect <file
name>. The Recycle Bin, the
System Volume Information
folder, non-NTFS volumes,
DFS links, CDs, Quorum Disk
(for cluster) and other
removable media cannot be
protected.
39 DPM failed to access the path Verify that the path can be accessed successfully by
<file name>. using Windows Explorer.
41 DPM failed to communicate 1) Make sure that <server name> is online and
with <server name> because remotely accessible from the DPM server.
the computer is unreachable. 2) If a firewall is enabled on <server name>, make sure
3) If you are using backup LAN, make sure that the
backup LAN settings are valid.
42 DPM failed to communicate 1) Verify that the DPM server has DCOM launch and
with the protection agent on access permissions for <server name> and that the
<server name> because system time on the DPM server and the protected
access is denied. computer is synchronized with the system time on the
domain controller.
2) If this computer does not need to be protected any
more, 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) Check to see that your domain controller can be
reached from the DPM server and the protected
computer.
4) If you are still facing 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 1) Check recent records from the DPMRA source in the
with the protection agent on Application Event Log on <server name> to find out
<server name> because the why the agent failed to respond.
agent is not responding. 2) Make sure that the DPM server is remotely
81
protection agent.
45 DPM failed to communicate To install a protection agent on <server name>, in the
with the protection agent on Management task area, on the Agents tab, click Install
<server name> because the in the Actions pane. If the computer is in the process of
agent is not installed or the restarting, allow some time for the computer to come
computer is rebooting. online.
46 DPM failed to perform the Select fewer objects. 1) If you are trying to protect a
operation because too many large number of data sources on a volume, consider
objects have been selected. protecting the whole volume instead of individual data
Select fewer objects and then sources.
retry this operation. 2)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.
51 Root directories were added to
or removed from protection for
volume <protected server
volume name> on <protected
server name>.
52 The DPM service was unable Restart the DPM Replication Agent service on <server
to communicate with the name>.
protection agent on <server
name>.
56 DPM failed to move data Retry the operation.
because it did not receive the
completion status from the
protection agent.
57 DPM cannot continue to 1) Free up disk space on the protected computer. 2)
protect the data on <protected Retry the operation.
server name> because there
is not enough disk space
available on one or more of its
volumes.
47 Some components of the 1) Verify that the protected computer <protected server
protection agent on <protected name> is not running an unsupported version of the
server name> were not operating system.
installed or configured 2) Consider restarting the computer <protected server
properly. name>. If the problem persists, uninstall the Microsoft
System Center Data Protection Manager 2007
Protection Agent by using Add or Remove Programs on
<protected server name>. Then, on the Agents tab of
the Management task area, reinstall the protection
82
agent on <protected server name>.
48 <Server name> needs to be 1) Restart <server name>.
restarted. This may be 2) If you have any protected data on this computer,
because the computer has not synchronize with consistency check after <server
been restarted since the name> successfully reboots.
protection agent was installed.
3040 To protect the selected data Restart the computer and then synchronize with
0 source, <server name> needs consistency check.
to be restarted for creating the
change journal.
49 The protection agent timed out 1) Make sure that the file <file name> is accessible.
while trying to access the file 2) Synchronize with consistency check.
<file name> for volume
<protected server volume
name> on <protected server
name>.
50 The DPM protection agent 1) Make sure that the file <file name> is accessible.
failed to perform a consistency 2) Retry the consistency check operation.
check on file <file name> for
volume <protected server
volume name> on <protected
server name>.
53 DPM failed to communicate 1) Make sure that <server name> is remotely
with <server name> because accessible from the DPM server.
of a communication error with 2) If a firewall is enabled on <server name>, make sure
the protection agent. that it is not blocking requests from the DPM server.
3) Restart the DPM Replication Agent service on
protection agent.
55 The protected volume Make sure that volume <volume name> can be
<volume name> on <server accessed, and then click the recommended action link
name> could not be accessed. below.
The volume may have been If a new volume <volume name> was created to
removed or dismounted, or replace a previously protected volume with the same
another process may be name, and you want to protect the new volume, you
exclusively using it. 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 inactivate the alert by
clicking "Inactive alert" Otherwise, click the
recommended action link below.
83
58 DPM is out of disk space for 1) Allocate more disk space for the replica. For more
the replica. information, see "How to modify disk allocation" in DPM
Help.
2) Rerun failed operation by clicking the link below.
59 DPM was used to trigger the
recovery for <data source
type> <data source name> on
<server name>. 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.
63 DPM cannot protect <file Make sure that the Resource Group has one virtual
name> because there is no name configured. Also, check that dependencies
virtual name configured for the between cluster resources are configured correctly.
Resource Group to which the
file belongs.
77 The consistency check job Rerun the consistency check job.
failed due to an internal error.
91 The replica of <data source
<server name> is not
consistent with the protected
data source.
92 Cannot access volume on the Stop protection of <data source name> and then
replica of <data source type> reconfigure protection for this data source.
<data source name> on
<server name>.
242 The share "<object name>" on Make sure that the share name and computer name
<server name> is not currently are accurate.
protected.
78 DPM is unable to continue Refer to the KB article http://go.microsoft.com/fwlink/?
protection for data sources on LinkId=95132 for more details on resolving this error
the protected server <server
name> since it has detected
an incompatible filter installed
on this server.
245 You must specify the e-mail In the Recipients box on the Recovery tab, type the e-
addresses of users whom you mail addresses.
want to notify about this
recovery operation.
84
246 Recovery cannot be Restart the recovery
performed right now as some
other conflicting job is running.
Please go to Alerts tab in
Monitoring task area for
details.
93 The replica of <data source If the replica creation is scheduled for a later time, no
type> <data source name> on action is required. If you have chosen to manually
<server name> is being create the replica, copy the data and then synchronize
created. with consistency check.
94 The data source <data source No action is needed. Wait for DPM to update its
type> <data source name> on database to reflect that this data source is no longer
<server name> is no longer protected.
protected and DPM no longer
has a replica for it. The replica
was probably deleted because
the ‘Stop Protection without
retaining replica’ task was run
on this data source.
95 Job failed on replica of <data Cancel the ongoing operation, or wait for it to complete.
source name> on <server Then retry the operation.
name> because of ongoing
synchronization.
96 Job failure on replica of <data Wait for the replica creation operation to complete.
source name> on <server Then retry the job.
name> caused by ongoing
replica creation.
97 Job failure on replica of <data Cancel the operation, or wait for it to complete. Then
source name> on <server retry the job.
consistency check.
98 Operation failed on replica of Cancel the operation, or wait for it to complete. Then
<data source name> on retry the job.
<server name> since a
recovery operation is currently
in progress.
source name> on <server retry the job.
stop-protection job.
source name> on <server retry the operation.
recovery point creation.
101 This job failed because the No action is needed. Wait for DPM to update its
replica for this data source is database to reflect that this data source is no longer
85
being deallocated, probably protected.
because the ‘Stop Protection
without retaining replica’ task
was run on this data source.
104 An unexpected error occurred Retry the operation.
during job execution.
107 The DPM protection agent is 1) Check recent records from the FSRecord source in
no longer tracking changes on the System Event Log on <protected server name> to
<protected server volume find out why the problem occurred.
name> on <protected server 2) Synchronize with consistency check.
name>.
109 The replica on the DPM server
for <data source type> <data
source name> on <server
name> is inconsistent with the
protected data source.
Changes cannot be applied.
238 <Server name> cannot be Restart <server name> and then try the recovery
used as a destination for operation again.
recovery because it has not
been restarted since the
protection agent was installed.
111 <Server name> has been
restarted without being
properly shut down.
131 File name extensions must
begin with a '.' and cannot
contain any of the following
characters: /, \, :, *, ?, ", <, >, |
132 Please remove duplicate file
name extensions.
135 Cannot protect this folder
because data on other mount
points of this volume have
been selected for protection.
112 Changes for <data source
<server name> cannot be
applied to <file name>.
113 Job failure for <data source Cancel the ongoing operation, or wait for it to complete.
type> <data source name> on Then retry the job.
<server name> caused by an
ongoing conflicting operation
on <server name>.
114 Job failure on <data source Cancel the operation, or wait for it to complete. Then
86
name> on <server name> retry the operation.
caused by ongoing backup
operation.
115 Job failure on <data source Cancel the operation, or wait for it to complete. Then
name> on <server name> retry the operation.
caused by ongoing recovery
from tape operation.
116 Job failure on <server name> Cancel the operations, or wait for them to complete.
caused by other ongoing Then retry the operation
conflicting operations on that
computer. Note that some
applications do not allow
parallel recovery and backup
operations on the same data
source.
117 The synchronization job failed Create a valid recovery point on the primary DPM
due to an internal error. server and rerun the synchronization job.
To create a valid recovery point on the primary DPM
server:
1) For SQL data, Exchange data or Windows
SharePoint Services data, in the Protection task area,
click 'Create recovery point', and select 'Express full
backup on disk'.
2) For other types of data, in the Protection task area,
click 'Create recovery point', and select 'Create a
recovery point after synchronizing.
118 The selected data cannot be Ensure that the replica is in "replica creation pending"
recovered to the DPM server state before recovering. For details on recovering a
<server name> because the DPM server, refer to the DPM 2010 Operations Guide.
replica is not in "replica
creation pending" state.
130 You cannot add more recovery To increase the recovery points per day, you must
points because the maximum either decrease the retention range or select fewer
number of recovery points for days of week.
the entire retention range is
<maximum limit> .
133 You cannot choose this Choose a recovery point that has a time difference with
recovery point because the a previous recovery point that is equal to or greater
time difference between it and than the specified synchronization frequency.
a previous recovery point is
less than your synchronization
frequency.
Specified synchronization
frequency: <value entered>
137 The protection group name Enter a different name.
entered already exists.
87
236 DPM will look for your
recovery tapes only in the
selected library. Ensure that
you load the tapes required for
recovery to this selected
library.
136 Unable to create protection Configure a tape library or add a disk to the storage
group because no disks or pool.
tape libraries available.
138 The target path <object name>
is located on the system
volume. If you use DPM to
protect data on this volume,
you cannot restore operating
system files or system state
from this protection group
member. To protect this
computer's system state,
select the system state as a
member of a protection group.
239 <Server name> is not
protected. You can filter the list
only by computers that have
been protected.
241 The volume <volume name>
on <server name> is not
currently protected.
140 The network bandwidth usage Enter a number between 1 and 10000.
throttling rate must be
between 1 and 10000 Mbps.
141 Cannot perform <input Wait for the ongoing job to complete or cancel the job
parameter tag> because the in the Monitoring task area.
replica is not idle.
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.
144 The backup frequency for Select a backup frequency that is equal to or greater
long-term protection needs to than <input parameter tag>.
be equal to or greater than the
backup frequency for short-
term protection.
88
Backup frequency for short-
term protection: <input
parameter tag>.
145 You cannot reduce the Before you can reduce the express full backup
express full backup schedule schedule of this protection group, you must modify the
because this would affect the protection group properties to specify a backup
long-term recovery goals of frequency that is equal to or greater than weekly.
this protection group.
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.
Please enter a valid name.
147 To view the protected
computers, you need to
enable protection of these
computers.
To enable protection, on the
Agent tab in the Management
task area, select the DPM
server, and then in the Details
pane, click Modify.
148 You have chosen to protect
replicas on another DPM
server (primary DPM server).
We recommend that you
protect the database (DPMDB)
of the primary DPM server
along with the replicas.
Without protecting DPMDB,
you will not be able to recover
the replicas of the primary
DPM server in case of a
disaster where the DPM
database and the replicas are
lost.
If the primary DPM server
database is protected, click
OK to continue to the next
step.
149 You have specified the change Free space on the volume on the protected computer
journal size on volume and retry the task
<volume name> for <server
name> to be set to <value
entered>. However, this is
greater than the available
89
space on the selected
computer.
150 You have selected replicas on
another DPM server (primary
DPM server) to protect.
File exclusions will not apply to
any data protected on a
primary DPM server. File
exclusion will apply to all other
protection group members.
152 DPM data source cannot be
added to the protection group
because of the existing
settings.
Create a new protected group
to add this data source.
156 The ability to add members to Either cancel the initial synchronization jobs for the
this protection group is members or wait until they complete.
temporarily disabled while
initial synchronization of one
or more members occurs.
157 <data source name> cannot
be added to protection
because it is already a
member of a protection group
158 <Value entered> is not a valid
value. The maximum is
<maximum size> <unit>.
159 <Value entered> is not a valid
value. Use only digits and,
optionally, a decimal point.
160 <Value entered> does not
meet the minimum allocation
value of <original calculated
value> <unit>.
164 <Volume name> on <server Please remove the volume from selection.
name> does not meet the
minimum size requirement of
1 GB.
168 The replicas for one or more of In the Protection task area, select protection group
the volumes being protected <protection group> and click Review Pending
are missing. This may be a Members. Follow instructions to allocate disk space for
result of one or more disks in protection.
the DPM storage pool being
offline or the deletion of
volumes created by DPM to
90
store the replicas. You cannot
modify disk allocation or
configure protection for any
members on these volumes
until the replicas have been
reallocated.
169 Although you chose to retain In the Protection task area, select the following member
the replica for this previously from <previously protected member's group name>:
protected volume, the replica <list of protected members>, and click “Delete replica”
is now missing from the DPM in the Details pane.
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.
171 There is insufficient space on Add more disks to the storage pool by using the Disks
the storage pool disks to tab in the Management task area, or reduce the
allocate the replica and specified allocations
recovery point volumes
172 The inputs are not valid for
custom scheme.
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
91
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 <data source
<server name>. 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
<volume label> to create the
replica since it is not
adequately sized. Volumes to
be used for the replica should
be greater than <minimum
size> GB
177 DPM failed to use the volume
<volume label> to create the
recovery point volume since it
is not adequately sized.
Volumes to be used for storing
the recovery points should be
greater than <minimum size>
GB
178 DPM failed to use volume
<volume label> since this has
already been selected to
protect <data source type>
<server name>
179 DPM cannot resize volumes Use the Disk Management Console to resize your
<volume label> and <volume volumes
label> which are being used to
protect <data source type>
<server name> since these
are custom volumes.
180 Failure to allocate disk space In the Protection task area, select protection group
to the storage pool for storing <protection group> and click Review Pending
the replica and the recovery Members. Follow instructions to allocate disk space for
points for <volume name> on protection.
92
<server name>. No protection
will be initiated for <volume
name> on <server name> until
disk space has been allocated
to the storage pool.
181 DPM could not create Refer to the allocation errors listed below and try to
<protection group> because of create the protection group again.
failed disk allocations.
182 Eseutil consistency check Copy the following files from the Exchange server
cannot be performed for this installation folder to "<folder path>" location on the
protection group, as DPM server:
eseutil.exe is not present on Ese.dll
the DPM server.
Eseutil.exe
Ensure that you do not copy the 64-bit version of
eseutil.exe to a 32-bit DPM server. The 32-bit version
of eseutil.exe can be obtained from the Exchange
Server product disk.
You can also choose not to run Eseutil consistency
check for this protection group, by deselecting the "Run
Eseutil Consistency check" option. However, this is not
recommended as it will not ensure the recoverability of
the protected Exchange data.
183 Select a single item for
creating a recovery point on
disk. You have currently
selected multiple items in the
list view.
184 Cannot create recovery point
for application data source
because protection is stopped.
185 There was a failure during Check the Alerts tab in the Monitoring task area to
recovery point consolidation. locate this alert and fix the issue. Please retry recovery
after that.
192 The requested operation could Run consistency check and retry the operation.
not be completed because the
replica was in an inconsistent
state.
195 Your changes cannot be Retry the operation.
applied because certain
protection group properties
have changed. The protection
group properties could have
changed due to either of the
following:
232 Only <maximum list items in
Browse view> of the items in
93
<object name> can be
displayed. Either select
<object name> for recovery or
use the Search tab to find
specific items to recover.
199 DPM was unable to protect the 1) Check your cluster configuration to ensure that
members in the resource shares and disks on which these shares reside are part
group <object name>. This of the same resource group
resource group contains some 2) Check your cluster configuration to ensure that the
resources that have application and the disks it requires are part of the
dependencies which not same resource group.
present as part of this group.
200 DPM could not perform the Retry the operation.
requested action on the
selected items.
This could be because the
selected item or property
associated with the items has
undergone changes which
prevent the action to be taken.
201 DPM failed to protect the SQL To be able to directly protect this Sql database you
database <data source name> could do either of the following:
since this was part of the 1) Rename the database and then protect it.
SharePoint Farm <referential
2) Stop protection of the SharePoint Farm and remove
data source name> which is
the replica associated with this farm. Then protect this
either under active protection
database.
or has an inactive replica
available.
202 DPM could not recover the Select another recovery point.
requested data.
The selected recovery point is
no longer available for
recovery.
203 Recovery failed because the 1. Choose a recovery point created after the move
data source files have been operation.
moved since this recovery 2. Choose a different recovery type.
point was created.
204 Maximum allowed frequency is
5 years
205 No tape labels have been
specified; you need to specify
tape labels for the
identification of tapes.
206 The specified retention range
is invalid.
Specify a value for retention
94
range which is equal to or less
than 4158 weeks or 1188
months or 99 years.
207 An unexpected error occurred Retry the operation.
during a VSS operation.
208 No recovery point was If synchronization has not occurred since the last
created, either because recovery point was created, you can synchronize the
synchronization has not replica with the protected data on the protected
occurred since the last computer and then create a recovery point. For more
recovery point was created, or information, see "How to synchronize a replica" and
because no changes were "How to create a recovery point" in DPM Help.
found during synchronization.
210 DPM was unable to create the 1) Make sure that the Volume Shadow Copy service is
recovery point due to a enabled on the DPM server. 2) Check recent records
general failure in the Volume from the VolSnap source in the Application Event Log
Shadow Copy service. to find out why the problem occurred. 3) Retry the
operation.
211 Cannot create a recovery point Wait for a few minutes and then retry the operation.
because another recovery
point creation is in progress.
212 Cannot delete recovery point Wait for all recovery jobs on the replica to complete and
because it is in use for then retry the operation.
recovery.
213 A recovery point was created Modify disk allocation to increase space allocation for
and immediately deleted the recovery point volume.
because of insufficient disk
space.
214 DPM does not have sufficient Increase the disk allocation space for the recovery
storage space available on the point volume, or delete old recovery points by using the
recovery point volume to Remove-RecoveryPoint cmdlet. For information about
create new recovery points. deleting recovery points, open DPM Management Shell
and run "Get-Help Remove-RecoveryPoint -detailed".
If you are using custom replica and recovery point
volumes, such as in the case of a SAN, you cannot
modify the disk space allocated by using DPM. In these
cases, identify the volume that corresponds to the
recovery point volume for the data source in question
from the "Modify Disk allocation" dialog box. Then,
open Disk Management, right-click the custom volume,
and then select "Extend Volume".
215 Cannot create a recovery point 1) Check recent records from the VolSnap source in the
because of a transient Application Event Log to find out why the problem
problem. occurred. 2) Retry the operation.
218 You must specify the e-mail
addresses of the recipients to
send notifications.
95
219 You must specify the SMTP On the Action menu, select Options. Select the SMTP
server settings before you can Server tab to configure settings.
subscribe to notifications.
227 DPM cannot access <file Make sure that the item is not locked by another
name> because the file or process.
folder has been exclusively
locked by another program.
229 DPM failed to access the path Verify that the path can be accessed successfully by
<file name>. using Windows Explorer.
220 DPM cannot enable e-mail
subscription for reports unless
SMTP details are configured in
the remote SQL Server
Reporting Service installation.
SMTP details need to be
configured manually when an
existing SQL Server 2008 is
chosen to be used for DPM
during DPM setup.
Enter the SMTP server name,
SMTP port number, and SMTP
“From” address manually in
the SQL Server Reporting
Service’s configuration file.
Configuration file path: <file
name>
Server: <computer name>
The SMTP Server details on
the SMTP Servers tab in the
Options dialog enables only
DPM alert notifications. For
more details, see DPM Help.
221 <Username> does not have Add the user to the Administrators group or specify
administrator privileges on the different administrator and try again.
DPM Server.
222 DPM cannot browse <server On the Agents tab in the Management task area, check
name> because access is the status of the agent. Also, verify that the system
denied. times on the DPM server and the protected computer
are synchronized with the system time on the domain
controller.
223 DPM cannot browse <server 1) Check recent records from the DPMRA source in the
name> because the agent is Application Event Log on <server name> to find out
not responding. why the agent failed to respond.
2) Make sure that the DPM server is remotely
96
protection agent.
224 DPM cannot browse <server 1) Make sure that <server name> is remotely
name> because of a accessible from the DPM server.
communication error with the 2) If a firewall is enabled on <server name>, make sure
agent. that it is not blocking requests from the DPM server.
protection agent.
name> either because no Management task area, on the Agents tab, click Install
agent is installed on <server in the Actions pane. If the computer is in the process of
name> or because the restarting, allow some time for the computer to come
computer is rebooting. online.
235 No library is available for From the Library tab in Management, click Rescan to
recovery to proceed. bring libraries online.
233 You have specified the same
library for both primary library
and copy library.
The library you select as the
primary library will read from
the source tape and the library
you select as the copy library
will copy the data to tape.
Specify two different libraries
or specify a multi-drive library
as a primary library.
234 You have selected a library
which does not contain the
online recovery tapes. The
library which contains online
recovery tapes is shown as
recommended.
If you do not select the
recommended library, ensure
that you transfer the recovery
tapes to the selected library
after you finish the recovery
wizard.
237 You have chosen to recover
the 'Latest' recovery time.
For Exchange mailbox
recovery, DPM supports only
the "Previous point in time"
97
recovery option.
For the selected mailbox, it is
<recovery point in time>.
247 <Input path> is not a valid
network path. You must
specify a path in the
\\server\share format. No
wildcards are allowed.
248 <Input path> is not a valid
local path. You must specify a
path such as d:\, d:\folder. No
wildcards are allowed.
249 <Input name> is not a valid file
or folder name. Make sure that
the file name is correct and
that the path is entered only in
the appropriate Original
location field.
419 DPM could not set security Review the error details, take appropriate action and
permissions on the replica or retry the operation.
recovery point volume that
was created.
420 DPM could not get security Review the error details, take appropriate action and
permissions on the replica or retry the operation.
recovery point volume.
450 An invalid path name was Specify the correct path of the .mdf or .bak file and try
specified for the DPM again.
database location.
451 An invalid path name was
specified for DPM Report
database location.
255 The selected recovery point no
longer exists.
265 DPM encountered an error Recover the data from another recovery point.
while reading from the
recovery point used for
recovery. Either the recovery
point no longer exists or, if you
selected a share for recovery,
the path to its contents is
missing from the recovery
point.
346 DPM is unable to retrieve the Ensure that the Windows Management Information
configuration information from (WMI) service <service name> is started and is
<server name>. accessible from the DPM server.
98
349 An error occurred when the Review the error details, take the appropriate action,
agent operation attempted to and then retry the agent operation.
transfer agent installation files
to <server name>.
355 Disk <NT disk number> cannot
be removed from the storage
pool because it contains
storage pool volumes.
267 The following computers do Verify that Windows Server 2003 Service Pack 1 is
not meet the minimum installed on the selected computers. If the operating
software requirements for system has been recently updated, Active Directory
installing the DPM protection updates may still be pending. Wait until the Active
agent: <list of servers>. Directory updates are complete, and then try to install
the protection agent again. The time needed for Active
Directory updates depends on your Active Directory
domain replication policy.
For more information about software requirements, see
the DPM 2010 System Requirements.
272 Work hours are not valid.
Specify valid work hours.
273 An Alias or Display name Specify valid names to search.
cannot be empty value or
characters <input name>.
274 Unable to configure security Make sure that the password you have provided has
settings for <server name> on administrator privileges on the target computer.
the computer <computer
name>.
275 Unable to remove <server Make sure that the password you have provided has
name> from the security group administrator privileges on the target computer.
on <computer name>.
270 The agent operation failed on Check the following to troubleshoot this issue:
<server name> because DPM 1) If the agent is no longer installed on the computer,
could not communicate with remove the protected data sources on this computer
the DPM protection agent. The from active protection. Then, remove the entry of this
computer may be protected by computer from the Agents tab in the Management task
another DPM server, or the area.
protection agent may have
2) If the agent is not installed on <server name>, run
been uninstalled on the
DpmAgentInstaller.exe with this DPM computer as a
protected computer.
parameter. For more information, see the DPM
Deployment Guide.
3) To attach the computer correctly to this DPM server,
run the SetDpmServer tool on the computer. For more
information, see Installing Protection Agents Manually
(http://go.microsoft.com/fwlink/?LinkId=100443). If the
computer is protected by another DPM server, or if the
99
protection agent has been uninstalled, you can remove
the record of the computer from this DPM server.
4) You can uninstall the DPM agent using Add or
Remove Programs on the selected computer. Then
remove the record of the computer on the Agent tab in
the Management task area of DPM Administrator
Console.
271 The user <username> does Remove the computers from the "Select Computers"
not have administrator access page or provide credentials for an account that has
to the following items: <server administrator access to all of the selected computers.
name>
276 A site, document, list or list- Please enter a valid value to search.
item cannot be empty or
characters <input name>.
277 Could not connect to the 1) Make sure that <server name> is online and
Service Control Manager on remotely accessible from the DPM server.
<server name>. 2) If a firewall is enabled on <server name>, make sure
278 Unable to connect to the Make sure that
Active Directory Domain 1) Server is a member of a domain and that a domain
Services database. controller is running.
2) There is network connectivity between the server
and the domain controller.
3) "File and Printer sharing for Microsoft Networks"
property is enabled in Local Area Connection.
291 The protection agent Verify that the credentials you provided have
installation failed. The administrator privileges on <server name> and then try
credentials you provided do to reinstall the protection agent again.
not have administrator
privileges on <server name>.
292 You cannot uninstall protection Remove all of the members that are associated with
agents from the protected the following computers from protection groups before
computers until you remove all uninstalling the protection agents: <list of servers>
protected members on the
associated computers from
protection groups.
294 The protection agent You must restart the protected computer <server
installation or upgrade name> before it can be protected.
succeeded. However, DPM
could not remove the
bootstrap service.
298 Recovery failed for <data Recover to an alternate location or try recovering from
source type> <data source another recovery point.
name> on <server name>.
100
333 A protection agent is already
installed on <server name>.
334 You cannot install the
protection agent on <server
name> because it is the DPM
server.
350 Disk <NT disk number> is Select a different disk to add to the storage pool.
already in the storage pool.
293 The protection agent operation Do the following to troubleshoot this issue:
failed. The credentials you 1) Verify that the credentials you entered belong to a
provided do not belong to a valid domain user account, and then retry the
valid domain user account. operation.
2 ) Verify that the domain controller is available and
functioning properly.
295 DPM could not remove the Use Add or Remove Programs in Control Panel to
Protection Agent Coordinator uninstall the DPM Agent Coordinator service on
service from <server name>. <server name>.
296 The protection agent is 1) Update the protection agent to a version compatible
incompatible with the version with the DPM server. From the DPM Administrator
of DPM that is installed on this Console, open the Agents tab in the Management task
computer. All subsequent area. Select the computer on which the protection
protection and recovery tasks agent is installed. Click Update from the Actions pane.
will fail on this computer until 2) If a firewall is enabled on the computer, run
you update the protection DPMAgentInstaller [DPM Server Name] on protected
agent. computer. From DPM Management Shell, run the
AttachProductServer.ps1 commandlet on DPM server
to update the DPM configuration.
297 The protection agent is Uninstall the protection agent from this computer and
incompatible with the version then reinstall the protection agent.
of DPM that is installed on this
computer. All subsequent
protection and recovery tasks
will fail on this computer until
you reinstall the correct
version of the protection
agent.
299 For <data source type> <data Make sure that the file is not already present and in use
source name> on <server on the destination computers and that there is sufficient
name>, the following items disk space for the files.
could not be recovered:
<temporary list of files>.
300 The protection agent operation Do the following to troubleshoot this issue:
failed because it could not 1) Verify that <server name> is online and remotely
communicate with <server accessible from the DPM server.
name>.
101
3) Verify that Internet Protocol Security (IPsec) is
configured on both the DPM server and the protected
computer. If IPsec is only configured for one computer,
turn off IPsec.
301 The protection agent upgrade To upgrade the protection agent:
failed because the protection 1) In DPM Administrator Console, in the Management
agent is not installed on task area, on the Agents tab, select the computer on
<server name>. 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 <server name>.
302 The protection agent operation Uninstall DPM or the DPM protection agent from
failed because it could not <server name> and install the DPM protection agent
access the protection agent on again from the computer that you want to use to protect
<server name>. <Server the computer.
name> may be running DPM,
or the DPM protection agent
may have been installed by
another DPM server.
303 The protection agent operation Review the error details, take the appropriate action,
failed on <server name>. and then retry the agent operation.
304 The protection agent operation Wait for the protection agent operation on <server
failed because another agent name> to finish, and then try reinstalling the protection
operation was running on agent again.
<server name>.
305 The agent operation failed Verify that the operating system is Windows
because the operating system Server 2003 Service Pack 1 (SP1) or later on the
on <server name> is not selected computers. If the operating system has been
supported. 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.
335 The protection agent
installation on Windows 2003
Servers causes the computer
to briefly lose network
connectivity.
336 The protection agent uninstall Wait a few moments and then try uninstalling the
is unavailable because the protection agent again.
DPM server is currently
102
communicating with the
protection agent on the
following protected computers:
<list of servers>.
306 The protection agent Use Add or Remove Programs in Control Panel to
installation failed because uninstall the protection agent from <server name>, and
another version of the then try reinstalling the protection agent.
protection agent is already
installed on <server name>.
307 The protection agent operation Use Add or Remove Programs in Control Panel to
failed because DPM detected uninstall the protection agent from <server name>, then
an unknown DPM protection reinstall the protection agent and perform the operation
agent on <server name>. again.
308 The protection agent operation If you recently installed a protection agent on <server
failed because DPM could not name>, the computer may be restarting. Wait a few
communicate with the minutes after restarting the computer for the protection
Protection Agent service on agent to become available. If the problem persists, do
<server name>. the following:
1) Verify that <server name> is remotely accessible
from the DPM server.
<server name>. If the service fails to start, uninstall the
protection agent by using Add or Remove Programs in
Control Panel on <server name>. Then in the
Management task area, on the Agents tab, in the
Actions pane, click Install to reinstall the protection
agent on <server name>.
309 The agent operation failed Verify that the system root is shared as ADMIN$ on
because the ADMIN$ share on <server name>.
<server name> does not exist.
310 The agent operation failed Verify that you have ADMIN$ share permissions on
because it could not access <server name>, and that the system time on the DPM
the ADMIN$ share on <server server and <server name> is synchronized with the
name>. system time on the domain controller.
311 Due to changes to <server In DPM Administrator Console, uninstall the DPM
name>, the DPM protection protection agent. In the Management task area, on the
agent is no longer properly Agents tab, select the protection agent, and then in the
installed. Actions pane click Uninstall.
312 The agent operation failed Restart the DPM Agent Coordinator service on <server
because the DPM Agent name>.
Coordinator service is not
responding.
313 The agent operation failed Review the log files on <server name>:
because an error occurred [windir]\temp\msdpm*.log and take appropriate action.
103
while running the installation Retry the operation, and if the error persists, restart the
program on <server name>. computer and then retry the operation again.
314 The agent operation failed Wait for the installation to complete and then retry the
because an installation is agent operation.
already in progress on <server
name>.
315 The agent operation failed
because server <server
name> is part of a cluster.
DPM does not support
protection of clustered servers.
316 The protection agent operation If you recently installed a protection agent on <server
on <server name> failed name>, the computer may be restarting. Wait a few
because the service did not minutes after restarting the computer for the protection
respond. agent to become available. Otherwise, troubleshoot the
problem as follows:
1) Check the recent records from the DPMRA source in
the Application Event Log on <server name> to find out
why the agent failed to respond.
2) Verify that the DPM server is remotely accessible
from <server name>.
3) If a firewall is enabled on the DPM server, verify that
it is not blocking requests from <server name>.
<server name>. If the service fails to start, reinstall the
DPM protection agent.
317 The protection agent Reinstall the missing files by running DPM Setup and
installation failed because the DPM updates.
files needed to install the
protection agent (version
<agent version>) are missing
from the <server name> DPM
server.
318 The agent operation failed Verify that both <server name> and the domain
because DPM was unable to controller are responding. Then in Microsoft
identify the computer account Management Console (MMC), open the Group Policy
for <server name>. 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 1) Verify that <server name> is remotely accessible
because of a communication from the DPM server.
error with the DPM Agent 2) If a firewall is enabled on <server name>, make sure
Coordinator service on <server that it is not blocking requests from the DPM server.
name>. Refer to the DPM 2010 Deployment Guide for more
information on configuring the firewall for DPM.
104
320 The agent upgrade failed In DPM Administrator Console, in the Management task
because the protection agent area, on the Agents tab, click Uninstall to remove the
is not installed on <server agent record from DPM. Then click Install to reinstall
name>. the agent on <server name>.
322 The following computers <list Do the following to troubleshoot this issue:
of servers> were not found in 1) Check the spelling of the computer name.
Active Directory Domain
2) Verify that Windows Server 2003 with Service
Services, or they do not have
Pack 1 or later is installed on the computer.
a Windows Server operating
system installed. 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.
324 The agent operation failed Do the following to troubleshoot this issue:
because the DPM Agent 1) Check the recent DPMAC source records in the
Coordinator service on <server application event log on <server name>.
name> did not respond.
2) Verify that the DPM server is remotely accessible
from <server name>.
3) If a firewall is enabled on the DPM server, verify that
it is not blocking requests from <server name>.
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.
325 The agent operation failed Restart the selected computers.
because the protection agent
is not active until you restart
the selected computers.
326 The protection agent operation Check the following:
failed because access was 1) If <server name> is protected by another DPM
denied to the <server name> server, you cannot install the protection agent on it.
DPM server.
2) If the DPM Agent Coordinator service is installed on
<server name>, use Add or Remove Programs in
Control Panel on <server name> to uninstall it.
3) If another protection agent management job is
running on <server name>, wait for it to complete, and
then retry the operation.
328 The agent operation failed Start the Remote Registry service on <server name>.
because the Remote Registry On the Administrative Tools menu, select Services. In
service is not running on the right pane, right-click Remote Registry, and then
105
<server name>. click Start. Note: You can disable the Remote Registry
service after the agent operation is complete.
338 You can only select Select less than <maximum installation servers>
<maximum installation computers to add to the Selected Computers list.
servers> computers to install
at a time.
343 The agent operation failed
because <server name> is not
a 32-bit computer or a 64-bit
computer.
329 The agent operation failed Install <name> version <version number> or later, or
because an incompatible uninstall <name> from the computer. If <name> was
version of <name> is installed installed by your original equipment manufacturer
on <server name>. (OEM), please contact your OEM support for
instructions.
330 The agent operation failed Start the Windows Installer service on <server name>.
because the Windows Installer On the Administrative Tools menu, select Services. In
service on <server name> is the right pane, right-click Windows Installer, and then
disabled. click Start. Note: You can disable the Windows Installer
service after the agent operation has completed.
337 You cannot install the Do the following to troubleshoot this issue:
protection agent on <server 1) If another DPM server is currently protecting <server
name> because access to the name> use that DPM server to uninstall the protection
computer has been denied. agent from <server name>. Then, use this DPM server
to install the protection agent on <server name>.
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.
340 The protection agent upgrade Uninstall the existing DPM protection agent from
failed because <server name> <server name> using Add or Remove Programs in
has a more recent version of Control Panel. Then in DPM Administrator Console,
the protection agent (version reinstall the DPM protection agent version that you
<agent version>) installed. want. In the Management task area, on the Agents tab,
click Install in the Actions pane.
341 The agent operation failed Retry the agent operation and provide credentials that
because the credentials you have administrator user rights on <server name>.
provided do not have sufficient
user rights on <server name>.
342 The agent operation failed 1) Verify that <server name> is online and remotely
106
because the DPM server could accessible from the DPM server.
not communicate with <server 2) If a firewall is enabled on <server name>, verify that
name>. it is not blocking requests from the DPM server.
3) Verify that the Remote Registry service on <server
name> 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.
344 DPM could not find the correct 1) Make sure that the correct version of the agent is
version of the DPM protection installed on the selected computer.
agent on the selected 2)If the protection agent has been recently upgraded, in
computer. DPM Management Shell, run Attach-
ProductionServer.ps1 [computer name] and refresh the
agent status again.
345 The agent operation failed Restart the DPM Agent Coordinator service on <server
because of a communication name>, and then try to reinstall the protection agent.
error with the DPM Agent
Coordinator service on <server
name>.
create the DPM Agent
Coordinator service on <server
name>.
communicate with the DPM
Agent Coordinator service on
<server name>.
351 Disk <NT disk number> cannot Make sure that the disks being added to the storage
be added to the storage pool. pool do not contain any of the following: system
volume, boot volume, OEM or other special volumes,
DPM software, or SQL Server databases.
452 The DPM service failed to Check the application and system event logs for
stop. information on the error.
453 The DPM service failed to Check the application and system event logs for
start. information on the error.
454 DpmSync failed to connect to Make sure that you have specified a valid SQL server
the specified SQL Server instance associated with DPM and you are logged on
instance. as a user with administrator privileges.
455 Failed to attach database Make sure that the SQL server services are running
[<database name>] at location and you are restoring a valid DPM database backup.
[<database location>] to SQL
107
server.
352 Disk <NT disk number> cannot Check Disk Management to see whether the disk is
be added to the storage pool online. If the disk is offline, check the hardware
because the disk either failed configuration and rescan.
or is missing.
354 Disk <NT disk number> is not In the Management task area, select the Disks tab and
listed in the storage pool. click Rescan to refresh all disks that are owned by
DPM.
356 The folder on which the Clear all unmounted directories from <DLS volume
replicas must be mounted root> directory and then retry the operation.
already exists.
467 The specified action can be Run the tool on the DPM server to complete these
performed only on a computer steps.
with DPM installed.
469 Unable to detach the Check that you have permission to detach the DPM
database. database.
358 The allocation of disk space Add more disks to the storage pool or reduce the
for replica volumes failed replica volume size requirement.
because there is not enough
unallocated disk space in the
storage pool.
360 The operation failed due to a Retry the operation.
virtual disk service error
361 Disk <NT disk number> was For more information about supported disk types, see
not added to the storage pool the DPM 2010 Deployment Guide.
because it could not be
converted to a dynamic disk.
362 The replica cannot be Reallocate the replicas before trying to increase them.
increased because the replica
volume is missing.
365 DPM is currently shutting After DPM shuts down, restart DPM and then retry this
down and cannot complete the operation
requested operation
366 The computer running DPM In the Management task area, select the Disks tab and
has deleted volume [<volume review all disks that are owned by DPM.
GUID>, <volume label>] from
DPM disk <NT disk number>
because it was not a DPM
volume.
367 DpmSync has completed with On the DPM server, use Event Viewer to view details
the following errors: <DPM for this event. The details are available in the
synchronization summary>. application event log.
368 DPM has deleted DPM volume
[<volume GUID>, <volume
108
label>] because the size of the
volume was modified
externally using system tools.
Do not change the size of
volumes on DPM-owned disks
using system tools.
369 A protection agent is not Install the protection agent on each node of the server
installed on <node> in cluster.
<cluster> server cluster.
Protection may fail if a failover
occurs to <node>.
370 Agent operation failed.
372 The agent operation failed Install the updated version <agent version> of the
because DPM detected a protection agent on the DPM server.
more recent version of the
DPM protection agent (version
<agent version>) on <server
name>.
400 The DPM server was unable Verify the following:
to retrieve information about 1) <Server name> is online and remotely accessible
the remote system using the from the DPM server.
Windows Management
2) A firewall if enabled on <server name> is not
Instrumentation (WMI) service
blocking WMI requests from the DPM server.
on <server name>.
3) The WMI service on <server name> is running.
401 The agent installation failed Verify the following:
while trying to install the Agent 1) The share \\<server name>\ADMIN$ is accessible
Coordinator service.
2) Remote calls from the DPM server to the Service
Control Manager (SCM) on <server name> are not
blocked by a firewall.
403 Access was denied when Verify that you have permissions to create the lock file
trying to create the lock file in \\<server name>\Admin$.
in \\<server name>\Admin$.
402 When trying to retrieve Verify that you have access to the WMI service on
information from the Windows <server name>.
Management Instrumentation
(WMI) service on <server
name>, access was denied.
404 The agent operation failed Verify the following:
when trying to install the Agent 1) The share \\<server name>\ADMIN$ is accessible
Coordinator service.
2) The remote calls from the DPM server to the Service
Control Manager (SCM) on <server name> are not
being blocked by a firewall.
405 DPM could not identify if Agent installation on <server name> can continue. To
computer <server name> is successfully protect clustered resources, you must
109
clustered. install the DPM protection agent on all the members of
the cluster. Review the error details and ensure that the
Windows Management Instrumentation service is
running and can be accessed remotely from the DPM
server.
406 DPM detected that server Agent installation on <chosen server name> can
<chosen server name> is continue. To successfully protect clustered resources,
clustered, but could not you must install the DPM protection agent on all the
identify the fully qualified members of the cluster. Ensure that the cluster state is
domain name of <server correctly configured and verify that all members are
name>. joined to the domain.
456 There were some failures in For details, please refer to application event log.
the synchronization operation.
457 Invalid command line For help about DpmSync, at the command prompt, type
arguments were specified. DpmSync -?.
458 The DPM database on the
DPM server <server name>
has been restored from a
backup. As a result, the alerts
that were generated before
<database restore time> do
not reflect the current state of
alerts on the DPM server.
To synchronize the MOM view
with the current state on the
DPM server:
1) In the MOM Operator
console, resolve all alerts for
the <server name> DPM
server, and the computers that
it protects: In Alerts view,
display all alerts for Microsoft
System Center Data
Protection Manager (DPM),
sort the alerts by the Source
column, and select the alerts
for <server name>.
To remove the selected alerts,
right-click, click Set Alert
Resolution State, and click
Resolved.
2) On the DPM server, re-
publish DPM alerts: In DPM
Administrator Console, select
Options on the Action menu,
click the Alert Publishing tab,
and click Publish Active Alerts.
This publishes all existing
110
alerts that may require a user
action to MOM.
460 Invalid combination of Run DpmSync -? to review the syntax of the tool.
arguments specified.
461 Instance name specified could Specify the correct name for the instance of SQL
not be found Server.
462 Error: Unable to retrieve DPM Specify the correct path and try again.
database file path
464 Path not found: '<file name>'. Ensure that the database backup exists at the specified
path.
465 Unable to close all Review the error details and try again.
connections for detaching the
database.
466 Unable to copy database files Review the error details and try again.
to <file name>.
470 DPM database is not present Check that the DPM database is present in the given
in the instance of SQL Server. instance of SQL Server.
471 Unable to attach the database. Ensure that the DPM database backup is valid.
517 The message cannot be sent Check the SMTP server settings.
to the SMTP server.
518 An authentication error You typed an incorrect , password, or SMTP server
occurred when trying to name. Type the correct password to enable e-mail
connect to the SMTP server. delivery of reports and alert notifications.
519 The SMTP server has rejected Confirm the recipient addresses.
one or more of the recipient
addresses.
520 The SMTP Server port number Enter a valid port number.
must be in the range between
1 and 65535.
522 Cannot connect to SMTP Verify SMTP server name and port number.
server.
523 The passwords entered do not Reenter the passwords.
match.
527 The SMTP server reports that Check for appropriate permissions to send via SMTP to
the From address is not valid. the specified server.
528 An e-mail message has been
successfully sent to
<recipient>.
529 An e-mail message has been
successfully sent to the
specified recipients.
111
530 A blank password is not Enter a password.
allowed.
531 The DPM alerts have been
published to the DPM Alerts
event log.
532 Changes to end-user recovery
settings do not fully take effect
for each protection group until
the next successful
synchronization is complete.
800 DPM must be installed on a Install DPM on a computer running Windows
computer running Windows Server 2003 Service Pack 1 (SP1). The Windows
Server 2003 Service Pack 1 Server 2003 SP1 redistributable package is available at
(SP1). http://go.microsoft.com/fwlink/?linkid=45556.
801 To install DPM, you must be Log on to the computer as an administrator or member
logged on as an administrator of the local administrators group, and then run Setup
or a member of the local again.
administrators group.
802 The computer processor Upgrade the computer hardware to meet the DPM
speed does not meet the DPM minimum configuration requirements; or install DPM on
minimum configuration a different computer. For information about DPM
requirements. The minimum system requirements, see the DPM 2010 System
required processor speed is Requirements.
<clock speed>.
803 The available memory on the Upgrade the computer hardware to meet the DPM
computer is less than the DPM minimum configuration requirements;, or install DPM on
minimum memory a different computer. For information about DPM
requirement. The minimum system requirements, see the DPM 2010 System
memory requirement is Requirements.
<minimum memory required>
MB, and the recommended
memory requirement is 2 GB.
805 There is not enough disk Free additional disk space on this disk, or choose a
space for <installation item>. different location.
809 DPM cannot load the file <file Run DPM Setup from the DPM product DVD. If you
name>. The file may be already ran Setup from the DVD, then the DVD is
missing or corrupt. 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 Use Add or Remove Programs in Control Panel to
created. 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
112
properly and that it is running.
813 The DPM uninstall failed. Review the error details, take appropriate action, and
then try uninstalling DPM again.
814 The configuration data for this Troubleshoot your Windows Installer installation.
product is corrupt. Contact your support personnel for further help.
817 The Setup log file path <file Verify that the Application Data folder path has fewer
name> is too long after being than 260 characters, and then run DPM Setup again.
fully qualified.
818 The Setup log file path <file Specify a valid Application Data folder path.
name> is not valid.
820 Setup cannot query the Verify that the Windows Management Instrumentation
system configuration. (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.
822 DPM Setup could not access Verify that the Windows Management Instrumentation
the SQL Server Reporting (WMI) service is running. If the WMI service is not
Services configuration. 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 Verify that the registry key <registry key> exists, and
registry key <registry key>. then run DPM Setup again.
828 DPM cannot connect to the To troubleshoot this issue, review the recent errors in
Service Control Manager the Windows Event Log.
(SCM).
829 DPM cannot open the handle To troubleshoot this issue, review the recent errors in
to the <Setup service name> the Windows Event Log.
service.
830 DPM cannot read the service Review the recent errors in the Windows Event Log on
<service name> configuration. <server name>.
832 Setup cannot grant the <> Verify that SQL Server is properly installed and that it is
account access to the DPM running.
database.
834 Setup cannot remove the To delete the reports manually, go to http://<computer
deployed reports. name>/<ReportServer$ instance name>.
833 Setup could not delete the To delete the <username> user account, on the
<username> user account. Administrative Tools menu, click Computer
Management. Expand Local Users and Groups, and
then select Users. Right-click <username>, and then
click Delete.
836 The DPM repair failed. Verify that the DPM server meets the software
requirements. Uninstall DPM, and then run DPM Setup
again.
113
841 Setup cannot calculate the Specify a different installation location.
disk space for the specified
location.
842 Setup cannot access the Verify that SQL Server 2008 is properly installed.
<registry key> registry key for
the <SQL Server instance
name> instance of SQL
Server.
869 The <directory path> directory Install the prerequisite software and DPM on a volume
is not on an NTFS volume. formatted with NTFS.
843 The physical location of the Verify that the instance of SQL Server is properly
existing DPM database cannot installed, and that the <service name> SQL Server
be found. service is running.
845 DPM Setup could not delete To delete the DPMDB database, in SQL Server
the DPMDB database. Manager Studio, connect to server <DPM server
name>\<instance name>. Expand the <instance name>
instance of SQL Server, expand Databases, right-click
the DPMDB database, and then click Delete.
846 DPM cannot locate Verify that the SQL Client Tools are installed. If they are
SqlCmd.exe. not installed, you must install the SQL Client Tools, and
then run DPM Setup again.
847 DPM cannot create the <Setup Restart the computer, then uninstall DPM, and then run
service name> service. Failure Setup again.
to create the service may be
due to a pending restart.
848 Setup is unable to copy the Verify that Setup has access to the installation location.
files from <source location> to
<installation location>.
849 Setup is unable to delete the Delete the folder manually.
folder <installation location>.
850 Setup is unable to mark files at After DPM setup is complete, delete the files manually.
<folder path> for deletion.
851 Cannot start Setup. Run the Setup program from the DPM product DVD. If
you already ran Setup from the DVD, then the DVD is
corrupt.
853 Setup is unable to register
DPM in Add or Remove
Programs.
854 Another instance of DPM Verify that only one instance of DPM Setup is running,
Setup is running. and then proceed with DPM Setup.
855 Setup was unable to delete Open SQL Server Management Studio, and connect to
the scheduled jobs. the DPM instance of SQL Server. Expand the instance
of SQL Server, browse to SQL Server Agent, and then
in Jobs, delete the <schedule category> category.
114
856 DPM could not access the Verify that the SQL Server service is running. If the
existing DPM database, or the SQL Server service is running, restore the DPM
DPM database is corrupt. database, and then run DPM Setup again.
857 DPM cannot enumerate the Protection agents may be installed on some of the
list of computers on which computers. Uninstall the agents on the protected
protection agents are installed computers using Add or Remove Programs in Control
because it cannot gain access Panel.
to the DPM database.
858 The DPM product key is Enter a valid DPM product key. The product key is
invalid. located on the back cover of the Data Protection
Manager product DVD.
884 DPM Setup cannot delete Manually delete the folder <folder path> after
folder <folder path>. completing DPM Setup.
885 DPM Setup cannot create the Verify that the current user has permissions to create
<file name> file. the file.
886 This program is for internal To launch the DPM Setup program, double-click
DPM use only. Setup.exe in the root folder of the product DVD.
859 Setup cannot parse the SQL Verify that SQL Server is properly installed.
Server 2008 Reporting
Services configuration file
(<file name>) for the SMTP
server address and the
address of the sender.
860 DPM cannot stop service Review the error details, take the appropriate action,
<Setup service name>. and then try installing DPM again.
861 DPM cannot read the Manually delete the folders after completing DPM
installation path registry key. Setup.
Some of the folders will not be
deleted.
862 Setup cannot start the <Setup Review the error details, take the appropriate action,
service name> service. and then try installing DPM again.
863 You cannot use the selected Select a different location on which to install DPM.
location <directory path> 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 <folder path>.
864 You cannot install DPM on Select a location on a local hard drive to install DPM.
removable media or a network
share. The location <media
location type> <media location
115
information> cannot be used
as an installation location.
868 DPM cannot query the volume Select another installation location on a local hard drive
information for directory to install DPM.
<directory path>.
865 Setup could not enumerate the On the Administrative Tools menu, select Computer
information about volumes Management, and then open Disk Management. Delete
allocated to DPM. the volumes allocated to DPM from the disks that were
added to the storage pool.
866 The Windows account that On the Administrative Tools menu, click Computer
was created in DPM Management. Expand Users and Groups, click Users,
Administrator Console in the right-click the Windows account, and then click Delete.
Recovery task area could not
be removed.
870 DPM cannot query the Select another installation location on a local hard drive
attributes of directory to install DPM.
<directory path>.
871 DPM Setup has detected an To install the earlier version of DPM, you must first
existing installation of DPM on uninstall the existing version.
this computer. The existing
installation is a later version
than the version you are trying
to install.
876 DPM Setup cannot create the If the folder already exists, delete the folder, and then
folder <folder path>. run DPM Setup again.
877 DPM Setup cannot write to file If the file already exists, delete the file, and then run
<file name>. Setup again.
879 DPM Setup could not delete To delete the service manually, at the command
service <Setup service prompt, type "sc delete <Setup service name>".
name>.
880 The DPM protection agent Review the error details, take the appropriate action,
configuration failed. and then try installing DPM again.
881 The required local group could Try installing DPM again.
not be created.
883 DPM Setup cannot read the Verify that the current user has permissions to read the
<file name> file. file.
878 Setup cannot create the Open SQL Server Management Studio, and then
protection job schedules. 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 <schedule
category> category.
882 DPM Setup could not create a If the DPM protection agent is installed on this
required service. This computer, use Add or Remove Programs in Control
computer may be protected by Panel to uninstall it, and then run DPM Setup again.
116
another computer running
DPM. You cannot install DPM
on a computer on which a
protection agent is installed.
887 An error occurred while trying Uninstall DPM by using Add or Remove Programs in
to configure DPM. Control Panel, and then run DPM Setup again.
1106 DPM: Resolved critical alert:
<server name>.
1107 The following alert became
inactive at <resolved time>.
1108 The following alert occurred at
<occurred since>.
1109 For more information, open
DPM Administrator Console
and review the alert details in
the Monitoring task area.
888 DPM Setup could not create To start using DPM, on the Start Menu, point to All
the DPM shortcut on your Programs, and then click Microsoft System Center Data
desktop. Protection Manager 2007.
889 The database files from a Delete the existing files at <location>, or select an
previous DPM installation alternative location for your database.
were found at <location>.
890 DPM does not support
upgrading from the version of
DPM that is currently installed.
892 The computer <computer In Internet Explorer, on the Tools menu, click Internet
name> could not be removed Options. In the Internet Options dialog box, on the
from the intranet security zone Security tab, click Local intranet, click Sites, then click
settings in Internet Explorer. Advanced, and then remove computer <computer
name> from the intranet zone.
893 Setup cannot delete the On the Administrative Tools menu, select Computer
volumes that are allocated to Management, and then open Disk Management. Delete
DPM. the volumes allocated to DPM from the disks that were
added to the storage pool.
894 DPM Setup could not delete Manually delete the DPM shortcut from your desktop.
the DPM shortcut on your
desktop.
895 The service <Setup service Restart the computer to delete the service <Setup
name> was not deleted from service name>.
the computer.
896 DPM could not connect to Verify that the SQL Server service <service name> is
database <database name>. started, and that you have permissions to query the
SQL Server.
117
897 DPM could not delete In SQL Server Management Studio, delete the
database <database name>. following databases: <database name>, <temporary
database name>.
898 DPM Setup cannot query the Verify that the Windows Management Instrumentation
SQL Server Reporting (WMI) service is running, and that your SQL Server
Services configuration. Reporting Services installation is not corrupt.
899 DPM Setup could not delete Manually delete the MSDPMTrustedMachines group.
the MSDPMTrustedMachines On the Administrative Tools menu, click Computer
local group. Management. Expand Local Users and Groups, and
then click Groups. Right-click
MSDPMTrustedMachines, and then click Delete.
900 DPM Setup could not delete
all the registry keys that DPM
uses.
901 DPM Setup could not delete Manually delete the DPM Agent Coordinator service.
the DPM Agent Coordinator On the Administrative Tools menu, click Services.
service. Right-click DPM Agent Coordinator, and then click
Delete.
904 The protection agent on Update the protection agent on <server name>.
<server name> is not
compatible with the DPM
version. The protection agent
version is <agent version>,
and the DPM version is
<computer version>.
905 The protection agent on Verify that all required DPM updates are applied to this
<server name> is not computer.
compatible with the DPM
version. The protection agent
version is <agent version>,
and the DPM version is
<computer version>.
907 The job encountered an Retry the operation.
internal database error.
914 The job failed because of an Make sure that the DPMRA service is running on the
unexpected error selected computer.
915 The operation failed because Check to see that the protected data source is installed
the data source VSS properly and the VSS writer service is running.
component <file name> is
missing.
921 The operation failed because Configure the mirrored database using a Fully Qualified
an error occurred while Domain Name (FQDN) instead of an IP address. DPM
enumerating the data source cannot back up mirrored databases that are configured
for the with IP addresses.
SqlServerWriter\<database
name> on which mirroring was
118
enabled using Internet
Protocol Version 4 (IPv4) or
Internet Protocol Version 6
(IPv6).
920 DPM has failed to write events Uninstall DPM and then reinstall DPM to recreate the
to the DPM Alerts event log. DPM Alerts event log.
Either the DPM Alerts event
log has been deleted or the
permissions have been
changed.
908 The job was canceled. The Retry the operation.
user either canceled the job or
modified the associated
protection group.
909 DPM has received an Retry the operation. If the problem persists, contact
improperly formed message Microsoft Customer Service and Support.
and was unable to interpret it.
910 The DPM service terminated Retry the operation.
unexpectedly during
completion of the job. The
termination may have been
caused by a system reboot.
911 DPM was not able to complete In the Monitoring task area, group jobs by type and
this job within the allotted time. 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 Retry the operation.
because of the failure of
another job on which it
depended.
913 The job was canceled Retry the operation.
because it was scheduled
during the inactivity timeframe.
916 Cannot connect to the DPM Please wait for DpmSync to complete its operation. If
service because it is running in DpmSync is not running and the DPM service is still in
recovery mode, which was recovery mode, then run DpmSync again.
initiated by the DpmSync tool.
918 Connection to the DPM Make sure that the DPM service is running. Review the
service has been lost. application event log for information about a possible
service shutdown.
917 Connection to the DPM DPM service could be running in recovery mode, which
service has been lost. was initiated by the DpmSync tool. If DpmSync is not
running and the DPM service is still in recovery mode,
then run DpmSync again.
939 The DPM Administrator Ensure that the version is between <minimum UI
119
Console version <version version> and <maximum UI version>.
number> is incompatible with
the DPM server version.
940 Unable to connect to the Review the event log and take appropriate action.
database because of a fatal Make sure that SQL Server is running.
database error. It is unlikely
that the database itself has
been damaged.
941 Unable to connect to the DPM Make sure that SQL Server is running and that it is
database. configured correctly.
942 The integrity of the database Contact an experienced SQL Server administrator
integrity is questionable whenever this error occurs. Look at Windows Event
because of a hardware or Log for troubleshooting. Run DBCC CHECKDB to
software problem. 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 Contact an experienced SQL Server administrator
database because the whenever this error occurs. In some cases, it may be
database is in an inconsistent necessary to restore the DPM database. If the problem
state. persists, contact Microsoft Customer Service and
Support.
944 Database operation failed. Make sure that SQL Server is running and that it is
configured correctly. Then retry the operation.
945 Unable to connect to the DPM Make sure that SQL Server is running and that it is
database because of a configured correctly.
general database failure.
946 Another instance of DPM is Restart the computer and then retry the operation
currently running. again.
948 Unable to connect to <server Verify that the DPM service is running on this computer.
name>.
949 A connection to DPM Server
<server name> is already
open.
951 No schedules found for the job
definition.
955 The consistency check
resulted in the following
changes to SQL Server Agent
schedules: Schedules added:
<schedules added> Schedules
removed: <schedules
removed> Schedules updated:
120
<schedules updated>.
956 DPM is unable to protect your To install agents on these servers, on the Agents tab in
Windows SharePoint Services the Management task area, click Install in the Action
farm until you install agents on pane. If any of the above servers correspond to a
the following servers : <server cluster, you need to install the DPM protection agent on
name>. all the physical nodes of that cluster.
975 The arguments for the job Retry the operation with the correct argument syntax.
definition are not valid.
976 The DPM job failed because it Restart the DPM service.
could not contact the DPM
engine.
998 The operation failed because Retry the operation.
of a protection agent failure.
999 An unexpected error caused a Restart the DPM service.
DPM service failure.
1000 Login failure caused by an Verify the password is correct and try again.
incorrect password.
1002 You cannot cancel the
selected job at this time.
1100 DPM: Information alert:
<server name>.
1101 DPM: Warning alert: <server
name>.
1102 DPM: Critical alert: <server
name>.
1103 DPM: Recovery alert: <server
name>.
1104 DPM: Resolved information
alert: <server name>.
1105 DPM: Resolved warning alert:
<server name>.
1200 Status: <alert status> For more information, open DPM Administrator Console
Volume: <volume name> and review the alert details in the Monitoring task area.
Computer: <server name>
Description: Used disk space
on replica volume exceeds
threshold of <threshold
value>.
Data source type: <data and review the alert details in the Monitoring task area.
source type>
Data source: <data source
121
name>
Protection group: <protection
group>
Description: Replica volume
cannot be detected.
Protection Group: <protection and review the alert details in the Monitoring task area.
group>
Description: DPM discovered
one of the following changes:
a. New shares or volumes
b. Deleted volumes or shares
c. Shares have been
remapped.
1204 The replica for <data source For more information, open DPM Administrator Console
name> on <server name> is and review the alert details in the Monitoring task area.
currently being synchronized
with consistency check. A
consistency check can be
started automatically or
manually. Automatic
consistency checks are
scheduled in the Protection
task area by selecting the
Optimize performance action.
Manual consistency checks
are initiated by an
administrator in the Protection
Create recovery point action.
source type> Data source:
<data source name>
Description: Replica is being
created.
1206 The replica of <data source For more information, open DPM Administrator Console
name> on <server name> is and review the alert details in the Monitoring task area.
inconsistent with the protected
data source. All protection
activities for this data source
will fail until the replica is
synchronized with consistency
check.
122
Computer: <server name> and review the alert details in the Monitoring task area.
Description: Recovery jobs
started @ <start date time>.
Description: New protectable and review the alert details in the Monitoring task area.
computers found.
Description: Data copy job and review the alert details in the Monitoring task area.
failed
Description: Backup to tape and review the alert details in the Monitoring task area.
failed.
started @ <start date time>
completed with some failures.
1211 Recovery to <protected server For more information, open DPM Administrator Console
name> that started at <start and review the alert details in the Monitoring task area.
date time> completed. Some
jobs have successfully
recovered data and some jobs
have failed.
started @ <start date time>
completed successfully.
source type>
name>
Description: Last <failure
count> recovery points not
created.
source type>
name>
123
Description: Synchronization
jobs failing.
source type>
name>
Description: DPM failed to
stop protection.
type> <data source name> on and review the alert details in the Monitoring task area.
<server name> is not created.
You have chosen to create the
replica manually. All
subsequent protection
created and synchronized with
consistency check.
type> <data source name> on and review the alert details in the Monitoring task area.
Replica creation job is
scheduled to run at a later
time. Data protection will not
start until replica creation is
complete.
Description: The disk <disk and review the alert details in the Monitoring task area.
name> cannot be detected or
has stopped responding. All
activities that use this disk will
fail until the disk is brought
back online.
Description: Incompatible
Description: Unable to contact
124
Description: Failed to update
end-user recovery
permissions.
Description: Network
bandwidth usage throttling not
working.
Description: DPM detected and review the alert details in the Monitoring task area.
multiple disks with the same
disk identification number
(DiskID). None of these disks
will be added to the DPM
Storage Pool.
1225 Unsupported data found. For more information, open DPM Administrator Console
and review the alert details in the Monitoring task area.
<library type> : <library> and review the alert details in the Monitoring task area.
Description: <library type>
<library> is not available, and
all jobs for this library will fail
until the connection is
established.
Description: Library is not
functioning efficiently.
Drive: <library drive>
Description: Tape is
decommissioned and should
be removed from the library.
Description: Number of free
tapes is less than or equals
the threshold value.
125
<library type>: <library> and review the alert details in the Monitoring task area.
Tape: <media label>
Description: Tape erase job
failed
1244 Database size on DPM server For more information, open DPM Administrator Console
has exceeded the threshold and review the alert details in the Monitoring task area.
value.
1255 The share <share name> that
previously mapped to <old
folder path> has changed to
<new folder path>. DPM will
continue to protect <old folder
path>, but recommends you
modify protection as
suggested in Recommended
Action.
2000 DPM failed to run the Retry the operation later.
operation because another
conflicting operation is in
progress.
Tape: <media list>
Description: Tape verification
job couldn't start or failed.
Description: Library catalog for and review the alert details in the Monitoring task area.
backup job was not built
correctly.
Library drive: <library drive>
Description: A drive in the
library is not functioning.
Tape: <media label>
Description: Tape has been
verified
Description: Job requires tape
that is not available in the
126
library
Tape: <media label>
Description: Detailed tape
inventory failed
Tape: <media label>
Description: Data integrity
verification failed.
Description: Used disk space
for recovery point volume
exceeds threshold of
<threshold value>.
source type>
name>
Description: DPM failed to
configure protection.
source type>
name>
Description: Consolidation of
recovery points failed.
2031 The specified path is invalid. The specified destination path is not valid. Restore to
an alternate location.
2032 The specified path does not The specified source path does not exist. Select a valid
exist. path.
2033 DPM encountered an error 1) Refer to the detailed error code in the description
while performing an operation above. Retry this operation after the issue has been
for <file name>. fixed.
2) If the error was due to insufficient resources, then it
127
could be a transient failure and you should retry this
operation after some time.
2034 The specified path does not The specified destination path does not reside on an
reside on an NTFS volume. NTFS volume. Restore to an NTFS volume .
2035 The operation failed because Increase the amount of free space on volume <volume
of inadequate disk space. name> on the destination computer and then retry the
operation, or recover to an alternate destination that
has sufficient free space.
2036 The Operation failed since 1) Run chkdsk on the affected volume and then run
DPM was unable to access synchronization with consistency check.
the file/folder <file name> on 2) If running chkdsk does not solve the problem, and
<agent protected server>. This the server indicated above is a protected server (and
could be due to the file/folder not the DPM server), consider deleting this file from the
being corrupt or the file system source and then running synchronization with
on the volume being corrupt. consistency check.
2037 DPM could not detect the Verify that <volume name> on <server name> exists. If
selected volume <volume the volume exists, retry the operation.
2038 Some items were not Retry the recovery to a destination that does not
recovered because recovering contain a reparse point.
items across a reparse point is
not permitted. The folder
<reparse point path> under
the recovery destination is a
reparse point.
3000 The requested report history
could not be found in SQL
Server Reporting Services.
4067 The number of DPM licenses Specify a number for the DPM licenses greater than or
must be greater than or equal equal to zero.
to zero.
3001 Reporting Services Server To repair the configuration, follow steps for repairing
cannot connect to the DPM DPM from DPM Setup Help.
database.
3002 DPM could not generate this
report. A parameter is missing
or it was incorrectly specified.
3003 The SQL Server Reporting Start the service on the computer on which the DPM
Services service is not database was created. On the Administrative Tools
running. menu, select Services. Right-click SQL Server
Reporting Services, and then click Start.
3004 You have insufficient Verify that you are an administrator on the DPM server.
permissions to perform this If the DPM SQL database is hosted on a remote
action on the report. computer, verify that you are a member of the DPM
administrators group on the remote SQL Server.
128
3005 DPM could not generate this
report. A parameter is missing
or it is incorrectly specified.
3006 The report you requested Repair your DPM installation using the steps described
could not be found on the SQL in the DPM 2010 Deployment Guide.
Server Reporting Services
server.
3007 The report cannot be Repair your DPM installation using the steps described
displayed because the report in the DPM 2010 Deployment Guide.
property settings are incorrect.
3008 The SQL Server Agent service Restart the SQL Server Agent service <instance
<instance name> is not name>.
responding.
3009 DPM could not set up a
schedule for this report. The
information is either missing or
it is incorrectly specified.
3010 DPM cannot set up an e-mail Click Options in the Actions pane, then click the SMTP
subscription for this report. Server tab, and provide the correct SMTP server name
The information may be and e-mail address.
missing or incorrect.
3011 There is not enough content to To generate this report, specify at least <day count>
generate a report for this time days.
period.
The number of days of
available data must be at least
<day count> before DPM can
generate this report.
3012 DPM cannot perform this Repair your DPM installation using the steps described
action because no valid in the DPM 2010 Deployment Guide.
property settings have been
detected for this report.
3013 DPM could not connect to SQL On the computer on which the DPM database was
Server Reporting Services created, restart the World Wide Web Publishing
server because of IIS Service. On the Administrative Tools menu, select
connectivity issues. Services, right-click World Wide Web Publishing
Service, and then click Start.
3014 An error occurred causing the Retry the reporting task. If the problem persists, repair
reporting job on <server your DPM installation using the steps described in the
name> to fail. The system files DPM 2010 Deployment Guide.
may be corrupt.
3015 DPM is unable to change the Log on to <server name>. On the Start menu, point to
e-mail settings. All Programs, point to Microsoft SQL Server 2008, point
to Configuration Tools, and then click Reporting
Services Configuration. In Configure Report Server,
129
update the e-mail settings.
3016 A Windows account is required To create the account, reinstall DPM using the steps
to view DPM reports. described in DPM Setup Help.
3021 DPM is unable to create the Delete the Windows account group, and then retry the
Windows account group operation.
because the group already
exists.
3017 The user account that DPM To reenable the account, in DPM Administrator
Reporting created is disabled. Console, click Reporting on the Navigation bar. Click
Options in the Actions pane, and on the Reporting
Password tab, enter a valid password.
3018 The reporting password for the Change the password for account <account name>. On
Windows account has expired. the Administrative Tools menu, click Computer
Management. Expand Local Users and Groups, and
then click Users. Right-click <account name>, and then
click Set Password.
3020 Unable to configure local Review the error details and take appropriate action.
Windows account in the Then retry the operation.
system. The operation is
allowed only on the primary
domain controller for the
domain.
3022 DPM is unable to create the Delete the Windows account, and then retry the
Windows account because the operation.
account already exists.
3023 DPM is unable to configure the Enter another password for the account.
Windows account because the
password you entered does
not meet the Group Policy
requirements.
3024 DPM cannot grant the DPM Verify that SQL Server is running, and that it is
database access to the <> configured correctly.
account.
3025 You are unable to add the Log on as an administrator or backup operator, and
local computer to the intranet then try the operation again.
security zone in Internet
Explorer because of
insufficient permissions.
3027 The report schedule has Check the DPM report settings.
expired and will be reset.
3030 DPM is unable to create the Specify today or a later date.
report schedule because the
date specified has already
past.
130
3031 DPM is unable to create the Specify a future date.
schedule because the time
specified has already past.
3032 The report file does not Repair your DPM installation using the steps described
contain an entry for the in the DPM 2010 Deployment Guide.
description.
3033 The report file contains an Repair your DPM installation using the steps described
incorrect description value. in the DPM 2010 Deployment Guide.
3028 You cannot add the computer We recommend that you reinstall Internet Explorer
to the trusted zone. 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
password in subsequent steps.
3029 DPM has detected incorrect Repair your DPM installation using the steps described
property settings for certain in the DPM 2010 Deployment Guide.
reports.
3034 DPM reporting requires Install ASP .NET 2.0. Use Add or Remove Programs in
ASP.NET 2.0, which is not Control Panel. Click Add/Remove Windows
found or installed on this Components, check Applications Server, and then click
computer. Details. Check ASP.Net and Internet Information
Services (IIS), and then click OK.
3155 Description: Data source For more information, open DPM Administrator Console
missing. and review the alert details in the Monitoring task area.
3167 The recovery jobs for <data No action required.
source name> that started at
<start date time>, with the
destination of <server name>,
have successfully completed.
3168 DPM database (DPMDB) size The DPM database (DPMDB) size cannot be reduced.
has exceeded the threshold To resolve this alert, you need to increase the free
limit. space in the DPMDB volume, or increase the alert
DPM database size: <DPM threshold value in the tape catalog retention dialog. If
database size> GB the tape catalog is very large, reducing the size of the
tape catalog may ensure that DPM database does not
DPM database location: <DPM
grow any further.
database location> on <server
name>.
3035 DPM is unable to read the Log on as an administrator and then retry the
registry to retrieve report operation.
settings because of insufficient
permissions.
3036 DPM reporting cannot query Connect to the computer on which the DPM database
the IIS configuration. was created. Verify that the Windows Management
Instrumentation service is running.
131
3038 SQL Server Reporting Verify that SQL Server Reporting Services is properly
Services is not installed or is installed and is running.
not configured properly.
3039 DPM reporting is not yet On the Administrative Tools menu, click Local Security
activated because the required Policy. Expand Local Policies, and then select User
security settings could not be Rights Assignment. Right-click Allow log on locally
applied to the DPMReport policy, and then click Properties. Click Add User or
local account. Groups, and add the DPMReport account. If the
account is listed in the Deny log on locally policy,
remove it.
3040 DPM Setup is unable to Log on to <server name>. On the Start menu, point to
update the report server All Programs, point to Microsoft SQL Server 2008, point
configuration to configure e- to Configuration Tools, and then click Reporting
mail settings. Services Configuration. In Configure Report Server,
update the e-mail settings.
3050 Unable to update shares or Re-run synchronization or wait for the next
share permissions. synchronization to occur. If the problem persists, check
your domain configuration.
3051 Unable to update the Active Either run a synchronization, or wait for the next
Directory Domain Services scheduled synchronization to occur. If the problem
database. persists, check your domain configuration.
3052 Active Directory Domain Redo the schema extension operation.
Services schema is not
configured properly.
3053 No nodes have been detected 1. On the Agents tab in the Management task area,
for cluster <cluster>. check if the cluster nodes are accessible
2. Use the cluster administrative console to check if the
cluster has been unclustered,
3054 One or more volumes are Ensure that the dependent volumes for the data
missing for the following sources are online.
applications: <list of data
sources>
3100 The used disk space on the Allocate more disk space for the replica. If no free disk
computer running DPM for the space is available in the storage pool, you may need to
replica of <data source type> add physical disks to the computer running DPM.
<data source name> has
exceeded the threshold value
of <threshold value>%%. If
you do not allocate more disk
space, synchronization jobs
may fail due to insufficient disk
space.
3101 Recovery data for <data Verify that the disk containing the replica volume and
source type> <data source the recovery point volume is shown in Disk
name> on <server name> in Management. If you are unable to locate the volumes in
protection group <protection Disk Management, use the Protection task area in DPM
132
group> resides on a volume Administrator Console to stop protection of the data
that cannot be detected. All source using the Delete replica option, and then add
subsequent protection the data source to a protection group again.
activities relating to <data
source name> will fail until this
volume is brought back online
or the replica is re-created.
3103 DPM failed to obtain catalog 1) If you do not expect to be performing item-level
information as part of the restores using this recovery point, then dismiss this
backup for <data source type> alert; otherwise, take the recommended actions in the
<data source name> on subsequent steps.
<server name>. Your recovery 2) If the operation failed for a short-term backup to disk,
point is valid, but you will be in the Protection task area, select the data source and
unable to perform item-level click Create recovery point to restart the backup.
recoveries using this recovery
3) If the operation failed for a short-term backup to
point.
tape, in the Protection task area, select all the failed
data sources that belong to the same protection group,
and click Create recovery point – tape. This will ensure
that the tape backups are located on the same tape.
4) Dismiss this alert immediately after starting your
backup.
3104 The replica for <data source No action required.
type> <data source name> is
currently being synchronized
with consistency check. A
consistency check can be
started automatically or
manually. Automatic
consistency checks are
scheduled in the Protection
Optimize performance action.
Manual consistency checks
are initiated by an
administrator in the Protection
Create recovery point action.
3105 The replica of <data source No action required.
<server name> is being
created. After the initial replica
is created, only incremental
changes are synchronized.
3106 The replica of <data source Synchronize with consistency check.
<server name> is inconsistent
with the protected data source.
All protection activities for data
133
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
source type> <data source
name> that started at <start
date time>, with the
are in progress.
3110 The recovery jobs for <data Make sure that the file is not already present and in use
source type> <data source on the destination computer, and that there is sufficient
name> that started at <start disk space for the files.
have completed. Some jobs
successfully recovered data
and some jobs failed.
The following items could not
be recovered: <temporary list
of files>.
3111 The recovery jobs for <data On the Jobs tab in the Monitoring tasks area, group
source type> <data source jobs by type to view details of the recovery jobs.
destination of <protected
server name>, have
completed. Most or all jobs
failed to recover the requested
data.
have successfully completed.
3113 Exchange Recovery If you are recovering to Exchange server which is CCR
or LCR, perform following steps:
1) Reseed the replica of the recovered storage group.
2) Resume storage group copy for the recovered
storage group.
3114 Recovery point creation jobs
for <data source type> <data
134
name> have been failing. The
number of failed recovery
point creation jobs = <failure
count>.
3115 Since <occurred since>,
synchronization jobs for <data
name> have failed. The total
number of failed jobs =
<failure count>. The last job
failed for the following reason:
3116 DPM failed to stop protection If you no longer want to protect any data sources on
for <data source type> <data the computer, you can uninstall the protection agent
source name> on <server from the computer. You can also retry the stop
name>. protection job.
3117 New computers were found See Details for list of computers.
that you may want to protect.
3118 The replica for <data source 1) Manually copy data to the replica path as specified in
type> <data source name> on the details for this data source in the Protection task
<server name> is not created. area.
You have chosen to create the 2) After you copy the data, click the link below to
replica manually. All synchronize with consistency check.
created and synchronized with
consistency check.
3119 The replica for <data source No action required.
Replica creation job is
scheduled to run at a later
time. Data protection will not
start until replica creation is
complete.
3120 The disk <disk name> cannot On the Disks tab in the Management task area, check
be detected or has stopped the status of disks. If a disk is missing, rescan the disk
responding. All subsequent configuration to detect the disk. If the disk is still
protection activities that use missing, verify physical disk connections and perform
this disk will fail until the disk is Rescan again. If the disk is no longer available, you
brought back online. can remove the disk from the storage pool. To continue
protecting the affected data, stop protection of the data
sources using the Delete replica option, and then add
the data sources to a protection group again.
3154 Description: New data source For more information, open DPM Administrator Console
found. and review the alert details in the Monitoring task area.
135
3121 The DPM protection agent on On the Agents tab in the Management task area, check
<server name> is incompatible the status of the agent and update to the correct
with this DPM instance. All version.
subsequent protection and
recovery activities for <server
name> will fail until the correct
version of the agent is
installed.
3122 The DPM protection agent on On the Agents tab in the Management task area, check
<server name> could not be the status of the agent.
contacted. Subsequent
protection activities for this
computer may fail if the
connection is not established.
The attempted contact failed
for the following reason:
3123 Failed to update permissions
used for end-user recovery on
<server name>. Permissions
update failed for the following
reason:
3124 DPM network bandwidth Either stop the DPM protection agent service on
usage throttling is not working <server name> and make sure that the QoS Packet
because the Windows Quality Scheduler is enabled, or disable network bandwidth
of Service (QoS) Packet usage throttling for the computer. To install the QoS
Scheduler is not enabled on Packet Scheduler: In Control Panel, point to Network
<server name>. 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.
3126 The share <share name> that To start protecting <new folder path>, in the Protection
previously mapped to <old task area, perform the following steps:
folder path> has changed to 1) Stop protection for this share.
<new folder path>. DPM will
2) Re-protect the same share again.
continue to protect <old folder
path>, but recommends you To setup protection properly for the <old folder path>, in
modify protection as the Protection task area, perform the following steps:
suggested in Recommended 1) Stop protection for this share.
Action. 2) Protect <old folder path>.
3127 DPM detected multiple disks 1) Check to see that multipath software is running on
with the same disk
136
identification number (DiskID). the DPM server.
None of these disks will be 2) In the Management task area, on the Disks tab, click
added to the DPM Storage Rescan.
Pool.
3151 DPM was unable to complete In the Monitoring task area, group jobs by type and
this job within the time review the job details. If the next scheduled occurrence
allocated. 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 Opt-in or opt-out of the Customer Experience
anonymous feedback Improvement Program.
automatically about your
hardware and software
configurations, and feature
usage patterns.
3159 Creation of recovery points for
<server name> have failed.
The last recovery point
creation failed for the following
reason:
3160 Synchronization jobs for <data
name> have failed.
3161 Recovery data for <data Verify that the disk containing the replica volume is
source name> on <server shown in Disk Management. Or, in the Protection task
name> in protection group area in DPM Administrator Console, use the Modify
<protection group> resides on disk allocation action to allocate replica space.
a volume that cannot be
detected. All subsequent
protection activities relating to
<data source name> will fail
until this volume is brought
back online or the replica is re-
created.
3162 The replica of <data source No action required.
name> on <server name> is
being created. After the initial
copy is made, only
incremental changes are
synchronized.
source name> that started at
137
are in progress.
3163 The replica of <data source
name> on <server name> is
inconsistent with the protected
data source. All protection
activities for data source will
fail until the replica is
synchronized with consistency
check.
3165 The recovery jobs for <data On the Jobs tab in the Monitoring tasks area, filter jobs
source name> that started at by type to view details of the recovery jobs.
have completed. Some jobs
have successfully recovered
data and some jobs have
failed.
3166 The recovery jobs for <data On the Jobs tab in the Monitoring tasks area, filter jobs
source name> that started at by type to view details of the recovery jobs.
destination of <protected
server name>, have
completed. Most or all jobs
failed to recover the requested
data.
3169 The used disk space on the Allocate more disk space for the recovery point volume
computer running DPM for the using the Modify disk allocation action in the Protection
recovery point volume of <data task area. If no free disk space is available in the
source type> <data source storage pool, you may need to add physical disks to the
name> has exceeded the computer running DPM.
threshold value of <threshold
value>%% (DPM accounts
600 MB for 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.
3170 DPM could not start a
recovery, consistency check,
or initial replica creation job for
<data source type> <data
name> for following reason:\n
3171 The start time is greater or
equal to the end time. Please
correct the filter definition.
138
3172 At least one library must be
selected in the filter definition.
3173 At least one data source must
be selected in the filter
definition.
3174 At least one job type and job
status must be specified in the
filter definition.
3175 Data transferred and time
elapsed must be an integer,
and greater than or equal to
zero, and less than the
maximum number size.
3176 Date not entered in the correct
format.
3177 The default filter cannot be
updated or deleted.
3178 Consolidation of recovery Check the Alerts tab in the Monitoring task area to
points of the replica failed for locate the specific alert for the operations indicated
<data source type> <data above. Follow the recommended action for that alert. If
source name> on <server you do not find any active alerts for the operations
name> when one of the indicated above, you should click the link below to
following operations was being inactivate this alert.
performed:
 Express full backup
 Consistency check
 Recovery
3179 There already exists a filter
with the given name. Please
specify a different filter name.
3200 Could not access end-user Check the domain configuration to ensure that the DPM
recovery-specific information schema extension has been successfully applied to the
in Active Directory Domain Active Directory. Also verify that DPM has permissions
Services to access the data in the extended schema.
3201 DPM failed to log in with the Check your password and then retry the operation.
specified password.
3202 Could not access end-user Re-run synchronization or wait for the next
recovery-specific content in synchronization to occur. If the problem persists, check
Active Directory Domain your domain configuration.
Services.
3301 <library type> <library> could
not be contacted. All jobs for
<library type> <library> will fail
if the connection is not
139
established. The attempted
contact failed for the following
reason:\n
3302 <library type> <library> is not The number of drives reported for this library is different
functioning efficiently for the from the number of drives detected by DPM. If any
following reason: drives are out of the library for servicing, ignore this
The drive information for alert; otherwise, remap the drives within the library
<library type> <library> is manually. For information about remapping tape library
incorrect and needs to be drives, see the DPM 2010 Operations Guide.
refreshed.
3303 Library drive <library drive> in
<library> is not functioning and
library jobs may fail until the
drive is repaired. The drive is
not functioning for the
following reason:\n
3304 DPM has marked the <media This tape is decommissioned and should be removed
label> tape as from the library. You may be able to recover data from
decommissioned, which this tape. If recovery from this tape fails, check for a
means that data cannot be duplicate or older copy of the data.
written to this tape in the
future. You may be able to
recover data from this tape.
3305 The number of free tapes in Add tape to the library and mark it as free.
the <library type> <library> is
less than or equals the
threshold value of <threshold
value>. You must add tape to
the library and mark it as free
in order to prevent future
backups from failing.
3308 <media label> could not be
erased for the following
reason:
3309 Data on the tapes <media list>
cannot be verified for the
following reason:\n
3310 The data copy job failed for
the following reason:\n
3311 The back up to tape job failed
3312 The backup to tape job
completed, but the catalog
was not built correctly for
140
name>. Although no data is
lost, you must rebuild the
catalog to access the data of
the backup job.
3313 Verification is completed for No action required.
the following tape(s) in <library
type> <library>: <media list>
3316 The detailed inventory of tape
failed for the following reason:
3500 Your search returned more Use the search controls to refine your search.
than 250 results. Only 250
results can be displayed.
3605 This job cannot be rerun
because the data is not valid.
To retry, in the Recovery task
area, copy the data to tape
using the Recovery wizard.
3314 The recovery job is paused Insert the required tape in the library through the I/E
because the required tape is port or by unlocking the library door. Click "Continue
not available in <library type> Job" in the details section of this alert, if you add the
<library>. required tape without using the Add tape (I/E port) or
Unlock Door actions on the Library tab in the
Management task area.
3315 <task name> is paused Insert the tape with label <media label> in the library
because the required tape through the I/E port or by unlocking the library door.
<media label> is not available Click "Continue Job" in the Details section of this alert,
in the library <library type> if you add the required tape without using the Add tape
<library>. (I/E port) or Unlock Door actions on the Library tab in
the Management task area.
3317 Data verification of <data
source name> on tape <media
list> in <library type> <library>
found data integrity issues on
the following files:
<temporary list of files>
3603 To cancel pending replica
creation for <volume name>
on <server name>, remove all
members from the protection
group <protection group> 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
141
therefore this job cannot be re-
run. On the Jobs tab in the
Monitoring task area, re-run
this job.
To retry, in the Recovery task
area, click Verify data in the
Actions pane.
To retry, recatalog the tape's
contents in the Recovery task
area.
because the protection group
associated with it has been
modified.
3700 An incompatible version of the Restore a valid database using the steps described in
database was detected. DPM the DPM 2010 Operations Guide, and then retry the
cannot continue loading DPM operation.
Administrator Console.
3750 Version <database version> of Restore a valid database using the steps described in
the DPM database, and the DPM 2010 Operations Guide, and then retry the
version <binary version> of the operation.
DPM application are not
compatible.
3751 The evaluation copy of DPM You must purchase a DPM license. For details about
has expired. obtaining a DPM license, see the Microsoft System
Center Data Protection Manager Web site at:
http://go.microsoft.com/fwlink/?LinkId=86309.
3752 DPM could not find the Uninstall DPM and then re-install DPM to recreate the
MSDPMTrustedMachines security group.
security group. Either this
group has been deleted or the
entry is corrupt.
3753 The version of the DPM To continue using DPM, you must install any service
database installed on this packs or hotfixes that were part of your previous DPM
computer is later than the installation.
version of the DPM
application.
3754 DPM Administrator Console
can be opened only by a user
belonging to a domain. Log on
using a domain user account,
and try again.
142
4026 DPM Setup failed to configure Use Add or Remove programs in Control Panel to
the service <service name>. uninstall DPM. After uninstalling, run DPM Setup again.
4027 DPM Setup was unable to Manually delete the volumes allocated to the storage
collect information about pool or format the disks.
volumes in the storage pool
because access to the
database was denied.
4028 Setup was unable to delete Manually delete the database using SQL Server
the <database name> Management Studio.
database.
4001 There is insufficient disk space To continue with the installation, free up <system disk
on system volume <system space required> MB of disk space on the system
drive> to complete the volume.
installation.
4002 The SQL Server Reporting Uninstall SQL Server 2008, and then run DPM Setup
Services installation is not again to install the prerequisite software.
valid because it is installed on
a computer on which Internet
Information Services (IIS) or
ASP.Net is not installed.
4003 Setup has detected that the 1) To use the local dedicated MS$DPM2007$ instance
installation of Reporting with DPM, uninstall SQL Server and run setup again.
Services is not correctly 2) To use the option of installing DPM with an existing
configured or no instance of instance of SQL Server, make sure that the Reporting
Reporting Services is linked to Services instance is also installed and linked correctly.
<instance name> of SQL For details, refer to DPM Setup Help.
Server.
4005 DPM found the following Setup will delete these databases.
databases that were created
by an earlier installation of
SQL Server Reporting
Services: <comma separated
database names>.
4006 Service <name> is running DPM Setup will change the credentials to a local user
under <credentials> account.
credentials. <name> must run
under local user credentials.
4007 Service <name> is not Uninstall <prerequisite> and then run DPM Setup
installed. The <prerequisite> again.
installation is not valid.
4012 The <name> service is In the Reporting Services Configuration tool, choose
running under <credentials> 'Windows Service Identity' and change the settings to
credentials. We recommend the built-in Network Service account for <SQL Server
that the service run under the instance name> instance of SQL Server 2008.
NT Authority\NetworkService
account.
143
4015 You installed DPM protection In DPM Administrator Console, click Management on
agents on several computers. the Navigation bar. On the Agents tab, select the
We recommend that you agents, and then click Uninstall.
uninstall them before
proceeding.
4017 DPM database <DPM If you are performing a clean installation of DPM, you
database> is missing or must delete the DPM database before you run Setup. If
corrupt. you are upgrading or repairing an existing installation of
DPM, you must restore a valid DPM database, and
then proceed with Setup.
4019 DPM Setup detected an In SQL Server Management Studio, delete the <DPM
existing DPM database in the database> database, and then run DPM Setup again. If
<SQL Server instance name> you need to reuse an older DPM database, back up the
instance of SQL Server. DPM database and restore it after completing the DPM
cannot be installed on an installation.
existing database.
4020 DPM Setup detected several In DPM Administrator Console, in the Protection task
existing protection groups. area, remove the groups from protection, and then run
DPM Setup again.
4021 DPM Setup could not access Verify that the computer is joined to a domain, that DNS
Active Directory Domain is correctly configured, and that you are logged on as a
Services. You cannot proceed domain user with administrator user rights.
with the DPM Installation.
4023 The <prerequisite> installation Manually install <prerequisite>. For instructions, see
failed. All changes made by "Manually Installing Prerequisite Software" in the
the <prerequisite> installation DPM 2010 Deployment Guide.
to the system were rolled
back.
4024 The <prerequisite> installation Manually install <prerequisite>. For instructions, see
failed. All changes made by "Manually Installing Prerequisite Software" in the
the <prerequisite> installation DPM 2010 Deployment Guide.
to the system were rolled
back.
4025 The <prerequisite> Use Add or Remove programs in Control Panel to
configuration failed. uninstall <prerequisite>. After uninstalling
<prerequisite> run DPM Setup again.
4032 DPM could not delete the Manually delete account <account name>.
<account name> user
account.
4033 DPM Setup could not remove Manually delete the DPM Administrator Console
the DPM Administrator shortcuts.
Console shortcuts from:
<comma separated shortcut
locations>.
4034 DPM Setup could not delete Manually delete service <service name>. On the
144
service <service name>. Administrative Tools menu, click Services.
4036 The DPM database was Delete the database files manually.
removed, however, DPM could
not remove database files
<database files complete
location>.
4029 Setup was unable to delete Open SQL Server Management Studio, and connect to
the schedules from the master the DPM instance of SQL Server. Expand the instance
database. of SQL Server, browse to SQL Server Agent, and then
in Jobs, delete the <schedule category> category.
4030 Setup was unable to remove If you are reinstalling DPM on this computer, no action
reports deployed with SQL is necessary. If you are not reinstalling DPM, you must
Server Reporting Services. uninstall SQL Server 2008 to remove the reports.
4031 The computer <computer In Internet Explorer, on the Tools menu, click Internet
name> could not be removed Options. In the Internet Options dialog box, on the
from the intranet security zone Security tab, click Local intranet, click Sites, then click
settings in Internet Explorer. Advanced, and then remove computer <computer
name> from the intranet zone.
4035 DPM Setup could not delete Delete the group manually. On the Administrative Tools
the <group name> group on menu, click Computer Management. Expand Local
computer <computer name>. Users and Groups, and then click Groups. Right-click
<group name>, and then click Delete.
4037 To finish deleting service Restart your computer.
<service name>, you must
restart the computer.
4038 DPM Setup was unable to Manually unmount the volumes using Disk
unmount the volumes from Management.
<volumes directory>.
4039 This computer has less than Add more memory to this computer or install DPM on a
the recommended amount of different computer.
memory for optimal
performance of DPM. The
recommended amount of
memory is 2 GB.
4040 The domain controller role is Install DPM on a computer that is not a domain
enabled on this computer. controller.
DPM does not support
installing DPM on a domain
controller.
4042 Setup has detected that SQL Install SQL Server 2008 Service Pack 1 or higher and
Server 2008 Service Pack 1 try again.
has not been installed on the
selected SQL Server.
4045 DPM Setup was unable to set Verify that the folder <directory path> is a valid location
permissions on folder and that the current user has access to the location.
145
<directory path>.
4046 DPM cannot delete <file Verify that the current user has permissions to delete
name>. the file.
4047 DPM Setup was unable to Review the error details, take the appropriate action,
configure service <Setup and then try running DPM Setup again.
service name>.
4049 The <prerequisite> installation Use Add or Remove Programs in Control Panel to
failed. All changes made by uninstall DPM. Then manually install <prerequisite>.
the <prerequisite> installation For instructions, see "Manually Installing Prerequisite
to the system were rolled Software" in the DPM 2010 Deployment Guide.
back.
4050 The <prerequisite> installation Use Add or Remove Programs in Control Panel to
failed. All changes made by uninstall DPM. Then manually install <prerequisite>.
the <prerequisite> installation For instructions, see "Manually Installing Prerequisite
to the system were rolled Software" in the DPM 2010 Deployment Guide.
back.
4054 Setup was unable to add Review the error details. Use Add or Remove Programs
protected computers to the in Control Panel to uninstall DPM, and then run DPM
<DCOM Users Group> group. Setup again.
4065 You did not specify the . Specify a .
4066 You did not specify a company Specify a company name.
name.
4072 The specified path <file name> Specify a valid path and verify that the path is
is invalid. accessible.
4073 The command line argument See "Installing DPM" in DPM Setup Help.
<command line argument> is
invalid.
4074 The path <file name> exceeds Choose a path with a shorter length.
<maximum limit> characters.
4075 The command line argument See "Installing DPM" in DPM Setup Help.
<command line argument> is
already specified.
4051 There is insufficient disk space To continue with the DPM installation, free up <binary
on the program files volume disk space required> MB of disk space on the volume.
<binary drive> to complete the
installation.
4052 You cannot install DPM on a
server if a DPM protection
agent has been installed it.
4053 DPM Setup was unable to Delete the protected computers from the group. On the
remove the protected Administrative Tools menu, click Computer
computers from the <DCOM Management. Expand Local Users and Groups, and
Users Group> group. then click Groups. Right-click <DCOM Users Group>,
146
and then click Delete.
4055 DPM Setup was unable to If Windows Firewall is enabled, remove DPM and the
remove DPM and the protection agent from the exceptions list. In Control
protection agent from the Panel, click Windows Firewall, click the Exceptions tab,
Windows Firewall exceptions and then delete Microsoft System Center Data
list. Protection Manager 2007 and the Microsoft System
Center Data Protection Manager 2007 Replication
Agent from the list of exceptions.
4056 DPM Setup was unable to add Review the error details. In Control Panel, click
DPM to the Windows Firewall Windows Firewall, and on the General tab, verify that
Exceptions. 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 To continue with the installation, free up <database disk
on the database volume space required> MB of disk space on the volume.
<database drive> to complete
the installation.
4058 DPM requires the To avoid expiration of SQL Server 2008, exit Setup and
Microsoft$DPM$ instance of install the SQL Server 2008 licensed retail copy, or
SQL Server. None of the upgrade to SQL Server 2008 within 180 days. To
existing SQL Server properly configure the SQL Server 2008 settings, see
installations have the name "Manually Installing Prerequisite Software" in the
Microsoft$DPM$. Setup will DPM 2010 Deployment Guide.
install the Evaluation Edition of
SQL Server 2008, which will
expire in 180 days.
4059 DPM Setup installs the To avoid expiration of SQL Server 2008, exit Setup and
Evaluation Edition of SQL install the SQL Server 2008 licensed retail copy, or
Server 2008 which expires upgrade to SQL Server 2008 within 180 days. To
180 days after installation. properly configure the SQL Server 2008 settings, see
"Manually Installing Prerequisite Software" in the
DPM 2010 Deployment Guide.
4063 The Default Web site that At the command prompt, run inetmgr.exe. To enable
Internet Information Services the Default Web site, expand the Web Sites folder,
(IIS) uses is disabled. You right-click Default Web Site, and then click Start.
cannot install or run SQL
Server Reporting Services if
this Web site is unavailable.
4064 The Default Web site used by Use Add or Remove Programs from Control Panel.
Internet Information Services Uninstall SQL Server 2008 and SQL Server 2008
(IIS) does not exist. SQL Reporting Services if already installed. Uninstall
Server 2008 Reporting Internet Information Services (IIS). Then run DPM
Services cannot be installed or Setup again to install IIS and SQL Server 2008 with
run unless this Web site is Reporting Services with the correct configuration.
available.
4068 Installation source <folder Make sure that the DPM installation DVD is copied
path> for installing
147
prerequisites either does not correctly and re-run Setup.
exist or cannot be accessed or
Setup cannot find one or more
prerequisites at the location.
4069 The input <input parameter Specify a valid input <input parameter tag>.
tag> is mandatory.
4070 The prerequisite check failed Review the errors in the DPM setup log file <Setup log
with errors. file>. Resolve the errors, and then run DPM Setup
again.
4071 DPM Setup could not delete Please delete the shortcuts manually.
the DPM Administrator
Console shortcut from:
<comma separated shortcut
locations>.
4076 The value for <command line See "Installing DPM" in the DPM Setup Help.
argument> was not specified.
4077 DPM is not installed on this Run DPM Setup from the DPM product DVD.
computer.
4078 DPM is already installed on To uninstall DPM, use Add or Remove Programs in
this computer Control Panel.
4079 DPM is not installed on this To install DPM, see "Installing DPM" in DPM Setup
computer. Help.
4080 No IN file is specified in the See "Installing DPM" in DPM Setup Help.
command line.
4081 DPM configuration failed. Refer to the "Troubleshooting" section of DPM Setup
Help.
4082 DPM cannot start service Start the service manually. On the Administrative Tools
<Setup service name>. menu, click Services. Right-click <Setup service
name>, and then click Start.
4083 DPM setup could not configure Refer to "Troubleshooting" section of DPM help.
agents.
4084 DPM setup could not configure Refer to "Troubleshooting" section of DPM help.
SQL Server 2008 Reporting
Services.
4086 DPM has been successfully Delete folder <folder path> manually.
installed. However, DPM
Setup could not delete the
extracted folder <folder path>.
4087 DPM Setup could not delete Delete folder <folder path> manually.
the extracted folder <folder
path>.
4088 DPM Setup could not delete Delete the directory manually. On the Administrative
the virtual directory <folder Tools menu, click Internet Information Services (IIS)
148
path>. Manager. Expand the Web Sites folder, expand Default
Web Site, and then delete the virtual directory <folder
path>.
4089 DPM Setup could not Verify that the MSSQL$<instance name> service is
configure the database started. If the service is not started, on the
<database name>. Administrative Tools menu, click Services. Right-click
MSSQL$<instance name>, and then click Start.
4090 DPM Setup detected that No action is required.
Microsoft$DPM$, the instance
of SQL Server used in the
current installation of DPM, is
an instance of SQL
Server 2008 Evaluation
Edition. Setup will upgrade the
instance to the SQL
Server 2008 Retail Edition as
part of the DPM upgrade.
4091 DPM Setup could not If the current installation of DPM uses an expired
determine the edition of SQL instance of the Evaluation Edition of SQL Server 2008,
Server used in the current you must manually upgrade to the retail edition of SQL
installation of DPM. Server 2008. For instructions, see the DPM 2010
Deployment Guide. For more information about this
error, see the application event log.
4093 DPM Setup has detected that No action required.
the current installation of DPM
uses the Evaluation Edition of
SQL Server 2000 Reporting
Services. Setup will upgrade
to the retail edition of SQL
Services as part of the
upgrade of DPM.
4208 DPM Writer could not access Make sure that Data Protection Manager is installed
the registry. correctly.
4211 You do not have sufficient On the DPM server, use Event Viewer to view details
privileges to perform this for this event. The details are available in the
operation. application event log.
4094 DPM Setup could not Verify that the Report Server and World Wide Web
determine the edition of SQL Publishing services are running: In Control Panel, click
Server 2008 Reporting Administrative Tools, click Services, and check the
Services used in the current Status column for each service.
installation of DPM.
4095 DPM Setup has detected that Manually upgrade to the retail edition of SQL
the current installation of DPM Server 2000 Reporting Services, and then run DPM
uses an expired instance of Setup again. For instructions for upgrading Reporting
the Evaluation Edition of SQL Services, see the DPM 2010 Deployment Guide.
149
Services.
4200 The DPM Writer service could Review the Application Event log for more details.
not be accessed. Verify that DPM is installed and that the DPM Writer
service is running.
4201 The backup operation did not Ensure that the DPM replicas are not busy and retry
complete successfully. Some the operation.
backup shadow copies could
not be created.
4206 DPM Writer could not connect Make sure that the SQL Server instance used by DPM
to the <database name> is running and is accessible over network.
database.
4207 DPM Writer could not query Make sure that the SQL Server instance used by DPM
the <database name> is running and is accessible over network.
database.
4209 DPM Writer encountered an Please restart the DPM Writer service, and then try the
internal error. backup operation again. For additional troubleshooting
information, review the application event log and the
DPM Troubleshooting Guide.
4210 DpmBackup encountered an Please try the backup operation again. For additional
internal error. troubleshooting information, see the DPM
Troubleshooting Guide.
4216 DpmPathMerge could not Make sure that the SQL Server services are running
query the <database name> with appropriate privileges.
database.
4217 DpmPathMerge could not Make sure that Data Protection Manager is installed
access the registry. correctly.
4317 DPM Setup failed to disable Manually stop and disable the Removable Storage
the Removable Storage service. On the Administrative tools menu, click
service (NtmsSvc). Services. Right-click Removable Storage, and then
click Stop. Then run DPM Setup again.
4318 DPM Setup failed to create the Review the error details, take the appropriate action,
DPMRADCOMTrustedMachin and then run DPM Setup again.
es or
DPMRADmTrustedMachines
group.
4319 DPM has been successfully Restart the computer to complete the DPM installation.
installed. However, you must
restart the computer to
complete the DPM installation.
configure the and then run DPM Setup again.
DPMRATrustedMachines
Group security settings.
4320 You cannot install DPM on a Use the Cluster Administrator tool to remove this
150
computer with Microsoft computer from the cluster or install DPM on another
Cluster service enabled. computer.
4323 DPM Setup failed to add a Review the error details, take the appropriate action,
user to the local group. and then run DPM Setup again.
4218 DpmPathMerge encountered Please try the operation again. For additional
an internal error. troubleshooting information, see the DPM
Troubleshooting Guide.
4219 Either because this replica To ensure that this replica is consistent with the
was restored from a backup protected data, run the FsPathMerge tool to manually
that was not created using the remove extraneous path information from the restored
DpmBackup tool, or because replica. For instructions for using FsPathMerge, see the
the GUID of the protected DPM Operations Guide.
volume has changed since the
backup was created,
DpmPathMerge cannot
automatically remove
extraneous path information.
4220 DPM writer was unable to In DPM Administrator Console, run a consistency check
snapshot the replica of <data for the data source to ensure that the replica is
source name>, because the consistent.
replica is not in a valid state
(Validity: <validity>).
4221 DPM Writer has timed out Retry again when no jobs are running for the selected
waiting for replica to be free data source.
and available for snapshot.
4222 DPM has run out of free 1) Increase the space allocated for the recovery point
recovery point space and will volume for <data source name>.
fail snapshots for <data source 2) Retry the operation after increasing the space for the
name> in order to prevent recovery point volume.
existing recovery points from
getting recycled.
4300 DPM Setup could not delete Delete the DPMRA service manually. At the command
the DPMRA service. prompt, type "sc delete DPMRA".
4301 DPM Setup was unable to For information about manually uninstalling Dr. Watson,
uninstall the Dr. Watson see "Troubleshooting" in DPM Setup Help.
version that DPM installed.
4303 DPM Setup has detected that Install Windows PowerShell and Power shell
the required version of Multilanguage User Interface pack. Then run DPM
Windows PowerShell is not Setup again.
installed. This software is
required for DPM to run
correctly.
4304 DPM Setup detected that the To install SIS, run "start /wait ocsetup.exe SIS-
Single Instance Store (SIS) Limited /quiet /norestart" from the command-line and
component is not installed. restart the computer. Then run DPM setup again
This software is required for
151
Data Protection Manager to
run correctly.
4305 DPM Setup detected a Download and install Microsoft Management Console
previous version of Microsoft 3.0 from http://go.microsoft.com/fwlink/?LinkId=55423
Management Console. or upgrade the operating system to Windows
Server 2003 R2, and then run DPM Setup again.
4306 DPM Setup is unable to use Review the error log for details. Verify that the Remote
the credentials provided to log SQL Server administrator credentials you provided are
on as <username>. correct and that they have logon permissions on the
local computer.
4307 DPM Setup is unable to Verify that the specified computer and the instance of
connect to the specified SQL Server meets the following requirements:
instance of SQL Server. 1) The computer is accessible over the network.
2) A firewall is not blocking requests from the DPM
computer. For steps to configure the firewall on the
SQL Server, follow the steps described here:
http://support.microsoft.com/kb/914277.
3) The specified user is an administrator on the
computer running the instance of SQL Server.
4308 An invalid SQL Server Specify a valid instance of SQL Server.
instance was specified.
4309 The SQL Server 2008 Manually install SQL Server 2008. For instructions, see
installation failed. All changes "Manually Installing Prerequisite Software" in the
made by the SQL Server 2008 DPM 2010 Deployment Guide.
installation to the system were
rolled back.
4312 DPM Setup detected that the
Removable Storage service is
running. To install DPM
correctly, DPM Setup will stop
and disable this service.
4313 DPM Setup could not delete Delete the service manually. At the command prompt,
the DPM Library Agent type "sc delete DPMLA".
service.
share the folder and then run DPM Setup again.
[InstallLocation]\Temp as
MTATempStore$.
4310 The SQL Server 2008 Review the SQL Server installation log file for failures,
installation failed. and then take the appropriate action.
4315 DPM Setup could not Verify that the DPM server is a member of a domain
configure the security settings and that a domain controller is running. Additionally,
for this computer. verify that there is network connectivity between the
DPM server and the domain controller.
152
4321 DPM cannot access registry Verify that the registry key exists, that user <> has full
key <registry key> on permissions, and that the Remote Registry service is
computer <computer name>. running on this computer and computer <computer
name>.
4324 You cannot choose the Specify a different instance to install DPM or choose
instance <instance name> on the option to let DPM install its own SQL Server
the local computer. instance. If DPM's SQL Server instance already exists,
it will be reused.
4325 DPM Setup failed to get the Verify that computers are joined to the same domain,
fully qualified domain name for that the DNS client service is running, and that DNS is
either the computer running accessible over the network. Then run DPM Setup
DPM or the computer with the again.
selected instance of SQL
Server.
4326 DPM Setup failed to create Review the error details, take the appropriate action,
certificate stores required for and then run DPM Setup again.
DPM.
4327 Setup failed to delete the At a command prompt, run "certutil.exe -delstore" to
certificate stores created for delete the certificates in DPMBackStore and
DPM. DPMRestoreStore.
4328 The service <name> is Run the SQL Configuration tool on the computer
running under <credentials> running SQL Server to change the account for the
credentials. It should be services. Then try again.
running under domain user
credentials.
4329 DPM setup is unable to verify Verify that this computer does not have the Microsoft
if the Microsoft Cluster service Cluster service enabled, and then proceed with the
is enabled on this computer. DPM installation.
4330 DPM Setup could not remove Manually delete account <user account name> from
the account <user account the group.
name> from the group <group
name>.
4331 The Microsoft System Center If no other DPM server is using the server for hosting
DPM Support Files on the SQL the DPM database, uninstall the Microsoft System
Server computer <computer Center DPM Support Files using Add or Remove
name> were not removed. Programs in Control Panel.
4332 Could not query database Review the error message and retry the action:
<database name> from the <exception message>
<instance name> instance of
SQL Server.
4333 DPM Management Shell is On the Start menu, select "DPM Management Shell"
already installed on this from "Microsoft System Center Data Protection
computer. Manager 2007".
4334 DPM 2010 cannot be installed Install DPM 2010 on a different computer and migrate
on the same computer as your settings using the upgrade tool. For details, refer
153
DPM 2006. to the DPM 2010 Deployment Guide.
4335 Cannot find file: <file name>. Run MigrateDPM2006 [-exportSettings] [-
dpm2006server ServerName] first to create the file.
4336 Settings file <file name> is Run MigrateDPM2006 [-exportSettings] [-
invalid. dpm2006server ServerName] to recreate the file.
4337 The DPM protection agent is Install the agent and try the operation again.
not installed on the computer
<computer name>.
4338 Could not find configuration for Enter a valid name for a computer configuration to
<computer name>. migrate.
4339 Failed to copy file <file name> Review the error details and take appropriate action.
from <source location> to Then retry the operation.
<destination location>.
4340 There is insufficient disk space Free <database disk space required> MB of disk space
on the database volume on the volume to continue with the installation.
<database drive> on
<computer name>.
4341 Setup cannot query the SQL Make sure that SQL Server service is running.
Server.
4342 A restart is required to
complete the uninstallation of
Data Protection Manager.
4343 MigrateDPM2006 has Make sure that:
encountered an error. 1) You have administrator access to <computer name>.
2) Check the computer name provided and make sure
the computer has an installation of Data Protection
Manager 2006 with Service Pack 1 applied.
4344 Setup could not detect an Install the SQLPrep.msi located on the installation DVD
installation of Microsoft or installation share, and try again. The package is
System Center DPM Support located inside the DPM 2010 install (msi) folder.
Files on the selected SQL
Server.
4345 Setup has detected that the Install the latest SQLPrep.msi located on the
selected SQL Server has an installation DVD or installation share, and try again.
older version of Microsoft The package is located inside the DPM 2010 install
System Center DPM Support (msi) folder.
Files installed.
4346 The settings for data source Run MigrateDPM2006 [-importSettings] [-
<data source name> on server dpm2006server ServerName] [-protectedServer
<server name> have not been ServerName] and then retry the data copy.
imported to this DPM server.
4347 Copy for replica <data source Review the error details and take appropriate action.
name> on computer <server Then retry the operation.
154
name> failed and this data
source is being skipped.
4348 DPM requires the Named On the selected server, run the SQL Server
Pipes protocol to be enabled Configuration Manager tool and enable the network
on the selected instance of configuration for the selected instance.
SQL Server.
4349 Unable to set permissions on Review the error details, take the appropriate action,
the folder corresponding to and then retry the installation.
"MTATempStore$" share.
4350 DPM Upgrade marked replicas
are invalid.
4351 Setup has detected that client- On the selected server, in Administrative Tools, run
side certificates are required Internet Information Services Manager. For the Default
for Internet Information Web site, select "Properties" and click the "Directory
Services on this computer. Security" tab. Under "Secure Communication", click
DPM does not support IIS "Edit" and set the option for client certificates option to
requiring client-side "Ignore client certificates" or "Accept client certificates".
certificates.
4352 Setup was unable to mount Using Disk Management, manually mount the DPM
replica volumes under the path volumes before using DPM.
4353 Setup was unable to dismount Using Disk Management, manually dismount the DPM
replica volumes under the path volumes.
4355 DPM setup has detected that
the SQL Server Agent service
on the selected instance is not
configured to run as
"Automatic". Setup will
reconfigure the service to
ensure DPM can function
correctly after installation.
4356 DPM Setup detected that a Install hotfix 940349 from
required hotfix is missing. http://support.microsoft.com/kb/940349, and then run
DPM Setup again.
4357 Setup has detected that this Disable library sharing by running the following
DPM server is using a shared commands and launch setup again.
library. 1. SetSharedDPMDatbase.exe –
RemoveDatabaseSharing.
2. AddLibraryServerForDpm.exe
-DpmServerWithLibrary -Remove
4358 DPM setup has detected the At the command prompt, run inetmgr.exe. To change
Default Web Site is not port for the Default Web site, expand Web Sites, right
configured to use port 80. click Default Web Site, and select properties. Configure
'TCP port' setting to '80'.Then, run setup again.
155
4359 DPM Setup was unable to set Ensure all volumes are online. In Disk Management
security permissions on some Console, right-click every DPM volume and select
of the volumes in the storage Properties. From the Security tab, restrict access to the
pool. The volume may be volumes for administrators group and the LocalSystem
missing. account only by applying the appropriate permissions.
4360 DPM setup cannot upgrade Ensure correct SQL data files are copied from existing
the existing installation DPM SQL instance and attached to the given SQL
because the DPM database instance. Then, run DPM 2010 Setup again.
version does not match with
installed DPM version.
6002 DPM cannot access the path Set the permissions for the SYSTEM account to allow
<file name> because the Full Control of the item.
SYSTEM account has been
denied permission.
6003 DPM cannot access the path Set the permissions for the SYSTEM account to allow
<file name> because the Full Control of the item.
SYSTEM account has been
denied permission.
2304 DPM has unexpectedly If you have another copy of this tape, then retry
3 reached the end of the tape recovery using the copy.
<media label>. This could be
because the tape was
tampered with.
2304 Rescan cannot be performed Wait for the other operations to complete, and then
4 because DPM is currently retry this operation.
performing other operations on
the server.
2304 DPM failed to move one or 1) Check to see that the library door is locked and that
5 more tapes to the I/E port slots the I/E port is retracted. 2) Check to see that there are
sufficient free I/E port slots in the library.
6012 DPM cannot access mount Set the permissions for the SYSTEM account to allow
points under the path <file List Folder Contents and Read for items in the specified
name> because the SYSTEM path.
account has been denied
permission.
6013 DPM cannot access mount Set the permissions for the SYSTEM account to allow
points under the path <file List Folder Contents and Read for items in the specified
name> because the SYSTEM path.
account has been denied
permission.
2400 Tape <media label> cannot be
7 marked as a cleaning tape
because it is not a cleaning
tape.
2400 DPM cannot complete the Retry the operation later.
8 requested operation on tape
156
<media label> because this
tape is being used by some
other job.
2401 Library lacks power or cables 1) Verify that the library is turned on.
4 are not connected properly 2) Verify that data connection and power cables are
connected properly.
3) Open Computer Management and verify that the
library is displayed in Device Manager.
2401 Tape is stuck in the library Remove the tape from the library autoloader. Consult
5 autoloader. the documentation for your hardware for instructions on
troubleshooting tape errors. When the tape is repaired,
run the library job again
2401 The <library type> <library> On the Libraries tab in the Management task area,
7 drive information needs to be select the library and click Rescan in the Actions pane.
refreshed.
2401 Drive cleaning failed or timed Change the cleaning tape and then, on the Libraries
8 out. tab in the Management task area, select the drive and
click Clean in the Actions pane.
2401 Drive <drive name> in <library Contact product support for your hardware to get the
9 type> <library> needs drive serviced. You should also review all protection
servicing. groups to identify if the absence of this drive requires
changes to drive allocations.
2402 DPM attempted to move a 1) On the Libraries tab in the Management task area,
1 tape to <element type> select the library <library> and click 'Inventory' in the
<element name> but this Actions pane.
<element type> was occupied. 2) If the <element type> contains a tape, remove this
DPM may not be in synch with tape by using the front panel of your library.
the current state of the library
<library>.
2402 The <element type> <element On the Libraries tab in the Management task area,
2 name> did not contain a tape select the <library type> <library> and click Inventory
when DPM expected it to. library in the Actions pane.
DPM might not be in synch
with the state of the <library
type> <library>
2402 The library <library> mandates 1) Remove the tape in the slot <slot name> by using
3 that when a tape is the front panel of your library.
dismounted, it should be 2) On the Libraries tab in the Management task area,
moved back to the slot it was click Inventory library in order to run inventory
originally mounted from.
However, the slot <slot name>
is not empty.
2402 A library with the same name
4 is already attached to this
server.
157
Please choose a different
name for the library.
2402 The operation cannot be
5 performed on <library type>
<library> because it does not
have any I/E ports.
2402 Operation cannot be Close and reopen DPM Administrator Console to
6 performed because DPM synchronize it with the actual state of the library.
Administrator Console is not
synchronized with the actual
state of the library.
2402 Operation failed since the slot Use the front panel of your library to move the tape
7 <slot name> in library from its current location to the slot specified above.
<library> was empty. This tape
is currently present in <media
location type> <media location
information>
2405 Operation cannot be
4 performed on the tape in
<media location type> <media
location information> because
it is a cleaning tape.
2402 Tape erase operation was
9 skipped because <library
type> <library> does not
support tape erase.
2403 DPM was unable to recatalog On the Libraries tab in the Management task area, click
1 the tape in <media location Inventory library. Then, select the tape <media label>
type> <media location and click Identify unknown tape.
information> in <library type>
<library> because this tape
has not been identified.
2403 DPM could not reserve the I/E Ensure that there are no pending alerts for the library.
4 port resource because one of Also check whether I/E port slots have been left open; if
required resources is not yes, close the I/E port slots.
accessible.
2403 The operation failed because Retry this operation after the I/E port is free.
6 the I/E port is currently in use.
2403 DPM failed to erase the Run a detailed inventory and a fast inventory.
7 selected tape because the
state of the <library type>
<library> as seen by DPM is
inconsistent with the actual
2403 The barcode on the tape 1. If the barcode of this tape has been changed, then
8 <media label> in <media click the link below to fix this issue. Refresh barcode on
158
location type> <media location tape <- this is a link to delete older barcode and set the
information> appears to have current as the actual barcode. 2. If this tape is a copy of
changed since the last time it a DPM tape created by external tool, erase this tape
was inventoried in DPM. before using it. To erase this tape and resolve this
issue, click the link below. Erase tape and refresh
barcode state <- this is a link
2403 Duplicate barcodes detected 1. Remove the tapes from the library. 2. Clear duplicate
9 on tapes with labels <media barcode information from DPM. <- this is a link. 3.
label> and <media label> Replace the barcodes on the tapes and insert them
back in library. 4. Inventory the library. <- this is a link to
run FI +DI
2404 DPM failed to recatalog the On the Library tab in the Management task area, click
0 imported tape <media label> Inventory library. Select the option to perform a detailed
because it has not been inventory.
inventoried
2404 DPM failed to recatalog the DPM can only recatalog a tape that has valid data on it.
1 imported tape <media label>
because the tape is blank.
2404 DPM failed to recatalog the It is likely that your data spans multiple tapes and the
2 imported tapes because they catalog information is present on another tape. Insert
do not contain the catalog all tapes associated with the backup and retry the
information. operation.
2405 Failed to perform the operation Add tape to the library, or to the drive in the case of a
0 since the tape <media label> stand-alone tape drive. Retry the operation after adding
is not available in <library tape.
type> <library>
2405 Required tape resource Wait for the other task to complete, or cancel the
1 <media label> is reserved by ongoing operation. Retry the operation.
another task.
2405 DPM could not reserve the 1) View and resolve all alerts for the library and its
2 drive resource because one of drive(s). Retry the operation after resolving the alerts.
required drive resources is not 2) Go to the Library tab in the Management pane and
online or it needs cleaning or click Rescan. Once the rescan operation has
servicing. completed successfully, retry the operation.
2405 Required drive resource is View and resolve all alerts for the library and drive, or
3 reserved by another task. wait for other operations to complete. Retry the
operation after resolving the alerts.
2405 Operation failed because no 1) On the Alerts tab in the Monitoring task area, resolve
5 usable drives were available in all alerts for this library and its drive. Retry this
<library type> <library>. Either operation after resolving the alerts.
no drive is online or all the 2) If you have some drives which are functioning
drives) need cleaning or correctly but are currently being used, wait for the other
servicing. operations to complete and then retry this operation.
2406 Unexpected tape detected in Check to see if there are any active alerts indicating
1 <media location type> <media suspect tapes. If such an alert exists, take the
159
location information> in appropriate recommended action and then retry this
<library type> <library> job.
2405 <library type> <library> has 1) If this library is associated with an active protection
6 been disabled by the DPM group, modify the protection group to associate it with
administrator another library to prevent tape-related jobs from failing.
2) If you want to use this library for your tape-related
jobs, on the Libraries tab in the Management task area,
select this library, and then click Enable library in the
Actions pane.
2406 Some certificates under Retry the job.
0 DPMBackupStore have
changed since the start of the
job.
2407 DPMBackupStore or Recreate DPMBackupStore and DPMRestoreStore
2 DPMRestoreStore is not Certificate stores using the Certificate Management
present. console.
2407 No certificate is present under Add certificates to the DPM backup certificates
3 DPMBackupStore. collection.
See "How to Encrypt Data in a Protection Group " in
DPM Help for more information about certificates.
2407 Failed to encrypt data on tape Retry the job
4
2407 Certificates on tape are
5 corrupt. Data on this tape
cannot be recovered.
2405 DPM failed to create a copy of 1) Retry the failed tape backup job using the alert in the
7 the tape backup for <data Monitoring task area.
source type> <data source 2) If your copy failed because the tape backup job did
name> on <server name> not run at all, in the Protection task area, click Create
because the tape backup recovery point - tape to create a short-term tape
failed or did not run. backup.
3) After successfully running the tape backup, retry the
failed copy job using the alert in the Monitoring task
area.
2405 The certificate <certificate 1) If this certificate contains a private key, move this
8 name> with serial number certificate to the DPM recovery certificates collection for
<certificate serial number> recovering data in the future, and replace this certificate
issued by <certificate issuer> with a valid certificate in the DPM backup certificates
will expire by <expiration collection to continue further backups.
date>. All encrypted backup 2) If this certificate does not contain a private key,
jobs will fail after this time replace this certificate with a valid certificate in the
DPM backup certificates collection to continue further
backups.
160
2405 The certificate <certificate 1) If this certificate contains a private key, move this
9 name> with serial number certificate to the DPM recovery certificates collection for
<certificate serial number> recovering data in future, and replace this certificate
issued by <certificate issuer> with a valid certificate in the DPM backup certificates
will expire by <expiration collection to continue further backups.
date>. All encrypted backup 2) If this certificate does not contain a private key,
jobs will fail after this time replace this certificate with a valid certificate in the
backups.
2407 Some of the certificates under 1) If this certificate contains a private key, move this
0 DPMBackupStore have certificate to the DPM recovery certificates collection for
expired 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
backups.
2407 This DPM server is not 1) Make sure that DPMBackupStore has the certificate
1 authorized to read or write to to decrypt this tape.
this encrypted tape because 2)Use this tape on a DPM server which is authorized to
there is no valid certificate in read this tape.
DPMBackupStore and
DPMRestoreStore which can
decrypt data.
2407 The command sent by DPM to Retry the operation.
6 the library agent timed out.
2407 DPM failed to mount the tape On the Library tab in the Management task area, select
7 <media label> in drive <drive the library and then click Inventory library. If enabled,
name> for the library <library>. select the option to run Fast inventory; otherwise, run
This is because DPM is not Detailed inventory.
synchronized with the current
2408 DPM failed to dismount the On the Library tab in the Management task area, select
6 tape <media label> in drive the library and then click Inventory library. If enabled,
<drive name> for the library select the option to run Fast inventory; otherwise, run
<library>. This is because Detailed inventory.
DPM is not synchronized with
the current state of the library.
2407 No certificate with private key In the Certificate Management console, open certificate
8 is present in DPMBackupStore stores for the Computer account on the DPM server.
Add a certificate which has the private key to the
DPMBackupStore certificates collection.
161
2407 DPM encountered an error Retry the operation.
9 while attempting to parse the
tape catalog information for
tape <media label>.
2408 DPM failed to perform the
2 operation since the specified
recovery point does not exist
2500 Rescan cannot be performed Please wait for the current library operations to
1 at this moment because DPM complete and then retry this operation
is performing other operations
on the <library type> <library>.
2501 DPM failed to inventory the Refer to your hardware manual for troubleshooting
1 <library type> <library>. This is steps.
possibly due to a hardware
issue.
2408 DPM encountered a critical 1) Check if you have another copy of this tape. If a
0 error while trying to parse the copy is available, use that to retry the recovery.
contents of the tape <media 2) If you do not have another copy of this tape, then
label>. This may be because open the Recovery task area and select all required
the data on this tape is individual recoverable items and perform the recovery.
corrupt.
2408 The tape in <library type> Go to the Libraries tab in the Management pane, select
4 <library> at <media location the tape, and click Erase tape to erase the content of
type> <media location this tape. After erasing this tape, DPM will be able to
information> has been written use it for backups.
to by some other tape backup
application by using an
unsupported physical block
size . DPM only supports a
physical block size between
1024 bytes and 65536 bytes
and hence will not be able to
read or overwrite the contents
of this tape.
2408 Recovery failed for <data Use your SAN software to take hardware snapshots of
3 source type> <data source the DPM replica and recovery point volumes and mount
name> on <server name>. them on the protected computer
Hardware snapshots of the
DPM replica and recovery
point volumes are not
mounted on the protected
computer for SAN recovery
2500 The tape in <library type> On the Libraries tab in the Management task area,
2 <library> at <media location select this tape and click Mark as cleaning tape
type> <media location
162
information> appears to be a
cleaning tape. However, this
tape is not marked as a
cleaning tape.
2500 The cleaning operation for 1) If supported, check the front panel of your library to
5 drive <drive name> on library verify that this cleaning operation completed
<library> took longer than successfully.
expected. The cleaning 2) If the cleaning operation failed, try changing the
operation may have failed. cleaning tape and run the cleaning job again.
2500 DPM is not synchronized with On the Libraries tab in the Management task area, click
9 the current state of your Inventory library. If available, select the option to
library. Jobs running on the perform a fast inventory, otherwise, perform a detailed
<library type> <library> can inventory.
potentially fail.
2501 DPM tried to access <element 1) On the Libraries tab in the Management task area,
0 type> <element name> on click Inventory library in order to run inventory. If
library <library>. This enabled, select the option to run Fast inventory,
<element type> does not exist. otherwise run Detailed inventory. This will update the
library state as seen by DPM.
2) Retry your failed operation after DPM has completed
the inventory successfully.
2501 DPM is not synchronized with On the Libraries tab in the Management task area, click
2 the current state of your Inventory library. If available, select the option to
library. Jobs running on the perform a fast inventory, otherwise, perform a detailed
<library type> <library> can inventory.
potentially fail.
2501 DPM detected that the drive Check the SCSI and bus mappings of the drive to
3 <drive name> does not appear ensure that the drive is mapped correctly. If you change
to be installed correctly. any of the mappings, open the Libraries tab in the
Management task area and click Rescan.
2501 <library type> <library> is not 1) Check if the library is turned on.
4 ready. 2) Check for loose connections on data or power
channels.
3) Make sure that the library is visible in Device
Manager.
4) Check to see that the door on the library is closed
5) Refer to your hardware manual for other
troubleshooting steps.
2501 Drive <drive name> was 1) Check that the drive is powered on.
5 detected as not ready. 2) Check if the drive is being serviced. If yes, you can
ignore this alert.
3) Check if the drive is connected properly.
163
2501 DPM failed to use the tape in Check if the tape in slot <media location type> <media
6 <media location type> <media location information> is a cleaning tape. If yes, on the
location information> because Libraries tab in the Management task area, select this
it appears to be a cleaning tape and click Mark as cleaning tape in the Actions
tape that is identified pane.
incorrectly as a backup tape.
2501 DPM could not access a drive Determine if some other application is using the drive
7 <drive name> since some and stop it.
other application is currently
using it.
2510 DPM encountered an error 1) Turn off the library <library>, and then turn it on and
0 while attempting to control the retry the operation.
autoloader on library <library> 2) Examine the front panel of your library to see if any
errors are being reported by your library.
2510 DPM encountered an error 1) Use the tape <media label> in a different drive. To do
1 while attempting to use tape this, first disable the drive <drive name>. Select this
<media label> on the drive tape and click ‘Identify unknown tape’. If this operation
<drive name>. This could be a fails, it indicates a potential problem with your tape.
problem with your drive or 2) Use the tape <media label> in a different library.
tape. Load the tape in the other library, select this tape, and
click 'Identify unknown tape'. If this operation fails, it
indicates a potential problem with your tape.
3) If either of the above action resulted in the tape
operation succeeding, it indicates a potential issue with
your drive <drive name>.
2510 DPM attempted to move a 1) On the Libraries tab in the Management task area,
2 tape to <element type> select the library <library> and click 'Inventory' in the
<element name> but this Actions pane.
<element type> was occupied. 2) If the <element type> contains a tape, remove the
DPM may not be in synch with tape by using the front panel of your library.
the current state of the library
<library>
2510 Tape drives or library devices On the Libraries tab in the Management task area, click
5 may have been disconnected 'Rescan' in the Actions pane.
or reconnected on the DPM
server.
2510 <library type> <library> is 1) Check if the <library type> <library> is turned on.
6 either turned off or has been 2) Check for loose data or power channel connections.
disconnected
3) Make sure the library is visible in Device Manager.
2510 Drive <drive name> requires Drive <drive name> will be automatically cleaned by
7 cleaning. The drive will not be DPM. If you are seeing this error frequently, please
164
used for further operations service the drive.
until it has been cleaned.
2510 The library <library> requires Use the front panel of the library <library> to move the
8 all drives to be empty in order tape from the drive <drive name> to an empty slot
to lock or unlock the door.
However, the drive <drive
name> has a tape in it.
2510 Tape might not be properly 1) Check to see if the tape has been inserted correctly
9 inserted in the stand-alone into the drive.
drive or the stand-alone drive 2) Check to see that the drive is ready and operational.
is not ready.
2512 The operation failed because Use the front panel of the library to close the I/E port.
3 the insert/eject (I/E) port of the
library <library> is open.
2512 Rescan failed because the In Device Manager, check to see that the drivers for the
4 tape drive or library hardware tape drive or library hardware are installed correctly.
does not seem to have been
set up correctly.
2512 DPM was unable to use 1) Determine if any other process on the DPM server is
5 <formatted device name value currently using the library. If this is the case, stop the
pairs> since this was being process.
used by some other process. 2) Check to see that your library is powered up and
functional
2512 Failed to obtain drive mapping Refer to the DPM 2010 Operations Guide for
6 information from the file instructions on modifying the DPMLA.xml to correctly
DPMLA.xml. The information represent your current library configuration.
in this file is not formatted
correctly.
3000 After a tape mount operation, Update the library state by performing an inventory, and
2 no tape is found in the drive or then retry the operation. On the Libraries tab in the
the tape in drive has changed. Management task area, click Inventory library.
3000 DPM failed to recatalog the If you have another copy of this tape, use that instead
8 contents of the tape <media for the re-catalog operation. If this is the only copy of
label> because it encountered the tape and you want to recover as much data as is
a critical error while attempting possible, on the Libraries tab in the Management task
to read catalog information area, select this tape, click View contents, and copy the
from this tape. This may be contents of this tape to disk.
because the tape data is
corrupt.
3001 The specified recovery point Increase the disk allocation space for the recovery
5 does not exist point volume, or delete old recovery points by using the
Remove-RecoveryPoint cmdlet. For information about
deleting recovery points, open DPM Management Shell
and run "Get-Help Remove-RecoveryPoint -detailed".
If you are using custom replica and recovery point
volumes, such as in the case of a SAN, you cannot
165
modify the disk space allocated by using DPM. In these
cases, identify the volume that corresponds to the
recovery point volume for the data source from the
“Modify disk allocation” dialog box. Then, open Disk
Management, right-click the custom volume, and then
select “Extend Volume".
3001 Errors occurred while taking a Retry the operation. If it fails consistently, remove the
2 VSS snapshot of volume(s). protected data from the protection group and reprotect
it again.
3002 A critical inconsistency was Click Modify Protection Group to validate exclusion or
4 detected, therefore changes inclusion filters for the data source. After the protection
cannot be replicated. group is modified, click the link below to run a
synchronization job with consistency check.
3002 One or more databases in the On the Exchange Server, verify the cause of failure
5 storage group failed to mount from event logs entries.
3002 One or more databases in On the Exchange Server, verify the cause of failure
6 storage group failed to from event logs entries.
dismount
3015 DPM is unable to continue
6 protection for <data source
name> on <server name>
because the change tracking
information is corrupt
name> on server <server
name> since the change
tracking information is corrupt
3002 Eseutil.exe failed to apply logs Retry the operation. If the problem persists, the
9 on database files to bring the recovery point may be corrupt. Retry recovery from
database to a clean shutdown another recovery point.
state.
3003 SIS is not enabled on the Enable SIS for the server.
0 server.
3003 The volume is no longer Make sure the volumes are online and mounted.
3 available - it may be
dismounted or offline
3003 DPM was unable to determine Re-run the job.
7 the last known backup tracking
information for this data
source.
3003 The change journal is corrupt Delete the change journal by running "fsutil usn
8 due to bad sectors on the disk. deletejournal" [see command usage for more
information] at a command prompt. Click the
recommended action link below to perform a
166
consistency check.
3004 At least one of the databases Ensure that all databases in the storage group are
5 is not online online, and then retry the job.
3004 Protection agent is unable to Run synchronization with consistent check.
6 synchronize the replica.
3005 Overwrite database' flag is not On the Exchange server, set the 'Overwrite database'
1 set for one or more databases flag and retry the operation.
being recovered
3007 The volume for one of the
5 specified database file
locations does not exist.
Check to see that the volumes
for all file locations specified
are available on the
destination SQL server
3007 Operation failed for <data 1) If your recovery point volume is offline, bring it online
6 source name> on <server and then run consistency check for the affected data
name> because the recovery sources.
point volume for this data 2) If your recovery point volume is not available to bring
source is not available on the online, remove the affected members from protection
DPM server. Future backups and re-protect them. When stopping protection for the
will also fail until this issue is affected members, select the option to delete the
fixed. replica on disk.
3007 DPM has run out of free space 1) Increase the space allocated for the recovery point
7 on the recovery point volume volume for <data source name>. We recommended
for <data source name> on that you increase the space by at least 25 percent more
<server name>. Protection for than the current allocation.
this data source will fail in 2) Run consistency check after increasing the space for
order to prevent existing the recovery point volume.
recovery points from being
deleted before their expiration.
3007 Operation failed for <data 1) Rerun the consistency check and see if it resolves
8 source name> on <server this issue.
name> due to a VSS error on 2) Check to see if your disks are connected properly to
the DPM server. Future the DPM server. If there are any disk cabling issues,
backups are also likely to fail rectify them and then run consistency check.
until this issue is fixed.
3) If you are certain that you do not have any disk
cabling issues, clear the VSS fault. Next, run chkdsk on
<volume name> and finally run consistency check.
3010 DPM has detected that some Open the DPM Management Shell and run .\Delete-
0 other application has created Shadowcopy.ps1 "<volume name>" to delete the
recovery points on the externally created recovery points on the recovery point
recovery point volume for volume.
<data source name> for server
<server name>. Future
backups will fail until these
167
recovery point are deleted.
3008 Operation failed for <data 1) Rerun the consistency check and see if it resolves
3 source name> on <server this issue.
name> due to a VSS error on 2) If running consistency check does not resolve this
the DPM server. issue, increase the page file size on the DPM server
and then run the consistency check job.
3008 Operation failed for <data Rerun the consistency check.
4 source name> on <server
name> due to a VSS error on
the DPM server.
3008 Operation failed for <agent Check the Event Viewer entries to figure out the cause.
5 protected server> as the Retry the operation after fixing the problem.
system ran out of memory.
3008 DPM has detected a Retry the operation. If the problem persists, contact
7 checksum mismatch during your network administrator to diagnose possible
data transfer over the network network issues.
3010 DPM encountered a critical Retry the operation. If the problem occurs again,
1 error while performing an I/O contact your hardware vendor to get your hardware
operation on the tape in serviced.
<media location type> <media
location information>.
3010 There was an unrecoverable Retry the operation with another tape, or try restoring
2 error during I/O operations on partial data from backup.
the drive.
3010 After a tape mount operation, Update the library state by performing an inventory, and
3 no tape is found in the drive or then retry the operation. On the Libraries tab in the
the tape in drive has changed. Management task area, click Inventory library.
3010 DPM failed to write to tape Remove the write protection from the tape and retry the
4 because the tape is write- operation.
protected. The tape may be in
(drive-name/slot id)
3010 The tape and the drive type Check that the tape and the drive type are compatible,
5 may not be compatible. and the drive is supported. Also check if the drive
firmware needs an upgrade.
3010 RA cannot read from/write to DPM will recreate the temp area with appropriate
7 temp area. permissions
3011 DPM has encountered a Retry the operation.
0 critical internal error. (Critical
error in reading/parsing
DirsAndFileOffsetFileList)
3010 No more space left in Temp 1) Create a folder called 'temp' under the DPM
6 storage volume. installation path on the DPM server (by default this path
would be "(Program Files)\Microsoft Data Protection
Manager\DPM".
168
2) Share this folder out as a share called "temp".
3) Give the local system account on the DPM server
Full Control permissions on this folder.
3010 Either the tape <media label> Use another copy of the tape and retry the operation.
8 has corrupt data or this is not You can view the contents of the tape to confirm that it
the right tape. contains the expected data.
3010 DPM failed to recatalog the If you have another copy of this tape, use that instead
9 contents of the tape because it for the recatalog operation. If this is the only copy of the
encountered a critical error tape and you want to recover as much data as
while attempting to read possible, then select this tape on the Libraries tab in
catalog information from this the Management task area, click View contents, and
tape. This may be because the copy the contents of this tape to disk.
tape data is corrupt.
3011 The VSS application writer or Please check that the Event Service and the VSS
1 the VSS provider is in a bad service are running, and check for errors associated
state. Either it was already in a with these services in the Application Event Log on the
bad state or it entered a bad server <server name>. Please allow 10 minutes for
state during the current VSS to repair itself and then retry the operation.
operation.
3011 DPM encountered a retryable Check the Application Event Log on <server name> for
2 VSS error. the cause of the failure. Fix the cause and retry the
operation.
3030 Synchronization for replica of Review the application event log on the protected
0 <data source name> on computer for errors from the DPM writer service. Take
<server name> failed because appropriate action and retry the operation.
the replica is not in a valid
state or is in an inactive state.
3011 DPM encountered an error Retry the operation.
3 while trying to create a
recovery point for one or more
volumes for data source <data
name>. This may have
happened because the volume
name is no longer valid.
3011 No VSS provider supports one Please stop protection for this volume and any data
4 or more volumes for data sources that are hosted on this volume.
source <data source name>
on <server name>, therefore
DPM cannot create recovery
points for these volumes.
3011 DPM failed to synchronize Retry the operation at a later point when the churn is
5 changes for <data source expected to be lower.
<server name> because the
snapshot volume did not have
169
sufficient storage space to
hold the churn on the
protected computer
3011 The change journal ID may
9 have changed since the last
synchronization. DPM is
unable to track changes on
this computer.
3012 DPM failed to recover all the Recover to an alternate location or try recovering from
0 files. another recovery point.
3011 VSS has deleted a shadow Increase the space allocated for the VSS diff area of
6 copy since it has probably run volumes involved in protection on this server.
out of disk space on the server
<server name>.
3011 A journal wrap error has 1) Click the link below to run synchronization with
7 occurred on the change consistency check.
journal, and therefore DPM is 2) If the problem persists, you can increase the change
unable to track any more journal size or configure the current protection group to
changes or may have missed synchronize more often. To change the synchronization
some changes for the data schedule, select the protection group in the Protection
source <data source name> task area, and in the Actions pane, click Modify
on <server name>. protection group. To change the change journal size,
click Modify disk allocation, select the Protected Server
tab, click Modify, and then change the space allocated.
3014 DPM cannot continue
cluster <virtual server name>
because this cluster
experienced an unexpected
failover.
3011 Change journal not initialized 1) Click the "Modify protection group for this data
8 or is the wrong size source..." link below to configure change journal size.
On the Disk Allocation page, select the Protected
Server tab and click Modify, then change the space
allocated.
2) After the protection group is modified, click the link
below to run a synchronization job with consistency
check.
3012 File copy failed. The directory Please make sure that the source and target locations
1 for source location <source are correct and have appropriate permissions.
location> or destination
location <destination location>
does not exist.
(<message>)
Exception trace:
170
<exception message>
3012 File copy failed. The source Please make sure that the source and target locations
2 location <source location> are correct and have appropriate permissions.
does not exist.
(<message>)
Exception trace :
<exception message>
3012 File copy failed due to an I/O Please make sure that the source and destination
3 error. locations exist and have full control permissions for the
Source location: <source local system account.
location>
Destination location:
<destination location>.
(<message>)
Exception trace :<exception
message>
3012 Catalog for backup job was Retry the operation.
4 not built correctly for <data
3012 Another backup job of <data Please wait for the earlier backup job to finish, and then
5 source name> on <server retry the backup. Or, you can cancel the current job,
name> is in progress. and then retry the backup job.
3012 Backup of <data source On the Jobs tab in the Monitoring task area, check for
6 name> on <server name> failures of synchronization jobs and resolve those.
cannot be completed. DPM Next, create a valid recovery point and then run the
could not find a valid recovery backup to tape job again. To create a valid recovery
point on disk. point:
1) For application data, in the Protection task area, click
Create recovery point, and then select Express full
backup on disk.
2) For file data, in the Protection task area, click Create
recovery point and then select Create a recovery point
after synchronizing.
3012 Operation failed due to an Retry the operation.
7 internal error
3012 Invalid backup type specified If you are backing up to tape, perform a full backup. If
8 for <data source name> on you are backing up to disk, perform an express full
<server name>. backup.
3012 DPM failed to generate the file On the Libraries tab in the Management task area,
9 list to complete the task. select the tape and then click View Contents in the
Actions pane.
3013 DPM failed to start tracking Verify that you do not have more than 100 protectable
0 changes for <data source data sources on a single volume. If this is the case,
171
type> <data source name> on check to see if you can split your data source across
<server name> because of more volumes.
insufficient memory resources
3015 DPM is attempting to back up Enable SIS on the computer by using Add/Remove
0 or restore a SIS link file, which Windows Components in Add or Remove Programs.
requires SIS to be enabled on
<server name>.
2 protecting <data source
because the volume on which
this data resides on has been
resized.
3015 DPM encountered an
4 unknown error while tracking
changes for <data source
because this computer has
been powered off without
shutting it down cleanly.
3013 The replica is inconsistent for No action required.
9 <data source type> <data
name> due to a CCR failover.
A synchronization job with
consistency check will be
automatically triggered after
30 minutes.
3014 Database mount failed for Please contact the exchange admin. Verify the cause of
3 <data source type> <data failure from event logs entries on the exchange server.
name>.
3014 Database dismount failed for On the Exchange server, verify the cause of failure
4 <data source type> <data from event logs entries.
name>.
3013 DPM is not synchronized with Check to see if you are protecting a clustered resource
1 the changes on <data source which has undergone a dirty failover. In this case, DPM
type> <data source name> on requires a synchronization with consistency check
<server name>. Protection before it can continue protection.
cannot continue.
3013 DPM skipped the Wait for the next scheduled backup job to trigger for
2 synchronization job for <data protection to continue. Alternately you can manually
172
source type> <data source trigger a backup job in the Protection task area by
name> on <server name> selecting this data source and then clicking Create
because it detected an recovery point - Disk.
unexpected backup state.
3013 A critical inconsistency was In the Protection task area, click Modify Protection
3 detected for <data source Group to validate exclusion and inclusion filters for the
type> <data source name> on data source. If modifying the protection group does not
<server name> and therefore start a consistency check, run a synchronization with
changes cannot be replicated consistency check.
for <file name>.
3013 DPM failed to clean up data of This may happen if the replica volume is being
4 old incremental backups on accessed from outside of DPM. Please see the detailed
the replica for <data source error, resolve the issue with respect to the replica
type> <data source name> on volume path, and retry the job. Otherwise, DPM will
<server name>. synchronize with the changes during the next
Synchronization will fail until scheduled synchronization job.
the replica cleanup succeeds.
3013 The replica of <data source In the Protection task area, click Modify Protection
5 type> <data source name> on Group to update the configuration information for the
<server name> is not data source on the DPM server and to increase the
consistent with the protected replica volume size if necessary. If modifying the
data source. protection group does not start a consistency check,
DPM has detected changes in run a synchronization with consistency check.
file locations or volume
configurations of protected
objects since the data source
was configured for protection.
DPM detected that some run a synchronization with consistency check.
protected objects are missing
since it was configured for
protection.
DPM detected new protectable run a synchronization with consistency check.
objects for the data source
protection.
173
DPM detected changes in run a synchronization with consistency check.
existing protected objects and
detected new protectable
objects for the data source
protection.
3030 The replica of <data source 1) Check to see if some SQL databases have been
1 type> <data source name> on added to the protected SharePoint farm. If this is the
<server name> is not case, go to the protection pane and select the option to
consistent with the protected Modify Protected Group. Go through the wizard without
data source. making any changes.
2) If no SQL databases have been added to the farm,
check to see if any of the SQL data bases belonging to
this farm is already protected as a SQL data source by
DPM. If this is the case, then go to the protection pane
and stop protecting this SQL database with the option
to delete the replica. After this is done, recreate
protection for this SharePoint farm.
3) If neither of the earlier options are valid, check to see
if your SQL writer is running correctly on the backend
nodes of your protected SharePoint farm. If the writer is
not a healthy state, restart the writer.
3030 The replica of <data source Check to see if some SQL databases have been
2 type> <data source name> on removed from the protected SharePoint farm. If this is
<server name> is not the case, go to the protection pane and stop protecting
consistent with the protected this farm with the option to retain current data backups.
data source. Then, recreate protection for this SharePoint farm.
3030 DPM failed to backup <data 1) Check to see if some SQL databases have been
3 source type> <data source added to/or removed from the protected SharePoint
name> on <server name> to farm. If this is the case, go to the protection pane and
tape. stop protecting this farm with the option to retain
current data backups. Then, recreate protection for this
SharePoint farm.
2) Check to see if any of the SQL data bases belonging
to this farm is already protected as a SQL data source
by DPM. If this is the case, then go to the protection
pane and stop protecting this SQL database with the
option to delete the replica. After this is done, recreate
protection for this SharePoint farm.
3014 DPM tried to do a SQL log If you see this failure as part of a backup job, then in
0 backup, either as part of a the Protection task area, select the SQL Server
backup job or a recovery to database and click Create recovery point. Choose
latest point in time job. The express full backup. Alternately, you can wait for the
SQL log backup job has next scheduled express full backup to run.
detected a discontinuity in the If this failure occurs as part of a recovery job, then try to
174
SQL log chain for <data recover from another point in time.
source type> database <data Review the Application Event Viewer logs on the
source name> since the last computer running SQL Server for more details.
backup. All incremental
backup jobs will fail until an
express full backup runs.
3018 The protection agent on Enable the protection agent on the protected computer
6 <server name> is disabled. in DPM Administrator Console, in the Management task
area, on the Agents tab.
3102 Cannot run an incremental
4 synchronization and create a
recovery point for <data
source name> because the
application does not support it.
3014 To recover <data source type> Please check that the SQL Server service on the
1 <data source name> on protected computer can be sent the start command
<server name>, DPM must successfully. After you ensure that the service can be
stop and start the SQL Server successfully started, retry the recovery. If this error
service on <server name>. occurs again, try to recover the master database from
After stopping the service, another recovery point.
DPM was unable to
successfully start the service.
3014 To recover <data source type> Please check that the SQL Server service on the
2 <data source name> on protected computer can be sent the stop command
<server name>, DPM must successfully. After you ensure that the service can be
stop and start the SQL Server successfully stopped, retry the recovery.
service on <server name>.
DPM was unable to
successfully stop the service.
3014 Data consistency verification Either the database files are corrupt or the proper
6 check failed for <object name> versions of the following files are missing.
of <data source type> <data If you have recently upgraded your Exchange server,
source name> on <server please copy them from that server to DPM server.
name>.
eseutil.exe
ese.dll
Contact the administrator for Exchange server, and
verify the issue. You can recover the last known good
backup to address the corrupted state.
3014 Eseutil.exe failed to apply logs Please contact the Exchange administrator. Event logs
7 on database files for <data on the above server may help resolve the issue. If the
source type> <data source problem persists, the recovery point may be corrupt.
name> on <server name> to Retry recovery from another recovery point.
bring the database to a clean
shutdown state.
3014 DPM was unable to access Verify that the cluster resource group <virtual server
8 the cluster resource group name> is accessible by using the Cluster
175
<virtual server name> for Administration console.
<data source name> of
protection group <protection
group>
3015 DPM failed to read its change
1 tracking information for <data
name>.
3015 The file system on <server Make sure the volumes are online and that the file
3 name> on which data source system is in a consistent state.
<data source name> of
protection group <protection
group> resides, is in an invalid
state and it is no longer
available.
3015 The alias of the user to which Please specify an alias which is offline and not
7 DPM has to connect the connected to any Exchange server.
recovered mail box is online
and connected to an
Exchange server.
3015 Verification failed for the tape Retry the tape backup and then retry verification.
8 backup of <data source type>
<server name> because the
tape backup failed.
experienced a failover.
3016 DPM failed to perform the tape Retry the tape backup job.
0 backup for <data source type>
experienced a failover.
3016 DPM is unable to determine Retry the operation. If the replica has been marked
1 tracking information for <data inconsistent, run a consistency check on this data
source type> <data source source.
3016 Protection cannot continue Delete the change journal on the protected computer
2 because the change journal by using the FsUtil.exe tool and recreate the change
used for tracking changes for journal. Next, run a consistency check on the data
<data source type> <data source.
name> is corrupt due to bad
176
sectors on the disk.
3016 The path to the SQL DPM creates the temporary folder in the same location
3 temporary folder for <data as the SQL database log file. The temporary folder
source type> <data source name is 'DPM_SQL_PROTECT'.
name> on <server name> is To fix this issue:
too long. This can cause
1) Change the location of the database log file so that
backup or recovery jobs to fail.
its physical path is as short as possible.
2) Run a consistency check job for this database.
3103 No library has been specified
0 for protection.
3103 Protection for <protection
1 group> has been set only to
tape.
3016 The backup job failed because Bring all databases in the storage group online and
7 DPM detected that some retry.
databases of the Exchange
Server Storage Group
instance <data source name>
on <server name> are offline.
3016 The <data source type> <data 1) Check that the database is online.
4 source name> on <server 2) Check that the database is not in a restoring state.
name> is not available
3) Verify that the database has not been deleted.
4) Make sure that the database is accessible.
3016 The backup job failed because Please stop protection for all databases that belong to
5 DPM detected that the <data this instance (with the ‘Retain protected data' option),
source name> instance of and reconfigure protection for the databases in a new
SQL Server 2000 on <server protection group. This will allow you to continue
name> has been upgraded to protection for the databases while still retaining old
SQL 2005. backups for recovery.
3016 DPM detected that the Ensure that all the disks added to the DPM storage
6 recovery point volume for pool are online.
source name> is not available
on the DPM server. Protection
jobs will fail until the recovery
point volume is brought online.
3016 Full backup is required for In the Protection task area, click 'Create recovery point-
8 <data source type> <data disk' and select 'Create a recovery point by using
source name> on <server express full backup'.
name> as <service name>
service has been restarted.
3016 The operation failed for <data 1) Check that the data source is online.
9 source type> <data source 2) Check that the data source is not in a restoring state.
3) Verify that the application writer is running.
because the data source is not
177
available. 4) Make sure that the data source is accessible.
5. Verify that the data source is not missing.
3017 The recovery to the latest Check the Application Event Viewer logs on the SQL
0 point in time failed. During a Server to find out why the tail log restore may have
recovery to the latest point in failed.
time, DPM tries to do a tail log You can do the following to fix the issue:
restore to apply the latest
1) Recovery to the latest point in time is not possible
changes on the SQL database
immediately after another recovery has been performed
on the same database. Allow a synchronization job to
<server name> at the end of
run before you attempt a recovery to the latest point in
the recovery. This tail log
time.
restore failed.
2) Choose an alternate point in time to recover to, if you
run into this problem repeatedly.
3017 The recovery to the latest Check the Application Event Viewer logs on the SQL
1 point in time has failed. During Server to find out why the SQL transaction log backup
a recovery to the latest point in may have failed.
time, DPM tries to do a SQL You can do the following to fix the issue:
transaction log backup to get
1) If the SQL log chain is broken, you will have to run a
the latest changes from the
full backup to re-initialize the log chain.
SQL database <data source
name> on <server name> 2) If the DPM replica for database is invalid, you will
before starting the recovery. have to run a consistency check operation for this
This transaction log backup database.
has failed. Choose an alternate point in time to recover to, if
transaction log backups cannot be successfully run
against database.
3017 The DPM job failed for <data This can happen if the SQL Server process is
2 source type> <data source overloaded, or running short of memory. Please ensure
name> on <server name> that you are able to successfully run transactions
because the SQL Server against the SQL database in question and then retry
instance refused a connection the failed job.
to the protection agent.
3017 Execution of SQL command Check the Application Event Viewer logs on the SQL
3 failed for <data source type> Server for entries posted by the SQL Server service to
<data source name> on find out why the SQL command may have failed. For
<server name>. more details, look at the SQL Server error logs.
3017 Recovery failed for <data On the Exchange Administrator Console, set the
4 source type> <data source 'Overwrite database' flags for the databases being
name> on <server name> recovered and retry the operation.
because the overwrite flag is
not set for <database name>.
3017 DPM failed to replicate Check to see that no application running on this
5 changes for <data source computer is malfunctioning to cause this high file
type> <data source name> on system activity. If you consistently run into this error, in
<server name> due to the high the Protection task area, click Modify disk allocation.
amount of file system activity On the Protected Computers tab, click Modify to
on this volume. increase the change journal size on the protected
178
computer.
3102 Recovery point cannot be
5 created on tape for data
because the protection for
<protection group> has been
set to disk.
3102 Protection for <protection
6 group> has been set only to
disk.
3102 <library type> <library> has
7 <total number> drives. You
cannot specify a value more
than that.
3017 File delete failed due to I/O Ensure that the file location is correct and that the file
6 error. File may be in use by has appropriate permissions.
some other application. File
location: <location>
3018 File delete failed because of Ensure that the file location is correct and that the file
3 unauthorized access error. File has appropriate permissions.
path: <location>
3018 DPM cannot continue 1) In the Monitoring task area, resolve the "Unable to
4 protection for <data source configure protection" alert for this data source.
type> <data source name> on 2) Click the link below to retry the job.
<server name>.
3018 Recovery for <data source In the Recovery task area, select the recovery point just
5 type> <data source name> to prior to the latest recovery point.
the latest recovery point
cannot be performed because
you have already recovered it
to a previous recovery point.
3018 Protection agent on <protected
7 server name> was
unexpectedly shut down
during synchronization. DPM
may have replicated data
partially for <data source
type> <data source name>.
3018 Recovery point for <data
8 source type> <data source
name> was created when the
replica was inconsistent.
Some data from this recovery
point may contain partially
synchronized data.
3018 The execution of the pre- Make sure that the pre-backup script does not have
179
9 backup script for <data source any errors and can execute successfully.
type> <data source name>
returned an error.
3019 The execution of the post- Make sure that the post-backup script does not have
0 backup script for <data source any errors and can execute successfully.
type> <data source name>
returned an error.
3019 The execution of the pre- Make sure that the pre-backup script finishes execution
1 backup script for <data source within the time specified, or increase the timeout
type> <data source name> period.
timed out.
3019 The execution of the post- Make sure that the post-backup script finishes
2 backup script for <data source execution within the time specified, or increase the
type> <data source name> timeout period.
timed out.
3019 The configuration of the pre- Make sure that the pre-backup script or post-backup
3 backup script or the post- script configuration XML file does not have any errors
backup script XML for <data and that the XML is well formed.
name> is incorrect.
3019 DPM cannot protect <data Enable case-sensitive support on the DPM server by
4 source name> on <server following the steps described in
name> because case- http://support.microsoft.com/default.aspx?scid=kb;EN-
sensitive support is not US;938455.
enabled on the DPM server.
3019 DPM has run out of free space 1) Increase the space allocated for the recovery point
5 on the recovery point volume volume for <data source name>.
and will fail synchronization for 2) Retry the operation after increasing the space for the
<data source name> on recovery point volume.
<server name> in order to
prevent existing recovery
points from being deleted.
3022 DPM failed to replicate the
1 changes for the <data source
type> <data source name>.
The operation failed while
DPM was attempting to apply
the changes to the replica.
3101 The parameter set that you
3 have specified is incorrect.
Specify only long-term tape
policy objective.
Specify only short- and long-
term tape policy objectives.
180
Specify only short-term disk
and long-term tape policy
objectives.
3101 Incremental synchronization
6 job cannot run on all the
protected items in this
protection group. Change the
synchronization frequency to
"Just before a recovery point".
3101 Long-term retention range can
7 be specified only in weeks,
months, or years.
3019 Recovery failed for <data Retry the operation and specify a recovery storage
7 source type> <data source group.
name> on <server name> as
the specified storage group is
not a recovery storage group.
3020 DPM has detected that the
9 cluster configuration has
changed for resource group
<virtual server name> and has
marked the replica
inconsistent.
3019 Recovery failed for <data Retry the operation and specify a storage group which
6 source type> <data source is not a recovery storage group, or select the Recover
name> on <server name> as to Recovery Storage Group option.
the specified storage group is
a recovery storage group.
3019 Recovery failed for <data Verify that the storage group or the database exists on
8 source type> <data source the Exchange server.
name> on <server name> as
the alternate storage group or
the database specified is
invalid.
3019 Recovery failed for <data Verify that the target database is in a dismounted state.
9 source type> <data source
because the target database
specified is in mounted state.
3020 Prepare for backup operation Please retry the operation.
0 for <data source type> <data
name> has been stopped
because this operation
depended on another backup
181
operation which failed or was
canceled.
3020 Prepare for recovery operation Please retry the operation.
1 for <data source type> <data
name> has been stopped
because this operation
depended on another recovery
operation which failed or was
canceled.
3020 The SQL temporary folder for DPM creates the temporary folder in the same location
2 <data source type> <data as the SQL database log file. The temporary folder
source name> on <server name is 'DPM_SQL_PROTECT'.
name> is not yet configured. DPM has not yet configured the temporary folder on
<server name>. In the Protection task area, create a
recovery point for this database.
3020 Replica for <data source type>
3 <data source name> on
<server name> is already
consistent. Scheduled
consistency check will not be
run on consistent replica.
3020 Replica writer is enabled for DPM requires the Replica writer to be disabled for
4 <data source type> <data protecting Exchange 2007 with LCR. Please disable
source name> on <server the replica writer by adding a DWORD value,
name> for Exchange 2007 EnableVssWriter, to the key
with LCR. 'HKLM\Software\Microsoft\Exchange\Replay\Parameter
s', setting the value to 0, and restarting the Microsoft
Exchange Replication Service. Then retry the
operation.
3020 Recovery failed for <data Provide an alternate name for the database to be
5 source type> <data source recovered. Ensure that no database with the name you
name> on <server name> have specified already exists on the SQL server.
because a database with the
name you specified already
exists on the SQL instance.
3020 DPM was unable to compile a
7 list of recoverable objects for
source name>. You will be
unable to perform detailed
level recoveries from this
recovery point. No action is
required because the next
scheduled full backup will
synchronize the list of
recoverable objects.
Alternately, in the Protection
182
task area, select the required
protected object, click 'Create
recovery point', and select the
option to create a recovery
point using a full backup.
3020 Data consistency check timed If the error has been reported for your Exchange
8 out for <object name> of <data server, it indicates that the Exchange server backup
source type> <data source files may be corrupt. Follow these steps to resolve the
name> on <server name>. issue:
1) Consult the Exchange server administrator to verify if
the databases and logs on the Exchange server are in
a good state.
2) If the database and logs on the Exchange server are
not corrupt, you need to run a synchronization with
consistency check for this data source.
3) In case the database and logs on the Exchange
server are corrupt, you can choose to recover the
Exchange data from the last known good backup.
3021 The execution of the pre- Check to see that the pre-snapshot step does not have
0 snapshot step returned an any errors and can execute successfully.
error.
3021 The execution of the pre- Check to see that the pre-snapshot step can
1 snapshot step timed out. successfully finish executing within the timeout period.
3021 The execution of the post- Check to see that the post-snapshot step does not
2 snapshot step returned an have any errors and can execute successfully.
error.
3021 The execution of the post- Check to see that the post-snapshot step can
3 snapshot step timed out. successfully finish executing within the timeout period.
3021 Failed to create the System Check the event log on the protected computer <server
4 State backup. name> and fix any errors reported.
3021 Failed to create the System Check the event log on the protected computer <server
5 State backup within the name> to determine why the backup timed out.
timeout period.
3021 DPM has detected a 1) Consult the administrator of the Exchange server to
6 discontinuity in the log chain rectify the problem. Please ensure that exchange
for <data source type> <data circular logging is turned off. Synchronization jobs may
source name> on <server continue to fail until this issue is resolved.
name> since the last 2) Last backup might have failed after log truncation.
synchronization.
In the Protection task area, click 'Create recovery point'
and select 'full backup' option.
3021 Operation failed because DPM Check the Application Event Log on <server name> for
8 encountered an unexpected the cause of the failure. Fix the cause and retry the
VSS error. operation.
3021 Cmdlet execution failed Please contact the exchange admin and resolve the
183
9 (<reason>) for <data source issue
<server name>.
3022 Activation of COM component Please make sure that the COM component
0 ExchangeCmdletWrapper ExchangeCmdletWrapper is configured appropriately.
failed on <server name>.
3100 Operation failed since the Ensure that Get-DatasourceDiskAllocation and Set-
0 protected data source size had DatasourceDiskAllocation are executed successfully
not been calculated for <data prior to running this operation.
source name> prior to running
this operation.
3101 Failed to create the protection Retry protection group creation by adding members.
0 group because no members
were selected for protection.
Specify only short-term disk
policy objective.
Specify only short-term tape
policy objective.
3100 Failed to create the protection
1 group since some of the
required schedules have not
been specified.
3100 Failed to create the protection Specify a library or stand-alone tape drive and then try
2 group because a library or to create the protection group.
stand-alone tape drive has not
been specified and tape
protection has been selected.
3100 Operation failed because Use the cluster management software to check to see if
3 <server name> is not the cluster resource group <server name> is online.
accessible from the DPM
server.
3100 Failed to enumerate resource 1. Verify that the Cluster service is running on the
4 groups on the cluster <server cluster <server name>
name>. 2. Verify that you can ping the cluster from the DPM
server.
3100 DPM cannot protect the On the Agents tab in the Management task area, install
5 cluster resource group on protection agents on all nodes that this resource group
<server name> because could fail over to.
protection agents are not
installed on all nodes that this
resource group could fail over
184
to.
3100 DPM cannot start the Create On to the Agents tab in the Management task area,
6 New Protection Group Wizard install protection agents on the computers that you
because there are no want to protect. After installing the agents successfully,
computers with protection start the Create New Protection Group Wizard.
agents installed.
3100 This item cannot be protected Click Help to view the list of prerequisite software for
8 because some prerequisite the selected item.
software is missing. Ensure
that all prerequisite software is
installed and then protect this
item.
3100 Modify Protection Group is Stop protection of protected members on these clusters
9 disabled because the following before you modify the protection group.
network names have been
deleted: <input parameter
tag>.
3101 The specified retention range
8 supports the following backup
frequencies only: <input
parameter tag>.
3101 The item <protectable object>
9 does not exist in protection
group <protection group>.
3102 The item <protectable object>
0 cannot be excluded because it
is a data source.
1 created for external data
source <data source name>.
2 created for unprotected data
3 created on disk for data
because the protection for
<protection group> has been
set to tape.
3102 Data source <data source
8 name> does not belong to a
protection group.
3102 Data source <data source
9 name> has no inactive replica
on <media label>.
185
3103 Journal size cannot be set for
2 <data source name> because
this data source does not use
a change journal.
3103 Operation failed because the
3 recovery point specified for
deletion was created as part of
an incremental tape backup.
DPM can only delete recovery
points that were created as
part of a full tape backup.
Retry the operation after
specifying a recovery point
created by a full tape backup.
This will automatically delete
all the recovery points created
by the full tape backup as well
as all dependent incremental
tape backups.
3103 The operation will remove the
4 following recovery point(s)
because they have
dependencies on each other:
3103 Consistency check schedule
6 should be modified using the
<input parameter tag> cmdlet.
3103 DayofWeek needs to be
7 specified to continue.
3103 Cannot specify consistency
8 check schedule for protection
groups configured only for
tape-based protection.
3103 RelativeInterval needs to be
9 specified to continue.
3104 Duplicate times specified,
0 please specify unique times.
3104 Duplicate weekdays specified,
1 please specify unique days of
the week.
3104 Cannot specify offset
2 schedules for protection
groups configured only for
tape-based protection.
3104 Consistency check cannot be
3 started for unprotected data
186
3104 Consistency check cannot be
4 started for data source <data
source name> because the
protection for <protection
group> has been set to tape.
3104 There are multiple copies of
5 data. Please choose one of
the following and pass it to this
cmdlet.
3104 The selected item cannot be
6 added to protection. From the
DPM computer, only DPM
database can be selected for
protection.
3104 You have chosen short-term Click Help for more information.
7 protection using disk for this
protection group.
You cannot do that because
you selected the DPM
database as a member of this
protection group and it can be
protected only using tape.
3104 Online recatalog can be run
8 for file volume and share data
sources only.
3104 The number of recovery point
9 locations should be equal to
the number of recoverable
items passed to this cmdlet.
3105 The recovery point location
0 that you have passed is
invalid. Please try again with a
different value.
3105 Add the search path string and
1 try again.
3105 This step cannot be performed
2 because some of the
prerequisite steps have not
executed. Please ensure that
the appropriate steps among
<missing step list> have been
executed successfully and
then retry this step. For more
details, see DPM Help.
187
3105 This protection group does not
3 support the given protection
type. Please try again with a
different value.
3105 All data sources passed
4 should belong to the same
protection group.
3105 The data source <data source
5 name> specified is not a part
of the protection group
<protection group>.
3105 The minimum space required
6 for the <disk item> is
<minimum size>. Please
choose a value more than that
and try again.
3105 The disk space requirement
7 for <disk item> cannot be less
than the current value of
<used size>. Please choose a
value more than that and try
again.
3105 The data source <data source
8 name> is not protected and
size calculations cannot be
done on it.
3106 This recovery source location
0 is on a disk and not on a tape.
3105 Size optimization cannot be
9 done on data source <data
source name>. This can be
done only if a part of the data
source is protected. Retry
without the -CalculateSize
option.
3106 Specify a scheduled replica
1 creation time that is less than
1 year.
3106 The protection type has been
2 set to disk-based protection
only, therefore this command
is ignored.
3106 This tape is marked as a
3 cleaning tape. Run the
command on the correct tape.
188
3106 Incorrect start time specified.
4 Enter the start time in the
following format "hh:mm"
3106 Child data source objects
5 cannot be obtained for
external data source <data
source name>.
3106 Protection group <protection
6 group> does not contain this
type of schedule.
3106 This file type has not been
7 specified for exclusion.
3106 This member is not specified
8 for protection and cannot be
removed from protection.
3106 Please specify the library to
9 use in RecoveryOption for
recovery from tape, and try
again.
3107 This operation is valid only on
0 a recovery point on tape.
3107 The recovery point location
1 passed does not belong to
current recovery point.
3107 This step cannot be performed
2 because prerequisite steps
have not been completed. For
more information, type 'Get-
Help <Cmdlet name>' in DPM
Management Shell.
3107 Invalid Search Detail Passed
3
3107 The target computer either
4 does not exist or is currently
not protected by DPM
3107 Shares can be retrieved only
5 from a volume recovery point
3107 Recovery cannot proceed as Ensure that you have run DpmSync -reallocateReplica
6 the replica for the selected before recovering data to the replica. For details, see
data source is not in "replica the DPM 2010 Operations Guide.
creation pending" state.
3107 The search string should use
7 UNC Format if the protected
computer is not specified. If
189
the search is intended on a
folder, then specify the
protected computer name.
3107 System state cannot be
8 recovered back to the original
location. Please restore to an
alternate location.
3107 The recoverable item cannot
9 be recovered. Please see
DPM Help for more details.
3108 The specified alternate
0 instance is the same as
original. Please specify a
different instance or change
the database name
3108 The specified alternate
2 database name is a system
database. DPM cannot
recover a system database to
an alternate location. Change
the specified database name
so that it is not a system
database.
3108 The alternate database name
3 is empty. Provide a valid
alternate database name to
use for the recovery
3108 The alternate SQL instance
4 name is either empty or
invalid. Provide a valid
alternate SQL instance name
to use for the recovery
3108 DPM cannot detect the volume If the volume is present, this problem can be rectified
5 <data source name> on server by refreshing the state using the Get-Datasource
<server name>. -ProductionServer <ProductionServer> -Inquire cmdlet,
then retry the current task.
3108 Data source <data source Remove the inactive protection for <referential data
6 name> cannot be selected for source name> in the Protection task area by selecting
protection because it was the data source and then clicking Remove inactive
previously protected as part of protection option in the Actions pane.
data source <referential data
source name> and has
inactive disk or tape replicas.
3108 Data source <referential data Remove the inactive protection for <data source name>
7 source name> cannot be in the Protection task area by selecting the data source
selected for protection and then clicking Remove inactive protection option in
190
because its component the Actions pane.
database <data source name>
was protected independently
and has inactive disk or tape
replicas.
3108 The specified short-term Please specify a daily backup frequency or remove the
8 backup frequency does not CreateIncrementals parameter.
support creation of
incremental backups.
3108 The specified IP address If you would like to change the sequence number of the
9 already exists in the list of IP IP address, first remove the IP address and then add it
addresses specified in the to the appropriate sequence number.
backup LAN IP address list.
3109 The specified IP address Only the addresses which are currently a part of the
0 cannot be removed because it Backup LAN can be removed. Use Get-
does not exist in the backup BackupNetworkAddress to view a list of IP addresses
LAN IP address list. which are a part of the Backup LAN.
3109 The specified address is not a Subnet address should be in either of the following
1 valid subnet address. formats, 10.212.12.55/16 (IPV4) or
A821:db8:3c4d:15::/64 (IPV6)
3109 The specified sequence Use Get-BackupNetworkAddress command to see the
2 number is not valid. Try again list of valid sequence numbers
with a valid number.
3109 The specified subnet mask is Valid subnet mask for IPV6 address lies between 1 -
3 not valid for IPV6. 128.
3109 The specified subnet mask is Valid subnet mask for IPV4 address lies between 1 -
4 not valid for IPV4. 32.
3109 The specified recovery options Check the parameters that you are passing to the
5 are not valid. cmdlet and ensure that these parameters correspond to
the data source type that you are attempting to recover.
3109 Failed to perform Test- Retry this operation on the DPM server which was used
6 DPMTapeData on the to create this recovery point.
specified recovery point since
this was created by some
other DPM installation.
3109 <Server name> is not an Contact your Exchange administrator or retry with the
7 owner for the Exchange fully qualified domain name (e.g. test.contoso.com).
cluster resource group <virtual
server name>.
3109 The PreferredPhysicalNode is Please provide all the values and try again.
8 specified incorrectly. For example, "PreferredPhysicalNode
(ResourceGroup1.contoso.com, server1.contoso.com),
(ResourceGroup2.contoso.com,
server2.contoso.com)".
191
3109 The retention range cannot be
9 achieved with the current
synchronization frequency.
3110 Invalid command line Please provide the correct parameters and try again.
0 parameters specified.
3110 The rescan operation failed.
2 For more details, view the
Jobs tab in the Monitoring task
area.
3110 Rescan operation completed
3 successfully.
3110 The door on the <library type>
5 <library> could not be
unlocked
3110 Door successfully unlocked for
6 <library type> <library>. You
can now open the library door.
The door will be automatically
locked again in <time in
minutes> minutes.
3110 The door on the <library type> Check the library door and ensure that it is closed
7 <library> could not be locked. properly. If the door is not closed, close it and then retry
this operation.
3110 Door successfully locked for
8 <library type> <library>.
3111 The selected drive is in use.
0 To disable the drive, wait for
the job to finish or cancel the
job.
3111 Selected drive is disabled.
2 Any protection jobs configured
to use the library to which the
selected drive belongs will use
the remaining drives on the
library.
3111 Selected drives are enabled.
3
3111 Cleaning tapes are not
4 available in <library>, to clean
the selected drives.
Add cleaning tapes and restart
the cleaning job.
3113 Door of <library type>
192
9 <library> is already unlocked.
0 <library> is being unlocked.
Please wait for the operation
to complete.
1 <library> is already locked.
3111 The selected tapes cannot be
6 marked as free because they
belong to protection groups.
You need to stop protection of
the associated protection
groups before you can mark
the tapes as free. The
protection group that a tape
belongs to is listed in the
Protection Group column.
3112 The selected tapes cannot be
0 erased because they belong to
protection groups.
groups before you can erase
the tapes. The protection
group that a tape belongs to is
listed in the Protection Group
column.
3112 I/E port door of <library> is
3 now open. Place the tapes to
be added in the I/E port, and
then click OK.
On clicking OK the I/E port
door will be closed and the
tapes in I/E port will be added
to the library.
3112 The selected tapes could not
4 be marked as free because
another job has reserved them
for use.
3112 The selected tape(s) could not
5 be marked as cleaning tapes
because they are currently in
use.
3112 <failure count> tape(s) could
6 not be marked as cleaning
tapes because they are
193
currently in use.
3112 DPM could not perform the Close and reopen DPM Administrator Console to
7 requested action on the synchronize it.
selected items.
This could be because the
selected items or some
properties associated with
these items have changes that
prevent the action from being
taken.
3112 The selected data will be
8 copied to the specified
location.
You can monitor the progress
of the copy job(s) on the Jobs
tab in the Monitoring task
area.
3112 <failure count> out of <total
9 number> selected tapes
cannot be marked as free
because they belong to
protection groups.
groups before you can mark
the tapes as free. The
protection group that a tape
belongs to is listed in the
Protection Group column.
0 number> selected tapes could
not be marked as free
because another job has
reserved them for use.
3113 The selected tape(s) could not
4 be unmarked as cleaning
currently in use.
1 number> selected tapes
cannot be marked as free. The
tapes must be erased.
Click Erase tape in the Actions
pane to erase the tapes. This
requirement to erase the tapes
was specified in the protection
groups to which the tapes
194
previously belonged.
3 number> tapes cannot not be
erased because they contain
data that is being protected.
groups before you can erase
the tapes. The protection
group that a tape belongs to is
listed in the Protection Group
column.
3113 <failure count> tape(s) could
5 not be unmarked as cleaning
currently in use.
3113 The selected tape is currently
6 being recataloged.
The contents of this tape can
be viewed only after the
recatalog operation
successfully completes.
3113 Operation failed because
7 <library type> <library> is
offline.
3113 Operation failed because
8 <library type> <library> is
disabled.
2 <library> is being locked.
Please wait for the operation
to complete.
3114 Connection already exists to
3 DPM server <server name>.
You can only be connected to
a single DPM server at a time.
Please end the existing
connection using Disconnect-
DPMServer before attempting
to run cmdlets that are
targeted to another DPM
server.
3114 The server <server name> Ping this server to verify that it is accessible and then
4 could not be found in Active retry the operation. If the server is accessible, verify
Directory. that the DPM service is running and that the current
user has a domain account and is a member of the
195
local administrators group. If the problem persists,
contact your DPM administrator.
3114 Tape in <location> cannot be
5 recataloged. Perform the
following before retrying this
cmdlet:
If the tape is marked as free,
run Set-Tape -NotFree on this
tape.
If the tape is marked as
unknown, run Start-
DPMLibraryInventory on this
tape.
3114 Operation failed because drive
6 <drive name> is offline.
3114 Operation failed because drive
7 <drive name> is disabled.
3115 All selected tapes were
0 successfully moved to the I/E
port slots of the library
<library>
3115 This operation is not allowed Take out the tape in <location>, replace the barcode,
1 on a suspect tape. and run detailed inventory on the tape.
3120 DPM was unable to initiate 1) Check to see that the computer name provided is the
0 recovery to the specified fully qualified domain name.
computer. 2) Check to see that the computer specified has a
protection agent installed on it.
3) If recovery is to a clustered server, ensure that all
physical nodes belonging to this cluster have the
protection agent installed.
3120 The selected recovery point is
3 not valid for recovery to a
DPM server.
3120 This option is disabled as the
4 DPM database DPMDB
cannot be recovered directly to
the original location. For more
information, see the
DPM 2010 Operations Guide.
3120 Latest point in time recovery is
5 not supported from:
1) Secondary DPM server.
2) Invalid replica.
3) Inactive protection.
196
3120 DPM cannot protect this
6 member. On the secondary
DPM server, you can only
protect data sources for the
primary DPM server or the
data sources of the computers
that the primary DPM server is
protecting.
3120 Cannot perform <input Complete the manual creation of the replica and then
7 parameter tag> on a replica retry this operation.
which is pending manual
replica creation.
3120 Cannot perform <input Verify that the disk containing the replica volume and
8 parameter tag> on a replica the recovery point volume is shown in Disk
which is missing. Management. If you are unable to locate the volumes in
the Disk Management console, open the Protection
task area in DPM Administrator Console to stop
protection of the data source using the Delete replica
option, and then add the data source to a protection
group again.
3120 Cannot perform <input Run synchronization with consistency check for this
9 parameter tag> on a replica replica and then retry this operation.
which is inconsistent.
DPM server, partial protection
of a replica is not allowed.
DPM server, you cannot
protect data sources which are
not protected by the primary
DPM server.
3130 Failed to create schedule with Specify a date which is less than or equal to 28.
0 the specified start time
because the date is invalid.
3121 You have selected a clustered
2 resource group for switching
protection. This operation will
apply to all the nodes under
this resource group: <server
name>. Protection for other
resource groups belonging to
this cluster may fail. You need
to perform this operation for all
resource groups to resume
protection.
197
3121 You cannot recover to original
3 location from a secondary
DPM server without switching
protection of the protected
computer to the secondary
DPM server.
To enable this, open DPM
Management Shell, run the
Switch-Protection.ps1 script,
and then try this operation
again.
3121 Switch protection failed
4 because there is no protection
agent on the protected
computer.
3121 Invalid input. Switching
5 protection back to primary
DPM server is not allowed on
a primary DPM server.
Switching protection back to
the primary DPM server is
allowed only on a secondary
DPM server.
3121 Invalid input. You cannot
6 switch protection for a primary
DPM server. Switching
protection is allowed to switch
protection for protected
computers only.
1 created for <data source
name> since protection has
been stopped for this data.
3200 DPM was unable to attach the 1) Check to see that the specified instance of SQL
0 content database to the SQL Server is online.
Instance <SQL Server 2) If your SQL database files do not have the .mdf, .ndf,
instance name> on the and .ldf extensions for the primary data file, secondary
recovery farm. data file, and log file, respectively, then DPM will not be
able to attach the content database to the specified
SQL Instance and cannot perform a site or document
recovery from it.
3200 DPM was unable to detect the 1) Check to see that the recovery farm is online and
1 presence of the Web running.
application named 2) Make sure you have created a Web application in
'DPMRecoveryWebApplication the recovery farm with the name
' in the recovery farm. 'DPMRecoveryWebApplication'.
For more information, see the DPM 2010 Operations
198
Guide.
3200 DPM was unable to attach the 1) Check to see that the recovery farm is online and
2 content database to the running.
recovery farm. 2) Check to see that the WSSCmdletWrapper DCOM
component is configured correctly on the front-end Web
server hosting the recovery farm.
Guide.
3200 DPM was unable to export the 1) Check to see that the recovery farm is online and
3 item <site URL> from the running.
recovery farm. 2) Check to see that the WSSCmdletWrapper DCOM
server hosting the recovery farm.
Guide.
3) Check that all features, Web templates, and
language packs present on the protected farm are also
present on the specified recovery farm.
4) It is possible that the item you want to recover is not
present in this version of the content database. Use a
different recovery point for recovery.
5) Run ConfigureSharePoint.exe on the recovery farm
server and modify the TEMP variable to point to a
location that has sufficient space to recover the
selected item.
3200 DPM was unable to detach the 1) Check to see that the recovery farm is online and
4 content database <content running.
database> from the recovery 2) Open the SharePoint Central Administration Console
farm. of the recovery farm and delete the content database.
3200 DPM was unable to import the 1) Check to see that the protected farm is online and
5 item <site URL> to the running.
protected farm. 2) Check to see that the WSSCmdletWrapper DCOM
server hosting the protected farm.
Guide.
3) Ensure that all features, Web templates, and
language packs present on the recovery farm are also
present on the protected farm.
4) Run ConfigureSharePoint.exe on the target server
and modify the TEMP variable to point to a location that
has sufficient space to recover the selected item.
3200 DPM found that 1) Check to see that the protected farm is online and
6 'DPMRecoveryWebApplication running.
' was not properly configured. 2) Open SharePoint Administration Console and delete
199
the Web application named
'DPMRecoveryWebApplication' and recreate it.
3) Retry the operation again.
3200 DPM failed to protect <data 1) Turn off the SharePoint VSS writer on the front-end
7 source name> because DPM Web servers that you do not want to protect the farm.
detected multiple front-end Only one front-end Web server in this farm should have
Web servers for the same farm the SharePoint VSS writer turned on.
that have the SharePoint VSS 2) Close the Create New Protection Group Wizard and
writer enabled. retry the operation.
3200 This Windows SharePoint 1) Verify that the appropriate SQL Server VSS Writers
8 Services farm cannot be on the computers hosting the Windows SharePoint
protected because DPM did Services databases are enabled.
not find any dependent 2) Verify that the Windows SharePoint Services Search
databases and search indices VSS Writers are enabled on the computers where the
to be protected. search indices are.
3121 You can offset synchronization
7 frequency only for incremental
backups.
3121 The offset is greater than
8 synchronization frequency.
3121 Invalid synchronization
9 frequency. You can only set
synchronization frequency to
6, 12 or 24 hours.
3122 DPM failed to apply the If you see this error on the primary DPM server then do
0 required policies to this the following:
protection group since the 1) Check to see if you can reduce the number of
recovery point limit for this express full backupss (or file recovery points) for the
DPM server has been data sources that are currently being protected.
exceeded.
2) Reduce the retention range for the existing
protection groups
3) Reduce the number of data sources being protected
by this DPM server
If you see this error on the secondary DPM server. Do
the following:
1) Check to see if you can reduce the synchronization
frequency for applications (or file recovery points) that
are currently being protected.
2) Reduce the retention range for the existing
protection groups.
3) Reduce the number of data sources being protected
by this DPM server.
200
DPM Error Codes
The content in this section provides guidance for resolving issues identified by specific error
messages in System Center Data Protection Manager (DPM) 2010.
The content in these topics may be updated. It is the most current information available and
supersedes the recommended actions in the product for the specified error.
In This Section
Error ID: 319
Error ID: 324
Error ID: 347
Error ID: 958
Error ID: 1243
Error ID: 3133
Error ID: 24050
Error ID: 24084
Error ID: 30101
Error ID: 30111
Error ID: 30300
Error ID: 30216
Error ID: 31224
Error ID: 32061
Error ID: 32062
Error ID: 32064
Error ID: 32065
Error ID: 32612
Reference
DPM 2010 Troubleshooting Guide
201
Error ID: 319
Error #319 — Data Protection Manager

Details
Product Data Protection Manager
ID 319
Source
Version 3.0
Symbolic Name
Message The agent operation failed because of a
communication error with the DPM Agent
Coordinator service on <ServerName>.
Explanation
This error can occur when you attempt to update a DPM protection agent on a protected
computer that is running a localized version of Windows Server 2003 SP2 that is not supported
by the DPM Agent Installer.
User Action
To resolve this issue, 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 appropriated localized version of hotfix
in Knowledge Base article 975759: Update for Windows Server 2003
(http://go.microsoft.com/fwlink/?LinkId=184897), and then try the upgrade again.
Note
The "Hotfix download available" form displays the languages for which the hotfix is
available.
202
Error ID: 324

You may encounter this error while attempting to install, uninstall, or upgrade an agent by using
DPM Management Shell.
Details
ID 324
Source
Version 3.0
Symbolic Name
Message The agent operation failed because the DPM
Agent Coordinator service on <server> did not
respond.
Explanation
This error might be caused by the following:
 The target computer is not reachable on the network.
 The firewall on the target computer is blocking requests from the DPM server.
User Action
To troubleshoot this issue, do the following:
1. Check the recent DPMAC source records in the application event log on <server>.
2. Verify that the DPM server is remotely accessible from <server>.
3. If a firewall is enabled on the DPM server, verify that it is not blocking requests from <server>.
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:
Installing an agent by using DPM Management Shell:

1. Copy DPMAgentInstaller.exe and DPMAgentInstaller_x64.exe to a share.
2. On the target computer, log on as an administrator and then open a command prompt
window with elevated privileges.
203
3. Navigate to the network share, and then run the appropriate DPMAgentInstaller <FQDN of
DPM server>.
4. On the DPM server, open DPM Administrator Console. In the Management task area, click
the Agents tab, click Install Agent, and then select Attach agents. Complete the wizard.
Uninstalling an agent by using DPM Management Shell:

1. Log on to the target computer and in Control Panel navigate to Programs and Features.
2. Uninstall the Microsoft Data Protection Manager 2010 Agent.
3. On the DPM server, start DPM Management Shell.
4. Run the RemoveProductionServer.ps1 script to remove the target computer from the DPM
server.
Upgrading an agent by using DPM Management Shell:

1. Copy the required DPMAgentInstaller.exe to a network share.
2. Log on to the target computer on which you want to upgrade the agent.
3. Navigate to the network share, and then run DPMAgentInstaller.exe.
4. On the DPM server, open DPM Administrator Console. In the Management task area, click
the Agents tab.
5. Refresh the status of the target computer.
Error ID: 347

Details
ID 347
Source
Version 3.0
Symbolic Name
Message Agent operation failed. (ID 370)
An error occurred when the agent operation
attempted to create the DPM Agent
Coordinator service on <Server Name>.
(ID 347 Details: The handle is not valid.)
204
Explanation
This error might occur when the Agent Coordinator service is not running or responding on the
target server.
User Action
 Verify that the 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 operation.
 Try installing the protection agent manually on the target computer. For more information, in
the DPM Deployment Guide, see Installing Protection Agents Manually
Error ID: 958

Details
ID 958
Source
Version 3.0
Symbolic Name
Message DPM cannot browse the contents of the virtual
machine on the protected computer <protected
computer>.
Explanation
Item-level recovery is not supported in the following scenarios:
 The VHD contains a dynamic disk inside the guest operating system.
 The VHD has no volume.
 HyperV role is not installed on the DPM server.
User Action
Perform a full restore of the virtual machine.
205
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
Error ID: 1243

Details
ID 1243
Source
Version 3.0
Symbolic Name
Message The detailed inventory of tape failed for the
following reason:
(ID: 3316)
Detailed inventory failed.
(ID 1243)
Explanation
Detailed inventory failures can be caused by the following conditions:
 The state of the DPM library changes without the changes being communicated to the DPM
server. This can happen if tapes are removed, inserted, or moved without running a fast
inventory after the operation.
 The specified tape is in a drive and being backed up.
 Detailed inventories can raise an error for a failure on each slot. If you have a lot of slots, you
might receive too many failure error alerts.
User Action
To resolve this issue, do one or more of the following:
 Perform a fast inventory after each tape operation.
 Ensure 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.
206
Caution
Serious problems might 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.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection
Manager\1.0\Alert
Value Name: DetailedInventoryFailed
Data Type: REG_DWORD
Value Data 0
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.
Error ID: 3133

Details
ID 3133
Source
Version 3.0
Symbolic Name
Message 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.
(ID 3133)
Explanation
DPM could not collect the list of URLs from some of the databases in the SharePoint farm. If
these databases have been cataloged previously, you can view a list of URLs for each database
in the Recovery task area. However, any URLs that have been added since the databases were
207
last cataloged will not appear. To view the list of databases that could not be cataloged, search for
the WSSCmdLetWrapper.errlog file in the DPM installation folders on the SharePoint front-end
Web server and DPM server.
User Action
Restart the catalog job for the SharePoint farm by running the Start-CreateCatalog cmdlet in
DPM Management Shell.
Error ID: 24050

Details
ID 24050
Source
Version 3.0
Symbolic Name
Message Failed to perform the operation since the tape
<Media Label> is not available in <Library
Type> <Library>.
(ID 24050)
Explanation
This error is usually caused by running out of free tapes in the library.
Note
To avoid running out of free tapes in the library, you can periodically check for Free tape
threshold reached alerts in the Alerts tab of the Monitoring task area.
User Action
1. In 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.
208
2. In 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
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 ensure that the new tapes appear as free. Then, click
Monitoring on the navigation bar, click the Alerts tab, and restart the failed jobs.
Error ID: 24084

You may encounter this error when a tape is written by a non-DPM application using a physical
block size either less than 1024 bytes or more than 65536 bytes.
Details
ID 24084
Source
Version 3.0
Symbolic Name
Message The tape in <LibraryType> <Library> at
<MediaLocationType> <MediaLocationInfo>
has been written to by another tape backup
application using an unsupported physical
block size.
Explanation
DPM only supports a physical block size between 1024 bytes and 65536 bytes. Therefore, DPM
cannot read or overwrite the contents of this tape.
If the tape was used by any other backup application with an unsupported block size, the block
size information will persist with the tape.
209
User Action
To resolve this issue, 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 will be able to 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.
Error ID: 30101

Details
ID 30101
Source
Version 3.0
Symbolic Name
Message Library drive <Library Drive> in <Library> is not
functioning and library jobs may fail until the
drive is repaired. The drive is not functioning
(ID: 3303)
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>.
(ID 30101)
Explanation
This issue is usually caused by the driver for the tape drive but can also be caused by hardware
issues. Possible causes include the following:
 When a tape reaches the end, some drivers will incorrectly return a Device I/O error code
instead of an End of tape reached code.
 An errant driver might not be able to handle multiple parallel write requests.
210
 The backup might fail because data was written successfully after an initial device I/O error.
 There might be a defective tape or a bad sector on the tape.
 The tape drive might be defective or dirty.
User Action
To resolve this issue, do one or more of the following:
1. The first step is to 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 will incorrectly return a Device I/O error code
instead of an End of tape reached code. To resolve this issue, modify the value of the following
registry key to match your tape size.
Caution
Serious problems might 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.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\Agent
Value Name: TapeSize
Value Data (in MBs) 00030000
When a tape reaches the end, DPM reads the TapeSize value (in MBs).
If the tape drive driver returns a Device I/O error code and the amount of data written by DPM is
greater than the TapeSize value (in MBs), DPM automatically converts the Device I/O error code
to an End of tape reached code, and then spans to the next tape.
If your tape size is different from the TapeSize value in the registry, you need to modify the
TapeSize value accordingly.
Reduce the number of parallel write buffers

An errant driver might not be able to handle multiple parallel write requests. To resolve this issue,
reduce the number of parallel write buffers that DPM uses by creating and modifying the following
registry key.
Caution
211
Serious problems might 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.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\Agent
Value Name: BufferQueueSize
Value Data 00000001
Start by setting the BufferQueueSize value to 1 or another low value, and then increase it to the
maximum value that the driver can accommodate before it begins to send device I/O error alerts
again.
Error ID: 30111

Details
ID 30111
Source
Version 3.0
Symbolic Name
Message 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. (ID 30111 Details: Unknown
error (0x80042306) (0x80042306))
Explanation
This error occurs when the shadow copy provider fails to create a snapshot for the requested
volume. The most common reason for this is that the required snapshot management licenses
are not installed on the servers in the cluster, and the hardware provider does not handle the
request to create a snapshot.
212
User Action
Ensure that the required licenses are installed on the server, and then retry the backup.
Error ID: 30300

Details
ID 30300
Source
Version 3.0
Symbolic Name
Message Recovery point creation jobs for <data source>
on <DPM server> have been failing. The
number of failed recovery point creation jobs =
n.
If the data source protected is SharePoint, then
click Error Details to view the list of databases
for which recovery point creation has failed.
(ID 3114)
Synchronization for the replica of <data
source> on <DPM server> failed because the
replica is not in a valid state or is in an inactive
state. (ID 30300 Details: VssError: The writer
experienced a non-transient error. If the
backup process is retried, the error is likely to
reoccur.)
Explanation
This alert may be raised on the secondary DPM server after a synchronization job for a data
source has failed on the primary DPM server.
User Action
Review the application event log on the protected computer for errors from the DPM writer
service. Take the appropriate action, and then try the operation again. The following are the
events you might find in the log and the recommended action for each event:
213
DPM writer was unable to snapshot the replica of <data source>,
because the replica is not in a valid state (Validity: <Validity
State>:
 In DPM Administrator Console on the primary DPM Server, run a consistency check for the
data source <data source> to ensure that the replica is consistent.
DPM Writer has timed out waiting for replica to be free and
available for snapshot.
 Retry the job from the secondary DPM server when no jobs are running on the primary DPM
server for the selected data source.
DPM has run out of free recovery point space and will fail
snapshots for <data source> in order to prevent existing
recovery points from getting recycled.
1. Increase the space allocated for the recovery point volume for <data source> on the primary
DPM server.
2. Retry the operation on the secondary DPM server.
DPM writer was unable to snapshot the replica of <data source>.

The following are possible causes:
 No valid recovery points are present on the replica.
 The last express full backup job for the data source failed.
 There was a failure while deleting the incremental recovery points that are not valid on the
replica.
To resolve this issue, in DPM Administrator Console on the primary DPM server, run an express
full backup job for the data source.
Error ID: 30216

Details
ID 30216
Source
Version 3.0
Symbolic Name
214
Message Windows Server Backup may truncate
Exchange and SQL Server logs being
protected by DPM.
Explanation
Using Windows Server Backup to create backups of a volume that is protected by DPM may
truncate the Exchange Server or SQL Server logs.
User Action
If you use Windows Server Backup to back up a volume, only do so by using the Backup Once
Wizard.
If you use the Backup Schedule Wizard to perform scheduled backups, ensure that the volumes
that are being protected by DPM do not contain application data such as Exchange Server
mailbox stores or SQL Server databases.
To resolve this error, reconfigure Windows Server Backup. Then in DPM Administrator Console,
in the Protection task area, select the volume, click Create recovery point, and then click
Express full backup.
Error ID: 31224

Details
ID 31224
Source
Version 3.0
Symbolic Name
Message Create protection group: <protection group
name> failed. The ‘Allocate Replica’ task for
<data source name> failed.
(ID 31224)
215
Explanation
You will encounter a replica creation error and a protection group creation error if you perform the
following actions in sequence:
1. Protect a data source in one protection group (protection group 1).
2. Stop protecting the data source in protection group 1 and retain its data.
3. Protect the data source in a second protection group (protection group 2).
4. Stop protecting the data source in protection group 2, retain its data, and then protect the
data source in a third protection group.
User Action
To protect a data source that has been previously protected in two other protection groups, you
must first remove all recovery points of the data source that are associated with the first
protection group as described in the following steps:
1. Get a list of all data sources on the DPM server.
$ds = Get-Datasource [-DPMservername]<DPMservername>
2. Identify the data source that you want to protect in the list. Using $ds returns a zero-based
array. So if the data source you want is the sixth one in the list, you would use $ds[5] to
identify it in the next step.
3. Get all the recovery points associated with the data source.
$rp = Get-RecoveryPoint $ds[5]
4. Select a recovery point that was taken when the data source was in the first protection group
(for example, $rp[2]).
5. Remove the recovery point.
Remove-RecoveryPoint $rp[2]
6. Repeat the last two steps until you have removed all recovery points associated with the data
source when it was in the first protection group.
Error ID: 32061

Details
ID 32061
Source
Version 3.0
216
Symbolic Name
Message Dynamic disks use a private region of the disk
to maintain a Logical Disk Manager (LDM)
database. The LDM database will be at
<CurrentLdmOccupancy>% occupancy after
this operation. When occupancy reaches
<LdmErrorThreshold>%, all volume creations
and grows will be disabled and backups that
require volume grows may fail.
Explanation
Dynamic disks use a private region at the end of the disk to maintain a Logical Disk Manager
(LDM) database that has a limited size that cannot be exceeded.
User Action
You can control the growth of the LDM database by migrating one or more data sources to a
different volume.
To migrate a data source to a different volume, in DPM Management Shell, run the
MigrateDatasourceDataFromDPM cmdlet.
Error ID: 32062

Details
ID 32062
Source
Version 3.0
Symbolic Name
database. The LDM database is currently at
<CurrentLdmOccupancy>% occupancy. When
occupancy reaches <LdmErrorThreshold>%,
all volume creations and grows will be disabled
and backups that require volume grows may
fail.
217
Explanation
User Action
different volume.
Error ID: 32064

Details
ID 32064
Source
Version 3.0
Symbolic Name
database. This volume creation or grow was
not allowed because the occupancy of the
LDM database would have been
<CurrentLdmOccupancy>% after this
operation, which is above the DPM limit of
<LdmErrorThreshold>%
Explanation
218
User Action
different volume.
Error ID: 32065

Details
ID 32065
Source
Version 3.0
Symbolic Name
database. The current occupancy of the LDM
database is <CurrentLdmOccupancy>%, which
is over the DPM limit of <LdmErrorThreshold>
%. Hence, all volume creations and grows
have been disabled.
Explanation
User Action
different volume.
219
Error ID: 32612
Error #32612— Data Protection Manager

Details
ID 32612
Source
Version 03.00
Symbolic Name
Message Failed to prepare a Cluster Shared Volume
(CSV) for backup as another backup using the
same CSV is in progress. (ID 32612 Details:
Unknown error (0x8007173d) (0x8007173D))
Explanation
This error might occur when a hardware provider is not installed on the protected server. If no
hardware provider is installed, DPM uses only software snapshots for backup, which means that
the CSV is left in redirected access mode for the entire length of the backup. While this is the
case, another virtual machine that is on the same CSV but on a different node of the cluster
cannot be backed up. If the CSV that is in redirected access mode is not released before another
backup is attempted, this error occurs.
User Action
If you are using software-based Volume Shadow Copy Service (VSS) providers, we recommend
that you also use VSS hardware providers. For more information, see VSS Hardware Providers
(http://go.microsoft.com/fwlink/?LinkId=179952). If a hardware VSS provider is already installed
on the node, check the status of the CSVs used by this virtual machine by using the Cluster
Administration Console, re-enable direct I/O for the CSV, and then try the operation again.
220

System Center Data Protection Manager 2010 Troubleshooting Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

System Center Data Protection Manager 2010 Troubleshooting Guide

Uploaded by

Copyright:

Available Formats

System Center Data Protection Manager 2010

Diagnostic Process for Request Tracking and Error Tracing...........................................................8

Standard Troubleshooting Procedures.......................................................................................... 10

Verifying Status of the DPM Service.............................................................................................10

Checking Name Resolution........................................................................................................... 11

Identifying DNS Errors.................................................................................................................. 12

Resolving "Access Denied" Errors................................................................................................13

Troubleshooting DPM Installation Issues......................................................................................14

Troubleshooting Installation Issues...............................................................................................14

Troubleshooting Protection Agent Installation Issues....................................................................17

Troubleshooting Remote SQL Server Issues................................................................................23

Troubleshooting Data Protection Issues.......................................................................................25

General Data Protection Issues.................................................................................................... 25

File Server Protection Issues........................................................................................................ 31

Exchange Server Protection Issues..............................................................................................32

SQL Server Protection Issues....................................................................................................... 38

Windows SharePoint Protection Issues........................................................................................44

System Protection Issues............................................................................................................. 47

Mirrored Databases Issues........................................................................................................... 48

Virtual Server Protection Issues.................................................................................................... 49

Manual Replica Creation Issues................................................................................................... 50

Incompatible Filter Driver Errors................................................................................................... 52

Client Computer Protection Issues............................................................................................... 53

Hyper-V Protection Issues............................................................................................................ 54

Troubleshooting Data Recovery Issues........................................................................................ 56

General Data Recovery Issues..................................................................................................... 56

Exchange Server Recovery Issues...............................................................................................57

SQL Server Recovery Issues........................................................................................................ 60

Windows SharePoint Recovery Issues......................................................................................... 61

Tape Library Recovery Issues....................................................................................................... 63

End-User Recovery Issues........................................................................................................... 63

Computers in Workgroups and Untrusted Domains Recovery Issues..........................................64

Troubleshooting Tape Library Management Issues......................................................................65

Troubleshooting Reporting Issues................................................................................................ 68

Troubleshooting Performance Issues........................................................................................... 74

Network Bandwidth Issues............................................................................................................ 74

Troubleshooting Database Issues.................................................................................................74

Troubleshooting Job Status Issues............................................................................................... 80

Troubleshooting the DPM System Recovery Tool.........................................................................80

Troubleshooting Disaster Recovery Issues...................................................................................82

DPM 2010 Error Code Catalog..................................................................................................... 86

DPM Error Codes....................................................................................................................... 237

Error ID: 319............................................................................................................................... 238

Error ID: 324............................................................................................................................... 239

Error ID: 347............................................................................................................................... 241

Error ID: 958............................................................................................................................... 242

Error ID: 1243............................................................................................................................. 242

Error ID: 3133............................................................................................................................. 244

Error ID: 24050........................................................................................................................... 245

Error ID: 30101........................................................................................................................... 247

Error ID: 30111............................................................................................................................ 249

Error ID: 30300........................................................................................................................... 250

Error ID: 30216........................................................................................................................... 251

Error ID: 31224........................................................................................................................... 252

Error ID: 32061........................................................................................................................... 253

Error ID: 32062........................................................................................................................... 254

Error ID: 32064........................................................................................................................... 255

Error ID: 32065........................................................................................................................... 256

Error ID: 32612........................................................................................................................... 257

Diagnostic Process for Request Tracking and

Error Tracing Tuning Feature

Parameter Overriding Registry Key Default Value Possible Values

Trace level TraceLogLevel TRACE_ERROR All valid trace level