July 17, 2006 at 3:14 am
I've got a worrying problem with SQL Server 2000 (SP4) on Windows 2003 SP1 and an IIS website building the pages out of the SQL database.
What I am seeing is that whenever traffic to the website climbs, the lsass.exe process spikes to 80/90% of CPU. We are not using Windows authentication on the site and the problem does not occur on the secondary server under the same load conditions.
The server is running as the System user and there are no deadlocks in the system. I am seeing around 30-40 connections open per database.
The server was originally not part of the Active Directory and was joined to the domain once the web site and SQL Server were running.
Does anyone have an idea of what might be going on and how to fix it.
Thanks in advance
July 18, 2006 at 9:26 am
I have seen this before on our servers as well. ours would happen for about 10 minutes. We tracked it down to the Replication of the Active Directory. (that was one server that had the problem)
We also had another issue where the Master Server had too many IP Addresses(between 150-200). Once we created another server that just had one and moved most AD functionality to that all of our servers behaved properly.
Hope this helps.
July 18, 2006 at 9:53 am
I'm sure this isn't the case but the sasser worm has the same filename.
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
July 19, 2006 at 12:51 am
Thanks for the suggestion, we do have an AD that is giving intermittant trouble on the same site. I'll have a look into that.
Sasser is definitely not infecting the server. Ran both Symantec and Trend scans and cleaners on it.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply