Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
MS DTC is unable to communicate with MS DTC on a remote system. No common RPC protocol is supported between the two systems. Please ensure that one or more of the following RPC protocols are common to both systems: TCP/IP, SPX, or NetBEUI. Error Specifics: .\iomgrclt.cpp:203, CmdLine: C:\WINNT\System32\msdtc.exe, Pid: <PID>.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is the role of the MSDTC service?
The solution to this problem is documented in Microsoft article ME817064.
After upgrading one of our SQL Server 2000 boxes to Windows 2003, this error occurred on another Windows 2000/SQL Server 2000 box. This occurred because there was a database link between the two SQL Servers. When the W2K/SQL2K box tried to talk back to the W2K3/SQL2K box, the application being used would hang and produce this error. By default, Windows 2003 has a few things disabled, simply enable them, and reboot. Go to Add/Remove Programs -> Windows Components -> Application Server -> Details. Here enable “Network COM+” and “Network DTC Access”. Reboot and the problem should disappear.
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated