DPMv3TShootGuide

System Center Data Protection Manager 2010 Troubleshooting Guide

Microsoft Corporation

Published: July 2010

FeedbackSend suggestions and comments about this document to [email protected].

mailto:%[email protected]?subject=DPM%202010%20Troubleshooting%20Guide%20Published%20July%202010

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 SectionDiagnostic 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 TrackingEvery 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

8

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.

Request Tracking Tuning FeatureThe 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 TracingLog 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 FeatureThe 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 each

file

<binary>TraceLogMaxSize 5 MB A file size (total disk

space consumed

for this binary’s log

= size * number of

files to retain)

Max number of

files to retain

<binary>TraceLogMaxNum 30 Any non-negative

number

9

<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.

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 SectionVerifying 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.

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:

To verify status of the DPM service

10

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 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.

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

To check name resolution

11

http://go.microsoft.com/fwlink/?linkid=45276

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.

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.

12

http://go.microsoft.com/fwlink/?LinkId=50823


Use Network Monitor to determine whether the correct DNS server responds to ping.

Additional ResourcesFor 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)

ToolsFor 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.

1. In Computer Management, expand System Tools, expand Local Users and Groups, and then click Groups.

To verify group membership on the file server

13





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.

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.

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 SectionTroubleshooting 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

To verify DCOM Launch and Access permission on the file server

14

Issue Possible Cause Resolution

Computer

stops

working

when you

uninstall

DPM 2010

with the

“Remove

data”

option.

1. Uninstall DPM 2010 using the “Retain data” option.

2. Delete the DPM database.

3. Use Disk Management to delete the volumes created by DPM.

Windows

Installer 4.5

installation

fails.

Run Windows Installer Setup from the \

DPM2010\setup\redist folder.

SQL Serve

r

installation

fails.

Summary.txt file contains the following:

A network error occurred while attempting

to read from the file: C:\SQLSVR2008\

x64\setup\x64\sqlncli10_x64.ms

If the SQL Server Native Client is

installed on the computer, remove it,

and then retry the DPM installation.

A DPM

installation

interrupts

non-DPM

application

s.

During DPM installation, Setup restarts

the Windows Management

Instrumentation (WMI) service. If you are

running applications other than DPM and

its prerequisite software on the DPM

server, you may experience an

interruption in the operation of those

applications while the WMI service is

restarted.

To prevent an interruption, shut down

all other applications before you run

DPM Setup.

Error 810

or ID:

4315. The

trust

relationship

between

this

workstation

and the

primary

domain

failed.

If the DPM server is unable to connect to

the domain controller during installation,

the DPM installation fails.

Verify that the DPM server can

communicate with the domain

controller. In addition, verify that the

DNS entries are for the domain

controller and that they are correctly

configured.

15


Error 812.

Configurati

on of

reports

failed.

This problem occurs when both

SQL Server Reporting Services and

Windows SharePoint Services are

installed in the same Internet Information

Services (IIS) application pool.

To resolve this issue, perform one of

the following tasks:

Uninstall Windows SharePoint Services by using Add or Remove 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.

Setup

cannot

query the

system

configuratio

n while

performing

the

prerequisit

e check on

Windows

Server

2008

operating

system.

This issue occurs if the WMI repository is

inconsistent.

To resolve this issue, verify that the

WMI repository is consistent by running

Winmgmt /verifyrepository at

the command prompt. If it is

inconsistent, resolve the issue and try

the installation again.

DPM is

unable to

configure

the

Windows

Server

account

because

The custom password filter software is

installed on the domain controllers.

Disable the custom password filter

before you install DPM.

16





the

password

you

entered

does not

meet the

Group

Policy

requiremen

ts.


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


SetDPMServer fails

with error code

0x80070534 and

error message “No

mapping between

account names and

security IDs was

done.”

A DPM 2010 agent

was installed on this

computer earlier, but

a SetDPMServer

action was not

performed.

1. Install the new protection agent.

2. Perform SetDPMServer on the old agent.

3. Uninstall the old protection agent.

4. Do an agent upgrade.

Protection agent

upgrade fails.

If there is an entry for DPM Protection Agent 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>.

17

http://go.microsoft.com/fwlink/?LinkID=179676


Error 300: The

agent operation

failed because it

could not

communicate with

the specified server.

Incorrect firewall configuration requirements on the DPM server.

The Remote Procedure Call (RPC) server is unavailable.

To resolve this issue, do the following:

For firewall configuration requirements, in the DPM Operations Guide, see Managing DPM Servers (http://go.microsoft.com/fwlink/?LinkId=187199).

For an unavailable RPC server, see Microsoft Knowledge Base article 224370, "Troubleshooting RPC Server is Unavailable in Windows" (http://go.microsoft.com/fwlink/?LinkId=45817).

Error 303: Agent

operation with

specified server

failed.

Another installation is running on the specified server.

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

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

Convert the boot volume to NTFS file system if you have sufficient space.

For more information about using the Convert

command for converting FAT volumes to

NTFS, see Microsoft TechNet article Convert


Review Microsoft Knowledge Base

article 156560, "Free Space Required to

Convert FAT to NTFS"


If neither of these actions resolves the problem, restart the specified server and then retry the operation.

Error 306: Agent

installation failed

because the

specified server

already has a

different version of

the protection agent

installed.

This issue occurs

when the protection

agent has already

been installed on a

server, but the DPM

database does not

have a record of the

protection agent

being installed.

Perform the following steps to reinstall the

protection agent:

1. Locally uninstall the protection agent from the server.

2. On the DPM server, in DPM Administrator Console, in the Management task area, on the Agents tab, select the server. In the 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 configuration

For firewall configuration requirements, in the DPM Operations Guide, see Managing DPM

18










The agent operation

failed because of a

communication error

with the DPM

Protection Agent

service on the

specified server.

requirements on the DPM server.

Internet Protocol Security (IPsec) configuration.

The RPC server is unavailable.

Servers (http://go.microsoft.com/fwlink/?LinkId=187199).

IPsec may be configured to block particular IP traffic, such as on a particular port or to particular addresses. For assistance in troubleshooting IPsec, see IPsec Troubleshooting (http://go.microsoft.com/fwlink/?LinkId=50885).

See Microsoft Knowledge Base article 224370, "Troubleshooting RPC Server is Unavailable in Windows" (http://go.microsoft.com/fwlink/?linkid=45817).

Error 316: The agent

operation failed

because the DPM

Protection Agent

service on the

specified server did

not respond.

Incorrect firewall

configuration

requirements on the

DPM server.

For firewall configuration requirements, in the DPM

Deployment Guide, see Installing Protection

Agents behind a Firewall



operation failed

because of a

communication error

with the DPM Agent

Coordinator service

on the specified

server.

Incorrect firewall

configuration

requirements on the

DPM server.


Operations Guide, see Managing DPM Servers



operation failed

because the DPM

Agent Coordinator

service on the

specified server did

not respond.

Incorrect firewall

configuration

requirements on the

DPM server.




Error 341:

Agent operation

failed because the

credentials provided

have insufficient

privileges on the

The account used does not have sufficient privileges on the server.

The system

Retry the operation with an account that has administrator privileges on the specified server.

Verify that system times on the DPM server and the server on which you are installing the agent are synchronized with the system time

19












specified server. times of the DPM server, the 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.

on the domain controller.

Verify that the DNS settings are correct.

Error 342:

The agent operation

failed because the

DPM server could

not communicate

with the specified

server.

Incorrect firewall

configuration

requirements on the

DPM server.




Error 347:

An error occurred

when the agent

operation attempted

to create the DPM

Agent Coordinator

service on <server

name>.

The production

server requires a

restart to install the

protection agent.

Install the protection agents manually. For more

information about manually installing protection

agents, see Installing Protection Agents Manually

(http://go.microsoft.com/fwlink/?LinkID=179676).

Error 348:

An error occurred

when the agent

operation attempted

to communicate with

the DPM Agent

Incorrect security

settings for the COM

object on the

computer.

Verify COM permissions on the server.

Verify that the DCOM configuration settings are set

as follows:

COM Security Default Access Permissions

Local Access and Remote Access permitted to

20




Coordinator service

on the specified

server.

Self

Local Access permitted to System

COM Security Machine Access Restriction

(Security Limits)

Local and Remote Access permitted to NT AUTHORITY\ANONYMOUS LOGON

Local and Remote Access permitted to BUILTIN\Distributed COM Users

Local and Remote Access permitted to \Everyone

COM Security Default Launch Permissions

Launch permitted to NT AUTHORITY\SYSTEM

Launch permitted to NT AUTHORITY\INTERACTIVE

Launch permitted to BUILTIN\Administrators

COM Security Machine Launch Restriction

(Security Limits)

Local Launch and Activate permitted to \Everyone

Local and Remote Launch, Local and Remote Activate permitted to BUILTIN\Administrators

Local and Remote Launch, Local and Remote Activate permitted to BUILTIN\Distributed COM Users

Error 271:

The user does not

have administrator

access.

- Or -

Error 377:

The agent operation

failed because the

minimum

requirements in the

DCOM configuration

were not met.

The DCOM

configuration settings

did not meet the

minimum

requirements.

Verify that DCOM is enabled. If DCOM is enabled,

verify that the DCOM configuration settings are set

as follows:

COM Security Default Access Permissions

Local Access and Remote Access permitted to Self

Local Access permitted to System

COM Security Machine Access Restriction

(Security Limits)

Local and Remote Access permitted to NT AUTHORITY\ANONYMOUS LOGON

Local and Remote Access permitted to

21


BUILTIN\Distributed COM Users

Local and Remote Access permitted to \Everyone

COM Security Default Launch Permissions

Launch permitted to NT AUTHORITY\SYSTEM

Launch permitted to NT AUTHORITY\INTERACTIVE

Launch permitted to BUILTIN\Administrators

COM Security Machine Launch Restriction

(Security Limits)

Local Launch and Activate permitted to \Everyone

Local and Remote Launch, Local and Remote Activate permitted to BUILTIN\Administrators

Local and Remote Launch, Local and Remote Activate permitted to BUILTIN\Distributed COM Users

System Error 1130:

Not enough server

storage is available

to process this

command.

- OR -

Event ID 2011: Not

enough memory to

complete the

transaction. Close

some applications

and retry.

The configuration

parameter

"IRPStackSize" of

the server is too

small for the server

to use a local device.

We recommend that you increase the value of this

parameter. See Microsoft Knowledge Base article

177078, "Antivirus software may cause Event ID

2011" (http://go.microsoft.com/fwlink/?

LinkId=73102).

The RPC server is

unavailable.

A firewall is enabled

on the remote

computer.

If a firewall is enabled on the remote computer on

which you are installing the protection agents,

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

22






SharePoint Services

farm back-end server

does not appear as

protected in DPM

Administrator

Console.

protection agent on a

back-end server to

protect a Windows

SharePoint Services

farm, the server does

not appear as

protected in the

Management task

area on the Agents

tab.

servers internally if the Windows SharePoint

Services farm has data on the server.

The protection agent

installation fails if you

are installing it on a

non-primary domain

controller running

Windows

Server 2003.

If the Primary

Domain Controller

(PDC) is running

Windows

Server 2000, the

required Distributed

COM Users group

will be missing.

To resolve this issue, upgrade the forest root PDC

emulator operations master role holder to

Windows Server 2003, and then perform the

protection agent installation again.

For more information, see Knowledge Base article

827016, "Local service and other well-known

security principals do not appear on your Windows

Server 2003 domain controller"


The application has

failed to start

because the

application

configuration is

incorrect.

The software

requirements must

be met on the

protected computer.

Install the .NET Framework 3.5 with Service

Pack 1 (SP1), and then try the protection agent

installation again.

Troubleshooting Remote SQL Server Issues

Troubleshooting Error ID 4307The 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,

23




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, 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

Server is in the incorrect format.

Make sure that the remote instance of SQL

Server is in the following format:

<Computer name>\<Instance name>

Note

Only use <Computer name> for the

default instance.

There is no network connectivity between the

DPM server and the computer running SQL

Server.

Make sure there is a connection between the

DPM server and the computer running SQL

Server.

24

Troubleshooting Data Protection Issues

This section includes troubleshooting assistance for data protection issues.

In This SectionGeneral 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

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

sources fail with agent

upgrade error.

The protection agent

on some members of

the cluster has not

been upgraded.

Upgrade the protection agent on all members of

the cluster.

Inconsistent drive

letter references in the

DPM New Protection

Group Wizard.

If you change a

volume drive letter

and then do not

restart the computer

before creating a

protection group for

that volume,

To display the correct drive letters in the New

Protection Group Wizard, you must refresh the

drive letters in SQL by performing the following

steps:

1. Remove the volume from the protection group, retaining the replicas.

2. Read the volume to the protection group.

25


inconsistent drive

letter references may

appear in the DPM

New Protection Group

Wizard.

DPM is no longer able

to communicate with

its protected

computers.

The DPM computer

may have been

temporarily disjoined

from the

Active Directory

domain to which it

previously belonged.

For example, the

DPM computer could

have been disjoined

because of a broken

workstation-domain

trust relationship.

When the DPM

computer is restarted,

it is rejoined to the

domain with the same

name but is assigned

a new Security

Identifier (SID). All

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.

To restore communication and resume data

protection activities, do the following:

1. Locally uninstall the protection agent from the protected computer.

2. On the DPM server, in DPM Administrator Console, in the Management task area, on the Agents tab, select the protected computer. In the Actions pane, click Refresh information.

The agent status changes to Error.

3. In the Details section, click Remove the record of the server from this DPM computer.

Reinstall the protection agent on the computer.

For instructions, in the Operations Guide, see

Managing DPM Servers


After you install a

protection agent on the

When you install a

protection agent, after

Wait 20 minutes after the computer restarts and

then run the DPM New Protection Group

26



computer and then

create a protection

group, you cannot

access any data

sources on the

computer.

the computer restarts

and is responsive to

the ping command, it

can take up to

20 minutes for the

protection agent to

respond to requests

from the DPM New

Protection Group

Wizard.

Wizard again, or try the following:

In DPM Administrator Console, in the Management task area, on the Agents tab, in the Actions pane, click Refresh information until the agent status changes to OK.

The recovery point

time is not consistent

with synchronization

time.

When a recovery

point is created, it

reflects the time of 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.

No action is required.

Synchronization jobs

fail and the details in

the application event

log include "Unable to

connect to

Active Directory."

The DPM server may

not have access rights

to update

Active Directory.

To troubleshoot this issue, do the following:

Retry the operation.

Check for network connectivity between the DPM server and the domain controller.

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.

27


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

not discover changes

to shares.

If a share on a

computer is protected

and the computer also

contains an

unsupported share,

then auto discovery

will fail to discover

changes to shares on

that computer, such

as new shares,

removed shares, and

share remappings.

No “pending members” will be discovered by

auto discovery for a computer with a protected

share if the computer also contains a share that

points to a destination in the following list of

unsupported shares:

FAT volume.

CD-ROM drive.

USB drive.

Mount point located inside another mount point.

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

increases after

choosing to compress

data for the protection

group.

Your tape hardware

may not allow the

tape backup

application to turn off

compression.

If your tape backup size increases after

selecting the Compress Data tape option in the

DPM New Protection Group Wizard, check your

protection group configuration for the 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,

28


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

backup fails because

your full tape backup is

not available.

- Or -

Your long-term backup

does not leverage the

latest tape backup that

was most recently

created.

If you are using tape

for both short-term

and long-term

protection, DPM

creates copies of the

latest short-term tape

full backup to

generate your long-

term tape backup.

To resolve this issue, when you create your

protection group, we recommend that you

schedule your short-term protection full backup

to run a day prior to your long-term protection.

This enables your long-term tape backup to

leverage the short-term tape backup that was

most recently created.

If you schedule the long-term tape backup to

run prior to the short-term tape backup, the

long-term backup will use the short-term full

backup of the previous week.

Data protection fails

when you are

protecting two domain

controllers.

If you are protecting

data on two domain

controllers and then

uninstall the

protection agent from

one of the domain

controllers, protection

will fail.

To restart protection, do the following:

1. On the protected server, from the command prompt, change the directory (CD) to <drive letter>:\Program Files\Microsoft Data Protection Manager\DPM\bin\.

2. Type SetDpmServer.exe -dpmServerName <DPM server name>.

Creating or modifying

a protection group

fails.

If the number of

recovery points

exceeds the number

that DPM has

provisioned, creating

or modifying a

protection group will

fail. In addition, you

cannot view the

number of recovery

points in DPM

Administrator

Console.

To view the number of existing recovery points,

do the following:

From the DPM Management Shell prompt, type

$dpm = Connect-DPMServer dpmoffice02

$dpm.CurrentShadowCopyProvision.

Replicas are marked

as inconsistent.

Once a volume is

marked as Missing,

DPM only brings the

volume back online

during the next disk

You must perform a manual consistency check.

For information about performing a consistency

check, in DPM 2010 Help, see How to

Synchronize a Replica

29




modification

operation, such as

Allocate disk space,

or after restarting the

computer. DPM then

marks the replica as

inconsistent.


Creating a protection

group fails when

protecting several

nodes in a cluster, and

the following error is

displayed:

"This item cannot be

protected because

some prerequisite

software is missing.

Ensure that all

prerequisite software

is installed and then

protect this item."

The software

prerequisites may not

be present on all

nodes in the cluster.

You must install the software prerequisites on

all nodes on the cluster that you are protecting.

For information about DPM prerequisite

software and the servers it protects, see

Protected Computer Requirements


Adding a DPM server

to a protection group

on the secondary DPM

server causes DPMRA

service to fail 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.

The name given to the

protection group on

the primary DPM

server contains

special characters.

Rename the protection group.

30



File Server Protection Issues

The following table provides troubleshooting guidance on file server data protection issues.

File Server Data Protection Issues


A Volume Missing

error occurs for some of

your protected server

volumes.

The DPM server

cannot identify the

volumes.

Perform the following steps to remove the

Volume Missing status.

1. In DPM Administrator Console, click 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

references in the DPM

New Protection Group

Wizard.

If you change a

volume drive letter

and then do not

restart the computer

before creating a

protection group for

that volume,

inconsistent drive

letter references may

appear in the DPM

New Protection

Group Wizard.

To display the correct drive letters in the New

Protection Group Wizard, you must refresh the

drive letters in SQL by performing the following

steps:

1. Remove the volume from the protection group, retaining the replicas.

2. Read the volume to the protection group.

The recovery point time

is not consistent with

synchronization time.

When a recovery

point is created, it

reflects the time of

the most recent

change to the

protected volume.

For example, if a

recovery point is

scheduled to be


31


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.

Replicas are marked as

inconsistent.

Once a volume is

marked as Missing,

DPM only brings the

volume back online

during the next disk

modification

operation, such as

Allocate disk space,

or after restarting the

computer. DPM then

marks the replica as

inconsistent.

You must perform a manual consistency check.

For information about performing a consistency

check, in DPM 2010 Help, see How to

Synchronize a Replica



The following table provides troubleshooting guidance on protection issues for computers running

Exchange Server.


Issue Possible Cause Details

Exchang

e Server

data is

unavaila

ble for

protectio

n.

Before you can protect

Exchange Server 2007

data, you must install

hotfix 940006. For more

details, see Knowledge

Base article 940006,

"Description of Update

The following versions of Exchange Server must be

installed on the computer that you want to protect:

Exchange Server 2003 with Service Pack 2 (SP2)

- Or -


Important

32





Rollup 4 for Exchange

2007"

(http://go.microsoft.com/f

wlink/?LinkId=99291).

To protect Exchange Server data, the Exchange

Server databases must be mounted within each

storage group.

DPM

cannot

protect

Exchang

e Server

data.

The eseutil.exe and

ese.dll versions that are

installed on the most

recent edition of

Exchange Server must

be the same versions

that are installed on the

DPM server.

You must update eseutil.exe and ese.dll on the DPM

server if they are updated on a computer running

Exchange Server after applying an upgrade or an update.

For more information about updating eseutil.exe and

ese.dll, in the DPM 2010 Deployment Guide, see Protected

Computer Software Requirements.

After you

rename

an

Exchang

e Server

storage

group,

the new

name

does not

appear

in the

DPM

New

Protectio

n Group

Wizard.

If you use the original

storage group name,

data recovery fails when

trying to dismount the

database.

After you rename an Exchange Server storage group, you

must restart the Microsoft Exchange Information Store

service before you create a new protection group.

To start the Microsoft Exchange Information Store

service

1. Click Start, point to Administrative Tools, and then click Services.

2. On the Services screen, scroll down and right-click Microsoft Exchange Information Store, and then click Restart.

DPM 20

10 does

not

support

increme

ntal

backups

if circular

logging

is

enabled

You cannot enable

circular logging if you

want incremental

backups for Exchange

Server storage groups.

For successful incremental backups, we recommend that

you disable circular logging for the protected storage

group. After you disable circular logging, restart the

Microsoft Exchange Information Store service

(MSExchangeIS).

To disable circular logging

1. Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager.

2. If the Administrative Groups branch exists in the left pane, expand it, expand the appropriate administrative group's branch, expand the Servers branch, and then

33






for

Exchang

e Server

storage

groups.

expand the appropriate server's branch.

If the Administrative Groups branch does not exist,

expand the Servers branch in the left pane, and then

expand the appropriate server's branch. To expand a

branch, double-click the branch or click the plus sign

(+) 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 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

initializati

on and

express

full

backup

operatio

ns stop

prior to

completi

on.

When you are protecting

data on a computer

running a version of

Exchange Server, the

DPM server must include

the Ese.dll and

eseutil.exe files that are

located in the Exchange

Server installation

location.

To protect data on a computer running Exchange Server,

perform the following steps:

1. On the computer running Exchange 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.

2. Cancel the replica initialization and express full 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.

34


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 VSS

writer

does not

clear

Backup

in

progres

s state

for the

storage

group.

In Exchange

Server 2007 RTM and


RTM, if you cancel the

backup on a storage

group within a particular

interval (between

PrepareForBackup and

DoSnapshot), the VSS

writer does not clear

Backup in progress

state for the storage

group.

To recycle the VSS writer for:

Event ID 2024 A: Restart the Microsoft Exchange

Information Store service to recycle the VSS writer.

Event ID 2024 B: Restart the Exchange Server Replication

service (Exssrv.exe) to recycle the VSS writer.

The

Microsoft

Exchang

e

Informati

on Store

service

does not

appear

on the

Select

Group

If the Exchange Local

Continuous Replication

(LCR) VSS replica writer

is enabled, the Microsoft

Exchange Information

Store service will not

appear on the Select

Group Members page

of the New Protection

Group Wizard.

To display the Exchange LCR-enabled storage groups in

the DPM New Protection Group Wizard, use the following

set key command to disable the (LCR) VSS replica writer:

set key EnableVssWriter under

HKLM\Software\Microsoft\Exchange\Replay\Parameters to

0

DWORD type

Note

After setting the registry key, you must restart the

Microsoft Exchange Server Replication service.

35


Member

s page

of the

New

Protectio

n Group

Wizard.

All data

replicatio

n jobs

fail.

If the versions of

Exchange Server

Database Utilities

(eseutil.exe) and ese.dll

that are installed on the

most recent edition of

the protected Exchange

Server are different from

the versions that are

installed on the DPM

server, all data

replication jobs will fail.

The eseutil.exe and ese.dll versions that are installed on

the most recent edition of Exchange Server must be the

same versions that are installed on the DPM server. For

example, if you are protecting Exchange Server 2003 SP2,

Exchange Server 2007, and Exchange Server 2007 SP1,

you must copy eseutil.exe and ese.dll from the server

running Exchange Server 2007 SP1 to the DPM server.

The following scenarios show the versions of eseutil.exe

and ese.dll that you must install on the DPM server:

32-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 computers running Exchange Server 2007, the 32-bit versions of eseutil.exe and 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.

Exchang

e Server

protectio

n fails.

If the Exchange writer is

turned off for the Volume

Shadow Copy service in

Windows Small Business

Server 2003, protection

will fail.

By default, the Setup program for Windows Small Business

Server 2003 turns off the Microsoft Exchange Server 2003

writer for the Volume Shadow Copy service. To protect

data using DPM 2010, the Exchange Server 2003 writer

must be turned on.

For more information about this issue, see Knowledge

36


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\

CurrentControlSet\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.


7. Stop and then restart the Microsoft Exchange Information Store service.

Local

continuo

us

replicatio

n (LCR)

protectio

n fails

with a

VSS

error.

If the Exchange Server

replication service is not

restarted after the

registry key is set, LCR

fails for the storage

group.

Restart the replication service after updating the registry

key.

Setting

and

unsetting

the

eseutil

flag

through

the

comman

d line

The preferred server

may not have been

specified.

Provide the topology as PT_CCR_ACTIVE_ONLY along

with the RunEseUtilConsistencyCheck option.

37





interface

(CLI)

fails.

ID

30112:

DPM

encount

ered a

retryable

VSS

error

(0x8004

23F3).

The next incremental

backup fails when an

incremental backup is

performed after you run

ntbackup on the storage

group.

Create a DPM full recovery point before performing an

incremental backup.

The

consiste

ncy

check

fails with

RMGene

ricError.

The consistency check

will fail if indexing,

encryption, or Single

Instance Storage (SIS) is

enabled for the folder

containing the .edb file.

To resolve this issue, disable indexing, encryption, and SIS

for the folder containing the .edb file.



SQL Server.



Sched

uled

SQL

Server

protect

ion

jobs

not

startin

Resources on the protected computer are

unavailable and hence SQL Server agent

is not able to start.

Restart the computer.

38


g.

DPM

is

unable

to

protect

a SQL

Server

databa

se.

You must have the required software

installed to protect a computer running

SQL Server.

The following versions of SQL Server must

be installed on the instance of SQL Server

that is hosting the database that you want

to protect:

SQL Server 2000 with Service Pack 4 (SP4)

- OR -

SQL Server 2005 with Service Pack 2 (SP2)

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


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

SQL

Server

If you are protecting SQL Server 2005 on a

Windows Server 2008 operating system,

For information about running editions of

SQL Server on Windows Server 2008, see

Running SQL Server on Windows Server

39



VSS

Writer

servic

e fails

during

protect

ion.

you must install SQL Server 2005 SP2. 2008 R2 or Windows Vista

(http://go.microsoft.com/fwlink/?

LinkId=130555).

The

SQL

Server

databa

se

backu

p fails.

If you physically delete one of the database

files from the SQL Server and do not

remove it from the database, the SQL

Server VSS Writer Service will continue to

report the deleted file and DPM will not be

able to locate it while performing backups.

Delete the database log files using the

following query:

ALTER DATABASE <file name>.mdf

REMOVE FILE <file name>_log.ldf

Note that you will not be able to restore to

the original location from the backups that

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

you

perfor

m an

inquiry

job in

the

DPM

New

Protec

tion

Group

Wizard

, such

as

viewin

g a list

of data

source

s, if

two

differe

This can occur in the following scenario,

where you have two SQL Server VSS

writers: SqlServerWriter and MSDEWriter.

You install an instance of SQL Server 2005. (The SQL Server VSS Writer Service is turned off by default)

Because the SQL Server VSS Writer Service is turned off, the MSDEWriter writer enumerates the SQL Server 2005 databases.

You turn on the SQL Server VSS Writer Service in the Service Control Manager, which sets the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Settings\MSDEVersionChecking registry key value to 1.

After the registry key value is set to 1, the MSDEWriter writer stops enumerating the SQL Server 2005 databases, and the SQLServerWriter writer starts enumerating them.

To resolve this issue, you must set the

value of the HKEY_LOCAL_MACHINE\

SYSTEM\CurrentControlSet\Services\VSS\

Settings\MSDEVersionChecking registry

key to 1 (a non-zero value), so the

MSDEWriter is the only writer that

enumerates the SQL Server 2005

databases.

40




nt SQL

Server

VSS

Writer

s are

enume

rating

the

same

data

source

, the

DPM

server

will

crash.

You then set the value of the registry key to

zero (0), which causes both the

MSDEwriter and SQLServerWriter writers

to start enumerating the SQL Server 2005

databases.

Datab

ase

protect

ion on

an

instan

ce of

SQL

Server

2005

fails.

If you are protecting a database on an

instance of SQL Server 2000 and then

upgrade to SQL Server 2005, database

protection on the instance of SQL

Server 2005 will fail.

After you upgrade to SQL Server 2005 and

then restart the SQL Server VSS Writer

service, DPM will not map the existing

replica to the protected database. This is

because the new VSS writer enumerates

the new database, and therefore DPM

recognizes it as a new data source.

If this issue occurs, we recommend that

you stop protection for the database that is

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

41


name.

No data loss occurs with this issue.

SQL

Server

2000

databa

se

replica

creatio

n job

fails

runnin

g on a

64 bit

compu

ter.

Replica creation jobs may fail on a SQL

Server 2000 database running on a 64-bit

computer in Windows in Windows (WOW)

mode.

If a replica creation job fails on a SQL

Server 2000 database running on a 64-bit

computer in Windows (WOW) mode, check

the event viewer on the SQL Server

computer for Event ID 20 "Volume Shadow

Copy Service error."

For information about a supported hotfix to

correct this issue, see Event ID 20


LinkId=73718).

SQL

Server

full

transa

ction

log

cause

s

synchr

onizati

on job

failure

s.

If the database transaction log

unexpectedly becomes full on a computer

that is running SQL Server, your

synchronization jobs will start to fail.

For information about how to resolve this

problem, see Microsoft Knowledge Base

article 317375, "A transaction log grows

unexpectedly or becomes full on computer

that is running SQL Server

"(http://go.microsoft.com/fwlink/?

LinkId=72730).

DPM

protect

ion

jobs

start to

fail.

If DPM is protecting a SQL Server

database that is using mirroring or log

shipping, after a failover the protected

primary database will no longer be online

and your DPM protection jobs will start to

fail.

If you plan to fail-back to the primary

database, do the following:

After your protection jobs start to fail and the replica is no longer valid, perform a consistency check.

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

42





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, 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.

Increm

ental

synchr

onizati

ons

fail for

the

SQL

Server

master

databa

DPM does not support configuring

incremental synchronizations for SQL

Server master databases.

DPM allows log backups for databases

configured in the full and bulk-logged

recovery models. However, log backups

cannot run against the SQL Server master

database.

Additionally, do not set the synchronization

frequency for the master database to "just

before a recovery point," because there

are no backup logs to obtain from the

protected server during the recovery.

43


se.

DPM

is not

protect

ing

SQL

Server

2005

databa

ses.

SQL Server 2005 includes database

snapshots that appear in the New

Protection Group Wizard as regular

databases. However, DPM does not

support protecting database snapshots for

recovery.

You can view database snapshots in the

Microsoft SQL Server Management Studio

in the Database Snapshots folder.



Windows SharePoint Services.



The SQL Server alias

did not resolve on the

SQL Server Agent and

protection for the

Windows SharePoint

Services farm fails.

The Windows

SharePoint Services

farm is unable to use

a SQL Server alias

that was created by

using cliconfg.exe.

You must reconfigure the SQL Server alias by

using the SQL Server Configuration Manager.

Not all the SQL

Server aliases are

configured on the

front-end Web server.

Check the list of servers on the Central Admin

page of the SharePoint farm. Identify the SQL

Server aliases from the list of SQL Server

computers. Verify if all the SQL Server aliases

have been configured on the SharePoint front-

end Web server (the one that communicates

with the DPM server).

The SQL Server alias

is not of type TCP/IP.

DPM supports only TCP/IP SQL Server aliases.

Reconfigure the aliases to type TCP/IP.

SQL Server client

connectivity

components are not

Install the SQL Server client connectivity

components on the front-end Web server.

44


installed on the front-

end Web server.

For Windows

SharePoint Services

3.0/MOSS 2007

farms, SQL Server

2005 client

connectivity

components are not

installed on the front-

end Web server.

Irrespective of the version of SQL Server on the

back-end servers, for MOSS 2007 and

Windows SharePoint Services 3.0, you should

install the SQL Server 2005 client connectivity

components on the front-end Web server. Also,

ensure that all the aliases are configured using

this version of the client connectivity

components.

Windows SharePoint

Services database log

files are not truncated.

If the path to any

Windows SharePoint

Services database

log file exceeds 150

characters, DPM

cannot truncate the

log file.

We recommend running periodic scripts to

truncate your Windows SharePoint Services

database log files.

The Copy-Only

registry value has

been set for the

specific SharePoint

farm on the DPM

server.

This registry entry needs to be deleted. It can

be found under the following path on the DPM

Server: “HKLM\Software\Microsoft\Microsoft

Data Protection Manager\CopyBackups” with

the name equivalent to the name of the Config

database of the farm.

The “Do not truncate

logs” setting has

been enabled for the

SQL Server computer

on which the

SharePoint

databases reside.

This can be reset by using the following

Windows PowerShell command: Set-DPMGlobalProperty -Dpmserver $DPMMachineName -TruncateSharePointDbLogs $true.

The server process

could not be started

because the configured

identity is incorrect.

Check the username

and password

(0x8000401A).

If the password is

reset for the Windows

SharePoint Services

farm, protection will

fail.

From the command prompt, run

ConfigureSharePoint.exe to reset the

password.

For more information about how to manage

password changes, see How to change service

accounts and service account passwords in

SharePoint Server 2007 and in Windows

SharePoint Services 3.0

45






Replica Inconsistent

alerts for one or more

SQL Server databases

that were earlier a part

of the SharePoint farm

appear in the

Monitoring pane.

DPM retains the

existing recovery

points of the

databases that have

been removed from

the SharePoint farm.

This can happen if

the removed

database is

recovered by using

DPM or if DPM has

been upgraded.

Resolve the alert by clicking Inactivate the

alert.

Some of the

SharePoint farm’s

consistency check jobs

appear to have

stopped (no data

transfer has occurred

for a long time).

The consistency

check was triggered

while recovery of one

of the farm’s

components was in

progress.

Cancel the consistency check job and restart

the consistency check for the farm from the

Protection pane.

The SharePoint catalog

task fails with HR

0x80004003 (Invalid

Pointer)

There is a network

connectivity issue

between the

SharePoint front-end

Web server and the

back-end server.

Rerun the catalog job by using Windows

PowerShell.


The following table provides troubleshooting guidance for Windows Server Backup (WSB) issues.



When using WSB, the following

errors might occur:

DPM has detected a discontinuity in the log chain

Performing backups using

WSB on a server which DPM

is protecting can interfere with

the backups DPM uses.

If you are using WSB, do the

following:

Ensure that WSB always takes a COPY backup

46


for <DatasourceType> <DatasourceName> on <ServerName> since the last synchronization.

The recovery to the latest point in time failed. During a recovery to the latest point in time, DPM attempts to perform a SQL Server transaction log backup to receive the latest changes from the SQL Server database <DatasourceName> on <ServerName> before 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.

using the WSB Backup Once Wizard.

If you are using WSB Scheduled Backups, ensure that the volumes you are backing up do not contain any application data such as Exchange Server data or SQL Server data.

After you reconfigure WSB, on the DPM server, run a new express full backup.


The following table provides troubleshooting guidance for system state protection issues.


47


Bare Metal Recovery (BMR)

backups fail with “Access

Denied” error.

You have just migrated

from System State

protection to BMR

protection.

1. Remove BMR protection.

2. Modify protection group and include BMR protection.

One or more prerequisites

for protecting this data

source is missing on your

Windows Server 2008

operating system.

This error occurs if the

Windows Server Backup

utility is not installed on the

protected server.

To resolve this issue, do the

following:

1. To install the Windows Server Backup utility, open a command 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

could not be started

because the configured

identity is incorrect.

Check the username

and password

If the password is

reset for the

Windows SharePoint

Services farm,

protection will fail.

From the command prompt, run

ConfigureSharePoint.exe to reset the

password.

For more information about how to manage

password changes, see How to change service

accounts and service account passwords in

48




(0x8000401A). SharePoint Server 2007 and in Windows

SharePoint Services 3.0




Microsoft Virtual Server.



You may see the

error One or

more volumes

are missing for

the following

application:

<Virtual

machine

name>. Ensure

that the

dependent

volumes for the

data sources

are online. when

you select a

Virtual

Server 2005 R2

based virtual

machine.

For Virtual

Server 2005 R2,

DPM does not

support backing

up virtual

machines hosted

on a volume that

does not have a

drive letter.

Note

This

problem

does not

apply to

Hyper-V

virtual

machines

.

Provide a drive letter mount point for the volumes on

which the VHD files exist and attempt to select for backup

with DPM again.

Data on the

virtual machine is

unavailable for

protection.

Virtual

Server 2005 R2

Service Pack 1

(SP1) may not be

installed on the

server you want

to protect.

Install Virtual Server 2005 R2 Service Pack 1 (SP1) on

the server that you want to protect.

49




Backup fails on

the virtual

machine with

unknown

error 0x800423f3

.

The Virtual

Server VSS

Writer service

does not support

online backup for

the client virtual

machine.

Use Windows Event Viewer on the Virtual Server machine

to find if Event ID 1044 exists. If this event exists, the

virtual machine cannot perform online backups.

You can perform offline backups by updating the following

registry key:

Set HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\

Virtual Server\1.0\Backup\BackupType\<VMNAME>

to 0.

Online backup

fails.

Online backups

fails if the virtual

machine contains

volumes that do

not support

shadow copies

(FAT 32 file

systems).

Additionally, if the

shadow copies

exist on different

virtual machine

volumes, the

backup fails.

Install Knowledge Base article 940349 “Availability of a

Volume Shadow Copy Service (VSS) update rollup

package for Windows Server 2003 to resolve some VSS

snapshot issues”

(http://support.microsoft.com/kb/940349) on the virtual

machine.

Ensure that the virtual machine is running before

configuring the backup, and then delete the entries for the

virtual machines for which the online backup is failing. Set

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\

Virtual Server\1.0\Backup\BackupType.


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

50

http://go.microsoft.com/fwlink?linkid=33686


incorrect directory creates an

incorrect replica hierarchy.

the location that is specified in

the Properties pane in DPM

Administrator Console when

you select manual replica

creation. If you transfer the

data to an incorrect location,

you can use FsPathMerge to

move the data or you can

delete the replica data and

create the replica again.

synchronization with

consistency check, you need

to do the following:

Remove the protected volume or share from the protection group and choose to delete the replica.

Add the volume or share to the protection group.

Manually create the replica again.

In the case of an incorrect

replica hierarchy,


consistency check can

potentially synchronize the

entire replica over the network

from the file server, consuming

valuable network bandwidth

and CPU resources.

Re-creating junction points

rather than using existing

junction points.

This issue occurs when you

use a tape backup that was

created from a DPM server. If

you do not choose to use

existing junction points during

the restore operation, data

may be restored to the

incorrect path.

If this occurs, manually delete

the data and the path, and

then manually create the

replica again.

Failing to restore security

settings when you restore the

data.

The backup of the data

includes the security settings

of the source data. If you

restore the data from the

backup without restoring the

security settings, the correct

access control lists (ACLs) will

not be configured on the files

and folders.

Wait until synchronization with

consistency check completes

successfully. Incorrect replica

data security settings can

allow nonprivileged users to

have access to the data.

Failure to restore the security

settings also means that


consistency check will take

longer to complete and

51


transfer more data over the

network.

Incorrect time stamps cause


consistency check to take

longer to complete.

Changing the file and folder

time stamps because of user

error or by-design behavior of

the backup software causes


consistency check to take a

long time to complete. For

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.

Do not set the time stamp of

restored files and folders to the

restore time. We recommend

that you use 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


If the WIM FS Filter driver

(Wimfltr.sys) is installed on the

protected server, an incompatible

filter error occurs.

Perform the following steps to continue protection.

1. On the protected server, browse to the registry path HKLM\Software\Microsoft\Microsoft Data Protection 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

protection for data sources on

the protected server because it

has detected an incompatible

filter.

Perform the following steps to continue protection:

1. On the protected server, browse to the application event log to check for events from the DPMRA service that indicate the name of the incompatible filter.

2. If there are no incompatible filters listed in the event log,

52


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\Microsoft 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.


Issue Possible Cause Solution

Missing recovery points If a scheduled recovery point

creation and a

synchronization/consistency check

from a client run concurrently, the

recovery point will get skipped.

To avoid losing a recovery point

for such clients, schedule

additional recovery point

creation at low usage times so

that client computers that

missed the recovery point

creation will get a recovery

point later.

Backups of client

computers connected to

corporate network

through DirectAccess fail

Edge traversal is blocked in the

firewall settings.

1. Launch the Windows Firewall console (Start -> Run -> firewall.cpl).

2. Click Advanced settings

53

Issue Possible Cause Solution

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

synchronize changes for

Microsoft Hyper-V \Backup

Using Child Partition

Snapshot\<<VM Name>> on

<<Resource Group>>

because the snapshot volume

did not have sufficient storage

space to hold the churn on the

protected computer (ID 30115

Details: Unknown error

(0x8004231f) (0x8004231F))

Insufficient

storage in

snapshot

pool.

Verify that the SAN has enough available storage to

create hardware snapshots.

DPM error: 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.

Auto-

mounting

of volumes

might not

be

enabled

Enable auto-mounting by using the following

command: Mountvol /E

54


(ID 30111 Details: Unknown

error (0x800423f4)

(0x800423F4))

VMMS event: No snapshots to

revert were found for virtual

machine 'CSVVM02'. (Virtual

machine ID 4774EF60-F4B6-

47D6-A0B9-60452C6B7FE8)

on the

protected

computer.

DPM error: 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))

The

hardware

provider

has

vetoed

snapshot

creation.

This is potentially a configuration issue. Check the

application event logs for VSS hardware provider

events and validate the storage configuration with

your SAN vendor.

The operation failed for

Microsoft Hyper-V \Backup

Using Child Partition

Snapshot\Win7.01 on

Win7.01.dpmcsv1.DC505.LAB

because the data source is

not available. (ID 30169


(0x80042308) (0x80042308))

Live

migration

caused

the virtual

machine

to move to

another

node while

the

backup

was in

progress.

Cluster

disks are

in a bad

state.

Data

source

was

deleted.

1. Rerun the backup job.

2. Diagnose the storage volume for the virtual machine.

For information about how to back up virtual

machines on CSV, in the DPM 2010 Operations

Guide, see Considerations for Backing Up

Virtual Machines on CSV with the System VSS

Provider (http://go.microsoft.com/fwlink/?

LinkId=196939).

DPM error: Failed to prepare

a Cluster Shared Volume

Too many

parallel

For information about how to enforce serial

backups, in the DPM 2010 Operations Guide, see

55





(CSV) for backup as another

backup using the same CSV

is in progress. (ID 32612


(0x8007173d) (0x8007173D))

backups

are

competing

for the

same CSV

LUN.

Considerations for Backing Up Virtual Machines on

CSV with the System VSS Provider


DPM error: An unexpected

error occurred during job

execution. (ID 104 Details:

Element not found

(0x80070490))

There

might be a

failed disk

in the

cluster.

Repair or remove the failed disk in the cluster.

Backup of Hyper-V virtual

machines are stalled and no

data transfer is happening.

TCP

Chimney

Offloading

maybe

active.

Run netsh int tcp set global chimney=disabled to disable TCP Chimney

Offloading.

Troubleshooting Data Recovery Issues

This section includes troubleshooting assistance for data recovery issues.

In This SectionGeneral Data Recovery Issues

Exchange Server Recovery Issues

SQL Server Recovery Issues

Windows SharePoint Recovery Issues

Tape Library Recovery Issues

End-User Recovery Issues

General Data Recovery Issues

The following table provides troubleshooting guidance for general data recovery issues.

General Data Recovery Issues

56




The Recovery Wizard

Summary page does not

display the details of the

recoverable items.

If you selected data to restore

at the item level, the Recovery

Wizard Summary page will

not display the details of the

recoverable items.

Item details will not appear on

the Recovery Wizard

Summary page for the

following:

Windows SharePoint 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

the same time a disk-to-tape

(D2T) short-term protection job

is scheduled to run, the

recovery will fail.

DPM will cancel a D2T short-

term protection job if it is

running at the same time you

are performing a recovery.

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

when trying to

mount or dismount

the Exchange

Server database.

If you rename

an Exchange

Server storage

group after

protecting it,

when DPM

The caption of the Exchange Server storage group is

used to mount and dismount the Exchange Server

databases. If you rename the storage group, the caption

stored in the protected object will be different from the

actual caption and the mount and dismount operations

will fail. If this occurs, we recommend that you do the

57


performs a

recovery

operation, the

recovery will fail

when trying to

mount or

dismount the

database.

following:

Rename the storage group back to the original storage group name.

When you detect a name change, update the caption name in the protected object.

You can use the component name to identify a storage group to mount and dismount the databases under it instead of the caption name.

ID 104: An

unexpected error

occurred during job

execution.

Exchange

Server 2007

requires

credentials of

an Exchange

Server

administrator

for dismounting

or mounting the

database.

The DPM

replication

agent requires

Local System

account

privileges, and

therefore,

recovery fails

when trying to

recover data on

an Exchange

Server 2007

server that is

configured for

clustered

continuous

replication

(CCR).

Perform the following steps to provide the user with the

Exchange Server Administrator privileges:

1. From the command prompt, type dcomcnfg, and then click OK.

2. On the Component Services screen, expand Component Services, expand Computers, expand My Computer, and then click DCOM Config.

3. Right-click ExchangeCmdletsWrapper, and then click Properties.

4. In the Properties dialog box, on the Identity tab, select This user.

5. Provide the credentials for the account that has Exchange Server Administrator privileges, and then click OK.

Recovery to the

latest

Programmable

Interval Timer (PIT)

If the

embedded

database (.edb)

and the

Dismount and remount the databases, and then retry the

recovery. If you cannot dismount and remount the

databases, restore the files and then copy them with a

clean shutdown. Then move the files to the original

58


fails. streaming

(.stm) files are

renamed and

then the

databases are

not dismounted

and then

remounted, the

recovery fails.

location and mount the database.

Mailbox recovery

fails with a

catastrophic error

when recovering to

an alternate

Exchange

Server 2003

database.

The restore flag

was not set

when

attempting to

recover a

mailbox to an

alternate

Exchange

Server 2003

database.

After the recovery fails, go to the Exchange Server

Management Console, set the recovery flag, and then

mount the database.

The Recover-

RecoverableItem

cmdlet fails

specifying that the

specified recovery

options were not

valid.

If you specify

the active

server name

when

recovering a

storage group

or database for

Exchange

Server

Clustered

Continuous

Replication

(CCR) through

the command-

line interface

(CLI), the

recovery fails.

The –TargetServer attribute should be

ResourceGroupName.ClusterServerName.DomainName.

eseutil execution

fails with error code

0xfffff764 in the

Application log.

This error

occurs if

the .stm

and .edb files

To bring the database to a Clean Shutdown state, move

the .stm file to the same folder as the .edb file, and then

run eseutil with the appropriate parameters.

59


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

database by selecting the

latest recovery point and then

perform another recovery

using the latest recovery

point, the database recovery

will fail.

When you recover a SQL Server

database using the latest

recovery point, DPM performs

the recovery using the SQL

Server logs that are available on

the protected server. After you

recover the database, you

cannot perform another 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.

60


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

SharePoint

Server 2007 – Unable

to see recovered list

item.

The item may still be in

the site or site

administrator’s Recycle

Bin.

We recommend that you recover the item

from the site or site administrator’s Recycle

Bin, if it is the same version of the file that you

are looking for, rather than recover it from the

replica. Alternatively, clear both the Recycle

Bins in SharePoint and then retry the

recovery.

Microsoft Office

SharePoint

Server 2010 –

Recovering list item

does not recover its

permissions.

The item already exists

in the list, or is in either

the user’s Recycle Bin

or the site

administrator’s Recycle

Bin.

If you are recovering an item that already

exists in either the user’s or the site

administrator’s Recycle Bin, DPM will restore

a duplicate item and apply the parent folder’s

permissions. However, if the item has been

deleted from all Recycle Bins, then it will be

restored along with the permissions.

Recovery points are

not displayed for sites

or documents in DPM

Administrator Console

in the Recovery task

area. (If you double-

click the content

databases, the sites

do not appear.)

DPM backs up the

databases and then

performs a catalog task

to get a list of all the

URLs in the content

databases. By default,

this process runs three

hours after the first

scheduled backup job

of the day. If the catalog

Run the catalog task.

61


task has not completed,

you will not be able to

expand the content

database in the DPM

Recovery UI.

After recovering a

Windows SharePoint

Services farm, you

cannot attach a

content database.

If you recover a

Windows SharePoint

Services farm that had

a detached database

prior to recovery, you

cannot attach the

database after the

recovery if the front-end

Web server was

different than the

database DPM used for

the recovery.


Delete the config cache on the front-end Web server that was not used for the recovery.

The cache is a set of XML files located in

the following folder: <drive letter>:\

Documents and Settings\All Users\

Application Data\Microsoft\SharePoint\

Config\<config database ID>.

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

Windows SharePoint

Services farm fails.

If a Quick Fix

Engineering (QFE) is

installed after the

Windows SharePoint

Services farm is

protected, the recovery

will fail.


1. Recover the Windows SharePoint Services farm by using the Recovery Wizard.

2. On the front-end Web server, from the command prompt, type psconfig -cmd upgrade -wait -force -inplace b2b.

Consistency check

fails with "Data source

not found".

If you perform a

recovery after the

content database is

deleted from SQL

Server Management

Studio, and not through

the Sharepoint

Console, the

consistency check will

fail.

You must stop protection, and then use the

New Protection Group Wizard to reprotect the

Windows SharePoint Services farm.

Permissions or ACLs

for the document or list

The document or list

item is being restored to

DPM recovers the permissions or ACLs only if

the item is being restored to the original

62


item have not been

restored.

an alternative URL

within the same farm.

location.

Recovering a

SharePoint content

database to its original

location fails.

The recovery point is

located on the tape and

the database has been

removed from the

SharePoint farm.

Recover the database by using the “Recover

to any SQL Instance” option.


The following table provides troubleshooting guidance on tape library recovery issues.



Tape read errors occur when

attempting to recover a file

server volume from tape.

File server data source

recovery from tape will fail if

there are corrupt files on the

tape.

If tape read errors occur, do the

following:

1. Select the contents of the 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.

63


The following table provides troubleshooting guidance on end-user recovery issues.



End-user

recovery (EUR)

configuration fails on

Windows Server 2008.

Try either one of the following solutions:

Copy DPMADSchemaExtension.exe from DPM install folder to the active directory 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

recovery functionality on

your DPM server and

then try to recover an

earlier version of a file or

folder from your

computer, your

computer automatically

tries to recover the file

or folder from the DPM

server.

This issue occurs if

the computer is

secured by DPM or

if there are no local

shadow copies of

the file or folder on

the computer.

To resolve this issue, you must download

Microsoft Knowledge Base article 903234 to

update the Timewarp client on the client

computer. To download article 903234, see An

update is available to the way that the Shadow

Copy Client accesses shadow copies in

Windows Server 2003 and in Windows XP


Computers in Workgroups and Untrusted Domains Recovery Issues

Computers in Workgroups and Untrusted Domains Recovery Issues


Protection agent

refresh fails after

system state recovery

Password set for

protection was

updated after the

Reset the password.

For more information, in the DPM 2010

Operations Guide, see Updating Password for

64






of protected computer. system state of the

protected machine

was backed up.

Workgroup or Untrusted Computers


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

added to the firewall.

Add the following exceptions to

the firewall on the DPM server:

SqlBrowser

SqlServer

Windows Management Instrumentation

Tape is written by a non-DPM

application using a physical block

size either less than 1024 bytes

or more than 65536 bytes.The

tape in <LibraryType> <Library>

at <MediaLocationType>

<MediaLocationInfo> has been

written to by another tape backup

application using an unsupported

physical block size.

DPM only supports

reading 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.

To resolve this issue, do the

following to erase the contents

of the tape:

In DPM Administrator Console, in the Management pane, on 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

standalone tape

drive, you might

have to erase the

tape using a tool

65




other than DPM.

A new tape library or stand-alone

tape drive does not appear in

DPM Administrator Console.

After performing the

Rescan operation, DPM

Administrator Console

cannot identify a new tape

library or stand-alone tape

drive on the DPM server.

After you install a new tape

library and then perform the

Rescan operation, if the tape

library does not appear on the

Libraries tab in the

Management task area of DPM

Administrator Console, do the

following:

Ensure that the tape library and drives are properly 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,

66


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

removing a tape that was stuck in

the tape library.

The library jobs fail

because Media Manager

continues to report the

nonexisting tape in the

drive.

To update the DPM library

information, do the following:

1. Properly remove the tape from the drive by following the recommended procedures of the tape 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 cannot

find the Quantum tape drive in the

Qualstar tape library.

If you are using the

incorrect drivers for the

Quantum tape drive, DPM

Library Management

cannot find it because the

drive was not initialized

and configured.

We recommend that you run

Ltotape.sys for the Quantum

LTO drives.

A new tape does not appear in

DPM Administrator Console.

After you add a new tape

to your tape library without

using Unlock library

door or Add tape

(IEPort), the new tape

might not appear in the

DPM Library Management

task area.

To display the new tape, do the

following:

1. In DPM Administrator Console, click Management on the taskbar.

2. On the Libraries tab, in the Actions pane, click Inventory library.

3. In the Inventory dialog box, select Fast inventory, and

67


then click Start.

A tape does not appear in the

Library Management task area.

If you run a detailed

inventory on the tape

library after inserting a

tape, the tape does not

appear in the Library

Management task area.

To display the tape in the Library

Management task area, insert

the tape in the tape library and

then do the following:

1. In DPM Administrator Console, click Management on the navigation bar.

2. On the Libraries tab, select the tape library.

3. In the Actions pane, click Inventory.

4. In the Inventory dialog box, select Fast inventory, and 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

inserted tape.

In DPM Administrator

Console, if you run a

detailed inventory, it will

not detect inserted tapes

that are new.

You must first run a fast

inventory, which detects any

tape (with or without a bar code)

in any library.

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


E-mail functionality

for reports is not

1. The Reporting Services Service Account should be changed to run under a domain

68


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 DPM\SQL\MSRS10.MSDPM2010\Reporting Services\ReportServer\rsreportserver.config. Change the SMTP Authenticate tab to 2.

You subscribe to five

reports for e-mail

delivery, but not all

reports are delivered.

If you schedule all five

reports to be sent at

the same time, the

memory limitations of

SQL Server Reporting

Services may prevent

some reports from

being sent.

When a DPM server is protecting a large

number of file servers, we recommend that you

stagger the delivery schedule for reports sent by

e-mail.

Reports are not

received by

designated e-mail

recipients and DPM

does not generate

any errors.

This issue is most

commonly caused

when the security

settings of the recipient

e-mail address restrict

e-mail delivery. This

could happen, for

example, if the

recipient e-mail

address is a

distribution group

Depending on the cause of the issue, there are

several solutions you can try:

Verify that the e-mail addresses used for subscribing to reports are valid.

Verify that the security settings on the e-mail alias or distribution group do not restrict e-mail notifications from being delivered to the intended addressee(s).

Verify that the From address, which is specified on the SMTP Server tab for use in e-mail messages, contains a valid e-mail

69


whose properties are

set to only receive e-

mail from authorized

senders.

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.

address.

For more information, in Deploying DPM 2010,

see Configuring the SMTP Server


When exporting

HTML reports to

MHTML, charts do

not display correctly.

If you try to export an

HTML report to Web

Archive (MHTML

format) on a DPM

server running

Windows Server 2003

Service Pack 2 (SP2),

the charts on the report

will not display.

This is an issue with Internet Explorer, and

occurs only the first time you export a report.

Subsequent exported reports will display

correctly.

When you try to view

a DPM report, you

see a “Cannot find

server” or “DNS

error” error message,

or the report is not

displayed in Internet

Explorer.

The proxy server

settings in Internet

Explorer may not be

set correctly.

To display reports in Internet Explorer, the proxy

server for local connections needs to be

bypassed.

To bypass the proxy server for local

connections:

1. In Internet Explorer, on the Tools menu, click Internet Options.

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

70



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

DPM report types

are missing from the

Reporting task area

of DPM Administrator

Console.

An administrator has

manually deleted one

or more of the DPM

report templates from

the DPM computer.

To restore the missing DPM report types, do the

following:

1. Ensure that no DPM jobs are running.

2. Close DPM Administrator Console.

3. In Add or Remove Programs, uninstall 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 export

reports to MHTML,

Excel, or PDF

formats.

If both Internet

Explorer Enhanced

Security and Secure

Socket Layer (SSL)

options are enabled,

DPM cannot export

reports to MHTML,

Microsoft Excel, or

PDF formats.

To export reports to MHTML, Excel, or PDF

formats, you must disable Internet Explorer

Enhanced Security.

To disable Internet Explorer Enhanced

Security:

1. In Add or Remove Programs, click Add/Remove Windows Components.

2. In the Windows Components Wizard dialog box, clear the Internet Enhanced Security Configurations check box.

A report has no data

in it when you view it

from DPM

Administrator

Console or in an e-

mail attachment.

One of the following

problems might have

prevented the report

from running at the

scheduled time:

Reporting could not connect to the DPM database.

The DPM computer was down for maintenance.

The DPM computer was

When a report fails, the report is run again as

soon as the DPM computer is back online or at

the next regularly scheduled time. This resolves

the problem of not being able to view the report

from DPM Administrator Console.

To ensure that e-mail subscribers receive the

corrected report:

1. Select the report type in the Reporting task area of DPM Administrator Console.

2. In the Actions pane, click Schedule.

3. In the Frequency drop-down list, click Once.

4. In the Date and Time drop-down lists, select

71


being restarted. the next available schedule.

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

always prompted for

user credentials to

access DPM reports.

DPM Setup

automatically adds the

name of the DPM

computer to the Local

Intranet security zone

in Internet Explorer to

permit access to DPM

reports without having

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.

To restore the default setting, manually remove

the DPM computer name from the Trusted Sites

zone and add it to the Local Intranet zone.

For more information on Internet Explorer

security zones, in the Internet Explorer 6.0

Resource Kit see Security Zones


When you try to view

reports, you receive

the following error

message:

An error has occurred during report processing. (rsProcessingAborted) Get Online Help

Logon failed. (rsLogonFailed) Get Online Help

The

DPMR$<MachineNam

e> account may not

have the required user

rights.

To resolve this error, you must ensure that the

DPMR$<MachineName> account has the Allow

log on locally user right.

To assign the Allow log on locally user right

to the DPMR$<MachineName> account:

1. In Administrative Tools, open Local Security Policy.

2. Under Security Settings, expand Local Policies, and then click User Rights Management.

3. In the details pane, right-click Allow log on locally, and then right-click Properties.

4. In the Allow log on locally Properties dialog box, click Add User or Group.

5. In the Select Users, Computers, or Groups dialog box, click Locations, click

72



Logon failure: the user has not been granted the requested logon type at this computer.

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

inactive replicas is

not reported correctly

in the Disk Utilization

Report.

For existing protection

groups or file servers,

current storage pool

details do not display

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.

Disk utilization for these replicas will be correct

in reports generated at least a day after the

change is made.

Notification deliveries

for reports and alerts

fail.

Your notification

deliveries will fail if you

enter the incorrect user

name for

authentication on the

SMTP server.

To enter the correct user name for

authentication, in the Options dialog box, on the

SMTP Server tab, in the User name box, type

the domain name of the user that appears in the

"From" address box. For example, if the user

name in the "From" address box is

[email protected], in the User

name box type <domain name>\Terry.

Logon failure

(0x80070569): The

user has not been

granted the

requested logon type

at this computer.

This error occurs when

your security policy

settings prevent the

user from logging on

using a local user

account.

To add a domain user account, perform the

following steps:

1. Remove the DPMR$DPMMACHINENAME account from the DPMDBReaders$DPMMACHINENAME group.

2. Delete the DPMR$DPMMACHINENAME account.

73


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 SectionNetwork Bandwidth Issues

Network Bandwidth Issues

The following table provides guidance for troubleshooting network bandwidth issues.

Network Bandwidth Issues


Network bandwidth usage is

not being throttled.

The quality of service (QoS)

may not be enabled on the

production server and the

DPM server.

If you enabled network

bandwidth usage throttling in


and the network bandwidth

usage is not being throttled,

verify that QoS is enabled on

the production server and the

DPM server.

74



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.

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

To resolve issues that might cause a transitory database failure

75

Error To troubleshoot this error

Error 940: Unable to connect to the database

because of a fatal database error. It is unlikely

that the database itself has been damaged.

Ensure that the DPM instance of SQL Server

(MSDPM2010) service is running. Then use

Windows Event Viewer to find information about

related events.

Error 941: Unable to connect to the DPM

database.

To resolve issues related to 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 (http://go.microsoft.com/fwlink/?LinkId=100602).

Error 942: Database integrity is in question

because of a hardware or software problem.

If the integrity of the DPM database is in

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

76



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 restarting SQL Server. Work with your SQL Server administrator to determine the best course of action.


database because the database is in an

inconsistent state.

If DPM finds that the database is in an

inconsistent state, the problem is unlikely to

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.

77




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 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.


database because of a general database

failure.

For general database failures, ensure that the

DPM service is running on the DPM server.

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)

78


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 (http://go.microsoft.com/fwlink/?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).

Database Exceptions

Exception To troubleshoot this exception

Exception 5168: Login failed for user <user

name>.

DpmSync fails when trying to restore the

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 IssuesThis 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 (http://go.microsoft.com/fwlink/?linkid=179156).

79




Using the sp_helpdb system stored procedure for SQL Server in the Transact-SQL Reference (http://go.microsoft.com/fwlink/?LinkId=189722).

Using the Database Console Commands (DBCC), DBCC SQLPERF and DBCC SHRINKFILE for SQL Server located in the “DBCC” section of the Transact-SQL Reference (http://go.microsoft.com/fwlink/?LinkId=189726).

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



displays an error for jobs that

are in progress and have not

completed.

The DPM jobs are still in

progress and have not

finished running.

While DPM jobs are in

progress, DPM continually

retries the job until it is

finished running. After the job

is complete, DPM will display

the correct job status.

File synchronization or recovery

point creation jobs continue to

run, even when DPM is not

transferring data.

DPM may be perpetually

attempting to cancel the job.

Verify that DPM is not

transferring data, and then

cancel the job. If the job

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

80





On the computer that you are

recovering, the Recovery

Center Rollback Wizard

suspends during the

progressing state. After you

restart the computer, it

remains suspended.

This issue occurs when there

are communication problems

between the DPM SRT server

and the protected server.

To resolve this issue, close

and then restart the Recovery

Center Rollback Wizard.

The restore operation fails. When you replace a disk that

has crashed with a disk that

contains partitions, the restore

operation may fail.

Replace the disk that has

crashed with one that does

not contain any partitions.

Volume attributes and access

control lists (ACLs) do not

restore properly.

This issue may be due to the

following:

Compressed volumes are restored as expected; however, you must set compression attributes manually.

DPM does not restore the security attribute of the root of a volume.

If the recovery fails, we

recommend that you restart

the computer with a Boot

Client CD, and then delete the

contents in the temporary

folder at the root of the

volume.

The recovery sets included in

a recovery point appear as

unspecified in the user

interface.

During a restore, the recovery

sets included in a recovery point

are not populated in the user

interface and appear as

unspecified.

If this issue occurs, you must

close the user interface,

restart the DPM System

Recovery Tool Data Store

service, and then restart the

restore operation.

After you create a new

recovery set, it does not

appear in the user interface.

If the schedule console is

already open, the new recovery

set may not appear.

To resolve this issue, refresh

the user interface. If the new

recovery set still does not

appear, close and then restart

the user interface.

Application data is not in a

consistent state on FAT32

volumes.

DPM SRT backs up FAT32

volumes as live volumes and

cannot guarantee an application

consistent state of data, or

provide a single point for all files

in the volume.

No resolution for this issue.

DPM SRT does not work A previous version of Recovery Uninstall any previous

81


correctly. Manager may have been

installed before installing the

DPM SRT.

versions of Recovery

Manager before installing the

DPM SRT.

Troubleshooting Disaster Recovery Issues

The following table provides troubleshooting guidance on DPM disaster recovery issues.

Disaster Recovery Issues


Error ID: 31008 appears

because DPM only refreshes

protection agents every 30

minutes.

If a protected domain controller

or secondary server becomes

unavailable, the protection

agents are not automatically

refreshed in DPM

Administration Console.

For disaster recovery

scenarios, in DPM

Administrator Console you

must wait for the scheduled

installation list refresh, which is

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.

General DPM Issues

Issue Possible

Cause

Resolution

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

protected from the same

instance as DPMDB, DPM

82

Issue Possible

Cause

Resolution

will stop working when the

master DB is recovered.

Scheduled jobs not getting triggered when DPM

uses a remote SQL instance

Ensure that the SQL Server

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

work on DPM servers that have NETBIOS names

longer than 15 characters.

If the NETBIOS name of the

DPM server is longer than

15 characters, use the

clipped name within the

cmdlets.

Unable to add GUID Partition Table (GPT) disk to

storage pool.

To resolve this issue, either

retry the operation or wait

30 sec.

After switching back protection, jobs for some data

sources start failing with Access Denied errors.

A new

backend/p

hysical

node was

added to a

SharePoin

t farm or

cluster

after

switch

protection.

This node

was

protected

directly by

the

secondary

server.

The

primary

DPM did

1. Attach agent from primary DPM to the newly added computer.

2. Run SetDPMServer -DPMServerName <primaryDPM.domain.com> on the newly added computer.

3. Make sure the primary protection is green.

4. Now run modify protection group on the secondary DPM server for the protection group containing affected data source.

a. Expand the primary DPM server node in the Modify Protection Wizard.

b. Expand the

83

Issue Possible

Cause

Resolution

not know

about this

new node

until

protection

was

switched

back.

SharePoint front-end/resource group to which the new computer was added.

5. Save the protection group.

DPM engine on secondary server stops working after

it is denied access to a file on the primary server with

the following stack:

Access to the path '\\dpmserver.contoso.com\MTATempStore$\PSInfo\78b18367-eb4e-4e1d-8cfd-a7e41cb48d6b.xml' is denied.</ExceptionMessage><ExceptionDetails>System.UnauthorizedAccessException: Access to the path '\\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)

Lack of

permissio

ns to a

share or a

name

resolution

conflict.

Change the name resolution

order.

For more information see

How to change name

resolution order on Windows

95 and Windows NT

(http://go.microsoft.com/fwlin

k/?LinkId=187186).

The user cannot open DPM Administrator Console. If the user

is a

member

of a group

You must add the user to the

Administrators group.

84




Issue Possible

Cause

Resolution

other than

the

Administra

tors

group,

such as

Backup

Operator,

they will

not have

access to

DPM

Administra

tor

Console.

Error 30115: DPM failed to synchronize changes for

<Datasource Type> <Datasource Name> on <Server

Name>.

The

shadow

copy

storage

area did

not have

sufficient

storage

space to

hold the

churn on

the

protected

computer.

Retry the operation at a later

point when the churn is

expected to be lower.

Error 30116: VSS has deleted a shadow copy. The

shadow

copy

storage

area might

have run

out of disk

space on

the server

<server

Increase the space allocated

for the shadow copy storage

area for protected volumes

on this computer.

To change the settings for

shadow copies, do the

following:

1. Click Start, click Control Panel, double-click Administrative Tools,

85

Issue Possible

Cause

Resolution

name>. and then double-click 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 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

86

Issue Possible

Cause

Resolution

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

Error

Code

Error Message Recommended Action

7 Unable to connect to the Active

Directory Domain Services

database.

Make sure that the DPM server is a member of a

domain and that a domain controller is running. Also

verify that there is network connectivity between the

DPM server and the domain controller.

16 DPM cannot access the path

<file name> because part of

the path has been deleted or

renamed.

Check the path and enter it again.

11 DPM cannot browse <server

name> because the host is

unreachable.

1) Verify that <server name> is online and remotely

accessible from the DPM server.

2) If a firewall is enabled on <server name>, verify that it

is not blocking requests from the DPM server.


name> because access was

Verify that the computer running DPM has DCOM

launch and access permissions for <server name>, and

87



Error

Code


denied. that the system time on the DPM server and <server

name> is synchronized with the system time on the

domain controller.


name> because the protection

agent is not responding.


name> because of a

communication error between

DPM and the protection agent

on the computer

To troubleshoot this error:

1) Verify that <server name> is remotely accessible

from the DPM server.



3) Restart the DPM Protection Agent (DPMRA) service

on <server name>. If the service fails to start, reinstall

the protection agent.


name> because a protection

agent is not installed on

<server name> or the

computer is restarting.

To install a protection agent on <server name>, in the

Management task area, on the Agents tab, click Install

in the Actions pane.

30 DPM cannot contact <server

name> until you complete the

protection agent installation by

restarting the computer.

Restart <server name> and then try the operation

again.


name> because the host is

unreachable.

1) Make sure that <server name> is online and remotely


2) If a firewall is enabled on <server name>, make sure

that it is not blocking requests from the DPM server.


name> because access is

denied.

On the Agents tab in the Management task area, check

the status of the agent. Also, verify that the system

times on the DPM server and the protected computer

are synchronized with the system time on the domain

controller.


name> because the agent is

not responding.

If you just installed an agent on <server name>, the

computer might be restarting. Wait a few minutes after

Windows starts for the agent to become available.

Otherwise, troubleshoot the problem as follows:

88

Error

Code


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.


name> because of a

communication error with the

agent.

If you just installed an agent on <server name>, the

server might be restarting. Wait a few minutes after

Windows starts for the agent to become available.

Otherwise, troubleshoot the problem as follows:

1) Make sure that <server name> is remotely accessible






protection agent.

60 The protection agent on

<server name> was

temporarily unable to respond

because it was in an

unexpected state.


62 Cannot find the volume

<volume name> on the

computer running DPM.

Make sure that the storage pool disk is accessible. If it

is not, reallocate disk space and then reprotect the data.

64 Volume <volume name> is

offline on the computer running

DPM.

Please take the recommended action in Event Viewer

on the DPM server.


name>, either because no

agent is installed on <server

name> or because the

computer is rebooting.



in the Actions pane.

89

Error

Code



<file name> because part of

the path has been deleted or

renamed.

Check the path and enter it again.

37 DPM cannot access <file

name> because an element

has been exclusively locked by

another process.

Try the selection later or check to see if the object is

locked by another process.

38 DPM 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

<file name>.

Verify that the path can be accessed successfully by

using Windows Explorer.

41 DPM failed to communicate

with <server name> because

the computer is unreachable.

1) Make sure that <server name> is online and remotely




3) If you are using backup LAN, make sure that the

backup LAN settings are valid.


with the protection agent on

<server name> because

access is denied.

1) Verify that the DPM server has DCOM launch and

access permissions for <server name> and that the

system time on the DPM server and the protected

computer is synchronized with the system time on the

domain controller.

2) If this computer does not 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

90

Error

Code


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.



<server name> because the

agent is not responding.










protection agent.




agent is not installed or the




in the Actions pane. If the computer is in the process of

restarting, allow some time for the computer to come

online.

46 DPM failed to perform the

operation because too many

objects have been selected.

Select fewer objects and then

retry this operation.

Select fewer objects. 1) If you are trying to protect a

large number of data sources on a volume, consider

protecting the whole volume instead of individual data

sources.

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

to communicate with the

protection agent on <server

name>.

Restart the DPM Replication Agent service on <server

name>.

91

Error

Code


56 DPM failed to move data

because it did not receive the

completion status from the

protection agent.


57 DPM cannot continue to

protect the data on <protected

server name> because there is

not enough disk space

available on one or more of its

volumes.

1) Free up disk space on the protected computer. 2)


47 Some components of the

protection agent on <protected

server name> were not

installed or configured properly.

1) Verify that the protected computer <protected server

name> is not running an unsupported version of the

operating system.

2) Consider restarting the computer <protected server

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

agent on <protected server name>.

48 <Server name> needs to be

restarted. This may be

because the computer has not

been restarted since the

protection agent was installed.

1) Restart <server name>.

2) If you have any protected data on this computer,

synchronize with consistency check after <server

name> successfully reboots.

3040

0

To protect the selected data

source, <server name> needs

to be restarted for creating the

change journal.

Restart the computer and then synchronize with

consistency check.

49 The protection agent timed out

while trying to access the file

<file name> for volume

<protected server volume

name> on <protected server

name>.

1) Make sure that the file <file name> is accessible.

2) Synchronize with consistency check.

50 The DPM protection agent

failed to perform a consistency

1) Make sure that the file <file name> is accessible.

2) Retry the consistency check operation.

92

Error

Code


check on file <file name> for

volume <protected server

volume name> on <protected

server name>.


with <server name> because

of a communication error with

the protection agent.





3) Restart the DPM Replication Agent service on

<server name>. If the service fails to start, re-install the

protection agent.

55 The protected volume <volume

name> on <server name>

could not be accessed. The

volume may have been

removed or dismounted, or

another process may be

exclusively using it.

Make sure that volume <volume name> can be

accessed, and then click the recommended action link

below.

If a new volume <volume name> was created to replace

a previously protected volume with the same name, and

you want to protect the new volume, you must remove

the original volume from its protection group, and then

add the new volume to the protection group. You can

retain the replica for future recoveries.

If you no longer want to protect any data sources on the

computer, you can uninstall the protection agent from

the computer. If the volume has been permanently

removed or deleted, remove the volume from its

protection group (optionally choosing to retain the

replica for future recoveries) and inactivate the alert by

clicking "Inactive alert" Otherwise, click the

recommended action link below.

58 DPM is out of disk space for

the replica.

1) Allocate more disk space for the replica. For more

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

93

Error

Code


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

name> because there is no

virtual name configured for the

Resource Group to which the

file belongs.

Make sure that the Resource Group has one virtual

name configured. Also, check that dependencies

between cluster resources are configured correctly.

77 The consistency check job

failed due to an internal error.

Rerun the consistency check job.

91 The replica of <data source


<server name> is not

consistent with the protected

data source.

92 Cannot access volume on the

replica of <data source type>

<data source name> on

<server name>.

Stop protection of <data source name> and then

reconfigure protection for this data source.

242 The share "<object name>" on

<server name> is not currently

protected.

Make sure that the share name and computer name are

accurate.

78 DPM is unable to continue

protection for data sources on

the protected server <server

name> since it has detected an

incompatible filter installed on

this server.

Refer to the KB article http://go.microsoft.com/fwlink/?

LinkId=95132 for more details on resolving this error

245 You must specify the e-mail

addresses of users whom you

want to notify about this

recovery operation.

In the Recipients box on the Recovery tab, type the e-

mail addresses.

94

Error

Code


246 Recovery cannot be performed

right now as some other

conflicting job is running.

Please go to Alerts tab in

Monitoring task area for

details.

Restart the recovery



<server name> is being

created.

If the replica creation is scheduled for a later time, no

action is required. If you have chosen to manually

create the replica, copy the data and then synchronize

with consistency check.

94 The data source <data source


<server name> is no longer

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.

No action is needed. Wait for DPM to update its

database to reflect that this data source is no longer

protected.

95 Job failed on replica of <data

source name> on <server

name> because of ongoing

synchronization.

Cancel the ongoing operation, or wait for it to complete.

Then retry the operation.

96 Job failure on replica of <data


name> caused by ongoing

replica creation.

Wait for the replica creation operation to complete. Then

retry the job.




consistency check.

Cancel the operation, or wait for it to complete. Then

retry the job.

98 Operation failed on replica of


<server name> since a

recovery operation is currently

in progress.


retry the job.

99 Job failure on replica of <data Cancel the operation, or wait for it to complete. Then

95

Error

Code




stop-protection job.

retry the job.




recovery point creation.


retry the operation.

101 This job failed because the

replica for this data source is

being deallocated, probably

because the ‘Stop Protection

without retaining replica’ task

was run on this data source.

No action is needed. Wait for DPM to update its

database to reflect that this data source is no longer

protected.

104 An unexpected error occurred

during job execution.


107 The DPM protection agent is

no longer tracking changes on

<protected server volume

name> on <protected server

name>.

1) Check recent records from the FSRecord source in

the System Event Log on <protected server name> to

find out why the problem occurred.

2) Synchronize with consistency check.

109 The replica on the DPM server

for <data source type> <data


name> is inconsistent with the

protected data source.

Changes cannot be applied.

238 <Server name> cannot be

used as a destination for

recovery because it has not

been restarted since the

protection agent was installed.

Restart <server name> and then try the recovery

operation again.

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

96

Error

Code


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


<server name> caused by an

ongoing conflicting operation

on <server name>.

Cancel the ongoing operation, or wait for it to complete.

Then retry the job.

114 Job failure on <data source


caused by ongoing backup

operation.



115 Job failure on <data source


caused by ongoing recovery

from tape operation.



116 Job failure on <server name>

caused by other ongoing

conflicting operations on that

computer. Note that some

applications do not allow

parallel recovery and backup

operations on the same data

source.

Cancel the operations, or wait for them to complete.

Then retry the operation

117 The synchronization job failed

due to an internal error.

Create a valid recovery point on the primary DPM

server and rerun the synchronization job.

To create a valid recovery point on the primary DPM

server:

97

Error

Code


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

recovered to the DPM server


replica is not in "replica

creation pending" state.

Ensure that the replica is in "replica creation pending"

state before recovering. For details on recovering a

DPM server, refer to the DPM 2010 Operations Guide.

130 You cannot add more recovery

points because the maximum

number of recovery points for

the entire retention range is

<maximum limit> .

To increase the recovery points per day, you must either

decrease the retention range or select fewer days of

week.

133 You cannot choose this

recovery point because the

time difference between it and

a previous recovery point is

less than your synchronization

frequency.

Specified synchronization

frequency: <value entered>

Choose a recovery point that has a time difference with

a previous recovery point that is equal to or greater than

the specified synchronization frequency.

137 The protection group name

entered already exists.

Enter a different name.

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

group because no disks or

tape libraries available.

Configure a tape library or add a disk to the storage

pool.

138 The target path <object name>

is located on the system

98

Error

Code


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

throttling rate must be between

1 and 10000 Mbps.

Enter a number between 1 and 10000.

141 Cannot perform <input

parameter tag> because the

replica is not idle.

Wait for the ongoing job to complete or cancel the job in

the Monitoring task area.

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


database.

144 The backup frequency for long-

term protection needs to be

equal to or greater than the

backup frequency for short-

term protection.

Backup frequency for short-

term protection: <input

Select a backup frequency that is equal to or greater

than <input parameter tag>.

99

Error

Code


parameter tag>.

145 You cannot reduce the express

full backup schedule because

this would affect the long-term

recovery goals of this

protection group.

Before you can reduce the express full backup schedule

of this protection group, you must modify the protection

group properties to specify a backup frequency that is

equal to or greater than weekly.

146 The specified protection group

name is not valid. A protection

group name must be between

1 and 64 characters, with at

least one alphabet letter.

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.

100

Error

Code


149 You have specified the change

journal size on volume

<volume name> for <server

name> to be set to <value

entered>. However, this is

greater than the available

space on the selected

computer.

Free space on the volume on the protected computer

and retry the task

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

this protection group is

temporarily disabled while

initial synchronization of one or

more members occurs.

Either cancel the initial synchronization jobs for the

members or wait until they complete.

157 <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.

101

Error

Code


160 <Value entered> does not meet

the minimum allocation value

of <original calculated value>

<unit>.

164 <Volume name> on <server

name> does not meet the

minimum size requirement of

1 GB.

Please remove the volume from selection.

168 The replicas for one or more of

the volumes being protected

are missing. This may be a

result of one or more disks in

the DPM storage pool being

offline or the deletion of

volumes created by DPM to

store the replicas. You cannot

modify disk allocation or

configure protection for any

members on these volumes

until the replicas have been

reallocated.

In the Protection task area, select protection group

<protection group> and click Review Pending Members.

Follow instructions to allocate disk space for protection.

169 Although you chose to retain

the replica for this previously

protected volume, the replica is

now missing from the DPM

server. Either the volume used

to store the replica has been

deleted from the storage pool,

or the disk on which the replica

was stored cannot be detected.

You cannot protect this

previously protected volume

until you delete the record of

this replica from DPM.

In the Protection task area, select the following member

from <previously protected member's group name>:

<list of protected members>, and click “Delete replica”

in the Details pane.

171 There is insufficient space on

the storage pool disks to

allocate the replica and

recovery point volumes

Add more disks to the storage pool by using the Disks

tab in the Management task area, or reduce the

specified allocations

102

Error

Code


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


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

103

Error

Code


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

<volume label> and <volume

label> which are being used to

protect <data source type>


<server name> since these are

custom volumes.

Use the Disk Management Console to resize your

volumes

180 Failure to allocate disk space

to the storage pool for storing

the replica and the recovery

points for <volume name> on

<server name>. No protection

will be initiated for <volume

name> on <server name> until

disk space has been allocated

to the storage pool.

In the Protection task area, select protection group

<protection group> and click Review Pending Members.

Follow instructions to allocate disk space for protection.

104

Error

Code


181 DPM could not create

<protection group> because of

failed disk allocations.

Refer to the allocation errors listed below and try to

create the protection group again.

182 Eseutil consistency check

cannot be performed for this

protection group, as eseutil.exe

is not present on the DPM

server.

Copy the following files from the Exchange server

installation folder to "<folder path>" location on the DPM

server:

Ese.dll

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

recovery point consolidation.

Check the Alerts tab in the Monitoring task area to

locate this alert and fix the issue. Please retry recovery

after that.

192 The requested operation could

not be completed because the

replica was in an inconsistent

state.

Run consistency check and retry the operation.

195 Your changes cannot be

applied because certain

protection group properties

have changed. The protection

group properties could have


105

Error

Code


changed due to either of the

following:

232 Only <maximum list items in

Browse view> of the items in

<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

members in the resource group

<object name>. This resource

group contains some

resources that have

dependencies which not

present as part of this group.

1) Check your cluster configuration to ensure that

shares and disks on which these shares reside are part

of the same resource group

2) Check your cluster configuration to ensure that the

application and the disks it requires are part of the same

resource group.

200 DPM could not perform the

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

database <data source name>

since this was part of the

SharePoint Farm <referential

data source name> which is

either under active protection

or has an inactive replica

available.

To be able to directly protect this Sql database you

could do either of the following:

1) Rename the database and then protect it.

2) Stop protection of the SharePoint Farm and remove

the replica associated with this farm. Then protect this

database.

202 DPM could not recover the

requested data.

The selected recovery point is

no longer available for

recovery.

Select another recovery point.

106

Error

Code


203 Recovery failed because the

data source files have been

moved since this recovery

point was created.

1. Choose a recovery point created after the move

operation.

2. Choose a different recovery type.

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

range which is equal to or less

than 4158 weeks or 1188

months or 99 years.

207 An unexpected error occurred

during a VSS operation.


208 No recovery point was created,

either because synchronization

has not occurred since the last

recovery point was created, or

because no changes were

found during synchronization.

If synchronization has not occurred since the last

recovery point was created, you can synchronize the

replica with the protected data on the protected

computer and then create a recovery point. For more

information, see "How to synchronize a replica" and

"How to create a recovery point" in DPM Help.

210 DPM was unable to create the

recovery point due to a general

failure in the Volume Shadow

Copy service.

1) Make sure that the Volume Shadow Copy service is

enabled on the DPM server. 2) Check recent records

from the VolSnap source in the Application Event Log to

find out why the problem occurred. 3) Retry the

operation.

211 Cannot create a recovery point

because another recovery

point creation is in progress.

Wait for a few minutes and then retry the operation.

212 Cannot delete recovery point

because it is in use for

recovery.

Wait for all recovery jobs on the replica to complete and

then retry the operation.

213 A recovery point was created Modify disk allocation to increase space allocation for

107

Error

Code


and immediately deleted

because of insufficient disk

space.

the recovery point volume.

214 DPM does not have sufficient

storage space available on the

recovery point volume to

create new recovery points.

Increase the disk allocation space for the recovery 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

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

because of a transient

problem.

1) Check recent records from the VolSnap source in the

Application Event Log to find out why the problem

occurred. 2) Retry the operation.

218 You must specify the e-mail

addresses of the recipients to

send notifications.

219 You must specify the SMTP

server settings before you can

subscribe to notifications.

On the Action menu, select Options. Select the SMTP

Server tab to configure settings.

227 DPM cannot access <file

name> because the file or

folder has been exclusively

locked by another program.

Make sure that the item is not locked by another

process.

229 DPM failed to access the path

<file name>.

Verify that the path can be accessed successfully by

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

108

Error

Code


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

administrator privileges on the

DPM Server.

Add the user to the Administrators group or specify

different administrator and try again.


name> because access is

denied.


the status of the agent. Also, verify that the system

times on the DPM server and the protected computer

are synchronized with the system time on the domain

controller.


name> because the agent is

not responding.










protection agent.


name> because of a



109

Error

Code


communication error with the

agent.





protection agent.


name> either because no

agent is installed on <server

name> or because the




in the Actions pane. If the computer is in the process of

restarting, allow some time for the computer to come

online.

235 No library is available for

recovery to proceed.

From the Library tab in Management, click Rescan to

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.

110

Error

Code


For Exchange mailbox

recovery, DPM supports only

the "Previous point in time"

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

permissions on the replica or

recovery point volume that was

created.

Review the error details, take appropriate action and


420 DPM could not get security

permissions on the replica or

recovery point volume.

Review the error details, take appropriate action and


450 An invalid path name was

specified for the DPM

database location.

Specify the correct path of the .mdf or .bak file and try

again.

451 An invalid path name was

specified for DPM Report

database location.

255 The selected recovery point no

longer exists.

111

Error

Code


265 DPM encountered an error

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.

Recover the data from another recovery point.

346 DPM is unable to retrieve the

configuration information from

<server name>.

Ensure that the Windows Management Information

(WMI) service <service name> is started and is


349 An error occurred when the

agent operation attempted to

transfer agent installation files

to <server name>.

Review the error details, take the appropriate action,

and then retry the agent operation.

355 Disk <NT disk number> cannot

be removed from the storage

pool because it contains

storage pool volumes.

267 The following computers do not

meet the minimum software

requirements for installing the

DPM protection agent: <list of

servers>.

Verify that Windows Server 2003 Service Pack 1 is

installed on the selected computers. If the operating

system has been recently updated, Active Directory

updates may still be pending. Wait until the Active

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

cannot be empty value or


characters <input name>.

Specify valid names to search.

274 Unable to configure security Make sure that the password you have provided has

112

Error

Code


settings for <server name> on

the computer <computer

name>.

administrator privileges on the target computer.

275 Unable to remove <server

name> from the security group

on <computer name>.

Make sure that the password you have provided has

administrator privileges on the target computer.

270 The agent operation failed on

<server name> because DPM

could not communicate with

the DPM protection agent. The

computer may be protected by

another DPM server, or the

protection agent may have

been uninstalled on the

protected computer.

Check the following to troubleshoot this issue:

1) If the agent is no longer installed on the computer,

remove the protected data sources on this computer

from active protection. Then, remove the entry of this

computer from the Agents tab in the Management task

area.

2) If the agent is not installed on <server name>, run

DpmAgentInstaller.exe with this DPM computer as a

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

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

not have administrator access

to the following items: <server

name>

Remove the computers from the "Select Computers"

page or provide credentials for an account that has

administrator access to all of the selected computers.

276 A site, document, list or list-

item cannot be empty or


characters <input name>.

Please enter a valid value to search.

277 Could not connect to the 1) Make sure that <server name> is online and remotely

113


Error

Code


Service Control Manager on

<server name>.




278 Unable to connect to the Active


database.

Make sure that

1) Server is a member of a domain and that a domain

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

installation failed. The

credentials you provided do not

have administrator privileges

on <server name>.

Verify that the credentials you provided have

administrator privileges on <server name> and then try

to reinstall the protection agent again.

292 You cannot uninstall protection

agents from the protected

computers until you remove all

protected members on the

associated computers from

protection groups.

Remove all of the members that are associated with the

following computers from protection groups before

uninstalling the protection agents: <list of servers>


installation or upgrade

succeeded. However, DPM

could not remove the bootstrap

service.

You must restart the protected computer <server name>

before it can be protected.

298 Recovery failed for <data

source type> <data source

name> on <server name>.

Recover to an alternate location or try recovering from

another recovery point.

333 A protection agent is already

installed on <server name>.

334 You cannot install the


name> because it is the DPM

server.

350 Disk <NT disk number> is Select a different disk to add to the storage pool.

114

Error

Code


already in the storage pool.

293 The protection agent operation

failed. The credentials you

provided do not belong to a

valid domain user account.

Do the following to troubleshoot this issue:

1) Verify that the credentials you entered belong to a

valid domain user account, and then retry the operation.

2 ) Verify that the domain controller is available and

functioning properly.

295 DPM could not remove the

Protection Agent Coordinator

service from <server name>.

Use Add or Remove Programs in Control Panel to

uninstall the DPM Agent Coordinator service on <server

name>.

296 The protection agent is

incompatible with the version

of DPM that is installed on this

computer. All subsequent

protection and recovery tasks

will fail on this computer until

you update the protection

agent.

1) Update the protection agent to a version compatible

with the DPM server. From the DPM Administrator

Console, open the Agents tab in the Management task

area. Select the computer on which the protection agent

is installed. Click Update from the Actions pane.

2) If a firewall is enabled on the computer, run

DPMAgentInstaller [DPM Server Name] on protected

computer. From DPM Management Shell, run the

AttachProductServer.ps1 commandlet on DPM server to

update the DPM configuration.

297 The protection agent is

incompatible with the version

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.

Uninstall the protection agent from this computer and

then reinstall the protection agent.

299 For <data source type> <data


name>, the following items

could not be recovered:

<temporary list of files>.

Make sure that the file is not already present and in use

on the destination computers and that there is sufficient

disk space for the files.


failed because it could not

communicate with <server

name>.





115

Error

Code



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

failed because the protection

agent is not installed on

<server name>.

To upgrade the protection agent:

1) In DPM Administrator Console, in the Management

task area, on the Agents tab, select the computer on

which the protection agent is installed, and then in the

Actions pane, click Uninstall to remove the protection

agent record.

2) On the Agents tab, click Install to reinstall the agent

on <server name>.


failed because it could not

access the protection agent on

<server name>. <Server

name> may be running DPM,

or the DPM protection agent

may have been installed by

another DPM server.

Uninstall DPM or the DPM protection agent from

<server name> and install the DPM protection agent

again from the computer that you want to use to protect

the computer.


failed on <server name>.




failed because another agent

operation was running on

<server name>.

Wait for the protection agent operation on <server

name> to finish, and then try reinstalling the protection

agent again.

305 The agent operation failed

because the operating system

on <server name> is not

supported.

Verify that the operating system is Windows

Server 2003 Service Pack 1 (SP1) or later on the

selected computers. If the operating system has been

recently updated, Active Directory updates may be

pending. In this case, wait until Active Directory is

finished updating, and then try installing the protection

agent again. The time required for Active Directory

updates depends on your domain Active Directory

replication policy.

For more information about software requirements, see

116

Error

Code


the DPM 2010 System Requirements.


installation on Windows 2003

Servers causes the computer

to briefly lose network

connectivity.

336 The protection agent uninstall

is unavailable because the

DPM server is currently

communicating with the

protection agent on the

following protected computers:

<list of servers>.

Wait a few moments and then try uninstalling the

protection agent again.


installation failed because

another version of the

protection agent is already

installed on <server name>.


uninstall the protection agent from <server name>, and

then try reinstalling the protection agent.


failed because DPM detected

an unknown DPM protection

agent on <server name>.


uninstall the protection agent from <server name>, then

reinstall the protection agent and perform the operation

again.


failed because DPM could not

communicate with the

Protection Agent service on

<server name>.

If you recently installed a protection agent on <server

name>, the computer may be restarting. Wait a few

minutes after restarting the computer for the protection

agent to become available. If the problem persists, do

the following:






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

117

Error

Code




because the ADMIN$ share on

<server name> does not exist.

Verify that the system root is shared as ADMIN$ on

<server name>.


because it could not access

the ADMIN$ share on <server

name>.

Verify that you have ADMIN$ share permissions on

<server name>, and that the system time on the DPM

server and <server name> is synchronized with the

system time on the domain controller.

311 Due to changes to <server

name>, the DPM protection

agent is no longer properly

installed.

In DPM Administrator Console, uninstall the DPM

protection agent. In the Management task area, on the

Agents tab, select the protection agent, and then in the

Actions pane click Uninstall.


because the DPM Agent

Coordinator service is not

responding.

Restart the DPM Agent Coordinator service on <server

name>.


because an error occurred

while running the installation

program on <server name>.

Review the log files on <server name>: [windir]\temp\

msdpm*.log and take appropriate action. Retry the

operation, and if the error persists, restart the computer

and then retry the operation again.


because an installation is

already in progress on <server

name>.

Wait for the installation to complete and then retry the

agent operation.


because server <server name>

is part of a cluster. DPM does

not support protection of

clustered servers.


on <server name> failed

because the service did not

respond.

If you recently installed a protection agent on <server

name>, the computer may be restarting. Wait a few

minutes after restarting the computer for the protection

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

118

Error

Code


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>.


name>. If the service fails to start, reinstall the DPM

protection agent.


installation failed because the

files needed to install the

protection agent (version

<agent version>) are missing

from the <server name> DPM

server.

Reinstall the missing files by running DPM Setup and

DPM updates.


because DPM was unable to

identify the computer account

for <server name>.

Verify that both <server name> and the domain

controller are responding. Then in Microsoft

Management Console (MMC), open the Group Policy

Object Editor snap-in for the local computer and verify

the local DNS client settings in Local Computer Policy\

Computer Configuration\Administrative Templates\

Network\DNS Client.


because of a communication

error with the DPM Agent

Coordinator service on <server

name>.





Refer to the DPM 2010 Deployment Guide for more

information on configuring the firewall for DPM.

320 The agent upgrade failed

because the protection agent is

not installed on <server

name>.

In DPM Administrator Console, in the Management task

area, on the Agents tab, click Uninstall to remove the

agent record from DPM. Then click Install to reinstall the


322 The following computers <list

of servers> were not found in

Active Directory Domain

Services, or they do not have a

Windows Server operating


1) Check the spelling of the computer name.

2) Verify that Windows Server 2003 with Service Pack 1

or later is installed on the computer.

3) Verify that you entered the fully qualified domain

119

Error

Code


system installed. 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.


because the DPM Agent


name> did not respond.


1) Check the recent DPMAC source records in the

application event log on <server name>.

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.


because the protection agent is

not active until you restart the

selected computers.

Restart the selected computers.


failed because access was

denied to the <server name>

DPM server.

Check the following:

1) If <server name> is protected by another DPM

server, you cannot install the protection agent on it.

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.


because the Remote Registry

service is not running on

Start the Remote Registry service on <server name>.

On the Administrative Tools menu, select Services. In

the right pane, right-click Remote Registry, and then

120

Error

Code


<server name>. click Start. Note: You can disable the Remote Registry

service after the agent operation is complete.

338 You can only select <maximum

installation servers> computers

to install at a time.

Select less than <maximum installation servers>

computers to add to the Selected Computers list.


because <server name> is not

a 32-bit computer or a 64-bit

computer.


because an incompatible

version of <name> is installed

on <server name>.

Install <name> version <version number> or later, or

uninstall <name> from the computer. If <name> was

installed by your original equipment manufacturer

(OEM), please contact your OEM support for

instructions.


because the Windows Installer

service on <server name> is

disabled.

Start the Windows Installer service on <server name>.

On the Administrative Tools menu, select Services. In

the right pane, right-click Windows Installer, and then

click Start. Note: You can disable the Windows Installer

service after the agent operation has completed.

337 You cannot install the


name> because access to the

computer has been denied.


1) If another DPM server is currently protecting <server

name> use that DPM server to uninstall the protection

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

failed because <server name>

has a more recent version of

Uninstall the existing DPM protection agent from

<server name> using Add or Remove Programs in

Control Panel. Then in DPM Administrator Console,

121

Error

Code


the protection agent (version

<agent version>) installed.

reinstall the DPM protection agent version that you

want. In the Management task area, on the Agents tab,

click Install in the Actions pane.


because the credentials you

provided do not have sufficient

user rights on <server name>.

Retry the agent operation and provide credentials that

have administrator user rights on <server name>.


because the DPM server could

not communicate with <server

name>.





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

version of the DPM protection

agent on the selected

computer.

1) Make sure that the correct version of the agent is

installed on the selected computer.

2)If the protection agent has been recently upgraded, in

DPM Management Shell, run Attach-

ProductionServer.ps1 [computer name] and refresh the

agent status again.


because of a communication

error with the DPM Agent


name>.

Restart the DPM Agent Coordinator service on <server

name>, and then try to reinstall the protection agent.



create the DPM Agent


name>.





communicate with the DPM



122

Error

Code


Agent Coordinator service on

<server name>.


be added to the storage pool.

Make sure that the disks being added to the storage

pool do not contain any of the following: system volume,

boot volume, OEM or other special volumes, DPM

software, or SQL Server databases.

452 The DPM service failed to stop. Check the application and system event logs for

information on the error.

453 The DPM service failed to

start.

Check the application and system event logs for

information on the error.

454 DpmSync failed to connect to

the specified SQL Server

instance.

Make sure that you have specified a valid SQL server

instance associated with DPM and you are logged on

as a user with administrator privileges.

455 Failed to attach database

[<database name>] at location

[<database location>] to SQL

server.

Make sure that the SQL server services are running and

you are restoring a valid DPM database backup.


be added to the storage pool

because the disk either failed

or is missing.

Check Disk Management to see whether the disk is

online. If the disk is offline, check the hardware

configuration and rescan.

354 Disk <NT disk number> is not

listed in the storage pool.

In the Management task area, select the Disks tab and

click Rescan to refresh all disks that are owned by

DPM.

356 The folder on which the

replicas must be mounted

already exists.

Clear all unmounted directories from <DLS volume

root> directory and then retry the operation.

467 The specified action can be

performed only on a computer

with DPM installed.

Run the tool on the DPM server to complete these

steps.

469 Unable to detach the database. Check that you have permission to detach the DPM

database.

358 The allocation of disk space for

replica volumes failed because

there is not enough

Add more disks to the storage pool or reduce the replica

volume size requirement.

123

Error

Code


unallocated disk space in the

storage pool.

360 The operation failed due to a

virtual disk service error


361 Disk <NT disk number> was

not added to the storage pool

because it could not be

converted to a dynamic disk.

For more information about supported disk types, see

the DPM 2010 Deployment Guide.

362 The replica cannot be

increased because the replica

volume is missing.

Reallocate the replicas before trying to increase them.

365 DPM is currently shutting down

and cannot complete the

requested operation

After DPM shuts down, restart DPM and then retry this

operation

366 The computer running DPM

has deleted volume [<volume

GUID>, <volume label>] from

DPM disk <NT disk number>

because it was not a DPM

volume.

In the Management task area, select the Disks tab and

review all disks that are owned by DPM.

367 DpmSync has completed with

the following errors: <DPM

synchronization summary>.

On the DPM server, use Event Viewer to view details for

this event. The details are available in the application

event log.

368 DPM has deleted DPM volume

[<volume GUID>, <volume

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

installed on <node> in

<cluster> server cluster.

Protection may fail if a failover

occurs to <node>.

Install the protection agent on each node of the server

cluster.

124

Error

Code


370 Agent operation failed.


because DPM detected a more

recent version of the DPM

protection agent (version

<agent version>) on <server

name>.

Install the updated version <agent version> of the

protection agent on the DPM server.

400 The DPM server was unable to

retrieve information about the

remote system using the

Windows Management

Instrumentation (WMI) service

on <server name>.

Verify the following:

1) <Server name> is online and remotely accessible


2) A firewall if enabled on <server name> is not blocking

WMI requests from the DPM server.

3) The WMI service on <server name> is running.

401 The agent installation failed

while trying to install the Agent

Coordinator service.


1) The share \\<server name>\ADMIN$ is accessible

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

trying to create the lock file in \\

<server name>\Admin$.

Verify that you have permissions to create the lock file

in \\<server name>\Admin$.

402 When trying to retrieve

information from the Windows

Management Instrumentation

(WMI) service on <server

name>, access was denied.

Verify that you have access to the WMI service on

<server name>.


when trying to install the Agent

Coordinator service.


1) The share \\<server name>\ADMIN$ is accessible

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

computer <server name> is

clustered.

Agent installation on <server name> can continue. To

successfully protect clustered resources, you must

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

125

Error

Code


running and can be accessed remotely from the DPM

server.

406 DPM detected that server

<chosen server name> is

clustered, but could not identify

the fully qualified domain name

of <server name>.

Agent installation on <chosen server name> can

continue. To successfully protect clustered resources,

you must install the DPM protection agent on all the

members of the cluster. Ensure that the cluster state is

correctly configured and verify that all members are

joined to the domain.

456 There were some failures in

the synchronization operation.

For details, please refer to application event log.

457 Invalid command line

arguments were specified.

For help about DpmSync, at the command prompt, type

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.

126

Error

Code


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

alerts that may require a user

action to MOM.

460 Invalid combination of

arguments specified.

Run DpmSync -? to review the syntax of the tool.

461 Instance name specified could

not be found

Specify the correct name for the instance of SQL

Server.

462 Error: Unable to retrieve DPM

database file path

Specify the correct path and try again.

464 Path not found: '<file name>'. Ensure that the database backup exists at the specified

path.

465 Unable to close all connections

for detaching the database.

Review the error details and try again.

466 Unable to copy database files

to <file name>.

Review the error details and try again.

470 DPM database is not present

in the instance of SQL Server.

Check that the DPM database is present in the given


471 Unable to attach the database. Ensure that the DPM database backup is valid.

517 The message cannot be sent

to the SMTP server.

Check the SMTP server settings.

518 An authentication error

occurred when trying to

connect to the SMTP server.

You typed an incorrect , password, or SMTP server

name. Type the correct password to enable e-mail

delivery of reports and alert notifications.

519 The SMTP server has rejected

one or more of the recipient

addresses.

Confirm the recipient addresses.

520 The SMTP Server port number

must be in the range between

Enter a valid port number.

127

Error

Code


1 and 65535.

522 Cannot connect to SMTP

server.

Verify SMTP server name and port number.

523 The passwords entered do not

match.

Reenter the passwords.

527 The SMTP server reports that

the From address is not valid.

Check for appropriate permissions to send via SMTP to

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.

530 A blank password is not

allowed.

Enter a password.

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

computer running Windows

Server 2003 Service Pack 1

(SP1).

Install DPM on a computer running Windows

Server 2003 Service Pack 1 (SP1). The Windows

Server 2003 SP1 redistributable package is available at

http://go.microsoft.com/fwlink/?linkid=45556.

801 To install DPM, you must be

logged on as an administrator

or a member of the local

administrators group.

Log on to the computer as an administrator or member

of the local administrators group, and then run Setup

again.

802 The computer processor speed

does not meet the DPM

minimum configuration

requirements. The minimum

Upgrade the computer hardware to meet the DPM

minimum configuration requirements; or install DPM on

a different computer. For information about DPM system

requirements, see the DPM 2010 System

128

Error

Code


required processor speed is

<clock speed>.

Requirements.

803 The available memory on the

computer is less than the DPM

minimum memory requirement.

The minimum memory

requirement is <minimum

memory required> MB, and the

recommended memory

requirement is 2 GB.

Upgrade the computer hardware to meet the DPM

minimum configuration requirements;, or install DPM on

a different computer. For information about DPM system

requirements, see the DPM 2010 System

Requirements.

805 There is not enough disk space

for <installation item>.

Free additional disk space on this disk, or choose a

different location.

809 DPM cannot load the file <file

name>. The file may be

missing or corrupt.

Run DPM Setup from the DPM product DVD. If you

already ran Setup from the DVD, then the DVD is

corrupt.

810 The DPM installation failed. Review the error details, take appropriate action, and

then run DPM Setup again.

811 The DPM database was not

created.


remove the DPM files and registry entries that were

created during Setup. Verify that SQL Server is properly

installed and that it is running, and then run Setup

again.

812 Report configuration failed. Verify that SQL Server Reporting Services is installed

properly and that it is running.

813 The DPM uninstall failed. Review the error details, take appropriate action, and

then try uninstalling DPM again.

814 The configuration data for this

product is corrupt.

Troubleshoot your Windows Installer installation.

Contact your support personnel for further help.

817 The Setup log file path <file

name> is too long after being

fully qualified.

Verify that the Application Data folder path has fewer

than 260 characters, and then run DPM Setup again.

818 The Setup log file path <file

name> is not valid.

Specify a valid Application Data folder path.

820 Setup cannot query the system

configuration.

Verify that the Windows Management Instrumentation

(WMI) service is running. If the WMI service is not

129

Error

Code


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

the SQL Server Reporting

Services 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.

823 DPM Setup cannot access

registry key <registry key>.

Verify that the registry key <registry key> exists, and


828 DPM cannot connect to the

Service Control Manager

(SCM).

To troubleshoot this issue, review the recent errors in

the Windows Event Log.

829 DPM cannot open the handle

to the <Setup service name>

service.

To troubleshoot this issue, review the recent errors in

the Windows Event Log.

830 DPM cannot read the service

<service name> configuration.

Review the recent errors in the Windows Event Log on

<server name>.

832 Setup cannot grant the <>

account access to the DPM

database.

Verify that SQL Server is properly installed and that it is

running.

834 Setup cannot remove the

deployed reports.

To delete the reports manually, go to http://<computer

name>/<ReportServer$ instance name>.

833 Setup could not delete the

<username> user account.

To delete the <username> user account, on the

Administrative Tools menu, click Computer

Management. Expand Local Users and Groups, and

then 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.

841 Setup cannot calculate the disk

space for the specified

location.

Specify a different installation location.

842 Setup cannot access the Verify that SQL Server 2008 is properly installed.

130

Error

Code


<registry key> registry key for

the <SQL Server instance

name> instance of SQL Server.

869 The <directory path> directory

is not on an NTFS volume.

Install the prerequisite software and DPM on a volume

formatted with NTFS.

843 The physical location of the

existing DPM database cannot

be found.

Verify that the instance of SQL Server is properly

installed, and that the <service name> SQL Server

service is running.

845 DPM Setup could not delete

the DPMDB database.

To delete the DPMDB database, in SQL Server

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

SqlCmd.exe.

Verify that the SQL Client Tools are installed. If they are

not installed, you must install the SQL Client Tools, and


847 DPM cannot create the <Setup

service name> service. Failure

to create the service may be

due to a pending restart.

Restart the computer, then uninstall DPM, and then run

Setup again.

848 Setup is unable to copy the

files from <source location> to

<installation location>.

Verify that Setup has access to the installation location.

849 Setup is unable to delete the

folder <installation location>.

Delete the folder manually.

850 Setup is unable to mark files at

<folder path> for deletion.

After DPM setup is complete, delete the files manually.

851 Cannot start Setup. Run the Setup program from the DPM product DVD. If

you 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

Setup is running.

Verify that only one instance of DPM Setup is running,

and then proceed with DPM Setup.

131

Error

Code


855 Setup was unable to delete the

scheduled jobs.

Open SQL Server Management Studio, and connect to

the DPM instance of SQL Server. Expand the instance

of SQL Server, browse to SQL Server Agent, and then

in Jobs, delete the <schedule category> category.

856 DPM could not access the

existing DPM database, or the

DPM database is corrupt.

Verify that the SQL Server service is running. If the SQL

Server service is running, restore the DPM database,

and then run DPM Setup again.

857 DPM cannot enumerate the list

of computers on which

protection agents are installed

because it cannot gain access

to the DPM database.

Protection agents may be installed on some of the

computers. Uninstall the agents on the protected

computers using Add or Remove Programs in Control

Panel.

858 The DPM product key is

invalid.

Enter a valid DPM product key. The product key is

located on the back cover of the Data Protection

Manager product DVD.

884 DPM Setup cannot delete

folder <folder path>.

Manually delete the folder <folder path> after

completing DPM Setup.

885 DPM Setup cannot create the

<file name> file.

Verify that the current user has permissions to create

the file.

886 This program is for internal

DPM use only.

To launch the DPM Setup program, double-click

Setup.exe in the root folder of the product DVD.

859 Setup cannot parse the SQL

Server 2008 Reporting

Services configuration file (<file

name>) for the SMTP server

address and the address of the

sender.

Verify that SQL Server is properly installed.

860 DPM cannot stop service

<Setup service name>.


and then try installing DPM again.

861 DPM cannot read the

installation path registry key.

Some of the folders will not be

deleted.

Manually delete the folders after completing DPM

Setup.

862 Setup cannot start the <Setup

service name> service.



132

Error

Code


863 You cannot use the selected

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>.

Select a different location on which to install DPM.

864 You cannot install DPM on

removable media or a network

share. The location <media

location type> <media location

information> cannot be used

as an installation location.

Select a location on a local hard drive to install DPM.

868 DPM cannot query the volume

information for directory

<directory path>.

Select another installation location on a local hard drive

to install DPM.

865 Setup could not enumerate the

information about volumes

allocated to DPM.

On the Administrative Tools menu, select Computer

Management, and then open Disk Management. Delete

the volumes allocated to DPM from the disks that were

added to the storage pool.

866 The Windows account that was

created in DPM Administrator

Console in the Recovery task

area could not be removed.

On the Administrative Tools menu, click Computer

Management. Expand Users and Groups, click Users,

right-click the Windows account, and then click Delete.

870 DPM cannot query the

attributes of directory

<directory path>.

Select another installation location on a local hard drive

to install DPM.

871 DPM Setup has detected an

existing installation of DPM on

this computer. The existing

installation is a later version

than the version you are trying

to install.

To install the earlier version of DPM, you must first

uninstall the existing version.

876 DPM Setup cannot create the If the folder already exists, delete the folder, and then

133

Error

Code


folder <folder path>. run DPM Setup again.

877 DPM Setup cannot write to file

<file name>.

If the file already exists, delete the file, and then run

Setup again.


service <Setup service name>.

To delete the service manually, at the command prompt,

type "sc delete <Setup service name>".

880 The DPM protection agent

configuration failed.



881 The required local group could

not be created.

Try installing DPM again.

883 DPM Setup cannot read the

<file name> file.

Verify that the current user has permissions to read the

file.

878 Setup cannot create the

protection job schedules.

Open SQL Server Management Studio, and then

connect to the DPM instance of SQL Server. Expand

the instance of SQL Server, browse to SQL Server

Agent, and then in Jobs, delete the <schedule

category> category.

882 DPM Setup could not create a

required service. This

computer may be protected by

another computer running

DPM. You cannot install DPM

on a computer on which a

protection agent is installed.

If the DPM protection agent is installed on this

computer, use Add or Remove Programs in Control

Panel to uninstall it, and then run DPM Setup again.

887 An error occurred while trying

to configure DPM.

Uninstall DPM by using Add or Remove Programs in

Control Panel, and then run DPM Setup again.

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


and review the alert details in

the Monitoring task area.

134

Error

Code


888 DPM Setup could not create

the DPM shortcut on your

desktop.

To start using DPM, on the Start Menu, point to All

Programs, and then click Microsoft System Center Data

Protection Manager 2007.

889 The database files from a

previous DPM installation were

found at <location>.

Delete the existing files at <location>, or select an

alternative location for your database.

890 DPM does not support

upgrading from the version of

DPM that is currently installed.

892 The computer <computer

name> could not be removed

from the intranet security zone

settings in Internet Explorer.

In Internet Explorer, on the Tools menu, click Internet

Options. In the Internet Options dialog box, on the

Security tab, click Local intranet, click Sites, then click

Advanced, and then remove computer <computer

name> from the intranet zone.

893 Setup cannot delete the

volumes that are allocated to

DPM.

On the Administrative Tools menu, select Computer

Management, and then open Disk Management. Delete

the volumes allocated to DPM from the disks that were

added to the storage pool.


the DPM shortcut on your

desktop.

Manually delete the DPM shortcut from your desktop.

895 The service <Setup service

name> was not deleted from

the computer.

Restart the computer to delete the service <Setup

service name>.

896 DPM could not connect to

database <database name>.

Verify that the SQL Server service <service name> is

started, and that you have permissions to query the

SQL Server.

897 DPM could not delete

database <database name>.

In SQL Server Management Studio, delete the following

databases: <database name>, <temporary database

name>.

898 DPM Setup cannot query the

SQL Server Reporting Services

configuration.


(WMI) service is running, and that your SQL Server

Reporting Services installation is not corrupt.


the MSDPMTrustedMachines

local group.

Manually delete the MSDPMTrustedMachines group.

On the Administrative Tools menu, click Computer


135

Error

Code


then click Groups. Right-click MSDPMTrustedMachines,

and then click Delete.

900 DPM Setup could not delete all

the registry keys that DPM

uses.


the DPM Agent Coordinator

service.

Manually delete the DPM Agent Coordinator service. On

the Administrative Tools menu, click Services. Right-

click DPM Agent Coordinator, and then click Delete.



compatible with the DPM

version. The protection agent

version is <agent version>, and

the DPM version is <computer

version>.

Update the protection agent on <server name>.



compatible with the DPM

version. The protection agent

version is <agent version>, and

the DPM version is <computer

version>.

Verify that all required DPM updates are applied to this

computer.

907 The job encountered an

internal database error.


914 The job failed because of an

unexpected error

Make sure that the DPMRA service is running on the

selected computer.

915 The operation failed because

the data source VSS

component <file name> is

missing.

Check to see that the protected data source is installed

properly and the VSS writer service is running.


an error occurred while

enumerating the data source

for the SqlServerWriter\

<database name> on which

mirroring was enabled using

Internet Protocol Version 4

Configure the mirrored database using a Fully Qualified

Domain Name (FQDN) instead of an IP address. DPM

cannot back up mirrored databases that are configured

with IP addresses.

136

Error

Code


(IPv4) or Internet Protocol

Version 6 (IPv6).

920 DPM has failed to write events

to the DPM Alerts event log.

Either the DPM Alerts event log

has been deleted or the

permissions have been

changed.

Uninstall DPM and then reinstall DPM to recreate the

DPM Alerts event log.

908 The job was canceled. The

user either canceled the job or

modified the associated

protection group.


909 DPM has received an

improperly formed message

and was unable to interpret it.

Retry the operation. If the problem persists, contact

Microsoft Customer Service and Support.

910 The DPM service terminated

unexpectedly during

completion of the job. The

termination may have been

caused by a system reboot.


911 DPM was not able to complete

this job within the allotted time.

In the Monitoring task area, group jobs by type and

review the job details. If the next scheduled occurrence

of this job is currently running, no action is required. If

the job is not currently running, retry the job.

912 The job has been canceled

because of the failure of

another job on which it

depended.


913 The job was canceled because

it was scheduled during the

inactivity timeframe.


916 Cannot connect to the DPM

service because it is running in

recovery mode, which was

initiated by the DpmSync tool.

Please wait for DpmSync to complete its operation. If

DpmSync is not running and the DPM service is still in

recovery mode, then run DpmSync again.

918 Connection to the DPM service Make sure that the DPM service is running. Review the

137

Error

Code


has been lost. application event log for information about a possible

service shutdown.

917 Connection to the DPM service

has been lost.

DPM service could be running in recovery mode, which

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

Console version <version

number> is incompatible with

the DPM server version.

Ensure that the version is between <minimum UI

version> and <maximum UI version>.

940 Unable to connect to the

database because of a fatal

database error. It is unlikely

that the database itself has

been damaged.

Review the event log and take appropriate action. Make

sure that SQL Server is running.

941 Unable to connect to the DPM

database.

Make sure that SQL Server is running and that it is


942 The integrity of the database

integrity is questionable

because of a hardware or

software problem.

Contact an experienced SQL Server administrator

whenever this error occurs. Look at Windows Event Log

for troubleshooting. Run DBCC CHECKDB to determine

the extent of the damage. It is possible that the problem

is in the cache only and not on the disk itself. If so,

restarting SQL Server corrects the problem. Otherwise,

use DBCC to repair the problem. In some cases, it may

be necessary to restore the DPM database.


database because the

database is in an inconsistent

state.

Contact an experienced SQL Server administrator

whenever this error occurs. In some cases, it may be

necessary to restore the DPM database. If the problem

persists, contact Microsoft Customer Service and

Support.

944 Database operation failed. Make sure that SQL Server is running and that it is

configured correctly. Then retry the operation.


database because of a general

database failure.

Make sure that SQL Server is running and that it is


946 Another instance of DPM is Restart the computer and then retry the operation

138

Error

Code


currently running. again.

948 Unable to connect to <server

name>.

Verify that the DPM service is running on this computer.

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:

<schedules updated>.

956 DPM is unable to protect your


farm until you install agents on

the following servers : <server

name>.

To install agents on these servers, on the Agents tab in

the Management task area, click Install in the Action

pane. If any of the above servers correspond to a

cluster, you need to install the DPM protection agent on

all the physical nodes of that cluster.

975 The arguments for the job

definition are not valid.

Retry the operation with the correct argument syntax.

976 The DPM job failed because it

could not contact the DPM

engine.

Restart the DPM service.


of a protection agent failure.


999 An unexpected error caused a

DPM service failure.

Restart the DPM service.

1000 Login failure caused by an

incorrect password.

Verify the password is correct and try again.

1002 You cannot cancel the selected

job at this time.

139

Error

Code


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>

Volume: <volume name>

Computer: <server name>

Description: Used disk space

on replica volume exceeds

threshold of <threshold value>.

For more information, open DPM Administrator Console

and review the alert details in the Monitoring task area.


Data source type: <data source

type>

Data source: <data source

name>


Protection group: <protection

group>

Description: Replica volume

cannot be detected.




Protection Group: <protection

group>

Description: DPM discovered

one of the following changes:

a. New shares or volumes



140

Error

Code


b. Deleted volumes or shares

c. Shares have been

remapped.

1204 The replica for <data source

name> on <server 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

task area by selecting the

Optimize performance action.

Manual consistency checks are

initiated by an administrator in

the Protection task area by

selecting the Create recovery

point action.





type> Data source: <data

source name>


Description: Replica is being

created.





inconsistent with the protected

data source. All protection

activities for this data source

will fail until the replica is

synchronized with consistency

check.





Description: Recovery jobs



141

Error

Code


started @ <start date time>.


Description: New protectable

computers found.




Description: Data copy job

failed




Description: Backup to tape

failed.






started @ <start date time>

completed with some failures.



1211 Recovery to <protected server

name> that started at <start

date time> completed. Some

jobs have successfully

recovered data and some jobs

have failed.






started @ <start date time>

completed successfully.





type>


name>


Description: Last <failure

count> recovery points not



142

Error

Code


created.



type>


name>


Description: Synchronization

jobs failing.





type>


name>


Description: DPM failed to stop

protection.





<server name> is not created.

You have chosen to create the

replica manually. All

subsequent protection



created and synchronized with

consistency check.






Replica creation job is

scheduled to run at a later

time. Data protection will not

start until replica creation is

complete.



1220 Status: <alert status> For more information, open DPM Administrator Console

143

Error

Code


Description: The disk <disk

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 DPM

protection agent.





Description: Unable to contact

DPM protection agent.





Description: Failed to update

end-user recovery

permissions.






Description: Network

bandwidth usage throttling not

working.




Description: DPM detected

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


144

Error

Code



<library type> : <library>

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.




<library type>: <library>

Tape: <media label>

Description: Tape erase job

failed



1244 Database size on DPM server

has exceeded the threshold

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

145

Error

Code


path>, but recommends you

modify protection as suggested

in Recommended Action.

2000 DPM failed to run the operation

because another conflicting

operation is in progress.

Retry the operation later.



Tape: <media list>

Description: Tape verification

job couldn't start or failed.




Description: Library catalog for

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

library





Tape: <media label>

Description: Detailed tape



146

Error

Code


inventory failed



Tape: <media label>

Description: Data integrity

verification failed.






Description: Used disk space

for recovery point volume

exceeds threshold of

<threshold value>.





type>


name>


Description: DPM failed to

configure protection.





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

exist.

The specified source path does not exist. Select a valid

path.

2033 DPM encountered an error 1) Refer to the detailed error code in the description

147

Error

Code


while performing an operation

for <file name>.

above. Retry this operation after the issue has been

fixed.

2) If the error was due to insufficient resources, then it

could be a transient failure and you should retry this

operation after some time.

2034 The specified path does not

reside on an NTFS volume.

The specified destination path does not reside on an

NTFS volume. Restore to an NTFS volume .


of inadequate disk space.

Increase the amount of free space on volume <volume

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

DPM was unable to access the

file/folder <file name> on

<agent protected server>. This

could be due to the file/folder

being corrupt or the file system

on the volume being corrupt.

1) Run chkdsk on the affected volume and then run

synchronization with consistency check.

2) If running chkdsk does not solve the problem, and

the server indicated above is a protected server (and

not the DPM server), consider deleting this file from the

source and then running synchronization with

consistency check.

2037 DPM could not detect the

selected volume <volume


Verify that <volume name> on <server name> exists. If

the volume exists, retry the operation.

2038 Some items were not

recovered because recovering

items across a reparse point is

not permitted. The folder

<reparse point path> under the

recovery destination is a

reparse point.

Retry the recovery to a destination that does not contain

a reparse point.

3000 The requested report history

could not be found in SQL

Server Reporting Services.

4067 The number of DPM licenses

must be greater than or equal

to zero.

Specify a number for the DPM licenses greater than or

equal to zero.

3001 Reporting Services Server

cannot connect to the DPM

To repair the configuration, follow steps for repairing

DPM from DPM Setup Help.

148

Error

Code


database.

3002 DPM could not generate this

report. A parameter is missing

or it was incorrectly specified.

3003 The SQL Server Reporting

Services service is not running.

Start the service on the computer on which the DPM

database was created. On the Administrative Tools

menu, select Services. Right-click SQL Server

Reporting Services, and then click Start.

3004 You have insufficient

permissions to perform this

action on the report.

Verify that you are an administrator on the DPM server.

If the DPM SQL database is hosted on a remote

computer, verify that you are a member of the DPM

administrators group on the remote SQL Server.

3005 DPM could not generate this

report. A parameter is missing

or it is incorrectly specified.

3006 The report you requested could

not be found on the SQL

Server Reporting Services

server.

Repair your DPM installation using the steps described

in the DPM 2010 Deployment Guide.

3007 The report cannot be displayed

because the report property

settings are incorrect.



3008 The SQL Server Agent service

<instance name> is not

responding.

Restart the SQL Server Agent service <instance

name>.

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

subscription for this report. The

information may be missing or

incorrect.

Click Options in the Actions pane, then click the SMTP

Server tab, and provide the correct SMTP server name

and e-mail address.

3011 There is not enough content to

generate a report for this time

period.

To generate this report, specify at least <day count>

days.

149

Error

Code


The number of days of

available data must be at least

<day count> before DPM can

generate this report.

3012 DPM cannot perform this

action because no valid

property settings have been

detected for this report.



3013 DPM could not connect to SQL

Server Reporting Services

server because of IIS

connectivity issues.

On the computer on which the DPM database was

created, restart the World Wide Web Publishing

Service. On the Administrative Tools menu, select

Services, right-click World Wide Web Publishing

Service, and then click Start.

3014 An error occurred causing the

reporting job on <server

name> to fail. The system files

may be corrupt.

Retry the reporting task. If the problem persists, repair

your DPM installation using the steps described in the

DPM 2010 Deployment Guide.

3015 DPM is unable to change the

e-mail settings.

Log on to <server name>. On the Start menu, point to

All Programs, point to Microsoft SQL Server 2008, point

to Configuration Tools, and then click Reporting

Services Configuration. In Configure Report Server,

update the e-mail settings.

3016 A Windows account is required

to view DPM reports.

To create the account, reinstall DPM using the steps

described in DPM Setup Help.

3021 DPM is unable to create the

Windows account group

because the group already

exists.

Delete the Windows account group, and then retry the

operation.

3017 The user account that DPM

Reporting created is disabled.

To reenable the account, in DPM Administrator 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

Windows account has expired.

Change the password for account <account name>. On

the Administrative Tools menu, click Computer


then click Users. Right-click <account name>, and then

150

Error

Code


click Set Password.

3020 Unable to configure local

Windows account in the

system. The operation is

allowed only on the primary

domain controller for the

domain.

Review the error details and take appropriate action.



Windows account because the

account already exists.

Delete the Windows account, and then retry the

operation.

3023 DPM is unable to configure the

Windows account because the

password you entered does

not meet the Group Policy

requirements.

Enter another password for the account.

3024 DPM cannot grant the DPM

database access to the <>

account.

Verify that SQL Server is running, and that it is


3025 You are unable to add the local

computer to the intranet

security zone in Internet

Explorer because of insufficient

permissions.

Log on as an administrator or backup operator, and

then try the operation again.

3027 The report schedule has

expired and will be reset.

Check the DPM report settings.


report schedule because the

date specified has already

past.

Specify today or a later date.


schedule because the time

specified has already past.

Specify a future date.

3032 The report file does not contain

an entry for the description.



3033 The report file contains an Repair your DPM installation using the steps described

151

Error

Code


incorrect description value. in the DPM 2010 Deployment Guide.

3028 You cannot add the computer

to the trusted zone.

We recommend that you reinstall Internet Explorer

Enhanced Security Configuration. Use Add or Remove

Programs in Control Panel. Click Add/Remove Windows

Components, and then check Internet Explorer

Enhanced Security Configuration. However, you can

proceed to the report by specifying your password in

subsequent steps.

3029 DPM has detected incorrect

property settings for certain

reports.



3034 DPM reporting requires

ASP.NET 2.0, which is not

found or installed on this

computer.

Install ASP .NET 2.0. Use Add or Remove Programs in

Control Panel. Click Add/Remove Windows

Components, check Applications Server, and then click

Details. Check ASP.Net and Internet Information

Services (IIS), and then click OK.

3155 Description: Data source

missing.



3167 The recovery jobs for <data

source name> that started at

<start date time>, with the

destination of <server name>,

have successfully completed.

No action required.

3168 DPM database (DPMDB) size

has exceeded the threshold

limit.

DPM database size: <DPM

database size> GB

DPM database location: <DPM

database location> on <server

name>.

The DPM database (DPMDB) size cannot be reduced.

To resolve this alert, you need to increase the free

space in the DPMDB volume, or increase the alert

threshold value in the tape catalog retention dialog. If

the tape catalog is very large, reducing the size of the

tape catalog may ensure that DPM database does not

grow any further.

3035 DPM is unable to read the

registry to retrieve report

settings because of insufficient

permissions.

Log on as an administrator and then retry the operation.

3036 DPM reporting cannot query Connect to the computer on which the DPM database

152

Error

Code


the IIS configuration. was created. Verify that the Windows Management

Instrumentation service is running.

3038 SQL Server Reporting Services

is not installed or is not

configured properly.

Verify that SQL Server Reporting Services is properly

installed and is running.

3039 DPM reporting is not yet

activated because the required

security settings could not be

applied to the DPMReport local

account.

On the Administrative Tools menu, click Local Security

Policy. Expand Local Policies, and then select User

Rights Assignment. Right-click Allow log on locally

policy, and then click Properties. Click Add User or

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 update

the report server configuration

to configure e-mail settings.

Log on to <server name>. On the Start menu, point to

All Programs, point to Microsoft SQL Server 2008, point

to Configuration Tools, and then click Reporting

Services Configuration. In Configure Report Server,

update the e-mail settings.

3050 Unable to update shares or

share permissions.

Re-run synchronization or wait for the next

synchronization to occur. If the problem persists, check

your domain configuration.

3051 Unable to update the Active


database.

Either run a synchronization, or wait for the next

scheduled synchronization to occur. If the problem

persists, check your domain configuration.

3052 Active Directory Domain

Services schema is not

configured properly.

Redo the schema extension operation.

3053 No nodes have been detected

for cluster <cluster>.

1. On the Agents tab in the Management task area,

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

missing for the following

applications: <list of data

sources>

Ensure that the dependent volumes for the data

sources are online.

3100 The used disk space on the

computer running DPM for the

Allocate more disk space for the replica. If no free disk

space is available in the storage pool, you may need to

153

Error

Code


replica of <data source type>

<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.

add physical disks to the computer running DPM.

3101 Recovery data for <data


name> on <server name> in

protection group <protection

group> resides on a volume

that cannot be detected. All


activities relating to <data

source name> will fail until this

volume is brought back online

or the replica is re-created.

Verify that the disk containing the replica volume and

the recovery point volume is shown in Disk

Management. If you are unable to locate the volumes in

Disk Management, use 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.

3103 DPM failed to obtain catalog

information as part of the

backup for <data source type>


<server name>. Your recovery

point is valid, but you will be

unable to perform item-level

recoveries using this recovery

point.

1) If you do not expect to be performing item-level

restores using this recovery point, then dismiss this

alert; otherwise, take the recommended actions in the

subsequent steps.

2) If the operation failed for a short-term backup to disk,

in the Protection task area, select the data source and

click Create recovery point to restart the backup.

3) If the operation failed for a short-term backup to tape,

in the Protection task area, select all the failed data

sources that belong to the same protection group, and

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.


type> <data source name> is

currently being synchronized

with consistency check. A

consistency check can be

No action required.

154

Error

Code


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 task area by

selecting the Create recovery

point action.



<server name> is being

created. After the initial replica

is created, only incremental

changes are synchronized.

No action required.



<server name> is inconsistent

with the protected data source.

All protection activities for data

source will fail until the replica

is synchronized with

consistency check. You can

recover data from existing

recovery points, but new

recovery points cannot be

created until the replica is

consistent

Synchronize with consistency check.




date time>, with the destination

of <server name>, are in

progress.

No action required.




Make sure that the file is not already present and in use

on the destination computer, and that there is sufficient

155

Error

Code



of <server name>, have

completed. Some jobs

successfully recovered data

and some jobs failed.

The following items could not

be recovered: <temporary list

of files>.

disk space for the files.





of <protected server name>,

have completed. Most or all

jobs failed to recover the

requested data.

On the Jobs tab in the Monitoring tasks area, group jobs

by type to view details of the recovery jobs.





of <server name>, have

successfully completed.

No action required.

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



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

156

Error

Code


number of failed jobs = <failure

count>. The last job failed for

the following reason:

3116 DPM failed to stop protection



name>.

If you no longer want to protect any data sources on the

computer, you can uninstall the protection agent from

the computer. You can also retry the stop protection job.

3117 New computers were found

that you may want to protect.

See Details for list of computers.




You have chosen to create the

replica manually. All




created and synchronized with

consistency check.

1) Manually copy data to the replica path as specified in

the details for this data source in the Protection task

area.

2) After you copy the data, click the link below to

synchronize with consistency check.




Replica creation job is

scheduled to run at a later

time. Data protection will not

start until replica creation is

complete.

No action required.

3120 The disk <disk name> cannot

be detected or has stopped

responding. All subsequent

protection activities that use

this disk will fail until the disk is

brought back online.

On the Disks tab in the Management task area, check

the status of disks. If a disk is missing, rescan the disk

configuration to detect the disk. If the disk is still

missing, verify physical disk connections and perform

Rescan again. If the disk is no longer available, you can

remove the disk from the storage pool. To continue

protecting the affected data, stop protection of the data

sources 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

157

Error

Code


found. and review the alert details in the Monitoring task area.

3121 The DPM protection agent on

<server name> is incompatible

with this DPM instance. All

subsequent protection and

recovery activities for <server

name> will fail until the correct

version of the agent is

installed.


the status of the agent and update to the correct

version.

3122 The DPM protection agent on

<server name> could not be

contacted. Subsequent

protection activities for this

computer may fail if the

connection is not established.

The attempted contact failed

for the following reason:


the status of the agent.

3123 Failed to update permissions

used for end-user recovery on

<server name>. Permissions

update failed for the following

reason:

3124 DPM network bandwidth usage

throttling is not working

because the Windows Quality

of Service (QoS) Packet

Scheduler is not enabled on

<server name>.

Either stop the DPM protection agent service on

<server name> and make sure that the QoS Packet

Scheduler is enabled, or disable network bandwidth

usage throttling for the computer. To install the QoS

Packet Scheduler: In Control Panel, point to Network

Connections, right-click the appropriate connection, and

then click Properties. On the General tab, click Install,

click Service, click Add, click QoS Packet Scheduler,

and then click OK.

3125 DPM has discovered new

unsupported files or folders on

one or more protected

volumes. DPM will continue to

protect the supported data on

these volumes, but will not

protect the unsupported data.

158

Error

Code


3126 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.

To start protecting <new folder path>, in the Protection

task area, perform the following steps:

1) Stop protection for this share.

2) Re-protect the same share again.

To setup protection properly for the <old folder path>, in

the Protection task area, perform the following steps:

1) Stop protection for this share.

2) Protect <old folder path>.

3127 DPM detected multiple disks

with the same disk

identification number (DiskID).

None of these disks will be

added to the DPM Storage

Pool.

1) Check to see that multipath software is running on

the DPM server.

2) In the Management task area, on the Disks tab, click

Rescan.

3151 DPM was unable to complete

this job within the time

allocated.

In the Monitoring task area, group jobs by type and

review the job details. If the next scheduled occurrence

of this job is currently running, no action is required. If

the job is not currently running, retry the job.

If you retry a synchronization job and it fails again,

consider enabling on-the-wire compression. For more

information, see "How to Enable On-the-Wire

Compression" in DPM Help.

3152 Choose to send Microsoft

anonymous feedback

automatically about your

hardware and software

configurations, and feature

usage patterns.

Opt-in or opt-out of the Customer Experience

Improvement Program.

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.

159

Error

Code


3161 Recovery data for <data


name> in protection group

<protection group> resides on

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.

Verify that the disk containing the replica volume is

shown in Disk Management. Or, in the Protection task

area in DPM Administrator Console, use the Modify disk

allocation action to allocate replica space.



being created. After the initial

copy is made, only incremental

changes are synchronized.

No action required.





are in progress.

No action required.



inconsistent with the protected

data source. All protection

activities for data source will

fail until the replica is

synchronized with consistency

check.





have completed. Some jobs

have successfully recovered

data and some jobs have

failed.

On the Jobs tab in the Monitoring tasks area, filter jobs


3166 The recovery jobs for <data On the Jobs tab in the Monitoring tasks area, filter jobs

160

Error

Code




destination of <protected

server name>, have

completed. Most or all jobs

failed to recover the requested

data.


3169 The used disk space on the

computer running DPM for the

recovery point volume of <data


name> has exceeded the

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.

Allocate more disk space for the recovery point volume

using the Modify disk allocation action in the Protection

task area. If no free disk space is available in the

storage pool, you may need to add physical disks to the

computer running DPM.

3170 DPM could not start a recovery,

consistency check, or initial

replica creation job for <data


name> on <server name> for

following reason:\n

3171 The start time is greater or

equal to the end time. Please

correct the filter definition.

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.

161

Error

Code


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

points of the replica failed for

<data source type> <data


name> when one of the

following operations was being

performed:

Express full backup

Consistency check

Recovery

Check the Alerts tab in the Monitoring task area to

locate the specific alert for the operations indicated

above. Follow the recommended action for that alert. If

you do not find any active alerts for the operations

indicated above, you should click the link below to

inactivate this alert.

3179 There already exists a filter

with the given name. Please

specify a different filter name.

3200 Could not access end-user

recovery-specific information in


Services

Check the domain configuration to ensure that the DPM

schema extension has been successfully applied to the

Active Directory. Also verify that DPM has permissions

to access the data in the extended schema.

3201 DPM failed to log in with the

specified password.

Check your password and then retry the operation.

3202 Could not access end-user

recovery-specific content in


Services.

Re-run synchronization or wait for the next

synchronization to occur. If the problem persists, check

your domain configuration.

3301 <library type> <library> could

not be contacted. All jobs for

<library type> <library> will fail

if the connection is not

162

Error

Code


established. The attempted

contact failed for the following

reason:\n

3302 <library type> <library> is not

functioning efficiently for the

following reason:

The drive information for

<library type> <library> is

incorrect and needs to be

refreshed.

The number of drives reported for this library is different

from the number of drives detected by DPM. If any

drives are out of the library for servicing, ignore this

alert; otherwise, remap the drives within the library

manually. For information about remapping tape library

drives, see the DPM 2010 Operations Guide.

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

label> tape as

decommissioned, which means

that data cannot be written to

this tape in the future. You may

be able to recover data from

this tape.

This tape is decommissioned and should be removed

from the library. You may be able to recover data from

this tape. If recovery from this tape fails, check for a

duplicate or older copy of the data.

3305 The number of free tapes in

the <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.

Add tape to the library and mark it as free.

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

163

Error

Code


3310 The data copy job failed for the

following reason:\n

3311 The back up to tape job failed

for the following reason:

3312 The backup to tape job

completed, but the catalog was

not built correctly for <data



Although no data is lost, you

must rebuild the catalog to

access the data of the backup

job.

3313 Verification is completed for the

following tape(s) in <library

type> <library>: <media list>

No action required.

3316 The detailed inventory of tape

failed for the following reason:

3500 Your search returned more

than 250 results. Only 250

results can be displayed.

Use the search controls to refine your search.

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

because the required tape is

not available in <library type>

<library>.

Insert the required tape in the library through the I/E

port or by unlocking the library door. Click "Continue

Job" in the details section of this alert, if you add the

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

because the required tape

<media label> is not available

in the library <library type>

<library>.

Insert the tape with label <media label> in the library

through the I/E port or by unlocking the library door.

Click "Continue Job" in the Details section of this alert, if

you add the required tape without using the Add tape

(I/E port) or Unlock Door actions on the Library tab in

164

Error

Code


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

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

165

Error

Code


database was detected. DPM

cannot continue loading DPM

Administrator Console.

the DPM 2010 Operations Guide, and then retry the

operation.

3750 Version <database version> of

the DPM database, and

version <binary version> of the

DPM application are not

compatible.

Restore a valid database using the steps described in

the DPM 2010 Operations Guide, and then retry the

operation.

3751 The evaluation copy of DPM

has expired.

You must purchase a DPM license. For details about

obtaining a DPM license, see the Microsoft System

Center Data Protection Manager Web site at:

http://go.microsoft.com/fwlink/?LinkId=86309.

3752 DPM could not find the

MSDPMTrustedMachines

security group. Either this

group has been deleted or the

entry is corrupt.

Uninstall DPM and then re-install DPM to recreate the

security group.

3753 The version of the DPM

database installed on this

computer is later than the

version of the DPM application.

To continue using DPM, you must install any service

packs or hotfixes that were part of your previous DPM

installation.

3754 DPM Administrator Console

can be opened only by a user

belonging to a domain. Log on

using a domain user account,

and try again.

4026 DPM Setup failed to configure

the service <service name>.

Use Add or Remove programs in Control Panel to

uninstall DPM. After uninstalling, run DPM Setup again.

4027 DPM Setup was unable to

collect information about

volumes in the storage pool

because access to the

database was denied.

Manually delete the volumes allocated to the storage

pool or format the disks.


<database name> database.

Manually delete the database using SQL Server

Management Studio.

4001 There is insufficient disk space To continue with the installation, free up <system disk

166

Error

Code


on system volume <system

drive> to complete the

installation.

space required> MB of disk space on the system

volume.

4002 The SQL Server Reporting

Services installation is not valid

because it is installed on a

computer on which Internet

Information Services (IIS) or

ASP.Net is not installed.

Uninstall SQL Server 2008, and then run DPM Setup

again to install the prerequisite software.

4003 Setup has detected that the

installation of Reporting

Services is not correctly

configured or no instance of

Reporting Services is linked to

<instance name> of SQL

Server.

1) To use the local dedicated MS$DPM2007$ instance

with DPM, uninstall SQL Server and run setup again.

2) To use the option of installing DPM with an existing

instance of SQL Server, make sure that the Reporting

Services instance is also installed and linked correctly.

For details, refer to DPM Setup Help.

4005 DPM found the following

databases that were created

by an earlier installation of SQL

Server Reporting Services:

<comma separated database

names>.

Setup will delete these databases.

4006 Service <name> is running

under <credentials>

credentials. <name> must run

under local user credentials.

DPM Setup will change the credentials to a local user

account.

4007 Service <name> is not

installed. The <prerequisite>

installation is not valid.

Uninstall <prerequisite> and then run DPM Setup again.

4012 The <name> service is running

under <credentials>

credentials. We recommend

that the service run under the

NT Authority\NetworkService

account.

In the Reporting Services Configuration tool, choose

'Windows Service Identity' and change the settings to

the built-in Network Service account for <SQL Server

instance name> instance of SQL Server 2008.

4015 You installed DPM protection

agents on several computers.

In DPM Administrator Console, click Management on

the Navigation bar. On the Agents tab, select the

167

Error

Code


We recommend that you

uninstall them before

proceeding.

agents, and then click Uninstall.

4017 DPM database <DPM

database> is missing or

corrupt.

If you are performing a clean installation of DPM, you

must delete the DPM database before you run Setup. If

you are upgrading or repairing an existing installation of

DPM, you must restore a valid DPM database, and then

proceed with Setup.

4019 DPM Setup detected an

existing DPM database in the

<SQL Server instance name>

instance of SQL Server. DPM

cannot be installed on an

existing database.

In SQL Server Management Studio, delete the <DPM

database> database, and then run DPM Setup again. If

you need to reuse an older DPM database, back up the

database and restore it after completing the DPM

installation.

4020 DPM Setup detected several

existing protection groups.

In DPM Administrator Console, in the Protection task

area, remove the groups from protection, and then run

DPM Setup again.

4021 DPM Setup could not access


Services. You cannot proceed

with the DPM Installation.

Verify that the computer is joined to a domain, that DNS

is correctly configured, and that you are logged on as a

domain user with administrator user rights.

4023 The <prerequisite> installation

failed. All changes made by the

<prerequisite> installation to

the system were rolled back.

Manually install <prerequisite>. For instructions, see

"Manually Installing Prerequisite Software" in the






Manually install <prerequisite>. For instructions, see



4025 The <prerequisite>

configuration failed.

Use Add or Remove programs in Control Panel to

uninstall <prerequisite>. After uninstalling

<prerequisite> run DPM Setup again.

4032 DPM could not delete the

<account name> user account.

Manually delete account <account name>.

4033 DPM Setup could not remove

the DPM Administrator

Manually delete the DPM Administrator Console

shortcuts.

168

Error

Code


Console shortcuts from:

<comma separated shortcut

locations>.


service <service name>.

Manually delete service <service name>. On the

Administrative Tools menu, click Services.

4036 The DPM database was

removed, however, DPM could

not remove database files

<database files complete

location>.

Delete the database files manually.


schedules from the master

database.

Open SQL Server Management Studio, and connect to

the DPM instance of SQL Server. Expand the instance

of SQL Server, browse to SQL Server Agent, and then

in Jobs, delete the <schedule category> category.

4030 Setup was unable to remove

reports deployed with SQL

Server Reporting Services.

If you are reinstalling DPM on this computer, no action

is necessary. If you are not reinstalling DPM, you must

uninstall SQL Server 2008 to remove the reports.

4031 The computer <computer

name> could not be removed

from the intranet security zone

settings in Internet Explorer.

In Internet Explorer, on the Tools menu, click Internet

Options. In the Internet Options dialog box, on the

Security tab, click Local intranet, click Sites, then click

Advanced, and then remove computer <computer

name> from the intranet zone.


the <group name> group on

computer <computer name>.

Delete the group manually. On the Administrative Tools

menu, click Computer Management. Expand Local

Users and Groups, and then click Groups. Right-click

<group name>, and then click Delete.

4037 To finish deleting service

<service name>, you must

restart the computer.

Restart your computer.


unmount the volumes from

<volumes directory>.

Manually unmount the volumes using Disk

Management.

4039 This computer has less than

the recommended amount of

memory for optimal

performance of DPM. The

Add more memory to this computer or install DPM on a

different computer.

169

Error

Code


recommended amount of

memory is 2 GB.

4040 The domain controller role is

enabled on this computer.

DPM does not support

installing DPM on a domain

controller.

Install DPM on a computer that is not a domain

controller.

4042 Setup has detected that SQL

Server 2008 Service Pack 1

has not been installed on the

selected SQL Server.

Install SQL Server 2008 Service Pack 1 or higher and

try again.

4045 DPM Setup was unable to set

permissions on folder

<directory path>.

Verify that the folder <directory path> is a valid location

and that the current user has access to the location.

4046 DPM cannot delete <file

name>.

Verify that the current user has permissions to delete

the file.


configure service <Setup

service name>.


and then try running DPM Setup again.






uninstall DPM. Then manually install <prerequisite>. For

instructions, see "Manually Installing Prerequisite

Software" in the DPM 2010 Deployment Guide.






uninstall DPM. Then manually install <prerequisite>. For

instructions, see "Manually Installing Prerequisite

Software" in the DPM 2010 Deployment Guide.

4054 Setup was unable to add

protected computers to the

<DCOM Users Group> group.

Review the error details. Use Add or Remove Programs

in Control Panel to uninstall DPM, and then run DPM

Setup again.

4065 You did not specify the . Specify a .

4066 You did not specify a company

name.

Specify a company name.

4072 The specified path <file name>

is invalid.

Specify a valid path and verify that the path is

accessible.

170

Error

Code


4073 The command line argument

<command line argument> is

invalid.

See "Installing DPM" in DPM Setup Help.

4074 The path <file name> exceeds

<maximum limit> characters.

Choose a path with a shorter length.

4075 The command line argument

<command line argument> is

already specified.


4051 There is insufficient disk space

on the program files volume

<binary drive> to complete the

installation.

To continue with the DPM installation, free up <binary

disk space required> MB of disk space on the volume.

4052 You cannot install DPM on a

server if a DPM protection

agent has been installed it.


remove the protected

computers from the <DCOM

Users Group> group.

Delete the protected computers from the group. On the

Administrative Tools menu, click Computer


then click Groups. Right-click <DCOM Users Group>,

and then click Delete.


remove DPM and the

protection agent from the

Windows Firewall exceptions

list.

If Windows Firewall is enabled, remove DPM and the

protection agent from the exceptions list. In Control

Panel, click Windows Firewall, click the Exceptions tab,

and then delete Microsoft System Center Data

Protection Manager 2007 and the Microsoft System

Center Data Protection Manager 2007 Replication

Agent from the list of exceptions.

4056 DPM Setup was unable to add

DPM to the Windows Firewall

Exceptions.

Review the error details. In Control Panel, click

Windows Firewall, and on the General tab, verify that

the "Don't allow exceptions" option is unchecked. Use

Add or Remove Programs in Control Panel to uninstall

DPM and then run DPM Setup again.


on the database volume

<database drive> to complete

the installation.

To continue with the installation, free up <database disk

space required> MB of disk space on the volume.

171

Error

Code


4058 DPM requires the

Microsoft$DPM$ instance of

SQL Server. None of the

existing SQL Server

installations have the name

Microsoft$DPM$. Setup will

install the Evaluation Edition of

SQL Server 2008, which will

expire in 180 days.

To avoid expiration of SQL Server 2008, exit Setup and

install the SQL Server 2008 licensed retail copy, or

upgrade to SQL Server 2008 within 180 days. To

properly configure the SQL Server 2008 settings, see



4059 DPM Setup installs the

Evaluation Edition of SQL

Server 2008 which expires

180 days after installation.

To avoid expiration of SQL Server 2008, exit Setup and

install the SQL Server 2008 licensed retail copy, or

upgrade to SQL Server 2008 within 180 days. To

properly configure the SQL Server 2008 settings, see



4063 The Default Web site that

Internet Information Services

(IIS) uses is disabled. You

cannot install or run SQL

Server Reporting Services if

this Web site is unavailable.

At the command prompt, run inetmgr.exe. To enable the

Default Web site, expand the Web Sites folder, right-

click Default Web Site, and then click Start.

4064 The Default Web site used by

Internet Information Services

(IIS) does not exist. SQL


Services cannot be installed or

run unless this Web site is

available.

Use Add or Remove Programs from Control Panel.

Uninstall SQL Server 2008 and SQL Server 2008

Reporting Services if already installed. Uninstall Internet

Information Services (IIS). Then run DPM Setup again

to install IIS and SQL Server 2008 with Reporting

Services with the correct configuration.

4068 Installation source <folder

path> for installing

prerequisites either does not

exist or cannot be accessed or

Setup cannot find one or more

prerequisites at the location.

Make sure that the DPM installation DVD is copied

correctly and re-run Setup.

4069 The input <input parameter

tag> is mandatory.

Specify a valid input <input parameter tag>.

4070 The prerequisite check failed

with errors.

Review the errors in the DPM setup log file <Setup log

file>. Resolve the errors, and then run DPM Setup

172

Error

Code


again.


the DPM Administrator

Console shortcut from:

<comma separated shortcut

locations>.

Please delete the shortcuts manually.

4076 The value for <command line

argument> was not specified.

See "Installing DPM" in the DPM Setup Help.

4077 DPM is not installed on this

computer.

Run DPM Setup from the DPM product DVD.

4078 DPM is already installed on

this computer

To uninstall DPM, use Add or Remove Programs in

Control Panel.

4079 DPM is not installed on this

computer.

To install DPM, see "Installing DPM" in DPM Setup

Help.

4080 No IN file is specified in the

command line.


4081 DPM configuration failed. Refer to the "Troubleshooting" section of DPM Setup

Help.

4082 DPM cannot start service

<Setup service name>.

Start the service manually. On the Administrative Tools

menu, click Services. Right-click <Setup service name>,

and then click Start.

4083 DPM setup could not configure

agents.

Refer to "Troubleshooting" section of DPM help.

4084 DPM setup could not configure

SQL Server 2008 Reporting

Services.

Refer to "Troubleshooting" section of DPM help.

4086 DPM has been successfully

installed. However, DPM Setup

could not delete the extracted

folder <folder path>.

Delete folder <folder path> manually.


the extracted folder <folder

path>.

Delete folder <folder path> manually.

4088 DPM Setup could not delete Delete the directory manually. On the Administrative

173

Error

Code


the virtual directory <folder

path>.

Tools menu, click Internet Information Services (IIS)

Manager. Expand the Web Sites folder, expand Default

Web Site, and then delete the virtual directory <folder

path>.

4089 DPM Setup could not configure

the database <database

name>.

Verify that the MSSQL$<instance name> service is

started. If the service is not started, on the

Administrative Tools menu, click Services. Right-click

MSSQL$<instance name>, and then click Start.

4090 DPM Setup detected that

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

determine the edition of SQL

Server used in the current

installation of DPM.

If the current installation of DPM uses an expired

instance of the Evaluation Edition of SQL Server 2008,

you must manually upgrade to the retail edition of SQL

Server 2008. For instructions, see the DPM 2010

Deployment Guide. For more information about this

error, see the application event log.

4093 DPM Setup has detected that

the current installation of DPM

uses the Evaluation Edition of

SQL Server 2000 Reporting

Services. Setup will upgrade to

the retail edition of SQL Server

2000 Reporting Services as

part of the upgrade of DPM.

No action required.

4208 DPM Writer could not access

the registry.

Make sure that Data Protection Manager is installed

correctly.

4211 You do not have sufficient

privileges to perform this

operation.

On the DPM server, use Event Viewer to view details for

this event. The details are available in the application

event log.

174

Error

Code


4094 DPM Setup could not

determine the edition of SQL


Services used in the current

installation of DPM.

Verify that the Report Server and World Wide Web

Publishing services are running: In Control Panel, click

Administrative Tools, click Services, and check the

Status column for each service.


the current installation of DPM

uses an expired instance of the

Evaluation Edition of SQL


Services.

Manually upgrade to the retail edition of SQL

Server 2000 Reporting Services, and then run DPM

Setup again. For instructions for upgrading Reporting

Services, see the DPM 2010 Deployment Guide.

4200 The DPM Writer service could

not be accessed.

Review the Application Event log for more details. Verify

that DPM is installed and that the DPM Writer service is

running.

4201 The backup operation did not

complete successfully. Some

backup shadow copies could

not be created.

Ensure that the DPM replicas are not busy and retry the

operation.

4206 DPM Writer could not connect

to the <database name>

database.

Make sure that the SQL Server instance used by DPM

is running and is accessible over network.

4207 DPM Writer could not query the

<database name> database.

Make sure that the SQL Server instance used by DPM

is running and is accessible over network.

4209 DPM Writer encountered an

internal error.

Please restart the DPM Writer service, and then try the

backup operation again. For additional troubleshooting

information, review the application event log and the

DPM Troubleshooting Guide.

4210 DpmBackup encountered an

internal error.

Please try the backup operation again. For additional

troubleshooting information, see the DPM

Troubleshooting Guide.

4216 DpmPathMerge could not

query the <database name>

database.

Make sure that the SQL Server services are running

with appropriate privileges.

4217 DpmPathMerge could not

access the registry.

Make sure that Data Protection Manager is installed

correctly.

4317 DPM Setup failed to disable Manually stop and disable the Removable Storage

175

Error

Code


the Removable Storage

service (NtmsSvc).

service. On the Administrative tools menu, click

Services. Right-click Removable Storage, and then click

Stop. Then run DPM Setup again.

4318 DPM Setup failed to create the

DPMRADCOMTrustedMachine

s or

DPMRADmTrustedMachines

group.



4319 DPM has been successfully

installed. However, you must

restart the computer to

complete the DPM installation.

Restart the computer to complete the DPM installation.


configure the

DPMRATrustedMachines

Group security settings.



4320 You cannot install DPM on a

computer with Microsoft

Cluster service enabled.

Use the Cluster Administrator tool to remove this

computer from the cluster or install DPM on another

computer.

4323 DPM Setup failed to add a user

to the local group.



4218 DpmPathMerge encountered

an internal error.

Please try the operation again. For additional

troubleshooting information, see the DPM

Troubleshooting Guide.

4219 Either because this replica was

restored from a backup that

was not created using the

DpmBackup tool, or because

the GUID of the protected

volume has changed since the

backup was created,

DpmPathMerge cannot

automatically remove

extraneous path information.

To ensure that this replica is consistent with the

protected data, run the FsPathMerge tool to manually

remove extraneous path information from the restored

replica. For instructions for using FsPathMerge, see the

DPM Operations Guide.

4220 DPM writer was unable to

snapshot the replica of <data

source name>, because the

In DPM Administrator Console, run a consistency check

for the data source to ensure that the replica is

176

Error

Code


replica is not in a valid state

(Validity: <validity>).

consistent.

4221 DPM Writer has timed out

waiting for replica to be free

and available for snapshot.

Retry again when no jobs are running for the selected

data source.

4222 DPM has run out of free

recovery point space and will

fail snapshots for <data source

name> in order to prevent

existing recovery points from

getting recycled.

1) Increase the space allocated for the recovery point

volume for <data source name>.

2) Retry the operation after increasing the space for the



the DPMRA service.

Delete the DPMRA service manually. At the command

prompt, type "sc delete DPMRA".


uninstall the Dr. Watson

version that DPM installed.

For information about manually uninstalling Dr. Watson,

see "Troubleshooting" in DPM Setup Help.


the required version of

Windows PowerShell is not

installed. This software is

required for DPM to run

correctly.

Install Windows PowerShell and Power shell

Multilanguage User Interface pack. Then run DPM

Setup again.

4304 DPM Setup detected that the

Single Instance Store (SIS)

component is not installed.

This software is required for

Data Protection Manager to

run correctly.

To install SIS, run "start /wait ocsetup.exe SIS-

Limited /quiet /norestart" from the command-line and

restart the computer. Then run DPM setup again

4305 DPM Setup detected a

previous version of Microsoft

Management Console.

Download and install Microsoft Management Console

3.0 from http://go.microsoft.com/fwlink/?LinkId=55423

or upgrade the operating system to Windows

Server 2003 R2, and then run DPM Setup again.

4306 DPM Setup is unable to use

the credentials provided to log

on as <username>.

Review the error log for details. Verify that the Remote

SQL Server administrator credentials you provided are

correct and that they have logon permissions on the

local computer.

177

Error

Code


4307 DPM Setup is unable to

connect to the specified


Verify that the specified computer and the instance of

SQL Server meets the following requirements:

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 instance

was specified.

Specify a valid instance of SQL Server.

4309 The SQL Server 2008

installation failed. All changes

made by the SQL Server 2008

installation to the system were

rolled back.

Manually install SQL Server 2008. For instructions, see



4312 DPM Setup detected that the

Removable Storage service is

running. To install DPM

correctly, DPM Setup will stop

and disable this service.


the DPM Library Agent service.

Delete the service manually. At the command prompt,

type "sc delete DPMLA".


share the folder

[InstallLocation]\Temp as

MTATempStore$.



4310 The SQL Server 2008

installation failed.

Review the SQL Server installation log file for failures,

and then take the appropriate action.

4315 DPM Setup could not configure

the security settings for this

computer.

Verify that the DPM server is a member of a domain

and that a domain controller is running. Additionally,

verify that there is network connectivity between the

DPM server and the domain controller.

4321 DPM cannot access registry

key <registry key> on

computer <computer name>.

Verify that the registry key exists, that user <> has full

permissions, and that the Remote Registry service is

running on this computer and computer <computer

178

Error

Code


name>.

4324 You cannot choose the

instance <instance name> on

the local computer.

Specify a different instance to install DPM or choose the

option to let DPM install its own SQL Server instance. If

DPM's SQL Server instance already exists, it will be

reused.

4325 DPM Setup failed to get the

fully qualified domain name for

either the computer running

DPM or the computer with the

selected instance of SQL

Server.

Verify that computers are joined to the same domain,

that the DNS client service is running, and that DNS is

accessible over the network. Then run DPM Setup

again.

4326 DPM Setup failed to create

certificate stores required for

DPM.



4327 Setup failed to delete the

certificate stores created for

DPM.

At a command prompt, run "certutil.exe -delstore" to

delete the certificates in DPMBackStore and

DPMRestoreStore.

4328 The service <name> is running

under <credentials>

credentials. It should be

running under domain user

credentials.

Run the SQL Configuration tool on the computer

running SQL Server to change the account for the

services. Then try again.

4329 DPM setup is unable to verify if

the Microsoft Cluster service is

enabled on this computer.

Verify that this computer does not have the Microsoft

Cluster service enabled, and then proceed with the

DPM installation.

4330 DPM Setup could not remove

the account <user account

name> from the group <group

name>.

Manually delete account <user account name> from the

group.

4331 The Microsoft System Center

DPM Support Files on the SQL

Server computer <computer

name> were not removed.

If no other DPM server is using the server for hosting

the DPM database, uninstall the Microsoft System

Center DPM Support Files using Add or Remove

Programs in Control Panel.

4332 Could not query database

<database name> from the

<instance name> instance of

Review the error message and retry the action:

<exception message>

179

Error

Code


SQL Server.

4333 DPM Management Shell is

already installed on this

computer.

On the Start menu, select "DPM Management Shell"

from "Microsoft System Center Data Protection

Manager 2007".

4334 DPM 2010 cannot be installed

on the same computer as

DPM 2006.

Install DPM 2010 on a different computer and migrate

your settings using the upgrade tool. For details, refer 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

invalid.

Run MigrateDPM2006 [-exportSettings] [-

dpm2006server ServerName] to recreate the file.

4337 The DPM protection agent is

not installed on the computer

<computer name>.

Install the agent and try the operation again.

4338 Could not find configuration for

<computer name>.

Enter a valid name for a computer configuration to

migrate.

4339 Failed to copy file <file name>

from <source location> to

<destination location>.




on the database volume

<database drive> on

<computer name>.

Free <database disk space required> MB of disk space

on the volume to continue with the installation.

4341 Setup cannot query the SQL

Server.

Make sure that SQL Server service is running.

4342 A restart is required to

complete the uninstallation of

Data Protection Manager.

4343 MigrateDPM2006 has

encountered an error.

Make sure that:

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

180

Error

Code


installation of Microsoft System

Center DPM Support Files on

the selected SQL Server.

or installation share, and try again. The package is

located inside the DPM 2010 install (msi) folder.

4345 Setup has detected that the

selected SQL Server has an

older version of Microsoft

System Center DPM Support

Files installed.

Install the latest SQLPrep.msi located on the installation

DVD or installation share, and try again. The package is

located inside the DPM 2010 install (msi) folder.

4346 The settings for data source

<data source name> on server

<server name> have not been

imported to this DPM server.

Run MigrateDPM2006 [-importSettings] [-

dpm2006server ServerName] [-protectedServer

ServerName] and then retry the data copy.

4347 Copy for replica <data source

name> on computer <server

name> failed and this data

source is being skipped.



4348 DPM requires the Named

Pipes protocol to be enabled

on the selected instance of

SQL Server.

On the selected server, run the SQL Server

Configuration Manager tool and enable the network

configuration for the selected instance.

4349 Unable to set permissions on

the folder corresponding to

"MTATempStore$" share.


and then retry the installation.

4350 DPM Upgrade marked replicas

are invalid.

4351 Setup has detected that client-

side certificates are required

for Internet Information

Services on this computer.

DPM does not support IIS

requiring client-side

certificates.

On the selected server, in Administrative Tools, run

Internet Information Services Manager. For the Default

Web site, select "Properties" and click the "Directory

Security" tab. Under "Secure Communication", click

"Edit" and set the option for client certificates option to

"Ignore client certificates" or "Accept client certificates".

4352 Setup was unable to mount

replica volumes under the path


Using Disk Management, manually mount the DPM

volumes before using DPM.

4353 Setup was unable to dismount Using Disk Management, manually dismount the DPM

181

Error

Code


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

required hotfix is missing.

Install hotfix 940349 from

http://support.microsoft.com/kb/940349, and then run

DPM Setup again.

4357 Setup has detected that this

DPM server is using a shared

library.

Disable library sharing by running the following

commands and launch setup again.

1. SetSharedDPMDatbase.exe –RemoveDatabaseSharing.

2. AddLibraryServerForDpm.exe -DpmServerWithLibrary -Remove

4358 DPM setup has detected the

Default Web Site is not

configured to use port 80.

At the command prompt, run inetmgr.exe. To change

port for the Default Web site, expand Web Sites, right

click Default Web Site, and select properties. Configure

'TCP port' setting to '80'.Then, run setup again.

4359 DPM Setup was unable to set

security permissions on some

of the volumes in the storage

pool. The volume may be

missing.

Ensure all volumes are online. In Disk Management

Console, right-click every DPM volume and select

Properties. From the Security tab, restrict access to the

volumes for administrators group and the LocalSystem

account only by applying the appropriate permissions.

4360 DPM setup cannot upgrade the

existing installation because

the DPM database version

does not match with installed

DPM version.

Ensure correct SQL data files are copied from existing

DPM SQL instance and attached to the given SQL

instance. Then, run DPM 2010 Setup again.


<file name> because the

SYSTEM account has been

denied permission.

Set the permissions for the SYSTEM account to allow

Full Control of the item.

182

Error

Code



<file name> because the

SYSTEM account has been

denied permission.


Full Control of the item.

2304

3

DPM has unexpectedly

reached the end of the tape

<media label>. This could be

because the tape was

tampered with.

If you have another copy of this tape, then retry

recovery using the copy.

2304

4

Rescan cannot be performed

because DPM is currently

performing other operations on

the server.

Wait for the other operations to complete, and then retry

this operation.

2304

5

DPM failed to move one or

more tapes to the I/E port slots

1) Check to see that the library door is locked and that

the I/E port is retracted. 2) Check to see that there are

sufficient free I/E port slots in the library.

6012 DPM cannot access mount

points under the path <file

name> because the SYSTEM

account has been denied

permission.


List Folder Contents and Read for items in the specified

path.

6013 DPM cannot access mount

points under the path <file

name> because the SYSTEM

account has been denied

permission.


List Folder Contents and Read for items in the specified

path.

2400

7

Tape <media label> cannot be

marked as a cleaning tape

because it is not a cleaning

tape.

2400

8

DPM cannot complete the

requested operation on tape

<media label> because this

tape is being used by some

other job.

Retry the operation later.

2401

4

Library lacks power or cables

are not connected properly

1) Verify that the library is turned on.

183

Error

Code


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

5

Tape is stuck in the library

autoloader.

Remove the tape from the library autoloader. Consult

the documentation for your hardware for instructions on

troubleshooting tape errors. When the tape is repaired,

run the library job again

2401

7

The <library type> <library>

drive information needs to be

refreshed.

On the Libraries tab in the Management task area,

select the library and click Rescan in the Actions pane.

2401

8

Drive cleaning failed or timed

out.

Change the cleaning tape and then, on the Libraries tab

in the Management task area, select the drive and click

Clean in the Actions pane.

2401

9

Drive <drive name> in <library

type> <library> needs

servicing.

Contact product support for your hardware to get the

drive serviced. You should also review all protection

groups to identify if the absence of this drive requires

changes to drive allocations.

2402

1

DPM attempted to move a tape

to <element type> <element

name> but this <element type>

was occupied. DPM may not

be in synch with the current

state of the library <library>.

1) On the Libraries tab in the Management task area,

select the library <library> and click 'Inventory' in the

Actions pane.

2) If the <element type> contains a tape, remove this

tape by using the front panel of your library.

2402

2

The <element type> <element

name> did not contain a tape

when DPM expected it to. DPM

might not be in synch with the

state of the <library type>

<library>


select the <library type> <library> and click Inventory

library in the Actions pane.

2402

3

The library <library> mandates

that when a tape is

dismounted, it should be

moved back to the slot it was

originally mounted from.

However, the slot <slot name>

is not empty.

1) Remove the tape in the slot <slot name> by using the

front panel of your library.


click Inventory library in order to run inventory

184

Error

Code


2402

4

A library with the same name is

already attached to this server.

Please choose a different

name for the library.

2402

5

The operation cannot be

performed on <library type>

<library> because it does not

have any I/E ports.

2402

6

Operation cannot be performed

because DPM Administrator

Console is not synchronized

with the actual state of the

library.

Close and reopen DPM Administrator Console to

synchronize it with the actual state of the library.

2402

7

Operation failed since the slot

<slot name> in library <library>

was empty. This tape is

currently present in <media


information>

Use the front panel of your library to move the tape from

its current location to the slot specified above.

2405

4

Operation cannot be performed

on the tape in <media location

type> <media location

information> because it is a

cleaning tape.

2402

9

Tape erase operation was

skipped because <library type>

<library> does not support tape

erase.

2403

1

DPM was unable to recatalog

the tape in <media location


information> in <library type>

<library> because this tape has

not been identified.

On the Libraries tab in the Management task area, click

Inventory library. Then, select the tape <media label>

and click Identify unknown tape.

2403

4

DPM could not reserve the I/E

port resource because one of

required resources is not

Ensure that there are no pending alerts for the library.

Also check whether I/E port slots have been left open; if

yes, close the I/E port slots.

185

Error

Code


accessible.

2403

6

The operation failed because

the I/E port is currently in use.

Retry this operation after the I/E port is free.

2403

7

DPM failed to erase the

selected tape because the

state of the <library type>

<library> as seen by DPM is

inconsistent with the actual

state of the library.

Run a detailed inventory and a fast inventory.

2403

8

The barcode on the tape

<media label> in <media


information> appears to have

changed since the last time it

was inventoried in DPM.

1. If the barcode of this tape has been changed, then

click the link below to fix this issue. Refresh barcode on

tape <- this is a link to delete older barcode and set the

current as the actual barcode. 2. If this tape is a copy of

a DPM tape created by external tool, erase this tape

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

9

Duplicate barcodes detected

on tapes with labels <media

label> and <media label>

1. Remove the tapes from the library. 2. Clear duplicate

barcode information from DPM. <- this is a link. 3.

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

0

DPM failed to recatalog the

imported tape <media label>

because it has not been

inventoried

On the Library tab in the Management task area, click

Inventory library. Select the option to perform a detailed

inventory.

2404

1


imported tape <media label>

because the tape is blank.

DPM can only recatalog a tape that has valid data on it.

2404

2


imported tapes because they

do not contain the catalog

information.

It is likely that your data spans multiple tapes and the

catalog information is present on another tape. Insert all

tapes associated with the backup and retry the

operation.

186

Error

Code


2405

0

Failed to perform the operation

since the tape <media label> is

not available in <library type>

<library>

Add tape to the library, or to the drive in the case of a

stand-alone tape drive. Retry the operation after adding

tape.

2405

1

Required tape resource

<media label> is reserved by

another task.

Wait for the other task to complete, or cancel the

ongoing operation. Retry the operation.

2405

2

DPM could not reserve the

drive resource because one of

required drive resources is not

online or it needs cleaning or

servicing.

1) View and resolve all alerts for the library and its

drive(s). Retry the operation after resolving the alerts.

2) Go to the Library tab in the Management pane and

click Rescan. Once the rescan operation has completed

successfully, retry the operation.

2405

3

Required drive resource is

reserved by another task.

View and resolve all alerts for the library and drive, or

wait for other operations to complete. Retry the

operation after resolving the alerts.

2405

5

Operation failed because no

usable drives were available in

<library type> <library>. Either

no drive is online or all the

drives) need cleaning or

servicing.

1) On the Alerts tab in the Monitoring task area, resolve

all alerts for this library and its drive. Retry this

operation after resolving the alerts.

2) If you have some drives which are functioning

correctly but are currently being used, wait for the other

operations to complete and then retry this operation.

2406

1

Unexpected tape detected in

<media location type> <media

location information> in <library

type> <library>

Check to see if there are any active alerts indicating

suspect tapes. If such an alert exists, take the

appropriate recommended action and then retry this job.

2405

6

<library type> <library> has

been disabled by the DPM

administrator

1) If this library is associated with an active protection

group, modify the protection group to associate it with

another library to prevent tape-related jobs from failing.

2) If you want to use this library for your tape-related

jobs, on the Libraries tab in the Management task area,

select this library, and then click Enable library in the

Actions pane.

2406

0

Some certificates under

DPMBackupStore have

changed since the start of the

job.

Retry the job.

187

Error

Code


2407

2

DPMBackupStore or

DPMRestoreStore is not

present.

Recreate DPMBackupStore and DPMRestoreStore

Certificate stores using the Certificate Management

console.

2407

3

No certificate is present under

DPMBackupStore.

Add certificates to the DPM backup certificates

collection.

See "How to Encrypt Data in a Protection Group " in

DPM Help for more information about certificates.

2407

4

Failed to encrypt data on tape Retry the job

2407

5

Certificates on tape are

corrupt. Data on this tape

cannot be recovered.

2405

7

DPM failed to create a copy of

the tape backup for <data



because the tape backup failed

or did not run.

1) Retry the failed tape backup job using the alert in the

Monitoring task area.

2) If your copy failed because the tape backup job did

not run at all, in the Protection task area, click Create

recovery point - tape to create a short-term tape

backup.

3) After successfully running the tape backup, retry the

failed copy job using the alert in the Monitoring task

area.

2405

8

The certificate <certificate

name> with serial number

<certificate serial number>

issued by <certificate issuer>

will expire by <expiration

date>. All encrypted backup

jobs will fail after this time

1) If this certificate contains a private key, move this

certificate to the DPM recovery certificates collection for

recovering data in the future, and replace this certificate

with a valid certificate in the DPM backup certificates

collection to continue further backups.

2) If this certificate does not contain a private key,

replace this certificate with a valid certificate in the DPM

backup certificates collection to continue further

backups.



2405

9

The certificate <certificate

name> with serial number

<certificate serial number>

issued by <certificate issuer>



recovering data in future, and replace this certificate


188

Error

Code


will expire by <expiration

date>. All encrypted backup

jobs will fail after this time





backups.



2407

0

Some of the certificates under

DPMBackupStore have

expired



recovering data in future, and replace this certificate






backups.



2407

1

This DPM server is not

authorized to read or write to

this encrypted tape because

there is no valid certificate in

DPMBackupStore and

DPMRestoreStore which can

decrypt data.

1) Make sure that DPMBackupStore has the certificate

to decrypt this tape.

2)Use this tape on a DPM server which is authorized to

read this tape.



2407

6

The command sent by DPM to

the library agent timed out.


2407

7

DPM failed to mount the tape

<media label> in drive <drive

name> for the library <library>.

This is because DPM is not

synchronized with the current

state of the library.

On the Library tab in the Management task area, select

the library and then click Inventory library. If enabled,

select the option to run Fast inventory; otherwise, run

Detailed inventory.

2408

6

DPM failed to dismount the

tape <media label> in drive

<drive name> for the library

<library>. This is because DPM

On the Library tab in the Management task area, select

the library and then click Inventory library. If enabled,

select the option to run Fast inventory; otherwise, run

Detailed inventory.

189

Error

Code


is not synchronized with the

current state of the library.

2407

8

No certificate with private key

is present in DPMBackupStore

In the Certificate Management console, open certificate

stores for the Computer account on the DPM server.

Add a certificate which has the private key to the

DPMBackupStore certificates collection.



2407

9

DPM encountered an error

while attempting to parse the

tape catalog information for

tape <media label>.


2408

2

DPM failed to perform the

operation since the specified

recovery point does not exist

2500

1

Rescan cannot be performed

at this moment because DPM

is performing other operations

on the <library type> <library>.

Please wait for the current library operations to

complete and then retry this operation

2501

1

DPM failed to inventory the

<library type> <library>. This is

possibly due to a hardware

issue.

Refer to your hardware manual for troubleshooting

steps.

2408

0

DPM encountered a critical

error while trying to parse the

contents of the tape <media

label>. This may be because

the data on this tape is corrupt.

1) Check if you have another copy of this tape. If a copy

is available, use that to retry the recovery.

2) If you do not have another copy of this tape, then

open the Recovery task area and select all required

individual recoverable items and perform the recovery.

2408

4

The tape in <library type>

<library> at <media location


information> has been written

to by some other tape backup

application by using an

unsupported physical block

size . DPM only supports a

physical block size between

Go to the Libraries tab in the Management pane, select

the tape, and click Erase tape to erase the content of

this tape. After erasing this tape, DPM will be able to

use it for backups.

190

Error

Code


1024 bytes and 65536 bytes

and hence will not be able to

read or overwrite the contents

of this tape.

2408

3

Recovery failed for <data



Hardware snapshots of the

DPM replica and recovery

point volumes are not mounted

on the protected computer for

SAN recovery

Use your SAN software to take hardware snapshots of

the DPM replica and recovery point volumes and mount

them on the protected computer

2500

2

The tape in <library type>

<library> at <media location


information> appears to be a

cleaning tape. However, this

tape is not marked as a

cleaning tape.


select this tape and click Mark as cleaning tape

2500

5

The cleaning operation for

drive <drive name> on library

<library> took longer than

expected. The cleaning

operation may have failed.

1) If supported, check the front panel of your library to

verify that this cleaning operation completed

successfully.

2) If the cleaning operation failed, try changing the

cleaning tape and run the cleaning job again.

2500

9

DPM is not synchronized with

the current state of your library.

Jobs running on the <library

type> <library> can potentially

fail.


Inventory library. If available, select the option to

perform a fast inventory, otherwise, perform a detailed

inventory.

2501

0

DPM tried to access <element

type> <element name> on

library <library>. This <element

type> does not exist.


click Inventory library in order to run inventory. If

enabled, select the option to run Fast inventory,

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

191

Error

Code


2 the current state of your library.

Jobs running on the <library

type> <library> can potentially

fail.

Inventory library. If available, select the option to

perform a fast inventory, otherwise, perform a detailed

inventory.

2501

3

DPM detected that the drive

<drive name> does not appear

to be installed correctly.

Check the SCSI and bus mappings of the drive to

ensure that the drive is mapped correctly. If you change

any of the mappings, open the Libraries tab in the

Management task area and click Rescan.

2501

4

<library type> <library> is not

ready.

1) Check if the library is turned on.

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

5

Drive <drive name> was

detected as not ready.

1) Check that the drive is powered on.

2) Check if the drive is being serviced. If yes, you can

ignore this alert.

3) Check if the drive is connected properly.



2501

6

DPM failed to use the tape in


location information> because

it appears to be a cleaning

tape that is identified

incorrectly as a backup tape.

Check if the tape in slot <media location type> <media

location information> is a cleaning tape. If yes, on the

Libraries tab in the Management task area, select this

tape and click Mark as cleaning tape in the Actions

pane.

2501

7

DPM could not access a drive

<drive name> since some

other application is currently

using it.

Determine if some other application is using the drive

and stop it.

2510

0


while attempting to control the

autoloader on library <library>

1) Turn off the library <library>, and then turn it on and


2) Examine the front panel of your library to see if any

errors are being reported by your library.

192

Error

Code




2510

1


while attempting to use tape

<media label> on the drive

<drive name>. This could be a

problem with your drive or

tape.

1) Use the tape <media label> in a different drive. To do

this, first disable the drive <drive name>. Select this

tape and click ‘Identify unknown tape’. If this operation

fails, it indicates a potential problem with your tape.

2) Use the tape <media label> in a different library.

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

2

DPM attempted to move a tape

to <element type> <element

name> but this <element type>

was occupied. DPM may not

be in synch with the current

state of the library <library>


select the library <library> and click 'Inventory' in the

Actions pane.

2) If the <element type> contains a tape, remove the

tape by using the front panel of your library.

2510

5

Tape drives or library devices

may have been disconnected

or reconnected on the DPM

server.


'Rescan' in the Actions pane.

2510

6


either turned off or has been

disconnected

1) Check if the <library type> <library> is turned on.

2) Check for loose data or power channel connections.

3) Make sure the library is visible in Device Manager.

2510

7

Drive <drive name> requires

cleaning. The drive will not be

used for further operations until

it has been cleaned.

Drive <drive name> will be automatically cleaned by

DPM. If you are seeing this error frequently, please

service the drive.

2510

8

The library <library> requires

all drives to be empty in order

to lock or unlock the door.

However, the drive <drive

Use the front panel of the library <library> to move the

tape from the drive <drive name> to an empty slot

193

Error

Code


name> has a tape in it.

2510

9

Tape might not be properly

inserted in the stand-alone

drive or the stand-alone drive

is not ready.

1) Check to see if the tape has been inserted correctly

into the drive.

2) Check to see that the drive is ready and operational.

2512

3

The operation failed because

the insert/eject (I/E) port of the

library <library> is open.

Use the front panel of the library to close the I/E port.

2512

4

Rescan failed because the

tape drive or library hardware

does not seem to have been

set up correctly.

In Device Manager, check to see that the drivers for the

tape drive or library hardware are installed correctly.

2512

5

DPM was unable to use

<formatted device name value

pairs> since this was being

used by some other process.

1) Determine if any other process on the DPM server is

currently using the library. If this is the case, stop the

process.

2) Check to see that your library is powered up and

functional

2512

6

Failed to obtain drive mapping

information from the file

DPMLA.xml. The information in

this file is not formatted

correctly.

Refer to the DPM 2010 Operations Guide for

instructions on modifying the DPMLA.xml to correctly

represent your current library configuration.

3000

2

After a tape mount operation,

no tape is found in the drive or

the tape in drive has changed.

Update the library state by performing an inventory, and

then retry the operation. On the Libraries tab in the

Management task area, click Inventory library.

3000

8


contents of the tape <media

label> because it encountered

a critical error while attempting

to read catalog information

from this tape. This may be

because the tape data is

corrupt.

If you have another copy of this tape, use that instead

for the re-catalog operation. If this is the only copy of

the tape and you want to recover as much data as is

possible, on the Libraries tab in the Management task

area, select this tape, click View contents, and copy the

contents of this tape to disk.

3001

5

The specified recovery point

does not exist

Increase the disk allocation space for the recovery point

volume, or delete old recovery points by using the

Remove-RecoveryPoint cmdlet. For information about

194

Error

Code


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 from the

“Modify disk allocation” dialog box. Then, open Disk

Management, right-click the custom volume, and then

select “Extend Volume".

3001

2

Errors occurred while taking a

VSS snapshot of volume(s).

Retry the operation. If it fails consistently, remove the

protected data from the protection group and reprotect it

again.

3002

4

A critical inconsistency was

detected, therefore changes

cannot be replicated.

Click Modify Protection Group to validate exclusion or

inclusion filters for the data source. After the protection

group is modified, click the link below to run a

synchronization job with consistency check.

3002

5

One or more databases in the

storage group failed to mount

On the Exchange Server, verify the cause of failure from

event logs entries.

3002

6

One or more databases in

storage group failed to

dismount

On the Exchange Server, verify the cause of failure from

event logs entries.

3015

6


protection for <data source


because the change tracking

information is corrupt

3022

2



name> on server <server

name> since the change

tracking information is corrupt

3002

9

Eseutil.exe failed to apply logs

on database files to bring the

database to a clean shutdown

state.

Retry the operation. If the problem persists, the

recovery point may be corrupt. Retry recovery from


195

Error

Code


3003

0

SIS is not enabled on the

server.

Enable SIS for the server.

3003

3

The volume is no longer

available - it may be

dismounted or offline

Make sure the volumes are online and mounted.

3003

7

DPM was unable to determine

the last known backup tracking

information for this data

source.

Re-run the job.

3003

8

The change journal is corrupt

due to bad sectors on the disk.

Delete the change journal by running "fsutil usn

deletejournal" [see command usage for more

information] at a command prompt. Click the

recommended action link below to perform a

consistency check.

3004

5

At least one of the databases

is not online

Ensure that all databases in the storage group are

online, and then retry the job.

3004

6

Protection agent is unable to

synchronize the replica.

Run synchronization with consistent check.

3005

1

Overwrite database' flag is not

set for one or more databases

being recovered

On the Exchange server, set the 'Overwrite database'

flag and retry the operation.

3007

5

The volume for one of the

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

6

Operation failed for <data


name> because the recovery

point volume for this data

source is not available on the

DPM server. Future backups

will also fail until this issue is

fixed.

1) If your recovery point volume is offline, bring it online

and then run consistency check for the affected data

sources.

2) If your recovery point volume is not available to bring

online, remove the affected members from protection

and re-protect them. When stopping protection for the

affected members, select the option to delete the replica

on disk.

196

Error

Code


3007

7

DPM has run out of free space

on the recovery point volume

for <data source name> on

<server name>. Protection for

this data source will fail in

order to prevent existing

recovery points from being

deleted before their expiration.


volume for <data source name>. We recommended that

you increase the space by at least 25 percent more

than the current allocation.

2) Run consistency check after increasing the space for

the recovery point volume.

3007

8



name> due to a VSS error on

the DPM server. Future

backups are also likely to fail

until this issue is fixed.

1) Rerun the consistency check and see if it resolves

this issue.

2) Check to see if your disks are connected properly to

the DPM server. If there are any disk cabling issues,

rectify them and then run consistency check.

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

0

DPM has detected that some

other application has created

recovery points on the

recovery point volume for

<data source name> for server

<server name>. Future

backups will fail until these

recovery point are deleted.

Open the DPM Management Shell and run .\Delete-

Shadowcopy.ps1 "<volume name>" to delete the

externally created recovery points on the recovery point

volume.

3008

3




the DPM server.

1) Rerun the consistency check and see if it resolves

this issue.

2) If running consistency check does not resolve this

issue, increase the page file size on the DPM server

and then run the consistency check job.

3008

4




the DPM server.

Rerun the consistency check.

3008

5

Operation failed for <agent

protected server> as the

system ran out of memory.

Check the Event Viewer entries to figure out the cause.

Retry the operation after fixing the problem.

3008 DPM has detected a checksum Retry the operation. If the problem persists, contact

197

Error

Code


7 mismatch during data transfer

over the network

your network administrator to diagnose possible

network issues.

3010

1

DPM encountered a critical

error while performing an I/O

operation on the tape in


location information>.

Retry the operation. If the problem occurs again,

contact your hardware vendor to get your hardware

serviced.

3010

2

There was an unrecoverable

error during I/O operations on

the drive.

Retry the operation with another tape, or try restoring

partial data from backup.

3010

3

After a tape mount operation,

no tape is found in the drive or

the tape in drive has changed.

Update the library state by performing an inventory, and

then retry the operation. On the Libraries tab in the

Management task area, click Inventory library.

3010

4

DPM failed to write to tape

because the tape is write-

protected. The tape may be in

(drive-name/slot id)

Remove the write protection from the tape and retry the

operation.

3010

5

The tape and the drive type

may not be compatible.

Check that the tape and the drive type are compatible,

and the drive is supported. Also check if the drive

firmware needs an upgrade.

3010

7

RA cannot read from/write to

temp area.

DPM will recreate the temp area with appropriate

permissions

3011

0

DPM has encountered a critical

internal error. (Critical error in

reading/parsing

DirsAndFileOffsetFileList)


3010

6

No more space left in Temp

storage volume.

1) Create a folder called 'temp' under the DPM

installation path on the DPM server (by default this path

would be "(Program Files)\Microsoft Data Protection

Manager\DPM".

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

8

Either the tape <media label>

has corrupt data or this is not

the right tape.

Use another copy of the tape and retry the operation.

You can view the contents of the tape to confirm that it

contains the expected data.

198

Error

Code


3010

9


contents of the tape because it

encountered a critical error

while attempting to read

catalog information from this

tape. This may be because the

tape data is corrupt.

If you have another copy of this tape, use that instead

for the recatalog operation. If this is the only copy of the

tape and you want to recover as much data as possible,

then select this tape on the Libraries tab in the

Management task area, click View contents, and copy

the contents of this tape to disk.

30111 The VSS application writer or

the VSS provider is in a bad

state. Either it was already in a

bad state or it entered a bad

state during the current

operation.

Please check that the Event Service and the VSS

service are running, and check for errors associated

with these services in the Application Event Log on the

server <server name>. Please allow 10 minutes for VSS

to repair itself and then retry the operation.

3011

2

DPM encountered a retryable

VSS error.

Check the Application Event Log on <server name> for

the cause of the failure. Fix the cause and retry the

operation.

3030

0

Synchronization for replica of


<server name> failed because

the replica is not in a valid

state or is in an inactive state.

Review the application event log on the protected

computer for errors from the DPM writer service. Take

appropriate action and retry the operation.

3011

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

4

No VSS provider supports one

or more volumes for data

source <data source name> on

<server name>, therefore DPM

cannot create recovery points

for these volumes.

Please stop protection for this volume and any data

sources that are hosted on this volume.

3011

5

DPM failed to synchronize

changes for <data source

Retry the operation at a later point when the churn is

expected to be lower.

199

Error

Code




snapshot volume did not have

sufficient storage space to hold

the churn on the protected

computer

3011

9

The change journal ID may

have changed since the last

synchronization. DPM is

unable to track changes on this

computer.

3012

0

DPM failed to recover all the

files.

Recover to an alternate location or try recovering from


3011

6

VSS has deleted a shadow

copy since it has probably run

out of disk space on the server

<server name>.

Increase the space allocated for the VSS diff area of

volumes involved in protection on this server.

3011

7

A journal wrap error has

occurred on the change

journal, and therefore DPM is

unable to track any more

changes or may have missed

some changes for the data

source <data source name> on

<server name>.

1) Click the link below to run synchronization with

consistency check.

2) If the problem persists, you can increase the change

journal size or configure the current protection group to

synchronize more often. To change the synchronization

schedule, select the protection group in the Protection

task area, and in the Actions pane, click Modify

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

9

DPM cannot continue



cluster <virtual server name>

because this cluster

experienced an unexpected

failover.

3011

8

Change journal not initialized

or is the wrong size

1) Click the "Modify protection group for this data

source..." link below to configure change journal size.

On the Disk Allocation page, select the Protected

200

Error

Code


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

1

File copy failed. The directory

for source location <source

location> or destination

location <destination location>

does not exist.

(<message>)

Exception trace:

<exception message>

Please make sure that the source and target locations

are correct and have appropriate permissions.

3012

2

File copy failed. The source

location <source location>

does not exist.

(<message>)

Exception trace :

<exception message>

Please make sure that the source and target locations

are correct and have appropriate permissions.

3012

3

File copy failed due to an I/O

error.

Source location: <source

location>

Destination location:

<destination location>.

(<message>)

Exception trace :<exception

message>

Please make sure that the source and destination

locations exist and have full control permissions for the

local system account.

3012

4

Catalog for backup job was not

built correctly for <data source


<server name>.


3012

5

Another backup job of <data


name> is in progress.

Please wait for the earlier backup job to finish, and then

retry the backup. Or, you can cancel the current job,

and then retry the backup job.

201

Error

Code


3012

6

Backup of <data source name>

on <server name> cannot be

completed. DPM could not find

a valid recovery point on disk.

On the Jobs tab in the Monitoring task area, check for

failures of synchronization jobs and resolve those. Next,

create a valid recovery point and then run the backup to

tape job again. To create a valid recovery 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

7

Operation failed due to an

internal error


3012

8

Invalid backup type specified


<server name>.

If you are backing up to tape, perform a full backup. If

you are backing up to disk, perform an express full

backup.

3012

9

DPM failed to generate the file

list to complete the task.


select the tape and then click View Contents in the

Actions pane.

3013

0

DPM failed to start tracking



<server name> because of

insufficient memory resources

Verify that you do not have more than 100 protectable

data sources on a single volume. If this is the case,

check to see if you can split your data source across

more volumes.

3015

0

DPM is attempting to back up

or restore a SIS link file, which

requires SIS to be enabled on

<server name>.

Enable SIS on the computer by using Add/Remove

Windows Components in Add or Remove Programs.

3015

2

DPM cannot continue

protecting <data source name>

on <server name> because the

volume on which this data

resides on has been resized.

3015

4

DPM encountered an unknown

error while tracking changes


<server name>.

202

Error

Code


3015

5




because this computer has

been powered off without

shutting it down cleanly.

3013

9

The replica is inconsistent for



name> due to a CCR failover.

A synchronization job with

consistency check will be

automatically triggered after 30

minutes.

No action required.

3014

3

Database mount failed for



name>.

Please contact the exchange admin. Verify the cause of

failure from event logs entries on the exchange server.

3014

4

Database dismount failed for



name>.

On the Exchange server, verify the cause of failure from

event logs entries.

3013

1

DPM is not synchronized with

the changes on <data source


<server name>. Protection

cannot continue.

Check to see if you are protecting a clustered resource

which has undergone a dirty failover. In this case, DPM

requires a synchronization with consistency check

before it can continue protection.

3013

2

DPM skipped the

synchronization job for <data



because it detected an

unexpected backup state.

Wait for the next scheduled backup job to trigger for

protection to continue. Alternately you can manually

trigger a backup job in the Protection task area by

selecting this data source and then clicking Create

recovery point - Disk.

3013

3

A critical inconsistency was

detected for <data source


<server name> and therefore

In the Protection task area, click Modify Protection

Group to validate exclusion and inclusion filters for the

data source. If modifying the protection group does not

start a consistency check, run a synchronization with

203

Error

Code


changes cannot be replicated

for <file name>.

consistency check.

3013

4

DPM failed to clean up data of

old incremental backups on the

replica for <data source type>


<server name>.

Synchronization will fail until

the replica cleanup succeeds.

This may happen if the replica volume is being

accessed from outside of DPM. Please see the detailed

error, resolve the issue with respect to the replica

volume path, and retry the job. Otherwise, DPM will

synchronize with the changes during the next scheduled

synchronization job.

3013

5

The replica of <data source




data source.

DPM has detected changes in

file locations or volume

configurations of protected

objects since the data source

was configured for protection.


Group to update the configuration information for the

data source on the DPM server and to increase the

replica volume size if necessary. If modifying the

protection group does not start a consistency check, run

a synchronization with consistency check.

3013

6





data source.

DPM detected that some

protected objects are missing

since it was configured for

protection.







3013

7





data source.

DPM detected new protectable

objects for the data source


protection.







204

Error

Code


3013

8





data source.

DPM detected changes in

existing protected objects and

detected new protectable

objects for the data source


protection.







3030

1





data source.

1) Check to see if some SQL databases have been

added to the protected SharePoint farm. If this is the

case, go to the protection pane and select the option to

Modify Protected Group. Go through the wizard without

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

2





data source.

Check to see if some SQL databases have been

removed from the protected SharePoint farm. If this is

the case, go to the protection pane and stop protecting

this farm with the option to retain current data backups.

Then, recreate protection for this SharePoint farm.

3030

3

DPM failed to backup <data


name> on <server name> to

tape.

1) Check to see if some SQL databases have been

added to/or removed from the protected SharePoint

farm. If this is the case, go to the protection pane and

stop protecting this farm with the option to retain current

data backups. Then, recreate protection for this

SharePoint farm.

205

Error

Code


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

0

DPM tried to do a SQL log

backup, either as part of a

backup job or a recovery to

latest point in time job. The

SQL log backup job has

detected a discontinuity in the

SQL log chain for <data source

type> database <data source

name> since the last backup.

All incremental backup jobs will

fail until an express full backup

runs.

If you see this failure as part of a backup job, then in the

Protection task area, select the SQL Server database

and click Create recovery point. Choose express full

backup. Alternately, you can wait for the next scheduled

express full backup to run.

If this failure occurs as part of a recovery job, then try to

recover from another point in time.

Review the Application Event Viewer logs on the

computer running SQL Server for more details.

3018

6

The protection agent on

<server name> is disabled.

Enable the protection agent on the protected computer

in DPM Administrator Console, in the Management task

area, on the Agents tab.

3102

4

Cannot run an incremental

synchronization and create a

recovery point for <data source

name> because the application

does not support it.

3014

1

To recover <data source type>


<server name>, DPM must

stop and start the SQL Server

service on <server name>.

After stopping the service,

DPM was unable to

successfully start the service.

Please check that the SQL Server service on the

protected computer can be sent the start command

successfully. After you ensure that the service can be

successfully started, retry the recovery. If this error

occurs again, try to recover the master database from


3014

2

To recover <data source type>


<server name>, DPM must

stop and start the SQL Server

Please check that the SQL Server service on the

protected computer can be sent the stop command

successfully. After you ensure that the service can be

successfully stopped, retry the recovery.

206

Error

Code


service on <server name>.

DPM was unable to

successfully stop the service.

3014

6

Data consistency verification

check failed for <object name>

of <data source type> <data


name>.

Either the database files are corrupt or the proper

versions of the following files are missing.

If you have recently upgraded your Exchange server,

please copy them from that server to DPM server.

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

7

Eseutil.exe failed to apply logs

on database files for <data


name> on <server name> to

bring the database to a clean

shutdown state.

Please contact the Exchange administrator. Event logs

on the above server may help resolve the issue. If the

problem persists, the recovery point may be corrupt.

Retry recovery from another recovery point.

3014

8

DPM was unable to access the

cluster resource group <virtual

server name> for <data source

name> of protection group

<protection group>

Verify that the cluster resource group <virtual server

name> is accessible by using the Cluster Administration

console.

3015

1

DPM failed to read its change

tracking information for <data


name>.

3015

3

The file system on <server

name> on which data source

<data source name> of

protection group <protection

group> resides, is in an invalid

state and it is no longer

available.

Make sure the volumes are online and that the file

system is in a consistent state.

3015

7

The alias of the user to which

DPM has to connect the

recovered mail box is online

Please specify an alias which is offline and not

connected to any Exchange server.

207

Error

Code


and connected to an Exchange

server.

3015

8

Verification failed for the tape

backup of <data source type>



tape backup failed.

Retry the tape backup and then retry verification.

3015

9

DPM cannot continue



cluster <virtual server name>

because this cluster

experienced a failover.

3016

0

DPM failed to perform the tape

backup for <data source type>

<data source name> on cluster

<virtual server name> because

this cluster experienced a

failover.

Retry the tape backup job.

3016

1

DPM is unable to determine

tracking information for <data



Retry the operation. If the replica has been marked

inconsistent, run a consistency check on this data

source.

3016

2

Protection cannot continue

because the change journal

used for tracking changes for



name> is corrupt due to bad

sectors on the disk.

Delete the change journal on the protected computer by

using the FsUtil.exe tool and recreate the change

journal. Next, run a consistency check on the data

source.

3016

3

The path to the SQL temporary

folder for <data source type>


<server name> is too long.

This can cause backup or

recovery jobs to fail.

DPM creates the temporary folder in the same location

as the SQL database log file. The temporary folder

name is 'DPM_SQL_PROTECT'.

To fix this issue:

1) Change the location of the database log file so that

its physical path is as short as possible.

2) Run a consistency check job for this database.

208

Error

Code


3103

0

No library has been specified

for protection.

3103

1

Protection for <protection

group> has been set only to

tape.

3016

7

The backup job failed because

DPM detected that some

databases of the Exchange

Server Storage Group instance


<server name> are offline.

Bring all databases in the storage group online and

retry.

3016

4

The <data source type> <data


name> is not available

1) Check that the database is online.

2) Check that the database is not in a restoring state.

3) Verify that the database has not been deleted.

4) Make sure that the database is accessible.

3016

5

The backup job failed because

DPM detected that the <data

source name> instance of SQL

Server 2000 on <server name>

has been upgraded to SQL

2005.

Please stop protection for all databases that belong to

this instance (with the ‘Retain protected data' option),

and reconfigure protection for the databases in a new

protection group. This will allow you to continue

protection for the databases while still retaining old

backups for recovery.

3016

6

DPM detected that the

recovery point volume for


source name> is not available

on the DPM server. Protection

jobs will fail until the recovery

point volume is brought online.

Ensure that all the disks added to the DPM storage pool

are online.

3016

8

Full backup is required for



name> as <service name>

service has been restarted.

In the Protection task area, click 'Create recovery point-

disk' and select 'Create a recovery point by using

express full backup'.

3016

9

The operation failed for <data



1) Check that the data source is online.

2) Check that the data source is not in a restoring state.

3) Verify that the application writer is running.

209

Error

Code


because the data source is not

available.

4) Make sure that the data source is accessible.

5. Verify that the data source is not missing.

3017

0

The recovery to the latest point

in time failed. During a

recovery to the latest point in

time, DPM tries to do a tail log

restore to apply the latest

changes on the SQL database


<server name> at the end of

the recovery. This tail log

restore failed.

Check the Application Event Viewer logs on the SQL

Server to find out why the tail log restore may have

failed.

You can do the following to fix the issue:

1) Recovery to the latest point in time is not possible

immediately after another recovery has been performed

on the same database. Allow a synchronization job to

run before you attempt a recovery to the latest point in

time.

2) Choose an alternate point in time to recover to, if you

run into this problem repeatedly.

3017

1

The recovery to the latest point

in time has failed. During a

recovery to the latest point in

time, DPM tries to do a SQL

transaction log backup to get

the latest changes from the

SQL database <data source


before starting the recovery.

This transaction log backup

has failed.


Server to find out why the SQL transaction log backup

may have failed.

You can do the following to fix the issue:

1) If the SQL log chain is broken, you will have to run a

full backup to re-initialize the log chain.

2) If the DPM replica for database is invalid, you will

have to run a consistency check operation for this

database.

Choose an alternate point in time to recover to, if

transaction log backups cannot be successfully run

against database.

3017

2

The DPM job failed for <data



because the SQL Server

instance refused a connection

to the protection agent.

This can happen if the SQL Server process is

overloaded, or running short of memory. Please ensure

that you are able to successfully run transactions

against the SQL database in question and then retry the

failed job.

3017

3

Execution of SQL command

failed for <data source type>


<server name>.


Server for entries posted by the SQL Server service to

find out why the SQL command may have failed. For

more details, look at the SQL Server error logs.

3017 Recovery failed for <data On the Exchange Administrator Console, set the

210

Error

Code


4 source type> <data source


because the overwrite flag is

not set for <database name>.

'Overwrite database' flags for the databases being

recovered and retry the operation.

3017

5

DPM failed to replicate



<server name> due to the high

amount of file system activity

on this volume.

Check to see that no application running on this

computer is malfunctioning to cause this high file

system activity. If you consistently run into this error, in

the Protection task area, click Modify disk allocation. On

the Protected Computers tab, click Modify to increase

the change journal size on the protected computer.

3102

5

Recovery point cannot be

created on tape for data source

<data source name> because

the protection for <protection

group> has been set to disk.

3102

6

Protection for <protection

group> has been set only to

disk.

3102

7

<library type> <library> has

<total number> drives. You

cannot specify a value more

than that.

3017

6

File delete failed due to I/O

error. File may be in use by

some other application. File

location: <location>

Ensure that the file location is correct and that the file

has appropriate permissions.

3018

3

File delete failed because of

unauthorized access error. File

path: <location>

Ensure that the file location is correct and that the file

has appropriate permissions.

3018

4

DPM cannot continue



<server name>.

1) In the Monitoring task area, resolve the "Unable to

configure protection" alert for this data source.

2) Click the link below to retry the job.

3018

5

Recovery for <data source

type> <data source name> to

the latest recovery point cannot

be performed because you

In the Recovery task area, select the recovery point just

prior to the latest recovery point.

211

Error

Code


have already recovered it to a

previous recovery point.

3018

7

Protection agent on <protected

server name> was

unexpectedly shut down during

synchronization. DPM may

have replicated data partially


source name>.

3018

8

Recovery point for <data


name> was created when the

replica was inconsistent. Some

data from this recovery point

may contain partially

synchronized data.

3018

9

The execution of the pre-

backup script for <data source

type> <data source name>

returned an error.

Make sure that the pre-backup script does not have any

errors and can execute successfully.

3019

0

The execution of the post-



returned an error.

Make sure that the post-backup script does not have

any errors and can execute successfully.

3019

1




timed out.

Make sure that the pre-backup script finishes execution

within the time specified, or increase the timeout period.

3019

2




timed out.

Make sure that the post-backup script finishes

execution within the time specified, or increase the

timeout period.

3019

3

The configuration of the pre-

backup script or the post-

backup script XML for <data


name> is incorrect.

Make sure that the pre-backup script or post-backup

script configuration XML file does not have any errors

and that the XML is well formed.

212

Error

Code


3019

4

DPM cannot protect <data


name> because case-sensitive

support is not enabled on the

DPM server.

Enable case-sensitive support on the DPM server by

following the steps described in

http://support.microsoft.com/default.aspx?scid=kb;EN-

US;938455.

3019

5

DPM has run out of free space

on the recovery point volume

and will fail synchronization for


<server name> in order to

prevent existing recovery

points from being deleted.


volume for <data source name>.

2) Retry the operation after increasing the space for the


3022

1

DPM failed to replicate the

changes for the <data source

type> <data source name>.

The operation failed while DPM

was attempting to apply the

changes to the replica.

3101

3

The parameter set that you

have specified is incorrect.

Specify only long-term tape

policy objective.

3101

4



Specify only short- and long-

term tape policy objectives.

3101

5



Specify only short-term disk

and long-term tape policy

objectives.

3101

6

Incremental synchronization

job cannot run on all the

protected items in this

protection group. Change the

synchronization frequency to

"Just before a recovery point".

213

Error

Code


3101

7

Long-term retention range can

be specified only in weeks,

months, or years.

3019

7



name> on <server name> as

the specified storage group is

not a recovery storage group.

Retry the operation and specify a recovery storage

group.

3020

9

DPM has detected that the

cluster configuration has

changed for resource group

<virtual server name> and has

marked the replica

inconsistent.

3019

6




the specified storage group is a

recovery storage group.

Retry the operation and specify a storage group which

is not a recovery storage group, or select the Recover

to Recovery Storage Group option.

3019

8




the alternate storage group or

the database specified is

invalid.

Verify that the storage group or the database exists on

the Exchange server.

3019

9




because the target database

specified is in mounted state.

Verify that the target database is in a dismounted state.

3020

0

Prepare for backup operation



name> has been stopped

because this operation

depended on another backup

operation which failed or was

canceled.

Please retry the operation.

214

Error

Code


3020

1

Prepare for recovery operation



name> has been stopped

because this operation

depended on another recovery

operation which failed or was

canceled.

Please retry the operation.

3020

2

The SQL temporary folder for



name> is not yet configured.

DPM creates the temporary folder in the same location

as the SQL database log file. The temporary folder

name is 'DPM_SQL_PROTECT'.

DPM has not yet configured the temporary folder on

<server name>. In the Protection task area, create a

recovery point for this database.

3020

3

Replica for <data source type>


<server name> is already

consistent. Scheduled

consistency check will not be

run on consistent replica.

3020

4

Replica writer is enabled for



name> for Exchange 2007 with

LCR.

DPM requires the Replica writer to be disabled for

protecting Exchange 2007 with LCR. Please disable the

replica writer by adding a DWORD value,

EnableVssWriter, to the key 'HKLM\Software\Microsoft\

Exchange\Replay\Parameters', setting the value to 0,

and restarting the Microsoft Exchange Replication

Service. Then retry the operation.

3020

5




because a database with the

name you specified already

exists on the SQL instance.

Provide an alternate name for the database to be

recovered. Ensure that no database with the name you

have specified already exists on the SQL server.

3020

7

DPM was unable to compile a

list of recoverable objects for


source name>. You will be

unable to perform detailed

215

Error

Code


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

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

8

Data consistency check timed

out for <object name> of <data



If the error has been reported for your Exchange server,

it indicates that the Exchange server backup files may

be corrupt. Follow these steps to resolve the 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

0


snapshot step returned an

error.

Check to see that the pre-snapshot step does not have


3021

1


snapshot step timed out.

Check to see that the pre-snapshot step can

successfully finish executing within the timeout period.

3021

2


snapshot step returned an

error.

Check to see that the post-snapshot step does not have


3021

3


snapshot step timed out.

Check to see that the post-snapshot step can

successfully finish executing within the timeout period.

3021

4

Failed to create the System

State backup.

Check the event log on the protected computer <server

name> and fix any errors reported.

216

Error

Code


3021

5

Failed to create the System

State backup within the timeout

period.

Check the event log on the protected computer <server

name> to determine why the backup timed out.

3021

6

DPM has detected a

discontinuity in the log chain



name> since the last

synchronization.

1) Consult the administrator of the Exchange server to

rectify the problem. Please ensure that exchange

circular logging is turned off. Synchronization jobs may

continue to fail until this issue is resolved.

2) Last backup might have failed after log truncation.

In the Protection task area, click 'Create recovery point'

and select 'full backup' option.

3021

8

Operation failed because DPM

encountered an unexpected

VSS error.

Check the Application Event Log on <server name> for

the cause of the failure. Fix the cause and retry the

operation.

3021

9

Cmdlet execution failed

(<reason>) for <data source


<server name>.

Please contact the exchange admin and resolve the

issue

3022

0

Activation of COM component

ExchangeCmdletWrapper

failed on <server name>.

Please make sure that the COM component

ExchangeCmdletWrapper is configured appropriately.

3100

0

Operation failed since the

protected data source size had

not been calculated for <data

source name> prior to running

this operation.

Ensure that Get-DatasourceDiskAllocation and Set-

DatasourceDiskAllocation are executed successfully

prior to running this operation.

3101

0

Failed to create the protection

group because no members

were selected for protection.

Retry protection group creation by adding members.

3101

1



Specify only short-term disk

policy objective.

3101

2



Specify only short-term tape

policy objective.

217

Error

Code


3100

1


group since some of the

required schedules have not

been specified.

3100

2


group because a library or

stand-alone tape drive has not

been specified and tape

protection has been selected.

Specify a library or stand-alone tape drive and then try

to create the protection group.

3100

3

Operation failed because


accessible from the DPM

server.

Use the cluster management software to check to see if

the cluster resource group <server name> is online.

3100

4

Failed to enumerate resource

groups on the cluster <server

name>.

1. Verify that the Cluster service is running on the

cluster <server name>

2. Verify that you can ping the cluster from the DPM

server.

3100

5

DPM cannot protect the cluster

resource group on <server

name> because protection

agents are not installed on all

nodes that this resource group

could fail over to.

On the Agents tab in the Management task area, install

protection agents on all nodes that this resource group

could fail over to.

3100

6

DPM cannot start the Create

New Protection Group Wizard

because there are no

computers with protection

agents installed.

On to the Agents tab in the Management task area,

install protection agents on the computers that you want

to protect. After installing the agents successfully, start

the Create New Protection Group Wizard.

3100

8

This item cannot be protected

because some prerequisite

software is missing. Ensure

that all prerequisite software is

installed and then protect this

item.

Click Help to view the list of prerequisite software for the

selected item.

3100

9

Modify Protection Group is

disabled because the following

network names have been

Stop protection of protected members on these clusters

before you modify the protection group.

218

Error

Code


deleted: <input parameter

tag>.

3101

8

The specified retention range

supports the following backup

frequencies only: <input

parameter tag>.

3101

9

The item <protectable object>

does not exist in protection

group <protection group>.

3102

0

The item <protectable object>

cannot be excluded because it

is a data source.

3102

1


created for external data

source <data source name>.

3102

2


created for unprotected data


3102

3


created on disk for data source


the protection for <protection

group> has been set to tape.

3102

8

Data source <data source

name> does not belong to a

protection group.

3102

9


name> has no inactive replica

on <media label>.

3103

2

Journal size cannot be set for


this data source does not use a

change journal.

3103

3

Operation failed because the

recovery point specified for

deletion was created as part of

219

Error

Code


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

4

The operation will remove the

following recovery point(s)

because they have

dependencies on each other:

3103

6

Consistency check schedule

should be modified using the

<input parameter tag> cmdlet.

3103

7

DayofWeek needs to be

specified to continue.

3103

8

Cannot specify consistency

check schedule for protection

groups configured only for

tape-based protection.

3103

9

RelativeInterval needs to be

specified to continue.

3104

0

Duplicate times specified,

please specify unique times.

3104

1

Duplicate weekdays specified,

please specify unique days of

the week.

3104

2

Cannot specify offset

schedules for protection

groups configured only for

tape-based protection.

220

Error

Code


3104

3

Consistency check cannot be

started for unprotected data


3104

4

Consistency check cannot be

started for data source <data

source name> because the

protection for <protection

group> has been set to tape.

3104

5

There are multiple copies of

data. Please choose one of the

following and pass it to this

cmdlet.

3104

6

The selected item cannot be

added to protection. From the

DPM computer, only DPM

database can be selected for

protection.

3104

7

You have chosen short-term

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.

Click Help for more information.

3104

8

Online recatalog can be run for

file volume and share data

sources only.

3104

9

The number of recovery point

locations should be equal to

the number of recoverable

items passed to this cmdlet.

3105

0

The recovery point location

that you have passed is invalid.

Please try again with a different

value.

221

Error

Code


3105

1

Add the search path string and

try again.

3105

2

This step cannot be performed

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.

3105

3

This protection group does not

support the given protection

type. Please try again with a

different value.

3105

4

All data sources passed should

belong to the same protection

group.

3105

5

The data source <data source

name> specified is not a part of

the protection group

<protection group>.

3105

6

The minimum space required

for the <disk item> is

<minimum size>. Please

choose a value more than that

and try again.

3105

7

The disk space requirement for

<disk item> cannot be less

than the current value of <used

size>. Please choose a value

more than that and try again.

3105

8

The data source <data source

name> is not protected and

size calculations cannot be

done on it.

222

Error

Code


3106

0

This recovery source location

is on a disk and not on a tape.

3105

9

Size optimization cannot be

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

1

Specify a scheduled replica

creation time that is less than 1

year.

3106

2

The protection type has been

set to disk-based protection

only, therefore this command is

ignored.

3106

3

This tape is marked as a

cleaning tape. Run the

command on the correct tape.

3106

4

Incorrect start time specified.

Enter the start time in the

following format "hh:mm"

3106

5

Child data source objects

cannot be obtained for external

data source <data source

name>.

3106

6

Protection group <protection

group> does not contain this

type of schedule.

3106

7

This file type has not been

specified for exclusion.

3106

8

This member is not specified

for protection and cannot be

removed from protection.

3106

9

Please specify the library to

use in RecoveryOption for

223

Error

Code


recovery from tape, and try

again.

3107

0

This operation is valid only on

a recovery point on tape.

3107

1

The recovery point location

passed does not belong to

current recovery point.

3107

2

This step cannot be performed

because prerequisite steps

have not been completed. For

more information, type 'Get-

Help <Cmdlet name>' in DPM

Management Shell.

3107

3

Invalid Search Detail Passed

3107

4

The target computer either

does not exist or is currently

not protected by DPM

3107

5

Shares can be retrieved only

from a volume recovery point

3107

6

Recovery cannot proceed as

the replica for the selected

data source is not in "replica

creation pending" state.

Ensure that you have run DpmSync -reallocateReplica

before recovering data to the replica. For details, see

the DPM 2010 Operations Guide.

3107

7

The search string should use

UNC Format if the protected

computer is not specified. If the

search is intended on a folder,

then specify the protected

computer name.

3107

8

System state cannot be

recovered back to the original

location. Please restore to an

alternate location.

3107

9

The recoverable item cannot

be recovered. Please see DPM

224

Error

Code


Help for more details.

3108

0

The specified alternate

instance is the same as

original. Please specify a

different instance or change

the database name

3108

2

The specified alternate

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

3

The alternate database name

is empty. Provide a valid

alternate database name to

use for the recovery

3108

4

The alternate SQL instance

name is either empty or invalid.

Provide a valid alternate SQL

instance name to use for the

recovery

3108

5

DPM cannot detect the volume

<data source name> on server

<server name>.

If the volume is present, this problem can be rectified by

refreshing the state using the Get-Datasource -

ProductionServer <ProductionServer> -Inquire cmdlet,

then retry the current task.

3108

6


name> cannot be selected for

protection because it was

previously protected as part of

data source <referential data

source name> and has inactive

disk or tape replicas.

Remove the inactive protection for <referential data

source name> in the Protection task area by selecting

the data source and then clicking Remove inactive

protection option in the Actions pane.

3108

7

Data source <referential data

source name> cannot be

selected for protection because

Remove the inactive protection for <data source name>

in the Protection task area by selecting the data source

and then clicking Remove inactive protection option in

225

Error

Code


its component database <data

source name> was protected

independently and has inactive

disk or tape replicas.

the Actions pane.

3108

8

The specified short-term

backup frequency does not

support creation of incremental

backups.

Please specify a daily backup frequency or remove the

CreateIncrementals parameter.

3108

9

The specified IP address

already exists in the list of IP

addresses specified in the

backup LAN IP address list.

If you would like to change the sequence number of the

IP address, first remove the IP address and then add it

to the appropriate sequence number.

3109

0

The specified IP address

cannot be removed because it

does not exist in the backup

LAN IP address list.

Only the addresses which are currently a part of the

Backup LAN can be removed. Use Get-

BackupNetworkAddress to view a list of IP addresses

which are a part of the Backup LAN.

3109

1

The specified address is not a

valid subnet address.

Subnet address should be in either of the following

formats, 10.212.12.55/16 (IPV4) or

A821:db8:3c4d:15::/64 (IPV6)

3109

2

The specified sequence

number is not valid. Try again

with a valid number.

Use Get-BackupNetworkAddress command to see the

list of valid sequence numbers

3109

3

The specified subnet mask is

not valid for IPV6.

Valid subnet mask for IPV6 address lies between 1 -

128.

3109

4

The specified subnet mask is

not valid for IPV4.

Valid subnet mask for IPV4 address lies between 1 - 32.

3109

5

The specified recovery options

are not valid.

Check the parameters that you are passing to the

cmdlet and ensure that these parameters correspond to

the data source type that you are attempting to recover.

3109

6

Failed to perform Test-

DPMTapeData on the specified

recovery point since this was

created by some other DPM

installation.

Retry this operation on the DPM server which was used

to create this recovery point.

3109

7

<Server name> is not an

owner for the Exchange cluster

Contact your Exchange administrator or retry with the

226

Error

Code


resource group <virtual server

name>.

fully qualified domain name (e.g. test.contoso.com).

3109

8

The PreferredPhysicalNode is

specified incorrectly.

Please provide all the values and try again.

For example, "PreferredPhysicalNode

(ResourceGroup1.contoso.com, server1.contoso.com),

(ResourceGroup2.contoso.com, server2.contoso.com)".

3109

9

The retention range cannot be

achieved with the current

synchronization frequency.

3110

0

Invalid command line

parameters specified.

Please provide the correct parameters and try again.

3110

2

The rescan operation failed.

For more details, view the Jobs

tab in the Monitoring task area.

3110

3

Rescan operation completed

successfully.

3110

5

The door on the <library type>

<library> could not be unlocked

3110

6

Door successfully unlocked for

<library type> <library>. You

can now open the library door.

The door will be automatically

locked again in <time in

minutes> minutes.

3110

7

The door on the <library type>

<library> could not be locked.

Check the library door and ensure that it is closed

properly. If the door is not closed, close it and then retry

this operation.

3110

8

Door successfully locked for

<library type> <library>.

31110 The selected drive is in use.

To disable the drive, wait for

the job to finish or cancel the

job.

31112 Selected drive is disabled.

227

Error

Code


Any protection jobs configured

to use the library to which the

selected drive belongs will use

the remaining drives on the

library.

31113 Selected drives are enabled.

31114 Cleaning tapes are not

available in <library>, to clean

the selected drives.

Add cleaning tapes and restart

the cleaning job.

3113

9

Door of <library type> <library>

is already unlocked.

3114

0


is being unlocked. Please wait

for the operation to complete.

3114

1


is already locked.

31116 The selected tapes cannot be

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

0

The selected tapes cannot be

erased because they belong to

protection groups.



groups before you can erase

the tapes. The protection group

that a tape belongs to is listed

228

Error

Code


in the Protection Group

column.

3112

3

I/E port door of <library> is 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

4

The selected tapes could not

be marked as free because

another job has reserved them

for use.

3112

5

The selected tape(s) could not

be marked as cleaning tapes

because they are currently in

use.

3112

6

<failure count> tape(s) could

not be marked as cleaning

tapes because they are

currently in use.

3112

7

DPM could not perform the

requested action on the

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.

Close and reopen DPM Administrator Console to

synchronize it.

3112

8

The selected data will be

copied to the specified

location.

You can monitor the progress

of the copy job(s) on the Jobs

tab in the Monitoring task area.

229

Error

Code


3112

9

<failure count> out of <total

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.

3113

0


number> selected tapes could

not be marked as free because

another job has reserved them

for use.

3113

4

The selected tape(s) could not

be unmarked as cleaning tapes

because they are currently in

use.

3113

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

previously belonged.

3113

3


number> tapes cannot not be

erased because they contain

data that is being protected.



groups before you can erase

230

Error

Code


the tapes. The protection group

that a tape belongs to is listed

in the Protection Group

column.

3113

5

<failure count> tape(s) could

not be unmarked as cleaning

tapes because they are

currently in use.

3113

6

The selected tape is currently

being recataloged.

The contents of this tape can

be viewed only after the

recatalog operation

successfully completes.

3113

7



offline.

3113

8



disabled.

3114

2


is being locked. Please wait for

the operation to complete.

3114

3

Connection already exists to

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

4

The server <server name>

could not be found in Active

Directory.

Ping this server to verify that it is accessible and then

retry the operation. If the server is accessible, verify that

the DPM service is running and that the current user

has a domain account and is a member of the local

administrators group. If the problem persists, contact

231

Error

Code


your DPM administrator.

3114

5

Tape in <location> cannot be

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

6

Operation failed because drive

<drive name> is offline.

3114

7

Operation failed because drive

<drive name> is disabled.

3115

0

All selected tapes were

successfully moved to the I/E

port slots of the library

<library>

3115

1

This operation is not allowed

on a suspect tape.

Take out the tape in <location>, replace the barcode,

and run detailed inventory on the tape.

3120

0

DPM was unable to initiate

recovery to the specified

computer.

1) Check to see that the computer name provided is the

fully qualified domain name.

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

3

The selected recovery point is

not valid for recovery to a DPM

server.

3120

4

This option is disabled as the

DPM database DPMDB cannot

be recovered directly to the

original location. For more

232

Error

Code


information, see the DPM 2010

Operations Guide.

3120

5

Latest point in time recovery is

not supported from:

1) Secondary DPM server.

2) Invalid replica.

3) Inactive protection.

3120

6

DPM cannot protect this

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

7

Cannot perform <input

parameter tag> on a replica

which is pending manual

replica creation.

Complete the manual creation of the replica and then

retry this operation.

3120

8



which is missing.

Verify that the disk containing the replica volume and

the recovery point volume is shown in Disk

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

9



which is inconsistent.

Run synchronization with consistency check for this

replica and then retry this operation.

3121

0



DPM server, partial protection

of a replica is not allowed.

3121

1



DPM server, you cannot

233

Error

Code


protect data sources which are

not protected by the primary

DPM server.

3130

0

Failed to create schedule with

the specified start time

because the date is invalid.

Specify a date which is less than or equal to 28.

3121

2

You have selected a clustered

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.

3121

3

You cannot recover to original

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

4

Switch protection failed

because there is no protection

agent on the protected

computer.

3121

5

Invalid input. Switching

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

234

Error

Code


a secondary DPM server.

3121

6

Invalid input. You cannot switch

protection for a primary DPM

server. Switching protection is

allowed to switch protection for

protected computers only.

3130

1


created for <data source

name> since protection has

been stopped for this data.

3200

0

DPM was unable to attach the

content database to the SQL

Instance <SQL Server instance

name> on the recovery farm.

1) Check to see that the specified instance of SQL

Server is online.

2) If your SQL database files do not have the .mdf, .ndf,

and .ldf extensions for the primary data file, secondary

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

1

DPM was unable to detect the

presence of the Web

application named

'DPMRecoveryWebApplication'

in the recovery farm.

1) Check to see that the recovery farm is online and

running.

2) Make sure you have created a Web application in the

recovery farm with the name

'DPMRecoveryWebApplication'.

For more information, see the DPM 2010 Operations

Guide.

3200

2

DPM was unable to attach the

content database to the

recovery farm.


running.

2) Check to see that the WSSCmdletWrapper DCOM

component is configured correctly on the front-end Web

server hosting the recovery farm.


Guide.

3200

3

DPM was unable to export the

item <site URL> from the

recovery farm.


running.



235

Error

Code


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

4

DPM was unable to detach the

content database <content

database> from the recovery

farm.


running.

2) Open the SharePoint Central Administration Console

of the recovery farm and delete the content database.

3200

5

DPM was unable to import the

item <site URL> to the

protected farm.

1) Check to see that the protected farm is online and

running.



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

6

DPM found that

'DPMRecoveryWebApplication'

was not properly configured.

1) Check to see that the protected farm is online and

running.

2) Open SharePoint Administration Console and delete

the Web application named

'DPMRecoveryWebApplication' and recreate it.

3) Retry the operation again.

236

Error

Code


3200

7

DPM failed to protect <data

source name> because DPM

detected multiple front-end

Web servers for the same farm

that have the SharePoint VSS

writer enabled.

1) Turn off the SharePoint VSS writer on the front-end

Web servers that you do not want to protect the farm.

Only one front-end Web server in this farm should have

the SharePoint VSS writer turned on.

2) Close the Create New Protection Group Wizard and


3200

8

This Windows SharePoint

Services farm cannot be

protected because DPM did

not find any dependent

databases and search indices

to be protected.

1) Verify that the appropriate SQL Server VSS Writers

on the computers hosting the Windows SharePoint

Services databases are enabled.

2) Verify that the Windows SharePoint Services Search

VSS Writers are enabled on the computers where the

search indices are.

3121

7

You can offset synchronization

frequency only for incremental

backups.

3121

8

The offset is greater than

synchronization frequency.

3121

9

Invalid synchronization

frequency. You can only set

synchronization frequency to 6,

12 or 24 hours.

3122

0

DPM failed to apply the

required policies to this

protection group since the

recovery point limit for this

DPM server has been

exceeded.

If you see this error on the primary DPM server then do

the following:

1) Check to see if you can reduce the number of

express full backupss (or file recovery points) for the

data sources 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

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

237

Error

Code


groups.

3) Reduce the number of data sources being protected

by this DPM server.

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 SectionError 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

238

ReferenceDPM 2010 Troubleshooting Guide

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>.

ExplanationThis 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 ActionTo 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.

The "Hotfix download available" form displays the languages for which the hotfix is

available.

Note

239


Error ID: 324

Error #324 — Data Protection ManagerYou 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.

ExplanationThis 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 ActionTo 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.

240

2. On the target computer, log on as an administrator and then open a command prompt window with elevated privileges.

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:

241

The handle is not valid.)

ExplanationThis error might occur when the Agent Coordinator service is not running or responding on the

target server.


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 (http://go.microsoft.com/fwlink/?LinkId=185786).

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>.

ExplanationItem-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.

242


HyperV role is not installed on the DPM server.

User ActionPerform a full restore of the virtual machine.

If none of the conditions listed in the Explanation section are present, and you still get this error,

try the workaround explained in Microsoft Knowledge Base article 2013544


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)

ExplanationDetailed 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.

243


User ActionTo 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.

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

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.

Caution Note

244

(ID 3133)

ExplanationDPM 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

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 ActionRestart 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)

ExplanationThis error is usually caused by running out of free tapes in the library.

Note

245

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.


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.

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 (http://go.microsoft.com/fwlink/?LinkId=185319).

3. Insert new tapes into the library, and then run a Fast inventory action followed by an Identify unknown tapes action. In DPM Administrator Console, click Management on the navigation bar, click the Libraries tab, and 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

Error #24084 — Data Protection ManagerYou 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

246


size.

ExplanationDPM 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.

User ActionTo 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.

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 for

the following reason:

(ID: 3303)

DPM encountered a critical error while

performing an I/O operation on the tape <Media

Note

247

Label> (Barcode - <Media Barcode>) in <Media

Location Type> <Media Location Info>.

(ID 30101)

ExplanationThis 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.

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 ActionTo 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 sizeWhen 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.

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).

Caution

248

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 buffersAn 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.

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

Caution

249

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))

ExplanationThis 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.

User ActionEnsure 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

250

state. (ID 30300 Details: VssError: The writer

experienced a non-transient error. If the backup

process is retried, the error is likely to reoccur.)

ExplanationThis 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 ActionReview 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:

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.

251

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

Message Windows Server Backup may truncate

Exchange and SQL Server logs being protected

by DPM.

ExplanationUsing Windows Server Backup to create backups of a volume that is protected by DPM may

truncate the Exchange Server or SQL Server logs.

User ActionIf 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.

252

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)

ExplanationYou 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 ActionTo 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]

253

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

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.

ExplanationDynamic 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 ActionYou 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.

254

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.




different volume.



255

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>%




different volume.



256

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.




different volume.



257

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))

ExplanationThis 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 ActionIf 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.

258


DPMv3TShootGuide

Documents

set hkeylocalmachinesoftwaremicrosoftvirtual

mtatempstorepsinfo78

management

reporting

monitoring

trusted sites

remote activate

inventory