We have SQL Server 2005 set up and we are seeing the following error messages
in our logs from Daily maintenance Plan.
Please comment on the severity of these errors.
Thanks,
mkb
================================================
Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[AllUserData]
REBUILD WITH ( PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF,
ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, SORT_IN_TEMPDB = OFF, ONLINE =
OFF )
" failed with the following error: "SQL Server detected a logical
consistency-based I/O error: incorrect pageid (expected 1:2676; actual
14616:395852048). It occurred during a read of page (1:2676) in database ID
13 at offset 0x000000014e8000 in file 'C:\\Program Files\\Microsoft SQL
Server\\MSSQL.1\\MSSQL\\DATA\\SP_IntranetMySites_W ebApp.mdf'. Additional
messages in the SQL Server error log or system event log may provide more
detail. This is a severe error condition that threatens database integrity
and must be corrected immediately. Complete a full database consistency check
(DBCC CHECKDB). This error can be caused by many factors; for more
information, see SQL Server Books Online.
The statement has been terminated.". Possible failure reasons: Problems with
the query, "ResultSet" property not set correctly, parameters not set
correctly, or connection not established correctly.
================================================== =
Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[AllUserData]
REORGANIZE WITH ( LOB_COMPACTION = OFF )
" failed with the following error: "SQL Server detected a logical
consistency-based I/O error: incorrect pageid (expected 1:2653; actual
47686:707280961). It occurred during a read of page (1:2653) in database ID
13 at offset 0x000000014ba000 in file 'C:\\Program Files\\Microsoft SQL
Server\\MSSQL.1\\MSSQL\\DATA\\SP_IntranetMySites_W ebApp.mdf'. Additional
messages in the SQL Server error log or system event log may provide more
detail. This is a severe error condition that threatens database integrity
and must be corrected immediately. Complete a full database consistency check
(DBCC CHECKDB). This error can be caused by many factors; for more
information, see SQL Server Books Online.". Possible failure reasons:
Problems with the query, "ResultSet" property not set correctly, parameters
not set correctly, or connection not established correctly.
================================================== ==
Executing the query "DBCC CHECKDB WITH NO_INFOMSGS
" failed with the following error: "An internal error occurred in DBCC that
prevented further processing. Contact Customer Support Services.
Check terminated. A failure was detected while collecting facts. Possibly
tempdb out of space or a system table is inconsistent. Check previous
errors.". Possible failure reasons: Problems with the query, "ResultSet"
property not set correctly, parameters not set correctly, or connection not
established correctly.
================================================== =
Hi
It seems that there is some corruption in the database. Have you had any
hardware issues? Is there any other information in the SQL Server log or
Windows Event Logs?
You could try dropping the index and running DBCC CHECKDB again. If it works
then re-create the index and run it again. If you don't find out what caused
this then it could happen again.
John
"MKBOBBA" wrote:
> We have SQL Server 2005 set up and we are seeing the following error messages
> in our logs from Daily maintenance Plan.
> Please comment on the severity of these errors.
> Thanks,
> mkb
> ================================================
> Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[AllUserData]
> REBUILD WITH ( PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF,
> ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, SORT_IN_TEMPDB = OFF, ONLINE =
> OFF )
> " failed with the following error: "SQL Server detected a logical
> consistency-based I/O error: incorrect pageid (expected 1:2676; actual
> 14616:395852048). It occurred during a read of page (1:2676) in database ID
> 13 at offset 0x000000014e8000 in file 'C:\\Program Files\\Microsoft SQL
> Server\\MSSQL.1\\MSSQL\\DATA\\SP_IntranetMySites_W ebApp.mdf'. Additional
> messages in the SQL Server error log or system event log may provide more
> detail. This is a severe error condition that threatens database integrity
> and must be corrected immediately. Complete a full database consistency check
> (DBCC CHECKDB). This error can be caused by many factors; for more
> information, see SQL Server Books Online.
> The statement has been terminated.". Possible failure reasons: Problems with
> the query, "ResultSet" property not set correctly, parameters not set
> correctly, or connection not established correctly.
>
> ================================================== =
> Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[AllUserData]
> REORGANIZE WITH ( LOB_COMPACTION = OFF )
> " failed with the following error: "SQL Server detected a logical
> consistency-based I/O error: incorrect pageid (expected 1:2653; actual
> 47686:707280961). It occurred during a read of page (1:2653) in database ID
> 13 at offset 0x000000014ba000 in file 'C:\\Program Files\\Microsoft SQL
> Server\\MSSQL.1\\MSSQL\\DATA\\SP_IntranetMySites_W ebApp.mdf'. Additional
> messages in the SQL Server error log or system event log may provide more
> detail. This is a severe error condition that threatens database integrity
> and must be corrected immediately. Complete a full database consistency check
> (DBCC CHECKDB). This error can be caused by many factors; for more
> information, see SQL Server Books Online.". Possible failure reasons:
> Problems with the query, "ResultSet" property not set correctly, parameters
> not set correctly, or connection not established correctly.
> ================================================== ==
> Executing the query "DBCC CHECKDB WITH NO_INFOMSGS
> " failed with the following error: "An internal error occurred in DBCC that
> prevented further processing. Contact Customer Support Services.
> Check terminated. A failure was detected while collecting facts. Possibly
> tempdb out of space or a system table is inconsistent. Check previous
> errors.". Possible failure reasons: Problems with the query, "ResultSet"
> property not set correctly, parameters not set correctly, or connection not
> established correctly.
> ================================================== =
>
|||And I forgot to add.. Make sure you have a good backup before doing this! You
could try restoring a backup on a different machine to try your tests out
before working on live (providing you have the hardware!)
John
"MKBOBBA" wrote:
> We have SQL Server 2005 set up and we are seeing the following error messages
> in our logs from Daily maintenance Plan.
> Please comment on the severity of these errors.
> Thanks,
> mkb
> ================================================
> Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[AllUserData]
> REBUILD WITH ( PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF,
> ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, SORT_IN_TEMPDB = OFF, ONLINE =
> OFF )
> " failed with the following error: "SQL Server detected a logical
> consistency-based I/O error: incorrect pageid (expected 1:2676; actual
> 14616:395852048). It occurred during a read of page (1:2676) in database ID
> 13 at offset 0x000000014e8000 in file 'C:\\Program Files\\Microsoft SQL
> Server\\MSSQL.1\\MSSQL\\DATA\\SP_IntranetMySites_W ebApp.mdf'. Additional
> messages in the SQL Server error log or system event log may provide more
> detail. This is a severe error condition that threatens database integrity
> and must be corrected immediately. Complete a full database consistency check
> (DBCC CHECKDB). This error can be caused by many factors; for more
> information, see SQL Server Books Online.
> The statement has been terminated.". Possible failure reasons: Problems with
> the query, "ResultSet" property not set correctly, parameters not set
> correctly, or connection not established correctly.
>
> ================================================== =
> Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[AllUserData]
> REORGANIZE WITH ( LOB_COMPACTION = OFF )
> " failed with the following error: "SQL Server detected a logical
> consistency-based I/O error: incorrect pageid (expected 1:2653; actual
> 47686:707280961). It occurred during a read of page (1:2653) in database ID
> 13 at offset 0x000000014ba000 in file 'C:\\Program Files\\Microsoft SQL
> Server\\MSSQL.1\\MSSQL\\DATA\\SP_IntranetMySites_W ebApp.mdf'. Additional
> messages in the SQL Server error log or system event log may provide more
> detail. This is a severe error condition that threatens database integrity
> and must be corrected immediately. Complete a full database consistency check
> (DBCC CHECKDB). This error can be caused by many factors; for more
> information, see SQL Server Books Online.". Possible failure reasons:
> Problems with the query, "ResultSet" property not set correctly, parameters
> not set correctly, or connection not established correctly.
> ================================================== ==
> Executing the query "DBCC CHECKDB WITH NO_INFOMSGS
> " failed with the following error: "An internal error occurred in DBCC that
> prevented further processing. Contact Customer Support Services.
> Check terminated. A failure was detected while collecting facts. Possibly
> tempdb out of space or a system table is inconsistent. Check previous
> errors.". Possible failure reasons: Problems with the query, "ResultSet"
> property not set correctly, parameters not set correctly, or connection not
> established correctly.
> ================================================== =
>
Showing posts with label severity. Show all posts
Showing posts with label severity. Show all posts
Wednesday, March 21, 2012
Errors when rebuilding indexes
We have SQL Server 2005 set up and we are seeing the following error messages
in our logs from Daily maintenance Plan.
Please comment on the severity of these errors.
Thanks,
mkb
================================================ Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[AllUserData]
REBUILD WITH ( PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF,
ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, SORT_IN_TEMPDB = OFF, ONLINE = OFF )
" failed with the following error: "SQL Server detected a logical
consistency-based I/O error: incorrect pageid (expected 1:2676; actual
14616:395852048). It occurred during a read of page (1:2676) in database ID
13 at offset 0x000000014e8000 in file 'C:\\Program Files\\Microsoft SQL
Server\\MSSQL.1\\MSSQL\\DATA\\SP_IntranetMySites_WebApp.mdf'. Additional
messages in the SQL Server error log or system event log may provide more
detail. This is a severe error condition that threatens database integrity
and must be corrected immediately. Complete a full database consistency check
(DBCC CHECKDB). This error can be caused by many factors; for more
information, see SQL Server Books Online.
The statement has been terminated.". Possible failure reasons: Problems with
the query, "ResultSet" property not set correctly, parameters not set
correctly, or connection not established correctly.
===================================================
Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[AllUserData]
REORGANIZE WITH ( LOB_COMPACTION = OFF )
" failed with the following error: "SQL Server detected a logical
consistency-based I/O error: incorrect pageid (expected 1:2653; actual
47686:707280961). It occurred during a read of page (1:2653) in database ID
13 at offset 0x000000014ba000 in file 'C:\\Program Files\\Microsoft SQL
Server\\MSSQL.1\\MSSQL\\DATA\\SP_IntranetMySites_WebApp.mdf'. Additional
messages in the SQL Server error log or system event log may provide more
detail. This is a severe error condition that threatens database integrity
and must be corrected immediately. Complete a full database consistency check
(DBCC CHECKDB). This error can be caused by many factors; for more
information, see SQL Server Books Online.". Possible failure reasons:
Problems with the query, "ResultSet" property not set correctly, parameters
not set correctly, or connection not established correctly.
====================================================
Executing the query "DBCC CHECKDB WITH NO_INFOMSGS
" failed with the following error: "An internal error occurred in DBCC that
prevented further processing. Contact Customer Support Services.
Check terminated. A failure was detected while collecting facts. Possibly
tempdb out of space or a system table is inconsistent. Check previous
errors.". Possible failure reasons: Problems with the query, "ResultSet"
property not set correctly, parameters not set correctly, or connection not
established correctly.
===================================================Hi
It seems that there is some corruption in the database. Have you had any
hardware issues? Is there any other information in the SQL Server log or
Windows Event Logs?
You could try dropping the index and running DBCC CHECKDB again. If it works
then re-create the index and run it again. If you don't find out what caused
this then it could happen again.
John
"MKBOBBA" wrote:
> We have SQL Server 2005 set up and we are seeing the following error messages
> in our logs from Daily maintenance Plan.
> Please comment on the severity of these errors.
> Thanks,
> mkb
> ================================================> Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[AllUserData]
> REBUILD WITH ( PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF,
> ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, SORT_IN_TEMPDB = OFF, ONLINE => OFF )
> " failed with the following error: "SQL Server detected a logical
> consistency-based I/O error: incorrect pageid (expected 1:2676; actual
> 14616:395852048). It occurred during a read of page (1:2676) in database ID
> 13 at offset 0x000000014e8000 in file 'C:\\Program Files\\Microsoft SQL
> Server\\MSSQL.1\\MSSQL\\DATA\\SP_IntranetMySites_WebApp.mdf'. Additional
> messages in the SQL Server error log or system event log may provide more
> detail. This is a severe error condition that threatens database integrity
> and must be corrected immediately. Complete a full database consistency check
> (DBCC CHECKDB). This error can be caused by many factors; for more
> information, see SQL Server Books Online.
> The statement has been terminated.". Possible failure reasons: Problems with
> the query, "ResultSet" property not set correctly, parameters not set
> correctly, or connection not established correctly.
>
> ===================================================> Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[AllUserData]
> REORGANIZE WITH ( LOB_COMPACTION = OFF )
> " failed with the following error: "SQL Server detected a logical
> consistency-based I/O error: incorrect pageid (expected 1:2653; actual
> 47686:707280961). It occurred during a read of page (1:2653) in database ID
> 13 at offset 0x000000014ba000 in file 'C:\\Program Files\\Microsoft SQL
> Server\\MSSQL.1\\MSSQL\\DATA\\SP_IntranetMySites_WebApp.mdf'. Additional
> messages in the SQL Server error log or system event log may provide more
> detail. This is a severe error condition that threatens database integrity
> and must be corrected immediately. Complete a full database consistency check
> (DBCC CHECKDB). This error can be caused by many factors; for more
> information, see SQL Server Books Online.". Possible failure reasons:
> Problems with the query, "ResultSet" property not set correctly, parameters
> not set correctly, or connection not established correctly.
> ====================================================> Executing the query "DBCC CHECKDB WITH NO_INFOMSGS
> " failed with the following error: "An internal error occurred in DBCC that
> prevented further processing. Contact Customer Support Services.
> Check terminated. A failure was detected while collecting facts. Possibly
> tempdb out of space or a system table is inconsistent. Check previous
> errors.". Possible failure reasons: Problems with the query, "ResultSet"
> property not set correctly, parameters not set correctly, or connection not
> established correctly.
> ===================================================>|||And I forgot to add.. Make sure you have a good backup before doing this! You
could try restoring a backup on a different machine to try your tests out
before working on live (providing you have the hardware!)
John
"MKBOBBA" wrote:
> We have SQL Server 2005 set up and we are seeing the following error messages
> in our logs from Daily maintenance Plan.
> Please comment on the severity of these errors.
> Thanks,
> mkb
> ================================================> Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[AllUserData]
> REBUILD WITH ( PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF,
> ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, SORT_IN_TEMPDB = OFF, ONLINE => OFF )
> " failed with the following error: "SQL Server detected a logical
> consistency-based I/O error: incorrect pageid (expected 1:2676; actual
> 14616:395852048). It occurred during a read of page (1:2676) in database ID
> 13 at offset 0x000000014e8000 in file 'C:\\Program Files\\Microsoft SQL
> Server\\MSSQL.1\\MSSQL\\DATA\\SP_IntranetMySites_WebApp.mdf'. Additional
> messages in the SQL Server error log or system event log may provide more
> detail. This is a severe error condition that threatens database integrity
> and must be corrected immediately. Complete a full database consistency check
> (DBCC CHECKDB). This error can be caused by many factors; for more
> information, see SQL Server Books Online.
> The statement has been terminated.". Possible failure reasons: Problems with
> the query, "ResultSet" property not set correctly, parameters not set
> correctly, or connection not established correctly.
>
> ===================================================> Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[AllUserData]
> REORGANIZE WITH ( LOB_COMPACTION = OFF )
> " failed with the following error: "SQL Server detected a logical
> consistency-based I/O error: incorrect pageid (expected 1:2653; actual
> 47686:707280961). It occurred during a read of page (1:2653) in database ID
> 13 at offset 0x000000014ba000 in file 'C:\\Program Files\\Microsoft SQL
> Server\\MSSQL.1\\MSSQL\\DATA\\SP_IntranetMySites_WebApp.mdf'. Additional
> messages in the SQL Server error log or system event log may provide more
> detail. This is a severe error condition that threatens database integrity
> and must be corrected immediately. Complete a full database consistency check
> (DBCC CHECKDB). This error can be caused by many factors; for more
> information, see SQL Server Books Online.". Possible failure reasons:
> Problems with the query, "ResultSet" property not set correctly, parameters
> not set correctly, or connection not established correctly.
> ====================================================> Executing the query "DBCC CHECKDB WITH NO_INFOMSGS
> " failed with the following error: "An internal error occurred in DBCC that
> prevented further processing. Contact Customer Support Services.
> Check terminated. A failure was detected while collecting facts. Possibly
> tempdb out of space or a system table is inconsistent. Check previous
> errors.". Possible failure reasons: Problems with the query, "ResultSet"
> property not set correctly, parameters not set correctly, or connection not
> established correctly.
> ===================================================>
in our logs from Daily maintenance Plan.
Please comment on the severity of these errors.
Thanks,
mkb
================================================ Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[AllUserData]
REBUILD WITH ( PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF,
ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, SORT_IN_TEMPDB = OFF, ONLINE = OFF )
" failed with the following error: "SQL Server detected a logical
consistency-based I/O error: incorrect pageid (expected 1:2676; actual
14616:395852048). It occurred during a read of page (1:2676) in database ID
13 at offset 0x000000014e8000 in file 'C:\\Program Files\\Microsoft SQL
Server\\MSSQL.1\\MSSQL\\DATA\\SP_IntranetMySites_WebApp.mdf'. Additional
messages in the SQL Server error log or system event log may provide more
detail. This is a severe error condition that threatens database integrity
and must be corrected immediately. Complete a full database consistency check
(DBCC CHECKDB). This error can be caused by many factors; for more
information, see SQL Server Books Online.
The statement has been terminated.". Possible failure reasons: Problems with
the query, "ResultSet" property not set correctly, parameters not set
correctly, or connection not established correctly.
===================================================
Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[AllUserData]
REORGANIZE WITH ( LOB_COMPACTION = OFF )
" failed with the following error: "SQL Server detected a logical
consistency-based I/O error: incorrect pageid (expected 1:2653; actual
47686:707280961). It occurred during a read of page (1:2653) in database ID
13 at offset 0x000000014ba000 in file 'C:\\Program Files\\Microsoft SQL
Server\\MSSQL.1\\MSSQL\\DATA\\SP_IntranetMySites_WebApp.mdf'. Additional
messages in the SQL Server error log or system event log may provide more
detail. This is a severe error condition that threatens database integrity
and must be corrected immediately. Complete a full database consistency check
(DBCC CHECKDB). This error can be caused by many factors; for more
information, see SQL Server Books Online.". Possible failure reasons:
Problems with the query, "ResultSet" property not set correctly, parameters
not set correctly, or connection not established correctly.
====================================================
Executing the query "DBCC CHECKDB WITH NO_INFOMSGS
" failed with the following error: "An internal error occurred in DBCC that
prevented further processing. Contact Customer Support Services.
Check terminated. A failure was detected while collecting facts. Possibly
tempdb out of space or a system table is inconsistent. Check previous
errors.". Possible failure reasons: Problems with the query, "ResultSet"
property not set correctly, parameters not set correctly, or connection not
established correctly.
===================================================Hi
It seems that there is some corruption in the database. Have you had any
hardware issues? Is there any other information in the SQL Server log or
Windows Event Logs?
You could try dropping the index and running DBCC CHECKDB again. If it works
then re-create the index and run it again. If you don't find out what caused
this then it could happen again.
John
"MKBOBBA" wrote:
> We have SQL Server 2005 set up and we are seeing the following error messages
> in our logs from Daily maintenance Plan.
> Please comment on the severity of these errors.
> Thanks,
> mkb
> ================================================> Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[AllUserData]
> REBUILD WITH ( PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF,
> ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, SORT_IN_TEMPDB = OFF, ONLINE => OFF )
> " failed with the following error: "SQL Server detected a logical
> consistency-based I/O error: incorrect pageid (expected 1:2676; actual
> 14616:395852048). It occurred during a read of page (1:2676) in database ID
> 13 at offset 0x000000014e8000 in file 'C:\\Program Files\\Microsoft SQL
> Server\\MSSQL.1\\MSSQL\\DATA\\SP_IntranetMySites_WebApp.mdf'. Additional
> messages in the SQL Server error log or system event log may provide more
> detail. This is a severe error condition that threatens database integrity
> and must be corrected immediately. Complete a full database consistency check
> (DBCC CHECKDB). This error can be caused by many factors; for more
> information, see SQL Server Books Online.
> The statement has been terminated.". Possible failure reasons: Problems with
> the query, "ResultSet" property not set correctly, parameters not set
> correctly, or connection not established correctly.
>
> ===================================================> Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[AllUserData]
> REORGANIZE WITH ( LOB_COMPACTION = OFF )
> " failed with the following error: "SQL Server detected a logical
> consistency-based I/O error: incorrect pageid (expected 1:2653; actual
> 47686:707280961). It occurred during a read of page (1:2653) in database ID
> 13 at offset 0x000000014ba000 in file 'C:\\Program Files\\Microsoft SQL
> Server\\MSSQL.1\\MSSQL\\DATA\\SP_IntranetMySites_WebApp.mdf'. Additional
> messages in the SQL Server error log or system event log may provide more
> detail. This is a severe error condition that threatens database integrity
> and must be corrected immediately. Complete a full database consistency check
> (DBCC CHECKDB). This error can be caused by many factors; for more
> information, see SQL Server Books Online.". Possible failure reasons:
> Problems with the query, "ResultSet" property not set correctly, parameters
> not set correctly, or connection not established correctly.
> ====================================================> Executing the query "DBCC CHECKDB WITH NO_INFOMSGS
> " failed with the following error: "An internal error occurred in DBCC that
> prevented further processing. Contact Customer Support Services.
> Check terminated. A failure was detected while collecting facts. Possibly
> tempdb out of space or a system table is inconsistent. Check previous
> errors.". Possible failure reasons: Problems with the query, "ResultSet"
> property not set correctly, parameters not set correctly, or connection not
> established correctly.
> ===================================================>|||And I forgot to add.. Make sure you have a good backup before doing this! You
could try restoring a backup on a different machine to try your tests out
before working on live (providing you have the hardware!)
John
"MKBOBBA" wrote:
> We have SQL Server 2005 set up and we are seeing the following error messages
> in our logs from Daily maintenance Plan.
> Please comment on the severity of these errors.
> Thanks,
> mkb
> ================================================> Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[AllUserData]
> REBUILD WITH ( PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF,
> ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, SORT_IN_TEMPDB = OFF, ONLINE => OFF )
> " failed with the following error: "SQL Server detected a logical
> consistency-based I/O error: incorrect pageid (expected 1:2676; actual
> 14616:395852048). It occurred during a read of page (1:2676) in database ID
> 13 at offset 0x000000014e8000 in file 'C:\\Program Files\\Microsoft SQL
> Server\\MSSQL.1\\MSSQL\\DATA\\SP_IntranetMySites_WebApp.mdf'. Additional
> messages in the SQL Server error log or system event log may provide more
> detail. This is a severe error condition that threatens database integrity
> and must be corrected immediately. Complete a full database consistency check
> (DBCC CHECKDB). This error can be caused by many factors; for more
> information, see SQL Server Books Online.
> The statement has been terminated.". Possible failure reasons: Problems with
> the query, "ResultSet" property not set correctly, parameters not set
> correctly, or connection not established correctly.
>
> ===================================================> Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[AllUserData]
> REORGANIZE WITH ( LOB_COMPACTION = OFF )
> " failed with the following error: "SQL Server detected a logical
> consistency-based I/O error: incorrect pageid (expected 1:2653; actual
> 47686:707280961). It occurred during a read of page (1:2653) in database ID
> 13 at offset 0x000000014ba000 in file 'C:\\Program Files\\Microsoft SQL
> Server\\MSSQL.1\\MSSQL\\DATA\\SP_IntranetMySites_WebApp.mdf'. Additional
> messages in the SQL Server error log or system event log may provide more
> detail. This is a severe error condition that threatens database integrity
> and must be corrected immediately. Complete a full database consistency check
> (DBCC CHECKDB). This error can be caused by many factors; for more
> information, see SQL Server Books Online.". Possible failure reasons:
> Problems with the query, "ResultSet" property not set correctly, parameters
> not set correctly, or connection not established correctly.
> ====================================================> Executing the query "DBCC CHECKDB WITH NO_INFOMSGS
> " failed with the following error: "An internal error occurred in DBCC that
> prevented further processing. Contact Customer Support Services.
> Check terminated. A failure was detected while collecting facts. Possibly
> tempdb out of space or a system table is inconsistent. Check previous
> errors.". Possible failure reasons: Problems with the query, "ResultSet"
> property not set correctly, parameters not set correctly, or connection not
> established correctly.
> ===================================================>
Errors when rebuilding indexes
We have SQL Server 2005 set up and we are seeing the following error message
s
in our logs from Daily maintenance Plan.
Please comment on the severity of these errors.
Thanks,
mkb
========================================
========
Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[AllU
serData]
REBUILD WITH ( PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF,
ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, SORT_IN_TEMPDB = OFF, ONLINE
=
OFF )
" failed with the following error: "SQL Server detected a logical
consistency-based I/O error: incorrect pageid (expected 1:2676; actual
14616:395852048). It occurred during a read of page (1:2676) in database ID
13 at offset 0x000000014e8000 in file 'C:\\Program Files\\Microsoft SQL
Server\\MSSQL. 1\\MSSQL\\DATA\\SP_IntranetMySites_WebAp
p.mdf'. Additional
messages in the SQL Server error log or system event log may provide more
detail. This is a severe error condition that threatens database integrity
and must be corrected immediately. Complete a full database consistency chec
k
(DBCC CHECKDB). This error can be caused by many factors; for more
information, see SQL Server Books Online.
The statement has been terminated.". Possible failure reasons: Problems with
the query, "ResultSet" property not set correctly, parameters not set
correctly, or connection not established correctly.
========================================
===========
Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[AllU
serData]
REORGANIZE WITH ( LOB_COMPACTION = OFF )
" failed with the following error: "SQL Server detected a logical
consistency-based I/O error: incorrect pageid (expected 1:2653; actual
47686:707280961). It occurred during a read of page (1:2653) in database ID
13 at offset 0x000000014ba000 in file 'C:\\Program Files\\Microsoft SQL
Server\\MSSQL. 1\\MSSQL\\DATA\\SP_IntranetMySites_WebAp
p.mdf'. Additional
messages in the SQL Server error log or system event log may provide more
detail. This is a severe error condition that threatens database integrity
and must be corrected immediately. Complete a full database consistency chec
k
(DBCC CHECKDB). This error can be caused by many factors; for more
information, see SQL Server Books Online.". Possible failure reasons:
Problems with the query, "ResultSet" property not set correctly, parameters
not set correctly, or connection not established correctly.
========================================
============
Executing the query "DBCC CHECKDB WITH NO_INFOMSGS
" failed with the following error: "An internal error occurred in DBCC that
prevented further processing. Contact Customer Support Services.
Check terminated. A failure was detected while collecting facts. Possibly
tempdb out of space or a system table is inconsistent. Check previous
errors.". Possible failure reasons: Problems with the query, "ResultSet"
property not set correctly, parameters not set correctly, or connection not
established correctly.
========================================
===========Hi
It seems that there is some corruption in the database. Have you had any
hardware issues? Is there any other information in the SQL Server log or
Windows Event Logs?
You could try dropping the index and running DBCC CHECKDB again. If it works
then re-create the index and run it again. If you don't find out what caused
this then it could happen again.
John
"MKBOBBA" wrote:
> We have SQL Server 2005 set up and we are seeing the following error messa
ges
> in our logs from Daily maintenance Plan.
> Please comment on the severity of these errors.
> Thanks,
> mkb
> ========================================
========
> Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[Al
lUserData]
> REBUILD WITH ( PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF,
> ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, SORT_IN_TEMPDB = OFF, ONLIN
E =
> OFF )
> " failed with the following error: "SQL Server detected a logical
> consistency-based I/O error: incorrect pageid (expected 1:2676; actual
> 14616:395852048). It occurred during a read of page (1:2676) in database I
D
> 13 at offset 0x000000014e8000 in file 'C:\\Program Files\\Microsoft SQL
> Server\\MSSQL. 1\\MSSQL\\DATA\\SP_IntranetMySites_WebAp
p.mdf'. Additional
> messages in the SQL Server error log or system event log may provide more
> detail. This is a severe error condition that threatens database integrity
> and must be corrected immediately. Complete a full database consistency ch
eck
> (DBCC CHECKDB). This error can be caused by many factors; for more
> information, see SQL Server Books Online.
> The statement has been terminated.". Possible failure reasons: Problems wi
th
> the query, "ResultSet" property not set correctly, parameters not set
> correctly, or connection not established correctly.
>
> ========================================
===========
> Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[Al
lUserData]
> REORGANIZE WITH ( LOB_COMPACTION = OFF )
> " failed with the following error: "SQL Server detected a logical
> consistency-based I/O error: incorrect pageid (expected 1:2653; actual
> 47686:707280961). It occurred during a read of page (1:2653) in database I
D
> 13 at offset 0x000000014ba000 in file 'C:\\Program Files\\Microsoft SQL
> Server\\MSSQL. 1\\MSSQL\\DATA\\SP_IntranetMySites_WebAp
p.mdf'. Additional
> messages in the SQL Server error log or system event log may provide more
> detail. This is a severe error condition that threatens database integrity
> and must be corrected immediately. Complete a full database consistency ch
eck
> (DBCC CHECKDB). This error can be caused by many factors; for more
> information, see SQL Server Books Online.". Possible failure reasons:
> Problems with the query, "ResultSet" property not set correctly, parameter
s
> not set correctly, or connection not established correctly.
> ========================================
============
> Executing the query "DBCC CHECKDB WITH NO_INFOMSGS
> " failed with the following error: "An internal error occurred in DBCC tha
t
> prevented further processing. Contact Customer Support Services.
> Check terminated. A failure was detected while collecting facts. Possibly
> tempdb out of space or a system table is inconsistent. Check previous
> errors.". Possible failure reasons: Problems with the query, "ResultSet"
> property not set correctly, parameters not set correctly, or connection no
t
> established correctly.
> ========================================
===========
>|||And I forgot to add.. Make sure you have a good backup before doing this! Yo
u
could try restoring a backup on a different machine to try your tests out
before working on live (providing you have the hardware!)
John
"MKBOBBA" wrote:
> We have SQL Server 2005 set up and we are seeing the following error messa
ges
> in our logs from Daily maintenance Plan.
> Please comment on the severity of these errors.
> Thanks,
> mkb
> ========================================
========
> Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[Al
lUserData]
> REBUILD WITH ( PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF,
> ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, SORT_IN_TEMPDB = OFF, ONLIN
E =
> OFF )
> " failed with the following error: "SQL Server detected a logical
> consistency-based I/O error: incorrect pageid (expected 1:2676; actual
> 14616:395852048). It occurred during a read of page (1:2676) in database I
D
> 13 at offset 0x000000014e8000 in file 'C:\\Program Files\\Microsoft SQL
> Server\\MSSQL. 1\\MSSQL\\DATA\\SP_IntranetMySites_WebAp
p.mdf'. Additional
> messages in the SQL Server error log or system event log may provide more
> detail. This is a severe error condition that threatens database integrity
> and must be corrected immediately. Complete a full database consistency ch
eck
> (DBCC CHECKDB). This error can be caused by many factors; for more
> information, see SQL Server Books Online.
> The statement has been terminated.". Possible failure reasons: Problems wi
th
> the query, "ResultSet" property not set correctly, parameters not set
> correctly, or connection not established correctly.
>
> ========================================
===========
> Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[Al
lUserData]
> REORGANIZE WITH ( LOB_COMPACTION = OFF )
> " failed with the following error: "SQL Server detected a logical
> consistency-based I/O error: incorrect pageid (expected 1:2653; actual
> 47686:707280961). It occurred during a read of page (1:2653) in database I
D
> 13 at offset 0x000000014ba000 in file 'C:\\Program Files\\Microsoft SQL
> Server\\MSSQL. 1\\MSSQL\\DATA\\SP_IntranetMySites_WebAp
p.mdf'. Additional
> messages in the SQL Server error log or system event log may provide more
> detail. This is a severe error condition that threatens database integrity
> and must be corrected immediately. Complete a full database consistency ch
eck
> (DBCC CHECKDB). This error can be caused by many factors; for more
> information, see SQL Server Books Online.". Possible failure reasons:
> Problems with the query, "ResultSet" property not set correctly, parameter
s
> not set correctly, or connection not established correctly.
> ========================================
============
> Executing the query "DBCC CHECKDB WITH NO_INFOMSGS
> " failed with the following error: "An internal error occurred in DBCC tha
t
> prevented further processing. Contact Customer Support Services.
> Check terminated. A failure was detected while collecting facts. Possibly
> tempdb out of space or a system table is inconsistent. Check previous
> errors.". Possible failure reasons: Problems with the query, "ResultSet"
> property not set correctly, parameters not set correctly, or connection no
t
> established correctly.
> ========================================
===========
>sql
s
in our logs from Daily maintenance Plan.
Please comment on the severity of these errors.
Thanks,
mkb
========================================
========
Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[AllU
serData]
REBUILD WITH ( PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF,
ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, SORT_IN_TEMPDB = OFF, ONLINE
=
OFF )
" failed with the following error: "SQL Server detected a logical
consistency-based I/O error: incorrect pageid (expected 1:2676; actual
14616:395852048). It occurred during a read of page (1:2676) in database ID
13 at offset 0x000000014e8000 in file 'C:\\Program Files\\Microsoft SQL
Server\\MSSQL. 1\\MSSQL\\DATA\\SP_IntranetMySites_WebAp
p.mdf'. Additional
messages in the SQL Server error log or system event log may provide more
detail. This is a severe error condition that threatens database integrity
and must be corrected immediately. Complete a full database consistency chec
k
(DBCC CHECKDB). This error can be caused by many factors; for more
information, see SQL Server Books Online.
The statement has been terminated.". Possible failure reasons: Problems with
the query, "ResultSet" property not set correctly, parameters not set
correctly, or connection not established correctly.
========================================
===========
Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[AllU
serData]
REORGANIZE WITH ( LOB_COMPACTION = OFF )
" failed with the following error: "SQL Server detected a logical
consistency-based I/O error: incorrect pageid (expected 1:2653; actual
47686:707280961). It occurred during a read of page (1:2653) in database ID
13 at offset 0x000000014ba000 in file 'C:\\Program Files\\Microsoft SQL
Server\\MSSQL. 1\\MSSQL\\DATA\\SP_IntranetMySites_WebAp
p.mdf'. Additional
messages in the SQL Server error log or system event log may provide more
detail. This is a severe error condition that threatens database integrity
and must be corrected immediately. Complete a full database consistency chec
k
(DBCC CHECKDB). This error can be caused by many factors; for more
information, see SQL Server Books Online.". Possible failure reasons:
Problems with the query, "ResultSet" property not set correctly, parameters
not set correctly, or connection not established correctly.
========================================
============
Executing the query "DBCC CHECKDB WITH NO_INFOMSGS
" failed with the following error: "An internal error occurred in DBCC that
prevented further processing. Contact Customer Support Services.
Check terminated. A failure was detected while collecting facts. Possibly
tempdb out of space or a system table is inconsistent. Check previous
errors.". Possible failure reasons: Problems with the query, "ResultSet"
property not set correctly, parameters not set correctly, or connection not
established correctly.
========================================
===========Hi
It seems that there is some corruption in the database. Have you had any
hardware issues? Is there any other information in the SQL Server log or
Windows Event Logs?
You could try dropping the index and running DBCC CHECKDB again. If it works
then re-create the index and run it again. If you don't find out what caused
this then it could happen again.
John
"MKBOBBA" wrote:
> We have SQL Server 2005 set up and we are seeing the following error messa
ges
> in our logs from Daily maintenance Plan.
> Please comment on the severity of these errors.
> Thanks,
> mkb
> ========================================
========
> Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[Al
lUserData]
> REBUILD WITH ( PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF,
> ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, SORT_IN_TEMPDB = OFF, ONLIN
E =
> OFF )
> " failed with the following error: "SQL Server detected a logical
> consistency-based I/O error: incorrect pageid (expected 1:2676; actual
> 14616:395852048). It occurred during a read of page (1:2676) in database I
D
> 13 at offset 0x000000014e8000 in file 'C:\\Program Files\\Microsoft SQL
> Server\\MSSQL. 1\\MSSQL\\DATA\\SP_IntranetMySites_WebAp
p.mdf'. Additional
> messages in the SQL Server error log or system event log may provide more
> detail. This is a severe error condition that threatens database integrity
> and must be corrected immediately. Complete a full database consistency ch
eck
> (DBCC CHECKDB). This error can be caused by many factors; for more
> information, see SQL Server Books Online.
> The statement has been terminated.". Possible failure reasons: Problems wi
th
> the query, "ResultSet" property not set correctly, parameters not set
> correctly, or connection not established correctly.
>
> ========================================
===========
> Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[Al
lUserData]
> REORGANIZE WITH ( LOB_COMPACTION = OFF )
> " failed with the following error: "SQL Server detected a logical
> consistency-based I/O error: incorrect pageid (expected 1:2653; actual
> 47686:707280961). It occurred during a read of page (1:2653) in database I
D
> 13 at offset 0x000000014ba000 in file 'C:\\Program Files\\Microsoft SQL
> Server\\MSSQL. 1\\MSSQL\\DATA\\SP_IntranetMySites_WebAp
p.mdf'. Additional
> messages in the SQL Server error log or system event log may provide more
> detail. This is a severe error condition that threatens database integrity
> and must be corrected immediately. Complete a full database consistency ch
eck
> (DBCC CHECKDB). This error can be caused by many factors; for more
> information, see SQL Server Books Online.". Possible failure reasons:
> Problems with the query, "ResultSet" property not set correctly, parameter
s
> not set correctly, or connection not established correctly.
> ========================================
============
> Executing the query "DBCC CHECKDB WITH NO_INFOMSGS
> " failed with the following error: "An internal error occurred in DBCC tha
t
> prevented further processing. Contact Customer Support Services.
> Check terminated. A failure was detected while collecting facts. Possibly
> tempdb out of space or a system table is inconsistent. Check previous
> errors.". Possible failure reasons: Problems with the query, "ResultSet"
> property not set correctly, parameters not set correctly, or connection no
t
> established correctly.
> ========================================
===========
>|||And I forgot to add.. Make sure you have a good backup before doing this! Yo
u
could try restoring a backup on a different machine to try your tests out
before working on live (providing you have the hardware!)
John
"MKBOBBA" wrote:
> We have SQL Server 2005 set up and we are seeing the following error messa
ges
> in our logs from Daily maintenance Plan.
> Please comment on the severity of these errors.
> Thanks,
> mkb
> ========================================
========
> Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[Al
lUserData]
> REBUILD WITH ( PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF,
> ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, SORT_IN_TEMPDB = OFF, ONLIN
E =
> OFF )
> " failed with the following error: "SQL Server detected a logical
> consistency-based I/O error: incorrect pageid (expected 1:2676; actual
> 14616:395852048). It occurred during a read of page (1:2676) in database I
D
> 13 at offset 0x000000014e8000 in file 'C:\\Program Files\\Microsoft SQL
> Server\\MSSQL. 1\\MSSQL\\DATA\\SP_IntranetMySites_WebAp
p.mdf'. Additional
> messages in the SQL Server error log or system event log may provide more
> detail. This is a severe error condition that threatens database integrity
> and must be corrected immediately. Complete a full database consistency ch
eck
> (DBCC CHECKDB). This error can be caused by many factors; for more
> information, see SQL Server Books Online.
> The statement has been terminated.". Possible failure reasons: Problems wi
th
> the query, "ResultSet" property not set correctly, parameters not set
> correctly, or connection not established correctly.
>
> ========================================
===========
> Executing the query "ALTER INDEX [AllUserData_PK] ON [dbo].[Al
lUserData]
> REORGANIZE WITH ( LOB_COMPACTION = OFF )
> " failed with the following error: "SQL Server detected a logical
> consistency-based I/O error: incorrect pageid (expected 1:2653; actual
> 47686:707280961). It occurred during a read of page (1:2653) in database I
D
> 13 at offset 0x000000014ba000 in file 'C:\\Program Files\\Microsoft SQL
> Server\\MSSQL. 1\\MSSQL\\DATA\\SP_IntranetMySites_WebAp
p.mdf'. Additional
> messages in the SQL Server error log or system event log may provide more
> detail. This is a severe error condition that threatens database integrity
> and must be corrected immediately. Complete a full database consistency ch
eck
> (DBCC CHECKDB). This error can be caused by many factors; for more
> information, see SQL Server Books Online.". Possible failure reasons:
> Problems with the query, "ResultSet" property not set correctly, parameter
s
> not set correctly, or connection not established correctly.
> ========================================
============
> Executing the query "DBCC CHECKDB WITH NO_INFOMSGS
> " failed with the following error: "An internal error occurred in DBCC tha
t
> prevented further processing. Contact Customer Support Services.
> Check terminated. A failure was detected while collecting facts. Possibly
> tempdb out of space or a system table is inconsistent. Check previous
> errors.". Possible failure reasons: Problems with the query, "ResultSet"
> property not set correctly, parameters not set correctly, or connection no
t
> established correctly.
> ========================================
===========
>sql
Sunday, March 11, 2012
Errors in log
The following are errors I found in one of my SQL Server Logs:
Error: 17207, Severity: 16, State: 1.
FCB::RemoveAlternateStreams: Operating system error (null) occurred while
creating or opening file 'C:\Program Files\Microsoft SQL
Server\MSSQL\data\master.mdf'. Diagnose and correct the operating system
error, and retry the operation.
Recovery is writing a checkpoint in database 'master' (1). This is an
informational message only. No user action is required.
CHECKDB for database 'master' finished without errors on 2007-06-12
14:09:11.613 (local time). This is an informational message only; no user
action is required.
I checked the security for master database file and it is ok. Any idea what
could cause this? thanks.
Lijun
On Jun 12, 9:13 pm, "Lijun Zhang" <sonyzhan...@.yahoo.com> wrote:
> The following are errors I found in one of my SQL Server Logs:
> Error: 17207, Severity: 16, State: 1.
> FCB::RemoveAlternateStreams: Operating system error (null) occurred while
> creating or opening file 'C:\Program Files\Microsoft SQL
> Server\MSSQL\data\master.mdf'. Diagnose and correct the operating system
> error, and retry the operation.
> Recovery is writing a checkpoint in database 'master' (1). This is an
> informational message only. No user action is required.
> CHECKDB for database 'master' finished without errors on 2007-06-12
> 14:09:11.613 (local time). This is an informational message only; no user
> action is required.
> I checked the security for master database file and it is ok. Any idea what
> could cause this? thanks.
> Lijun
Hi
Does this error happen regularly?
Other applications accessing the file such as Anti-Virus software can
cause problems similar to this e.g.
https://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=201223&SiteID=1
John
|||Yes. I have to rebuild the master database to solve the problem.
Lijun
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:1181719774.789471.92510@.o11g2000prd.googlegro ups.com...
> On Jun 12, 9:13 pm, "Lijun Zhang" <sonyzhan...@.yahoo.com> wrote:
> Hi
> Does this error happen regularly?
> Other applications accessing the file such as Anti-Virus software can
> cause problems similar to this e.g.
> https://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=201223&SiteID=1
> John
>
|||Hi Lijun
On Jun 13, 8:23 pm, "Lijun Zhang" <sonyzhan...@.yahoo.com> wrote:
> Yes. I have to rebuild the master database to solve the problem.
> Lijun
> "John Bell" <jbellnewspo...@.hotmail.com> wrote in message
> news:1181719774.789471.92510@.o11g2000prd.googlegro ups.com...
That seems quite drastic as the message is only a warning and CHECKDB
returned no errors! Do you know what the cause was?
John
|||No. I don't know what is the cause.
Lijun
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:1181805578.143092.163530@.n15g2000prd.googlegr oups.com...
> Hi Lijun
> On Jun 13, 8:23 pm, "Lijun Zhang" <sonyzhan...@.yahoo.com> wrote:
> That seems quite drastic as the message is only a warning and CHECKDB
> returned no errors! Do you know what the cause was?
> John
>
Error: 17207, Severity: 16, State: 1.
FCB::RemoveAlternateStreams: Operating system error (null) occurred while
creating or opening file 'C:\Program Files\Microsoft SQL
Server\MSSQL\data\master.mdf'. Diagnose and correct the operating system
error, and retry the operation.
Recovery is writing a checkpoint in database 'master' (1). This is an
informational message only. No user action is required.
CHECKDB for database 'master' finished without errors on 2007-06-12
14:09:11.613 (local time). This is an informational message only; no user
action is required.
I checked the security for master database file and it is ok. Any idea what
could cause this? thanks.
Lijun
On Jun 12, 9:13 pm, "Lijun Zhang" <sonyzhan...@.yahoo.com> wrote:
> The following are errors I found in one of my SQL Server Logs:
> Error: 17207, Severity: 16, State: 1.
> FCB::RemoveAlternateStreams: Operating system error (null) occurred while
> creating or opening file 'C:\Program Files\Microsoft SQL
> Server\MSSQL\data\master.mdf'. Diagnose and correct the operating system
> error, and retry the operation.
> Recovery is writing a checkpoint in database 'master' (1). This is an
> informational message only. No user action is required.
> CHECKDB for database 'master' finished without errors on 2007-06-12
> 14:09:11.613 (local time). This is an informational message only; no user
> action is required.
> I checked the security for master database file and it is ok. Any idea what
> could cause this? thanks.
> Lijun
Hi
Does this error happen regularly?
Other applications accessing the file such as Anti-Virus software can
cause problems similar to this e.g.
https://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=201223&SiteID=1
John
|||Yes. I have to rebuild the master database to solve the problem.
Lijun
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:1181719774.789471.92510@.o11g2000prd.googlegro ups.com...
> On Jun 12, 9:13 pm, "Lijun Zhang" <sonyzhan...@.yahoo.com> wrote:
> Hi
> Does this error happen regularly?
> Other applications accessing the file such as Anti-Virus software can
> cause problems similar to this e.g.
> https://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=201223&SiteID=1
> John
>
|||Hi Lijun
On Jun 13, 8:23 pm, "Lijun Zhang" <sonyzhan...@.yahoo.com> wrote:
> Yes. I have to rebuild the master database to solve the problem.
> Lijun
> "John Bell" <jbellnewspo...@.hotmail.com> wrote in message
> news:1181719774.789471.92510@.o11g2000prd.googlegro ups.com...
That seems quite drastic as the message is only a warning and CHECKDB
returned no errors! Do you know what the cause was?
John
|||No. I don't know what is the cause.
Lijun
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:1181805578.143092.163530@.n15g2000prd.googlegr oups.com...
> Hi Lijun
> On Jun 13, 8:23 pm, "Lijun Zhang" <sonyzhan...@.yahoo.com> wrote:
> That seems quite drastic as the message is only a warning and CHECKDB
> returned no errors! Do you know what the cause was?
> John
>
Errors in log
The following are errors I found in one of my SQL Server Logs:
Error: 17207, Severity: 16, State: 1.
FCB::RemoveAlternateStreams: Operating system error (null) occurred while
creating or opening file 'C:\Program Files\Microsoft SQL
Server\MSSQL\data\master.mdf'. Diagnose and correct the operating system
error, and retry the operation.
Recovery is writing a checkpoint in database 'master' (1). This is an
informational message only. No user action is required.
CHECKDB for database 'master' finished without errors on 2007-06-12
14:09:11.613 (local time). This is an informational message only; no user
action is required.
I checked the security for master database file and it is ok. Any idea what
could cause this? thanks.
LijunOn Jun 12, 9:13 pm, "Lijun Zhang" <sonyzhan...@.yahoo.com> wrote:
> The following are errors I found in one of my SQL Server Logs:
> Error: 17207, Severity: 16, State: 1.
> FCB::RemoveAlternateStreams: Operating system error (null) occurred while
> creating or opening file 'C:\Program Files\Microsoft SQL
> Server\MSSQL\data\master.mdf'. Diagnose and correct the operating system
> error, and retry the operation.
> Recovery is writing a checkpoint in database 'master' (1). This is an
> informational message only. No user action is required.
> CHECKDB for database 'master' finished without errors on 2007-06-12
> 14:09:11.613 (local time). This is an informational message only; no user
> action is required.
> I checked the security for master database file and it is ok. Any idea what
> could cause this? thanks.
> Lijun
Hi
Does this error happen regularly?
Other applications accessing the file such as Anti-Virus software can
cause problems similar to this e.g.
https://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=201223&SiteID=1
John|||Yes. I have to rebuild the master database to solve the problem.
Lijun
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:1181719774.789471.92510@.o11g2000prd.googlegroups.com...
> On Jun 12, 9:13 pm, "Lijun Zhang" <sonyzhan...@.yahoo.com> wrote:
>> The following are errors I found in one of my SQL Server Logs:
>> Error: 17207, Severity: 16, State: 1.
>> FCB::RemoveAlternateStreams: Operating system error (null) occurred while
>> creating or opening file 'C:\Program Files\Microsoft SQL
>> Server\MSSQL\data\master.mdf'. Diagnose and correct the operating system
>> error, and retry the operation.
>> Recovery is writing a checkpoint in database 'master' (1). This is an
>> informational message only. No user action is required.
>> CHECKDB for database 'master' finished without errors on 2007-06-12
>> 14:09:11.613 (local time). This is an informational message only; no user
>> action is required.
>> I checked the security for master database file and it is ok. Any idea
>> what
>> could cause this? thanks.
>> Lijun
> Hi
> Does this error happen regularly?
> Other applications accessing the file such as Anti-Virus software can
> cause problems similar to this e.g.
> https://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=201223&SiteID=1
> John
>|||Hi Lijun
On Jun 13, 8:23 pm, "Lijun Zhang" <sonyzhan...@.yahoo.com> wrote:
> Yes. I have to rebuild the master database to solve the problem.
> Lijun
> "John Bell" <jbellnewspo...@.hotmail.com> wrote in message
> news:1181719774.789471.92510@.o11g2000prd.googlegroups.com...
That seems quite drastic as the message is only a warning and CHECKDB
returned no errors! Do you know what the cause was?
John|||No. I don't know what is the cause.
Lijun
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:1181805578.143092.163530@.n15g2000prd.googlegroups.com...
> Hi Lijun
> On Jun 13, 8:23 pm, "Lijun Zhang" <sonyzhan...@.yahoo.com> wrote:
>> Yes. I have to rebuild the master database to solve the problem.
>> Lijun
>> "John Bell" <jbellnewspo...@.hotmail.com> wrote in message
>> news:1181719774.789471.92510@.o11g2000prd.googlegroups.com...
> That seems quite drastic as the message is only a warning and CHECKDB
> returned no errors! Do you know what the cause was?
> John
>
Error: 17207, Severity: 16, State: 1.
FCB::RemoveAlternateStreams: Operating system error (null) occurred while
creating or opening file 'C:\Program Files\Microsoft SQL
Server\MSSQL\data\master.mdf'. Diagnose and correct the operating system
error, and retry the operation.
Recovery is writing a checkpoint in database 'master' (1). This is an
informational message only. No user action is required.
CHECKDB for database 'master' finished without errors on 2007-06-12
14:09:11.613 (local time). This is an informational message only; no user
action is required.
I checked the security for master database file and it is ok. Any idea what
could cause this? thanks.
LijunOn Jun 12, 9:13 pm, "Lijun Zhang" <sonyzhan...@.yahoo.com> wrote:
> The following are errors I found in one of my SQL Server Logs:
> Error: 17207, Severity: 16, State: 1.
> FCB::RemoveAlternateStreams: Operating system error (null) occurred while
> creating or opening file 'C:\Program Files\Microsoft SQL
> Server\MSSQL\data\master.mdf'. Diagnose and correct the operating system
> error, and retry the operation.
> Recovery is writing a checkpoint in database 'master' (1). This is an
> informational message only. No user action is required.
> CHECKDB for database 'master' finished without errors on 2007-06-12
> 14:09:11.613 (local time). This is an informational message only; no user
> action is required.
> I checked the security for master database file and it is ok. Any idea what
> could cause this? thanks.
> Lijun
Hi
Does this error happen regularly?
Other applications accessing the file such as Anti-Virus software can
cause problems similar to this e.g.
https://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=201223&SiteID=1
John|||Yes. I have to rebuild the master database to solve the problem.
Lijun
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:1181719774.789471.92510@.o11g2000prd.googlegroups.com...
> On Jun 12, 9:13 pm, "Lijun Zhang" <sonyzhan...@.yahoo.com> wrote:
>> The following are errors I found in one of my SQL Server Logs:
>> Error: 17207, Severity: 16, State: 1.
>> FCB::RemoveAlternateStreams: Operating system error (null) occurred while
>> creating or opening file 'C:\Program Files\Microsoft SQL
>> Server\MSSQL\data\master.mdf'. Diagnose and correct the operating system
>> error, and retry the operation.
>> Recovery is writing a checkpoint in database 'master' (1). This is an
>> informational message only. No user action is required.
>> CHECKDB for database 'master' finished without errors on 2007-06-12
>> 14:09:11.613 (local time). This is an informational message only; no user
>> action is required.
>> I checked the security for master database file and it is ok. Any idea
>> what
>> could cause this? thanks.
>> Lijun
> Hi
> Does this error happen regularly?
> Other applications accessing the file such as Anti-Virus software can
> cause problems similar to this e.g.
> https://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=201223&SiteID=1
> John
>|||Hi Lijun
On Jun 13, 8:23 pm, "Lijun Zhang" <sonyzhan...@.yahoo.com> wrote:
> Yes. I have to rebuild the master database to solve the problem.
> Lijun
> "John Bell" <jbellnewspo...@.hotmail.com> wrote in message
> news:1181719774.789471.92510@.o11g2000prd.googlegroups.com...
That seems quite drastic as the message is only a warning and CHECKDB
returned no errors! Do you know what the cause was?
John|||No. I don't know what is the cause.
Lijun
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:1181805578.143092.163530@.n15g2000prd.googlegroups.com...
> Hi Lijun
> On Jun 13, 8:23 pm, "Lijun Zhang" <sonyzhan...@.yahoo.com> wrote:
>> Yes. I have to rebuild the master database to solve the problem.
>> Lijun
>> "John Bell" <jbellnewspo...@.hotmail.com> wrote in message
>> news:1181719774.789471.92510@.o11g2000prd.googlegroups.com...
> That seems quite drastic as the message is only a warning and CHECKDB
> returned no errors! Do you know what the cause was?
> John
>
Errors in log
The following are errors I found in one of my SQL Server Logs:
Error: 17207, Severity: 16, State: 1.
FCB::RemoveAlternateStreams: Operating system error (null) occurred while
creating or opening file 'C:\Program Files\Microsoft SQL
Server\MSSQL\data\master.mdf'. Diagnose and correct the operating system
error, and retry the operation.
Recovery is writing a checkpoint in database 'master' (1). This is an
informational message only. No user action is required.
CHECKDB for database 'master' finished without errors on 2007-06-12
14:09:11.613 (local time). This is an informational message only; no user
action is required.
I checked the security for master database file and it is ok. Any idea what
could cause this? thanks.
LijunOn Jun 12, 9:13 pm, "Lijun Zhang" <sonyzhan...@.yahoo.com> wrote:
> The following are errors I found in one of my SQL Server Logs:
> Error: 17207, Severity: 16, State: 1.
> FCB::RemoveAlternateStreams: Operating system error (null) occurred while
> creating or opening file 'C:\Program Files\Microsoft SQL
> Server\MSSQL\data\master.mdf'. Diagnose and correct the operating system
> error, and retry the operation.
> Recovery is writing a checkpoint in database 'master' (1). This is an
> informational message only. No user action is required.
> CHECKDB for database 'master' finished without errors on 2007-06-12
> 14:09:11.613 (local time). This is an informational message only; no user
> action is required.
> I checked the security for master database file and it is ok. Any idea wha
t
> could cause this? thanks.
> Lijun
Hi
Does this error happen regularly?
Other applications accessing the file such as Anti-Virus software can
cause problems similar to this e.g.
https://forums.microsoft.com/MSDN/S...201223&SiteID=1
John|||Yes. I have to rebuild the master database to solve the problem.
Lijun
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:1181719774.789471.92510@.o11g2000prd.googlegroups.com...
> On Jun 12, 9:13 pm, "Lijun Zhang" <sonyzhan...@.yahoo.com> wrote:
> Hi
> Does this error happen regularly?
> Other applications accessing the file such as Anti-Virus software can
> cause problems similar to this e.g.
> https://forums.microsoft.com/MSDN/S...201223&SiteID=1
> John
>|||Hi Lijun
On Jun 13, 8:23 pm, "Lijun Zhang" <sonyzhan...@.yahoo.com> wrote:
> Yes. I have to rebuild the master database to solve the problem.
> Lijun
> "John Bell" <jbellnewspo...@.hotmail.com> wrote in message
> news:1181719774.789471.92510@.o11g2000prd.googlegroups.com...
That seems quite drastic as the message is only a warning and CHECKDB
returned no errors! Do you know what the cause was?
John|||No. I don't know what is the cause.
Lijun
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:1181805578.143092.163530@.n15g2000prd.googlegroups.com...
> Hi Lijun
> On Jun 13, 8:23 pm, "Lijun Zhang" <sonyzhan...@.yahoo.com> wrote:
> That seems quite drastic as the message is only a warning and CHECKDB
> returned no errors! Do you know what the cause was?
> John
>
Error: 17207, Severity: 16, State: 1.
FCB::RemoveAlternateStreams: Operating system error (null) occurred while
creating or opening file 'C:\Program Files\Microsoft SQL
Server\MSSQL\data\master.mdf'. Diagnose and correct the operating system
error, and retry the operation.
Recovery is writing a checkpoint in database 'master' (1). This is an
informational message only. No user action is required.
CHECKDB for database 'master' finished without errors on 2007-06-12
14:09:11.613 (local time). This is an informational message only; no user
action is required.
I checked the security for master database file and it is ok. Any idea what
could cause this? thanks.
LijunOn Jun 12, 9:13 pm, "Lijun Zhang" <sonyzhan...@.yahoo.com> wrote:
> The following are errors I found in one of my SQL Server Logs:
> Error: 17207, Severity: 16, State: 1.
> FCB::RemoveAlternateStreams: Operating system error (null) occurred while
> creating or opening file 'C:\Program Files\Microsoft SQL
> Server\MSSQL\data\master.mdf'. Diagnose and correct the operating system
> error, and retry the operation.
> Recovery is writing a checkpoint in database 'master' (1). This is an
> informational message only. No user action is required.
> CHECKDB for database 'master' finished without errors on 2007-06-12
> 14:09:11.613 (local time). This is an informational message only; no user
> action is required.
> I checked the security for master database file and it is ok. Any idea wha
t
> could cause this? thanks.
> Lijun
Hi
Does this error happen regularly?
Other applications accessing the file such as Anti-Virus software can
cause problems similar to this e.g.
https://forums.microsoft.com/MSDN/S...201223&SiteID=1
John|||Yes. I have to rebuild the master database to solve the problem.
Lijun
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:1181719774.789471.92510@.o11g2000prd.googlegroups.com...
> On Jun 12, 9:13 pm, "Lijun Zhang" <sonyzhan...@.yahoo.com> wrote:
> Hi
> Does this error happen regularly?
> Other applications accessing the file such as Anti-Virus software can
> cause problems similar to this e.g.
> https://forums.microsoft.com/MSDN/S...201223&SiteID=1
> John
>|||Hi Lijun
On Jun 13, 8:23 pm, "Lijun Zhang" <sonyzhan...@.yahoo.com> wrote:
> Yes. I have to rebuild the master database to solve the problem.
> Lijun
> "John Bell" <jbellnewspo...@.hotmail.com> wrote in message
> news:1181719774.789471.92510@.o11g2000prd.googlegroups.com...
That seems quite drastic as the message is only a warning and CHECKDB
returned no errors! Do you know what the cause was?
John|||No. I don't know what is the cause.
Lijun
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:1181805578.143092.163530@.n15g2000prd.googlegroups.com...
> Hi Lijun
> On Jun 13, 8:23 pm, "Lijun Zhang" <sonyzhan...@.yahoo.com> wrote:
> That seems quite drastic as the message is only a warning and CHECKDB
> returned no errors! Do you know what the cause was?
> John
>
Errors from DBCC CHECKDB not caught by CATCH
I'm having problems catching errors from DBCC CHECKDB even though the errors
have a severity level above 10. I'm using the "broken" database created by
Paul Randal,
http://blogs.msdn.com/sqlserverstorageengine/archive/2007/04/17/example-corrupt-database-to-play-with.aspx (see the zip file at the end).
Even though a "DBCC CHECKDB (broken)" results in two errors with severity
level 16 the following code will never end up in the CATCH block..
BEGIN TRY
DBCC CHECKDB(broken)
END TRY
BEGIN CATCH
SELECT
ERROR_NUMBER() AS ErrorNumber,
ERROR_SEVERITY() AS ErrorSeverity,
ERROR_STATE() AS ErrorState,
ERROR_PROCEDURE() AS ErrorProcedure,
ERROR_LINE() AS ErrorLine,
ERROR_MESSAGE() AS ErrorMessage;
END CATCH
Does anyone know if this is by design or a bug? I'm using SQL Server 2005
with Service Pack 2.Hi Allan,
I've reported it on connect as a bug.
Use @.@.ERROR instead and don't use BEGIN TRY.
The CATCH is never reached, in fact - if you using BEGIN TRY and DBCC
CHECKDB fails then it stays in the BEGIN block and if you check @.@.ERROR its
actually 0!
Tony.
--
Tony Rogerson, SQL Server MVP
http://sqlblogcasts.com/blogs/tonyrogerson
[Ramblings from the field from a SQL consultant]
http://sqlserverfaq.com
[UK SQL User Community]
"Allan" <allan@.newsgroups.nospam> wrote in message
news:B2E2D4EC-7F2D-434C-9F0C-AEA328C57188@.microsoft.com...
> I'm having problems catching errors from DBCC CHECKDB even though the
> errors
> have a severity level above 10. I'm using the "broken" database created by
> Paul Randal,
> http://blogs.msdn.com/sqlserverstorageengine/archive/2007/04/17/example-corrupt-database-to-play-with.aspx
> (see the zip file at the end).
> Even though a "DBCC CHECKDB (broken)" results in two errors with severity
> level 16 the following code will never end up in the CATCH block..
> BEGIN TRY
> DBCC CHECKDB(broken)
> END TRY
> BEGIN CATCH
> SELECT
> ERROR_NUMBER() AS ErrorNumber,
> ERROR_SEVERITY() AS ErrorSeverity,
> ERROR_STATE() AS ErrorState,
> ERROR_PROCEDURE() AS ErrorProcedure,
> ERROR_LINE() AS ErrorLine,
> ERROR_MESSAGE() AS ErrorMessage;
> END CATCH
> Does anyone know if this is by design or a bug? I'm using SQL Server 2005
> with Service Pack 2.
have a severity level above 10. I'm using the "broken" database created by
Paul Randal,
http://blogs.msdn.com/sqlserverstorageengine/archive/2007/04/17/example-corrupt-database-to-play-with.aspx (see the zip file at the end).
Even though a "DBCC CHECKDB (broken)" results in two errors with severity
level 16 the following code will never end up in the CATCH block..
BEGIN TRY
DBCC CHECKDB(broken)
END TRY
BEGIN CATCH
SELECT
ERROR_NUMBER() AS ErrorNumber,
ERROR_SEVERITY() AS ErrorSeverity,
ERROR_STATE() AS ErrorState,
ERROR_PROCEDURE() AS ErrorProcedure,
ERROR_LINE() AS ErrorLine,
ERROR_MESSAGE() AS ErrorMessage;
END CATCH
Does anyone know if this is by design or a bug? I'm using SQL Server 2005
with Service Pack 2.Hi Allan,
I've reported it on connect as a bug.
Use @.@.ERROR instead and don't use BEGIN TRY.
The CATCH is never reached, in fact - if you using BEGIN TRY and DBCC
CHECKDB fails then it stays in the BEGIN block and if you check @.@.ERROR its
actually 0!
Tony.
--
Tony Rogerson, SQL Server MVP
http://sqlblogcasts.com/blogs/tonyrogerson
[Ramblings from the field from a SQL consultant]
http://sqlserverfaq.com
[UK SQL User Community]
"Allan" <allan@.newsgroups.nospam> wrote in message
news:B2E2D4EC-7F2D-434C-9F0C-AEA328C57188@.microsoft.com...
> I'm having problems catching errors from DBCC CHECKDB even though the
> errors
> have a severity level above 10. I'm using the "broken" database created by
> Paul Randal,
> http://blogs.msdn.com/sqlserverstorageengine/archive/2007/04/17/example-corrupt-database-to-play-with.aspx
> (see the zip file at the end).
> Even though a "DBCC CHECKDB (broken)" results in two errors with severity
> level 16 the following code will never end up in the CATCH block..
> BEGIN TRY
> DBCC CHECKDB(broken)
> END TRY
> BEGIN CATCH
> SELECT
> ERROR_NUMBER() AS ErrorNumber,
> ERROR_SEVERITY() AS ErrorSeverity,
> ERROR_STATE() AS ErrorState,
> ERROR_PROCEDURE() AS ErrorProcedure,
> ERROR_LINE() AS ErrorLine,
> ERROR_MESSAGE() AS ErrorMessage;
> END CATCH
> Does anyone know if this is by design or a bug? I'm using SQL Server 2005
> with Service Pack 2.
Friday, March 9, 2012
Errors from DBCC CHECKDB not caught by CATCH
I'm having problems catching errors from DBCC CHECKDB even though the errors
have a severity level above 10. I'm using the "broken" database created by
Paul Randal,
http://blogs.msdn.com/sqlserverstor...-play-with.aspx (see the zip file at the end).
Even though a "DBCC CHECKDB (broken)" results in two errors with severity
level 16 the following code will never end up in the CATCH block..
BEGIN TRY
DBCC CHECKDB(broken)
END TRY
BEGIN CATCH
SELECT
ERROR_NUMBER() AS ErrorNumber,
ERROR_SEVERITY() AS ErrorSeverity,
ERROR_STATE() AS ErrorState,
ERROR_PROCEDURE() AS ErrorProcedure,
ERROR_LINE() AS ErrorLine,
ERROR_MESSAGE() AS ErrorMessage;
END CATCH
Does anyone know if this is by design or a bug? I'm using SQL Server 2005
with Service Pack 2.Hi Allan,
I've reported it on connect as a bug.
Use @.@.ERROR instead and don't use BEGIN TRY.
The CATCH is never reached, in fact - if you using BEGIN TRY and DBCC
CHECKDB fails then it stays in the BEGIN block and if you check @.@.ERROR its
actually 0!
Tony.
Tony Rogerson, SQL Server MVP
http://sqlblogcasts.com/blogs/tonyrogerson
[Ramblings from the field from a SQL consultant]
http://sqlserverfaq.com
[UK SQL User Community]
"Allan" <allan@.newsgroups.nospam> wrote in message
news:B2E2D4EC-7F2D-434C-9F0C-AEA328C57188@.microsoft.com...
> I'm having problems catching errors from DBCC CHECKDB even though the
> errors
> have a severity level above 10. I'm using the "broken" database created by
> Paul Randal,
> http://blogs.msdn.com/sqlserverstor...-play-with.aspx
> (see the zip file at the end).
> Even though a "DBCC CHECKDB (broken)" results in two errors with severity
> level 16 the following code will never end up in the CATCH block..
> BEGIN TRY
> DBCC CHECKDB(broken)
> END TRY
> BEGIN CATCH
> SELECT
> ERROR_NUMBER() AS ErrorNumber,
> ERROR_SEVERITY() AS ErrorSeverity,
> ERROR_STATE() AS ErrorState,
> ERROR_PROCEDURE() AS ErrorProcedure,
> ERROR_LINE() AS ErrorLine,
> ERROR_MESSAGE() AS ErrorMessage;
> END CATCH
> Does anyone know if this is by design or a bug? I'm using SQL Server 2005
> with Service Pack 2.
have a severity level above 10. I'm using the "broken" database created by
Paul Randal,
http://blogs.msdn.com/sqlserverstor...-play-with.aspx (see the zip file at the end).
Even though a "DBCC CHECKDB (broken)" results in two errors with severity
level 16 the following code will never end up in the CATCH block..
BEGIN TRY
DBCC CHECKDB(broken)
END TRY
BEGIN CATCH
SELECT
ERROR_NUMBER() AS ErrorNumber,
ERROR_SEVERITY() AS ErrorSeverity,
ERROR_STATE() AS ErrorState,
ERROR_PROCEDURE() AS ErrorProcedure,
ERROR_LINE() AS ErrorLine,
ERROR_MESSAGE() AS ErrorMessage;
END CATCH
Does anyone know if this is by design or a bug? I'm using SQL Server 2005
with Service Pack 2.Hi Allan,
I've reported it on connect as a bug.
Use @.@.ERROR instead and don't use BEGIN TRY.
The CATCH is never reached, in fact - if you using BEGIN TRY and DBCC
CHECKDB fails then it stays in the BEGIN block and if you check @.@.ERROR its
actually 0!
Tony.
Tony Rogerson, SQL Server MVP
http://sqlblogcasts.com/blogs/tonyrogerson
[Ramblings from the field from a SQL consultant]
http://sqlserverfaq.com
[UK SQL User Community]
"Allan" <allan@.newsgroups.nospam> wrote in message
news:B2E2D4EC-7F2D-434C-9F0C-AEA328C57188@.microsoft.com...
> I'm having problems catching errors from DBCC CHECKDB even though the
> errors
> have a severity level above 10. I'm using the "broken" database created by
> Paul Randal,
> http://blogs.msdn.com/sqlserverstor...-play-with.aspx
> (see the zip file at the end).
> Even though a "DBCC CHECKDB (broken)" results in two errors with severity
> level 16 the following code will never end up in the CATCH block..
> BEGIN TRY
> DBCC CHECKDB(broken)
> END TRY
> BEGIN CATCH
> SELECT
> ERROR_NUMBER() AS ErrorNumber,
> ERROR_SEVERITY() AS ErrorSeverity,
> ERROR_STATE() AS ErrorState,
> ERROR_PROCEDURE() AS ErrorProcedure,
> ERROR_LINE() AS ErrorLine,
> ERROR_MESSAGE() AS ErrorMessage;
> END CATCH
> Does anyone know if this is by design or a bug? I'm using SQL Server 2005
> with Service Pack 2.
errors 17825 17059
I have a box with three instances on it one instance is getting the following
messages,
2004-09-23 14:06:58.55 server Error: 17825, Severity: 18, State: 4
2004-09-23 14:06:58.55 server Could not close Net-Library ''..
2004-09-23 14:06:58.55 server Error: 17059, Severity: 18, State: 0
2004-09-23 14:06:58.55 server Operating system error 10093: Either the
application has not called WSAStartup, or WSAStartup failed...
It seems remote logins will not connect but local logins will work. The only
why I found to correct this is stop/start the sql service for the instance.
These errors have just recently started and I am not aware of any changes
made or software installed on this box. I have not found much information on
these errors. Has any seen this before? What did you do to correct?
Thanks,
Dave
I don't know anything specific about the last 2 errors. The first (10093)
indicates that "server" has a socket problem. Specifically, the instance
failed to initialize the winsock library prior to attempting to utilize any
socket functions. That would explain why remote users can't connect. Don't
know what the solution is - the problem appears to lie in the networking
layer (perhaps a configuration issue).
"daproud" <daproud@.discussions.microsoft.com> wrote in message
news:82D2DE52-6F07-4BBF-805C-9D7898D36F40@.microsoft.com...
> I have a box with three instances on it one instance is getting the
following
> messages,
> 2004-09-23 14:06:58.55 server Error: 17825, Severity: 18, State: 4
> 2004-09-23 14:06:58.55 server Could not close Net-Library ''..
> 2004-09-23 14:06:58.55 server Error: 17059, Severity: 18, State: 0
> 2004-09-23 14:06:58.55 server Operating system error 10093: Either the
> application has not called WSAStartup, or WSAStartup failed...
> It seems remote logins will not connect but local logins will work. The
only
> why I found to correct this is stop/start the sql service for the
instance.
> These errors have just recently started and I am not aware of any changes
> made or software installed on this box. I have not found much information
on
> these errors. Has any seen this before? What did you do to correct?
> Thanks,
> Dave
messages,
2004-09-23 14:06:58.55 server Error: 17825, Severity: 18, State: 4
2004-09-23 14:06:58.55 server Could not close Net-Library ''..
2004-09-23 14:06:58.55 server Error: 17059, Severity: 18, State: 0
2004-09-23 14:06:58.55 server Operating system error 10093: Either the
application has not called WSAStartup, or WSAStartup failed...
It seems remote logins will not connect but local logins will work. The only
why I found to correct this is stop/start the sql service for the instance.
These errors have just recently started and I am not aware of any changes
made or software installed on this box. I have not found much information on
these errors. Has any seen this before? What did you do to correct?
Thanks,
Dave
I don't know anything specific about the last 2 errors. The first (10093)
indicates that "server" has a socket problem. Specifically, the instance
failed to initialize the winsock library prior to attempting to utilize any
socket functions. That would explain why remote users can't connect. Don't
know what the solution is - the problem appears to lie in the networking
layer (perhaps a configuration issue).
"daproud" <daproud@.discussions.microsoft.com> wrote in message
news:82D2DE52-6F07-4BBF-805C-9D7898D36F40@.microsoft.com...
> I have a box with three instances on it one instance is getting the
following
> messages,
> 2004-09-23 14:06:58.55 server Error: 17825, Severity: 18, State: 4
> 2004-09-23 14:06:58.55 server Could not close Net-Library ''..
> 2004-09-23 14:06:58.55 server Error: 17059, Severity: 18, State: 0
> 2004-09-23 14:06:58.55 server Operating system error 10093: Either the
> application has not called WSAStartup, or WSAStartup failed...
> It seems remote logins will not connect but local logins will work. The
only
> why I found to correct this is stop/start the sql service for the
instance.
> These errors have just recently started and I am not aware of any changes
> made or software installed on this box. I have not found much information
on
> these errors. Has any seen this before? What did you do to correct?
> Thanks,
> Dave
Friday, February 24, 2012
Error: The Scheduler 83 appears to be hung.
What could cause the error message listed below.
Thanks,
2004-10-22 04:14:50.31 server Error: 17883, Severity: 1, State: 0
2004-10-22 04:14:50.31 server The Scheduler 83 appears to be hung. SPID
0, ECID 2812, UMS Context 0x07B9A6F0.
2004-10-22 04:18:50.30 server Error: 17883, Severity: 1, State: 0
2004-10-22 04:18:50.30 server The Scheduler 83 appears to be hung. SPID
0, ECID 2812, UMS Context 0x07B9A6F0.
2004-10-22 04:20:50.30 server Error: 17883, Severity: 1, State: 0
2004-10-22 04:20:50.30 server The Scheduler 83 appears to be hung. SPID
0, ECID 2812, UMS Context 0x07B9A6F0.
2004-10-22 04:26:50.28 server Error: 17883, Severity: 1, State: 0
2004-10-22 04:26:50.28 server The Scheduler 83 appears to be hung. SPID
0, ECID 2812, UMS Context 0x07B9A6F0.
2004-10-22 04:28:50.28 server Error: 17883, Severity: 1, State: 0
2004-10-22 04:28:50.28 server The Scheduler 83 appears to be hung. SPID
0, ECID 2812, UMS Context 0x07B9A6F0.Hi
Have a look at http://support.microsoft.com/default.aspx?scid=kb;en-us;810885
If that dose not solve your problem, what SQL Server version and hotfix
level (select @.@.version) ar e you on?
Regards
Mike
"Joe K." wrote:
> What could cause the error message listed below.
> Thanks,
> 2004-10-22 04:14:50.31 server Error: 17883, Severity: 1, State: 0
> 2004-10-22 04:14:50.31 server The Scheduler 83 appears to be hung. SPID
> 0, ECID 2812, UMS Context 0x07B9A6F0.
> 2004-10-22 04:18:50.30 server Error: 17883, Severity: 1, State: 0
> 2004-10-22 04:18:50.30 server The Scheduler 83 appears to be hung. SPID
> 0, ECID 2812, UMS Context 0x07B9A6F0.
> 2004-10-22 04:20:50.30 server Error: 17883, Severity: 1, State: 0
> 2004-10-22 04:20:50.30 server The Scheduler 83 appears to be hung. SPID
> 0, ECID 2812, UMS Context 0x07B9A6F0.
> 2004-10-22 04:26:50.28 server Error: 17883, Severity: 1, State: 0
> 2004-10-22 04:26:50.28 server The Scheduler 83 appears to be hung. SPID
> 0, ECID 2812, UMS Context 0x07B9A6F0.
> 2004-10-22 04:28:50.28 server Error: 17883, Severity: 1, State: 0
> 2004-10-22 04:28:50.28 server The Scheduler 83 appears to be hung. SPID
> 0, ECID 2812, UMS Context 0x07B9A6F0.
Thanks,
2004-10-22 04:14:50.31 server Error: 17883, Severity: 1, State: 0
2004-10-22 04:14:50.31 server The Scheduler 83 appears to be hung. SPID
0, ECID 2812, UMS Context 0x07B9A6F0.
2004-10-22 04:18:50.30 server Error: 17883, Severity: 1, State: 0
2004-10-22 04:18:50.30 server The Scheduler 83 appears to be hung. SPID
0, ECID 2812, UMS Context 0x07B9A6F0.
2004-10-22 04:20:50.30 server Error: 17883, Severity: 1, State: 0
2004-10-22 04:20:50.30 server The Scheduler 83 appears to be hung. SPID
0, ECID 2812, UMS Context 0x07B9A6F0.
2004-10-22 04:26:50.28 server Error: 17883, Severity: 1, State: 0
2004-10-22 04:26:50.28 server The Scheduler 83 appears to be hung. SPID
0, ECID 2812, UMS Context 0x07B9A6F0.
2004-10-22 04:28:50.28 server Error: 17883, Severity: 1, State: 0
2004-10-22 04:28:50.28 server The Scheduler 83 appears to be hung. SPID
0, ECID 2812, UMS Context 0x07B9A6F0.Hi
Have a look at http://support.microsoft.com/default.aspx?scid=kb;en-us;810885
If that dose not solve your problem, what SQL Server version and hotfix
level (select @.@.version) ar e you on?
Regards
Mike
"Joe K." wrote:
> What could cause the error message listed below.
> Thanks,
> 2004-10-22 04:14:50.31 server Error: 17883, Severity: 1, State: 0
> 2004-10-22 04:14:50.31 server The Scheduler 83 appears to be hung. SPID
> 0, ECID 2812, UMS Context 0x07B9A6F0.
> 2004-10-22 04:18:50.30 server Error: 17883, Severity: 1, State: 0
> 2004-10-22 04:18:50.30 server The Scheduler 83 appears to be hung. SPID
> 0, ECID 2812, UMS Context 0x07B9A6F0.
> 2004-10-22 04:20:50.30 server Error: 17883, Severity: 1, State: 0
> 2004-10-22 04:20:50.30 server The Scheduler 83 appears to be hung. SPID
> 0, ECID 2812, UMS Context 0x07B9A6F0.
> 2004-10-22 04:26:50.28 server Error: 17883, Severity: 1, State: 0
> 2004-10-22 04:26:50.28 server The Scheduler 83 appears to be hung. SPID
> 0, ECID 2812, UMS Context 0x07B9A6F0.
> 2004-10-22 04:28:50.28 server Error: 17883, Severity: 1, State: 0
> 2004-10-22 04:28:50.28 server The Scheduler 83 appears to be hung. SPID
> 0, ECID 2812, UMS Context 0x07B9A6F0.
Sunday, February 19, 2012
Error: The Scheduler 83 appears to be hung.
What could cause the error message listed below.
Thanks,
2004-10-22 04:14:50.31 server Error: 17883, Severity: 1, State: 0
2004-10-22 04:14:50.31 server The Scheduler 83 appears to be hung. SPID
0, ECID 2812, UMS Context 0x07B9A6F0.
2004-10-22 04:18:50.30 server Error: 17883, Severity: 1, State: 0
2004-10-22 04:18:50.30 server The Scheduler 83 appears to be hung. SPID
0, ECID 2812, UMS Context 0x07B9A6F0.
2004-10-22 04:20:50.30 server Error: 17883, Severity: 1, State: 0
2004-10-22 04:20:50.30 server The Scheduler 83 appears to be hung. SPID
0, ECID 2812, UMS Context 0x07B9A6F0.
2004-10-22 04:26:50.28 server Error: 17883, Severity: 1, State: 0
2004-10-22 04:26:50.28 server The Scheduler 83 appears to be hung. SPID
0, ECID 2812, UMS Context 0x07B9A6F0.
2004-10-22 04:28:50.28 server Error: 17883, Severity: 1, State: 0
2004-10-22 04:28:50.28 server The Scheduler 83 appears to be hung. SPID
0, ECID 2812, UMS Context 0x07B9A6F0.Hi
Have a look at [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;810885[/url
]
If that dose not solve your problem, what SQL Server version and hotfix
level (select @.@.version) ar e you on?
Regards
Mike
"Joe K." wrote:
> What could cause the error message listed below.
> Thanks,
> 2004-10-22 04:14:50.31 server Error: 17883, Severity: 1, State: 0
> 2004-10-22 04:14:50.31 server The Scheduler 83 appears to be hung. SPID
> 0, ECID 2812, UMS Context 0x07B9A6F0.
> 2004-10-22 04:18:50.30 server Error: 17883, Severity: 1, State: 0
> 2004-10-22 04:18:50.30 server The Scheduler 83 appears to be hung. SPID
> 0, ECID 2812, UMS Context 0x07B9A6F0.
> 2004-10-22 04:20:50.30 server Error: 17883, Severity: 1, State: 0
> 2004-10-22 04:20:50.30 server The Scheduler 83 appears to be hung. SPID
> 0, ECID 2812, UMS Context 0x07B9A6F0.
> 2004-10-22 04:26:50.28 server Error: 17883, Severity: 1, State: 0
> 2004-10-22 04:26:50.28 server The Scheduler 83 appears to be hung. SPID
> 0, ECID 2812, UMS Context 0x07B9A6F0.
> 2004-10-22 04:28:50.28 server Error: 17883, Severity: 1, State: 0
> 2004-10-22 04:28:50.28 server The Scheduler 83 appears to be hung. SPID
> 0, ECID 2812, UMS Context 0x07B9A6F0.
Thanks,
2004-10-22 04:14:50.31 server Error: 17883, Severity: 1, State: 0
2004-10-22 04:14:50.31 server The Scheduler 83 appears to be hung. SPID
0, ECID 2812, UMS Context 0x07B9A6F0.
2004-10-22 04:18:50.30 server Error: 17883, Severity: 1, State: 0
2004-10-22 04:18:50.30 server The Scheduler 83 appears to be hung. SPID
0, ECID 2812, UMS Context 0x07B9A6F0.
2004-10-22 04:20:50.30 server Error: 17883, Severity: 1, State: 0
2004-10-22 04:20:50.30 server The Scheduler 83 appears to be hung. SPID
0, ECID 2812, UMS Context 0x07B9A6F0.
2004-10-22 04:26:50.28 server Error: 17883, Severity: 1, State: 0
2004-10-22 04:26:50.28 server The Scheduler 83 appears to be hung. SPID
0, ECID 2812, UMS Context 0x07B9A6F0.
2004-10-22 04:28:50.28 server Error: 17883, Severity: 1, State: 0
2004-10-22 04:28:50.28 server The Scheduler 83 appears to be hung. SPID
0, ECID 2812, UMS Context 0x07B9A6F0.Hi
Have a look at [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;810885[/url
]
If that dose not solve your problem, what SQL Server version and hotfix
level (select @.@.version) ar e you on?
Regards
Mike
"Joe K." wrote:
> What could cause the error message listed below.
> Thanks,
> 2004-10-22 04:14:50.31 server Error: 17883, Severity: 1, State: 0
> 2004-10-22 04:14:50.31 server The Scheduler 83 appears to be hung. SPID
> 0, ECID 2812, UMS Context 0x07B9A6F0.
> 2004-10-22 04:18:50.30 server Error: 17883, Severity: 1, State: 0
> 2004-10-22 04:18:50.30 server The Scheduler 83 appears to be hung. SPID
> 0, ECID 2812, UMS Context 0x07B9A6F0.
> 2004-10-22 04:20:50.30 server Error: 17883, Severity: 1, State: 0
> 2004-10-22 04:20:50.30 server The Scheduler 83 appears to be hung. SPID
> 0, ECID 2812, UMS Context 0x07B9A6F0.
> 2004-10-22 04:26:50.28 server Error: 17883, Severity: 1, State: 0
> 2004-10-22 04:26:50.28 server The Scheduler 83 appears to be hung. SPID
> 0, ECID 2812, UMS Context 0x07B9A6F0.
> 2004-10-22 04:28:50.28 server Error: 17883, Severity: 1, State: 0
> 2004-10-22 04:28:50.28 server The Scheduler 83 appears to be hung. SPID
> 0, ECID 2812, UMS Context 0x07B9A6F0.
Error: The Scheduler 83 appears to be hung.
What could cause the error message listed below.
Thanks,
2004-10-22 04:14:50.31 server Error: 17883, Severity: 1, State: 0
2004-10-22 04:14:50.31 server The Scheduler 83 appears to be hung. SPID
0, ECID 2812, UMS Context 0x07B9A6F0.
2004-10-22 04:18:50.30 server Error: 17883, Severity: 1, State: 0
2004-10-22 04:18:50.30 server The Scheduler 83 appears to be hung. SPID
0, ECID 2812, UMS Context 0x07B9A6F0.
2004-10-22 04:20:50.30 server Error: 17883, Severity: 1, State: 0
2004-10-22 04:20:50.30 server The Scheduler 83 appears to be hung. SPID
0, ECID 2812, UMS Context 0x07B9A6F0.
2004-10-22 04:26:50.28 server Error: 17883, Severity: 1, State: 0
2004-10-22 04:26:50.28 server The Scheduler 83 appears to be hung. SPID
0, ECID 2812, UMS Context 0x07B9A6F0.
2004-10-22 04:28:50.28 server Error: 17883, Severity: 1, State: 0
2004-10-22 04:28:50.28 server The Scheduler 83 appears to be hung. SPID
0, ECID 2812, UMS Context 0x07B9A6F0.
Hi
Have a look at http://support.microsoft.com/default...b;en-us;810885
If that dose not solve your problem, what SQL Server version and hotfix
level (select @.@.version) ar e you on?
Regards
Mike
"Joe K." wrote:
> What could cause the error message listed below.
> Thanks,
> 2004-10-22 04:14:50.31 server Error: 17883, Severity: 1, State: 0
> 2004-10-22 04:14:50.31 server The Scheduler 83 appears to be hung. SPID
> 0, ECID 2812, UMS Context 0x07B9A6F0.
> 2004-10-22 04:18:50.30 server Error: 17883, Severity: 1, State: 0
> 2004-10-22 04:18:50.30 server The Scheduler 83 appears to be hung. SPID
> 0, ECID 2812, UMS Context 0x07B9A6F0.
> 2004-10-22 04:20:50.30 server Error: 17883, Severity: 1, State: 0
> 2004-10-22 04:20:50.30 server The Scheduler 83 appears to be hung. SPID
> 0, ECID 2812, UMS Context 0x07B9A6F0.
> 2004-10-22 04:26:50.28 server Error: 17883, Severity: 1, State: 0
> 2004-10-22 04:26:50.28 server The Scheduler 83 appears to be hung. SPID
> 0, ECID 2812, UMS Context 0x07B9A6F0.
> 2004-10-22 04:28:50.28 server Error: 17883, Severity: 1, State: 0
> 2004-10-22 04:28:50.28 server The Scheduler 83 appears to be hung. SPID
> 0, ECID 2812, UMS Context 0x07B9A6F0.
Thanks,
2004-10-22 04:14:50.31 server Error: 17883, Severity: 1, State: 0
2004-10-22 04:14:50.31 server The Scheduler 83 appears to be hung. SPID
0, ECID 2812, UMS Context 0x07B9A6F0.
2004-10-22 04:18:50.30 server Error: 17883, Severity: 1, State: 0
2004-10-22 04:18:50.30 server The Scheduler 83 appears to be hung. SPID
0, ECID 2812, UMS Context 0x07B9A6F0.
2004-10-22 04:20:50.30 server Error: 17883, Severity: 1, State: 0
2004-10-22 04:20:50.30 server The Scheduler 83 appears to be hung. SPID
0, ECID 2812, UMS Context 0x07B9A6F0.
2004-10-22 04:26:50.28 server Error: 17883, Severity: 1, State: 0
2004-10-22 04:26:50.28 server The Scheduler 83 appears to be hung. SPID
0, ECID 2812, UMS Context 0x07B9A6F0.
2004-10-22 04:28:50.28 server Error: 17883, Severity: 1, State: 0
2004-10-22 04:28:50.28 server The Scheduler 83 appears to be hung. SPID
0, ECID 2812, UMS Context 0x07B9A6F0.
Hi
Have a look at http://support.microsoft.com/default...b;en-us;810885
If that dose not solve your problem, what SQL Server version and hotfix
level (select @.@.version) ar e you on?
Regards
Mike
"Joe K." wrote:
> What could cause the error message listed below.
> Thanks,
> 2004-10-22 04:14:50.31 server Error: 17883, Severity: 1, State: 0
> 2004-10-22 04:14:50.31 server The Scheduler 83 appears to be hung. SPID
> 0, ECID 2812, UMS Context 0x07B9A6F0.
> 2004-10-22 04:18:50.30 server Error: 17883, Severity: 1, State: 0
> 2004-10-22 04:18:50.30 server The Scheduler 83 appears to be hung. SPID
> 0, ECID 2812, UMS Context 0x07B9A6F0.
> 2004-10-22 04:20:50.30 server Error: 17883, Severity: 1, State: 0
> 2004-10-22 04:20:50.30 server The Scheduler 83 appears to be hung. SPID
> 0, ECID 2812, UMS Context 0x07B9A6F0.
> 2004-10-22 04:26:50.28 server Error: 17883, Severity: 1, State: 0
> 2004-10-22 04:26:50.28 server The Scheduler 83 appears to be hung. SPID
> 0, ECID 2812, UMS Context 0x07B9A6F0.
> 2004-10-22 04:28:50.28 server Error: 17883, Severity: 1, State: 0
> 2004-10-22 04:28:50.28 server The Scheduler 83 appears to be hung. SPID
> 0, ECID 2812, UMS Context 0x07B9A6F0.
Subscribe to:
Posts (Atom)