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.

12

DPM cannot browse <server name> because access was denied.

Verify that the computer running DPM has DCOM launch and access permissions for <server name>, and that the system time on the DPM server and <server name> is synchronized with the system time on the domain controller.

13

DPM cannot browse <server name> because the protection agent is not responding.

14

DPM cannot browse <server 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.

2) If a firewall is enabled on <server name>, verify that it is not blocking requests 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.

15

DPM cannot browse <server 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.

31

DPM cannot browse <server name> because the host is unreachable.

1) Make sure that <server name> is online and remotely accessible from the DPM server.

2) If a firewall is enabled on <server name>, make sure that it is not blocking requests from the DPM server.

32

DPM cannot browse <server 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.

33

DPM cannot browse <server 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:

1) Check recent records from the DPMRA source in the Application Event Log on <server name> to find out why the agent failed to respond.

2) Make sure that the DPM server is remotely accessible from <server name>.

3) If a firewall is enabled on the DPM server, make sure that it is not blocking requests from <server name>.

4) Restart the DPM Protection Agent service on <server name>. If the service fails to start, re-install the protection agent.

34

DPM cannot browse <server 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 from the DPM server.

2) If a firewall is enabled on <server name>, make sure that it is not blocking requests from the DPM server.

3) Restart the DPM Protection Agent service on <server name>. If the service fails to start, re-install the protection agent.

60

The protection agent on <server name> was temporarily unable to respond because it was in an unexpected state.

Retry the operation.

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.

35

DPM cannot browse <server name>, either because no agent is installed on <server name> or because the computer is rebooting.

To install a protection agent on <server name>, in the Management task area, on the Agents tab, click Install in the Actions pane.

36

DPM cannot access the path <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 accessible from the DPM server.

2) If a firewall is enabled on <server name>, make sure that it is not blocking requests from the DPM server.

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

42

DPM failed to communicate 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 computer.

4) If you are still facing communication issues between DPM and the protected computer, review the event log on the DPM server and the protected computer for events related to communication issues.

43

DPM failed to communicate with the protection agent on <server name> because the agent is not responding.

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.

45

DPM failed to communicate with the protection agent on <server name> because the agent is not installed or the computer is rebooting.

To install a protection agent on <server name>, in the Management task area, on the Agents tab, click Install 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>.

56

DPM failed to move data because it did not receive the completion status from the protection agent.

Retry the operation.

57

DPM cannot continue to protect the data on <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) Retry the operation.

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.

30400

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 check on file <file name> for volume <protected server volume name> on <protected server name>.

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

2) Retry the consistency check operation.

53

DPM failed to communicate with <server name> because of a communication error with the protection agent.

1) Make sure that <server name> is remotely accessible from the DPM server.

2) If a firewall is enabled on <server name>, make sure that it is not blocking requests from the DPM server.

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 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 type> <data source name> on <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.

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

93

The replica of <data source type> <data source name> on <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 type> <data source name> on <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 source name> on <server name> caused by ongoing replica creation.

Wait for the replica creation operation to complete. Then retry the job.

97

Job failure on replica of <data source name> on <server name> caused by ongoing consistency check.

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

98

Operation failed on replica of <data source name> on <server name> since a recovery operation is currently in progress.

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

99

Job failure on replica of <data source name> on <server name> caused by ongoing stop-protection job.

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

100

Job failure on replica of <data source name> on <server name> caused by ongoing recovery point creation.

Cancel the operation, or wait for it to complete. Then 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.

Retry the operation.

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 source name> on <server 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 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 type> <data source name> on <server name> cannot be applied to <file name>.

113

Job failure for <data source type> <data source name> on <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 name> on <server name> caused by ongoing backup operation.

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

115

Job failure on <data source name> on <server name> caused by ongoing recovery from tape operation.

Cancel the operation, or wait for it to complete. Then retry the 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:

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 <server name> because the 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 2007 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 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 Directory Domain Services 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 parameter tag>.

Select a backup frequency that is equal to or greater than <input 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.

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.

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

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 Windows SharePoint Services data, then you have to remove the databases from protection.

175

Existing volumes do not meet the size requirements for replica and recovery point volumes for <data source type> <data source name> on <server name>. Either use the DPM storage pool disks for protection or create volumes that are adequately sized. DPM will not use any volumes in which either operating system or DPM component are installed.

176

DPM failed to use the volume <volume label> to create the replica since it is not adequately sized. Volumes to be used for the replica should be greater than <minimum size> GB

177

DPM failed to use the volume <volume label> to create the recovery point volume since it is not adequately sized. Volumes to be used for storing the recovery points should be greater than <minimum size> GB

178

DPM failed to use volume <volume label> since this has already been selected to protect <data source type> <data source name> on <server name>

179

DPM cannot resize volumes <volume label> and <volume label> which are being used to protect <data source type> <data source name> on <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.

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 changed due to either of the following:

Retry the operation.

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.

Retry the operation.

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.

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.

Retry the 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 and immediately deleted because of insufficient disk space.

Modify disk allocation to increase space allocation for 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 configured manually when an existing SQL Server 2005 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.

222

DPM cannot browse <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.

223

DPM cannot browse <server name> because the agent is not responding.

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 Replication Agent service on <server name>. If the service fails to start, re-install the protection agent.

224

DPM cannot browse <server name> because of a communication error with the agent.

1) Make sure that <server name> is remotely accessible from the DPM server.

2) If a firewall is enabled on <server name>, make sure that it is not blocking requests from the DPM server.

3) Restart the DPM Replication Agent service on <server name>. If the service fails to start, re-install the protection agent.

225

DPM cannot browse <server name> either because no agent is installed on <server name> or because the computer is rebooting.

To install a protection agent on <server name>, in the Management task area, on the Agents tab, click Install 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.

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

420

DPM could not get security permissions on the replica or recovery point volume.

Review the error details, take appropriate action and retry the operation.

450

An invalid path name was specified for the DPM database location.

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

451

An invalid path name was specified for DPM Report database location.

255

The selected recovery point no longer exists.

265

DPM encountered an error 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 accessible from the DPM server.

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 2007 System Requirements.

272

Work hours are not valid. Specify valid work hours.

273

An Alias or Display name cannot be empty value or contain any of the following characters <input name>.

Specify valid names to search.

274

Unable to configure security settings for <server name> on the computer <computer name>.

Make sure that the password you have provided has 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 details, see the DPM Deployment Guide.

3)To attach the computer correctly to this DPM server, run the SetDpmServer tool on the computer. Refer to Help for details. 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 contain any of the following characters <input name>.

Please enter a valid value to search.

277

Could not connect to the Service Control Manager on <server name>.

1) Make sure that <server name> is online and remotely accessible from the DPM server.

2) If a firewall is enabled on <server name>, make sure that it is not blocking requests from the DPM server.

278

Unable to connect to the Active Directory Domain Services 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>

294

The protection agent 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 protection agent on <server name> because it is the DPM server.

350

Disk <NT disk number> is already in the storage pool.

Select a different disk to add to 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 source name> on <server 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.

300

The protection agent operation failed because it could not communicate with <server name>.

Do the following to troubleshoot this issue:

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.

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

302

The protection agent operation 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.

303

The protection agent operation failed on <server name>.

Review the error details, take the appropriate action, and then retry the agent operation.

304

The protection agent operation 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 the DPM 2007 System Requirements.

335

The protection agent 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.

306

The protection agent installation failed because another version of the protection agent is already installed on <server name>.

Use Add or Remove Programs in Control Panel to uninstall the protection agent from <server name>, and then try reinstalling the protection agent.

307

The protection agent operation failed because DPM detected an unknown DPM protection agent on <server name>.

Use Add or Remove Programs in Control Panel to uninstall the protection agent from <server name>, then reinstall the protection agent and perform the operation again.

308

The protection agent operation failed because DPM could not communicate with the Protection Agent service on <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:

1) Verify that <server name> is 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.

3) Restart the DPM Protection Agent service on <server name>. If the service fails to start, uninstall the protection agent by using Add or Remove Programs in Control Panel on <server name>. Then in the Management task area, on the Agents tab, in the Actions pane, click Install to reinstall the protection agent on <server name>.

309

The agent operation failed because the ADMIN$ share on <server name> does not exist.

Verify that the system root is shared as ADMIN$ on <server name>.

310

The agent operation failed 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.

312

The agent operation failed because the DPM Agent Coordinator service is not responding.

Restart the DPM Agent Coordinator service on <server name>.

313

The agent operation failed 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.

314

The agent operation failed because an installation is already in progress on <server name>.

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

315

The agent operation failed because server <server name> is part of a cluster. DPM does not support protection of clustered servers.

316

The protection agent operation 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 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>.

4) Restart the DPM Protection Agent service on <server name>. If the service fails to start, reinstall the DPM protection agent.

317

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

318

The agent operation failed 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.

319

The agent operation failed because of a communication error with the DPM Agent Coordinator service on <server name>.

1) Verify that <server name> is remotely accessible from the DPM server.

2) If a firewall is enabled on <server name>, make sure that it is not blocking requests from the DPM server. Refer to the DPM 2007 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 agent on <server name>.

322

The following computers <list of servers> were not found in Active Directory Domain Services, or they do not have a Windows Server operating system installed.

Do the following to troubleshoot this issue:

1) Check the spelling of the computer name.

2) Verify that Windows Server 2003 with Service Pack 1 or later is installed on the computer.

3) Verify that you entered the fully qualified domain name for the computer.

4) If the computer has recently been added to the domain, you may need to wait for Active Directory to update.

5) If the computer was recently restarted, wait a few moments and then retry the agent operation again.

6) Verify that a two-way trust is enabled between the domain that the selected computer belongs to and the DPM server's domain.

324

The agent operation failed because the DPM Agent Coordinator service on <server name> did not respond.

Do the following to troubleshoot this issue:

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.

325

The agent operation failed because the protection agent is not active until you restart the selected computers.

Restart the selected computers.

326

The protection agent operation failed because access was denied to the <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.

328

The agent operation failed because the Remote Registry service is not running on <server name>.

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

343

The agent operation failed because <server name> is not a 32-bit x86-based computer or a 64-bit x64-based computer.

329

The agent operation failed 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.

330

The agent operation failed 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 protection agent on <server name> because access to the computer has been denied.

Do the following to troubleshoot this issue:

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 the protection agent (version <agent version>) installed.

Uninstall the existing DPM protection agent from <server name> using Add or Remove Programs in Control Panel. Then in DPM Administrator Console, reinstall the DPM protection agent version that you want. In the Management task area, on the Agents tab, click Install in the Actions pane.

341

The agent operation failed because the credentials you provided do not have sufficient user rights on <server name>.

Retry the agent operation and provide credentials that have administrator user rights on <server name>.

342

The agent operation failed because the DPM server could not communicate with <server name>.

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.

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.

345

The agent operation failed because of a communication error with the DPM Agent Coordinator service on <server name>.

Restart the DPM Agent Coordinator service on <server name>, and then try to reinstall the protection agent.

347

An error occurred when the agent operation attempted to create the DPM Agent Coordinator service on <server name>.

Review the error details, take the appropriate action, and then retry the agent operation.

348

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

Review the error details, take the appropriate action, and then retry the agent operation.

351

Disk <NT disk number> cannot be added to the storage pool.

Make sure that the disks being added to the storage pool do not contain any of the following: system volume, boot volume, OEM or other special volumes, DPM software, or SQL Server databases.

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.

352

Disk <NT disk number> cannot be added to the storage pool because the disk either failed or is missing.

Check Disk Management to see whether the disk is online. If the disk is offline, check the hardware configuration and 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 unallocated disk space in the storage pool.

Add more disks to the storage pool or reduce the replica volume size requirement.

360

The operation failed due to a virtual disk service error

Retry the operation.

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

370

Agent operation failed.

372

The 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 from the DPM server.

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.

Verify the following:

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

404

The agent operation failed when trying to install the Agent Coordinator service.

Verify the following:

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

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 instance of SQL Server.

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.