Error 823, Severity 24, State 2

Here is my problem:
About a month ago or so, I had some hardware problems with a dell server
running sharepoint portal server and SQL 2000 on the same server where the
server just died a couple of times requiring restart. We got the hardware
problems resolved, and at first, we had some errors about torn pages and
database suspect and we restored from a backup. Databases were no longer in
suspect mode and everything looked fine.
A couple of days ago, while looking at possibly moving the SQL databases to
a SQL cluster we have, I noticed that we are getting some errors while
performing certain actions on the server.
First, if I try to go and do a SQL backup from within SQL Enterprise
manager, I get:
Error 823: I/O error (torn page) detected during read at offset
0x00000000b18000 in file 'e:\Program files\microsoft SQL
server\mssql\data\<database name>'
Here is the kicker... this happens on EVERY database on that server at same
offset, and then it gets me into the sql server backup window to do the
backup. The backup goes fine and then I get another I/O error (without the
Error 823 in front) at the same offset.
The error that is logged in the eventviewer is
Event ID: 17052
Error: 823, severity: 24, State:2
I/O error (torn page) detected during read at offset 0x00000000b18000 in
file 'e:\Program files\microsoft SQL server\mssql\data\<database name>'
I have tried the following:
DBCC CHECKDB returns the following:
DBCC results for 'SSO'.
DBCC results for 'sysobjects'.
There are 61 rows in 1 pages for object 'sysobjects'.
..
..
DBCC results for 'SSO_Config'.
There are 1 rows in 1 pages for object 'SSO_Config'
CHECKDB found 0 allocation errors and 0 consistency errors in database
'SSO'.
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
I ran DBCC CHECKCATALOG on some of the databases and got the following:
DBCC results for 'SSO'.
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
Also ran DBCC CHECKALLOC and got:
CHECKALLOC found 0 allocation errors and 0 consistency errors in database
'SSO'.
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
So it seems as if everything is fine. People connect to the databases
through Sharepoint, and that seems to be working fine.
If someone could shed some light on this problem and how to correct, that
would be awesome and i would be very greatful.
Thank you in advance.
Chuck
You should contact Dell for the utilities to perform full hardware
diagnostics on the server.
The following KB's explain how to turn on an additional trace flag that will
allow you to gather more information when 823 errors occur
http://support.microsoft.com/default...b;en-us;828339
http://support.microsoft.com/default...b;en-us;826433
Also, make sure that if you're using /PAE, you have the appropriate
hotfix/patches at the OS level to prevent issues like memory corruption
http://support.microsoft.com/default...b;en-us;838765
You can also run SQLIOStress to simulate a load to determine if you may have
hardware issues
http://support.microsoft.com/default...22120121120120
HTH.
"msnews.microsoft.com" <nonya@.bid.edu> wrote in message
news:eG%23mqey2FHA.1716@.TK2MSFTNGP10.phx.gbl...
> Here is my problem:
> About a month ago or so, I had some hardware problems with a dell server
> running sharepoint portal server and SQL 2000 on the same server where the
> server just died a couple of times requiring restart. We got the hardware
> problems resolved, and at first, we had some errors about torn pages and
> database suspect and we restored from a backup. Databases were no longer
> in suspect mode and everything looked fine.
> A couple of days ago, while looking at possibly moving the SQL databases
> to a SQL cluster we have, I noticed that we are getting some errors while
> performing certain actions on the server.
> First, if I try to go and do a SQL backup from within SQL Enterprise
> manager, I get:
> Error 823: I/O error (torn page) detected during read at offset
> 0x00000000b18000 in file 'e:\Program files\microsoft SQL
> server\mssql\data\<database name>'
> Here is the kicker... this happens on EVERY database on that server at
> same offset, and then it gets me into the sql server backup window to do
> the backup. The backup goes fine and then I get another I/O error
> (without the Error 823 in front) at the same offset.
> The error that is logged in the eventviewer is
> Event ID: 17052
> Error: 823, severity: 24, State:2
> I/O error (torn page) detected during read at offset 0x00000000b18000 in
> file 'e:\Program files\microsoft SQL server\mssql\data\<database name>'
> I have tried the following:
> DBCC CHECKDB returns the following:
> DBCC results for 'SSO'.
> DBCC results for 'sysobjects'.
> There are 61 rows in 1 pages for object 'sysobjects'.
> .
> .
> DBCC results for 'SSO_Config'.
> There are 1 rows in 1 pages for object 'SSO_Config'
> CHECKDB found 0 allocation errors and 0 consistency errors in database
> 'SSO'.
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
> I ran DBCC CHECKCATALOG on some of the databases and got the following:
> DBCC results for 'SSO'.
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
> Also ran DBCC CHECKALLOC and got:
> CHECKALLOC found 0 allocation errors and 0 consistency errors in database
> 'SSO'.
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
> So it seems as if everything is fine. People connect to the databases
> through Sharepoint, and that seems to be working fine.
> If someone could shed some light on this problem and how to correct, that
> would be awesome and i would be very greatful.
> Thank you in advance.
> Chuck
>
sql

Error 823, Severity 24, State 2

Here is my problem:
About a month ago or so, I had some hardware problems with a dell server
running sharepoint portal server and SQL 2000 on the same server where the
server just died a couple of times requiring restart. We got the hardware
problems resolved, and at first, we had some errors about torn pages and
database suspect and we restored from a backup. Databases were no longer in
suspect mode and everything looked fine.
A couple of days ago, while looking at possibly moving the SQL databases to
a SQL cluster we have, I noticed that we are getting some errors while
performing certain actions on the server.
First, if I try to go and do a SQL backup from within SQL Enterprise
manager, I get:
Error 823: I/O error (torn page) detected during read at offset
0x00000000b18000 in file 'e:\Program files\microsoft SQL
server\mssql\data\<database name>'
Here is the kicker... this happens on EVERY database on that server at same
offset, and then it gets me into the sql server backup window to do the
backup. The backup goes fine and then I get another I/O error (without the
Error 823 in front) at the same offset.
The error that is logged in the eventviewer is
Event ID: 17052
Error: 823, severity: 24, State:2
I/O error (torn page) detected during read at offset 0x00000000b18000 in
file 'e:\Program files\microsoft SQL server\mssql\data\<database name>'
I have tried the following:
DBCC CHECKDB returns the following:
DBCC results for 'SSO'.
DBCC results for 'sysobjects'.
There are 61 rows in 1 pages for object 'sysobjects'.
.
.
DBCC results for 'SSO_Config'.
There are 1 rows in 1 pages for object 'SSO_Config'
CHECKDB found 0 allocation errors and 0 consistency errors in database
'SSO'.
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
I ran DBCC CHECKCATALOG on some of the databases and got the following:
DBCC results for 'SSO'.
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
Also ran DBCC CHECKALLOC and got:
CHECKALLOC found 0 allocation errors and 0 consistency errors in database
'SSO'.
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
So it seems as if everything is fine. People connect to the databases
through Sharepoint, and that seems to be working fine.
If someone could shed some light on this problem and how to correct, that
would be awesome and i would be very greatful.
Thank you in advance.
ChuckYou should contact Dell for the utilities to perform full hardware
diagnostics on the server.
The following KB's explain how to turn on an additional trace flag that will
allow you to gather more information when 823 errors occur
http://support.microsoft.com/defaul...kb;en-us;828339
http://support.microsoft.com/defaul...kb;en-us;826433
Also, make sure that if you're using /PAE, you have the appropriate
hotfix/patches at the OS level to prevent issues like memory corruption
http://support.microsoft.com/defaul...kb;en-us;838765
You can also run SQLIOStress to simulate a load to determine if you may have
hardware issues
21120120" target="_blank">http://support.microsoft.com/defaul...br />
21120120
HTH.
"msnews.microsoft.com" <nonya@.bid.edu> wrote in message
news:eG%23mqey2FHA.1716@.TK2MSFTNGP10.phx.gbl...
> Here is my problem:
> About a month ago or so, I had some hardware problems with a dell server
> running sharepoint portal server and SQL 2000 on the same server where the
> server just died a couple of times requiring restart. We got the hardware
> problems resolved, and at first, we had some errors about torn pages and
> database suspect and we restored from a backup. Databases were no longer
> in suspect mode and everything looked fine.
> A couple of days ago, while looking at possibly moving the SQL databases
> to a SQL cluster we have, I noticed that we are getting some errors while
> performing certain actions on the server.
> First, if I try to go and do a SQL backup from within SQL Enterprise
> manager, I get:
> Error 823: I/O error (torn page) detected during read at offset
> 0x00000000b18000 in file 'e:\Program files\microsoft SQL
> server\mssql\data\<database name>'
> Here is the kicker... this happens on EVERY database on that server at
> same offset, and then it gets me into the sql server backup window to do
> the backup. The backup goes fine and then I get another I/O error
> (without the Error 823 in front) at the same offset.
> The error that is logged in the eventviewer is
> Event ID: 17052
> Error: 823, severity: 24, State:2
> I/O error (torn page) detected during read at offset 0x00000000b18000 in
> file 'e:\Program files\microsoft SQL server\mssql\data\<database name>'
> I have tried the following:
> DBCC CHECKDB returns the following:
> DBCC results for 'SSO'.
> DBCC results for 'sysobjects'.
> There are 61 rows in 1 pages for object 'sysobjects'.
> .
> .
> DBCC results for 'SSO_Config'.
> There are 1 rows in 1 pages for object 'SSO_Config'
> CHECKDB found 0 allocation errors and 0 consistency errors in database
> 'SSO'.
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
> I ran DBCC CHECKCATALOG on some of the databases and got the following:
> DBCC results for 'SSO'.
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
> Also ran DBCC CHECKALLOC and got:
> CHECKALLOC found 0 allocation errors and 0 consistency errors in database
> 'SSO'.
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
> So it seems as if everything is fine. People connect to the databases
> through Sharepoint, and that seems to be working fine.
> If someone could shed some light on this problem and how to correct, that
> would be awesome and i would be very greatful.
> Thank you in advance.
> Chuck
>

Error 500, Maximum concurrent users have reached

We are running three web sites in a clustered environment
WLBS. The web servers are connected to a Database Server
running MS SQL server enterprise edition licensed as per
CPU license. The Windows 2000 Advanced Server Licensing
mode on all the servers is per SEAT license.

Our customers are accessing our web servers and after some
time getting error 500, Maximum concurrent users have
reached.

We have been told by our software provider that the
connection problem lies with the ADO components which
communicating with the SQL server.

We have been turning round and round, without any luck.

Your help will be highly appreciated.

Thanks and best regards

Dave

Learning is a Never Ending process

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!Dave Kissoondoyal (network@.bowmans.intnet.mu) writes:
> We are running three web sites in a clustered environment
> WLBS. The web servers are connected to a Database Server
> running MS SQL server enterprise edition licensed as per
> CPU license. The Windows 2000 Advanced Server Licensing
> mode on all the servers is per SEAT license.
> Our customers are accessing our web servers and after some
> time getting error 500, Maximum concurrent users have
> reached.
> We have been told by our software provider that the
> connection problem lies with the ADO components which
> communicating with the SQL server.

A message that starts with a three-digit number with a leading 5
looks like a response code from a protocol that sits on top of
TCP/IP. That is, I would assume that this message comes from the
web server and not SQL Server.

Whether the web server reacts this way due to some error code
from SQL Server, I don't know. But it seems that you will have
to investigate the web server first.

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp