You are browsing the archive for Troubleshooting.

Getting the non-administrator client recovery working in DPM 2010

8:47 am in Uncategorized by mikeresseler

As said in a previous post, with the latest QFE, it is now possible to give your end-users the possibility to recover data from the DPM server through the DPM Client UI, without them being local administrator on their machine.

This is a feature that many administrators wanted, and now it is finally there.

So after installing the QFE on my environment, I started to test this out.

Now here is the first catch…

There is a mistake in the documentation of the KB.  It states the following:

The administrator of a client computer has to set the name of non-admin users who have permissions to perform end-user recovery of protected data of a client computer.  To do this, the administrator must add the following registry key and value for each of those non-admin users

Registry Key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\Agent\ClientProtection and then create a new key called ClientOwner as REG_MULTI_SZ

So first thing is browse to that hive


Second thing was inserting the new registry key


When I couldn’t get it working, I wrote an email to the product team and also digged in to the log files.  There it clearly stood that the key needed to be ClientOwners with an S at the back.

PS: REG_MULTI_SZ = Multi-String Value


I changed that, but it still didn’t work as I expected.  Luckily, the product team replied very fast (thank you Venkat!) and gave me the naming convention to use for placing the non-admin users in that key. (which I had wrong also ofcourse…)

The convention is: DOMAIN\Username



And if you want multiple non-admin users in that registry, then you need to use DOMAIN\Username, DOMAIN\Username2


When that was done, I rebooted the windows computer, waited until a backup was taken and then it worked:



Next post will go deeper into the Client protection



Update: Thanks to Alex Smits, who saw I had the wrong QFE link…

From the Forums: Could not enumerate Exchange

8:50 am in Uncategorized by mikeresseler

Here’s a strange case that has been discussed on the great DPM forums.

A user reported that he could not enumerate the Exchange server when he was creating a protection group for Exchange Server using the DPM wizard.

These are the errors he got:

DPM could not enumerate application component Microsoft Exchange Server\Microsoft Information Store\xxx\17a465cc-90ca-4abd-927f-9aed49f33b5e on protected computer xxx. (ID: 964)
Please make sure that writer is in good state.

DPM could not enumerate application component Microsoft Exchange Server\Microsoft Information Store\xxx\17a465cc-90ca-4abd-927f-9aed49f33b5e\File on protected computer xxx. (ID: 964)
Please make sure that writer is in good state.

DPM could not enumerate application component Microsoft Exchange Server\Microsoft Information Store\xxx\17a465cc-90ca-4abd-927f-9aed49f33b5e\Logs on protected computer xxx. (ID: 964)
Please make sure that writer is in good state.

We let him do all the usual stuff but it didn’t solved anything.

Until today, nothing was found to solve this case, and there were many more reporting this issue.  But today, a user named Frans Molenaar found a solution.  Although it sounds like a very strange solution which has nothing to do with the issue, I decided to test it out in my sandbox and come to the conclusion that it actually indeed solved the case.

So here goes:

First: Check on the exchange server if the following powershell scripts exist:

In  %ExchangeInstallPath%\bin you need to find the following scripts:

  • CommonConnectFunctions.ps1
  • CommonConnectFunctions.strings.psd1
  • Connect-ExchangeServer-help.xml
  • ConnectFunctions.ps1
  • ConnectFunctions.strings.psd1
  • RemoteExchange.ps1
  • RemoteExchange.strings.psd1

Second: Check the following registry keys if they exist:


“ApplicationBase”=”C:\\Program Files\\Microsoft\\Exchange Server\\V14\\bin”
“AssemblyName”=”Microsoft.Exchange.PowerShell.Configuration, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35″
“Description”=”Admin Tasks for the Exchange Server”
“ModuleName”=”C:\\Program Files\\Microsoft\\Exchange Server\\V14\\bin\\Microsoft.Exchange.PowerShell.Configuration.dll”
“Vendor”=”Microsoft Corporation”

“ApplicationBase”=”C:\\Program Files\\Microsoft\\Exchange Server\\V14\\bin”
“AssemblyName”=”Microsoft.Exchange.PowerShell.Configuration, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35″
“Description”=”Setup Tasks for the Exchange Server”
“ModuleName”=”C:\\Program Files\\Microsoft\\Exchange Server\\V14\\bin\\Microsoft.Exchange.PowerShell.configuration.dll”

“ApplicationBase”=”C:\\Program Files\\Microsoft\\Exchange Server\\V14\\bin”
“AssemblyName”=”Microsoft.Exchange.Management.Powershell.Support, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35″
“Description”=”Support Tasks for the Exchange Server”
“ModuleName”=”C:\\Program Files\\Microsoft\\Exchange Server\\V14\\bin\\Microsoft.Exchange.Management.Powershell.Support.dll”
“Vendor”=”Microsoft Corporation”

If this is not the case, then copy the registry keys from another exchange server and after that, it works.

To test this, I exported some of the registry keys, removed them and tried the DPM wizard.  I got exactly the error as described in the thread.  After imorting the keys again, everything worked as a charm.

If you have this similar issue, then check these things out

For the complete thread:

And thank you Frans Molenaar for finding this solution



DPM 2010 Hyper-V Protection: Cluster networks for CSV redirected access

1:01 pm in Uncategorized by mikeresseler

Another great KB is launched…

This is all about that you can “kill” your network by protecting your hyper-v virtual machines on a CSV, by using a software VSS providor.

This has been discussed on the forums for many many times, and now, we finally have a clear, explained reason, and some workarounds and solutions

A must read KB if you want to protect VM’s




DPM and the case of EFS

7:59 am in Uncategorized by mikeresseler

A question that has come to the forums many times… How does DPM handle files that are encrypted with EFS.

Although most of us kind of knew how it worked at the back, it was never a proven statement.  Now, there is finally a KB that explains it quite well.

When you are protecting files that are encrypted, this is what happens:

– If a file has not changed since the last sync, DPM will not transfer any data. 
– If a file has changed and is not encrypted with EFS, DPM transfers only the changed blocks of a file.
– If a file has changed and the file is protected with EFS, DPM will transfer the entire file.
So now we know it for sure 😉
Make sure that you keep this in mind when planning your PG’s.  This could lead to a significant increase in transferred data so plan well.

DPM SQL Management Studio: Evaluation has expired

6:22 am in Uncategorized by mikeresseler

On the forums, we got a notification from a user that he got the following error when trying to open the SQL Management Studio from DPM.


I had asked him to check if it was a licensed version and so it was.  This intrigued me and I decided to check a few things.  On my test environment, I received the exact same notification although DPM and SQL were still running.  Because my test environment was an upgrade from beta to RC to eval, I figured that it had to do something with the upgrade, and the fact that the first instances of SQL were installed with evaluation versions.

So I decided to ask for the help of the MVP’s and very soon (actually from minute one :-)) I received answer from Kenneth Van Surksum, Artem Pronichkin and Denny Cherry with possible solutions.

Apparently, there are two versions of this problem.

1. Only the SQL Management Studio has expired.  This is the problem when you did the upgrade path from the Beta 1 because that was still with SQL 2008 evaluation without SP1, and this was fixed in SP1.  To fix it now, you can follow KB 971268 (


2. The second issue is that SQL itself has also expired, which strangely leads that DPM continue to work, until the first time that you need to restart the SQL server or restart the server itself (everybody needs to patch right :-)) This is discussed in KB 2020443 (

So in the end, if you are facing or the Management Studio expiration, or after a restart the the SQL instance doesn’t start, then work with the solutions and it will be fixed

Thanks for the assistance guys



From the forums: DPM is unable to enumerate Virtual SSP Writer on computer [computer name]. (ID: 3005)

4:38 pm in Uncategorized by mikeresseler

This is an interesting one that I found on the forums.  Normally, when you get this error message, this is the advice that I give:

1. Is the SPWriter service running on the WFE servers?

2. If they are running, use the following to register the writer: (

Or in short: stsadm -o registerwsswriter if you don’t want to go trough the article

3. Do a vssadmin list writers to see if there are errors with the vss writers

4. Run the configuresharepoint again with a farm administrator account

5. Try again


But in this case, and in a few other cases, it didn’t seemed to resolve the issue.  So the problem had to be somewhere else.  Since the issue couldn’t be helped with the assistance of the forum guys, a call was opened with Microsoft.

Unfortunately, the DPM guys couldn’t solve it either.  Therefore, the sharepoint guys had to assist, and in this joint venture, they found the solution:

Here is the quote of the administrator with the problem

Basically, the error was related to the inability to enumerate all resources defined in the farm’s configuration.  What the actual issue was turned out to be a missing database for one of the search services that was configured.

A similar internal MS bug was found that referenced issues with the Search services.  This led us to look at restarting our Search services on all of the servers in the farm.  Even though all of the search services were "running", one of them would not restart and asked to reprovide the credentials and database names, etc.  Before I submitted the restart, I verified on the SQL Server that the database that was referenced, did not exist !  You may ask, "How was SharePoint stating that the service was running if indeed it was not?"  I’m not sure, but after restarting the particular search service, the database was recreated and the VSS enumeration by DPM worked!

So a possible solution (one that worked for me) is to restart all of your search services and ensure that all ‘referenced’ databases actually exist.

So in the end, it was not a problem with DPM but with the Sharepoint config.  Since I found this interesting (a sharepoint farm that worked, but had issues after all :-)) I decided to search a bit more for this issue.  It seems that it happens quite a lot after an inplace upgrade of sharepoint.

So if you ever get this error, the first 5 steps don’t work for you, then make sure that you check out if the databases exist

Forum Source:



From the forums: Manual agent installation on a DC or RODC

7:59 am in Uncategorized by mikeresseler

As promised in previous post, here is already an interesting topic.

Many people seem to be having issues with installing an agent on a domain controller (DC) or on a read-only domain controller (RODC).  Whether it is through the automatic install or the manual install, sometimes it doesn’t work.  This can be due to various reasons, one of them being the DC or RODC secured more properly.

Below you can find a method for deploying an agent on a DC or RODC when you encounter this.  The method comes from Praveen D [MSFT]

1. Create and populate the following security groups on Primary domain controller: (Where $PSNAME is the name of RODC on which you are planning to install agent)
    a. Create DPMRADCOMTRUSTEDMACHINES$PSNAME  and add DPM server as a member
    b. Create DPMRADMTRUSTEDMACHINES$PSNAME and add DPM server as a member
    c. Add DPM server as a member of Builtin\Distributed com users group
2. Ensure that above changes are replicated on to RODC
3. Install agent on RODC
4. Grant launch and activate permissions for DPM server on DPM RA service by doing the following:
    a. Run "dcomcnfg"
    b. Expand Component Services ->  Expand Computers -> Expand My Computer -> Expand DCOM Config
    c. Right click DPM RA Service and select Properties
    d. Under ‘General’, "Authentication Level – Default"
    e. Under ‘Location’, only "Run application on this computer" should be checked
    f. Under Security, verify that the "Launch and Activation Permissions" (select > "Edit") include the machine account for the DPM Server and Allow
    j. Click OK
5. Copy setagentcfg.exe, traceprovider.dll and LKRhDPM.dll from "c:\Program Files\Microsoft DPM\DPM\setup" on DPM server and place them in "c:\Program Files\Microsoft DPM\DPM\setup" on RODC.
6. Run "setagentcfg.exe a DPMRA domain\DPMserver"  on RODC using an elevated command prompt. (Run setagentcfg.exe from the location above i.e c:\Program Files\Microsoft DPM\DPM\setup)
7. If  a firewall is enabled on RODC run the following commands:
    a. netsh advfirewall firewall set rule group="@FirewallAPI.dll,-29502" new enable=yes
    b. netsh advfirewall firewall set rule group="@FirewallAPI.dll,-34251" new enable=yes
    c. netsh advfirewall firewall add rule name=dpmra dir=in program="%PROGRAMFILES%\Microsoft Data Protection Manager\DPM\bin\DPMRA.exe" profile=Any action=allow
    d. netsh advfirewall firewall add rule name=DPMRA_DCOM_135 dir=in action=allow protocol=TCP localport=135 profile=Any
8. Attach agent on DPM server, now you are ready to protect the RODC.



Another fine new blog?

7:54 am in Uncategorized by mikeresseler

Hey All,

Just discovered (by accident) a new blog about DPM.  The name of the blog is DPMCallBack and can be found here:

The first post is already a good one so I’m hoping for more :-)

The post describes the questions that you will get when you have issues with your DPM installation.  Whenever you want to open a case for DPM, it is good to have these questions answered in advance, it will save you some time 😉

Here is a copy of the questions:

• Is this a fresh installation of DPM using the RTM bits or was this an upgrade from a previous version or from Beta?

• When did the problem first start? You can select the Monitoring tab and review the Alerts/Jobs for details.

• Has it ever worked as expected?

• What changes (if any) were made just prior to the failures?

• Can you reproduce the problem? If so can you please provide the exact steps?

• Are other protected data sources experiencing the same problem?

• Is the error specific to one type of data source? Example, Exchange jobs fail but SQL and SharePoint are successful.

• What is the application version that is experiencing the problem? Example, SQL 2005, SQL 2008, Exchange 2007…etc.

• Is the protected data source running on a standalone server, domain controller or a cluster?

• Is the system that is experiencing the problem in the same domain as the DPM server?

• Do other protected data sources reside on the same machine? Are they also failing?

• Is the target machine for which you’re experiencing the issue on the same LAN as the DPM server or over a WAN?

• What is the error message and ID in the Details pane? If possible, please copy/paste this or provide a screenshot.




Hotfix: Dynamic Disk Hotfix

2:40 pm in Uncategorized by mikeresseler

Hey All,

Microsoft released a hotfix for potential problems with Windows Server 2008 systems.

Could be an important one if you are experiencing issues with dynamic disks, which is what DPM uses.





Troubleshoot Sharepoint Recoveries

7:30 am in Uncategorized by mikeresseler

Hey All,

Just saw a nice video about troubleshooting Sharepoint Recoveries with system center data protection manager 2007.

The video is created by Shane Brasher who is a Senior DPM Support Escalation Engineer.

You can find the video @

In the Video, Shane demonstrates two common failures and how to find information about them.

One of these errors is not enough disk space for the recovery.  It is indeed a fact that to recover something from sharepoint you need to recover the entire site.  And this is sometimes overlooked by administrators.  Both on the recovery farm as the production farm you need to have enough space to recover.

The error you will receive is ID 2035 and can be found in the DPM UI, eventviewer and the MSDPMCurr.errlog

And finally, it is also found back in the trace logs when you need to make them for Microsoft Support.

The other error he explained is a little more difficult to understand.  What he did was recover a site but to an alternate site.

The error shown now was ID 32005: The system cannot find the file specified.

Again, this error is visible in the DPM UI, eventviewer and the MSDPMCurr.errorlog but just shows this cryptic notification.

The log you need here is the WSSCmdLetsWrapperCurr.errlog where there is a much better answer about this error.

It states that you are trying to restore a site to another location which has the wrong template so be aware.

Anyway, a must seen video for all you DPM admins out there.