Windows Server 2003 Esent help - I'd like someone with hands on experience with this

[Motorheader]

I "inherited" a Windows Server 2003 with no SP's installed. The unit is the only DC in the network of 10 users. It runs MSSql and has roaming profiles. Nothing really special.

Anyhow the thing was configured with mirrored (Raid 1) 40GB drives using a hardware based LSI controller and has been pretty troublefree with the exception of low disk space.

Since I "inherited" the server I've noticed Esent errors in the Event Viewer. I removed and replaced the original drives, installed the new drives, created the new Mirror, then ghosted one of the original drives over. That all went well and got rid of the low disk space messages.

My problem is that I'm having a difficult time with the Esent errors in the Event viewer. I keep getting EventID messages 489, 494, and 454. The server keeps generating these with grovel (1740) messages as well.

In Symantec Security I have set it to NOT scan the Sysvol folder or the SIS folder, so that isn't the culprit. I thought maybe the issue was related to not enough drive space, but that has been resolved with the upgrade of the drives.

Any Server 2003 gurus here have any insight as to a resolution?

Thanks.

 

[Bored SysAdmin]

I feel your pain - taking care such old machine can be a major pain the rear. I'd suggest for you to check these MS articles:
http://support.microsoft.com/kb/278316
http://technet2.microsoft.com/...5cc01033.mspx?mfr=true

Good Luck and please share if you ever get em fixed.

p.s: Get rid of Symantec - its a resource hog and trouble makes. Nod32 is far better and very lightweight a/v product

 

[Motorheader]

Thanks for the input. Anything that is going to change the security settings of certain folders is a road I really don't want to go down. There are folders mapped as drives, 3 different levels of users on the network, and with the roaming profiles that would create much more of a mess than the Esent issues in the Event log.

As far as Symantec goes - I have complete faith in the Corporate version of the product. They already have the license - and moving them to a different Server based product wouldn't be cost effective at the moment. In addition I can honestly say I've never had a false positive with it. Thanks for the suggestion though.

I really hate inheriting someone's mess - especially one like this.

In my research I've not seen one person post "here's the answer". I've seen multiple posts with suggestions for resolution going as far back as 2000, but not one clear and concise answer. One tech post I saw even had a new server that had yet to be brought online having the issue.

 

[RebateMonger]

You need to get Server 2003 SP2 installed.

Do you have Certificate Services installed on the Server?

 

[Motorheader]

Originally posted by: RebateMonger
You need to get Server 2003 SP2 installed.

Do you have Certificate Services installed on the Server?

Thanks for the suggestion. I installed SP2 - which went pretty much without a hitch. Or so I thought. :disgust: MS has updated their requirements, notes, and KB articles addressing the type of issue I ran into. I'm going from memory, but it was a "no access to network resources" type of error for users trying to log into the server. What a nightmare that was.

Certificate services - I can't say yes or no at the moment - I'm going to be going back there later in the week.

I guess I'll be pulling the server out again in an attempt to get SP2 installed correctly again. Other than completely failing, what is the worst that could happen.