Solved

Torn Page Recovery

Posted on 2010-11-10
56
2,369 Views
Last Modified: 2012-05-10
We recently had to recover a SBS 2003 from an outdate system partition backup, and unfortunately the SQL instances on the unit seem to have suffered fairly badly in the ordeal.  MSDB for the default system SQL instance was beyond recovery and I was able to get that resolved nicely and quickly via a question on this site.  Now when I try to start the instance the following error shows up in the application logs : SQL Server detected a logical consistency-based I/O error: torn page (expected signature: 0x55555555; actual signature: 0xaaaaaaa9). It occurred during a read of page (1:74) in database ID 5 at offset 0x00000000094000 in file 'D:\Pfx Engagement\Admin\Data\Admin_Data.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).

To further complicate matters, there are two SQL instances that appear to be related to this ProFX Engagement software the end user is having issues with (due to the DB problems).  I can post a screenshot of what SQL EM shows for instances if that last bit isn't clear.
0
Comment
Question by:BizTekConnection
  • 31
  • 25
56 Comments
 
LVL 16

Expert Comment

by:EvilPostIt
Comment Utility
This is a pretty serious error and you will most probably end up losing some data. Whats your backup strategy like? Ie full db backups transaction log backups etc.
0
 
LVL 16

Expert Comment

by:EvilPostIt
Comment Utility
By the way dont start the restore process yet. If your transaction log is not damaged you will want to take a tail log backup first.

Also you want to track down which object the corruption actually exists in.

Run the following against the offending database.

DBCC CHECKDB WITH NO_INFOMSGS

This should tell you where the corruption lies. Hopefully it will be a non-clustered index so fingers crossed. As this can just be rebuilt.
0
 

Author Comment

by:BizTekConnection
Comment Utility
Unfortunately, the backup scenario (I didn't implement any of this, just got to come in and maintan after the fact) was running a script from the 3rd party software that starts by deleting out the contents of the backup directory (and thus the previous backup) with no archival process.  I didn't find this out until after it had run once, so there are no good backups that I'm aware of. :(
0
 
LVL 16

Expert Comment

by:EvilPostIt
Comment Utility
Do a DBCC CHECKDB WITH NO_INFOMSGS if you like post the results back.
0
 

Author Comment

by:BizTekConnection
Comment Utility
Oh and how do I run that dbcc against the offender?  I can't start the SQL instance it is part of, so I can't run queries against it directly in SQL SMSE and I'm not enough of a SQL guru to know the phrasing I need to hit it without being connected.
0
 
LVL 16

Expert Comment

by:EvilPostIt
Comment Utility
So the SQL Server service isnt starting. Your original post states the error is around database id 5 anything more than 4 is a user database.

Could you check to see if the SQL Server services have started. If not you could try a starting it in single user mode as below. Which version of SQL Server are you using as the below applies to 2005 / 2008 & 2008 R2.

http://msdn.microsoft.com/en-us/library/ms188236.aspx
0
 

Author Comment

by:BizTekConnection
Comment Utility
Right, as I stated in my initial post, the error is logged when I try to start that SQL instance.  I have multiple SQL instances on the unit, and as far as I know this instance is SQL 2005.  Let me post some screen shots of all the SQL that is on this old box.

Now, the odd thing that I haven't figured out (since I didn't implement this server) is that ProsystemsFX is the software name, but at one point the client interface states it cannot connect to the CPM instance of SQL.
sbs2003-sql.JPG
0
 
LVL 16

Expert Comment

by:EvilPostIt
Comment Utility
This is sql server enterprise manager which is SQL Server 2000. Just because the application cannot connect to the database then doesnt mean SQL Server isnt starting. It just means that it may not be able to connect to the user database which is dependant on what the application does when it connects. Enterprise Manager can be flacky.

If they are in fact SQL Server 2005 in dont think that enterprise manager can even connect to 2005 instances. So look for SQL Server Management Studio which should be under Start > Programs > SQL Server 2005.

Please could you check the SQL Server services on the box to see if they have started. If you look in services for Microsoft SQL Server, the instance name should be somewhere in the name of the service too.

If they are not started do a search on the filesystem for a file called errorlog (no extension will be included as this is the complete filename.) there will be 1 per instance. These are text based files and you should be able to read each startup message. The instance name will also be included in this file.

0
 

Author Comment

by:BizTekConnection
Comment Utility
No, the services haven't started.  I am not trying to start them through SSEM, I am trying to start the service from computer management which is when the previously posted error logs get logged.  I have SQL 8 and SQL 9 both on this box, just snagged SSEM to get the shot of the instance names.  Let me get the error logs for you for both SQL instances.

2010-11-10 08:16:39.81 server    Microsoft SQL Server  2000 - 8.00.760 (Intel X86)
      Dec 17 2002 14:22:05
      Copyright (c) 1988-2003 Microsoft Corporation
      Desktop Engine on Windows NT 5.2 (Build 3790: Service Pack 2)

2010-11-10 08:16:39.81 server    Copyright (C) 1988-2002 Microsoft Corporation.
2010-11-10 08:16:39.81 server    All rights reserved.
2010-11-10 08:16:39.81 server    Server Process ID is 8676.
2010-11-10 08:16:39.81 server    Logging SQL Server messages in file 'D:\CPASsql\MSSQL$CPM\LOG\ERRORLOG'.
2010-11-10 08:16:39.82 server    SQL Server is starting at priority class 'normal'(4 CPUs detected).
2010-11-10 08:16:39.92 server    SQL Server configured for thread mode processing.
2010-11-10 08:16:39.92 server    Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
2010-11-10 08:16:39.93 spid3     Starting up database 'master'.
2010-11-10 08:16:39.96 spid3     Error: 9003, Severity: 20, State: 1.
2010-11-10 08:16:39.96 spid3     Cannot recover the master database. Exiting.


There's the first log, here's the second :

2010-11-07 08:46:14.15 Server      Microsoft SQL Server 2005 - 9.00.4053.00 (Intel X86)
      May 26 2009 14:24:20
      Copyright (c) 1988-2005 Microsoft Corporation
      Express Edition on Windows NT 5.2 (Build 3790: Service Pack 2)

2010-11-07 08:46:14.21 Server      (c) 2005 Microsoft Corporation.
2010-11-07 08:46:14.21 Server      All rights reserved.
2010-11-07 08:46:14.21 Server      Server process ID is 2240.
2010-11-07 08:46:14.21 Server      Authentication mode is MIXED.
2010-11-07 08:46:14.23 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2010-11-07 08:46:14.23 Server      This instance of SQL Server last reported using a process ID of 2204 at 11/7/2010 8:34:08 AM (local) 11/7/2010 2:34:08 PM (UTC). This is an informational message only; no user action is required.
2010-11-07 08:46:14.23 Server      Registry startup parameters:
2010-11-07 08:46:14.26 Server             -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2010-11-07 08:46:14.26 Server             -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2010-11-07 08:46:14.26 Server             -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2010-11-07 08:46:14.39 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2010-11-07 08:46:14.39 Server      Detected 4 CPUs. This is an informational message; no user action is required.
2010-11-07 08:46:15.28 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
2010-11-07 08:46:17.01 Server      Database mirroring has been enabled on this instance of SQL Server.
2010-11-07 08:46:17.24 spid4s      Starting up database 'master'.
2010-11-07 08:46:17.86 spid4s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2010-11-07 08:46:18.44 spid4s      SQL Trace ID 1 was started by login "sa".
2010-11-07 08:46:18.52 spid4s      Starting up database 'mssqlsystemresource'.
2010-11-07 08:46:18.56 spid4s      The resource database build version is 9.00.4035. This is an informational message only. No user action is required.
2010-11-07 08:46:19.20 spid8s      Starting up database 'model'.
2010-11-07 08:46:19.24 spid4s      Server name is 'LRSERV01\PROFXENGAGEMENT'. This is an informational message only. No user action is required.
2010-11-07 08:46:19.26 spid4s      Starting up database 'msdb'.
2010-11-07 08:46:19.80 spid8s      Clearing tempdb database.
2010-11-07 08:46:19.80 Server      A self-generated certificate was successfully loaded for encryption.
2010-11-07 08:46:19.84 Server      Server is listening on [ 'any' <ipv4> 2029].
2010-11-07 08:46:19.84 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\PROFXENGAGEMENT ].
2010-11-07 08:46:19.84 Server      Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$PROFXENGAGEMENT\sql\query ].
2010-11-07 08:46:19.84 Server      Dedicated administrator connection support was not started because it is not available on this edition of SQL Server. This is an informational message only. No user action is required.
2010-11-07 08:46:19.87 Server      SQL Server is now ready for client connections. This is an informational message; no user action is required.
2010-11-07 08:46:20.36 spid8s      Starting up database 'tempdb'.
2010-11-07 08:46:20.51 spid4s      Recovery is complete. This is an informational message only. No user action is required.
2010-11-07 08:46:20.59 spid11s     The Service Broker protocol transport is disabled or not configured.
2010-11-07 08:46:20.61 spid11s     The Database Mirroring protocol transport is disabled or not configured.
2010-11-07 08:46:20.75 spid11s     Service Broker manager has started.
2010-11-07 22:00:02.56 Server      Server resumed execution after being idle 47590 seconds: user activity awakened the server. This is an informational message only. No user action is required.
2010-11-07 22:00:03.85 spid51      Starting up database 'CentralAdmin'.
2010-11-07 22:00:05.58 spid51      Error: 824, Severity: 24, State: 2.
2010-11-07 22:00:05.58 spid51      SQL Server detected a logical consistency-based I/O error: torn page (expected signature: 0x55555555; actual signature: 0xaaaaaaa9). It occurred during a read of page (1:74) in database ID 5 at offset 0x00000000094000 in file 'D:\Pfx Engagement\Admin\Data\Admin_Data.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.
2010-11-08 01:00:20.59 spid1s      Server resumed execution after being idle 9904 seconds. Reason: timer event.
2010-11-08 03:00:00.18 Server      Server resumed execution after being idle 6267 seconds: user activity awakened the server. This is an informational message only. No user action is required.
2010-11-08 03:00:03.12 spid51      Using 'dbghelp.dll' version '4.0.5'
2010-11-08 03:00:03.12 spid51      **Dump thread - spid = 51, PSS = 0x040135D8, EC = 0x040135E0
2010-11-08 03:00:03.12 spid51      ***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0047.txt
2010-11-08 03:00:03.12 spid51      * *******************************************************************************
2010-11-08 03:00:03.12 spid51      *
2010-11-08 03:00:03.12 spid51      * BEGIN STACK DUMP:
2010-11-08 03:00:03.12 spid51      *   11/08/10 03:00:03 spid 51
2010-11-08 03:00:03.12 spid51      *
2010-11-08 03:00:03.12 spid51      * CPerIndexMetaQS::ErrorAbort - Index corruption
2010-11-08 03:00:03.12 spid51      *
2010-11-08 03:00:03.12 spid51      * Input Buffer 255 bytes -
2010-11-08 03:00:03.12 spid51      *                     16 00 00 00 12 00 00 00 02 00 00 00 00 00 00 00 00 00
2010-11-08 03:00:03.12 spid51      *        U S P _ A d  01 00 00 00 1b 00 55 00 53 00 50 00 5f 00 41 00 64 00
2010-11-08 03:00:03.12 spid51      *  m i n _ S c h T a  6d 00 69 00 6e 00 5f 00 53 00 63 00 68 00 54 00 61 00
2010-11-08 03:00:03.12 spid51      *  s k H i s t o r y  73 00 6b 00 48 00 69 00 73 00 74 00 6f 00 72 00 79 00
2010-11-08 03:00:03.12 spid51      *  I n s         @ i _ T a 49 00 6e 00 73 00 00 00 09 40 00 69 00 5f 00 54 00 61
2010-11-08 03:00:03.12 spid51      *   s k I D  &             00 73 00 6b 00 49 00 44 00 00 26 04 04 01 00 00 00 09
2010-11-08 03:00:03.12 spid51      *  @ i _ S t a t u s  40 00 69 00 5f 00 53 00 74 00 61 00 74 00 75 00 73 00
2010-11-08 03:00:03.12 spid51      *   &       @ i _ M e 00 26 04 04 02 00 00 00 0a 40 00 69 00 5f 00 4d 00 65
2010-11-08 03:00:03.12 spid51      *   s s a g e  §Ð        Ð 00 73 00 73 00 61 00 67 00 65 00 00 a7 d0 07 09 04 d0
2010-11-08 03:00:03.12 spid51      *   4   @ i _ S t a r 00 34 00 00 0c 40 00 69 00 5f 00 53 00 74 00 61 00 72
2010-11-08 03:00:03.12 spid51      *   t T i m e  o  (¿  00 74 00 54 00 69 00 6d 00 65 00 00 6f 08 08 28 9e 00
2010-11-08 03:00:03.12 spid51      *    Q¿  @ i _ E n d  00 19 51 94 00 0a 40 00 69 00 5f 00 45 00 6e 00 64 00
2010-11-08 03:00:03.12 spid51      *  T i m e  o         54 00 69 00 6d 00 65 00 00 6f 08 08 8d 01 00 00 00 00
2010-11-08 03:00:03.12 spid51      *     @ i _ S t a t e 00 00 08 40 00 69 00 5f 00 53 00 74 00 61 00 74 00 65
2010-11-08 03:00:03.12 spid51      *    h    @ o _ I n s 00 00 68 01 01 00 0d 40 00 6f 00 5f 00 49 00 6e 00 73
2010-11-08 03:00:03.12 spid51      *   t a n c e I D  &  00 74 00 61 00 6e 00 63 00 65 00 49 00 44 00 01 26 04
2010-11-08 03:00:03.12 spid51      *                     00
2010-11-08 03:00:03.12 spid51      *  
2010-11-08 03:00:03.12 spid51      *
2010-11-08 03:00:03.12 spid51      *  MODULE                          BASE      END       SIZE
2010-11-08 03:00:03.12 spid51      * sqlservr                       01000000  02C1FFFF  01c20000
2010-11-08 03:00:03.12 spid51      * ntdll                          7C800000  7C8C1FFF  000c2000
2010-11-08 03:00:03.12 spid51      * kernel32                       77E40000  77F41FFF  00102000
2010-11-08 03:00:03.12 spid51      * MSVCR80                        78130000  781CAFFF  0009b000
2010-11-08 03:00:03.12 spid51      * msvcrt                         77BA0000  77BF9FFF  0005a000
2010-11-08 03:00:03.12 spid51      * MSVCP80                        7C420000  7C4A6FFF  00087000
2010-11-08 03:00:03.12 spid51      * ADVAPI32                       7D1E0000  7D27BFFF  0009c000
2010-11-08 03:00:03.12 spid51      * RPCRT4                         77C50000  77CEFFFF  000a0000
2010-11-08 03:00:03.12 spid51      * Secur32                        76F50000  76F62FFF  00013000
2010-11-08 03:00:03.12 spid51      * sqlos                          344D0000  344D4FFF  00005000
2010-11-08 03:00:03.12 spid51      * USERENV                        76920000  769E1FFF  000c2000
2010-11-08 03:00:03.12 spid51      * USER32                         77380000  77410FFF  00091000
2010-11-08 03:00:03.12 spid51      * GDI32                          77C00000  77C48FFF  00049000
2010-11-08 03:00:03.12 spid51      * WINMM                          76AA0000  76ACCFFF  0002d000
2010-11-08 03:00:03.12 spid51      * opends60                       333E0000  333E6FFF  00007000
2010-11-08 03:00:03.12 spid51      * NETAPI32                       71C40000  71C96FFF  00057000
2010-11-08 03:00:03.12 spid51      * psapi                          76B70000  76B7AFFF  0000b000
2010-11-08 03:00:03.12 spid51      * instapi                        48060000  48069FFF  0000a000
2010-11-08 03:00:03.12 spid51      * sqlevn70                       4F610000  4F7B8FFF  001a9000
2010-11-08 03:00:03.12 spid51      * rsaenh                         68000000  68034FFF  00035000
2010-11-08 03:00:03.12 spid51      * AUTHZ                          76C40000  76C53FFF  00014000
2010-11-08 03:00:03.12 spid51      * MSCOREE                        79000000  79049FFF  0004a000
2010-11-08 03:00:03.12 spid51      * mscoreei                       33AE0000  33B45FFF  00066000
2010-11-08 03:00:03.12 spid51      * ole32                          77670000  777A8FFF  00139000
2010-11-08 03:00:03.12 spid51      * msv1_0                         76C90000  76CB6FFF  00027000
2010-11-08 03:00:03.12 spid51      * cryptdll                       766E0000  766EBFFF  0000c000
2010-11-08 03:00:03.12 spid51      * WS2_32                         71C00000  71C16FFF  00017000
2010-11-08 03:00:03.12 spid51      * WS2HELP                        71BF0000  71BF7FFF  00008000
2010-11-08 03:00:03.12 spid51      * iphlpapi                       76CF0000  76D09FFF  0001a000
2010-11-08 03:00:03.12 spid51      * kerberos                       71CA0000  71CF8FFF  00059000
2010-11-08 03:00:03.12 spid51      * MSASN1                         76190000  761A1FFF  00012000
2010-11-08 03:00:03.12 spid51      * schannel                       76750000  76777FFF  00028000
2010-11-08 03:00:03.12 spid51      * CRYPT32                        761B0000  76242FFF  00093000
2010-11-08 03:00:03.12 spid51      * security                       71F60000  71F63FFF  00004000
2010-11-08 03:00:03.12 spid51      * VERSION                        77B90000  77B97FFF  00008000
2010-11-08 03:00:03.13 spid51      * SHELL32                        7C8D0000  7D0CEFFF  007ff000
2010-11-08 03:00:03.13 spid51      * SHLWAPI                        7D180000  7D1D1FFF  00052000
2010-11-08 03:00:03.13 spid51      * comctl32                       77420000  77522FFF  00103000
2010-11-08 03:00:03.13 spid51      * dssenh                         68100000  68126FFF  00027000
2010-11-08 03:00:03.13 spid51      * mswsock                        71B20000  71B60FFF  00041000
2010-11-08 03:00:03.13 spid51      * hnetcfg                        4A6F0000  4A749FFF  0005a000
2010-11-08 03:00:03.13 spid51      * wshtcpip                       71AE0000  71AE7FFF  00008000
2010-11-08 03:00:03.13 spid51      * NTMARTA                        77E00000  77E20FFF  00021000
2010-11-08 03:00:03.13 spid51      * WLDAP32                        76F10000  76F3DFFF  0002e000
2010-11-08 03:00:03.13 spid51      * SAMLIB                         7E020000  7E02EFFF  0000f000
2010-11-08 03:00:03.13 spid51      * ntdsapi                        766F0000  76703FFF  00014000
2010-11-08 03:00:03.13 spid51      * DNSAPI                         76ED0000  76EF9FFF  0002a000
2010-11-08 03:00:03.13 spid51      * winrnr                         76F70000  76F76FFF  00007000
2010-11-08 03:00:03.13 spid51      * rasadhlp                       76F80000  76F84FFF  00005000
2010-11-08 03:00:03.13 spid51      * dbghelp                        4AB80000  4AC94FFF  00115000
2010-11-08 03:00:03.13 spid51      *
2010-11-08 03:00:03.13 spid51      *        Edi: 4AD7EB90:  00134388  4AD7E9FA  00000005  040E9594  040E8470  00000016  
2010-11-08 03:00:03.13 spid51      *        Esi: 00000000:  
2010-11-08 03:00:03.13 spid51      *        Eax: 4AD7DD2C:  000042AC  00000000  00000000  77E4BEF7  00000000  7C827739  
2010-11-08 03:00:03.13 spid51      *        Ebx: 0000003F:  
2010-11-08 03:00:03.13 spid51      *        Ecx: 4AD7E39C:  00000000  00010007  00000000  00000000  4AD7D80A  4AD7E648  
2010-11-08 03:00:03.13 spid51      *        Edx: 0000003D:  
2010-11-08 03:00:03.13 spid51      *        Eip: 77E4BEF7:  10C2C95E  01093D00  840FC000  00000095  F29DE950  9090FFFF  
2010-11-08 03:00:03.13 spid51      *        Ebp: 4AD7DD7C:  4AD7DDC0  021AE24C  000042AC  00000000  00000000  00000000  
2010-11-08 03:00:03.13 spid51      *      SegCs: 7813001B:  00000000  00000000  00000000  00000000  00000000  00000000  
2010-11-08 03:00:03.13 spid51      *     EFlags: 00000246:  
2010-11-08 03:00:03.13 spid51      *        Esp: 4AD7DD28:  040135D8  000042AC  00000000  00000000  77E4BEF7  00000000  
2010-11-08 03:00:03.13 spid51      *      SegSs: 78130023:  00000000  00000000  00000000  00000000  00000000  00000000  
2010-11-08 03:00:03.13 spid51      * *******************************************************************************
2010-11-08 03:00:03.13 spid51      * -------------------------------------------------------------------------------
2010-11-08 03:00:03.13 spid51      * Short Stack Dump
2010-11-08 03:00:03.13 spid51      77E4BEF7 Module(kernel32+0000BEF7)
2010-11-08 03:00:03.13 spid51      021AE24C Module(sqlservr+011AE24C)
2010-11-08 03:00:03.13 spid51      021B2160 Module(sqlservr+011B2160)
2010-11-08 03:00:03.13 spid51      01E58E81 Module(sqlservr+00E58E81)
2010-11-08 03:00:03.13 spid51      01E59037 Module(sqlservr+00E59037)
2010-11-08 03:00:03.13 spid51      014E3777 Module(sqlservr+004E3777)
2010-11-08 03:00:03.13 spid51      0104132B Module(sqlservr+0004132B)
2010-11-08 03:00:03.13 spid51      0102A8C0 Module(sqlservr+0002A8C0)
2010-11-08 03:00:03.13 spid51      0102A7D1 Module(sqlservr+0002A7D1)
2010-11-08 03:00:03.13 spid51      010633E3 Module(sqlservr+000633E3)
2010-11-08 03:00:03.13 spid51      01063168 Module(sqlservr+00063168)
2010-11-08 03:00:03.13 spid51      0102522F Module(sqlservr+0002522F)
2010-11-08 03:00:03.13 spid51      010257F0 Module(sqlservr+000257F0)
2010-11-08 03:00:03.13 spid51      010232BB Module(sqlservr+000232BB)
2010-11-08 03:00:03.13 spid51      013D58A6 Module(sqlservr+003D58A6)
2010-11-08 03:00:03.13 spid51      013D571D Module(sqlservr+003D571D)
2010-11-08 03:00:03.13 spid51      013D55B2 Module(sqlservr+003D55B2)
2010-11-08 03:00:03.14 spid51      0102522F Module(sqlservr+0002522F)
2010-11-08 03:00:03.14 spid51      010257F0 Module(sqlservr+000257F0)
2010-11-08 03:00:03.14 spid51      010232BB Module(sqlservr+000232BB)
2010-11-08 03:00:03.14 spid51      0103D647 Module(sqlservr+0003D647)
2010-11-08 03:00:03.14 spid51      0103D30F Module(sqlservr+0003D30F)
2010-11-08 03:00:03.14 spid51      01006E27 Module(sqlservr+00006E27)
2010-11-08 03:00:03.14 spid51      01006F4D Module(sqlservr+00006F4D)
2010-11-08 03:00:03.14 spid51      01006C5D Module(sqlservr+00006C5D)
2010-11-08 03:00:03.14 spid51      010AAC3C Module(sqlservr+000AAC3C)
2010-11-08 03:00:03.14 spid51      010AAB5C Module(sqlservr+000AAB5C)
2010-11-08 03:00:03.14 spid51      010AA60C Module(sqlservr+000AA60C)
2010-11-08 03:00:03.15 spid51      010AA7A9 Module(sqlservr+000AA7A9)
2010-11-08 03:00:03.15 spid51      781329BB Module(MSVCR80+000029BB)
2010-11-08 03:00:03.15 spid51      78132A47 Module(MSVCR80+00002A47)
2010-11-08 03:00:03.16 spid51      Stack Signature for the dump is 0x3A9FD5AD
2010-11-08 03:00:03.89 spid51      External dump process return code 0x20000001.
External dump process returned no errors.

2010-11-08 03:00:05.65 spid51      Error: 824, Severity: 24, State: 2.
2010-11-08 03:00:05.65 spid51      SQL Server detected a logical consistency-based I/O error: torn page (expected signature: 0x55555555; actual signature: 0xaaaaaaa9). It occurred during a read of page (1:1490) in database ID 5 at offset 0x00000000ba4000 in file 'D:\Pfx Engagement\Admin\Data\Admin_Data.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.
2010-11-08 04:00:34.70 Server      Server resumed execution after being idle 2716 seconds: user activity awakened the server. This is an informational message only. No user action is required.
2010-11-08 04:00:57.48 spid52      I/O is frozen on database model. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
2010-11-08 04:00:57.49 spid51      I/O is frozen on database msdb. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
2010-11-08 04:00:57.49 spid53      I/O is frozen on database master. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
2010-11-08 04:00:59.26 spid51      I/O was resumed on database msdb. No user action is required.
2010-11-08 04:00:59.26 spid53      I/O was resumed on database master. No user action is required.
2010-11-08 04:00:59.27 spid52      I/O was resumed on database model. No user action is required.
2010-11-08 04:01:00.81 Backup      Database backed up. Database: master, creation date(time): 2010/11/07(08:46:17), pages dumped: 1, first LSN: 682:304:50, last LSN: 682:336:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{6D1A3E8F-3DE6-4833-B6E2-78F5200F101D}3'}). This is an informational message only. No user action is required.
2010-11-08 04:01:00.82 Backup      Database backed up. Database: msdb, creation date(time): 2005/10/14(01:54:05), pages dumped: 1, first LSN: 416:88:47, last LSN: 416:120:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{6D1A3E8F-3DE6-4833-B6E2-78F5200F101D}2'}). This is an informational message only. No user action is required.
2010-11-08 04:01:00.84 Backup      Database backed up. Database: model, creation date(time): 2003/04/08(09:13:36), pages dumped: 1, first LSN: 130:112:37, last LSN: 130:136:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{6D1A3E8F-3DE6-4833-B6E2-78F5200F101D}1'}). This is an informational message only. No user action is required.
2010-11-08 05:46:28.18 Server      Server resumed execution after being idle 5415 seconds: user activity awakened the server. This is an informational message only. No user action is required.
2010-11-08 22:00:04.43 Server      Server resumed execution after being idle 57503 seconds: user activity awakened the server. This is an informational message only. No user action is required.
2010-11-08 22:00:06.81 spid51      Error: 824, Severity: 24, State: 2.
2010-11-08 22:00:06.81 spid51      SQL Server detected a logical consistency-based I/O error: torn page (expected signature: 0x55555555; actual signature: 0xaaaaaaa9). It occurred during a read of page (1:74) in database ID 5 at offset 0x00000000094000 in file 'D:\Pfx Engagement\Admin\Data\Admin_Data.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.
2010-11-09 01:00:25.57 spid1s      Server resumed execution after being idle 9907 seconds. Reason: timer event.
2010-11-09 03:00:02.65 Server      Server resumed execution after being idle 6264 seconds: user activity awakened the server. This is an informational message only. No user action is required.
2010-11-09 03:00:03.21 spid51      Using 'dbghelp.dll' version '4.0.5'
2010-11-09 03:00:03.22 spid51      **Dump thread - spid = 51, PSS = 0x0400B5D8, EC = 0x0400B5E0
2010-11-09 03:00:03.22 spid51      ***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0048.txt
2010-11-09 03:00:03.22 spid51      * *******************************************************************************
2010-11-09 03:00:03.22 spid51      *
2010-11-09 03:00:03.22 spid51      * BEGIN STACK DUMP:
2010-11-09 03:00:03.22 spid51      *   11/09/10 03:00:03 spid 51
2010-11-09 03:00:03.22 spid51      *
2010-11-09 03:00:03.22 spid51      * CPerIndexMetaQS::ErrorAbort - Index corruption
2010-11-09 03:00:03.22 spid51      *
2010-11-09 03:00:03.22 spid51      * Input Buffer 255 bytes -
2010-11-09 03:00:03.22 spid51      *                     16 00 00 00 12 00 00 00 02 00 00 00 00 00 00 00 00 00
2010-11-09 03:00:03.22 spid51      *        U S P _ A d  01 00 00 00 1b 00 55 00 53 00 50 00 5f 00 41 00 64 00
2010-11-09 03:00:03.22 spid51      *  m i n _ S c h T a  6d 00 69 00 6e 00 5f 00 53 00 63 00 68 00 54 00 61 00
2010-11-09 03:00:03.22 spid51      *  s k H i s t o r y  73 00 6b 00 48 00 69 00 73 00 74 00 6f 00 72 00 79 00
2010-11-09 03:00:03.22 spid51      *  I n s         @ i _ T a 49 00 6e 00 73 00 00 00 09 40 00 69 00 5f 00 54 00 61
2010-11-09 03:00:03.22 spid51      *   s k I D  &             00 73 00 6b 00 49 00 44 00 00 26 04 04 01 00 00 00 09
2010-11-09 03:00:03.22 spid51      *  @ i _ S t a t u s  40 00 69 00 5f 00 53 00 74 00 61 00 74 00 75 00 73 00
2010-11-09 03:00:03.22 spid51      *   &       @ i _ M e 00 26 04 04 02 00 00 00 0a 40 00 69 00 5f 00 4d 00 65
2010-11-09 03:00:03.22 spid51      *   s s a g e  §Ð        Ð 00 73 00 73 00 61 00 67 00 65 00 00 a7 d0 07 09 04 d0
2010-11-09 03:00:03.22 spid51      *   4   @ i _ S t a r 00 34 00 00 0c 40 00 69 00 5f 00 53 00 74 00 61 00 72
2010-11-09 03:00:03.22 spid51      *   t T i m e  o  )¿  00 74 00 54 00 69 00 6d 00 65 00 00 6f 08 08 29 9e 00
2010-11-09 03:00:03.22 spid51      *    T¿  @ i _ E n d  00 07 54 94 00 0a 40 00 69 00 5f 00 45 00 6e 00 64 00
2010-11-09 03:00:03.22 spid51      *  T i m e  o         54 00 69 00 6d 00 65 00 00 6f 08 08 8d 01 00 00 00 00
2010-11-09 03:00:03.22 spid51      *     @ i _ S t a t e 00 00 08 40 00 69 00 5f 00 53 00 74 00 61 00 74 00 65
2010-11-09 03:00:03.22 spid51      *    h    @ o _ I n s 00 00 68 01 01 00 0d 40 00 6f 00 5f 00 49 00 6e 00 73
2010-11-09 03:00:03.22 spid51      *   t a n c e I D  &  00 74 00 61 00 6e 00 63 00 65 00 49 00 44 00 01 26 04
2010-11-09 03:00:03.22 spid51      *                     00
2010-11-09 03:00:03.22 spid51      *  
2010-11-09 03:00:03.22 spid51      *
2010-11-09 03:00:03.22 spid51      *  MODULE                          BASE      END       SIZE
2010-11-09 03:00:03.22 spid51      * sqlservr                       01000000  02C1FFFF  01c20000
2010-11-09 03:00:03.22 spid51      * ntdll                          7C800000  7C8C1FFF  000c2000
2010-11-09 03:00:03.22 spid51      * kernel32                       77E40000  77F41FFF  00102000
2010-11-09 03:00:03.22 spid51      * MSVCR80                        78130000  781CAFFF  0009b000
2010-11-09 03:00:03.22 spid51      * msvcrt                         77BA0000  77BF9FFF  0005a000
2010-11-09 03:00:03.22 spid51      * MSVCP80                        7C420000  7C4A6FFF  00087000
2010-11-09 03:00:03.22 spid51      * ADVAPI32                       7D1E0000  7D27BFFF  0009c000
2010-11-09 03:00:03.22 spid51      * RPCRT4                         77C50000  77CEFFFF  000a0000
2010-11-09 03:00:03.22 spid51      * Secur32                        76F50000  76F62FFF  00013000
2010-11-09 03:00:03.22 spid51      * sqlos                          344D0000  344D4FFF  00005000
2010-11-09 03:00:03.22 spid51      * USERENV                        76920000  769E1FFF  000c2000
2010-11-09 03:00:03.22 spid51      * USER32                         77380000  77410FFF  00091000
2010-11-09 03:00:03.22 spid51      * GDI32                          77C00000  77C48FFF  00049000
2010-11-09 03:00:03.22 spid51      * WINMM                          76AA0000  76ACCFFF  0002d000
2010-11-09 03:00:03.22 spid51      * opends60                       333E0000  333E6FFF  00007000
2010-11-09 03:00:03.22 spid51      * NETAPI32                       71C40000  71C96FFF  00057000
2010-11-09 03:00:03.22 spid51      * psapi                          76B70000  76B7AFFF  0000b000
2010-11-09 03:00:03.22 spid51      * instapi                        48060000  48069FFF  0000a000
2010-11-09 03:00:03.22 spid51      * sqlevn70                       4F610000  4F7B8FFF  001a9000
2010-11-09 03:00:03.22 spid51      * rsaenh                         68000000  68034FFF  00035000
2010-11-09 03:00:03.22 spid51      * AUTHZ                          76C40000  76C53FFF  00014000
2010-11-09 03:00:03.22 spid51      * MSCOREE                        79000000  79049FFF  0004a000
2010-11-09 03:00:03.22 spid51      * mscoreei                       33AE0000  33B45FFF  00066000
2010-11-09 03:00:03.22 spid51      * ole32                          77670000  777A8FFF  00139000
2010-11-09 03:00:03.22 spid51      * msv1_0                         76C90000  76CB6FFF  00027000
2010-11-09 03:00:03.22 spid51      * cryptdll                       766E0000  766EBFFF  0000c000
2010-11-09 03:00:03.22 spid51      * WS2_32                         71C00000  71C16FFF  00017000
2010-11-09 03:00:03.22 spid51      * WS2HELP                        71BF0000  71BF7FFF  00008000
2010-11-09 03:00:03.22 spid51      * iphlpapi                       76CF0000  76D09FFF  0001a000
2010-11-09 03:00:03.22 spid51      * kerberos                       71CA0000  71CF8FFF  00059000
2010-11-09 03:00:03.22 spid51      * MSASN1                         76190000  761A1FFF  00012000
2010-11-09 03:00:03.22 spid51      * schannel                       76750000  76777FFF  00028000
2010-11-09 03:00:03.22 spid51      * CRYPT32                        761B0000  76242FFF  00093000
2010-11-09 03:00:03.22 spid51      * security                       71F60000  71F63FFF  00004000
2010-11-09 03:00:03.22 spid51      * VERSION                        77B90000  77B97FFF  00008000
2010-11-09 03:00:03.22 spid51      * SHELL32                        7C8D0000  7D0CEFFF  007ff000
2010-11-09 03:00:03.22 spid51      * SHLWAPI                        7D180000  7D1D1FFF  00052000
2010-11-09 03:00:03.22 spid51      * comctl32                       77420000  77522FFF  00103000
2010-11-09 03:00:03.22 spid51      * dssenh                         68100000  68126FFF  00027000
2010-11-09 03:00:03.22 spid51      * mswsock                        71B20000  71B60FFF  00041000
2010-11-09 03:00:03.22 spid51      * hnetcfg                        4A6F0000  4A749FFF  0005a000
2010-11-09 03:00:03.22 spid51      * wshtcpip                       71AE0000  71AE7FFF  00008000
2010-11-09 03:00:03.22 spid51      * NTMARTA                        77E00000  77E20FFF  00021000
2010-11-09 03:00:03.22 spid51      * WLDAP32                        76F10000  76F3DFFF  0002e000
2010-11-09 03:00:03.22 spid51      * SAMLIB                         7E020000  7E02EFFF  0000f000
2010-11-09 03:00:03.22 spid51      * ntdsapi                        766F0000  76703FFF  00014000
2010-11-09 03:00:03.22 spid51      * DNSAPI                         76ED0000  76EF9FFF  0002a000
2010-11-09 03:00:03.22 spid51      * winrnr                         76F70000  76F76FFF  00007000
2010-11-09 03:00:03.22 spid51      * rasadhlp                       76F80000  76F84FFF  00005000
2010-11-09 03:00:03.22 spid51      * xpsp2res                       4AE00000  4B0C4FFF  002c5000
2010-11-09 03:00:03.22 spid51      * CLBCatQ                        777B0000  77832FFF  00083000
2010-11-09 03:00:03.22 spid51      * OLEAUT32                       77D00000  77D8AFFF  0008b000
2010-11-09 03:00:03.22 spid51      * COMRes                         77010000  770D5FFF  000c6000
2010-11-09 03:00:03.22 spid51      * sqlncli                        4AB10000  4AD36FFF  00227000
2010-11-09 03:00:03.22 spid51      * COMCTL32                       77530000  775C6FFF  00097000
2010-11-09 03:00:03.22 spid51      * comdlg32                       762B0000  762F8FFF  00049000
2010-11-09 03:00:03.22 spid51      * SQLNCLIR                       4B150000  4B182FFF  00033000
2010-11-09 03:00:03.22 spid51      * sqlvdi                         4B190000  4B1B1FFF  00022000
2010-11-09 03:00:03.22 spid51      * dbghelp                        4A900000  4AA14FFF  00115000
2010-11-09 03:00:03.22 spid51      *
2010-11-09 03:00:03.22 spid51      *        Edi: 4B14EB90:  0014A8A8  4B14E9FA  00000005  04033594  04032470  00000016  
2010-11-09 03:00:03.22 spid51      *        Esi: 00000000:  
2010-11-09 03:00:03.22 spid51      *        Eax: 4B14DD2C:  000042AC  00000000  00000000  77E4BEF7  00000000  7C827739  
2010-11-09 03:00:03.22 spid51      *        Ebx: 0000003F:  
2010-11-09 03:00:03.22 spid51      *        Ecx: 4B14E39C:  00000000  00010007  4B14DF00  7813FD04  0000002E  00000100  
2010-11-09 03:00:03.22 spid51      *        Edx: 0000003D:  
2010-11-09 03:00:03.22 spid51      *        Eip: 77E4BEF7:  10C2C95E  01093D00  840FC000  00000095  F29DE950  9090FFFF  
2010-11-09 03:00:03.22 spid51      *        Ebp: 4B14DD7C:  4B14DDC0  021AE24C  000042AC  00000000  00000000  00000000  
2010-11-09 03:00:03.22 spid51      *      SegCs: 7813001B:  00000000  00000000  00000000  00000000  00000000  00000000  
2010-11-09 03:00:03.22 spid51      *     EFlags: 00000246:  
2010-11-09 03:00:03.22 spid51      *        Esp: 4B14DD28:  0400B5D8  000042AC  00000000  00000000  77E4BEF7  00000000  
2010-11-09 03:00:03.22 spid51      *      SegSs: 78130023:  00000000  00000000  00000000  00000000  00000000  00000000  
2010-11-09 03:00:03.22 spid51      * *******************************************************************************
2010-11-09 03:00:03.22 spid51      * -------------------------------------------------------------------------------
2010-11-09 03:00:03.22 spid51      * Short Stack Dump
2010-11-09 03:00:03.23 spid51      77E4BEF7 Module(kernel32+0000BEF7)
2010-11-09 03:00:03.23 spid51      021AE24C Module(sqlservr+011AE24C)
2010-11-09 03:00:03.23 spid51      021B2160 Module(sqlservr+011B2160)
2010-11-09 03:00:03.23 spid51      01E58E81 Module(sqlservr+00E58E81)
2010-11-09 03:00:03.23 spid51      01E59037 Module(sqlservr+00E59037)
2010-11-09 03:00:03.23 spid51      014E3777 Module(sqlservr+004E3777)
2010-11-09 03:00:03.23 spid51      0104132B Module(sqlservr+0004132B)
2010-11-09 03:00:03.23 spid51      0102A8C0 Module(sqlservr+0002A8C0)
2010-11-09 03:00:03.23 spid51      0102A7D1 Module(sqlservr+0002A7D1)
2010-11-09 03:00:03.23 spid51      010633E3 Module(sqlservr+000633E3)
2010-11-09 03:00:03.23 spid51      01063168 Module(sqlservr+00063168)
2010-11-09 03:00:03.23 spid51      0102522F Module(sqlservr+0002522F)
2010-11-09 03:00:03.23 spid51      010257F0 Module(sqlservr+000257F0)
2010-11-09 03:00:03.23 spid51      010232BB Module(sqlservr+000232BB)
2010-11-09 03:00:03.23 spid51      013D58A6 Module(sqlservr+003D58A6)
2010-11-09 03:00:03.23 spid51      013D571D Module(sqlservr+003D571D)
2010-11-09 03:00:03.23 spid51      013D55B2 Module(sqlservr+003D55B2)
2010-11-09 03:00:03.23 spid51      0102522F Module(sqlservr+0002522F)
2010-11-09 03:00:03.23 spid51      010257F0 Module(sqlservr+000257F0)
2010-11-09 03:00:03.23 spid51      010232BB Module(sqlservr+000232BB)
2010-11-09 03:00:03.23 spid51      0103D647 Module(sqlservr+0003D647)
2010-11-09 03:00:03.23 spid51      0103D30F Module(sqlservr+0003D30F)
2010-11-09 03:00:03.23 spid51      01006E27 Module(sqlservr+00006E27)
2010-11-09 03:00:03.23 spid51      01006F4D Module(sqlservr+00006F4D)
2010-11-09 03:00:03.23 spid51      01006C5D Module(sqlservr+00006C5D)
2010-11-09 03:00:03.23 spid51      010AAC3C Module(sqlservr+000AAC3C)
2010-11-09 03:00:03.23 spid51      010AAB5C Module(sqlservr+000AAB5C)
2010-11-09 03:00:03.23 spid51      010AA60C Module(sqlservr+000AA60C)
2010-11-09 03:00:03.24 spid51      010AA7A9 Module(sqlservr+000AA7A9)
2010-11-09 03:00:03.24 spid51      781329BB Module(MSVCR80+000029BB)
2010-11-09 03:00:03.25 spid51      78132A47 Module(MSVCR80+00002A47)
2010-11-09 03:00:03.25 spid51      Stack Signature for the dump is 0x3A9FD5AD
2010-11-09 03:00:05.09 spid51      External dump process return code 0x20000001.
External dump process returned no errors.

2010-11-09 03:00:07.07 spid51      Error: 824, Severity: 24, State: 2.
2010-11-09 03:00:07.07 spid51      SQL Server detected a logical consistency-based I/O error: torn page (expected signature: 0x55555555; actual signature: 0xaaaaaaa9). It occurred during a read of page (1:1490) in database ID 5 at offset 0x00000000ba4000 in file 'D:\Pfx Engagement\Admin\Data\Admin_Data.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.
2010-11-09 04:00:35.46 Server      Server resumed execution after being idle 2714 seconds: user activity awakened the server. This is an informational message only. No user action is required.
2010-11-09 04:01:01.73 spid51      I/O is frozen on database model. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
2010-11-09 04:01:01.73 spid52      I/O is frozen on database msdb. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
2010-11-09 04:01:01.74 spid53      I/O is frozen on database master. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
2010-11-09 04:01:05.95 spid52      I/O was resumed on database msdb. No user action is required.
2010-11-09 04:01:05.95 spid53      I/O was resumed on database master. No user action is required.
2010-11-09 04:01:05.95 spid51      I/O was resumed on database model. No user action is required.
2010-11-09 04:01:06.99 Backup      Database backed up. Database: model, creation date(time): 2003/04/08(09:13:36), pages dumped: 1, first LSN: 130:192:37, last LSN: 130:216:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{1F51F641-7BB8-42FB-9ED7-3A75741D2118}1'}). This is an informational message only. No user action is required.
2010-11-09 04:01:06.99 Backup      Database backed up. Database: master, creation date(time): 2010/11/07(08:46:17), pages dumped: 1, first LSN: 682:456:37, last LSN: 682:480:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{1F51F641-7BB8-42FB-9ED7-3A75741D2118}3'}). This is an informational message only. No user action is required.
2010-11-09 04:01:07.05 Backup      Database backed up. Database: msdb, creation date(time): 2005/10/14(01:54:05), pages dumped: 1, first LSN: 416:248:180, last LSN: 416:328:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{1F51F641-7BB8-42FB-9ED7-3A75741D2118}2'}). This is an informational message only. No user action is required.
2010-11-09 05:42:35.21 Server      Server resumed execution after being idle 5176 seconds: user activity awakened the server. This is an informational message only. No user action is required.
2010-11-09 09:51:04.71 Server      Server resumed execution after being idle 13996 seconds: user activity awakened the server. This is an informational message only. No user action is required.
2010-11-09 09:52:02.17 spid51      Error: 824, Severity: 24, State: 2.
2010-11-09 09:52:02.17 spid51      SQL Server detected a logical consistency-based I/O error: torn page (expected signature: 0x55555555; actual signature: 0xaaaaaaa9). It occurred during a read of page (1:162) in database ID 5 at offset 0x00000000144000 in file 'D:\Pfx Engagement\Admin\Data\Admin_Data.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.
2010-11-09 09:52:40.18 spid53      DBCC CHECKDB (master) executed by mcserv01\support found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 1 seconds.
2010-11-09 09:52:45.49 spid53      DBCC CHECKDB (mssqlsystemresource) executed by mcserv01\support found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 4 seconds.
2010-11-09 09:56:36.00 spid51      Error: 824, Severity: 24, State: 2.
2010-11-09 09:56:36.00 spid51      SQL Server detected a logical consistency-based I/O error: torn page (expected signature: 0x55555555; actual signature: 0xaaaaaaa9). It occurred during a read of page (1:74) in database ID 5 at offset 0x00000000094000 in file 'D:\Pfx Engagement\Admin\Data\Admin_Data.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.
2010-11-09 09:56:54.45 spid51      Using 'xpstar90.dll' version '2005.90.4035' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
2010-11-09 10:06:27.40 spid51      Error: 824, Severity: 24, State: 2.
2010-11-09 10:06:27.40 spid51      SQL Server detected a logical consistency-based I/O error: torn page (expected signature: 0x55555555; actual signature: 0xaaaaaaa9). It occurred during a read of page (1:162) in database ID 5 at offset 0x00000000144000 in file 'D:\Pfx Engagement\Admin\Data\Admin_Data.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.
2010-11-09 22:00:04.59 Server      Server resumed execution after being idle 41904 seconds: user activity awakened the server. This is an informational message only. No user action is required.
2010-11-09 22:00:06.95 spid51      Error: 824, Severity: 24, State: 2.
2010-11-09 22:00:06.95 spid51      SQL Server detected a logical consistency-based I/O error: torn page (expected signature: 0x55555555; actual signature: 0xaaaaaaa9). It occurred during a read of page (1:74) in database ID 5 at offset 0x00000000094000 in file 'D:\Pfx Engagement\Admin\Data\Admin_Data.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.
2010-11-10 01:00:30.56 spid1s      Server resumed execution after being idle 9912 seconds. Reason: timer event.
2010-11-10 03:00:00.23 Server      Server resumed execution after being idle 6257 seconds: user activity awakened the server. This is an informational message only. No user action is required.
2010-11-10 03:00:01.64 spid51      Using 'dbghelp.dll' version '4.0.5'
2010-11-10 03:00:01.64 spid51      **Dump thread - spid = 51, PSS = 0x075495D8, EC = 0x075495E0
2010-11-10 03:00:01.64 spid51      ***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0049.txt
2010-11-10 03:00:01.64 spid51      * *******************************************************************************
2010-11-10 03:00:01.64 spid51      *
2010-11-10 03:00:01.64 spid51      * BEGIN STACK DUMP:
2010-11-10 03:00:01.64 spid51      *   11/10/10 03:00:01 spid 51
2010-11-10 03:00:01.64 spid51      *
2010-11-10 03:00:01.64 spid51      * CPerIndexMetaQS::ErrorAbort - Index corruption
2010-11-10 03:00:01.64 spid51      *
2010-11-10 03:00:01.64 spid51      * Input Buffer 255 bytes -
2010-11-10 03:00:01.64 spid51      *                     16 00 00 00 12 00 00 00 02 00 00 00 00 00 00 00 00 00
2010-11-10 03:00:01.64 spid51      *        U S P _ A d  01 00 00 00 1b 00 55 00 53 00 50 00 5f 00 41 00 64 00
2010-11-10 03:00:01.64 spid51      *  m i n _ S c h T a  6d 00 69 00 6e 00 5f 00 53 00 63 00 68 00 54 00 61 00
2010-11-10 03:00:01.64 spid51      *  s k H i s t o r y  73 00 6b 00 48 00 69 00 73 00 74 00 6f 00 72 00 79 00
2010-11-10 03:00:01.64 spid51      *  I n s         @ i _ T a 49 00 6e 00 73 00 00 00 09 40 00 69 00 5f 00 54 00 61
2010-11-10 03:00:01.64 spid51      *   s k I D  &             00 73 00 6b 00 49 00 44 00 00 26 04 04 01 00 00 00 09
2010-11-10 03:00:01.64 spid51      *  @ i _ S t a t u s  40 00 69 00 5f 00 53 00 74 00 61 00 74 00 75 00 73 00
2010-11-10 03:00:01.64 spid51      *   &       @ i _ M e 00 26 04 04 02 00 00 00 0a 40 00 69 00 5f 00 4d 00 65
2010-11-10 03:00:01.64 spid51      *   s s a g e  §Ð        Ð 00 73 00 73 00 61 00 67 00 65 00 00 a7 d0 07 09 04 d0
2010-11-10 03:00:01.64 spid51      *   4   @ i _ S t a r 00 34 00 00 0c 40 00 69 00 5f 00 53 00 74 00 61 00 72
2010-11-10 03:00:01.64 spid51      *   t T i m e  o  *¿  00 74 00 54 00 69 00 6d 00 65 00 00 6f 08 08 2a 9e 00
2010-11-10 03:00:01.64 spid51      *   1Q¿  @ i _ E n d  00 31 51 94 00 0a 40 00 69 00 5f 00 45 00 6e 00 64 00
2010-11-10 03:00:01.64 spid51      *  T i m e  o         54 00 69 00 6d 00 65 00 00 6f 08 08 8d 01 00 00 00 00
2010-11-10 03:00:01.64 spid51      *     @ i _ S t a t e 00 00 08 40 00 69 00 5f 00 53 00 74 00 61 00 74 00 65
2010-11-10 03:00:01.64 spid51      *    h    @ o _ I n s 00 00 68 01 01 00 0d 40 00 6f 00 5f 00 49 00 6e 00 73
2010-11-10 03:00:01.64 spid51      *   t a n c e I D  &  00 74 00 61 00 6e 00 63 00 65 00 49 00 44 00 01 26 04
2010-11-10 03:00:01.64 spid51      *                     00
2010-11-10 03:00:01.64 spid51      *  
2010-11-10 03:00:01.64 spid51      *
2010-11-10 03:00:01.64 spid51      *  MODULE                          BASE      END       SIZE
2010-11-10 03:00:01.64 spid51      * sqlservr                       01000000  02C1FFFF  01c20000
2010-11-10 03:00:01.64 spid51      * ntdll                          7C800000  7C8C1FFF  000c2000
2010-11-10 03:00:01.64 spid51      * kernel32                       77E40000  77F41FFF  00102000
2010-11-10 03:00:01.64 spid51      * MSVCR80                        78130000  781CAFFF  0009b000
2010-11-10 03:00:01.64 spid51      * msvcrt                         77BA0000  77BF9FFF  0005a000
2010-11-10 03:00:01.64 spid51      * MSVCP80                        7C420000  7C4A6FFF  00087000
2010-11-10 03:00:01.64 spid51      * ADVAPI32                       7D1E0000  7D27BFFF  0009c000
2010-11-10 03:00:01.64 spid51      * RPCRT4                         77C50000  77CEFFFF  000a0000
2010-11-10 03:00:01.64 spid51      * Secur32                        76F50000  76F62FFF  00013000
2010-11-10 03:00:01.64 spid51      * sqlos                          344D0000  344D4FFF  00005000
2010-11-10 03:00:01.64 spid51      * USERENV                        76920000  769E1FFF  000c2000
2010-11-10 03:00:01.64 spid51      * USER32                         77380000  77410FFF  00091000
2010-11-10 03:00:01.64 spid51      * GDI32                          77C00000  77C48FFF  00049000
2010-11-10 03:00:01.64 spid51      * WINMM                          76AA0000  76ACCFFF  0002d000
2010-11-10 03:00:01.64 spid51      * opends60                       333E0000  333E6FFF  00007000
2010-11-10 03:00:01.64 spid51      * NETAPI32                       71C40000  71C96FFF  00057000
2010-11-10 03:00:01.64 spid51      * psapi                          76B70000  76B7AFFF  0000b000
2010-11-10 03:00:01.64 spid51      * instapi                        48060000  48069FFF  0000a000
2010-11-10 03:00:01.64 spid51      * sqlevn70                       4F610000  4F7B8FFF  001a9000
2010-11-10 03:00:01.64 spid51      * rsaenh                         68000000  68034FFF  00035000
2010-11-10 03:00:01.64 spid51      * AUTHZ                          76C40000  76C53FFF  00014000
2010-11-10 03:00:01.64 spid51      * MSCOREE                        79000000  79049FFF  0004a000
2010-11-10 03:00:01.64 spid51      * mscoreei                       33AE0000  33B45FFF  00066000
2010-11-10 03:00:01.64 spid51      * ole32                          77670000  777A8FFF  00139000
2010-11-10 03:00:01.64 spid51      * msv1_0                         76C90000  76CB6FFF  00027000
2010-11-10 03:00:01.64 spid51      * cryptdll                       766E0000  766EBFFF  0000c000
2010-11-10 03:00:01.64 spid51      * WS2_32                         71C00000  71C16FFF  00017000
2010-11-10 03:00:01.64 spid51      * WS2HELP                        71BF0000  71BF7FFF  00008000
2010-11-10 03:00:01.64 spid51      * iphlpapi                       76CF0000  76D09FFF  0001a000
2010-11-10 03:00:01.64 spid51      * kerberos                       71CA0000  71CF8FFF  00059000
2010-11-10 03:00:01.64 spid51      * MSASN1                         76190000  761A1FFF  00012000
2010-11-10 03:00:01.64 spid51      * schannel                       76750000  76777FFF  00028000
2010-11-10 03:00:01.64 spid51      * CRYPT32                        761B0000  76242FFF  00093000
2010-11-10 03:00:01.64 spid51      * security                       71F60000  71F63FFF  00004000
2010-11-10 03:00:01.64 spid51      * VERSION                        77B90000  77B97FFF  00008000
2010-11-10 03:00:01.64 spid51      * SHELL32                        7C8D0000  7D0CEFFF  007ff000
2010-11-10 03:00:01.64 spid51      * SHLWAPI                        7D180000  7D1D1FFF  00052000
2010-11-10 03:00:01.64 spid51      * comctl32                       77420000  77522FFF  00103000
2010-11-10 03:00:01.64 spid51      * dssenh                         68100000  68126FFF  00027000
2010-11-10 03:00:01.64 spid51      * mswsock                        71B20000  71B60FFF  00041000
2010-11-10 03:00:01.64 spid51      * hnetcfg                        4A6F0000  4A749FFF  0005a000
2010-11-10 03:00:01.64 spid51      * wshtcpip                       71AE0000  71AE7FFF  00008000
2010-11-10 03:00:01.64 spid51      * NTMARTA                        77E00000  77E20FFF  00021000
2010-11-10 03:00:01.64 spid51      * WLDAP32                        76F10000  76F3DFFF  0002e000
2010-11-10 03:00:01.64 spid51      * SAMLIB                         7E020000  7E02EFFF  0000f000
2010-11-10 03:00:01.64 spid51      * ntdsapi                        766F0000  76703FFF  00014000
2010-11-10 03:00:01.64 spid51      * DNSAPI                         76ED0000  76EF9FFF  0002a000
2010-11-10 03:00:01.64 spid51      * winrnr                         76F70000  76F76FFF  00007000
2010-11-10 03:00:01.64 spid51      * rasadhlp                       76F80000  76F84FFF  00005000
2010-11-10 03:00:01.64 spid51      * xpsp2res                       4AE00000  4B0C4FFF  002c5000
2010-11-10 03:00:01.64 spid51      * CLBCatQ                        777B0000  77832FFF  00083000
2010-11-10 03:00:01.64 spid51      * OLEAUT32                       77D00000  77D8AFFF  0008b000
2010-11-10 03:00:01.64 spid51      * COMRes                         77010000  770D5FFF  000c6000
2010-11-10 03:00:01.64 spid51      * sqlncli                        4AB10000  4AD36FFF  00227000
2010-11-10 03:00:01.64 spid51      * COMCTL32                       77530000  775C6FFF  00097000
2010-11-10 03:00:01.64 spid51      * comdlg32                       762B0000  762F8FFF  00049000
2010-11-10 03:00:01.64 spid51      * SQLNCLIR                       4B150000  4B182FFF  00033000
2010-11-10 03:00:01.64 spid51      * sqlvdi                         4B190000  4B1B1FFF  00022000
2010-11-10 03:00:01.64 spid51      * xpstar90                       4C5E0000  4C62AFFF  0004b000
2010-11-10 03:00:01.64 spid51      * SQLSCM90                       34370000  34378FFF  00009000
2010-11-10 03:00:01.64 spid51      * ODBC32                         4C630000  4C66CFFF  0003d000
2010-11-10 03:00:01.64 spid51      * BatchParser90                  4ADE0000  4ADFEFFF  0001f000
2010-11-10 03:00:01.64 spid51      * ATL80                          7C630000  7C64AFFF  0001b000
2010-11-10 03:00:01.64 spid51      * odbcint                        4B130000  4B146FFF  00017000
2010-11-10 03:00:01.64 spid51      * xpstar90                       4B2B0000  4B2D5FFF  00026000
2010-11-10 03:00:01.64 spid51      * dbghelp                        4A9A0000  4AAB4FFF  00115000
2010-11-10 03:00:01.64 spid51      *
2010-11-10 03:00:01.64 spid51      *        Edi: 33EAEB90:  0015A428  33EAE9FA  00000005  074B9594  074B8470  00000016  
2010-11-10 03:00:01.64 spid51      *        Esi: 00000000:  
2010-11-10 03:00:01.64 spid51      *        Eax: 33EADD2C:  000042AC  00000000  00000000  77E4BEF7  00000000  7C827739  
2010-11-10 03:00:01.64 spid51      *        Ebx: 0000003F:  
2010-11-10 03:00:01.64 spid51      *        Ecx: 33EAE39C:  00000000  00010007  33EADF00  7813FD04  0000002E  00000100  
2010-11-10 03:00:01.64 spid51      *        Edx: 0000003D:  
2010-11-10 03:00:01.64 spid51      *        Eip: 77E4BEF7:  10C2C95E  01093D00  840FC000  00000095  F29DE950  9090FFFF  
2010-11-10 03:00:01.64 spid51      *        Ebp: 33EADD7C:  33EADDC0  021AE24C  000042AC  00000000  00000000  00000000  
2010-11-10 03:00:01.64 spid51      *      SegCs: 7813001B:  00000000  00000000  00000000  00000000  00000000  00000000  
2010-11-10 03:00:01.64 spid51      *     EFlags: 00000246:  
2010-11-10 03:00:01.64 spid51      *        Esp: 33EADD28:  075495D8  000042AC  00000000  00000000  77E4BEF7  00000000  
2010-11-10 03:00:01.64 spid51      *      SegSs: 78130023:  00000000  00000000  00000000  00000000  00000000  00000000  
2010-11-10 03:00:01.64 spid51      * *******************************************************************************
2010-11-10 03:00:01.64 spid51      * -------------------------------------------------------------------------------
2010-11-10 03:00:01.64 spid51      * Short Stack Dump
2010-11-10 03:00:01.65 spid51      77E4BEF7 Module(kernel32+0000BEF7)
2010-11-10 03:00:01.65 spid51      021AE24C Module(sqlservr+011AE24C)
2010-11-10 03:00:01.65 spid51      021B2160 Module(sqlservr+011B2160)
2010-11-10 03:00:01.65 spid51      01E58E81 Module(sqlservr+00E58E81)
2010-11-10 03:00:01.65 spid51      01E59037 Module(sqlservr+00E59037)
2010-11-10 03:00:01.65 spid51      014E3777 Module(sqlservr+004E3777)
2010-11-10 03:00:01.65 spid51      0104132B Module(sqlservr+0004132B)
2010-11-10 03:00:01.65 spid51      0102A8C0 Module(sqlservr+0002A8C0)
2010-11-10 03:00:01.65 spid51      0102A7D1 Module(sqlservr+0002A7D1)
2010-11-10 03:00:01.65 spid51      010633E3 Module(sqlservr+000633E3)
2010-11-10 03:00:01.65 spid51      01063168 Module(sqlservr+00063168)
2010-11-10 03:00:01.65 spid51      0102522F Module(sqlservr+0002522F)
2010-11-10 03:00:01.65 spid51      010257F0 Module(sqlservr+000257F0)
2010-11-10 03:00:01.65 spid51      010232BB Module(sqlservr+000232BB)
2010-11-10 03:00:01.65 spid51      013D58A6 Module(sqlservr+003D58A6)
2010-11-10 03:00:01.65 spid51      013D571D Module(sqlservr+003D571D)
2010-11-10 03:00:01.65 spid51      013D55B2 Module(sqlservr+003D55B2)
2010-11-10 03:00:01.65 spid51      0102522F Module(sqlservr+0002522F)
2010-11-10 03:00:01.65 spid51      010257F0 Module(sqlservr+000257F0)
2010-11-10 03:00:01.65 spid51      010232BB Module(sqlservr+000232BB)
2010-11-10 03:00:01.65 spid51      0103D647 Module(sqlservr+0003D647)
2010-11-10 03:00:01.65 spid51      0103D30F Module(sqlservr+0003D30F)
2010-11-10 03:00:01.65 spid51      01006E27 Module(sqlservr+00006E27)
2010-11-10 03:00:01.65 spid51      01006F4D Module(sqlservr+00006F4D)
2010-11-10 03:00:01.65 spid51      01006C5D Module(sqlservr+00006C5D)
2010-11-10 03:00:01.65 spid51      010AAC3C Module(sqlservr+000AAC3C)
2010-11-10 03:00:01.65 spid51      010AAB5C Module(sqlservr+000AAB5C)
2010-11-10 03:00:01.68 spid51      010AA60C Module(sqlservr+000AA60C)
2010-11-10 03:00:01.69 spid51      010AA7A9 Module(sqlservr+000AA7A9)
2010-11-10 03:00:01.69 spid51      781329BB Module(MSVCR80+000029BB)
2010-11-10 03:00:01.69 spid51      78132A47 Module(MSVCR80+00002A47)
2010-11-10 03:00:01.70 spid51      Stack Signature for the dump is 0x3A9FD5AD
2010-11-10 03:00:04.03 spid51      External dump process return code 0x20000001.
External dump process returned no errors.

2010-11-10 03:00:05.62 spid51      Error: 824, Severity: 24, State: 2.
2010-11-10 03:00:05.62 spid51      SQL Server detected a logical consistency-based I/O error: torn page (expected signature: 0x55555555; actual signature: 0xaaaaaaa9). It occurred during a read of page (1:1490) in database ID 5 at offset 0x00000000ba4000 in file 'D:\Pfx Engagement\Admin\Data\Admin_Data.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.
2010-11-10 04:00:33.48 Server      Server resumed execution after being idle 2714 seconds: user activity awakened the server. This is an informational message only. No user action is required.
2010-11-10 04:00:45.92 spid52      I/O is frozen on database model. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
2010-11-10 04:00:45.92 spid51      I/O is frozen on database msdb. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
2010-11-10 04:00:45.93 spid53      I/O is frozen on database master. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
2010-11-10 04:00:49.03 spid53      I/O was resumed on database master. No user action is required.
2010-11-10 04:00:49.03 spid51      I/O was resumed on database msdb. No user action is required.
2010-11-10 04:00:49.04 spid52      I/O was resumed on database model. No user action is required.
2010-11-10 04:00:50.06 Backup      Database backed up. Database: master, creation date(time): 2010/11/07(08:46:17), pages dumped: 1, first LSN: 683:168:37, last LSN: 683:192:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{C1A3F8DA-454D-470A-A9DA-BC2988FA675B}3'}). This is an informational message only. No user action is required.
2010-11-10 04:00:50.16 Backup      Database backed up. Database: model, creation date(time): 2003/04/08(09:13:36), pages dumped: 1, first LSN: 130:272:37, last LSN: 130:296:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{C1A3F8DA-454D-470A-A9DA-BC2988FA675B}1'}). This is an informational message only. No user action is required.
2010-11-10 04:00:50.20 Backup      Database backed up. Database: msdb, creation date(time): 2005/10/14(01:54:05), pages dumped: 1, first LSN: 416:456:180, last LSN: 416:536:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{C1A3F8DA-454D-470A-A9DA-BC2988FA675B}2'}). This is an informational message only. No user action is required.
2010-11-10 05:41:38.35 Server      Server resumed execution after being idle 5136 seconds: user activity awakened the server. This is an informational message only. No user action is required.
2010-11-10 08:11:48.23 Server      Server resumed execution after being idle 8096 seconds: user activity awakened the server. This is an informational message only. No user action is required.
2010-11-10 08:11:49.85 spid51      Error: 824, Severity: 24, State: 2.
2010-11-10 08:11:49.85 spid51      SQL Server detected a logical consistency-based I/O error: torn page (expected signature: 0x55555555; actual signature: 0xaaaaaaa9). It occurred during a read of page (1:74) in database ID 5 at offset 0x00000000094000 in file 'D:\Pfx Engagement\Admin\Data\Admin_Data.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.
0
 
LVL 16

Expert Comment

by:EvilPostIt
Comment Utility
Ok first things first, on your 2000 instance (the first log posted you have lost the master database. This means that you will have to do a master database rebuild as below

http://technet.microsoft.com/en-us/library/aa197950(SQL.80).aspx

Once this is restored the database will basically think it is a fresh install. Although we can troubleshoot this bit by bit. Am looking at the second log now.
0
 

Author Comment

by:BizTekConnection
Comment Utility
Forgive my lack of SQL knowledge, but if the master DB thinks it is a fresh install, does the end user lose any data that was in that DB instance?
0
 
LVL 16

Expert Comment

by:EvilPostIt
Comment Utility
The second instance (Which is SQL Server 2005) still seems to be up. As per the log master, model & msdb all started successfully (At 3am on the 7th of November) and the log entries have carried on until 8:11 today. So this is not crashing. Can you confirm wether you have SQL Server Management Studio.

The SQL Server Services for SQL 2005 will be SQL Server ******
0
 
LVL 16

Expert Comment

by:EvilPostIt
Comment Utility
The end user still may loose data as we do not know the state of the user databases yet. The user databases will not be touched as part of this process. You will need to re-attatch them after the master rebuild. But to be safe it might be an idea to copy the data files off somewhere safe.
0
 

Author Comment

by:BizTekConnection
Comment Utility
I can confirm I have SQL Server Management Studio installed on this box.  I'll look at copying the user DB files and then doing the master rebuild against the master DB for the SQL 2000 instance.
0
 
LVL 16

Expert Comment

by:EvilPostIt
Comment Utility
Can you connect to the SQL Server 2005 instance using SQL Server Management Studio? As this does seem to be up and running.
0
 

Author Comment

by:BizTekConnection
Comment Utility
Yes, I can connect to the SQL server 2005 instance, and none of the DBs there are showing any issues at a quick glance.  Yet isn't that the instance complaining of a torn page?
0
 
LVL 16

Expert Comment

by:EvilPostIt
Comment Utility
Just noticed that you are using the free versions SQL 2000 & 2005.

Look at this for MSDE master recovery.

http://blogs.msdn.com/b/joaol/archive/2008/03/13/how-to-rebuild-your-master-database-in-msde-when-it-became-corrupted.aspx
0
 
LVL 16

Expert Comment

by:EvilPostIt
Comment Utility
Yes but in the log. They will still be online.

USE MASTER
GO
Run select name from sys.databases WHERE DB_ID=5

I think this is going to be a database Called CentralAdmin but just to be safe better check.

If it is the CentralAdmin database do the following

USE CentralAdmin
GO
DBCC CHECKDB WITH NO_INFOMSGS
0
 
LVL 16

Expert Comment

by:EvilPostIt
Comment Utility
Sorry that first section should be...

USE MASTER
GO
select name from sys.databases WHERE DB_ID=5

without the "run"
0
 

Author Comment

by:BizTekConnection
Comment Utility
Ok, two questions :

1. Where do I input the CLI from the last link  "rebuilding MSDE master DB"?

2. This is what I get when I tried running the query in SSMSE after connecting to the Profxengagement instance : Msg 207, Level 16, State 1, Line 1
Invalid column name 'DB_ID'.
0
 
LVL 16

Expert Comment

by:EvilPostIt
Comment Utility
Second question first.

USE MASTER
GO
select name from sys.databases WHERE Dataabse_ID=5
0
 

Author Comment

by:BizTekConnection
Comment Utility
Ok, it is CentralAdmin, and I tried to do the DBCC checkdb against it.  Here are the results.

Msg 8921, Level 16, State 1, Line 1
Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.
Msg 824, Level 24, State 2, Line 1
SQL Server detected a logical consistency-based I/O error: torn page (expected signature: 0x55555555; actual signature: 0xaaaaaaa9). It occurred during a read of page (1:114) in database ID 8 at offset 0x000000000e4000 in file 'D:\Pfx Engagement\Admin\Data\Admin_Data.MDF:MSSQL_DBCC8'.  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.
0
 
LVL 16

Expert Comment

by:EvilPostIt
Comment Utility
Could you post the output of SELECT NAME,Database_ID FROM sys.databases

This is giving information relating to Database ID 8????? hmmm

Also just to be sure do DBCC CHECKDB ('CentralAdmin') WITH NO_INFOMSGS,ALL_ERRORMSGS
0
 

Author Comment

by:BizTekConnection
Comment Utility
Just tried that, I did have 'use central admin' and 'go' for the first two lines, with a third line doing the dbcc checkdb as you specify.  Here's a screenshot of the results of the select name query.
sqlqueryname.JPG
0
 

Author Comment

by:BizTekConnection
Comment Utility
Whoops, forgot to mention : after running the query with the modification for the DBCC CHECKDB lines I still got the same msg 8921, level 16, state 1, line 1 error as well as the msg 824, level 24, state 2, line 1 error.
0
 
LVL 16

Expert Comment

by:EvilPostIt
Comment Utility
Could you remove the where clause....

Also is the dbcc output exactly the same as the one before? Could you post it again.
0
 
LVL 16

Expert Comment

by:EvilPostIt
Comment Utility
Run the following against the CentralAdmin database

DBCC TRACEON(3604)
DBCC PAGE('CentralAdmin',1,114,0)
0
 

Author Comment

by:BizTekConnection
Comment Utility
The only query I saw a 'where' clause to remove is the "select name" query - when I remove the "where" clause I get an error : Msg 102, Level 15, State 1, Line 1
Incorrect syntax near '='.


Attached is my query/results for the dbcc checkdb
dbccerror.JPG
0
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

 

Author Comment

by:BizTekConnection
Comment Utility
Ok, here are the results of the DBCC traceon(3604) query.


dbcctraceon.JPG
0
 
LVL 16

Expert Comment

by:EvilPostIt
Comment Utility
Ok this explain why the DBCC command cannot complete without error. One of the system tables is corrupt which mean you wont be able to fix this database. You will have to create a new one and copy the data across.

As you can see under the metadata section is states that this page belongs to object id 60 which is the sysobjvalues table (A system table).

Find a user table and see if you can run DBCC CHECKTABLE ('YOURTABLE').
0
 
LVL 16

Expert Comment

by:EvilPostIt
Comment Utility
Actually you may also want to do SELECT OBJECT_NAME(60) just to make sure it does return the sysobjvalues table.
0
 

Author Comment

by:BizTekConnection
Comment Utility
I think I correctly ran the DBCC Checktable against one of the user tables :


dbcctest.JPG
0
 

Author Comment

by:BizTekConnection
Comment Utility
So which query do I want to add "SELECT OBJECT_NAME(60) " to?
0
 
LVL 16

Expert Comment

by:EvilPostIt
Comment Utility
just run it against the CentralAdmin database it will return which object is corrupted.
0
 

Author Comment

by:BizTekConnection
Comment Utility
Ok, results of running that against CentralAdmin is one line, one column : sysobjvalues
0
 
LVL 16

Expert Comment

by:EvilPostIt
Comment Utility
Now run the following.

exec sp_msforeachtable "print 'DBCC CHECKTABLE (''?'')'"

Copy the output into another query window and execute that.
0
 
LVL 16

Expert Comment

by:EvilPostIt
Comment Utility
Yes just as i thought and mentioned earlier.
0
 
LVL 16

Expert Comment

by:EvilPostIt
Comment Utility
Could you also do a DBCC CHECKDB with the other 2 databases on the system to ensure they are ok.

Try this too

Its worth taking a backup.

BACKUP DATABASE CentralAdmin to disk='D:\CentralAdmin.BAK'
0
 

Author Comment

by:BizTekConnection
Comment Utility
Ok, here is a copy/paste of the messages I got when I ran your above query starting with "exec sp_msforeeachtable" :

Msg 824, Level 24, State 2, Procedure sp_MSforeach_worker, Line 31
SQL Server detected a logical consistency-based I/O error: torn page (expected signature: 0xaaaaaaaa; actual signature: 0x55555556). It occurred during a read of page (1:218) in database ID 5 at offset 0x000000001b4000 in file 'D:\Pfx Engagement\Admin\Data\Admin_Data.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.
0
 

Author Comment

by:BizTekConnection
Comment Utility
The backup database command executed successfully.  I now have a .bak file on the root of the D partition for that DB.  I tried to run a dbcc on the second (long name) DB "CentralBin_79a5b99c etc etc" and couldn't get it to like the syntax.  I tried clicking on the DB to see if I could go into properties and copy/paste the name rather than manually type it for the dbcc and it did come up with an error and mark the DB as suspect.

The Datair_datair instance came back with 0 errors, so it looks like it is ok.
0
 
LVL 16

Expert Comment

by:EvilPostIt
Comment Utility
you need single quotes so

DBCC CHECKDB ('CentralBin_79A5B99C-C5EC-4ADB-AA95-6589884D04B6') WITH NO_INFOMSGS,ALL_ERRORMSGS
0
 
LVL 16

Expert Comment

by:EvilPostIt
Comment Utility
Where ever you see " page (1:218)" do the dbcc page ('CentralAdmin',1,218,0)

 page (1:218)  1 is the file number and 218 is the page number.
0
 

Author Comment

by:BizTekConnection
Comment Utility
Ok, here's what I get from running the DBCC against CentralBin as you suggested :

Msg 926, Level 14, State 1, Line 1
Database 'CentralBin_79A5B99C-C5EC-4ADB-AA95-6589884D04B6' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.

Where am I looking for these "page (1:218)" items to run the dbcc against?
0
 
LVL 16

Expert Comment

by:EvilPostIt
Comment Utility
In the output that you provided to me from the dbcc statements.

With regards to the other point

ALTER DATABASE [CentralBin_79A5B99C-C5EC-4ADB-AA95-6589884D04B6] SET EMERGENCY
DBCC CHECKDB ('CentralBin_79A5B99C-C5EC-4ADB-AA95-6589884D04B6') WITH NO_INFOMSGS,ALL_ERRORMSGS

As you have taken a backup of CentralAdmin run the following command
DBCC CHECKDB ('CentralAdmin',REPAIR_ALLOW_DATA_LOSS)

Yes are most probably going to loose some data from doing this but without backups you have no choice.

If that fails (which i think it will due to the system table corruption) start building a new database as per the attatched link. Although dont delete the corrupted one as most of the user tables seem fine.

http://blog.sqlauthority.com/2007/08/21/sql-server-2005-create-script-to-copy-database-schema-and-all-the-objects-stored-procedure-functions-triggers-tables-views-constraints-and-all-other-database-objects/

0
 
LVL 16

Expert Comment

by:EvilPostIt
Comment Utility
I will check back on later as i need to leave now. Shold be about 1-2 hours but have given you a fair bit to play with in my last post.
0
 
LVL 16

Expert Comment

by:EvilPostIt
Comment Utility
How's it going?
0
 

Author Comment

by:BizTekConnection
Comment Utility
Still working on this, I ended up going to lunch right after you left and got caught up in some install/fix work for some other issues afterwards.  I'm going to chew on the last post you added with the recovery options outlined.  
0
 

Author Comment

by:BizTekConnection
Comment Utility
Ok, I added the alter database line to my DBCC attemtp for DB "CentralBin" and here are my results : Msg 8921, Level 16, State 1, Line 2
Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.
Msg 9003, Level 20, State 1, Line 1
The log scan number (810:468:1) passed to log scan in database 'CentralBin_79A5B99C-C5EC-4ADB-AA95-6589884D04B6' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup.
Msg 3414, Level 21, State 1, Line 1
An error occurred during recovery, preventing the database 'CentralBin_79A5B99C-C5EC-4ADB-AA95-6589884D04B6' (database ID 6) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.
Msg 824, Level 24, State 2, Line 2
SQL Server detected a logical consistency-based I/O error: torn page (expected signature: 0xaaaaaaaa; actual signature: 0x55555556). It occurred during a read of page (1:597) in database ID 6 at offset 0x000000004aa000 in file 'D:\Pfx Engagement\Admin\Data\CentralBin_79A5B99C-C5EC-4ADB-AA95-6589884D04B6_Data.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.

Additionally I tried both the "repair_allow_data_loss" and the link you showed me, the repair attempt came back with the same torn page issue, and I'm attaching the results of the script generation attempt.
scriptattempt.JPG
0
 
LVL 16

Expert Comment

by:EvilPostIt
Comment Utility
Ok, with the centralbin db try that sp_msforeachtable script I gave you before to determine if the user tables are corrupted.

With regard to the other database try right clicking on the database objects and selecting the script option.

On the other hand what you could do would be to go back to the software vendor and get the build scripts for the database as all you need is a shell of the database to import into.

Did you try the dbcc checktable repair_allow_dataloss?
0
 

Author Comment

by:BizTekConnection
Comment Utility
Yes, I tried dbcc checktable repair_allow_dataloss before attempting the script, same torn page errors we've been seeing out of this darned thing all day.  I'll see about trying to script per DB object.
0
 

Author Comment

by:BizTekConnection
Comment Utility
I ran exec sp_msforeachtable against the CentralBin DB and got the following error :

Msg 601, Level 12, State 3, Procedure sp_MSforeach_worker, Line 31
Could not continue scan with NOLOCK due to data movement.


As for scripting each DB object, I fear my lack of SQL knowledge has possibly got me trying the wrong thing here.  What are the exact steps I'd need to do, as I can't seem to find a way to try to create the script without doing it against the entire DB.
0
 

Author Comment

by:BizTekConnection
Comment Utility
Ok, I've got to leave for the day but I'll check back on this in the morning.  Additionally I'll see about contacting the vendor and what kind of luck I have on that route as it may be the easiest path to take to get a working copy of this DB back up and running.
0
 
LVL 16

Accepted Solution

by:
EvilPostIt earned 500 total points
Comment Utility
Ok try the following now....

ALTER DATABASE [CentralAdmin] SET EMERGENCY
ALTER DATABASE CentralAdmin SET SINGLE_USER
DBCC CHECKDB ('CentralAdmin',REPAIR_ALLOW_DATA_LOSS) WITH NO_INFOMSGS

With regard to your point about not feeling confident about scripting the db. This is fair as this can be kinda fiddly at the best of time. Although thats not going to be made easier by the system table corruption.

Any luck with the vendor?
0
 
LVL 16

Assisted Solution

by:EvilPostIt
EvilPostIt earned 500 total points
Comment Utility
Been reading a few more article regards the corruption of the sysobjvalues table and as i thought there is no way to fix this. So the only option is to get a shell of the database schema and copy whatever data you can across.

With regards to the CentralBin database the transaction log seems to be corrupt, can you backup this database so that we can try the repair statement. Also do DBCC PAGE('CentralBin_79A5B99C-C5EC-4ADB-AA95-6589884D04B6',1,597,0) to find which object is corrupted.
0
 

Author Closing Comment

by:BizTekConnection
Comment Utility
Ok, going to close this one as I suspect the CentralBin DB is related to the other one.  In any case, I will contact support for this product once my client gets back under a support contract with them.  Thanks for all the thoughts and suggestions.
0
 
LVL 16

Expert Comment

by:EvilPostIt
Comment Utility
Hi,

Just a quick follow up but I dropped Paul Randal a note regarding your database corruption and he has said the same as me. Ie that you will have to just copy what data you can out of the database as there is no way to recover this.

Thanks
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

Recently, when I was asked to create a new SQL 2005 cluster, Microsoft released a new service pack for MS SQL 2005 what is Service Pack 3. When I finished the installation of MS SQL 2005 I found myself troubled why the installation of SP3 failed …
When writing XML code a very difficult part is when we like to remove all the elements or attributes from the XML that have no data. I would like to share a set of recursive MSSQL stored procedures that I have made to remove those elements from …
This demo shows you how to set up the containerized NetScaler CPX with NetScaler Management and Analytics System in a non-routable Mesos/Marathon environment for use with Micro-Services applications.
This video shows how to remove a single email address from the Outlook 2010 Auto Suggestion memory. NOTE: For Outlook 2016 and 2013 perform the exact same steps. Open a new email: Click the New email button in Outlook. Start typing the address: …

772 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

9 Experts available now in Live!

Get 1:1 Help Now