NTDS Database error (Event ID 1168)

[philote]

I've been getting this error a lot lately and it appears to be related to the browser service. I restarted the browser service and two more of these errors appeared in the event log. I also am unable to browse the network segment where our server sits.

I looked up the event id on EventId.Net and was directed to knowledgebase article Q827531. That article seems to describe the situation I'm experiencing, HOWEVER, it says to get the fix for it I have to contact Micro$oft Product $upport $ervices. Yes, those $'s are intentional as they charge lots of $$$ to get support. The article notes however that charges for support calls MAY be cancelled if a specific update will fix your problem. Has anyone had to call support before for a similar problem? And did you have to pay? I'm quite upset that I can't get this fix without having to call M$ support.

Kevin
A+, Network+, MCP

 

[karmic]

I take it this is a domain controller? There are a couple of things to check, i've run into this problem before specifically with tNtds.dit.

http://support.microsoft.com/defaul...port/kb/articles/Q280/3/64.ASP&NoWebContent=1

http://support.microsoft.com/defaul...port/kb/articles/Q303/0/77.ASP&NoWebContent=1

It's so pitiful, microsoft is so strapped for cash these days and trying to get clients to pay for all their services now...

~ K.I.S.S - Don't make it any more complex than it has to be ~

 

[philote]

Thanks for your help but unfortunately those two articles don't really describe my problem. Q827531 gives my error exactly and I believe I need the fix it refers to.

And yeah, poor, poor M$ must be going broke. ($245 per incident for support!?)

Kevin
A+, Network+, MCP

 

[karmic]

This number refers to problems with service pack 4 installation, big surprise... Sp4 has been a nightmare for many, many people. I personally refuse to install it on any server I maintain.
This is the article you refer to?

http://support.microsoft.com/default.aspx?scid=kb;en-us;827531

I take it you've installed sp4 already? did you previously install sp3? can you revert to sp3?

I swear microsoft is purposely creating problems with their service packs lately just to make the money. It seems that only since sp4 came out they're now charging big time for services. Or maybe they're trying to catch software pirates, who knows.

Anyhow, if you can remove sp4 and reinstall sp3, do it. What can it hurt?

~ K.I.S.S - Don't make it any more complex than it has to be ~

 

[philote]

Yeah, that's the article. Thanks for the advice, I probably will uninstall SP4 if I can.

If it wouldn't be such a pain in the butt, I'd switch us over to Linux. I mean, with Samba, VNC, WINE, and the other numerous (and free) tools, why stay with Windows?

Kevin
A+, Network+, MCP

 

[karmic]

That's what i'm looking at... unfortunately microsoft has to stay for alot of people. There's alot of software packages that will not run under linux. But I agree with you. If you have a bare bones server, linux should be the way to go.

good luck

~ K.I.S.S - Don't make it any more complex than it has to be ~

 

[JTors]

I found this: "SP4 adds some additional AD database consistency checks. This particular error is caused by orphaned objects in AD. A few of these in the event log should not be cause for concern; but if they start cropping up over and over, then there might be a more serious problem."

The fix is to reboot a DC (preferably the one logging the errors) into directory services restore mode, run ntdsutil, and do a semantic check. Details of performing this check can be found in Q814202 (this article has nothing to do with the errors at hand; it just shows how to do the check). If ntdsutil cannot fix the errors it finds, it will report the offending objects, which you will then need to delete with ADSIedit.

See Q827531, a hotfix is available from Microsoft.

 

[philote]

Thanks JTors. I'll see if I can try that out some time soon. Unfortunately I work 8-5 and we need our server running 6am-8pm. That means I'll have to either come in really early or stay really late or work on a weekend :-(

Kevin
A+, Network+, MCP