MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

Benjamin Mateos — Wed, 27 Apr 2005 00:45:59 GMT

Maybe a wrong registry entry set by SP1 ???

Interesting at least.

/r

Benji

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

Pims — Tue, 24 May 2005 23:42:36 GMT

Indeed, you helped me in a production environment. Thanks.

Pims

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

Spencer Steel — Thu, 02 Jun 2005 13:39:22 GMT

Thanks for that - I just came across this odd problem ... very odd that just opening and closing should sort it without changing anything !

Nice clean start-up now ... thanks !

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

Raffi C. — Fri, 10 Jun 2005 21:55:18 GMT

Same bug bit me too, and this strange procedure (like basically change nothing) resolved the problem.

Heart cheers to the original poster, jhoward!

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

Raffi C. — Fri, 10 Jun 2005 21:55:36 GMT

Same bug bit me too, and this strange procedure (like basically change nothing) resolved the problem.

Heart cheers to the original poster, jhoward!

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

Thilo — Tue, 14 Jun 2005 10:05:14 GMT

Great help, thank you.

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

pdc — Fri, 17 Jun 2005 03:24:16 GMT

I was expecting a step to sacrifice a chicken and stand on one leg.

However bizarre, it works.

Cheers!

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

Kenneth — Fri, 17 Jun 2005 22:04:04 GMT

I'm chalking this one up under wierd fixes. Thanks

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

Alan Florance — Thu, 23 Jun 2005 16:42:57 GMT

I have discovered the same problem and this appears to have corrected it.

Was this caused by changing the service permissions in SP1 ??

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

Mitchell — Thu, 23 Jun 2005 18:07:22 GMT

Thank you so much for such a simple fix.

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

jhoward — Thu, 23 Jun 2005 18:23:04 GMT

Alan (and the literally hundreds of others who have mailed me directly) - Glad the fix works for you too. I've had a dig around and can't find out _why_ this sequence makes a difference, or what the underlying cause is. If I find any more information though, or there's a hotfix made available, I'll obviously publish the info.
Cheers,
John.

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

Zeveck — Fri, 24 Jun 2005 17:20:34 GMT

Thanx!!

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

Steve — Wed, 06 Jul 2005 12:08:19 GMT

Just tried this fix on my DCs and the error came back on the next reboot. Was looking good for a while there.
Back to the drawing board for me!

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

JP — Mon, 11 Jul 2005 00:11:52 GMT

Worked for me in a fresh install too. Thanks for the quick and easy fix.

-JP

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

Armin — Tue, 19 Jul 2005 16:03:45 GMT

Thanks from germany. It works for me too.
Bye, Armin

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

saffi — Sun, 24 Jul 2005 16:33:52 GMT

I think it works because by clicking yes on the security tab you reset the security in a registry hive. Network service needs to make extra keys there (at least I read a fix with setting permissions on a hive). So if you troubleshoot, look for that...

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

saffi — Mon, 25 Jul 2005 17:27:08 GMT

See this:

Event ID: 53258
======================
CAUSE:
The Network Service account used to run MSDTC did not have permission to
update the HKLM\Software\Microsoft\MSDTC registry key.

RESOLUTION:
Either give this account Create Subkey and Set Value permissions on the key.

Event ID: 1097 & Event ID: 1030
======================

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

Alistair — Mon, 05 Sep 2005 12:34:20 GMT

Thanks. Worked for me

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

Yoshihao (retired MS Japan) — Wed, 07 Sep 2005 10:19:32 GMT

Thanks from Japan.

I think that - Microsoft support team must publish its case on KB. :(

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

Dave — Mon, 31 Oct 2005 05:46:22 GMT

Fantastic - this solved an issue for us in a production environment on our SMS 2003 server no less. Thank you very much. :)

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

Alex Silverberg — Wed, 16 Nov 2005 20:28:25 GMT

U have thanks from Japan and Germany and now thanks from Russia! Great help, thank you very much:)

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

sdb — Fri, 02 Dec 2005 23:49:04 GMT

Great stuff, adding your blog to my favorites! Thanks!

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

Michael — Sat, 17 Dec 2005 01:23:39 GMT

I was looking all over the Microsoft web site for a fix for this. Then I google’d it and found this web site. Thanks for it.. I suspected that the one of the settings in the MSDTC section in the registry was mangled after I installed something. Did a diff before and after this fix “NO DICE!”. After looking at the setting in that dialog. I would suspect that the built-in account displayed IN the dialog somehow gets reset. Looks like a bug Microsoft!

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

Paul — Sun, 08 Jan 2006 19:34:55 GMT

It's all good now, thanks a lot...

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

Jeff — Mon, 23 Jan 2006 18:02:11 GMT

Did you ever knoooow that your my heeeeroooo? ;)

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

Alain — Wed, 25 Jan 2006 17:39:00 GMT

And now Thanks from France !

I too hat the problem on a windows 2003 SP1, under Virtual Server 2005, and your trick solved the problem. I think it updated some security settings somewhere.

I had also userenv errors 1058 and 1030 "Can't access to gpt.ini file for policy {....}" and " stop applying strategy" which were solved in a similar manner : "change/restore polcy setting" and reboot ! No more errors.
See: http://www.eventid.net/display.asp?eventid=1058&eventno=1752&source=Userenv&phase=1

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

Paul Frazer — Sat, 04 Feb 2006 05:57:48 GMT

You Rock!! Thanks!!!

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

michael — Mon, 06 Feb 2006 21:15:39 GMT

Have the same problem in clustered configuration. Strange enough but MSDTC runs on the second node but when fails on the first node it blows up the whole cluster server on the first node, fails back to the second node and records 53258 in the log.

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

Marco — Tue, 28 Feb 2006 16:33:11 GMT

This works in my enviroment too! >Thanks!!!

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

Marcial Franco — Tue, 07 Mar 2006 22:00:43 GMT

Thanks from Spain (Santiago de Compostela)

;)

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

Stefan — Sat, 01 Apr 2006 23:03:53 GMT

for me again, after exchange 2003 installation with sp2 an removing that again it was there again, and by this way it went away again...

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

Stefan (Germany) — Wed, 03 May 2006 12:17:55 GMT

Thank you very much, it works !!

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

tom — Wed, 14 Jun 2006 19:58:27 GMT

Thanks a million, this worked in my production 2k3 server! :)

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

cbsilcor — Thu, 06 Jul 2006 10:54:59 GMT

Thanks a lot for this resolution, strange but effective, a million thanks

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

Mike F — Thu, 06 Jul 2006 16:22:10 GMT

Thanks!! This worked on one of my Win2003 production DC's! Awesome!

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

Boris — Fri, 07 Jul 2006 01:12:41 GMT

Your solution works fine. Thanks from Bolivia...

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

LEO — Wed, 12 Jul 2006 13:21:19 GMT

Thanks for Grate Your Help! From Japan--

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

Chris C — Wed, 26 Jul 2006 00:54:52 GMT

Don't know how you figured this out, but it worked like a charm. Thanks!

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

Beetowen — Wed, 09 Aug 2006 16:48:07 GMT

thx

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

jomiro — Thu, 17 Aug 2006 17:28:09 GMT

worked for me. thanks

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

Grzegorz — Thu, 24 Aug 2006 22:11:17 GMT

Thanks for that from Poland :-)

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

Helpme — Sat, 26 Aug 2006 22:56:32 GMT

Thanks for the straight-forward help. This type of help is far and few between... thanks again.

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

Gregg — Fri, 01 Sep 2006 17:07:41 GMT

That fixed my problem. The next Event id said "The CRM log file was originally created on a computer with a different name."
Sure enough I had changed the name of a DC and that's when it started.

Thanks!!!

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

andreaccs — Wed, 13 Sep 2006 11:43:34 GMT

on behalf of a customer of mine THANK YOU!!

Event Source:MSDTC Event ID: 53258. Just click Ok?

dfeuchter — Fri, 27 Apr 2007 11:27:25 GMT

I found a really nice Solution for an error on a Domain Controller the Error entry is: Event Type: Warning

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

Wafi Aljunedi — Wed, 12 Mar 2008 11:57:55 GMT

Thanks, It's wonderful with windows server2003 64 bit too.

Microsoft Virtual Server Host Clustering on Domain Controllers | Rob’s Blog

Microsoft Virtual Server Host Clustering on Domain Controllers | Rob’s Blog — Sun, 30 Mar 2008 14:01:51 GMT

PingBack from http://robwhitehouse.com/virtualisation/microsoft-virtual-server-host-clustering-on-domain-controllers/

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

Murdock — Thu, 17 Apr 2008 16:43:33 GMT

Thanks! Helped another production system get healthy again!

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

Ron Paul — Fri, 06 Jun 2008 03:47:40 GMT

You've helped more than any other John Howard ever has.

Top work for this find XD

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

Mike — Sun, 15 Jun 2008 15:40:28 GMT

Had this problem. Found your fix. Worked great. Thanks. Happy Father's Day! Mike

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

Froosh — Wed, 18 Jun 2008 06:49:29 GMT

Simply opening and saving the config didn't work for me, but I noticed that the account name was lacking a space (NetworkService rather than Network Service). Adding the space got me working, no problems.

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

Clive Evans — Mon, 30 Jun 2008 04:20:08 GMT

Many many thanks, seems to have fixed it for me too.

msdtc svc 53258

msdtc svc 53258 — Tue, 08 Jul 2008 10:00:45 GMT

PingBack from http://dandre.vidsdigest.info/msdtcsvc53258.html

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

Brian — Fri, 29 Aug 2008 04:28:41 GMT

Covered in http://support.microsoft.com/kb/923977

Error en el suceso ID 4143, error en dsrestor | Joan Garcia Camba

Error en el suceso ID 4143, error en dsrestor | Joan Garcia Camba — Wed, 24 Dec 2008 12:13:59 GMT

PingBack from http://www.joangarcia.info/error-en-el-suceso-id-4143-error-en-dsrestor/

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

The Dave — Sun, 22 Mar 2009 00:03:25 GMT

Years and a service pack later, still a relevant tip for an unfixed bug... Thanks once again!

re: MSDTC Event ID 4143 and 53258 on Windows Server 2003 SP1 Domain Controller

ECS Systems Administrator — Tue, 28 Jul 2009 21:00:15 GMT

Mad props; solved my MSDTC event log entries as well. Many thanks!