COM+ crashes after SP3 Installation

[apexinternet]

After installing Service Pack 3 . com+ crashes... this is the log:

eventviewer:

The COM+ Event System detected a bad return code during its internal processing. HRESULT was 80070002 from line 536 of .\notify.cpp. Please contact Microsoft Product Support Services to report this error.

The COM+ Event System detected a corrupt IEventSubscription object. The COM+ Event System has removed object ID {71EDA56F-317A-11D2-98A9-00C04F8EE1C4}. The subscriber will no longer be notified when the event occurs.

com+ log:

===================== COM+ =====================
Time: 8/20/2002 19:28:35.328
Type: Error
Category: Executive
Event ID: 4099
The run-time environment was unable to initialize for transactions required to support transactional components. Make sure that MS DTC is running.(DtcGetTransactionManagerEx(): hr = 0x8004d01b)

com+ setup log:

COM+[7:41:10]: ********************************************************************************
COM+[7:41:10]: Setup started - [DATE:08,20,2002 TIME: 07:41 pm]
COM+[7:41:10]: ********************************************************************************
COM+[7:41:10]: Start OC_INIT_COMPONENT Component = com
COM+[7:41:10]: INF VERSION (com) = 1999,9,3422,5
COM+[7:41:10]: Instantiating CMasterNT5Srv
COM+[7:41:10]: Memory usage for setup process...
COM+[7:41:10]: PeakWorkingSetSize: 35680 Kb, WorkingSetSize: 31196 Kb
COM+[7:41:10]: QuotaPeakPagedPoolUsage: 41 Kb, QuotaPagedPoolUsage: 40 Kb
COM+[7:41:10]: PeakPagefileUsage: 34264 Kb, PagefileUsage: 28456 Kb
COM+[7:41:10]: MTSS: Answer File =
COM+[7:41:10]: Calling SetupOpenInfFile.
COM+[7:41:10]: Unable to open Answer File!!
COM+[7:41:10]: DRID-39104 -> Path: C:\WINNT\java\trustlibCOM+[7:41:10]: Installed COM product version = 3.0.0.3421
COM+[7:41:10]: SETUP VERSION = 3.0.0.3421
COM+[7:41:10]: Installation Mode = MAINTENANCE
COM+[7:41:10]: Maintnenance Mode = ADD_REMOVE
COM+[7:41:10]: DRID-39103 -> Path: C:\Program Files\Common Files\ODBC\Data SourcesCOM+[7:41:10]: End OC_INIT_COMPONENT Return Value = 0
COM+[7:41:10]: Start OC_INIT_COMPONENT Component = dtc
COM+[7:41:10]: INF VERSION (dtc) = 1999,9,3421,0
COM+[7:41:10]: Installed DTC product version = 3.0.0.3421
COM+[7:41:10]: DTC Installation Mode = MAINTENANCE
COM+[7:41:10]: DTC Maintnenance Mode = ADD_REMOVE
COM+[7:41:10]: End OC_INIT_COMPONENT Return Value = 0
COM+[7:41:12]: Start OC_QUERY_STATEComponent = dtc Subcomponent = dtc
COM+[7:41:12]: Subcomponent dtc state: O-,C-,R+
COM+[7:41:12]: End OC_QUERY_STATE Return Value = 0
COM+[7:41:12]: Start OC_QUERY_STATEComponent = com Subcomponent = com
COM+[7:41:12]: Subcomponent com state: O-,C-,R+
COM+[7:41:12]: End OC_QUERY_STATE Return Value = 0
COM+[7:41:13]: Start OC_CLEANUP Component = com
COM+[7:41:13]: COM+ was not installed
COM+[7:41:13]: Memory usage for setup process...
COM+[7:41:13]: PeakWorkingSetSize: 42016 Kb, WorkingSetSize: 35484 Kb
COM+[7:41:13]: QuotaPeakPagedPoolUsage: 70 Kb, QuotaPagedPoolUsage: 59 Kb
COM+[7:41:13]: PeakPagefileUsage: 34264 Kb, PagefileUsage: 25812 Kb
COM+[7:41:13]: End OC_CLEANUP Return Value = 0
COM+[7:41:13]: Start OC_CLEANUP Component = dtc
COM+[7:41:13]: End OC_CLEANUP Return Value = 0
COM+[7:41:52]: ********************************************************************************
COM+[7:41:52]: Setup finished - [DATE:08,20,2002 TIME: 07:41 pm]
COM+[7:41:52]: ********************************************************************************

 

[wolfpack1993]

We have the same problem. Anybody have a solution?

 

[XtX]

Me too!!!
Anyone was able to solve this problem??
Please, desperate help!

 

[projekt01]

I have also the same Problem does has anybody a solution?

 

[NoDuff]

I am having the same Warning running under Win2K Adv. Serv. SP3. I have found this link

http://www.eventid.net/display.asp?eventid=4106&source=

that seems to address it, but I HAVE NOT given it a shot. My system seems to be running fine other than that so I don't want to risk $%&#ing it up! If anyone has any luck please let me know.

 

[mikethefixer]

I have run into this issue after installing SP4. Has anyone come across a solution that does not involve deleting registry keys?

Thanks....