Any one had 3624 error in sql server 2000 - SP3

[sguslan]

Cheers all,

We have an HP DL760/8 CPU with HyperThreading Enabled/8GB RAM and an HP EVA5000 SAN running win2003 /SQL Server2000 SP3. The main active DB size is 400 GB with many tables having more than 30 million rows.
Suddenly we are experiencing error 3624 for no apparent reason.

Any one has experienced such errors?

________________________________________________________________________________
If you do not like change, get out of the IT business...

 

[hmckillop]

A few other people seem to get the same errors, some theories are reported here

http://weblogs.sqlteam.com/chrism/archive/2003/10/27/373.aspx

Microsoft have posted some fixes for 3624 problem

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

to be of more specific helpe, we would need to know exactly when the error is happening. Are you able to run profiler to identify the statement or proc call which is causing the problem?


"I'm living so far beyond my income that we may almost be said to be living apart

 

[sguslan]

Thanks foryour help. I lloked at the links you rpovided earlier but none helped, because we have a different behavior. It affects many SPIDS in the system and not related to a particular query, though , only one online application -websphere/linux- is having broken connection pipes every now and then. Yesterday we found that the same application can not insert a row in a particular table[login audit where a record is inserted after a login from the web app] for one particular user[users auth data is stored in SQL]. We suspected an index corruption and reindexed the 2 non clustered indexes on that table. Afeter which the system seems to stop report such errors.
We also opened a case with MS. I'll keep you posted ...
Thanks for help again.
GOD bless.

________________________________________________________________________________
If you do not like change, get out of the IT business...

 

[sguslan]

Cheers,
This is a followup:
Microsoft replied to our case, and found in their analysis of the system and DB logs, that a third party open source encryption dll which we use to encrypt user' passwords was the cause.
It caused a memory corruption which cause an SQL file curruption whch we resolved by reindexing the DB affected by the flaw.
The 3rd party dll was OK for a while under low login activities but misbehaved under heavier use.

________________________________________________________________________________
If you do not like change, get out of the IT business...