December 21, 2007 at 12:16 pm
Hi,
We have a Windows 2003 SP1 server running SQL 2000 SP4 (8.00.2039) and we lost a disk on our SAN. When everything came up, we keep getting the following error message over and over in the log:
DATE/TIME:12/21/2007 9:33:10 AM
DESCRIPTION:Error: 7105, Severity: 22, State: 6
Page (1:28575), slot 1 for text, ntext, or image node does not exist.
COMMENT:(None)
JOB RUN:(None)
I had one database come up suspect and I recovered it from a backup and I ran dbcc checkdb on all the databases and all of them come up with the same result:
CHECKDB found 0 allocation errors and 0 consistency errors in database.
Because the error does not specify which database or table is having the problem, how do I find out what object is corrupted since the CHECKDB is not showing any additional information?
Thanks,
Isabelle
Thanks!
Bea Isabelle
December 26, 2007 at 8:50 am
Hopefully, the attached link will help.
December 26, 2007 at 9:36 am
Hi,
I already saw that article and we are not running SQL Server 2000 with an affinity mask and we are not seeing any other errors. It is frustrating because I don't know what database or table is having the problem. I just keep getting this same error over and over:
DATE/TIME:12/26/2007 8:34:30 AM
DESCRIPTION:Error: 7105, Severity: 22, State: 6
Page (1:28575), slot 1 for text, ntext, or image node does not exist.
COMMENT:(None)
JOB RUN:(None)
I don't even see this error in the alert log. There is an alert setup and it just keeps going off. It is set for all Databases. Isn't there a way to get some more detailed info on the error?
Thanks,
Isabelle
Thanks!
Bea Isabelle
December 26, 2007 at 10:35 am
Hi,
It looks like there is a problem with Reporting Services. I found this in the log:
ReportingServicesService!dbcleanup!1a2c!12/26/2007-00:04:34:: e ERROR: Sql Error in CleanExpiredSessions: System.Data.SqlClient.SqlException: Page (1:28575), slot 1 for text, ntext, or image node does not exist.
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at Microsoft.ReportingServices.Library.InstrumentedSqlCommand.ExecuteNonQuery()
at Microsoft.ReportingServices.Library.DatabaseSessionStorage.CleanExpiredSessions()
ReportingServicesService!library!1a2c!12/26/2007-00:04:34:: w WARN: Transaction rollback was not executed connection is invalid
ReportingServicesService!library!1a2c!12/26/2007-00:04:34:: i INFO: Cleaned 0 batch records, 0 policies, 0 sessions, 0 cache entries, 0 snapshots, 0 chunks, 0 running jobs
ReportingServicesService!dbcleanup!d7c!12/26/2007-00:14:37:: e ERROR: Sql Error in CleanExpiredSessions: System.Data.SqlClient.SqlException: Page (1:28575), slot 1 for text, ntext, or image node does not exist.
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
So now I'm looking into what could be causing the problem with reporting services.
Thanks,
Isabelle
Thanks!
Bea Isabelle
December 27, 2007 at 6:10 pm
It's not a problem with Reporting Services - its a corruption in the database that RS is using.
What's the output from a DBCC CHECKDB on the database? Do you have a backup you can restore from?
Thanks
Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
January 7, 2008 at 12:10 pm
Hi,
Just wanted to update my post. It turned out that a table in the ReportServerTempDB database was corrupt. The weird thing is that I ran DBCC CHECKDB on the database and it came back with no errors and then ran it again a few days later, and it came back with consistency errors on a specific table.
CHECKTABLE found 0 allocation errors and 487 consistency errors in table 'PersistedStream' (object ID 533576939).
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKTABLE (ReportServerTempDB.dbo.PersistedStream ).
So I ran it with the REPAIR_ALLOW_DATA_LOSS option and it fixed it.
Thanks everybody for your replies.
Isabelle
Thanks!
Bea Isabelle
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply