Export (0) Print
Expand All
Expand Minimize

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.

Events

Event ID Source Message

771

Microsoft-Windows-Complus

A new CRM log file was created. This CRM log file is not secure because the application Identity is Interactive User or the file system is not NTFS. %1%0

772

Microsoft-Windows-Complus

A new Compensating Resource Manager (CRM) log file was created. This CRM log file is secure. %1%0

773

Microsoft-Windows-Complus

A new Compensating Resource Manager (CRM) log file was created for the System Application.%0

774

Microsoft-Windows-Complus

The mtstocom launching routine has started.%1%0

775

Microsoft-Windows-Complus

The mtstocom launching routine has completed.%1%0

776

Microsoft-Windows-Complus

The MTSTOCOM migration utility is attempting to retry populating the packages collection because it failed its first attempt.%1%0

777

Microsoft-Windows-Complus

Application image succesfully dumped.%1%0

778

Microsoft-Windows-Complus

Application image dump failed.%1%0

779

Microsoft-Windows-Complus

Microsoft Message Queuing (MSMQ) Workgroup configuration does not provide sender identity for a COM+ application that has security enabled. The usage is accepted.%1%0

780

Microsoft-Windows-Complus

Microsoft Message Queuing (MSMQ) Message Authentication is disabled for a COM+ application that has security enabled. The usage is accepted.%1%0

781

Microsoft-Windows-Complus

The COM+ sub system is suppressing duplicate event log entries for a duration of %1 seconds. The suppression timeout can be controlled by a REG_DWORD value named %2 under the following registry key: HKLM\%3.

782

Microsoft-Windows-Complus

The average call duration has exceeded the configured threshold.%1%0

783

Microsoft-Windows-Complus

The average call duration has exceeded 10 minutes. If this is not the expected behavior, please see article 910904 in the Microsoft Knowledge Base at http://support.microsoft.com for details on how to use the COM+ AutoDump feature to automatically generate dump files and/or terminate the process if the problem occurs again.%1%0

4433

Microsoft-Windows-Complus

An error occurred in a COM+ component. %1%0

4434

Microsoft-Windows-Complus

A method call to an object in a COM+ application was rejected because the caller is not properly authorized to make this call. The COM+ application is configured to use Application and Component level access checks, and enforcement of these checks is currently enabled. The remainder of this message provides information about the component method that the caller attempted to invoke and the identity of the caller.%1%0

4435

Microsoft-Windows-Complus

A method call to an object in a COM+ application was rejected because the caller is not properly authorized to make this call. The COM+ application is configured to use Application and Component level access checks, and enforcement of these checks is currently enabled. Information about the component method that the caller attempted to invoke and about the identity of the caller could not be obtained, probably due to low memory conditions on this computer.%0

4440

Microsoft-Windows-Complus

The Compensating Resource Manager (CRM) log file was originally created on a computer with a different name. It has been updated with the name of the current computer. If this warning appears when the computer name has been changed, no further action is required. %1%0

4441

Microsoft-Windows-Complus

The Compensating Resource Manager (CRM) log file was originally created with a different application ID. It has been updated with the current application ID. If this warning appears when the CRM log file has been renamed, no further action is required. %1%0

4444

Microsoft-Windows-Complus

An empty Compensating Resource Manager (CRM) log file was detected. It has been re-initialized. If this warning appears when the CRM log file is being initially created, no further action is required. %1%0

4445

Microsoft-Windows-Complus

An incompletely initialized Compensating Resource Manager (CRM) log file was detected. It has been re-initialized. If this warning appears when the CRM log file is being initially created, no further action is required. %1%0

4446

Microsoft-Windows-Complus

The application attempted to use the Compensating Resource Manager (CRM) but the CRM is not enabled for this application. You can correct this problem using the Component Services administrative tool. Display the Properties for your application. Select the Advanced tab and check Enable Compensating Resource Managers. The CRM can only be enabled for server applications. %1%0

4449

Microsoft-Windows-Complus

The system has called the Compensating Resource Manager (CRM) Compensator custom component and that component has failed and generated an exception. This indicates a problem with the CRM Compensator component. Notify the developer of the CRM Compensator component that this failure has occurred. The system will continue because the IgnoreCompensatorErrors registry flag is set, but correct compensation might not have occurred. %1%0

4450

Microsoft-Windows-Complus

The system has called the Compensating Resource Manager (CRM) Compensator custom component and that component has returned an error. This indicates a problem with the CRM Compensator component. Notify the developer of the CRM Compensator component that this failure has occurred. The system will continue because the IgnoreCompensatorErrors registry flag is set, but correct compensation might not have occurred. %1%0

4451

Microsoft-Windows-Complus

The Compensating Resource Manager (CRM) log file for this application is located on a disk which is low on space. This may cause failures of this application. Increase the space available on this disk. The CRM log file name is: %1%0

4453

Microsoft-Windows-Complus

Compensating Resource Manager (CRM) Worker custom components require a transaction. You can correct this problem using the Component Services administrative tool. Display the Properties for your CRM Worker component. Select the Transactions tab. Select the Transaction support Required option button.%1%0

4454

Microsoft-Windows-Complus

Event class failed Query Interface. Check the event log for any other errors from the EventSystem.%1%0

4455

Microsoft-Windows-Complus

Failed to create event class. Check the event log for any other errors from the EventSystem.%1%0

4456

Microsoft-Windows-Complus

Event class failed Query Interface. Check the event log for any other errors from the EventSystem.%1%0

4457

Microsoft-Windows-Complus

A previous instance of this server application has been terminated.%1%0

4458

Microsoft-Windows-Complus

During installation of this component into a COM+ application a registry value was changed from its original value. If you are experiencing activation problems with this component, check the registry values.%1%0

4459

Microsoft-Windows-Complus

Controlled registration of this component failed. It has been registered directly. If you are not using partitions you can ignore this warning. If you are using partitions you may need to add support components that are required before controlled registration of this component can succeed. Check your documentation for details.%1%0

4460

Microsoft-Windows-Complus

You have installed an application which contains one or more private components into the base partition. Private components are not supported in the base partition. The private components have been made public.%1%0

4462

Microsoft-Windows-Complus

The attempt to trace an event has failed with E_OUTOFMEMORY. This has happened a total of %1 times.%0

4463

Microsoft-Windows-Complus

During initialization, the System Application stopped an open COM+ tracing session. %0

4464

Microsoft-Windows-Complus

During controlled registration of this component the component cancelled registry redirection. This may cause problems with component installation. Check your documentation for details.%1%0

4465

Microsoft-Windows-Complus

The %0 component in application %1 has tried to retrieve the %2 property from the current object context, but the property was not found. This could have been caused by turning off the IISIntrinsics COM+ admin sdk property for this component, or its creator. See KBARTICLE for more details.

4689

Microsoft-Windows-Complus

The run-time environment has detected an inconsistency in its internal state. This indicates a potential instability in the process that could be caused by the custom components running in the COM+ application, the components they make use of, or other factors. %1%0

4690

Microsoft-Windows-Complus

The run-time environment has detected the absence of a critical resource and has caused the process that hosted it to terminate. %1%0

4698

Microsoft-Windows-Complus

Failed to create a stub object for given interface. %1%0

4729

Microsoft-Windows-Complus

The run-time environment was unable to create a new UUID. %1%0

4741

Microsoft-Windows-Complus

An attempt was made to access a Shared Property Manager (SPM) property Group in LockMethod mode, by an object without just-in-time (JIT) Activation, or by an object with a lock on another Property Group. %1%0

4767

Microsoft-Windows-Complus

The class ID of the proxy stub DLL for the interface is not available, or failed to load the proxy stub DLL, or failed to create a proxy.%0

4769

Microsoft-Windows-Complus

An unexpected error occurred. The failing function is listed below. The data section may have additional information.%1%0

4771

Microsoft-Windows-Complus

COM+ Queued Components failed to obtain necessary information from the catalog.%1%0

4772

Microsoft-Windows-Complus

The COM+ Queued Components Player was unable to create an instance of a Queued Component. %1%0

4786

Microsoft-Windows-Complus

The system has called a custom component and that component has failed and generated an exception. This indicates a problem with the custom component. Notify the developer of this component that a failure has occurred and provide the following information: %1%2%0

4789

Microsoft-Windows-Complus

The server was unable to determine if a queued message was sent by a trusted partner due to a lack of available memory. The sender is assumed to be untrusted. %1%0

4790

Microsoft-Windows-Complus

The server was unable to determine if a queued message was sent by a trusted partner due to an unexpected failure in a Windows API call. The sender is assumed to be untrusted. The failed API and corresponding error code: %1%0

4791

Microsoft-Windows-Complus

The COM+ Services DLL (Comsvcs.dll) was unable to load because allocation of thread local storage failed. %1%0

4792

Microsoft-Windows-Complus

The current registration database is corrupt. COM+ catalog has reverted to a previous version of the database. %1%0

4794

Microsoft-Windows-Complus

COM+ Services was unable to load a required string resource. The string resource identifier was not found. This results from an error in the localization process for this product and should be reported to Microsoft customer support. The binary data for this event contains the resource identifier that failed to load. %1%0

4796

Microsoft-Windows-Complus

COM+ Services was unable to obtain local security accounts manager (SAM) information. COM+ will continue to operate normally, but any calls between local and remote COM+ components will incur additional overhead. Error specifics: %1%0

4797

Microsoft-Windows-Complus

COM+ Services was unable to initialize due to a failure in the system API shown below. This is often caused by a shortage of system resources on the local machine.%1%0

4798

Microsoft-Windows-Complus

The system has called the Compensating Resource Manager (CRM) Compensator custom component and that component has failed and generated an exception. This indicates a problem with the CRM Compensator component. Notify the developer of the CRM Compensator component that this failure has occurred. %1%0

4800

Microsoft-Windows-Complus

COM+ Services was unable to authorize the incoming call due to an unexpected failure. The incoming call was denied and a "permission denied" error was returned to the caller. The unexpected error code is: %1%0

4801

Microsoft-Windows-Complus

COM+ Services was unable to determine the caller's identity because of an unexpected error. This may be caused by a shortage of system resources on the local machine. The caller will be treated as anonymous which may result in access failures or other errors. The name of the failed API and the error code that it returned are: %1%0

4802

Microsoft-Windows-Complus

COM+ Services was unable to process a component's call to IsCallerInRole due to an unexpected failure. The following unexpected error code was returned to the caller.%1%0

4803

Microsoft-Windows-Complus

The system has called the Compensating Resource Manager (CRM) Compensator custom component and that component has returned an error. This indicates a problem with the CRM Compensator component. Notify the developer of the CRM Compensator component that this failure has occurred. %1%0

4804

Microsoft-Windows-Complus

The system failed to create the Compensating Resource Manager (CRM) Compensator custom component. %1%0

4805

Microsoft-Windows-Complus

The system failed to create the Compensating Resource Manager (CRM) Compensator because the system is out of memory. %1%0

4806

Microsoft-Windows-Complus

The Queued Components Listener received an improperly formatted message.%1%0

4808

Microsoft-Windows-Complus

An unexpected error was returned by the Message Queuing API %1%0

4810

Microsoft-Windows-Complus

The server was unable to determine if a queued message was sent by a trusted partner due to an unexpected failure in a COM+ catalog component. The sender is assumed to be untrusted. The failed catalog API and corresponding error code are: %1%0

4818

Microsoft-Windows-Complus

The following component is configured for Construction, and either the IObjectConstruct::Construct() method failed, or the component does not support IObjectConstruct. Activation failed for object: %1%0

4819

Microsoft-Windows-Complus

Error creating security descriptor. %0

4820

Microsoft-Windows-Complus

Failed to initialize registration database server. %0

4821

Microsoft-Windows-Complus

Failed to initialize registration database API. %0

4822

Microsoft-Windows-Complus

A condition has occurred that indicates this COM+ application is in an unstable state or is not functioning correctly. Assertion Failure: %1%0

4823

Microsoft-Windows-Complus

COM Replication: an unexpected error occurred. The failing function is: %1%0

4825

Microsoft-Windows-Complus

Output arguments are not supported by queued methods. The data section contains the IID and method number.%1%0

4827

Microsoft-Windows-Complus

A COM+ service (such as Queued Components or Compensating Resource Manager) failed an ApplicationFree event. This is not a normal occurrence, but it is considered a non-critical error. The service GUID and HRESULT are: %1%0

4828

Microsoft-Windows-Complus

A COM+ service (such as Queued Components or Compensating Resource Manager) failed an ApplicationShutdown event. This is not a normal occurrence, but it is considered a non-critical error. The service GUID and HRESULT are: %1%0

4829

Microsoft-Windows-Complus

A COM+ service (such as Queued Components or Compensating Resource Manager) failed to start. The service GUID and HRESULT are: %1%0

4830

Microsoft-Windows-Complus

COM+ has determined that your machine is running very low on available memory. In order to ensure proper system behavior, the activation of the component has been refused. If this problem continues, either install more memory or increase the size of your paging file. Memory statistics are: %1%0

4831

Microsoft-Windows-Complus

COM+ failed an activation because the creation of a context property returned E_OUTOFMEMORY %1%0

4832

Microsoft-Windows-Complus

A request for a callback on a Microsoft Exchange Message Transfer Agent (MTA) thread failed. This should happen only if the system is in an extremely unstable state. It is possible that custom components running in this COM+ application caused the instability that led to this failure. %1%0

4833

Microsoft-Windows-Complus

The initialization of the COM+ surrogate failed -- the CApplication object failed to initialize.%1%0

4834

Microsoft-Windows-Complus

The shutdown process of COM+ surrogate failed because of an unknown ApplId. This is an unexpected error but is ignored because the application is in the process of shutting down.%1%0

4835

Microsoft-Windows-Complus

The Bring Your Own Transaction (BYOT) Gateway failed to import the transaction using Transaction Internet Protocol (TIP). Make sure that the installed Microsoft Distributed Coordinator (MS DTC) supports the TIP protocol. %1%0

4836

Microsoft-Windows-Complus

The Bring Your Own Transaction (BYOT) Gateway failed to create the component.%1%0

4837

Microsoft-Windows-Complus

The Bring Your Own Transaction (BYOT) Gateway could not set transactional property in new object context.%1%0

4840

Microsoft-Windows-Complus

The IObjectControl::Activate() method failed. The CLSID of the object is: %1%0

4844

Microsoft-Windows-Complus

COM+ Services was unable to initialize security infrastructure due to a failure in the system API shown below. This is often caused by a shortage of system resources on the local machine. No components requiring security infrastructure services will be created in this process. %1%0

4853

Microsoft-Windows-Complus

Unknown event ID. Please check the event log for any other errors from the EventSystem.%1%0

4854

Microsoft-Windows-Complus

Unable to instantiate Exception Class.%1%0

4859

Microsoft-Windows-Complus

Compensating Resource Manager (CRM) recovery has failed because Microsoft Distributed Transaction Coordinator (MS DTC) thinks that the previous instance of this application is still connected. This is a temporary condition that can occur if the system is too busy. Attempt the CRM recovery again by restarting this application.%1%0

4860

Microsoft-Windows-Complus

The Compensating Resource Manager (CRM) Compensator custom component has timed out out waiting for the CRM Worker custom component to complete. See the COM+ CRM documentation for further explanation of this error.%1%0

4861

Microsoft-Windows-Complus

Compensating Resource Manager (CRM) recovery has failed because the device is not ready. This is a temporary condition which can occur during cluster failover. Attempt the CRM recovery again by restarting this application.%1%0

4862

Microsoft-Windows-Complus

You have attempted to use COM+ Conversation support, and an error was generated accessing the database. You must specify a valid DSN in the construct string of the COMSvcs.Conversation component. For information on what a valid DSN is, see the documentation for the SQLDriverConnect API in MSDN or the Platform SDK. An example of a valid DSN is "DSN=Conversation".%0

4865

Microsoft-Windows-Complus

A COM+ service (such as Queued Components or Compensating Resource Manager) failed in its PauseProcess method. The service GUID and HRESULT are: %1%0

4866

Microsoft-Windows-Complus

A COM+ service (such as Queued Components or Compensating Resource Manager) failed in its ResumeProcess method. The service GUID and HRESULT are: %1%0

4867

Microsoft-Windows-Complus

The COM+ tracing GUIDs could not be registered. Tracing will be disabled.%0

4868

Microsoft-Windows-Complus

The COM+ tracing session failed to initialize. %1%0

4869

Microsoft-Windows-Complus

The COM+ event filter encountered an unexpected error. The system event will not be fired. %1%0

5377

Microsoft-Windows-Complus

An external error has been reported to COM+ services.%1%0

5378

Microsoft-Windows-Complus

An external error has been reported to COM+ services.%1%0

5379

Microsoft-Windows-Complus

The server process has lost its connection with Microsoft Distributed Transaction Coordinator (MS DTC) service. This is expected if MS DTC has stopped, or if MS DTC failover has occurred on a cluster.%1%0

5380

Microsoft-Windows-Complus

COM+ could not create a new thread due to a low memory situation.%1%0

5485

Microsoft-Windows-Complus

COM+ failed to find the correct partition for the admin SDK. The admin SDK will use the base partition. Check that users are configured into partitions correctly. See your documentation for details.%1%0

Related Management Information

COM+ Service

Application Server

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft