none
Receiving an error when trying to add Exchange server to DPM (Error ID 964)

    Question

  • I'm trying to create a new protection group on my DPM 2010 server and I am having trouble.

    My setup is as follows:

    2 Servers, Primary is Win 2003 R2 32-bit domain controller, secondary is Win 2008 R2 64-bit Exchange 2010 SP1 and DPM 2010 (I wish I could put DPM on its own but we do not have the budget, has plenty of memory and processor to run apps).

    I am trying to create a protection group (using the wizard) to backup the Exchange mailbox database, but I am receiving an error when clicking on the + to expand the selection window.

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

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

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

     

    Any thoughts or ideas on what I could be doing wrong?  This is a fresh install of DPM and Exchange has been running perfectly for a few months now.
    Thanks in advanced for your help!

    Thursday, September 09, 2010 9:02 PM

Answers

All replies

  • Hey,

    Can you do a vssadmin list writers and see if the exchange writer has any issues?

    When DPM cannot enumerate, it is mostly the vss writer that has issues

    Brgds,

    Mike Resseler


    Visit System Center User Group Belgium @ http://scug.be and http://scug.be/blogs/scdpm
    Monday, September 13, 2010 11:40 AM
  • Hello,

    Mike is correct.  I good place to start would be with the exchange vss writers.
    Question for you, if you stop and restart the Exchange VSS writer (or reboot) do you get the same thing?
    The event log should show an VSS error of some sort that may give a better indication as to what is going on.


    Thanks
    Shane

    Wednesday, September 15, 2010 3:56 PM
  • I apologize for not getting back to you sooner, I have been out sick since Monday.  Here are the results when I run the vssadmin tool on the server, looks like no errors.  I have rebooted this machine many times since installing DPM. Thanks again for the help.

    Microsoft Windows [Version 6.1.7600]
    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

    C:\Windows\system32>vssadmin list writers
    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2005 Microsoft Corp.

    Waiting for responses.
    These may be delayed if a shadow copy is being prepared.

    Writer name: 'Task Scheduler Writer'
       Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
       Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
       State: [1] Stable
       Last error: No error

    Writer name: 'VSS Metadata Store Writer'
       Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
       Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
       State: [1] Stable
       Last error: No error

    Writer name: 'Performance Counters Writer'
       Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
       Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
       State: [1] Stable
       Last error: No error

    Writer name: 'System Writer'
       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
       Writer Instance Id: {66d4cc02-c258-4288-8b18-fde7a92736e0}
       State: [1] Stable
       Last error: No error

    Writer name: 'SqlServerWriter'
       Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
       Writer Instance Id: {b6a9f91a-d24d-4703-9718-b0cce3ea412e}
       State: [1] Stable
       Last error: No error

    Writer name: 'DPM Writer'
       Writer Id: {0074a271-4f24-43e0-9ec7-28a44189cb80}
       Writer Instance Id: {4a55c626-21cf-435d-a804-15b3c6b21e94}
       State: [1] Stable
       Last error: No error

    Writer name: 'IIS Config Writer'
       Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
       Writer Instance Id: {55ec7f3f-0f14-4757-82fe-26a489d66e92}
       State: [1] Stable
       Last error: No error

    Writer name: 'IIS Metabase Writer'
       Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
       Writer Instance Id: {2c45b535-688a-421c-9a1b-10fab5fef177}
       State: [1] Stable
       Last error: No error

    Writer name: 'OSearch14 VSS Writer'
       Writer Id: {0ff1ce14-0201-0000-0000-000000000000}
       Writer Instance Id: {5710367f-4f38-489a-afb1-05d33ee2fb9d}
       State: [1] Stable
       Last error: No error

    Writer name: 'ASR Writer'
       Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
       Writer Instance Id: {f2149e70-3506-40e0-95e9-1c039c31d908}
       State: [1] Stable
       Last error: No error

    Writer name: 'BITS Writer'
       Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
       Writer Instance Id: {d41dc3d2-5c5c-4be7-8f27-9bec0ac9d0a5}
       State: [1] Stable
       Last error: No error

    Writer name: 'WMI Writer'
       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
       Writer Instance Id: {bd1d788d-dbbc-435e-8e84-8427cacc388a}
       State: [1] Stable
       Last error: No error

    Writer name: 'Registry Writer'
       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Writer Instance Id: {3063ca2a-329d-4349-9c49-f5f3964253d7}
       State: [1] Stable
       Last error: No error

    Writer name: 'Microsoft Exchange Writer'
       Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
       Writer Instance Id: {3afaaab7-0367-4c65-9ec3-b6c4b024e704}
       State: [1] Stable
       Last error: No error

    Writer name: 'Shadow Copy Optimization Writer'
       Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
       Writer Instance Id: {d51af656-79c9-4318-bc55-c1eb2e0f3920}
       State: [1] Stable
       Last error: No error

    Writer name: 'COM+ REGDB Writer'
       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
       Writer Instance Id: {e00263a1-9961-4db4-ae3d-cba782238888}
       State: [1] Stable
       Last error: No error

    Wednesday, September 15, 2010 7:56 PM
  • Hi Shane,

    Thanks for the suggestion, I posted the results above for you to review.  I have rebooted this server many times since installing DPM and I am still receiving the same error.

     

    Thanks

    Ryan

    Wednesday, September 15, 2010 7:58 PM
  • Hi

    Open the binary catalouge of the DPM agent installation on the Exchange server. Run the SetDpmServer -DPMServerName <servername>. It seems like the COM+ rights isn't correct since your not able to list the servers workloads and your VSS writers is reporting as stable.

    If you want you can verify the COM+ rights. Look at my blogpost regarding this.

    http://robertanddpm.blogspot.com/2010/08/dpm-ra-rights.html

     

    BR

    Robert Hedblom



    Check out my DPM blog @ http://robertanddpm.blogspot.com

    Friday, September 17, 2010 6:50 AM
  • Hello,

    Was the vssadmin output done during the time of failure?

    If DCOM settings are in doubt, a full list of steps to ensure that DCOM has the correct settings can be found here:
    http://blogs.technet.com/b/askcore/archive/2008/05/09/troubleshooting-agent-deployment-in-data-protection-manager-2007-dcom.aspx

    Thanks
    Shane

    Friday, September 17, 2010 9:02 PM
  • Hi, im having the same exactly problem..

    DPM could not enumerate application component Microsoft Exchange Server\Microsoft Information Store\MRT01EXC01\e4afed79-6a88-4e85-b31c-1aab30e56413 on protected computer mrt01exc01.abborges.pt. (ID: 964)

    vsswriter reports no problems at all.

    Did you found solution yet?

    Thanks!

    Thursday, September 23, 2010 9:19 PM
  • Same problem here.

    DPM can't enumerate microsoft exchange.

    I checked all the dcom permission and they are right. I'm able to bakcup system state and shares just not exchange.

    vss writer reports no errors.

     

    btw this is exchange 2010 sp1

     

     

    Tuesday, September 28, 2010 6:30 PM
  • I haven't found a solution yet.  I needed to get my backups up and running so I gave up on DPM and installed Symantec Backup Exec.  No problems to report with BE.
    Tuesday, October 05, 2010 3:44 PM
  • I wonder if it is a Exchange 2010 SP1 issue since I'm not the only one?
    Tuesday, October 05, 2010 3:47 PM
  • Still no solution, this is annoying I need to be able to backup my exchange server. If there is no solution soon I'll have to ditch DPM and get another backup software
    Tuesday, October 05, 2010 6:37 PM
  • Ya, unfortunately that is what I ended up having to do.  Maybe a few months down the line I'll try again, but for now I've switched to Backup Exec.
    Thursday, October 07, 2010 9:37 PM
  • Hello,

    It's the exchange vss writer that enumerates the exchange storage groups.  DPM tracing via the DPM MPSreports and\or the MSDPMCurr.errlog should show one of the other:

    a.) The enumeration is not making it to the DPM server at all
    or
    b.) Enumeration is making it to the DPM server but DPM is having a problem displaying or interpretting it.

    The tracing can be setup on both the exchange and DPM server and ran simultaneously. 

    DPM MPSreports
    http://www.microsoft.com/downloads/details.aspx?FamilyID=721492aa-bdef-410e-855b-5f25a1355bae&displayLang=en

    The trace logs will be in an ETL format and will have to be converted into that you can read.  Log Parser is good for that. http://www.microsoft.com/downloads/en/details.aspx?FamilyID=890cd06b-abf8-4c25-91b2-f8d975cf8c07&displaylang=en


    I'd suggest though to open up a support case with Microsoft help analyze all the data and to expedite a resolution.

     

    Thanks
    Shane

    Wednesday, October 13, 2010 3:27 PM
  • Unfortunately my company does not have support with Microsoft and we do not have the money right now to open up a support ticket.  If you have any other ideas I'd be glad to try them.

     

    Thanks
    Ryan

    Friday, October 22, 2010 8:37 PM
  • Hello,

    Unfortunately a deeper level of analysis (verbose tracing etc...) is not the kind of thing that can always be accurately done on a forum posting as the logs themselves can get rather large and filtering through them all can take quite a while at times. As stated before:

    a.) The enumeration is not making it to the DPM server at all
    or
    b.) Enumeration is making it to the DPM server but DPM is having a problem displaying or interpretting it.

    If you can't open up a support incident then if you wish, you can take a look at the logs and see if the enumeration is taking place. As you are trying to enumerate the SG in question, go back to the exchange server and make sure the exchange writer is in a stable state.

    Shane

     

    Monday, October 25, 2010 2:19 PM
  • Hi,

    We are experiencing same kind of problems: "DPM could not enumerate application component Microsoft Exchang Server\Microsoft Information Store\Replica\exnode1\....." and "vssadmin list writers" display no errors on the exnode1 -server. Tried reinstalling the agent which caused the DPM console to crash (mmc stopped responding) but agent install was successful at least to the extent that I can enumerate shares and system protection from exnode1 in the DPM console.

    Any solutions or possible workarounds for backing up EX2k10 DAG servers with DPM 2010?

    Jaakko

    Saturday, November 27, 2010 7:57 AM
  • Hi,

    I recently had a similar issue with a customer.


    Look into the E14CmdletsWrapperCurr.errlog (on the protected Exchange server in Program Files\Microsoft DPM\Temp) and search for error like:

    1704   15A4   01/06  18:00:18.367  31     E14Cmdlets.cs(424)                WARNING       E14Cmdlets:GetDAGName(): Exception Caught = System.Management.Automation.PSArgumentException: The Windows PowerShell snap-in 'Microsoft.Exchange.Management.PowerShell.E2010' is not installed on this machine.

    1704   15A4   01/06  18:00:18.367  31     E14Cmdlets.cs(424)                WARNING          at System.Management.Automation.PSSnapInReader.ReadOne(RegistryKey mshSnapInRoot, String mshsnapinId)

    It appeared that there was a problem with the Exchange Powershell files that started after upgrading Exchange 2010 to SP1. We verified if the following Powershell files were present in the %ExchangeInstallPath%\bin directory:

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

    Also checked if these registry files existed:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\PowerShellSnapIns]
    @=""

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\PowerShellSnapIns\Microsoft.Exchange.Management.PowerShell.E2010]
    "CustomPSSnapInType"="Microsoft.Exchange.Management.PowerShell.AdminPSSnapIn"
    "ApplicationBase"="C:\\Program Files\\Microsoft\\Exchange Server\\V14\\bin"
    "AssemblyName"="Microsoft.Exchange.PowerShell.Configuration, Version=14.0.0.0, 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"
    "PowerShellVersion"="1.0"
    "Vendor"="Microsoft Corporation"
    "Version"="14.0.0.0"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\PowerShellSnapIns\Microsoft.Exchange.Management.PowerShell.Setup]
    "CustomPSSnapInType"="Microsoft.Exchange.Management.PowerShell.SetupPSSnapIn"
    "ApplicationBase"="C:\\Program Files\\Microsoft\\Exchange Server\\V14\\bin"
    "AssemblyName"="Microsoft.Exchange.PowerShell.Configuration, Version=14.0.0.0, 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"
    "PowerShellVersion"="1.0"
    "Vendor"="Microsoft"
    "Version"="14.0.0.0"

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\PowerShellSnapIns\Microsoft.Exchange.Management.Powershell.Support]
    "CustomPSSnapInType"="Microsoft.Exchange.Management.Powershell.Support.SupportPSSnapIn"
    "ApplicationBase"="C:\\Program Files\\Microsoft\\Exchange Server\\V14\\bin"
    "AssemblyName"="Microsoft.Exchange.Management.Powershell.Support, Version=14.0.0.0, 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"
    "PowerShellVersion"="1.0"
    "Vendor"="Microsoft Corporation"
    "Version"="14.0.0.0"

    Customer was missing 2 of these registry keys. After copying them from a other Exchange 2010 server to this one, DPM could enumerate fine.

    After that, we installed SP1 on a Exchange 2010 VM and exactly the same happened. So this can be reproduced.

    Hope this will help,

    Frans Moolenaar

     

    • Edited by FransMo Monday, January 17, 2011 9:46 AM added background info
    • Proposed as answer by Nageshbk Wednesday, February 09, 2011 10:17 AM
    Thursday, January 13, 2011 8:00 AM
  • Frans thank you very much, i had the exact same problem.  I've also noticed that on my primary exchange server the exchange powershell tool no longer exists.  I had to copy the entire bin folder from another updated 2010 SP1 server.  I'm thinking SP1 is causing troubles.
    Tuesday, January 18, 2011 8:36 AM
  • housekeeping - closing old post.  Open a new post if you still have a need.

    Regards, A.Nadar, This posting is provided "AS IS" with no warranties, and confers no rights.

    Wednesday, June 20, 2012 9:59 PM
  • Thanks so much this solved my problem.. I had missing registries 

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\PowerShellSnapIns\Microsoft.Exchange.Management.Powershell.Support]

    and 

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\PowerShellSnapIns\Microsoft.Exchange.Management.PowerShell.E2010]

    Tuesday, October 16, 2012 8:07 AM
  • This worked for me as well ... Running Exchange 2010 SP2 RU6.  I couldn't add a new database to an existing DPM protection group.  I did notice I couldn't run the Exchange Management Shell on the Exchange server too.  

    I followed these instructions and it worked perfectly.  Both issues are resolved.  Thank you.

    Tuesday, August 20, 2013 1:46 PM
  • Had an similar issue today:

    have to protect Exchange 2010  with DPM 2012 R2 on Server 2012 R2.

    Installed an connected the agent without Problems via setdpmserver.exe.

    By configuring the Protectiongroup there were no Exchange Databases shown in DPM, but information ID: 964 about Exchange VSS-Writer.

    Checked the writers, no issue. Checked DCOM, no issue. Checked Registry, no issue.

    Tried different Workflows but nothing worked for me.

    Then I installed .net Framework 4.0 on exchangeserver , bingo ...

    Different to your problem I was able to install and configure Protection Agent.

    • Proposed as answer by ntAdmin Thursday, April 03, 2014 9:41 AM
    Thursday, April 03, 2014 9:40 AM
  • I can confirm the scenario and the solution proposed by ntAdmin. As I know there's no public reference about .NET Framework 4.0 requirement for DPM Agent or Exchange protection. Thanks to a colleague I clearly found the evidence of this requirement in the wrapper configuration file Program Files\Microsoft Data Protection Manager\DPM\bin\E14CmdletsWrapper.exe.config:

    <?xml version="1.0"?>
    <configuration>
        <startup useLegacyV2RuntimeActivationPolicy="true">
            <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0"/>
        </startup>
    </configuration>

    As posted here http://www.experts-exchange.com/Software/Backup_Restore/Q_28402388.html it is necessary to install the Microsoft .NE Framework 4.0 (Extended), the .NET 4.0 Client Profile isn't enough.

    Thursday, July 17, 2014 5:11 PM