none
Server 2003 Event 10010 DCOM Problem RRS feed

  • Question

  • I have a server running Windows Server 2003 which after running for a day or so will start to post the error:

    The server {CLSID} did not register with DCOM within the required timeout.

    The CLSID can be the same or different and it is generally one of our ActiveX DCOM components that our client programs use to obtain business data from the server. These objects are created and used without any issue for about 24 hours after a reboot. Then they start to be reported every 20 minutes or so and users get various "Access Denied" and "Out of memory" errors because the server does not create the specified objects.

    These server has 4 8 core chips and 32GB of memory. I have monitored its status and I have not noted any point at which memory is limited or the processor utilization climbs about 15%.

    Can anyone give me an idea of what is going here or what steps I can take to troubleshoot it? Rebooted the server every day is just not a long term option.

    Thank You

    Monday, June 13, 2011 11:47 AM

Answers

  • Hi Dman65,

    Thank you for your updates.

    To Windows 2003 64 bit server, the suggested session value as below:
    .SessionViewSize=104 MB
    .SessionPoolSize=64 MB
    .Interactive desktop heap size=20480 KB
    .Non-interactive desktop heap size =768 KB

    To fix your issue, please follow steps below:
    1. backup your registry first
    2. change SessionPoolSize value to 64 Decimal under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management
    3. reboot your server
    4. If the issue reoccur, change Interactive desktop heap size and Non-interactive desktop heap size to suggested value,
    change shared section from 1024,3072,512 to 1024,20480,768, under HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\SubSystems\Windows, please refer to Desktop Heap Overview, Desktop Heap part 2 articles for details.
    5. reboot your server

    If there are more inquiries on this issue, please feel free to let us know.


    Regards,
    Rick Tan
    Wednesday, June 22, 2011 3:32 AM
    Moderator

All replies

  • Hi,

    can you browse the CLSID and tell me which component is it pointing to

    the path is HKCR /Root

    Please do post the detailed event id with the hexa code. Also please do let us know when do you encounter this issue.
    Use procmon to verify the permissions on the hkcr/root and CLSID folder.

     

    Monday, June 13, 2011 2:14 PM
    Moderator
  • I am not certain what the information below will tell you. These are all custom components that our client applications call to retrieve data. I checked and rechecked the permissions and everything is fine.

    One thing I need to make clear is that these components do start and work correctly except for certain periods of time when they post these errors. After about 5 to 10 minutes, they no longer generate these errors and no changes are made to the system to get them working, they just start working again by themselves. Rebooting the server will result in none of these errors being generated for about 20 hours, and then they will start again.

     

    Event Type:    Error
    Event Source:    DCOM
    Event Category:    None
    Event ID:    10010
    Date:        6/9/2011
    Time:        3:02:36 PM
    User:        N/A
    Computer:    FLEX1
    Description:
    The server {CC579335-BB2F-11D4-BE90-00A0CC21C880} did not register with DCOM within the required timeout.For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


    {72E10212-2AF4-11D7-BF40-00A0CC21C880}= srvrDentSummary.srvSummary

    {CC579335-BB2F-11D4-BE90-00A0CC21C880} = srvrCompanyData.OldCompServ

    {ACE92661-89D5-11D6-BF29-00A0CC21C880} = srvrQueryArraySpec.srvQueryArray

    {840C513A-1F51-11D7-BF3F-00A0CC21C880} = srvrDirectH.srvPlan

    {F32295EB-306D-44CB-A265-1550FF19066E}= srvrF247.srvF247

    {A9315077-AEA9-472A-A8D3-C92D73E4EFBB} = srvrSysReq.srvSysReq

    {B2E94C53-CA61-11D2-BE1C-00A0CC21C880} = srvOldComp.OldCompServ

    {35314A9A-AD91-11D3-BE5C-00A0CC21C880} = srvrDD01Employee.srvParticipation

    {840C50E8-1F51-11D7-BF3F-00A0CC21C880}= srvrHPlanA.srvHCodes

    {840C4FDB-1F51-11D7-BF3F-00A0CC21C880} = srvrVE.srvParticipation

    {840C513A-1F51-11D7-BF3F-00A0CC21C880} = srvrDirectH.srvPlan

     

     

    Monday, June 13, 2011 8:04 PM
  • Hi Dman65,

    Thank you for your post.

    Please backup your registry first and change the SessionViewSize value to 100 Decimal.
    The SessionViewSize registry entry is located under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management

    If there are more inquiries on this issue, please feel free to let us know.


    Regards,
    Rick Tan
    Friday, June 17, 2011 3:32 AM
    Moderator
  • I made the changes, but I am still getting these errors. I rebooted the machine this morning at 7:20AM Eastern, and at 2:54PM eastern this error was recorded in the system log:

     

    Event Type:    Warning
    Event Source:    Win32k
    Event Category:    None
    Event ID:    243
    Date:        6/21/2011
    Time:        2:54:14 PM
    User:        N/A
    Computer:    FLEX1
    Description:
    A desktop heap allocation failed.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 00 00 00 00 01 00 56 00   ......V.
    0008: 00 00 00 00 f3 00 00 80   ....ó..€
    0010: 00 00 00 00 00 00 00 00   ........
    0018: 00 00 00 00 00 00 00 00   ........
    0020: 00 00 00 00 00 00 00 00   ........

    -----------------------------------------------------------------

    After that point there are several sporadic occurences of the 10010 error.

     

    This is running on a Windows 2003 64 bit server with 32GB RAM. Do I need to make the SessionViewSize larger? There is no point in time where the amount of memory used is climbing to any where near the maximum.

    Tuesday, June 21, 2011 7:48 PM
  • Hi Dman65,

    Thank you for your updates.

    To Windows 2003 64 bit server, the suggested session value as below:
    .SessionViewSize=104 MB
    .SessionPoolSize=64 MB
    .Interactive desktop heap size=20480 KB
    .Non-interactive desktop heap size =768 KB

    To fix your issue, please follow steps below:
    1. backup your registry first
    2. change SessionPoolSize value to 64 Decimal under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management
    3. reboot your server
    4. If the issue reoccur, change Interactive desktop heap size and Non-interactive desktop heap size to suggested value,
    change shared section from 1024,3072,512 to 1024,20480,768, under HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\SubSystems\Windows, please refer to Desktop Heap Overview, Desktop Heap part 2 articles for details.
    5. reboot your server

    If there are more inquiries on this issue, please feel free to let us know.


    Regards,
    Rick Tan
    Wednesday, June 22, 2011 3:32 AM
    Moderator