Share via

Troubleshoot setup and server issues


Updated: May 13, 2016

Applies To: System Center 2012 SP1 - Data Protection Manager, System Center 2012 - Data Protection Manager, System Center 2012 R2 Data Protection Manager

This topic documents the following known issues and resolutions relating to System Center 2012 – Data Protection Manager (DPM) servers.

Setup and configuration issues

Issue Possible Cause Resolution
Unable to install DPM on Read-Only Domain Controller Create a group DPMRATrustedDPMRAs$<Machine name> and then retry setup.
Upgrade fails and trying to uninstall DPM through Add/Remove Programs goes to upgrade rather than uninstall. Copy the DPM 2010 SKUHelper.dll from the setup media and replace the SKUHelper.dll at <Install_Location>\DPM\Setup.

Then try uninstalling with Retain Data option.
Configclasses.xsd is not removed from bin folder after uninstalling CTP2 upgrade. This is a known issue. Delete Configclasses.xsd from the Bin folder and then delete the CTP2 folder.
Computer stops working when you uninstall DPM 2010 with the “Remove data” option. 1. Uninstall DPM 2010 by using the Retain data option.
2. Delete the DPM database.
3. Use Disk Management to delete the volumes created by DPM.
Windows Installer 4.5 installation fails. Run Windows Installer Setup from the \DPM2010\Setup\Redist folder.
SQL Server installation fails. Summary.txt file contains the following:
A network error occurred while attempting to read from the file: C:\SQLSVR2008\x64\setup\x64\
If the SQL Server Native Client is installed on the computer, remove it, and then retry the DPM installation.
A DPM installation interrupts non-DPM applications. During DPM installation, Setup restarts the Windows Management Instrumentation (WMI) service. If you are running applications other than DPM and its prerequisite software on the DPM server, you can experience an interruption in the operation of those applications while the WMI service is restarted. To prevent an interruption, shut down all other applications before you run DPM Setup.
Error 810 or ID: 4315. The trust relationship between this workstation and the primary domain failed. If the DPM server is unable to connect to the domain controller during installation, the DPM installation fails. Verify that the DPM server can communicate with the domain controller. In addition, verify that the DNS entries are for the domain controller and that they are correctly configured.
Error 812. Configuration of reports failed. This problem occurs when both SQL Server Reporting Services and Windows SharePoint Services are installed in the same Internet Information Services (IIS) application pool. To resolve this issue, perform one of the following tasks:

- Uninstall Windows SharePoint Services by using Add or Remove Programs, uninstall DPM, and then install DPM again.


- Configure a side-by-side installation of SQL Server Reporting Services and Windows SharePoint Services. For instructions, see Troubleshooting a Side-by-Side Installation of Reporting Services and Windows SharePoint Services.
Error 820. Setup cannot query the system configuration while performing the prerequisite check on the Windows Server 2008 operating system. This issue occurs if the WMI repository is inconsistent. To resolve this issue, verify that the WMI repository is consistent. At the command prompt, run Winmgmt /verifyrepository. If it is inconsistent, resolve the issue and try the installation again.
DPM is unable to configure the Windows Server account because the password you entered does not meet the Group Policy requirements. The custom password filter software is installed on the domain controllers. Disable the custom password filter before you install DPM.
DPM tries to install a SQL Server instance even when there is one present on the computer. The installation fails and trying to open SQL Configuration Manager gives an Invalid Class error. SQL Server installation does not register certain WMI components. At an elevated command prompt, run the following command: C:\Program Files (x86)\Microsoft SQL Server\100\Shared>mofcomp sqlmgmproviderxpsp2up.mof
Data sources cannot be protected because prerequisite software is missing Error 31008 appears because the DPM prerequisite software requirements are not met. Make sure you have the prerequisites listed in Software Requirements.
Uninstalling DPM does not remove reports When DPM is using a remote instance of SQL Server, uninstalling DPM does not remove the reports that were generated by DPM. To remove these reports, navigate to Reports$<InstanceName> under Default Web Site using Internet Information Services (IIS) Manager, and delete the DpmReports directory.
Network bandwidth usage is not being throttled. The quality of service (QoS) may not be enabled on the production server and the DPM server. If you enabled network bandwidth usage throttling in DPM Administrator Console and the network bandwidth usage is not being throttled, verify that QoS is enabled on the production server and the DPM server.

General issues

Issue Possible Cause Resolution
DPM stops working when master DB is recovered. If the master DB was protected from the same instance as DPMDB, DPM will stop working when the master DB is recovered.
Scheduled jobs not getting triggered when DPM uses a remote SQL instance Ensure that the SQL Server services are running as inbuilt accounts (local system network service) or domain accounts. Running the SQL Server services under the "Managed service account" is not supported.
Some of the DPM Management Shell cmdlets do not work on DPM servers that have NETBIOS names longer than 15 characters. If the NETBIOS name of the DPM server is longer than 15 characters, use the clipped name within the cmdlets.
Unable to add GUID Partition Table (GPT) disk to storage pool. To resolve this issue, either retry the operation or wait 30 sec.
After switching back protection, jobs for some data sources start failing with Access Denied errors. A new backend/physical node was added to a SharePoint farm or cluster after switch protection. This node was protected directly by the secondary server. The primary DPM did not know about this new node until protection was switched back.
  1. Attach agent from primary DPM to the newly added computer.
  2. Run SetDPMServer -DPMServerName <> on the newly added computer.
  3. Make sure the primary protection is green.
  4. Now run modify protection group on the secondary DPM server for the protection group containing affected data source.

    1. Expand the primary DPM server node in the Modify Protection Wizard.
    2. Expand the SharePoint front-end/resource group to which the new computer was added.
  5. Save the protection group.
DPM engine on secondary server stops working after it is denied access to a file on the primary server with the following stack:

 Access to the path '\\\MTATempStore$\PSInfo\78b18367-eb4e-4e1d-8cfd-a7e41cb48d6b.xml' is denied.</ExceptionMessage><ExceptionDetails>System.UnauthorizedAccessException: Access to the path '\\\MTATempStore$\PSInfo\78b18367-eb4e-4e1d-8cfd-a7e41cb48d6b.xml' is denied.

 at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)

 at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy)

 at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy)
Lack of permissions to a share or a name resolution conflict. Change the name resolution order.

For more information see How to change name resolution order on Windows 95 and Windows NT.
The user cannot open DPM Administrator Console. If the user is a member of a group other than the Administrators group, such as Backup Operator, they will not have access to DPM Administrator Console. You must add the user to the Administrators group.
Error 30115: DPM failed to synchronize changes for <Datasource Type> <Datasource Name> on <Server Name>. The shadow copy storage area did not have sufficient storage space to hold the churn on the protected computer. Retry the operation at a later point when the churn is expected to be lower.
Error 30116: VSS has deleted a shadow copy. The shadow copy storage area might have run out of disk space on the server <server name>. Increase the space allocated for the shadow copy storage area for protected volumes on this computer.

To change the settings for shadow copies, do the following:

1. Click Start, click Control Panel, double-click Administrative Tools, and then double-click Computer Management to open Computer Management.
2. In the console tree, expand the node to Computer Management/System Tools/Shared Folders.
3. Right-click Shared Folders, select All Tasks, and click Configure Shadow Copies.
4. Click the volume where you want to make changes, and then click Settings.
5. In the Settings dialog box, change the settings as appropriate.

Note the following:

- To perform this procedure, you must be a member of the Administrators group on the local computer, or you must have been delegated the appropriate authority. If the computer is joined to a domain, members of the Domain Administration group might be able to perform this procedure.
- There is a limit of 64 shadow copies per volume that can be stored. When this limit is reached, the oldest shadow copy will be deleted and cannot be retrieved.
DPM Management Shell stops responding when specific cmdlets are running on a remote instance of DPM server The following cmdlets cause the remote dpm2012short Management Shell to stop responding. Set-MaintenanceJobStartTimeGet-BackupNetworkAddressAdd-BackupNetworkAddressRemove-BackupNetworkAddress




The cmdlets run successfully when they are run in dpm2012short Management Shell on a local dpm2012short server.
BitLocker locks volumes on reboot If you have enabled BitLocker on the DPM server, replicas and shadow copy volumes get locked and become inaccessible. This leads to failure of DPM jobs. The administrator needs to unlock the volumes so DPM jobs can run.