Comments

# Benjamin Mateos said:

Maybe a wrong registry entry set by SP1 ???

Interesting at least.

/r

Benji

26 April 05 at 5:45 PM

# Pims said:

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

Pims

24 May 05 at 4:42 PM

# Spencer Steel said:

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 !

02 June 05 at 6:39 AM

# Raffi C. said:

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

Heart cheers to the original poster, jhoward!

10 June 05 at 2:55 PM

# Raffi C. said:

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

Heart cheers to the original poster, jhoward!

10 June 05 at 2:55 PM

# Thilo said:

Great help, thank you.

14 June 05 at 3:05 AM

# pdc said:

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

However bizarre, it works.

Cheers!

16 June 05 at 8:24 PM

# Kenneth said:

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

17 June 05 at 3:04 PM

# Alan Florance said:

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

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

23 June 05 at 9:42 AM

# Mitchell said:

Thank you so much for such a simple fix.

23 June 05 at 11:07 AM

# jhoward said:

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.

23 June 05 at 11:23 AM

# Zeveck said:

Thanx!!

24 June 05 at 10:20 AM

# Steve said:

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!

06 July 05 at 5:08 AM

# JP said:

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

-JP

10 July 05 at 5:11 PM

# Armin said:

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

19 July 05 at 9:03 AM

# saffi said:

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...

24 July 05 at 9:33 AM

# saffi said:

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
======================

25 July 05 at 10:27 AM

# Alistair said:

Thanks. Worked for me

05 September 05 at 5:34 AM

# Yoshihao (retired MS Japan) said:

Thanks from Japan.

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

07 September 05 at 3:19 AM

# Dave said:

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

30 October 05 at 10:46 PM

# Alex Silverberg said:

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

16 November 05 at 12:28 PM

# sdb said:

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

02 December 05 at 3:49 PM

# Michael said:

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!

16 December 05 at 5:23 PM

# Paul said:

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

08 January 06 at 11:34 AM

# Jeff said:

Did you ever knoooow that your my heeeeroooo? ;)

23 January 06 at 10:02 AM

# Alain said:

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

25 January 06 at 9:39 AM

# Paul Frazer said:

You Rock!! Thanks!!!

03 February 06 at 9:57 PM

# michael said:

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.

06 February 06 at 1:15 PM

# Marco said:

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

28 February 06 at 8:33 AM

# Marcial Franco said:

Thanks from Spain (Santiago de Compostela)

;)

07 March 06 at 2:00 PM

# Stefan said:

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...

01 April 06 at 4:03 PM

# Stefan (Germany) said:

Thank you very much, it works !!

03 May 06 at 5:17 AM

# tom said:

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

14 June 06 at 12:58 PM

# cbsilcor said:

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

06 July 06 at 3:54 AM

# Mike F said:

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

06 July 06 at 9:22 AM

# Boris said:

Your solution works fine. Thanks from Bolivia...

06 July 06 at 6:12 PM

# LEO said:

Thanks for Grate Your Help!  From Japan--

12 July 06 at 6:21 AM

# Chris C said:

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

25 July 06 at 5:54 PM

# Beetowen said:

thx

09 August 06 at 9:48 AM

# jomiro said:

worked for me. thanks

17 August 06 at 10:28 AM

# Grzegorz said:

Thanks for that from Poland :-)

24 August 06 at 3:11 PM

# Helpme said:

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

26 August 06 at 3:56 PM

# Gregg said:

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!!!

01 September 06 at 10:07 AM

# andreaccs said:

on behalf of a customer of mine THANK YOU!!

13 September 06 at 4:43 AM

# dfeuchter said:

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

27 April 07 at 4:27 AM

# Wafi Aljunedi said:

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

12 March 08 at 4:57 AM

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

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

30 March 08 at 7:01 AM

# Murdock said:

Thanks!  Helped another production system get healthy again!

17 April 08 at 9:43 AM

# Ron Paul said:

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

Top work for this find XD

05 June 08 at 8:47 PM

# Mike said:

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

15 June 08 at 8:40 AM

# Froosh said:

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.

17 June 08 at 11:49 PM

# Clive Evans said:

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

29 June 08 at 9:20 PM

# msdtc svc 53258 said:

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

08 July 08 at 3:00 AM

# Brian said:

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

28 August 08 at 9:28 PM

Leave a Comment

Comment Policy: No HTML allowed. URIs and line breaks are converted automatically. Your e–mail address will not show up on any public page.

Name (required) 

Your URL (optional)

Comments (required) 

Remember Me?