FIX: You may receive an "E_INVALIDARG" error message when you try to create an instance of a .NET serviced component

When you try to create an instance of a Microsoft .NET serviced component that is deployed in the COM+ environment, you may receive the following error message: This error message is returned by the activation request.

When you try to create an instance of a new serviced component, an old instance of the serviced component is destroyed. COM+ is supposed to clean up all the other resources that are associated with the old serviced component. However, sometimes this destruction may not be successful, or COM+ may not clean up the associated resources. Therefore, COM+ does not create the instance of the serviced component, and you may receive the error message that is mentioned in the "Symptoms" section.

To resolve this problem, obtain the latest service pack for the Microsoft .NET Framework 1.1. The following file is available for download from the Microsoft Download Center:

The Microsoft .NET Framework 1.1 Service Pack 1

Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

1. Click Start, click Run, type regedit, and then click OK.
2. In Registry Editor, create the following registry subkey:
   
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\COM3\System.EnterpriseServices
3. Add a value to the registry key that you created in step 2. To do this, follow these steps:
   1. On the Edit menu, point to New, and then click DWORD Value.
   2. In the right pane of Registry Editor, replace the selected text with DisableAsyncFinalization under the Name column, and then press ENTER.
   3. On the Edit menu, click Modify.
      
      The Edit DWORD Value dialog box appears.
   4. In the Value data box, replace the existing text with 00000001, and then click OK.
4. On the File menu, click Exit to close Registry Editor.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

This problem was first corrected in the Microsoft .NET Framework 1.1 Service Pack 1.

For additional information, click the following article number to view the article in the Microsoft Knowledge Base: