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 Operations Guide. For more information on resolving those errors, see the (User interface messages that are merely informational or instructional have been removed from this catalog.
Lime Green Hydraulic Lime Mortar A natural lime based mortar for conservation, restoration and new build.
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.
The placeholder text indicates a value that DPM provides in the actual error message. Error Messages. Error Codes Error Messages 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. 11 DPM cannot browse because the host is unreachable.
1) Verify that is online and remotely accessible from the DPM server. 2) If a firewall is enabled on, verify that it is not blocking requests from the DPM server. 12 DPM cannot browse because access was denied. Verify that the computer running DPM has DCOM launch and access permissions for, and that the system time on the DPM server and is synchronized with the system time on the domain controller. 13 DPM cannot browse because the protection agent is not responding.
14 DPM cannot browse because of a communication error between DPM and the protection agent on the computer To troubleshoot this error: 1) Verify that is remotely accessible from the DPM server. 2) If a firewall is enabled on, verify that it is not blocking requests from the DPM server. 3) Restart the DPM Protection Agent (DPMRA) service on. If the service fails to start, reinstall the protection agent. 15 DPM cannot browse because a protection agent is not installed on or the computer is restarting. To install a protection agent on, in the Management task area, on the Agents tab, click Install in the Actions pane.
16 DPM cannot access the path because part of the path has been deleted or renamed. Check the path and enter it again.
30 DPM cannot contact until you complete the protection agent installation by restarting the computer. Restart and then try the operation again. 31 DPM cannot browse because the host is unreachable. 1) Make sure that is online and remotely accessible from the DPM server. 2) If a firewall is enabled on, make sure that it is not blocking requests from the DPM server. 32 DPM cannot browse 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 because the agent is not responding. If you just installed an agent on, 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 to find out why the agent failed to respond. 2) Make sure that the DPM server is remotely accessible from.
3) If a firewall is enabled on the DPM server, make sure that it is not blocking requests from. 4) Restart the DPM Protection Agent service on. If the service fails to start, re-install the protection agent. 34 DPM cannot browse because of a communication error with the agent. If you just installed an agent on, 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 is remotely accessible from the DPM server.
2) If a firewall is enabled on, make sure that it is not blocking requests from the DPM server. 3) Restart the DPM Protection Agent service on. If the service fails to start, re-install the protection agent. 35 DPM cannot browse, either because no agent is installed on or because the computer is rebooting. To install a protection agent on, in the Management task area, on the Agents tab, click Install in the Actions pane. 36 DPM cannot access the path because part of the path has been deleted or renamed. Check the path and enter it again.
37 DPM cannot access 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. The Recycle Bin, the System Volume Information folder, non-NTFS volumes, DFS links, CDs, Quorum Disk (for cluster) and other removable media cannot be protected. 39 DPM failed to access the path. Verify that the path can be accessed successfully by using Windows Explorer. 41 DPM failed to communicate with because the computer is unreachable.
1) Make sure that is online and remotely accessible from the DPM server. 2) If a firewall is enabled on, 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 because access is denied. 1) Verify that the DPM server has DCOM launch and access permissions for 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 because the agent is not responding. 1) Check recent records from the DPMRA source in the Application Event Log on to find out why the agent failed to respond. 2) Make sure that the DPM server is remotely accessible from.
3) If a firewall is enabled on the DPM server, make sure that it is not blocking requests from. 4) Restart the DPM Protection Agent service on. If the service fails to start, re-install the protection agent. 45 DPM failed to communicate with the protection agent on because the agent is not installed or the computer is rebooting. To install a protection agent on, 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. 47 Some components of the protection agent on were not installed or configured properly. 1) Verify that the protected computer is not running an unsupported version of the operating system. 2) Consider restarting the computer. If the problem persists, uninstall the Microsoft System Center Data Protection Manager 2007 Protection Agent by using Add or Remove Programs on. Then, on the Agents tab of the Management task area, reinstall the protection agent on. 48 needs to be restarted.
This may be because the computer has not been restarted since the protection agent was installed. 2) If you have any protected data on this computer, synchronize with consistency check after successfully reboots. 49 The protection agent timed out while trying to access the file for volume on. 1) Make sure that the file is accessible. 2) Synchronize with consistency check. 50 The DPM protection agent failed to perform a consistency check on file for volume on. 1) Make sure that the file is accessible.
2) Retry the consistency check operation. 51 Root directories were added to or removed from protection for volume on. 52 The DPM service was unable to communicate with the protection agent on. Restart the DPM Replication Agent service on. 53 DPM failed to communicate with because of a communication error with the protection agent. 1) Make sure that is remotely accessible from the DPM server. 2) If a firewall is enabled on, make sure that it is not blocking requests from the DPM server.
3) Restart the DPM Replication Agent service on. If the service fails to start, re-install the protection agent. 55 The protected volume on could not be accessed. The volume may have been removed or dismounted, or another process may be exclusively using it. Make sure that volume can be accessed, and then click the recommended action link below.
If a new volume 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.
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 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. 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 on. 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. 60 The protection agent on was temporarily unable to respond because it was in an unexpected state. Retry the operation.
62 Cannot find the volume 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. 63 DPM cannot protect 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. 64 Volume is offline on the computer running DPM. Please take the recommended action in Event Viewer on the DPM server. 77 The consistency check job failed due to an internal error. Rerun the consistency check job.
78 DPM is unable to continue protection for data sources on the protected server since it has detected an incompatible filter installed on this server. Refer to the KB article for more details on resolving this error 91 The replica of on is not consistent with the protected data source. 92 Cannot access volume on the replica of on. Stop protection of and then reconfigure protection for this data source.
93 The replica of on 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 on 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 on because of ongoing synchronization.
Cancel the ongoing operation, or wait for it to complete. Then retry the operation. 96 Job failure on replica of on caused by ongoing replica creation. Wait for the replica creation operation to complete. Then retry the job.
97 Job failure on replica of on caused by ongoing consistency check. Cancel the operation, or wait for it to complete. Then retry the job.
98 Operation failed on replica of on 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 on 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 on 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 on. 1) Check recent records from the FSRecord source in the System Event Log on to find out why the problem occurred. 2) Synchronize with consistency check. 109 The replica on the DPM server for on is inconsistent with the protected data source.
Changes cannot be applied. 111 has been restarted without being properly shut down.
112 Changes for on cannot be applied to. 113 Job failure for on caused by an ongoing conflicting operation on.
Cancel the ongoing operation, or wait for it to complete. Then retry the job.
114 Job failure on on caused by ongoing backup operation. Cancel the operation, or wait for it to complete. Then retry the operation. 115 Job failure on on caused by ongoing recovery from tape operation. Cancel the operation, or wait for it to complete.
Then retry the operation. 116 Job failure on 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 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.
To increase the recovery points per day, you must either decrease the retention range or select fewer days of week. 131 File name extensions must begin with a '.' And cannot contain any of the following characters: /,,:, *,?, ',, 132 Please remove duplicate file name extensions. 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: Choose a recovery point that has a time difference with a previous recovery point that is equal to or greater than the specified synchronization frequency. 135 Cannot protect this folder because data on other mount points of this volume have been selected for protection.
136 Unable to create protection group because no disks or tape libraries available. Configure a tape library or add a disk to the storage pool. 137 The protection group name entered already exists.
Enter a different name. 138 The target path 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. 140 The network bandwidth usage throttling rate must be between 1 and 10000 Mbps. Enter a number between 1 and 10000. 141 Cannot perform 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:. Select a backup frequency that is equal to or greater than.
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 for to be set to. 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 cannot be added to protection because it is already a member of a protection group 158 is not a valid value. The maximum is. 159 is not a valid value.
Use only digits and, optionally, a decimal point. 160 does not meet the minimum allocation value of. 164 on 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 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:, 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 on. 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 to create the replica since it is not adequately sized. Volumes to be used for the replica should be greater than GB 177 DPM failed to use the volume 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 GB 178 DPM failed to use volume since this has already been selected to protect on 179 DPM cannot resize volumes and which are being used to protect on 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 on.
No protection will be initiated for on until disk space has been allocated to the storage pool. In the Protection task area, select protection group and click Review Pending Members. Follow instructions to allocate disk space for protection. 181 DPM could not create 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 ' 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. 199 DPM was unable to protect the members in the resource group.
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 since this was part of the SharePoint Farm 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. Choose a recovery point created after the move operation. 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. 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: Server: 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 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 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 because the agent is not responding. 1) Check recent records from the DPMRA source in the Application Event Log on to find out why the agent failed to respond. 2) Make sure that the DPM server is remotely accessible from.
3) If a firewall is enabled on the DPM server, make sure that it is not blocking requests from. 4) Restart the DPM Replication Agent service on.
If the service fails to start, re-install the protection agent. 224 DPM cannot browse because of a communication error with the agent. 1) Make sure that is remotely accessible from the DPM server. 2) If a firewall is enabled on, make sure that it is not blocking requests from the DPM server.
3) Restart the DPM Replication Agent service on. If the service fails to start, re-install the protection agent. 225 DPM cannot browse either because no agent is installed on or because the computer is rebooting. To install a protection agent on, 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. 227 DPM cannot access 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.
Verify that the path can be accessed successfully by using Windows Explorer. 232 Only of the items in can be displayed. Either select for recovery or use the Search tab to find specific items to recover. 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. 235 No library is available for recovery to proceed. From the Library tab in Management, click Rescan to bring libraries online. 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. 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. 238 cannot be used as a destination for recovery because it has not been restarted since the protection agent was installed. Restart and then try the recovery operation again. 239 is not protected. You can filter the list only by computers that have been protected.
241 The volume on is not currently protected. 242 The share ' on is not currently protected.
Make sure that the share name and computer name are accurate. 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 247 is not a valid network path. You must specify a path in the server share format. No wildcards are allowed. 248 is not a valid local path. You must specify a path such as d:, d: folder. No wildcards are allowed.
249 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. 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. 267 The following computers do not meet the minimum software requirements for installing the DPM protection agent:.
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. 270 The agent operation failed on 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, 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 (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 does not have administrator access to the following items: Remove the computers from the 'Select Computers' page or provide credentials for an account that has administrator access to all of the selected computers. 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. Specify valid names to search. 274 Unable to configure security settings for on the computer. Make sure that the password you have provided has administrator privileges on the target computer.
275 Unable to remove from the security group on. Make sure that the password you have provided has administrator privileges on the target computer. 276 A site, document, list or list-item cannot be empty or contain any of the following characters. Please enter a valid value to search. 277 Could not connect to the Service Control Manager on. 1) Make sure that is online and remotely accessible from the DPM server.
2) If a firewall is enabled on, 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. Verify that the credentials you provided have administrator privileges on 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: 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. 294 The protection agent installation or upgrade succeeded. However, DPM could not remove the bootstrap service.
You must restart the protected computer before it can be protected. 295 DPM could not remove the Protection Agent Coordinator service from. Use Add or Remove Programs in Control Panel to uninstall the DPM Agent Coordinator service on. 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. 298 Recovery failed for on. Recover to an alternate location or try recovering from another recovery point.
299 For on, the following items could not be recovered:. 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.
Do the following to troubleshoot this issue: 1) Verify that is online and remotely accessible from the DPM server. 2) If a firewall is enabled on, 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. 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. 302 The protection agent operation failed because it could not access the protection agent on. 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 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. 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. Wait for the protection agent operation on to finish, and then try reinstalling the protection agent again. 305 The agent operation failed because the operating system on 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. 306 The protection agent installation failed because another version of the protection agent is already installed on.
Use Add or Remove Programs in Control Panel to uninstall the protection agent from, and then try reinstalling the protection agent. 307 The protection agent operation failed because DPM detected an unknown DPM protection agent on.
Use Add or Remove Programs in Control Panel to uninstall the protection agent from, 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. If you recently installed a protection agent on, 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 is remotely accessible from the DPM server. 2) If a firewall is enabled on, verify that it is not blocking requests from the DPM server.
3) Restart the DPM Protection Agent service on. If the service fails to start, uninstall the protection agent by using Add or Remove Programs in Control Panel on. Then in the Management task area, on the Agents tab, in the Actions pane, click Install to reinstall the protection agent on. 309 The agent operation failed because the ADMIN$ share on does not exist. Verify that the system root is shared as ADMIN$ on. 310 The agent operation failed because it could not access the ADMIN$ share on. Verify that you have ADMIN$ share permissions on, and that the system time on the DPM server and is synchronized with the system time on the domain controller.
311 Due to changes to, 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. 313 The agent operation failed because an error occurred while running the installation program on. Review the log files on: [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.
Wait for the installation to complete and then retry the agent operation. 315 The agent operation failed because server is part of a cluster. DPM does not support protection of clustered servers. 316 The protection agent operation on failed because the service did not respond. If you recently installed a protection agent on, 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 to find out why the agent failed to respond.
2) Verify that the DPM server is remotely accessible from. 3) If a firewall is enabled on the DPM server, verify that it is not blocking requests from. 4) Restart the DPM Protection Agent service on. 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 ) are missing from the 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. Verify that both 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.
1) Verify that is remotely accessible from the DPM server. 2) If a firewall is enabled on, 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. 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.
322 The following computers 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 did not respond. Do the following to troubleshoot this issue: 1) Check the recent DPMAC source records in the application event log on.
2) Verify that the DPM server is remotely accessible from. 3) If a firewall is enabled on the DPM server, verify that it is not blocking requests from. 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 DPM server. Check the following: 1) If is protected by another DPM server, you cannot install the protection agent on it. 2) If the DPM Agent Coordinator service is installed on, use Add or Remove Programs in Control Panel on to uninstall it. 3) If another protection agent management job is running on, wait for it to complete, and then retry the operation. 328 The agent operation failed because the Remote Registry service is not running on.
Start the Remote Registry service on. On the Administrative Tools menu, select Services. In the right pane, right-click Remote Registry, and then click Start. Note: You can disable the Remote Registry service after the agent operation is complete.
329 The agent operation failed because an incompatible version of is installed on. Install version or later, or uninstall from the computer. If 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 is disabled. Start the Windows Installer service on.
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. 333 A protection agent is already installed on. 334 You cannot install the protection agent on because it is the DPM server. 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:.
Wait a few moments and then try uninstalling the protection agent again. 337 You cannot install the protection agent on because access to the computer has been denied. Do the following to troubleshoot this issue: 1) If another DPM server is currently protecting use that DPM server to uninstall the protection agent from. Then, use this DPM server to install the protection agent on. 2) Verify that the time on the DPM server and the selected computer is synchronized with the domain controller.
At a command prompt, type 'net time /set' to synchronize the time with the domain controller. 3) If the computer is a domain controller, verify that the primary domain controller (the PDC Emulator) is running Windows Server 2003 with Service Pack 1 (SP1), and that Active Directory has completed replication between the domain controllers since the Windows Server 2003 SP1 installation. 338 You can only select computers to install at a time. Select less than computers to add to the Selected Computers list. 340 The protection agent upgrade failed because has a more recent version of the protection agent (version ) installed.
Uninstall the existing DPM protection agent from 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. Retry the agent operation and provide credentials that have administrator user rights on. 342 The agent operation failed because the DPM server could not communicate with.
1) Verify that is online and remotely accessible from the DPM server. 2) If a firewall is enabled on, verify that it is not blocking requests from the DPM server.
3) Verify that the Remote Registry service on is running during the protection agent operation. If the Remote Registry service is not started, on the Administrative Tools menu, select Services. In the right pane, right-click Remote Registry, and then click Start. Note: You can disable the service after the protection agent operation is complete. 343 The agent operation failed because is not a 32-bit x86-based computer or a 64-bit x64-based computer. 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. Restart the DPM Agent Coordinator service on, and then try to reinstall the protection agent.
346 DPM is unable to retrieve the configuration information from. Ensure that the Windows Management Information (WMI) service is started and is accessible from the DPM server.
347 An error occurred when the agent operation attempted to create the DPM Agent Coordinator service on. 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.
Review the error details, take the appropriate action, and then retry the agent operation. 349 An error occurred when the agent operation attempted to transfer agent installation files to. Review the error details, take the appropriate action, and then retry the agent operation. 350 Disk is already in the storage pool. Select a different disk to add to the storage pool. 351 Disk cannot be added to the storage pool.
Make sure that the disks being added to the storage pool do not contain any of the following: system volume, boot volume, OEM or other special volumes, DPM software, or SQL Server databases. 352 Disk 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 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. 355 Disk cannot be removed from the storage pool because it contains storage pool volumes. 356 The folder on which the replicas must be mounted already exists. Clear all unmounted directories from directory and then retry the operation.
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 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 [, ] from DPM disk 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:. 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 [, ] 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 in server cluster. Protection may fail if a failover occurs to. 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 ) on.
Install the updated 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. Verify the following: 1) is online and remotely accessible from the DPM server. 2) A firewall if enabled on is not blocking WMI requests from the DPM server. 3) The WMI service on is running. 401 The agent installation failed while trying to install the Agent Coordinator service. Verify the following: 1) The share ADMIN$ is accessible 2) Remote calls from the DPM server to the Service Control Manager (SCM) on are not blocked by a firewall.
402 When trying to retrieve information from the Windows Management Instrumentation (WMI) service on, access was denied. Verify that you have access to the WMI service on.
403 Access was denied when trying to create the lock file in Admin$. Verify that you have permissions to create the lock file in Admin$. 404 The agent operation failed when trying to install the Agent Coordinator service. Verify the following: 1) The share ADMIN$ is accessible 2) The remote calls from the DPM server to the Service Control Manager (SCM) on are not being blocked by a firewall. 405 DPM could not identify if computer is clustered. Agent installation on 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 is clustered, but could not identify the fully qualified domain name of. Agent installation on 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. 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. 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 [] at location [] to SQL server. Make sure that the SQL server services are running and you are restoring a valid DPM database backup. 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 has been restored from a backup. As a result, the alerts that were generated before 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 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. 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: '. 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.
Review the error details and try again. 467 The specified action can be performed only on a computer with DPM installed.
Run the tool on the DPM server to complete these steps. 469 Unable to detach the database. Check that you have permission to detach the DPM database. 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. 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 1 and 65535. Enter a valid port number. 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. 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 801 To install DPM, you must be logged on as an administrator or a member of the local administrators group. Log on to the computer as an administrator or member of the local administrators group, and then run Setup again. 802 The computer processor speed does not meet the DPM minimum configuration requirements. The minimum required processor speed is.
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 2007 System Requirements. 803 The available memory on the computer is less than the DPM minimum memory requirement.
The minimum memory requirement is 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 2007 System Requirements.
805 There is not enough disk space for. Free additional disk space on this disk, or choose a different location. 807 Setup has detected that IIS has not been installed on the chosen SQL server. Refer to the 'Manually installing Prerequisite Software' section of DPM help for instructions to install IIS and SQL Server 2005 with Reporting Services on the server. Perform the installation on the selected SQL Server and try again. 809 DPM cannot load the file.
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. Use Add or Remove Programs in Control Panel to remove the DPM files and registry entries that were created during Setup.
Verify that SQL Server is properly installed and that it is running, and then run Setup again. 812 Report configuration failed.
Verify that SQL Server Reporting Services is installed properly and that it is running. 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 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 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 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.
Verify that the Windows Management Instrumentation (WMI) service is running. If the WMI service is not running, in Control Panel, click Administrative Tools, and then click Services. Right-click Windows Management Instrumentation, and then click Start. 823 DPM Setup cannot access registry key. Verify that the registry key exists, and then run DPM Setup again. 828 DPM cannot connect to the Service Control Manager (SCM). To troubleshoot this issue, review the recent errors in the Windows Event Log.
829 DPM cannot open the handle to the service. To troubleshoot this issue, review the recent errors in the Windows Event Log. 830 DPM cannot read the service configuration. Review the recent errors in the Windows Event Log on. 832 Setup cannot grant the account access to the DPM database. Verify that SQL Server is properly installed and that it is running.
833 Setup could not delete the user account. To delete the user account, on the Administrative Tools menu, click Computer Management. Expand Local Users and Groups, and then select Users. Right-click, and then click Delete.
834 Setup cannot remove the deployed reports. To delete the reports manually, go to 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 registry key for the instance of SQL Server. Verify that SQL Server 2005 is properly installed. 843 The physical location of the existing DPM database cannot be found. Verify that the instance of SQL Server is properly installed, and that the 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. Expand the instance of SQL Server, expand Databases, right-click the DPMDB database, and then click Delete. 846 DPM cannot locate SqlCmd.exe. Verify that the SQL Client Tools are installed. If they are not installed, you must install the SQL Client Tools, and then run DPM Setup again. 847 DPM cannot create the 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 to. Verify that Setup has access to the installation location. 849 Setup is unable to delete the folder. Delete the folder manually.
850 Setup is unable to mark files at 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. 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 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. 859 Setup cannot parse the SQL Server 2005 Reporting Services configuration file () for the SMTP server address and the address of the sender.
Verify that SQL Server is properly installed. 860 DPM cannot stop service. Review the error details, take the appropriate action, and then try installing DPM again. 861 DPM cannot read the installation path registry key.
Some of the folders will not be deleted. Manually delete the folders after completing DPM Setup. 862 Setup cannot start the service. Verify that Microsoft SQL Server 2005 is properly installed and that the Microsoft$DPM$Acct account is enabled.
863 You cannot use the selected location 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. Select a different location on which to install DPM.
864 You cannot install DPM on removable media or a network share. The location cannot be used as an installation location.
Select a location on a local hard drive to install DPM. 865 Setup could not enumerate the information about volumes allocated to DPM. On the Administrative Tools menu, 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.
867 DPM Setup cannot lock down IIS as required for security purposes. Use Add or Remove Programs in Control Panel to uninstall DPM, SQL Server 2005, and Internet Information Server (IIS). Then run DPM Setup again. 868 DPM cannot query the volume information for directory.
Select another installation location on a local hard drive to install DPM. 869 The directory is not on an NTFS volume. Install the prerequisite software and DPM on a volume formatted with NTFS. 870 DPM cannot query the attributes of directory. Select another installation location on a local hard drive to install DPM. 871 DPM Setup has detected an existing installation of DPM on this computer.
The existing installation is a later version than the version you are trying to install. To install the earlier version of DPM, you must first uninstall the existing version. 876 DPM Setup cannot create the folder.
If the folder already exists, delete the folder, and then run DPM Setup again. 877 DPM Setup cannot write to file. If the file already exists, delete the file, and then run Setup again.
878 Setup cannot create the protection job schedules. Open SQL Server Management Studio, and then connect to the DPM instance of SQL Server. Expand the instance of SQL Server, browse to SQL Server Agent, and then in Jobs, delete the category.
879 DPM Setup could not delete service. To delete the service manually, at the command prompt, type 'sc delete '.
880 The DPM protection agent configuration failed. Review the error details, take the appropriate action, and then try installing DPM again. 881 The required local group could not be created. Try installing DPM again. 882 DPM Setup could not create a required service. This computer may be protected by another computer running DPM.
You cannot install DPM on a computer on which a protection agent is installed. If the DPM protection agent is installed on this computer, use Add or Remove Programs in Control Panel to uninstall it, and then run DPM Setup again. 883 DPM Setup cannot read the file. Verify that the current user has permissions to read the file. 884 DPM Setup cannot delete folder. Manually delete the folder after completing DPM Setup.
885 DPM Setup cannot create the file. Verify that the current user has permissions to create the file. 886 This program is for internal DPM use only.
To launch the DPM Setup program, double-click Setup.exe in the root folder of the product DVD. 887 An error occurred while trying to configure DPM. Uninstall DPM by using Add or Remove Programs in Control Panel, and then run DPM Setup again. 888 DPM Setup could not create the DPM shortcut on your desktop. To start using DPM, 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.
Delete the existing files at, 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 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 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. 894 DPM Setup could not delete the DPM shortcut on your desktop.
Manually delete the DPM shortcut from your desktop. 895 The service was not deleted from the computer. Restart the computer to delete the service. 896 DPM could not connect to database. Verify that the SQL Server service is started, and that you have permissions to query the SQL Server. 897 DPM could not delete database.
In SQL Server Management Studio, delete the following databases:,. 898 DPM Setup cannot query the SQL Server Reporting Services configuration. Verify that the Windows Management Instrumentation (WMI) service is running, and that your SQL Server Reporting Services installation is not corrupt. 899 DPM Setup could not delete the MSDPMTrustedMachines local group. Manually delete the MSDPMTrustedMachines group.
On the Administrative Tools menu, click Computer Management. Expand Local Users and Groups, and then click Groups. Right-click MSDPMTrustedMachines, and then click Delete. 900 DPM Setup could not delete all the registry keys that DPM uses. 901 DPM Setup could not delete the DPM Agent Coordinator service. Manually delete the DPM Agent Coordinator service.
On the Administrative Tools menu, click Services. Right-click DPM Agent Coordinator, and then click Delete.
904 The protection agent on is not compatible with the DPM version. The protection agent version is, and the DPM version is.
Update the protection agent on. 905 The protection agent on is not compatible with the DPM version. The protection agent version is, and the DPM version is. Verify that all required DPM updates are applied to this computer.
907 The job encountered an internal database error. Retry the operation. 908 The job was canceled. The user either canceled the job or modified the associated protection group. Retry the operation. 909 DPM has received an improperly formed message and was unable to interpret it. Retry the operation.
If the problem persists, contact Microsoft Customer Service and Support. 910 The DPM service terminated unexpectedly during completion of the job. The termination may have been caused by a system reboot.
Retry the operation. 911 DPM was not able to complete this job within the allotted time. In the Monitoring task area, group jobs by type and review the job details. If the next scheduled occurrence of this job is currently running, no action is required. If the job is not currently running, retry the job.
912 The job has been canceled because of the failure of another job on which it depended. Retry the operation. 913 The job was canceled because it was scheduled during the inactivity timeframe. Retry the operation. 914 The job failed because of an unexpected error Make sure that the DPMRA service is running on the selected computer.
915 The operation failed because the data source VSS component is missing. Check to see that the protected data source is installed properly and the VSS writer service is running. 916 Cannot connect to the DPM service because it is running in recovery mode, which was initiated by the DpmSync tool. Please wait for DpmSync to complete its operation. If DpmSync is not running and the DPM service is still in recovery mode, then run DpmSync again. 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. 918 Connection to the DPM service has been lost.
Make sure that the DPM service is running. Review the application event log for information about a possible service shutdown. 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. 921 The operation failed because an error occurred while enumerating the data source for the SqlServerWriter on which mirroring was enabled using Internet Protocol Version 4 (IPv4) or Internet Protocol Version 6 (IPv6).
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. 939 The DPM Administrator Console version is incompatible with the DPM server version.
Ensure that the version is between and. 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 configured correctly.
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. 943 Unable to connect to the DPM 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. 945 Unable to connect to the DPM database because of a general database failure.
Make sure that SQL Server is running and that it is configured correctly. 946 Another instance of DPM is currently running.
Restart the computer and then retry the operation again. 948 Unable to connect to.
Verify that the DPM service is running on this computer. 949 A connection to DPM Server 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 removed: Schedules updated:.
956 DPM is unable to protect your Windows SharePoint Services farm until you install agents on the following servers:. 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.
998 The operation failed because of a protection agent failure. Retry the operation. 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. 1100 DPM: Information alert:.
1101 DPM: Warning alert:. 1102 DPM: Critical alert:. 1103 DPM: Recovery alert:. 1104 DPM: Resolved information alert:. 1105 DPM: Resolved warning alert:.
1106 DPM: Resolved critical alert:. 1107 The following alert became inactive. 1108 The following alert occurred. 1109 For more information, open DPM Administrator Console and review the alert details in the Monitoring task area. 1200 Status: Volume: Computer: Description: Used disk space on replica volume exceeds threshold of.
For more information, open DPM Administrator Console and review the alert details in the Monitoring task area. 1201 Status: Data source type: Data source: Computer: Protection group: Description: Replica volume cannot be detected. For more information, open DPM Administrator Console and review the alert details in the Monitoring task area. 1202 Status: Protection Group: Description: DPM discovered one of the following changes: a. New shares or volumes b. Deleted volumes or shares c. Shares have been remapped.
For more information, open DPM Administrator Console and review the alert details in the Monitoring task area. 1204 The replica for on 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. For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1205 Status: Data source type: Data source: Computer: Description: Replica is being created. For more information, open DPM Administrator Console and review the alert details in the Monitoring task area. 1206 The replica of on is inconsistent with the protected data source. All protection activities for this data source will fail until the replica is synchronized with consistency check. For more information, open DPM Administrator Console and review the alert details in the Monitoring task area. 1209 Status: Computer: Description: Recovery jobs started @.
For more information, open DPM Administrator Console and review the alert details in the Monitoring task area. 1210 Status: Computer: Description: Recovery jobs started @ completed with some failures. For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1211 Recovery to that started at completed. Some jobs have successfully recovered data and some jobs have failed. For more information, open DPM Administrator Console and review the alert details in the Monitoring task area. 1212 Status: Computer: Description: Recovery jobs started @ completed successfully. For more information, open DPM Administrator Console and review the alert details in the Monitoring task area. 1214 Status: Data source type: Data source: Computer: Description: Last recovery points not created.
For more information, open DPM Administrator Console and review the alert details in the Monitoring task area. 1215 Status: Data source type: Data source: Computer: Description: Synchronization jobs failing. For more information, open DPM Administrator Console and review the alert details in the Monitoring task area. 1216 Status: Data source type: Data source: Computer: Description: DPM failed to stop protection. For more information, open DPM Administrator Console and review the alert details in the Monitoring task area. 1217 Status: Description: New protectable computers found.
For more information, open DPM Administrator Console and review the alert details in the Monitoring task area. 1218 The replica for on is not created. You have chosen to create the replica manually. All subsequent protection activities for this data source will fail until the replica is created and synchronized with consistency check. For more information, open DPM Administrator Console and review the alert details in the Monitoring task area. 1219 The replica for on is not created. Replica creation job is scheduled to run at a later time.
Data protection will not start until replica creation is complete. For more information, open DPM Administrator Console and review the alert details in the Monitoring task area. 1220 Status: Description: The disk cannot be detected or has stopped responding.
All subsequent protection activities that use this disk will fail until the disk is brought back online. For more information, open DPM Administrator Console and review the alert details in the Monitoring task area. 1221 Status: Computer: Description: Incompatible DPM protection agent.
For more information, open DPM Administrator Console and review the alert details in the Monitoring task area. 1222 Status: Computer: Description: Unable to contact DPM protection agent. For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1223 Status: Computer: Description: Failed to update end-user recovery permissions. For more information, open DPM Administrator Console and review the alert details in the Monitoring task area. 1224 Status: Volume: Computer: Description: Network bandwidth usage throttling not working. For more information, open DPM Administrator Console and review the alert details in the Monitoring task area. 1225 Unsupported data found. For more information, open DPM Administrator Console and review the alert details in the Monitoring task area. 1226 Status:: Description: is not available, and all jobs for this library will fail until the connection is established.
For more information, open DPM Administrator Console and review the alert details in the Monitoring task area. 1227 Status:: Description: Library is not functioning efficiently. For more information, open DPM Administrator Console and review the alert details in the Monitoring task area. 1228 Status:: Drive: Description: Tape is decommissioned and should be removed from the library. For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1229 Status:: Description: Number of free tapes is less than or equals the threshold value. For more information, open DPM Administrator Console and review the alert details in the Monitoring task area. 1230 Status:: Tape: Description: Tape erase job failed For more information, open DPM Administrator Console and review the alert details in the Monitoring task area. 1231 Status:: Tape: Description: Tape verification job couldn't start or failed. For more information, open DPM Administrator Console and review the alert details in the Monitoring task area. 1232 Status: Description: Data copy job failed For more information, open DPM Administrator Console and review the alert details in the Monitoring task area. 1233 Status: Description: Library catalog for backup job was not built correctly.
For more information, open DPM Administrator Console and review the alert details in the Monitoring task area. 1234 Status: Description: Backup to tape failed. For more information, open DPM Administrator Console and review the alert details in the Monitoring task area. 1237 Status:: Library drive: Description: A drive in the library is not functioning.
For more information, open DPM Administrator Console and review the alert details in the Monitoring task area. 1238 Status:: Tape: Description: Tape has been verified For more information, open DPM Administrator Console and review the alert details in the Monitoring task area. 1240 Status:: Description: Job requires tape that is not available in the library For more information, open DPM Administrator Console and review the alert details in the Monitoring task area. 1243 Status:: Tape: Description: Detailed tape inventory failed For more information, open DPM Administrator Console and review the alert details in the Monitoring task area. 1244 Database size on DPM server has exceeded the threshold value. For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1245 Status:: Tape: Description: Data integrity verification failed. For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1246 Status: Volume: Computer: Description: Used disk space for recovery point volume exceeds threshold of. For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1247 Status: Data source type: Data source: Computer: Description: DPM failed to configure protection. For more information, open DPM Administrator Console and review the alert details in the Monitoring task area. 1248 Status: Data source type: Data source: Computer: Description: Consolidation of recovery points failed. For more information, open DPM Administrator Console and review the alert details in the Monitoring task area. 1249 Status: Description: DPM detected multiple disks with the same disk identification number (DiskID). None of these disks will be added to the DPM Storage Pool. For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
1255 The share that previously mapped to has changed to. DPM will continue to protect, 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. 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 while performing an operation for. 1) Refer to the detailed error code in the description 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. 2035 The operation failed because of inadequate disk space. Increase the amount of free space on volume 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 on. 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 on. Verify that on 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 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.
3001 Reporting Services Server cannot connect to the DPM database. To repair the configuration, follow steps for repairing DPM from DPM Setup Help. 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 2007 Deployment Guide. 3007 The report cannot be displayed because the report property settings are incorrect. Repair your DPM installation using the steps described in the DPM 2007 Deployment Guide.
3008 The SQL Server Agent service is not responding. Restart the SQL Server Agent service. 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. The number of days of available data must be at least before DPM can generate this report. To generate this report, specify at least days.
3012 DPM cannot perform this action because no valid property settings have been detected for this report. Repair your DPM installation using the steps described in the DPM 2007 Deployment Guide. 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 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 2007 Deployment Guide. 3015 DPM is unable to change the e-mail settings. On the Start menu, point to All Programs, point to Microsoft SQL Server 2005, 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. 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. On the Administrative Tools menu, click Computer Management. Expand Local Users and Groups, and then click Users. Right-click, and then click Set Password.
3020 Unable to configure local Windows account in the system. The operation is allowed only on the primary domain controller for the domain. Review the error details and take appropriate action.
Then retry the operation. 3021 DPM is unable to create the Windows account group because the group already exists.
Delete the Windows account group, and then retry the operation. 3022 DPM is unable to create the Windows account because the account already exists. Delete the Windows account, and then retry the operation. 3023 DPM is unable to configure the Windows account because the password you entered does not meet the Group Policy requirements.
Enter another password for the account. 3024 DPM cannot grant the DPM database access to the account. Verify that SQL Server is running, and that it is configured correctly. 3025 You are unable to add the local computer to the intranet security zone in Internet Explorer because of insufficient permissions.
Log on as an administrator or backup operator, and then try the operation again. 3027 The report schedule has expired and will be reset. Check the DPM report settings. 3028 You cannot add the computer to the trusted zone. We recommend that you reinstall Internet Explorer Enhanced Security Configuration. Use Add or Remove Programs in Control Panel. Click Add/Remove Windows Components, and then check Internet Explorer Enhanced Security Configuration.
However, you can proceed to the report by specifying your password in subsequent steps. 3029 DPM has detected incorrect property settings for certain reports.
Repair your DPM installation using the steps described in the DPM 2007 Deployment Guide. 3030 DPM is unable to create the report schedule because the date specified has already past. Specify today or a later date. 3031 DPM is unable to create the schedule because the time specified has already past. Specify a future date.
3032 The report file does not contain an entry for the description. Repair your DPM installation using the steps described in the DPM 2007 Deployment Guide. 3033 The report file contains an incorrect description value. Repair your DPM installation using the steps described in the DPM 2007 Deployment Guide. 3034 DPM reporting requires ASP.NET 2.0, which is not found or installed on this computer. Install ASP.NET 2.0. Use Add or Remove Programs in Control Panel.
Click Add/Remove Windows Components, check Applications Server, and then click Details. Check ASP.Net and Internet Information Services (IIS), and then click OK. 3035 DPM is unable to read the registry to retrieve report settings because of insufficient permissions. Log on as an administrator and then retry the operation. 3036 DPM reporting cannot query the IIS configuration. Connect to the computer on which the DPM database was created.
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. On the Start menu, point to All Programs, point to Microsoft SQL Server 2005, 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 Directory Domain Services database.
Either run a synchronization, or wait for the next scheduled synchronization to occur. If the problem persists, check your domain configuration. 3052 Active Directory Domain Services schema is not configured properly. Redo the schema extension operation.
3053 No nodes have been detected for cluster. 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: Ensure that the dependent volumes for the data sources are online. 3100 The used disk space on the computer running DPM for the replica of has exceeded the threshold value of%%. If you do not allocate more disk space, synchronization jobs may fail due to insufficient disk space. Allocate more disk space for the replica. If no free disk space is available in the storage pool, you may need to add physical disks to the computer running DPM.
3101 Recovery data for on in protection group resides on a volume that cannot be detected. All subsequent protection activities relating to 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 on. 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. 3104 The replica for 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.
No action required. 3105 The replica of on is being created. After the initial replica is created, only incremental changes are synchronized. No action required. 3106 The replica of on 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. 3109 The recovery jobs for that started at, with the destination of, are in progress.
No action required. 3110 The recovery jobs for that started at, with the destination of, have completed. Some jobs successfully recovered data and some jobs failed. The following items could not be recovered:.
Make sure that the file is not already present and in use on the destination computer, and that there is sufficient disk space for the files. 3111 The recovery jobs for that started at, with the destination of, 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. 3112 The recovery jobs for that started at, with the destination of, 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 for on have been failing. The number of failed recovery point creation jobs =.
3115 Since, synchronization jobs for on have failed. The total number of failed jobs =. The last job failed for the following reason: 3116 DPM failed to stop protection for on. 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.
3118 The replica for on is not created. You have chosen to create the replica manually.
All subsequent protection activities for this data source will fail until the replica is created and synchronized with consistency check. 1) Manually copy data to the replica path as specified in the details for this data source in the Protection task area. 2) After you copy the data, click the link below to synchronize with consistency check. 3119 The replica for on is not created. 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 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.
3121 The DPM protection agent on is incompatible with this DPM instance. All subsequent protection and recovery activities for will fail until the correct version of the agent is installed. On the Agents tab in the Management task area, check the status of the agent and update to the correct version. 3122 The DPM protection agent on 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: On the Agents tab in the Management task area, check the status of the agent. 3123 Failed to update permissions used for end-user recovery on.
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. Either stop the DPM protection agent service on 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. 3126 The share that previously mapped to has changed to.
DPM will continue to protect, but recommends you modify protection as suggested in Recommended Action. To start protecting, 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, in the Protection task area, perform the following steps: 1) Stop protection for this share. 3127 DPM detected multiple disks with the same disk identification number (DiskID). None of these disks will be added to the DPM Storage Pool.
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.
3154 Description: New data source found. For more information, open DPM Administrator Console and review the alert details in the Monitoring task area.
3155 Description: Data source missing. For more information, open DPM Administrator Console and review the alert details in the Monitoring task area. 3159 Creation of recovery points for on have failed. The last recovery point creation failed for the following reason: 3160 Synchronization jobs for on have failed. 3161 Recovery data for on in protection group resides on a volume that cannot be detected. All subsequent protection activities relating to 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. 3162 The replica of on is being created. After the initial copy is made, only incremental changes are synchronized.
No action required. 3163 The replica of on is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check.
3164 The recovery jobs for that started at, with the destination of, are in progress. No action required. 3165 The recovery jobs for that started at, with the destination of, have completed. Some jobs have successfully recovered data and some jobs have failed. On the Jobs tab in the Monitoring tasks area, filter jobs by type to view details of the recovery jobs. 3166 The recovery jobs for that started at, with the destination of, have completed.
Most or all jobs failed to recover the requested data. On the Jobs tab in the Monitoring tasks area, filter jobs by type to view details of the recovery jobs. 3167 The recovery jobs for that started at, with the destination of, have successfully completed. No action required.
3168 DPM database (DPMDB) size has exceeded the threshold limit. DPM database size: GB DPM database location: on. 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. 3169 The used disk space on the computer running DPM for the recovery point volume of has exceeded the threshold value of%% (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 on 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. 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 on 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 Active Directory Domain 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 Active Directory Domain Services. Re-run synchronization or wait for the next synchronization to occur.
If the problem persists, check your domain configuration. 3301 could not be contacted. All jobs for will fail if the connection is not established. The attempted contact failed for the following reason: n 3302 is not functioning efficiently for the following reason: The drive information for 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 2007 Operations Guide. 3303 Library drive in 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 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 is less than or equals the threshold value of. 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 could not be erased for the following reason: 3309 Data on the tapes cannot be verified for the following reason: n 3310 The data copy job failed for the following reason: n 3311 The back up to tape job failed for the following reason: 3312 The backup to tape job completed, but the catalog was not built correctly for on. 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: No action required. 3314 The recovery job is paused because the required tape is not available in. 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 is paused because the required tape is not available in the library. Insert the tape with 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 the Management task area. 3316 The detailed inventory of tape failed for the following reason: 3317 Data verification of on tape in found data integrity issues on the following files: 3500 Your search returned more than 250 results. Only 250 results can be displayed. Use the search controls to refine your search. 3603 To cancel pending replica creation for on, remove all members from the 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. 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.
3606 This job cannot be rerun because the data is not valid. To retry, in the Recovery task area, click Verify data in the Actions pane. 3607 This job cannot be rerun because the data is not valid. To retry, recatalog the tape's contents in the Recovery task area.
3609 This job cannot be rerun because the protection group associated with it has been modified. 3700 An incompatible version of the database was detected. DPM cannot continue loading DPM Administrator Console. Restore a valid database using the steps described in the DPM 2007 Operations Guide, and then retry the operation. 3750 Version of the DPM database, and version of the DPM application are not compatible. Restore a valid database using the steps described in the DPM 2007 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: 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. 4001 There is insufficient disk space on system volume to complete the installation. To continue with the installation, free up 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 2005, 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 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:. Setup will delete these databases. 4006 Service is running under credentials.
Must run under local user credentials. DPM Setup will change the credentials to a local user account. 4007 Service is not installed. The installation is not valid. Uninstall and then run DPM Setup again. 4012 The service is running under 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 instance of SQL Server 2005. 4015 You installed DPM protection agents on several computers. We recommend that you uninstall them before proceeding. In DPM Administrator Console, click Management on the Navigation bar. On the Agents tab, select the agents, and then click Uninstall.
4017 DPM database 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 instance of SQL Server. DPM cannot be installed on an existing database. In SQL Server Management Studio, delete the 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 Active Directory Domain 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 installation failed.
All changes made by the installation to the system were rolled back. Manually install. For instructions, see 'Manually Installing Prerequisite Software' in the DPM 2007 Deployment Guide. 4024 The installation failed.
All changes made by the installation to the system were rolled back. Manually install. For instructions, see 'Manually Installing Prerequisite Software' in the DPM 2007 Deployment Guide.
4025 The configuration failed. Use Add or Remove programs in Control Panel to uninstall. After uninstalling run DPM Setup again.
4026 DPM Setup failed to configure the service. Use Add or Remove programs in Control Panel to uninstall DPM. After uninstalling, run DPM Setup again. 4027 DPM Setup was unable to collect information about volumes in the storage pool because access to the database was denied. Manually delete the volumes allocated to the storage pool or format the disks. 4028 Setup was unable to delete the database.
Manually delete the database using SQL Server Management Studio. 4029 Setup was unable to delete the schedules from the master database. Open SQL Server Management Studio, and connect to the DPM instance of SQL Server.
Expand the instance of SQL Server, browse to SQL Server Agent, and then in Jobs, delete the 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 2005 to remove the reports. 4031 The computer 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 from the intranet zone. 4032 DPM could not delete the user account. Manually delete account.
4033 DPM Setup could not remove the DPM Administrator Console shortcuts from:. Manually delete the DPM Administrator Console shortcuts. 4034 DPM Setup could not delete service.
Manually delete service. On the Administrative Tools menu, click Services.
4035 DPM Setup could not delete the group on computer. Delete the group manually. On the Administrative Tools menu, click Computer Management. Expand Local Users and Groups, and then click Groups.
Right-click, and then click Delete. 4036 The DPM database was removed, however, DPM could not remove database files. Delete the database files manually.
4037 To finish deleting service, you must restart the computer. Restart your computer.
4038 DPM Setup was unable to unmount the volumes from. Manually unmount the volumes using Disk Management. 4039 This computer has less than the recommended amount of memory for optimal performance of DPM.
The recommended amount of memory is 2 GB. Add more memory to this computer or install DPM on a different computer. 4040 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 2005 Service Pack 2 has not been installed on the selected SQL Server.
Install SQL Server 2005 Service Pack 2 or higher and try again. 4045 DPM Setup was unable to set permissions on folder. Verify that the folder is a valid location and that the current user has access to the location. 4046 DPM cannot delete.
Verify that the current user has permissions to delete the file. 4047 DPM Setup was unable to configure service. Review the error details, take the appropriate action, and then try running DPM Setup again. 4049 The installation failed.
All changes made by the installation to the system were rolled back. Use Add or Remove Programs in Control Panel to uninstall DPM. Then manually install.
For instructions, see 'Manually Installing Prerequisite Software' in the DPM 2007 Deployment Guide. 4050 The installation failed. All changes made by the installation to the system were rolled back. Use Add or Remove Programs in Control Panel to uninstall DPM. Then manually install. For instructions, see 'Manually Installing Prerequisite Software' in the DPM 2007 Deployment Guide.
4051 There is insufficient disk space on the program files volume to complete the installation. To continue with the DPM installation, free up MB of disk space on the volume. 4052 You cannot install DPM on a server if a DPM protection agent has been installed it. 4053 DPM Setup was unable to remove the protected computers from the group.
Delete the protected computers from the group. On the Administrative Tools menu, click Computer Management.
Expand Local Users and Groups, and then click Groups. Right-click, and then click Delete. 4054 Setup was unable to add protected computers to the group. Review the error details.
Use Add or Remove Programs in Control Panel to uninstall DPM, and then run DPM Setup again. 4055 DPM Setup was unable to remove DPM and the protection agent from the Windows Firewall exceptions list. If Windows Firewall is enabled, remove DPM and the protection agent from the exceptions list. In Control Panel, click Windows Firewall, click the Exceptions tab, and then delete Microsoft System Center Data Protection Manager 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. 4057 There is insufficient disk space on the database volume to complete the installation. To continue with the installation, free up MB of disk space on the volume.
4058 DPM requires the Microsoft$DPM$ instance of SQL Server. None of the existing SQL Server installations have the name Microsoft$DPM$. Setup will install the Evaluation Edition of SQL Server 2005, which will expire in 180 days. To avoid expiration of SQL Server 2005, exit Setup and install the SQL Server 2005 licensed retail copy, or upgrade to SQL Server 2005 within 180 days. To properly configure the SQL Server 2005 settings, see 'Manually Installing Prerequisite Software' in the DPM 2007 Deployment Guide. 4059 DPM Setup installs the Evaluation Edition of SQL Server 2005 which expires 180 days after installation.
To avoid expiration of SQL Server 2005, exit Setup and install the SQL Server 2005 licensed retail copy, or upgrade to SQL Server 2005 within 180 days. To properly configure the SQL Server 2005 settings, see 'Manually Installing Prerequisite Software' in the DPM 2007 Deployment Guide.
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 Server 2005 Reporting Services cannot be installed or run unless this Web site is available. Use Add or Remove Programs from Control Panel. Uninstall SQL Server 2005 and SQL Server 2005 Reporting Services if already installed. Uninstall Internet Information Server (IIS). Then run DPM Setup again to install IIS and SQL Server 2005 with Reporting Services with the correct configuration. 4065 You did not specify the. 4066 You did not specify a company name.
Specify a company name. 4067 The number of DPM licenses must be greater than or equal to zero. Specify a number for the DPM licenses greater than or equal to zero. 4068 Installation source 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 is mandatory. Specify a valid input. 4070 The prerequisite check failed with errors. Review the errors in the DPM setup log file. Resolve the errors, and then run DPM Setup again.
4071 DPM Setup could not delete the DPM Administrator Console shortcut from:. Please delete the shortcuts manually. 4072 The specified path is invalid. Specify a valid path and verify that the path is accessible. 4073 The command line argument is invalid.
See 'Installing DPM' in DPM Setup Help. 4074 The path exceeds characters. Choose a path with a shorter length. 4075 The command line argument is already specified.
See 'Installing DPM' in DPM Setup Help. 4076 The value for was not specified. See 'Installing DPM' in the DPM Setup Help. 4077 DPM is not installed on this computer. Run DPM Setup from the DPM product DVD. 4078 DPM is already installed on this computer To uninstall DPM, use Add or Remove Programs in Control Panel.
4079 DPM is not installed on this computer. To install DPM, see 'Installing DPM' in DPM Setup Help. 4080 No IN file is specified in the command line.
See 'Installing DPM' in DPM Setup Help. 4081 DPM configuration failed. Refer to the 'Troubleshooting' section of DPM Setup Help. 4082 DPM cannot start service. Start the service manually. On the Administrative Tools menu, click Services.
Right-click, 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 2005 Reporting Services. Refer to 'Troubleshooting' section of DPM help.
4086 DPM has been successfully installed. However, DPM Setup could not delete the extracted folder. Delete folder manually. 4087 DPM Setup could not delete the extracted folder.
Delete folder manually. 4088 DPM Setup could not delete the virtual directory.
Delete the directory manually. On the Administrative Tools menu, click Internet Information Services (IIS) Manager.
Expand the Web Sites folder, expand Default Web Site, and then delete the virtual directory. 4089 DPM Setup could not configure the database. Verify that the MSSQL$ service is started. If the service is not started, on the Administrative Tools menu, click Services. Right-click MSSQL$, 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 2005 Evaluation Edition.
Setup will upgrade the instance to the SQL Server 2005 Retail Edition as part of the DPM upgrade. No action is required. 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 2005, you must manually upgrade to the retail edition of SQL Server 2005. For instructions, see the DPM 2007 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. 4094 DPM Setup could not determine the edition of SQL Server 2005 Reporting Services used in the current installation of DPM. Verify that the Report Server and World Wide Web Publishing services are running: In Control Panel, click Administrative Tools, click Services, and check the Status column for each service.
4095 DPM Setup has detected that the current installation of DPM uses an expired instance of the Evaluation Edition of SQL Server 2000 Reporting Services. Manually upgrade to the retail edition of SQL Server 2000 Reporting Services, and then run DPM Setup again. For instructions for upgrading Reporting Services, see the DPM 2007 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. 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. Make sure that the SQL Server instance used by DPM is running and is accessible over network. 4208 DPM Writer could not access the registry. Make sure that Data Protection Manager is installed correctly. 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. 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. 4216 DpmPathMerge could not query the 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. 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, because the replica is not in a valid state (Validity: ). In DPM Administrator Console, run a consistency check for the data source to ensure that the replica is 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 in order to prevent existing recovery points from getting recycled.
1) Increase the space allocated for the recovery point volume for. 2) Retry the operation after increasing the space for the recovery point volume. 4300 DPM Setup could not delete the DPMRA service. Delete the DPMRA service manually. At the command prompt, type 'sc delete DPMRA'. 4301 DPM Setup was unable to uninstall the Dr. Watson version that DPM installed.
For information about manually uninstalling Dr. Watson, see 'Troubleshooting' in DPM Setup Help. 4303 DPM Setup has detected that 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 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. Review the error log for details. Verify that the Remote SQL Server administrator credentials you provided are correct and that they have logon permissions on the local computer. 4307 DPM Setup is unable to connect to the specified instance of SQL Server.
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: 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 2005 installation failed. All changes made by the SQL Server 2005 installation to the system were rolled back. Manually install SQL Server 2005.
For instructions, see 'Manually Installing Prerequisite Software' in the DPM 2007 Deployment Guide. 4310 The SQL Server 2005 installation failed.
All changes made by the SQL Server 2005 installation to the system were rolled back. Review the log file for failures and take the appropriate action. Uninstall SQL Server 2005 using Add or Remove Programs in Control Panel.
Then run DPM Setup again or refer to the steps in 'Installing Prerequisite Software Manually' in the DPM 2007 Deployment Guide. 4312 DPM Setup detected that the Removable Storage service is running. To install DPM correctly, DPM Setup will stop and disable this service. 4313 DPM Setup could not delete the DPM Library Agent service.
Delete the service manually. At the command prompt, type 'sc delete DPMLA'. 4314 DPM Setup was unable to share the folder [InstallLocation] Temp as MTATempStore$. Review the error details, take the appropriate action, and then run DPM Setup again. 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. 4316 DPM Setup was unable to configure the DPMRATrustedMachines Group security settings.
Review the error details, take the appropriate action, and then run DPM Setup again. 4317 DPM Setup failed to disable the Removable Storage service (NtmsSvc). Manually stop and disable the Removable Storage 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 DPMRADCOMTrustedMachines or DPMRADmTrustedMachines group. Review the error details, take the appropriate action, and then run DPM Setup again. 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.
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. 4321 DPM cannot access registry key on computer. Verify that the registry key exists, that user has full permissions, and that the Remote Registry service is running on this computer and computer. 4323 DPM Setup failed to add a user to the local group. Review the error details, take the appropriate action, and then run DPM Setup again.
4324 You cannot choose the instance on the local machine. Specify a different instance to install DPM or choose the option to let DPM install its own SQL Server instance. If DPM's SQL Server instance already exists, it will be reused. 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.
Review the error details, take the appropriate action, and then run DPM Setup again. 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 is running under 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 from the group. Manually delete account from the group. 4331 The Microsoft System Center DPM Support Files on the SQL Server computer 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 from the instance of SQL Server. Review the error message and retry the action: 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 2007 cannot be installed on the same computer as DPM 2006. Install DPM 2007 on a different computer and migrate your settings using the upgrade tool. For details, refer to the DPM 2007 Upgrade Guide. 4335 Cannot find file:.
Run MigrateDPM2006 [-exportSettings] [-dpm2006server ServerName] first to create the file. 4336 Settings file is invalid. Run MigrateDPM2006 [-exportSettings] [-dpm2006server ServerName] to recreate the file. 4337 The DPM protection agent is not installed on the computer. Install the agent and try the operation again.
4338 Could not find configuration for. Enter a valid name for a computer configuration to migrate. 4339 Failed to copy file from to. Review the error details and take appropriate action. Then retry the operation. 4340 There is insufficient disk space on the database volume on. Free 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. 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 installation of Microsoft System Center DPM Support Files on the selected SQL Server.
Install the SQLPrep.msi located on the installation DVD or installation share, and try again. The package is located inside the DPM2007 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 DPM2007 msi folder. 4346 The settings for data source on server 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 on computer failed and this data source is being skipped. Review the error details and take appropriate action. Then retry the operation. 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. Review the error details, take the appropriate action, 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 replica volumes under the path. Using Disk Management, manually dismount the DPM 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, and then run DPM Setup again. 4357 DPM setup has detected that this server contains data protected from another DPM server or has protection enabled for another DPM server.
Upgrade for DPM servers protecting other DPM servers is not supported. Uninstall DPM v2 Beta2 and the instance of SQL Server 2005 installed with it before installing DPM 2007. 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 current DPM database is inconsistent. To upgrade DPM 2007 Beta2 to DPM 2007, refer to the FAQ for additional information on how to fix this problem, or uninstall DPM 2007 Beta2 and prerequisites with the 'Remove Data' option checked and run DPM 2007 Setup again.
6002 DPM cannot access the path because the SYSTEM account has been denied permission. Set the permissions for the SYSTEM account to allow Full Control of the item.
6003 DPM cannot access the path because the SYSTEM account has been denied permission. Set the permissions for the SYSTEM account to allow Full Control of the item. 6012 DPM cannot access mount points under the path because the SYSTEM account has been denied permission.
Set the permissions for the SYSTEM account to allow List Folder Contents and Read for items in the specified path. 6013 DPM cannot access mount points under the path because the SYSTEM account has been denied permission. Set the permissions for the SYSTEM account to allow List Folder Contents and Read for items in the specified path. 23043 DPM has unexpectedly reached the end of the tape.
This could be because the tape was tampered with. If you have another copy of this tape, then retry recovery using the copy. 23044 Rescan cannot be performed because DPM is currently performing other operations on the server. Wait for the other operations to complete, and then retry this operation. 23045 DPM failed to move one or more tapes to the I/E port slots 1) Check to see that the library door is locked and that the I/E port is retracted. 2) Check to see that there are sufficient free I/E port slots in the library.
24007 Tape cannot be marked as a cleaning tape because it is not a cleaning tape. 24008 DPM cannot complete the requested operation on tape because this tape is being used by some other job. Retry the operation later. 24014 Library lacks power or cables are not connected properly 1) Verify that the library is turned on. 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. 24015 Tape is stuck in the library autoloader.
Remove the tape from the library autoloader. Consult the documentation for your hardware for instructions on troubleshooting tape errors. When the tape is repaired, run the library job again 24017 The 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. 24018 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. 24019 Drive in 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. 24021 DPM attempted to move a tape to but this was occupied.
DPM may not be in synch with the current state of the library. 1) On the Libraries tab in the Management task area, select the library and click 'Inventory' in the Actions pane. 2) If the contains a tape, remove this tape by using the front panel of your library. 24022 The did not contain a tape when DPM expected it to. DPM might not be in synch with the state of the On the Libraries tab in the Management task area, select the and click Inventory library in the Actions pane. 24023 The library mandates that when a tape is dismounted, it should be moved back to the slot it was originally mounted from.
However, the slot is not empty. 1) Remove the tape in the slot by using the front panel of your library. 2) On the Libraries tab in the Management task area, click Inventory library in order to run inventory 24024 A library with the same name is already attached to this server. Please choose a different name for the library. 24025 The operation cannot be performed on because it does not have any I/E ports. 24026 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.
24027 Operation failed since the slot in library was empty. This tape is currently present in Use the front panel of your library to move the tape from its current location to the slot specified above. 24029 Tape erase operation was skipped because does not support tape erase. 24031 DPM was unable to recatalog the tape in in because this tape has not been identified. On the Libraries tab in the Management task area, click Inventory library. Then, select the tape and click Identify unknown tape.
24034 DPM could not reserve the I/E port resource because one of required resources is not accessible. 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. 24036 The operation failed because the I/E port is currently in use. Retry this operation after the I/E port is free. 24037 DPM failed to erase the selected tape because the state of the as seen by DPM is inconsistent with the actual state of the library.
Run a detailed inventory and a fast inventory. 24038 The barcode on the tape in appears to have changed since the last time it was inventoried in DPM.
If the barcode of this tape has been changed, then click the link below to fix this issue. Refresh barcode on tape and 1. Remove the tapes from the library. Clear duplicate barcode information from DPM. 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. 24041 DPM failed to recatalog the imported tape because the tape is blank. DPM can only recatalog a tape that has valid data on it.
24042 DPM failed to recatalog the imported tapes because they do not contain the catalog information. It is likely that your data spans multiple tapes and the catalog information is present on another tape. Insert all tapes associated with the backup and retry the operation. 24050 Failed to perform the operation since the tape is not available in Add tape to the library, or to the drive in the case of a stand-alone tape drive.
Retry the operation after adding tape. 24051 Required tape resource is reserved by another task. Wait for the other task to complete, or cancel the ongoing operation. Retry the operation. 24052 DPM could not reserve the drive resource because one of required drive resources is not online or it needs cleaning or servicing. 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. 24053 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. 24054 Operation cannot be performed on the tape in because it is a cleaning tape.
24055 Operation failed because no usable drives were available in. 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. 24056 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. 24057 DPM failed to create a copy of the tape backup for on 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. 24058 The certificate with serial number issued by will expire. 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. See 'How to Encrypt Data in a Protection Group ' in DPM Help for more information about certificates.
24059 The certificate with serial number issued by will expire. 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 future, and replace this certificate with a valid certificate in the DPM backup certificates collection to continue further backups. 2) If this certificate does not contain a private key, replace this certificate with a valid certificate in the DPM backup certificates collection to continue further backups. See 'How to Encrypt Data in a Protection Group ' in DPM Help for more information about certificates. 24060 Some certificates under DPMBackupStore have changed since the start of the job. Retry the job.
24061 Unexpected tape detected in in Check to see if there are any active alerts indicating suspect tapes. If such an alert exists, take the appropriate recommended action and then retry this job.
24070 Some of the certificates under DPMBackupStore have expired 1) If this certificate contains a private key, move this certificate to the DPM recovery certificates collection for recovering data in future, and replace this certificate with a valid certificate in the DPM backup certificates collection to continue further backups. 2) If this certificate does not contain a private key, replace this certificate with a valid certificate in the DPM backup certificates collection to continue further backups. See 'How to Encrypt Data in a Protection Group ' in DPM Help for more information about certificates. 24071 This DPM server is not authorized to read or write to this encrypted tape because there is no valid certificate in DPMBackupStore and DPMRestoreStore 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.
See 'How to Encrypt Data in a Protection Group ' in DPM Help for more information about certificates. 24072 DPMBackupStore or DPMRestoreStore is not present. Recreate DPMBackupStore and DPMRestoreStore Certificate stores using the Certificate Management console. 24073 No certificate is present under DPMBackupStore. Add certificates to the DPM backup certificates collection. See 'How to Encrypt Data in a Protection Group ' in DPM Help for more information about certificates.
24074 Failed to encrypt data on tape Retry the job 24075 Certificates on tape are corrupt. Data on this tape cannot be recovered. 24076 The command sent by DPM to the library agent timed out. Retry the operation.
24077 DPM failed to mount the tape in drive for the 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. 24078 No certificate with private key is present in DPMBackupStore In the Certificate Management console, open certificate stores for the Computer account on the DPM server. Add a certificate which has the private key to the DPMBackupStore certificates collection.
See 'How to Encrypt Data in a Protection Group ' in DPM Help for more information about certificates. 24079 DPM encountered an error while attempting to parse the tape catalog information for tape. Retry the operation.
24080 DPM encountered a critical error while trying to parse the contents of the tape. 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. 24082 DPM failed to perform the operation since the specified recovery point does not exist 24083 Recovery failed for on. 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 24084 The tape in at 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 1024 bytes and 65536 bytes and hence will not be able to read or overwrite the contents of this tape. 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.
24086 DPM failed to dismount the tape in drive for the 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. 25001 Rescan cannot be performed at this moment because DPM is performing other operations on the.
Please wait for the current library operations to complete and then retry this operation 25002 The tape in at appears to be a cleaning tape. However, this tape is not marked as a cleaning tape. On the Libraries tab in the Management task area, select this tape and click Mark as cleaning tape 25005 The cleaning operation for drive on 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. 25009 DPM is not synchronized with the current state of your library.
Jobs running on the can potentially fail. On the Libraries tab in the Management task area, click Inventory library. If available, select the option to perform a fast inventory, otherwise, perform a detailed inventory.
25010 DPM tried to access on library. This does not exist. 1) On the Libraries tab in the Management task area, 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.
25011 DPM failed to inventory the. This is possibly due to a hardware issue. Refer to your hardware manual for troubleshooting steps. 25012 DPM is not synchronized with the current state of your library. Jobs running on the can potentially fail.
On the Libraries tab in the Management task area, click Inventory library. If available, select the option to perform a fast inventory, otherwise, perform a detailed inventory.
25013 DPM detected that the drive 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. 25014 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. 25015 Drive 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. 4) Refer to your hardware manual for other troubleshooting steps.
25016 DPM failed to use the tape in because it appears to be a cleaning tape that is identified incorrectly as a backup tape. Check if the tape in slot 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. 25017 DPM could not access a drive since some other application is currently using it.
Determine if some other application is using the drive and stop it. 25100 DPM encountered an error while attempting to control the autoloader on library 1) Turn off the library, and then turn it on and retry the operation. 2) Examine the front panel of your library to see if any errors are being reported by your library. 3) Refer to your hardware manual for other troubleshooting steps.
25101 DPM encountered an error while attempting to use tape on the drive. This could be a problem with your drive or tape. 1) Use the tape in a different drive. To do this, first disable the drive. Select this tape and click ‘Identify unknown tape’.
If this operation fails, it indicates a potential problem with your tape. 2) Use the tape 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.
4) Refer to your hardware manual for other troubleshooting steps. 25102 DPM attempted to move a tape to but this was occupied. DPM may not be in synch with the current state of the library 1) On the Libraries tab in the Management task area, select the library and click 'Inventory' in the Actions pane. 2) If the contains a tape, remove the tape by using the front panel of your library. 25105 Tape drives or library devices may have been disconnected or reconnected on the DPM server. On the Libraries tab in the Management task area, click 'Rescan' in the Actions pane. 25106 is either turned off or has been disconnected 1) Check if the is turned on.
2) Check for loose data or power channel connections. 3) Make sure the library is visible in Device Manager.
25107 Drive requires cleaning. The drive will not be used for further operations until it has been cleaned. Drive will be automatically cleaned by DPM.
If you are seeing this error frequently, please service the drive. 25108 The library requires all drives to be empty in order to lock or unlock the door. However, the drive has a tape in it. Use the front panel of the library to move the tape from the drive to an empty slot 25109 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. 25123 The operation failed because the insert/eject (I/E) port of the library is open. Use the front panel of the library to close the I/E port. 25124 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. 25125 DPM was unable to use 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 25126 Failed to obtain drive mapping information from the file DPMLA.xml. The information in this file is not formatted correctly. Refer to the DPM 2007 Operations Guide for instructions on modifying the DPMLA.xml to correctly represent your current library configuration. 30002 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. 30008 DPM failed to recatalog the 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 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.
30012 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. 30015 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 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'.
30024 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. 30025 One or more databases in the storage group failed to mount On the Exchange Server, verify the cause of failure from event logs entries.
30026 One or more databases in storage group failed to dismount On the Exchange Server, verify the cause of failure from event logs entries. 30029 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 another recovery point. 30030 SIS is not enabled on the server. Enable SIS for the server.
30033 The volume is no longer available - it may be dismounted or offline Make sure the volumes are online and mounted. 30037 DPM was unable to determine the last known backup tracking information for this data source. Re-run the job. 30038 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.
30045 At least one of the databases is not online Ensure that all databases in the storage group are online, and then retry the job. 30046 Protection agent is unable to synchronize the replica. Run synchronization with consistent check. 30051 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. 30075 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 30076 Operation failed for on 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.
30077 DPM has run out of free space on the recovery point volume for on. Protection for this data source will fail in order to prevent existing recovery points from being deleted before their expiration. 1) Increase the space allocated for the recovery point volume for. 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.
30078 Operation failed for on 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 and finally run consistency check. 30083 Operation failed for on due to a VSS error on 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. 30084 Operation failed for on due to a VSS error on the DPM server. Rerun the consistency check. 30085 Operation failed for as the system ran out of memory.
Check the Event Viewer entries to figure out the cause. Retry the operation after fixing the problem. 30087 DPM has detected a checksum mismatch during data transfer over the network Retry the operation.
If the problem persists, contact your network administrator to diagnose possible network issues. 30100 DPM has detected that some other application has created recovery points on the recovery point volume for for server. Future backups will fail until these recovery point are deleted. Open the DPM Management Shell and run. Delete-Shadowcopy.ps1 ' to delete the externally created recovery points on the recovery point volume. 30101 DPM encountered a critical error while performing an I/O operation on the tape in.
Retry the operation. If the problem occurs again, contact your hardware vendor to get your hardware serviced. 30102 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. 30103 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. 30104 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. 30105 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. 30106 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. 30107 RA cannot read from/write to temp area.
DPM will recreate the temp area with appropriate permissions 30108 Either the tape 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. 30109 DPM failed to recatalog the 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.
30110 DPM has encountered a critical internal error. (Critical error in reading/parsing DirsAndFileOffsetFileList) Retry the operation. 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. Please allow 10 minutes for VSS to repair itself and then retry the operation.
30112 DPM encountered a retryable VSS error. Check the Application Event Log on for the cause of the failure.
Fix the cause and retry the operation. 30113 DPM encountered an error while trying to create a recovery point for one or more volumes for data source on. This may have happened because the volume name is no longer valid. Retry the operation. 30114 No VSS provider supports one or more volumes for data source on, 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. 30115 DPM failed to synchronize changes for on because the snapshot volume 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.
30116 VSS has deleted a shadow copy since it has probably run out of disk space on the server. Increase the space allocated for the VSS diff area of volumes involved in protection on this server. 30117 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 on. 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. 30118 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 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. 30119 The change journal ID may have changed since the last synchronization. DPM is unable to track changes on this computer.
30120 DPM failed to recover all the files. Recover to an alternate location or try recovering from another recovery point. 30121 File copy failed.
The directory for source location or destination location does not exist. () Exception trace: Please make sure that the source and target locations are correct and have appropriate permissions. 30122 File copy failed. The source location does not exist. () Exception trace: Please make sure that the source and target locations are correct and have appropriate permissions. 30123 File copy failed due to an I/O error. Source location: Destination location:.
() Exception trace: Please make sure that the source and destination locations exist and have full control permissions for the local system account. 30124 Catalog for backup job was not built correctly for on. Retry the operation. 30125 Another backup job of on 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. 30126 Backup of on 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. 30127 Operation failed due to an internal error Retry the operation. 30128 Invalid backup type specified for on. If you are backing up to tape, perform a full backup.
If you are backing up to disk, perform an express full backup. 30129 DPM failed to generate the file list to complete the task. On the Libraries tab in the Management task area, select the tape and then click View Contents in the Actions pane.
30130 DPM failed to start tracking changes for on 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. 30131 DPM is not synchronized with the changes on on. 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. 30132 DPM skipped the synchronization job for on 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. 30133 A critical inconsistency was detected for on and therefore changes cannot be replicated for. 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 consistency check.
30134 DPM failed to clean up data of old incremental backups on the replica for on. 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. 30135 The replica of on is not consistent with the protected data source. DPM has detected changes in file locations or volume configurations of protected objects since the data source was configured for protection. In the Protection task area, click Modify 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. 30136 The replica of on is not consistent with the protected data source.
DPM detected that some protected objects are missing since it was configured for protection. In the Protection task area, click Modify 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. 30137 The replica of on is not consistent with the protected data source. DPM detected new protectable objects for the data source since it was configured for protection. In the Protection task area, click Modify 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. 30138 The replica of on is not consistent with the protected data source. DPM detected changes in existing protected objects and detected new protectable objects for the data source since it was configured for protection.
In the Protection task area, click Modify 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.
30139 The replica is inconsistent for on due to a CCR failover. A synchronization job with consistency check will be automatically triggered after 30 minutes. No action required. 30140 DPM tried to do a SQL log backup, either as part of a backup job or a recovery to latest point in time job. The SQL log backup job has detected a discontinuity in the SQL log chain for database 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. 30141 To recover on, DPM must stop and start the SQL Server service on.
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 another recovery point. 30142 To recover on, DPM must stop and start the SQL Server service on. DPM was unable to successfully stop the service.
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.
30143 Database mount failed for on. Please contact the exchange admin. Verify the cause of failure from event logs entries on the exchange server.
30144 Database dismount failed for on. On the Exchange server, verify the cause of failure from event logs entries. 30146 Data consistency verification check failed for of on. 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. 30147 Eseutil.exe failed to apply logs on database files for on 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.
30148 DPM was unable to access the cluster resource group for of protection group Verify that the cluster resource group is accessible by using the Cluster Administration console. 30149 DPM cannot continue protection for on cluster because this cluster experienced an unexpected failover. 30150 DPM is attempting to back up or restore a SIS link file, which requires SIS to be enabled on. Enable SIS on the computer by using Add/Remove Windows Components in Add or Remove Programs. 30151 DPM failed to read its change tracking information for on.
30152 DPM cannot continue protecting on because the volume on which this data resides on has been resized. 30153 The file system on on which data source of 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. 30154 DPM encountered an unknown error while tracking changes for on.
30155 DPM is unable to continue protection for on because this computer has been powered off without shutting it down cleanly. 30156 DPM is unable to continue protection for on because the change tracking information is corrupt 30157 The alias of the user to which DPM has to connect the recovered mail box is online and connected to an Exchange server. Please specify an alias which is offline and not connected to any Exchange server. 30158 Verification failed for the tape backup of on because the tape backup failed. Retry the tape backup and then retry verification.
30159 DPM cannot continue protection for on cluster because this cluster experienced a failover. 30160 DPM failed to perform the tape backup for on cluster because this cluster experienced a failover. Retry the tape backup job.
30161 DPM is unable to determine tracking information for on. Retry the operation. If the replica has been marked inconsistent, run a consistency check on this data source. 30162 Protection cannot continue because the change journal used for tracking changes for on 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. 30163 The path to the SQL temporary folder for on 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.
30164 The on 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. 30165 The backup job failed because DPM detected that the instance of SQL Server 2000 on 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. 30166 DPM detected that the recovery point volume for 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. 30167 The backup job failed because DPM detected that some databases of the Exchange Server Storage Group instance on are offline. Bring all databases in the storage group online and retry. 30168 Full backup is required for on as 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'.
30169 The operation failed for on because the data source is not available. 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. 4) Make sure that the data source is accessible. Verify that the data source is not missing. 30170 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 on 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. 30171 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 on before starting the recovery. This transaction log backup has failed. Check the Application Event Viewer logs on the SQL 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. 30172 The DPM job failed for on 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. 30173 Execution of SQL command failed for on. Check the Application Event Viewer logs on the SQL 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. 30174 Recovery failed for on because the overwrite flag is not set for.
On the Exchange Administrator Console, set the 'Overwrite database' flags for the databases being recovered and retry the operation. 30175 DPM failed to replicate changes for on 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. 30176 File delete failed due to I/O error. File may be in use by some other application.
File location: Ensure that the file location is correct and that the file has appropriate permissions. 30183 File delete failed because of unauthorized access error.
File path: Ensure that the file location is correct and that the file has appropriate permissions. 30184 DPM cannot continue protection for on.
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. 30185 Recovery for to the latest recovery point cannot be performed because you have already recovered it to a previous recovery point. In the Recovery task area, select the recovery point just prior to the latest recovery point. 30186 The protection agent on is disabled. Enable the protection agent on the protected computer in DPM Administrator Console, in the Management task area, on the Agents tab.
30187 Protection agent on was unexpectedly shut down during synchronization. DPM may have replicated data partially for. 30188 Recovery point for was created when the replica was inconsistent. Some data from this recovery point may contain partially synchronized data.
30189 The execution of the pre-backup script for returned an error. Make sure that the pre-backup script does not have any errors and can execute successfully. 30190 The execution of the post-backup script for returned an error. Make sure that the post-backup script does not have any errors and can execute successfully.
30191 The execution of the pre-backup script for timed out. Make sure that the pre-backup script finishes execution within the time specified, or increase the timeout period. 30192 The execution of the post-backup script for timed out. Make sure that the post-backup script finishes execution within the time specified, or increase the timeout period. 30193 The configuration of the pre-backup script or the post-backup script XML for 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. 30194 DPM cannot protect on 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 30195 DPM has run out of free space on the recovery point volume and will fail synchronization for on in order to prevent existing recovery points from being deleted. 1) Increase the space allocated for the recovery point volume for. 2) Retry the operation after increasing the space for the recovery point volume. 30196 Recovery failed for on as 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. 30197 Recovery failed for on as the specified storage group is not a recovery storage group. Retry the operation and specify a recovery storage group.
30198 Recovery failed for on as the alternate storage group or the database specified is invalid. Verify that the storage group or the database exists on the Exchange server. 30199 Recovery failed for on because the target database specified is in mounted state. Verify that the target database is in a dismounted state. 30200 Prepare for backup operation for on has been stopped because this operation depended on another backup operation which failed or was canceled. Please retry the operation.
30201 Prepare for recovery operation for on has been stopped because this operation depended on another recovery operation which failed or was canceled. Please retry the operation. 30202 The SQL temporary folder for on 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. In the Protection task area, create a recovery point for this database. 30203 Replica for on is already consistent. Scheduled consistency check will not be run on consistent replica. 30204 Replica writer is enabled for on 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. 30205 Recovery failed for on 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. 30207 DPM was unable to compile a list of recoverable objects for. You will be unable to perform detailed level recoveries from this recovery point. No action is required because the next scheduled full backup will synchronize the list of recoverable objects.
Alternately, in the Protection task area, select the required protected object, click 'Create recovery point', and select the option to create a recovery point using a full backup. 30208 Data consistency check timed out for of on. 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. 30209 DPM has detected that the cluster configuration has changed for resource group and has marked the replica inconsistent.
30210 The execution of the pre-snapshot step returned an error. Check to see that the pre-snapshot step does not have any errors and can execute successfully. 30211 The execution of the pre-snapshot step timed out. Check to see that the pre-snapshot step can successfully finish executing within the timeout period. 30212 The execution of the post-snapshot step returned an error.
Check to see that the post-snapshot step does not have any errors and can execute successfully. 30213 The execution of the post-snapshot step timed out. Check to see that the post-snapshot step can successfully finish executing within the timeout period. 30214 Failed to create the System State backup. Check the event log on the protected computer and fix any errors reported. 30215 Failed to create the System State backup within the timeout period.
Check the event log on the protected computer to determine why the backup timed out. 30216 DPM has detected a discontinuity in the log chain for on 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. 30218 Operation failed because DPM encountered an unexpected VSS error. Check the Application Event Log on for the cause of the failure. Fix the cause and retry the operation.
30219 Cmdlet execution failed () for on. Please contact the exchange admin and resolve the issue 30220 Activation of COM component ExchangeCmdletWrapper failed on. Please make sure that the COM component ExchangeCmdletWrapper is configured appropriately. 30221 DPM failed to replicate the changes for the. The operation failed while DPM was attempting to apply the changes to the replica. 30222 DPM is unable to continue protection for on server since the change tracking information is corrupt 30300 Synchronization for replica of on 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.
30301 The replica of on is not consistent with the protected 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. 30302 The replica of on is not consistent with the protected 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. 30303 DPM failed to backup on 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.
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. 30400 To protect the selected data source, needs to be restarted for creating the change journal.
Restart the computer and then synchronize with consistency check. 31000 Operation failed since the protected data source size had not been calculated for prior to running this operation.
Ensure that Get-DatasourceDiskAllocation and Set-DatasourceDiskAllocation are executed successfully prior to running this operation. 31001 Failed to create the protection group since some of the required schedules have not been specified. 31002 Failed to create the protection 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. 31003 Operation failed because is not accessible from the DPM server. Use the cluster management software to check to see if the cluster resource group is online. 31004 Failed to enumerate resource groups on the cluster.
Verify that the Cluster service is running on the cluster 2. Verify that you can ping the cluster from the DPM server. 31005 DPM cannot protect the cluster resource group on 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.
31006 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. 31008 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.
31009 Modify Protection Group is disabled because the following network names have been deleted:. Stop protection of protected members on these clusters before you modify the protection group. 31010 Failed to create the protection group because no members were selected for protection. Retry protection group creation by adding members.
31011 The parameter set that you have specified is incorrect. Specify only short-term disk policy objective. 31012 The parameter set that you have specified is incorrect. Specify only short-term tape policy objective. 31013 The parameter set that you have specified is incorrect. Specify only long-term tape policy objective. 31014 The parameter set that you have specified is incorrect.
Specify only short- and long-term tape policy objectives. 31015 The parameter set that you have specified is incorrect. Specify only short-term disk and long-term tape policy objectives. 31016 Incremental synchronization job cannot run on all the protected items in this protection group. Change the synchronization frequency to 'Just before a recovery point'. 31017 Long-term retention range can be specified only in weeks, months, or years. 31018 The specified retention range supports the following backup frequencies only:.
31019 The item does not exist in protection group. 31020 The item cannot be excluded because it is a data source. 31021 Recovery point cannot be created for external data source. 31022 Recovery point cannot be created for unprotected data source. 31023 Recovery point cannot be created on disk for data source because the protection for has been set to tape.
31024 Cannot run an incremental synchronization and create a recovery point for because the application does not support it. 31025 Recovery point cannot be created on tape for data source because the protection for has been set to disk. 31026 Protection for has been set only to disk.
31027 has drives. You cannot specify a value more than that. 31028 Data source does not belong to a protection group. 31029 Data source has no inactive replica on. 31030 No library has been specified for protection. 31031 Protection for has been set only to tape.
31032 Journal size cannot be set for because this data source does not use a change journal. 31033 Operation failed because the recovery point specified for deletion was created as part of an incremental tape backup. DPM can only delete recovery points that were created as part of a full tape backup. Retry the operation after specifying a recovery point created by a full tape backup. This will automatically delete all the recovery points created by the full tape backup as well as all dependent incremental tape backups.
31034 The operation will remove the following recovery point(s) because they have dependencies on each other: 31036 Consistency check schedule should be modified using the cmdlet. 31037 DayofWeek needs to be specified to continue. 31038 Cannot specify consistency check schedule for protection groups configured only for tape-based protection. 31039 RelativeInterval needs to be specified to continue. 31040 Duplicate times specified, please specify unique times. 31041 Duplicate weekdays specified, please specify unique days of the week. 31042 Cannot specify offset schedules for protection groups configured only for tape-based protection.
31043 Consistency check cannot be started for unprotected data source. 31044 Consistency check cannot be started for data source because the protection for has been set to tape. 31045 There are multiple copies of data. Please choose one of the following and pass it to this cmdlet. 31046 The selected item cannot be added to protection. From the DPM computer, only DPM database can be selected for protection.
31047 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. 31048 Online recatalog can be run for file volume and share data sources only. 31049 The number of recovery point locations should be equal to the number of recoverable items passed to this cmdlet. 31050 The recovery point location that you have passed is invalid. Please try again with a different value.
31051 Add the search path string and try again. 31052 This step cannot be performed because some of the prerequisite steps have not executed. Please ensure that the appropriate steps among have been executed successfully and then retry this step. For more details, see DPM Help. 31053 This protection group does not support the given protection type.
Please try again with a different value. 31054 All data sources passed should belong to the same protection group. 31055 The data source specified is not a part of the protection group. 31056 The minimum space required for the is. Please choose a value more than that and try again. 31057 The disk space requirement for cannot be less than the current value of. Please choose a value more than that and try again.
31058 The data source is not protected and size calculations cannot be done on it. 31059 Size optimization cannot be done on data source. This can be done only if a part of the data source is protected. Retry without the -CalculateSize option. 31060 This recovery source location is on a disk and not on a tape. 31061 Specify a scheduled replica creation time that is less than 1 year. 31062 The protection type has been set to disk-based protection only, therefore this command is ignored.
31063 This tape is marked as a cleaning tape. Run the command on the correct tape. 31064 Incorrect start time specified. Enter the start time in the following format 'hh:mm' 31065 Child data source objects cannot be obtained for external data source. 31066 Protection group does not contain this type of schedule. 31067 This file type has not been specified for exclusion. 31068 This member is not specified for protection and cannot be removed from protection.
31069 Please specify the library to use in RecoveryOption for recovery from tape, and try again. 31070 This operation is valid only on a recovery point on tape. 31071 The recovery point location passed does not belong to current recovery point. 31072 This step cannot be performed because prerequisite steps have not been completed. For more information, type 'Get-Help ' in DPM Management Shell. 31073 Invalid Search Detail Passed 31074 The target computer either does not exist or is currently not protected by DPM 31075 Shares can be retrieved only from a volume recovery point 31076 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 2007 Operations Guide. 31077 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. 31078 System state cannot be recovered back to the original location.
Please restore to an alternate location. 31079 The recoverable item cannot be recovered. Please see DPM Help for more details.
31080 The specified alternate instance is the same as original. Please specify a different instance or change the database name 31082 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. 31083 The alternate database name is empty.
Provide a valid alternate database name to use for the recovery 31084 The alternate SQL instance name is either empty or invalid. Provide a valid alternate SQL instance name to use for the recovery 31085 DPM cannot detect the volume on server. If the volume is present, this problem can be rectified by refreshing the state using the Get-Datasource -ProductionServer -Inquire cmdlet, then retry the current task. 31086 Data source cannot be selected for protection because it was previously protected as part of data source and has inactive disk or tape replicas. Remove the inactive protection for in the Protection task area by selecting the data source and then clicking Remove inactive protection option in the Actions pane.
31087 Data source cannot be selected for protection because its component database was protected independently and has inactive disk or tape replicas. Remove the inactive protection for in the Protection task area by selecting the data source and then clicking Remove inactive protection option in the Actions pane. 31088 The specified short-term backup frequency does not support creation of incremental backups. Please specify a daily backup frequency or remove the CreateIncrementals parameter. 31089 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.
31090 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. 31091 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) 31092 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 31093 The specified subnet mask is not valid for IPV6. Valid subnet mask for IPV6 address lies between 1 - 128. 31094 The specified subnet mask is not valid for IPV4. Valid subnet mask for IPV4 address lies between 1 - 32.
31095 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.
31096 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. 31097 is not an owner for the Exchange cluster resource group.
Contact your Exchange administrator or retry with the fully qualified domain name (e.g. 31098 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)'. 31099 The retention range cannot be achieved with the current synchronization frequency. 31100 Invalid command line parameters specified. Please provide the correct parameters and try again.
31102 The rescan operation failed. For more details, view the Jobs tab in the Monitoring task area. 31103 Rescan operation completed successfully. 31105 The door on the could not be unlocked 31106 Door successfully unlocked for. You can now open the library door. The door will be automatically locked again in minutes. 31107 The door on the 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. 31108 Door successfully locked for.
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. 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, to clean the selected drives. Add cleaning tapes and restart the cleaning job. 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. 31120 The selected tapes cannot be erased because they belong to protection groups. You need to stop protection of the associated protection groups before you can erase the tapes. The protection group that a tape belongs to is listed in the Protection Group column. 31123 I/E port door of 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. 31124 The selected tapes could not be marked as free because another job has reserved them for use. 31125 The selected tape(s) could not be marked as cleaning tapes because they are currently in use. Bidai Serial Bidai Song Sadhna. 31126 tape(s) could not be marked as cleaning tapes because they are currently in use.
31127 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. 31128 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. 31129 out of 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. 31130 out of selected tapes could not be marked as free because another job has reserved them for use. 31131 out of 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. 31133 out of tapes cannot not be erased because they contain data that is being protected. You need to stop protection of the associated protection groups before you can erase the tapes.
The protection group that a tape belongs to is listed in the Protection Group column. 31134 The selected tape(s) could not be unmarked as cleaning tapes because they are currently in use. 31135 tape(s) could not be unmarked as cleaning tapes because they are currently in use. 31136 The selected tape is currently being recataloged. The contents of this tape can be viewed only after the recatalog operation successfully completes. 31137 Operation failed because is offline. 31138 Operation failed because is disabled.
31139 Door of is already unlocked. 31140 Door of is being unlocked. Please wait for the operation to complete. 31141 Door of is already locked. 31142 Door of is being locked.
Please wait for the operation to complete. 31143 Connection already exists to DPM server.
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. 31144 The server 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 your DPM administrator. 31145 Tape in 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.
31146 Operation failed because drive is offline. 31147 Operation failed because drive is disabled.
31150 All selected tapes were successfully moved to the I/E port slots of the library 31151 This operation is not allowed on a suspect tape. Take out the tape in, replace the barcode, and run detailed inventory on the tape.
31200 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. 31203 The selected recovery point is not valid for recovery to a DPM server. 31204 This option is disabled as the DPM database DPMDB cannot be recovered directly to the original location. For more information, see the DPM 2007 Operations Guide.
31205 Latest point in time recovery is not supported from: 1) Secondary DPM server. 2) Invalid replica. 3) Inactive protection. 31206 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. 31207 Cannot perform on a replica which is pending manual replica creation. Complete the manual creation of the replica and then retry this operation.
31208 Cannot perform on a replica 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. 31209 Cannot perform on a replica which is inconsistent. Run synchronization with consistency check for this replica and then retry this operation. 31210 DPM cannot protect this member. On the secondary DPM server, partial protection of a replica is not allowed.
31211 DPM cannot protect this member. On the secondary DPM server, you cannot protect data sources which are not protected by the primary DPM server. 31212 You have selected a clustered resource group for switching protection. This operation will apply to all the nodes under this resource group:. Protection for other resource groups belonging to this cluster may fail. You need to perform this operation for all resource groups to resume protection.
31213 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. 31214 Switch protection failed because there is no protection agent on the protected computer. 31215 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 a secondary DPM server. 31216 Invalid input.
You cannot switch protection for a primary DPM server. Switching protection is allowed to switch protection for protected computers only. 31217 You can offset synchronization frequency only for incremental backups.
31218 The offset is greater than synchronization frequency. 31219 Invalid synchronization frequency. You can only set synchronization frequency to 6, 12 or 24 hours. 31220 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.
Cypress At2lp Rc42 Software Development. 2) Reduce the retention range for the existing protection groups. 3) Reduce the number of data sources being protected by this DPM server.
31300 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. 31301 Recovery point cannot be created for since protection has been stopped for this data. 32000 DPM was unable to attach the content database to the SQL Instance 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. 32001 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 2007 Operations Guide. 32002 DPM was unable to attach the content database to the recovery farm. 1) Check to see that the recovery farm is online and running.
2) Check to see that the WSSCmdletWrapper DCOM component is configured correctly on the front-end Web server hosting the recovery farm. For more information, see. 32003 DPM was unable to export the item from the recovery farm. 1) Check to see that the recovery farm is online and running. 2) Check to see that the WSSCmdletWrapper DCOM component is configured correctly on the front-end Web server hosting the recovery farm.
For more information, see. 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. 32004 DPM was unable to detach the content database from the recovery farm. 1) Check to see that the recovery farm is online and running. 2) Open the SharePoint Central Administration Console of the recovery farm and delete the content database.
32005 DPM was unable to import the item to the protected farm. 1) Check to see that the protected farm is online and running. 2) Check to see that the WSSCmdletWrapper DCOM component is configured correctly on the front-end Web server hosting the protected farm. For more information, see.
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. 32006 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. 32007 DPM failed to protect 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 retry the operation. 32008 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.
You've reached the right place. We have every kind of drivers you'll ever need. Here you'll find free access to the drivers you need. Just do a search using one of our partner sites and you'll find what you need quick and reliably.
No fears of viruses or malwares. Sometimes it's discouraging to download a driver, only to find out your computer's been hijacked by a virus. That's why it's important to download the proper driver from the appropriate authority websites like driveraccess.com. Do you need Windows drivers? Well the most common requests for drivers are Windows drivers. We predict that 90% of all requests are for Windows drivers. It ranges from drivers for the video card to software drivers.
But don't fret, we have each and every single one of these drivers. Guess what, they are all FREE!! Why would you want to ever pay for something that's FREE.
Only someone insane would pay for a FREE item. But there are many out there who goes to other websites and end up paying for FREE drivers. That's why we have a website called driveraccess.
It's access to any and all drivers FREE. We do not host any of the drivers here so it makes it easy for us to give away something that's FREE. Our partners are nice enough to give it away for free and make it accessible to the world. What makes it safe? Well we get this question a lot and the thing that makes it safe is we test our system regularly for security risks. We make sure that none of our links are from spywares or malwares. And we charge our sponsors to put their links on our site so we make just enough to pay for our hosting service and if that's paid for, why would we bother you with the fees?
We remove any potential risks to our site by making it simple and lean. That means it loads up fast and what you see it all you will ever see. Nothing more and nothing less. There's no need to see more than what we already have on our site.
Our partners are the ones that have the drivers you need. We have nothing here. Why do you not charge??
Yes we are crazy like that. We don't like charging because we know there's no fee to us so why would we charge?
Just think of us as the FREE police. We give away information for FREE. Driveraccess.com will never charge you.
We will direct you to the right place for you to get what you need and run. So don't think too much and use our services freely.