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.
Server Application ID: {02D4B3F1-FD88-11D1-960D-00805FC79235}
Server Application Instance ID:{<ID>}
Server Application Name: System Application
Error Code = 0x8004d01b : The Transaction Manager is not available.
COM+ Services Internals Information:
File: d:\qxp_slp\com\com1x\src\comsvcs\txprop\dtcinfo.cp p, Line: 164
Comsvcs.dll file version: ENU 2001.12.4414.258 shp
This problem can appear after installing SP2 on Windows XP. See the link to “www.pcbanter.net - COM + Error after installing SP2“, for information on registering MSDTC and IIS packages. There is also an MS KB article, ME315296 on how to rebuild a damaged COM+ catalog.
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.
Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.