November 15, 2005 at 10:51 am
We have a problem on one of our servers where by MSDTC keeps stopping unexpectidly usually during the night.
The Windows event log has the following error, but I can't find anything on google
The MS DTC Transaction Manager is in an inconsistent state and cannot proceed. Please contact Microsoft Product Support. (null)
File: .\tmtx.cpp, Line: 2570.
Any help appreciated.
Thanks Jeet
November 15, 2005 at 10:58 am
What machine is it?
Does it has all patches?
Did occur it suddenly? If so any clue what has changed? (network, new machines...)
November 16, 2005 at 3:41 am
Is it happening every night, or ?? At the same time ???
There is nothing in the system log ??
Does any program stop due to backup at the same time ??
November 16, 2005 at 3:44 am
We are Running sql server 2000 (version 8.00.2039, SP4) on a windows server 2000 machine.
This box has not changed at all, and there are no network changes that I am aware of. It started about 3 weeks ago and happens every few days.
Thanks Jeet
November 21, 2005 at 2:50 am
Hello
We do have the same Problem.
We think it might have something to do with one of the october microsoft security updates.
But we are still looking for a solution.
Regards Andreas
Regards Andreas Rullmann
December 15, 2005 at 6:26 am
December 19, 2005 at 10:11 am
Did you ever get this resolved?
We are experiencing the same effect here.
January 30, 2006 at 7:57 am
Same here. Anybody could resolve this?
Otherwise we'll uninstall the security-patch regarding MSDTC..
February 13, 2006 at 6:21 pm
Hi,
we are having the same problem couple of times. Did anyone manage to get rid of it? Or did unistalling the security patch solved the problem?
February 14, 2006 at 12:20 am
Microsoft has a KB article for this error message.
http://support.microsoft.com/?id=912816
As per KB
This problem occurs after you install the cumulative security update that is referenced in the following Microsoft Knowledge Base article:
=> You can call Microsoft PSS and get hotfix.
April 27, 2006 at 4:25 am
Uninstalling the security patch solved the problem..
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply