none
Remote Registry high on CASHT server RRS feed

  • Question

  • Hi All,

    I have a DR site running Exchange 2010 SP1 RU3, but somehow on CASHT server the RAM so high, when I trace which process consume the RAM, its remote registry, I know this is not normal, is this KB : http://support.microsoft.com/kb/2563399 can solve the problem ? Or any SP / RU from Exchange can solve the problem ?


    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. Krisna Ismayanto | My blogs: Krisna Ismayanto | Twitter: @ikrisna

    Tuesday, September 11, 2012 5:33 AM

Answers

  • Hi Krisna,

    Yes, BES is sensitive, but as my experience with BES too, Windows update is not have a serious impact with BES itself. For Exchange, yes it related with compatibility. So far, as RIM published on their latest compatibility matrix, Exchange 2010 SP2 already supported by BES 5.03.

    So, since this issue related with Windows, I think it safe to deploy the hotfix. I also have an environment consist of Exchange 2010 SP1 RU6 with Windows Server 2008 R2 SP1 and latest update, also with BES 5.03 in server farm, so far running well :).

    Hope it helps.

    • Proposed as answer by Noya Lau Monday, October 1, 2012 9:31 AM
    • Marked as answer by Noya Lau Friday, October 5, 2012 11:04 PM
    Thursday, September 13, 2012 11:56 AM

All replies

  • On Tue, 11 Sep 2012 05:33:18 +0000, Krisna Ismayanto wrote:
     
    >I have a DR site running Exchange 2010 SP1 RU3, but somehow on CASHT server the RAM so high, when I trace which process consume the RAM, its remote registry, I know this is not normal, is this KB : http://support.microsoft.com/kb/2563399 can solve the problem ?
     
    Have you checked the file versions in the KB against the file versions
    running on your server? If the KB has an inferior build number than
    you already have the fix.
     
    >Or any SP / RU from Exchange can solve the problem ?
     
    Don't know.
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    Tuesday, September 11, 2012 8:43 PM
  • Hi Rich,

    mine is inferior then the KB.


    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. Krisna Ismayanto | My blogs: Krisna Ismayanto | Twitter: @ikrisna

    Thursday, September 13, 2012 4:48 AM
  • Hi All,

    I have a DR site running Exchange 2010 SP1 RU3, but somehow on CASHT server the RAM so high, when I trace which process consume the RAM, its remote registry, I know this is not normal, is this KB : http://support.microsoft.com/kb/2563399 can solve the problem ? Or any SP / RU from Exchange can solve the problem ?


    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. Krisna Ismayanto | My blogs: Krisna Ismayanto | Twitter: @ikrisna

    From the KB:

    Consider the following scenario:
    • You create some customized version 2 performance counters on a computer that is running Windows Server 2008 R2 or Windows 7.
    • Some applications or services remotely query these performance counters.
    In this scenario, the memory usage of the Remote Registry service on the computer keeps increasing. After a while, the available memory is exhausted on the computer. Therefore, the application or service that runs on the computer crashes or stops responding.

    IMHO, if that symptomps similar with your case, then try to deploy the hotfix. Also make sure Exchange and Windows Server always on latest update/patch.

    Thursday, September 13, 2012 10:32 AM
  • Hi Raymond,

    Thanks for the advise for do a Windows Update too, but somehow stuck because in my environment there's also BES which my experience quite a sensitive application. :)


    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. Krisna Ismayanto | My blogs: Krisna Ismayanto | Twitter: @ikrisna

    Thursday, September 13, 2012 10:37 AM
  • Hi Krisna,

    Yes, BES is sensitive, but as my experience with BES too, Windows update is not have a serious impact with BES itself. For Exchange, yes it related with compatibility. So far, as RIM published on their latest compatibility matrix, Exchange 2010 SP2 already supported by BES 5.03.

    So, since this issue related with Windows, I think it safe to deploy the hotfix. I also have an environment consist of Exchange 2010 SP1 RU6 with Windows Server 2008 R2 SP1 and latest update, also with BES 5.03 in server farm, so far running well :).

    Hope it helps.

    • Proposed as answer by Noya Lau Monday, October 1, 2012 9:31 AM
    • Marked as answer by Noya Lau Friday, October 5, 2012 11:04 PM
    Thursday, September 13, 2012 11:56 AM
  • On Thu, 13 Sep 2012 04:48:26 +0000, Krisna Ismayanto wrote:
     
    >mine is inferior then the KB.
     
    Then install the hotfix.
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    Friday, September 14, 2012 2:07 AM
  • Moreover, please also refer to the KB2699780. Hope helps.


    Noya Lau

    TechNet Community Support

    Sunday, September 16, 2012 1:43 AM
  • Hi 

    I have the same issue on CAS-Mailbox server hosting only PF 

    also I guess you will got a lot of warning event from Resource Exhaustion Detector

    do you monitor your environment with scom ? 

    do you got lot of crashing services and strange alerts :(  

    anyhow there a plan to reboot the server this week to release resources from page file

    I will monitor the server after to see if this will solve the problem .

    I rather wait for OS services pack to solve this issue :(  

    my server have  exchange 2010 SP2 RU3 - installing SP2 won't solve your problem but still always good to install the latest SP

    BTW was you can follow the part of the work around to reboot remote registry service    

    http://support.microsoft.com/kb/2699780 

    Sunday, September 16, 2012 8:05 PM