PDA

View Full Version : Re: COM + Error after installing SP2


Trevor Miller
September 14th 04, 01:56 PM
I tried the reinstall of msdtc however now I am getting the following

When I try to expand theMy Computer node its pops up with
An Error occurred while processing the last operation
Error code 8004E00F - COM+ was unable to talk to the Microsoft Distributed
Transaction Coordinator

The event log has two notable events for this
--------------------------------------------------------
Event Type: Error
Event Source: COM+
Event Category: (98)
Event ID: 4691
Date: 9/14/2004
Time: 10:18:59 AM
User: N/A
Computer: TMILLER
Description:
The run-time environment was unable to initialize for transactions required
to support transactional components. Make sure that MS-DTC is running.
(DtcGetTransactionManagerEx(): hr = 0x8004d027)
-------------------------------------------------------------------------------


AND

-------------------------------------------------------------------------------
Event Type: Error
Event Source: MSDTC Client
Event Category: MSDTC Proxy
Event ID: 4427
Date: 9/14/2004
Time: 10:19:00 AM
User: N/A
Computer: TMILLER
Description:
Failed to initialize the needed name objects. Error Specifics:
d:\qxp_slp\com\com1x\dtc\dtc\msdtcprx\src\dtcinit. cpp:215, CmdLine:
C:\WINDOWS\system32\dllhost.exe
/Processid:{02D4B3F1-FD88-11D1-960D-00805FC79235}, Pid: 3636
No Callstack (0)

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 05 40 00 80 .@.€
-------------------------------------------------------------------------

So once this happened I tried "Microsoft Knowledge
Base Article - 315296" to clean 'Clean Up a Damaged COM+ Catalog' but that
did not make any change. I will go research these new errors to hopefully
get somewhere with this.


Trev





"John" > wrote in message
om...
>> TransactionManager->GetWhereabouts failed. If Distributed Transaction
>> Coordinator is configured to use remote host to coordinate transactions,
>> it
>> is likely that remote host cannot be contacted. You can configure MSDTC
>> to
>> use local coordinator by clicking MSDTC toolbar button in Component
>> Services
>> MMC snap-in. Since further execution is impossible at this time, server
>> process has been terminated.
>
> This worked for me:
>
> cd %systemroot%\system32
> msdtc -uninstall
> msdtc -install
>
> If this does not work try performing the steps in "Microsoft Knowledge
> Base Article - 315296" to clean 'Clean Up a Damaged COM+ Catalog' and
> then do the step above again. I don't think 315296 actually helped
> fix the problem; but I can't say for sure since I did do 315296 before
> doing the steps above. Therefore, try just the steps above first. If
> you do perform 315296, the following may apply: If "IIS In-Process
> Applications" and "IIS Out-Of-Process Pooled Applications" do not
> appear in the "COM+ Applications" folder of the Component Manager:
>
> cd %systemroot%\system32\inetsrv
> rundll32 wamreg.dll, CreateIISPackage

Trevor Miller
September 14th 04, 02:08 PM
Okay I got it working. Once I reinstalled COM+ and came across the other
errors I couldnt get anywhere. I tried to reintall msdtc again and all
appears to be fine. So I guess the logical path needed was to reintall COM
+ as per KB315296 then reinstall msdtc.

Thanks all


"John" > wrote in message
om...
>> TransactionManager->GetWhereabouts failed. If Distributed Transaction
>> Coordinator is configured to use remote host to coordinate transactions,
>> it
>> is likely that remote host cannot be contacted. You can configure MSDTC
>> to
>> use local coordinator by clicking MSDTC toolbar button in Component
>> Services
>> MMC snap-in. Since further execution is impossible at this time, server
>> process has been terminated.
>
> This worked for me:
>
> cd %systemroot%\system32
> msdtc -uninstall
> msdtc -install
>
> If this does not work try performing the steps in "Microsoft Knowledge
> Base Article - 315296" to clean 'Clean Up a Damaged COM+ Catalog' and
> then do the step above again. I don't think 315296 actually helped
> fix the problem; but I can't say for sure since I did do 315296 before
> doing the steps above. Therefore, try just the steps above first. If
> you do perform 315296, the following may apply: If "IIS In-Process
> Applications" and "IIS Out-Of-Process Pooled Applications" do not
> appear in the "COM+ Applications" folder of the Component Manager:
>
> cd %systemroot%\system32\inetsrv
> rundll32 wamreg.dll, CreateIISPackage

Google