Event ID 10001 — COM General Functionality

Event ID 10001 — COM General Functionality

Updated: February 22, 2008

Applies To: Windows Server 2008

COM+ applications use Microsoft Component Object Model (COM) technology in Microsoft Windows operating systems to communicate and take advantage of Windows services. COM technologies include COM+, DCOM, and ActiveX Controls.

Event Details

Product: Windows Operating System
ID: 10001
Source: Microsoft-Windows-DistributedCOM
Version: 6.0
Symbolic Name: EVENT_RPCSS_RUNAS_CREATEPROCESS_FAILURE
Message: Unable to start a DCOM server: %3 as %4/%5. The error:”%2″ happened while starting this command:%1

Resolve
Correct the low-resource condition or report the error to Microsoft

There is a problem with the COM service. However, there is not enough information available in the event message to provide a definitive recommendation to resolve the problem. The following steps may help to resolve the problem:

  • You may be able to resolve the problem by reinstalling the application to restore a missing file.
  • Check the system for a low-resource condition.
  • You can resolve a low-resource condition by increasing the page file size. A page file is a hidden file or files on the hard disk that the operating system uses to hold parts of programs and data files that do not fit in memory. Virtual memory comprises the paging file and physical memory or random access memory (RAM). Windows moves data from the paging file to memory as needed, and it moves data from memory to the paging file to make room for new data. Increasing the page file size usually does not require a restart of the computer.
  • You may be able to resolve a low-resource condition by ending unnecessary processes to free memory resources. Be careful when you end a process. If you end a process that is associated with an open program, the program will close and you will lose unsaved data. If you end a process that is associated with a system service, part of the system might not function properly.

If you continue to get this error, note any details in the event message, and then contact Microsoft Customer Service and Support (CSS). For information about how to contact CSS, see Enterprise Support (http://go.microsoft.com/fwlink/?LinkId=52267).

To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.

Check the system for a low-resource condition

To check the system for a low-resource condition:

  1. Right-click the taskbar, and then click Task Manager.
  2. Click the Performance tab, and look for the amount of physical memory used under Memory and Physical Memory Usage History. If the amount of memory used is high, consider increasing the size of the page file.

Increase the size of the page file

To increase the size of the page file:

  1. Click Start, click Control Panel, and then double-click System.
  2. Under Tasks, click Advanced System Settings. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. Click the Advanced tab. Under Performance, click Settings.
  4. In the Performance Options dialog box, click the Advanced tab.
  5. Under Virtual Memory, click Change.
  6. Clear the Automatically manage paging file size for all drives check box.
  7. Under Drive [Volume Label], click the drive that contains the paging file that you want to change.
  8. Click Custom size, type a new size in megabytes in the Initial size (MB) or Maximum size (MB) box, click Set, and then click OK.

Free memory to end a process

To free memory to end a process:

  1. Right-click the taskbar, and then click Task Manager.
  2. Click the Processes tab, and then click Show processes from all users (at the bottom). If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. Be careful when you end processes. If you end a process that is associated with an open program, the program will close and you will lose unsaved data. If you end a process that is associated with a system service, part of the system might not function properly.

    Try to identify processes that are leaking memory by looking for a process with unusually high memory consumption. Select a process to end, and then click End Process. For more information about how to identify a process that is leaking memory, see Using Performance Monitor to Identify a Pool Leak (http://go.microsoft.com/fwlink/?LinkId=105512).

For more information about RAM, virtual memory, and page file, see RAM, Virtual Memory, Pagefile and all that stuff (http://go.microsoft.com/fwlink/?LinkId=105511).

Verify

You can verify that your security policy for this server is configured properly by running the Component Services administrative tool and ensuring that the required security properties are set.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To open Component Services and verify that the required security properties are set:

  1. Click Start, and then click Run.
  2. Type comexp.msc, and then click OK. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. To locate your computer, click Component Services, click Computers, and then click My Computer.
  4. Right-click My Computer, and then click Properties.
  5. Click the COM Security tab, and confirm that the Access Permissions and Launch and Activition Permissions properties are set properly.

Related Management Information

COM General Functionality

Application Server

Related:

The managed folder assistant did not provision mailbox %1 because there is corrupt data in Active Directory. Exception details: %2.

Details
Product: Exchange
Event ID: 10001
Source: MSExchangeMailboxAssistants
Version: 8.0
Symbolic Name: InvalidElcDataInAD
Message: The managed folder assistant did not provision mailbox %1 because there is corrupt data in Active Directory. Exception details: %2.
   
Explanation

This Error event indicates that the managed folder mailbox assistant (formerly known as e-mail life cycle assistant) could not retrieve managed folder mailbox policy information (formerly known as E-Mail Life Cycle Policy data) from the Active Directory® directory service to provision the mailbox specified in the event description. The managed folder mailbox assistant is a time-based Exchange assistant that provisions the managed default folders and managed custom folders in user mailboxes on scheduled intervals.

For more information about managed folders, managed content settings, managed folder mailbox policies, and managed folder assistant, see Deploying Messaging Records Management.

The managed folder mailbox assistant uses the managed folder mailbox policy information to either set the content status to expired or copy the content of a managed folder to a different folder. This event may occur when managed folder mailbox policy information in Active Directory has been corrupted or is invalid.

   
User Action

To resolve this error, take one or more of the following steps:

  • Re-configure the managed folder mailbox policy for the mailbox specified in the event description. For detailed instructions, see How to Create a Managed Folder Mailbox Policy.

  • Restart Microsoft Exchange Mailbox Assistants service by using Services snap-in.

If this error frequently occurs, contact Microsoft Product Support Services. For information, visit the Microsoft Help and Support Web site.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related:

Unable to start a DCOM Server: %3 as %4/%5. The error: “%%%2” Happened while starting this command:%1

Details
Product: Windows Operating System
Event ID: 10001
Source: DCOM
Version: 5.0
Component: System Event Log
Symbolic Name: EVENT_RPCSS_RUNAS_CREATEPROCESS_FAILURE
Message: Unable to start a DCOM Server: %3 as %4/%5. The error: “%%%2” Happened while starting this command:%1
   
Explanation

The Component Object Model (COM) infrastructure could not activate the requested server. Possible causes include:

  • There is not enough memory available
  • An error occurred with another file that the COM infrastructure depends on.
       
    User Action

    Review the Windows error code displayed in the message. If the error indicates that the system is out of memory, save your work, close other programs, and then try to start the service again. Alternatively, increase the amount of RAM installed on the computer.

    If the message displays a system, server, or configuration error, contact your service support vendor.

    To determine the service vendor

    1. Click Start, and then click My Computer.
    2. Using the executable file name displayed in the message after ‘command:,’ navigate to the program.
    3. Right-click the program name, and then click Properties.
      The Properties dialog box for the program is displayed.
    4. To determine who the vendor is for this service, refer to the Version tab.You can also find the path to the executable file in this tool.

    Related:

    Poison Count is %1 for the message with RecordID %2. The message has reached or exceeded the configured poison threshold of %3. After the Microsoft Exchange Transport service restarted, the message was moved to the poison message queue.

    Details
    Product: Exchange
    Event ID: 10001
    Source: MSExchangeTransport
    Version: 8.0
    Symbolic Name: MessageEnqueuedToPoisonQueue
    Message: Poison Count is %1 for the message with RecordID %2. The message has reached or exceeded the configured poison threshold of %3. After the Microsoft Exchange Transport service restarted, the message was moved to the poison message queue.
       
    Explanation

    This Warning event indicates that the transport process detected a message that could harm a Microsoft® Exchange environment. That message was moved to the poison message queue.

    The poison message queue is a persistent queue that isolates messages that are detected as potentially fatal to a computer that is running Exchange Server 2007. This queue is typically empty. If no such messages exist in the poison message queue, the queue does not appear in the queue viewing interfaces. For information about how to manage queues, see Managing the Queue Database.

       
    User Action

    No user action is required. However, we recommend that you contact Microsoft Product Support to report the potentially harmful message that Exchange detected. For more information about how to contact support, visit the Microsoft Help and Support Web site.

    Note   Do not delete the poison message from the poison queue. Microsoft Product Support Services may have to examine the message.

    If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

    Related: