COM+ Event ID: 4768
Event Type: Error
Event Source: COM+
Event Category: Unknown Event
ID: 4786
Description: 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 them with the information below.
Method Name: IObjectControl::Deactivate()
Exception: E0434F4D
Address: 0x77E649D3
Call Stack:
kernel32!RaiseException + 0x48
mscorsvr!CoEEShutDownCOM + 0xe448
mscorsvr!CoEEShutDownCOM + 0xe3cb
mscorsvr!CoEEShutDownCOM + 0xe37f
mscorsvr!CoEEShutDownCOM + 0xe322
mscorsvr!GetMetaDataPublicInterfaceFromInternal + 0x26ef
mscorsvr!CoEEShutDownCOM + 0x15eae
mscorsvr!ReleaseFusionInterfaces + 0x1d2fa
comsvcs!RegisterComEvents + 0x3f074
comsvcs!RegisterComEvents + 0x40146
ole32!ReadStringStream + 0x22057
ole32!CreateDataAdviseHolder + 0x1534
ole32!CoQueryAuthenticationServices + 0xf5f
ole32!CoQueryAuthenticationServices + 0x1b06
ole32!CoQueryAuthenticationServices + 0x2236
Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Description: Faulting application w3wp.exe, version 6.0.3790.1830, faulting module kernel32.dll, version 5.2.3790.2756, fault address 0x00015e02. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data: 0000: 41 70 70 6c 69 63 61 74 Applicat 0008: 69 6f 6e 20 46 61 69 6c ion Fail 0010: 75 72 65 20 20 77 33 77 ure w3w 0018: 70 2e 65 78 65 20 36 2e p.exe 6. 0020: 30 2e 33 37 39 30 2e 31 0.3790.1 0028: 38 33 30 20 69 6e 20 6b 830 in k 0030: 65 72 6e 65 6c 33 32 2e ernel32. 0038: 64 6c 6c 20 35 2e 32 2e dll 5.2. 0040: 33 37 39 30 2e 32 37 35 3790.275 0048: 36 20 61 74 20 6f 66 66 6 at off 0050: 73 65 74 20 30 30 30 31 set 0001 0058: 35 65 30 32 5e02

Back to the top

• Analyze dump files of the process that were taken when you experience the underlying delay.
• Run the application under a profiler utility.
• Use logging throughout the application.

• Use the executionTimeout setting.
• Use the Server.ScriptTimeout property.

Back to the top

Steps to reproduce the problem

1. Follow the steps in Microsoft Knowledge Base article 306296 to create a simple ServicedComponent class and then install the class into COM+. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
   306296  (http://kbalertz.com/Feedback.aspx?kbNumber=306296/ ) How to create a serviced .NET component in Visual C# .NET
2. Add the following code example to the ServicedComponent class.

   protected override void Activate()
   {
   	// Sleep for 100 seconds.
   	// (The default ASP.NET time-out is 90 seconds.)
   	System.Threading.Thread.Sleep(1000*100);
   }
   

3. Create a Web application in Microsoft Visual C#. To do this, follow these steps:
   1. Start Microsoft Visual Studio .NET.
   2. On the File menu, point to New, and then click Project.
   3. In the New Project dialog box, click Visual C# Projects under Project Types, and then click ASP.NET Web Application under Templates.
   4. In the Location box, type http://localhost/TestWeb1.
   5. Click OK to create the project. WebForm1.aspx is added to your project.
4. In Solution Explorer, right-click TestWeb1, and then click Add Reference.
5. In the Add Reference dialog box, click Browse.
6. In the Select Component dialog box, select the DLL that contains the ServicedComponent-derived class that you generated in step 1.
7. In Solution Explorer, right-click WebForm1.aspx, and then click View Code.
8. Add the following code example to the Page_Load event procedure.

   // Create an instance of the ServicedComponent-derived class.
   // Note: Change the namespace and the class name as appropriate.
   MyNamespace.MyServicedComponent sc = new MyNamespace.MyServicedComponent();
   
   // Call any method on this object to cause the Activate method to occur.
   sc.DoTrans();
   

9. Use a stress test utility to test the http://localhost/TestWeb1/WebForm1.aspx page. For example, follow the steps that are listed in the following Microsoft Knowledge Base article:
   815161  (http://kbalertz.com/Feedback.aspx?kbNumber=815161/ ) How to measure ASP.NET responsiveness with the Web Application Stress Tool

Back to the top