none
MMC crashed when trying to open Management tab RRS feed

  • Question

  • Hello, folks.

    We have a problem.

    We have freshly installation of Windows Server 2012R2 and DPM 2012R2.
    We connected DPM to DB in production.

    When we start DPM console it works OK, until we don't try to click on Management tab.

    Then we get MMC crashed and this message message about System.Collections.Generic.KeyNotFoundException.

    Any idea why ?

    Thank you in advance.

    Wednesday, October 1, 2014 11:55 AM

All replies

  • Hello, folks.

    We have a problem.

    We have freshly installation of Windows Server 2012R2 and DPM 2012R2.
    We connected DPM to DB in production.

    When we start DPM console it works OK, until we don't try to click on Management tab.

    Then we get MMC crashed and this message message about System.Collections.Generic.KeyNotFoundException.

    Any idea why ?

    Thank you in advance.

    Wednesday, October 1, 2014 11:55 AM
  • what you mean with "We connected DPM to DB in production" ?

    if you restored a existing DB as DPMDB, please run "DpmSync.exe -sync"


    Seidl Michael | http://www.techguy.at | twitter.com/techguyat | facebook.com/techguyat

    Thursday, October 2, 2014 9:10 AM
  • It's not restored DB, it's newly created DB.

    Whole installation was started from 0.

    Thursday, October 2, 2014 9:14 AM
  • Hi,

    Do you have a library attached to your DPM server?  Also what is the number of tapes, slots and drives associated with the library.  We have the same issue and as the library scales, so does the time it takes to get into the management tab.  It used to take 5 minutes or more on multiple DPM servers.  We just doubled our library config and it is no longer possible to get in to the tab anymore.  MMC timeout values kill the console. 

    We opened multiple Premier support cases and they don't have a fix for this and really don't want to believe that its the config of the library.  From what I understand, the first time you hit the management tab, the DB has to scan the entire config and it times out as its too large. 

    They did help us change the MMC timeout value but it no longer works as the library is too big again. 

    Hope this helps as I will be changing my library to be a MUCH smaller config on our next server.

    Eric

    Wednesday, October 8, 2014 1:30 PM
  • I also stood up a new 2012 R2 DPM last week and faced same issue, however that was not only when goes to management tab particularly. it was due to credentials format applied during installation. Lets have a look into this if it is related to your issue.

    http://blogs.technet.com/b/dpm/archive/2012/01/30/fix-the-dpm-console-crashes-and-logs-event-id-945-when-making-any-changes.aspx

    Wednesday, October 8, 2014 6:41 PM
  • Hi,

    Check this and see if it's applicable.

    1. Take a DPMDB backup.

    2. Using SQL management studio - connect to instance used by DPM - Expand the DPMDB database and go to the table tbl_AM_Server.

    3. Edit the table, and under the "servername" column check for the DPM server name. It should be the FQDN. If it is the NetBIOS name then change it to the FQDN.

    4. Save the changes and try to open the console and select the Management
    tab. At this point it should no longer crash.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.


    Wednesday, October 8, 2014 9:10 PM
    Moderator
  • Do a search on "MMC timeout value Data protection manager 2012" and you will see that others have the issue with the library and it will also show the registry fix that was given by support.   In our case we use a VTL.  It took roughly 5 minutes to get into the management tab until recently we had to create another duplicate library on all our DPM servers as we were upgrading our VTL hardware and needed to run in parallel.  Now it usually just times out and crashes.

    I also did check the DPM DB and see if the Server name was the FQDN and it was already set. 

    Thanks

    Thursday, October 9, 2014 2:21 PM
  • Hi,

    If MMC is crashing due to high number of library slots - add / modify this registry setting.

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows
      USERPostMessageLimit:REG_DWORD:4e20


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Thursday, October 9, 2014 4:04 PM
    Moderator