Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

SQL Server Stack Dump Expand / Collapse
Author
Message
Posted Wednesday, June 30, 2010 4:20 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Tuesday, September 16, 2014 8:43 AM
Points: 1,797, Visits: 485
We had the below stack dump this morning on our SQL Server 2005 Cluster. I have tried investigating the exception address and exception code with no luck.

Any help would be much appreciated.

Bios Version is DELL - 1
Phoenix ROM BIOS PLUS Version 1.10 A03
Current time is 06:38:44 06/30/10.
8 Intel x86 level 15, 2992 Mhz processor (s).
Windows NT 5.2 Build 3790 CSD Service Pack 2.

Memory
MemoryLoad = 92%
Total Physical = 16379 MB
Available Physical = 1188 MB
Total Page File = 38318 MB
Available Page File = 23695 MB
Total Virtual = 2047 MB
Available Virtual = 221 MB
***Stack Dump being sent to D:\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0187.txt
SqlDumpExceptionHandler: Process 17 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is
terminating this process.
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 06/30/10 06:38:44 spid 17
*
*
* Exception Address = 01FDEB09 Module(sqlservr+00FDEB09)
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred writing address 00000018
*
*
* MODULE BASE END SIZE
* sqlservr 01000000 02C22FFF 01c23000
* ntdll 7C800000 7C8BFFFF 000c0000
* kernel32 77E40000 77F41FFF 00102000
* MSVCR80 78130000 781CAFFF 0009b000
* msvcrt 77BA0000 77BF9FFF 0005a000
* MSVCP80 7C420000 7C4A6FFF 00087000
* ADVAPI32 77F50000 77FEAFFF 0009b000
* RPCRT4 77C50000 77CEEFFF 0009f000
* Secur32 76F50000 76F62FFF 00013000
* sqlos 344D0000 344D4FFF 00005000
* USERENV 76920000 769E1FFF 000c2000
* USER32 77380000 77410FFF 00091000
* GDI32 77C00000 77C48FFF 00049000
* WINMM 76AA0000 76ACCFFF 0002d000
* opends60 333E0000 333E6FFF 00007000
* NETAPI32 71C40000 71C96FFF 00057000
* IMM32 76290000 762ACFFF 0001d000
* psapi 76B70000 76B7AFFF 0000b000
* instapi 48060000 48069FFF 0000a000
* CLUSAPI 74DE0000 74DF1FFF 00012000
* ole32 77670000 777A8FFF 00139000
* OLEAUT32 77D00000 77D8AFFF 0008b000
* RESUTILS 74EF0000 74F02FFF 00013000
* sqlevn70 4F610000 4F7B8FFF 001a9000
* NTMARTA 77E00000 77E20FFF 00021000
* WLDAP32 76F10000 76F3DFFF 0002e000
* SAMLIB 7E020000 7E02EFFF 0000f000
* rsaenh 68000000 68034FFF 00035000
* AUTHZ 76C40000 76C53FFF 00014000
* MSCOREE 79000000 79045FFF 00046000
* msv1_0 76C90000 76CB6FFF 00027000
* WS2_32 71C00000 71C16FFF 00017000
* WS2HELP 71BF0000 71BF7FFF 00008000
* iphlpapi 76CF0000 76D09FFF 0001a000
* kerberos 71CA0000 71CF7FFF 00058000
* cryptdll 766E0000 766EBFFF 0000c000
* MSASN1 76190000 761A1FFF 00012000
* schannel 76750000 76776FFF 00027000
* CRYPT32 761B0000 76242FFF 00093000
* COMRES 77010000 770D5FFF 000c6000
* XOLEHLP 57B10000 57B15FFF 00006000
* MSDTCPRX 61150000 611C8FFF 00079000
* msvcp60 57790000 577F4FFF 00065000
* MTXCLU 74F40000 74F58FFF 00019000
* VERSION 77B90000 77B97FFF 00008000
* WSOCK32 71BB0000 71BB8FFF 00009000
* mswsock 71B20000 71B60FFF 00041000
* DNSAPI 76ED0000 76EF9FFF 0002a000
* winrnr 76F70000 76F76FFF 00007000
* rasadhlp 76F80000 76F84FFF 00005000
* hnetcfg 5F270000 5F2C9FFF 0005a000
* wshtcpip 71AE0000 71AE7FFF 00008000
* security 71F60000 71F63FFF 00004000
* msfte 58540000 58799FFF 0025a000
* dbghelp 587B0000 588C4FFF 00115000
* WINTRUST 76BB0000 76BDAFFF 0002b000
* imagehlp 76C10000 76C37FFF 00028000
* dssenh 68100000 68126FFF 00027000
* ntdsapi 766F0000 76703FFF 00014000
* xpsp2res 58D40000 59004FFF 002c5000
* CLBCatQ 777B0000 77832FFF 00083000
* sqlncli 59010000 59236FFF 00227000
* COMCTL32 77530000 775C6FFF 00097000
* comdlg32 762B0000 762F8FFF 00049000
* SHLWAPI 77DA0000 77DF1FFF 00052000
* SHELL32 7C8D0000 7D0CEFFF 007ff000
* comctl32 77420000 77522FFF 00103000
* SQLNCLIR 592C0000 592F2FFF 00033000
* msftepxy 59310000 59324FFF 00015000
* xpstar90 5C470000 5C4BAFFF 0004b000
* SQLSCM90 5C4E0000 5C4E8FFF 00009000
* ODBC32 5C500000 5C53CFFF 0003d000
* BatchParser90 5C540000 5C55EFFF 0001f000
* ATL80 7C630000 7C64AFFF 0001b000
* odbcint 5C850000 5C866FFF 00017000
* xpstar90 5C870000 5C895FFF 00026000
* msxmlsql 78800000 788D4FFF 000d5000
* msxml2 5FD80000 5FE2EFFF 000af000
* msxml3 72E50000 72F66FFF 00117000
* xpsqlbot 5DD60000 5DD65FFF 00006000
* xplog70 5DD80000 5DD8BFFF 0000c000
* xplog70 5DDA0000 5DDA2FFF 00003000
* odsole70 00890000 0089EFFF 0000f000
* SXS 75DA0000 75E5CFFF 000bd000
* WININET 623A0000 6246FFFF 000d0000
* Normaliz 5C130000 5C138FFF 00009000
* iertutil 62470000 624B4FFF 00045000
* mlang 74540000 745D2FFF 00093000
* urlmon 625C0000 626E6FFF 00127000
* RASAPI32 76E90000 76ECEFFF 0003f000
* rasman 76E40000 76E51FFF 00012000
* TAPI32 76E60000 76E8EFFF 0002f000
* rtutils 76E30000 76E3BFFF 0000c000
* sensapi 722F0000 722F4FFF 00005000
* xp_sqlbackup 5F200000 5F24DFFF 0004e000
* sqlvdi 61CD0000 61CF1FFF 00022000
* sqlmap90 33320000 3333DFFF 0001e000
* MAPI32 62200000 6221EFFF 0001f000
* sqlmap90 58BF0000 58BF5FFF 00006000
* scrrun 736F0000 73714FFF 00025000
* MFC42 73EB0000 73FD0FFF 00121000
* sqlevn70 678D0000 67AD4FFF 00205000
* sqlevn70 67AE0000 67CE2FFF 00203000
* sqlevn70 67CF0000 67E98FFF 001a9000
* sqlevn70 68130000 6831BFFF 001ec000
* sqlevn70 68320000 68518FFF 001f9000
* sqlevn70 68520000 68700FFF 001e1000
* sqlevn70 68710000 688B8FFF 001a9000
* sqlevn70 688C0000 68A68FFF 001a9000
* sqlevn70 68A70000 68C18FFF 001a9000
* xprepl 5A660000 5A671FFF 00012000
* mscorwks 737A0000 73D2EFFF 0058f000
* dbghelp 639B0000 63AC4FFF 00115000
*
* Edi: 00000000:
* Esi: 00000000:
* Eax: 00000000:
* Ebx: 0BD3C398: 0BD3A040 09ACD709 000011B0 000011AF 000011C1 000011B4
* Ecx: 00000002:
* Edx: 0BD3A9D8: 290550A8 503984F0 000024C0 23BBD170 432565B8 00000000
* Eip: 01FDEB09: FF184083 D2334C75 8320488D 42750039 00047983 C2833C75
* Ebp: 5AF0EE2C: 5AF0EE68 01FDE899 0BD3C398 00000000 5AF099CD 00000001
* SegCs: 0000001B:
* EFlags: 00010246: 00760041 006E004F 006F0043 0052006D 006C0065 00610065
* Esp: 5AF0EE2C: 5AF0EE68 01FDE899 0BD3C398 00000000 5AF099CD 00000001
* SegSs: 00000023:
* *******************************************************************************
* -------------------------------------------------------------------------------
* Short Stack Dump
01FDEB09 Module(sqlservr+00FDEB09)
01FDE899 Module(sqlservr+00FDE899)
01FDE900 Module(sqlservr+00FDE900)
01FDF65D Module(sqlservr+00FDF65D)
01FDCBB3 Module(sqlservr+00FDCBB3)
01FDCE72 Module(sqlservr+00FDCE72)
0104331C Module(sqlservr+0004331C)
01028B48 Module(sqlservr+00028B48)
0102C5CE Module(sqlservr+0002C5CE)
0102A389 Module(sqlservr+0002A389)
0102713A Module(sqlservr+0002713A)
010276FB Module(sqlservr+000276FB)
01024DE6 Module(sqlservr+00024DE6)
0156E41F Module(sqlservr+0056E41F)
0108368B Module(sqlservr+0008368B)
010837D4 Module(sqlservr+000837D4)
010834D8 Module(sqlservr+000834D8)
01083326 Module(sqlservr+00083326)
01083628 Module(sqlservr+00083628)
01006684 Module(sqlservr+00006684)
010067AA Module(sqlservr+000067AA)
010064BA Module(sqlservr+000064BA)
0145E8D4 Module(sqlservr+0045E8D4)
0145F88C Module(sqlservr+0045F88C)
0145F33C Module(sqlservr+0045F33C)
0145F4D9 Module(sqlservr+0045F4D9)
781329BB Module(MSVCR80+000029BB)
78132A47 Module(MSVCR80+00002A47)

PSS @0x4A80C7D8
---------------



CSession @0x4A80C168
--------------------
m_spid = 17 m_cRef = 5 m_rgcRefType[0] = 1
m_rgcRefType[1] = 0 m_rgcRefType[2] = 2 m_rgcRefType[3] = 1
m_rgcRefType[4] = 0 m_rgcRefType[5] = 1 m_pmo = 0x4A80C040
m_pstackBhfPool = 0x00000000 m_dwLoginFlags = 0x0000 m_fBackground = -1
m_fClientRequestConnReset = 0 m_fUserProc = 0 m_fConnReset = 0
m_fIsConnReset = 0 m_fInLogin = 0 m_fAuditLoginSent = 0
m_fAuditLoginFailedSent = 0 m_fReplRelease = 0 m_fKill = 0
m_ulLoginStamp = 432804957 m_eclClient = 5 m_protType = 0
m_hHttpToken = FFFFFFFF

m_pV7LoginRec
---------------------
00000000: 00000000 00000000 00000000 00000000 00000000 †....................

00000014: 00000000 00000000 00000000 00000000 00000000 †....................

00000028: 00000000 00000000 00000000 00000000 00000000 †....................

0000003C: 00000000 00000000 00000000 00000000 00000000 †....................

00000050: 00000000 00000000 00000000 0000†††††††††††††††..............



CBatch @0x4A80CCE0
------------------
m_pSess = 0x4A80C168 m_pConn = 0x4A80C738 m_cRef = 2
m_rgcRefType[0] = 1 m_rgcRefType[1] = 1 m_rgcRefType[2] = 0
m_rgcRefType[3] = 0 m_rgcRefType[4] = 0 m_pTask = 0x00A587A8


EXCEPT (null) @0x5AF0D29C
-------------------------
exc_number = 0 exc_severity = 0 exc_func = 0x02426A80



Task @0x00A587A8
----------------
CPU Ticks used (ms) = 141 Task State = 2
WAITINFO_INTERNAL: WaitResource = 0x00000000 WAITINFO_INTERNAL: WaitType = 0x0
WAITINFO_INTERNAL: WaitSpinlock = 0x00000000 SchedulerId = 0x1
ThreadId = 0x24c0 m_state = 0 m_eAbortSev = 0



EC @0x4A80C7E0
--------------
spid = 17 ecid = 0 ec_stat = 0x0
ec_stat2 = 0x0 ec_atomic = 0x0 __fSubProc = 1
ec_dbccContext = 0x00000000 __pSETLS = 0x4A80C778 __pSEParams = 0x5AF0FC40
__pDbLocks = 0x00000000

SEInternalTLS @0x4A80C778
-------------------------
m_flags = 0 m_TLSstatus = 3 m_owningTask = 0x00A587A8
m_activeHeapDatasetList = 0x4A80C778 m_activeIndexDatasetList = 0x4A80C780


SEParams @0x5AF0FC40
--------------------
m_lockTimeout = -1 m_isoLevel = 4096 m_logDontReplicate = 1
m_neverReplicate = 1 m_XactWorkspace = 0x3EAFDA80 m_pSessionLocks = 0x5AF0FB50
m_pDbLocks = 0x5AF0FCD0 m_execStats = 0x32BB7B28 m_pAllocFileLimit = 0x00000000




------------------------
I am the master of my fate:
I am the captain of my soul.
------------------------
Blog: http://sqlserver365.blogspot.co.uk/
Twitter: @ckwmcgowan
------------------------

Post #945338
Posted Wednesday, June 30, 2010 7:27 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 6:23 AM
Points: 43,042, Visits: 36,201
Call Microsoft's customer support and open a case. There are very few people that can debug a stack dump effectively and most work for MS.

Just make sure that you have the latest patch level first.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #945464
Posted Wednesday, June 30, 2010 7:38 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Tuesday, September 16, 2014 8:43 AM
Points: 1,797, Visits: 485
Thanks GilaMonster, I'm on the case I will post any updates.

------------------------
I am the master of my fate:
I am the captain of my soul.
------------------------
Blog: http://sqlserver365.blogspot.co.uk/
Twitter: @ckwmcgowan
------------------------

Post #945473
Posted Friday, September 30, 2011 3:40 PM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Yesterday @ 10:38 PM
Points: 3,931, Visits: 7,160
Did you ever find a resolution to this? Since 3:23pm today we're suddenly getting log dumps every 1 minute and it's incredibly confusing perusing through these dump files.

The gist of it looks like this...and appear to have something to do with our transactional replication i.e. (s p _ M S u p d...)

Also, I keep getting these alerts
DESCRIPTION: Replication-Replication Distribution Subsystem: agent NAS2-MSSQL1-COREISSUE-CI_PUB_TABLES-NAS2-DBR-12 failed. Unspecified error

Current time is 15:20:30 09/30/11.                                                                               
=====================================================================
BugCheck Dump
=====================================================================

This file is generated by Microsoft SQL Server
version 10.0.4064.0
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.


Computer type is Intel(R) Xeon(R) CPU E5620 @ 2.40GHz.
8 X64 level 8664, 2394 Mhz processor (s).
Windows NT 5.2 Build 3790 CSD Service Pack 2.

Memory
MemoryLoad = 86%
Total Physical = 16370 MB
Available Physical = 2215 MB
Total Page File = 32264 MB
Available Page File = 17979 MB
Total Virtual = 8388607 MB
Available Virtual = 8364396 MB
**Dump thread - spid = 0, EC = 0x00000000AC5820F0
*
* User initiated stack dump. This is not a server exception dump.
*
***Stack Dump being sent to D:\SQL\LOG\SQLDump0004.txt
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 09/30/11 15:20:30 spid 168
*
* ex_raise2: Exception raised, major=52, minor=42, state=9, severity=22
*
* Input Buffer 255 bytes -
* ¨ 16 00 00 00 12 00 00 00 02 00 0b 19 00 00 a8 00 00 00
* $ [ d b o ] . 01 00 00 00 24 00 5b 00 64 00 62 00 6f 00 5d 00 2e 00
* [ s p _ M S u p d 5b 00 73 00 70 00 5f 00 4d 00 53 00 75 00 70 00 64 00
* _ d b o A l l A u 5f 00 64 00 62 00 6f 00 41 00 6c 00 6c 00 41 00 75 00
* t h s A c c o u n 74 00 68 00 73 00 41 00 63 00 63 00 6f 00 75 00 6e 00
* t s ] 74 00 73 00 5d 00 00 00 00 02 1f 00 02 1f 00 02 1f 00
* o nŸ ètü 02 1f 00 00 6f 08 08 6e 9f 00 00 e8 74 fc 00 00 02 1f
* 00 02 1f 00 02 1f 00 02 1f 00 02 1f 00 02 1f 00 02 1f
* 00 02 1f 00 02 1f 00 02 1f 00 02 1f 00 02 1f 00 02 1f
* 00 02 1f 00 02 1f 00 02 1f 00 02 1f 00 02 1f 00 02 1f
* 00 02 1f 00 02 1f 00 02 1f 00 02 1f 00 02 1f 00 02 1f
* 00 02 1f 00 02 1f 00 02 1f 00 02 1f 00 02 1f 00 02 1f
* 00 02 1f 00 02 1f 00 02 1f 00 02 1f 00 02 1f 00 02 1f
* 00 02 1f 00 02 1f 00 02 1f 00 02 1f 00 02 1f 00 02 1f
* 00 02 1f 00 02 1f 00 02 1f 00 02 1f 00 02 1f 00 02 1f
* & ß_] 00 02 1f 00 02 1f 00 02 1f 00 00 26 04 04 df 5f 5d 00
* 00 02 1f 00 02 1f 00 02 1f 00 02 1f 00 02 1f 00 02 1f
* 00 02 1f 00 02 1f 00 02 1f 00 02 1f 00 02 1f 00 02 1f
* & ¥ 00 00 26 04 04 01 00 00 00 00 00 a5 09 00 09 00 10 00
* ÿ$ [ d b o 00 00 00 00 00 02 00 ff 24 00 5b 00 64 00 62 00 6f 00
* ] . [ s p _ M S u 5d 00 2e 00 5b 00 73 00 70 00 5f 00 4d 00 53 00 75 00
* p d _ d b o A l l 70 00 64 00 5f 00 64 00 62 00 6f 00 41 00 6c 00 6c 00
* A u t h s A c c o 41 00 75 00 74 00 68 00 73 00 41 00 63 00 63 00 6f 00
* u n t s ] 75 00 6e 00 74 00 73 00 5d 00 00 00 00 02 1f 00 02 1f

We have our End of Day and Month End processing occuring tonight at midnight (which generally runs for several hours into the morning) and then Corporate Reporting will "attempt" to start sending out 40,000+ reports from the data replicated into these tables...

I'm a tad freaked. Did you find a solution?


______________________________________________________________________________
"Never argue with an idiot; They'll drag you down to their level and beat you with experience"
Post #1183966
Posted Friday, September 30, 2011 3:51 PM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 6:23 AM
Points: 43,042, Visits: 36,201
In general, for any form of stack dump, call Microsoft Customer Support and open a case.

This however looks like database corruption. Error 5242 is:
An inconsistency was detected during an internal operation in database '%.*ls'(ID:%d) on page %S_PGID. Please contact technical support.


Please run the following and post the full and complete results.

DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS




Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1183969
Posted Friday, September 30, 2011 4:01 PM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Yesterday @ 10:38 PM
Points: 3,931, Visits: 7,160
Thanks for the quick response Gail. I am running the CHECKDB and will attach the results (currently at 7.9% and climbing S-L-O-W-L-Y...)

Question to throw your way though...since this database is just a replicated DB from our production environment...couldn't I just drop the DB and recreate all the publications/subscriptions and be done with it? I mean it the DB is corrupted, won't that overwrite it all?



______________________________________________________________________________
"Never argue with an idiot; They'll drag you down to their level and beat you with experience"
Post #1183970
Posted Friday, September 30, 2011 4:04 PM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 6:23 AM
Points: 43,042, Visits: 36,201
If it is corrupt, it's an option.


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1183971
Posted Friday, September 30, 2011 4:18 PM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Yesterday @ 10:38 PM
Points: 3,931, Visits: 7,160
On second thought...attempting to redo replication like that (dropping the DB, then recreating the subscriptions, etc) gives you an error that you can't drop a database when it's being used for replication...

Do you know if there's a way to get around it? Without having to redo EVERYTHING?


______________________________________________________________________________
"Never argue with an idiot; They'll drag you down to their level and beat you with experience"
Post #1183977
Posted Friday, September 30, 2011 4:24 PM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 6:23 AM
Points: 43,042, Visits: 36,201
MyDoggieJessie (9/30/2011)
Do you know if there's a way to get around it? Without having to redo EVERYTHING?


Without the checkDB output, no.

You can drop a database involved in replication as long as the subscription is dropped first.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1183979
Posted Friday, September 30, 2011 5:23 PM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Yesterday @ 10:38 PM
Points: 3,931, Visits: 7,160
Attached is the output from the CHECHDB...doesn't look too good at a first glance...

______________________________________________________________________________
"Never argue with an idiot; They'll drag you down to their level and beat you with experience"


  Post Attachments 
DB_CheckDB.zip (3 views, 719 bytes)
Post #1183986
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse