| Event Id | 4197 |
| Source | MSDTC |
| Description | i> Could not locate the MS DTC XA Transaction Manager contact object. ii>An address could not bind to a socket. Make sure the TCP/IP stack is installed and running properly. This event might mean that the 'nameserver' port (specified in the services file) which is used as the default by WINS for replication and discovering other WINSs has been taken by another process or service running on this computer. You have two options - either bring down that other process or service or direct WINS to use another port. If you choose the second option, set the value 'PortNo' (REG_DWORD) under the Wins\Parameters subkey in the registry to 1512. NOTE: Changing the port number this way will prevent this WINS from replicating or discovering other WINSs unless they too are directed to use the same port number as this WINS. |
| Event Information | According to Microsoft : Cause : This event record might mean that the "nameserver" port (specified in the services file) used as a default by WINS for replication and discovering other Windows Internet Name Services has been taken by another process or service running on this computer. Resolution : You have two options for solving this problem; either bring down the other process or service, or direct WINS to use another port. If you choose the second option, set the value of PortNo (REG_DWORD) in the Wins\Parameters key to 1512. Note: Changing the port number this way will prevent this WINS server from replicating or discovering other Windows Internet Name Services unless they too are directed to use the same port number. According to News Group: ------------------------------------------------------------------------------ I got this error when trying to start the DTC service. I finally resolved the problem be uninstalling and reinstalling the msdtc. ------------------------------------------------------------------------------ This hotfix corrects several problems that may occur when you use Microsoft SQL Server with an XA-compliant transaction manager such as BEAs Tuxedo. These problems only occur when the transaction manager performs distributed transactions with Microsoft SQL Server using the XA protocol. Under some circumstances Microsoft DTC returns the error XAERR_NOTA (no transaction). The Microsoft DTC transaction manager process may also leak memory when Tuxedo performs XA transactions with Microsoft SQL Server. ------------------------------------------------------------------------------ |
| Reference Links | FIX: Memory Leak When Using XA TM and SQL Server/DTC INFO: Oracle TRC Files and MTS Event id 4197 from MSDTC |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.