605 Severity 21 Errors

Aug 10, 2005

We are seeing random 605 Severity 21 Errors. We applied SP4 over the weekend, but sure enough Monday night we received another one.

We repaired the DB and don't have a copy of it when it was correct, so I can't send my DBCC results. I do have this from the Errorlog though. It occurred during our database load process.

2005-08-08 19:39:25.95 spid77 Getpage: bstat=0x9, sstat=0, cache
2005-08-08 19:39:25.95 spid77 pageno is/should be:objid is/should be:
2005-08-08 19:39:25.95 spid77 (1:1787)/(1:1787)610101214/1266103551
2005-08-08 19:39:25.95 spid77 ... IAM indicates that page is allocated to this object
2005-08-08 19:39:25.97 spid77 Getpage: bstat=0x9, sstat=0, cache
2005-08-08 19:39:25.97 spid77 pageno is/should be:objid is/should be:
2005-08-08 19:39:25.97 spid77 (1:1787)/(1:1787)610101214/1266103551
2005-08-08 19:39:25.97 spid77 ... IAM indicates that page is allocated to this object
2005-08-08 19:39:25.97 spid77 Getpage: bstat=0x9, sstat=0, cache
2005-08-08 19:39:25.97 spid77 pageno is/should be:objid is/should be:
2005-08-08 19:39:25.97 spid77 (1:1787)/(1:1787)610101214/1266103551
2005-08-08 19:39:25.97 spid77 ... IAM indicates that page is allocated to this object
2005-08-08 19:39:25.97 spid77 Error: 605, Severity: 21, State: 1
2005-08-08 19:39:25.97 spid77 Attempt to fetch logical page (1:1787) in database 'db1' belongs to object 'IEFPROD_FACA_GEO_LOC', not to object 'FacilityInterest'..

View 7 Replies

Severity Errors 19-25

Sep 6, 2000

I have the following severity errors 19-25. I am a new using to SQL Server 7.0 and would like some advice in dealing with these errors. I am going to run the DBCC CHECKDB to determine what the errors are. Is this the right approach. Thanks!!!

View 1 Replies View Related

Alert To Severity 24 Errors.

Mar 6, 2000

I'm getting an intermittent alert on SQL 7.0. This alert is firing on a severity 24 hardware error.
This has now happened twice and both times I have looked at both the SQL error logs and the
SQL Server event viewer. There are no references to the severity 24 errors in either the SQL error logs or
the event viewer. What could cause this alert and why isn't it being logged properly?

Randy

View 1 Replies View Related

Handle SQL Errors With Severity 10

Jul 23, 2005

how to handle sql errors with severity less then 10 in .NETi call to stored procedure which raise error with severity 10 for examplehowever in c# i can't cach this error (with severiry >= 11 it going to thecatch block in my c# app), also the @@ERROR is equal to zero when severity<= 10--Message posted via http://www.sqlmonster.com

View 2 Replies View Related

Why Is Severity 20 Assigned To SSPI Errors

Aug 28, 2007

At our site, we page DBAs whenever an alert with a severity of 20 or greater is raised. This never was an issue until SQL Server 2005. Now every SSPI error is paged since it is a severity 20. I don't believe the errors are severe enough to qualify an assignment of 20. Anybody else have any thoughts on this?

Thanks.

View 4 Replies View Related

SQL Server 2008 :: How To Make Sproc Return Errors For Underlying Table Errors

Jul 1, 2015

I recently updated the datatype of a sproc parameter from bit to tinyint. When I executed the sproc with the updated parameters the sproc appeared to succeed and returned "1 row(s) affected" in the console. However, the update triggered by the sproc did not actually work.

The table column was a bit which only allows 0 or 1 and the sproc was passing a value of 2 so the table was rejecting this value. However, the sproc did not return an error and appeared to return success. So is there a way to configure the database or sproc to return an error message when this type of error occurs?

View 1 Replies View Related

Parent Package Reports Failure On Errors, But No Errors In Log

Jul 31, 2006

I have a parent package that calls child packages inside a For Each container. When I debug/run the parent package (from VS), I get the following error message: Warning: The Execution method succeeded, but the number of errors raised (3) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.

It appears to be failing while executing the child package. However, the logs (via the "progress" tab) for both the parent package and the child package show no errors other than the one listed above (and that shows in the parent package log). The child package appears to validate completely without error (all components are green and no error messages in the log). I turned on SSIS logging to a text file and see nothing in there either.

If I bump up the MaximumErrorCount in the parent package and in the Execute Package Task that calls the child package to 4 (to go one above the error count indicated in the message above), the whole thing executes sucessfully. I don't want to leave the Max Error Count set like this. Is there something I am missing? For example are there errors that do not get logged by default? I get some warnings, do a certain number of warnings equal an error?

Thanks,

Lee

View 5 Replies View Related

How To Solve 0 Allocation Errors And 1 Consistency Errors In

Apr 20, 2006

Starwin writes "when i execute DBCC CHECKDB, DBCC CHECKCATALOG
I reveived the following error.
how to solve it?

Server: Msg 8909, Level 16, State 1, Line 1 Table error: Object ID -2093955965, index ID 711, page ID (3:2530). The PageId in the page header = (34443:343146507).
. . . .
. . . .

CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID -1635188736)' (object ID -1635188736).
CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID -1600811521)' (object ID -1600811521).

. . . .
. . . .

Server: Msg 8909, Level 16, State 1, Line 1 Table error: Object ID -8748568, index ID 50307, page ID (3:2497). The PageId in the page header = (26707:762626875).
Server: Msg 8909, Level 16, State 1, Line 1 Table error: Object ID -7615284, index ID 35836, page ID (3:2534). The PageId in the page heade"

View 1 Replies View Related

Severity 18 Error

May 11, 2000

We have sites that connect to a database server and we received the following error for several hours on our network monitoring software:

Thu May 11 06:36:15 2000 [DB/MSSQLServer] Error ODS Error: 17802, Severity: 18, State: 3 2000-05-11 06:36:15.67 ods Could not create server event thread.

I could connect to the server but could not get into SQL Enterprise Mgr or through Query Analyzer. I would get a network connection error. I had checked the client config utility and it was correct. Eventually the network guys rebooted the server and the problem went away. This is a MAJOR production server and I was wondering if anyone had seen this error before. Could someone be running a robot to tie up SQL? Any input would be appreciated.

Alan

View 2 Replies View Related

Error: 605, Severity: 21

Jul 26, 2007

In my ERRORLOG file I have this error come up able every 10 minutes:

2007-07-26 08:16:31.93 spid65 Getpage: bstat=0x9, sstat=0x10000, cache
2007-07-26 08:16:31.93 spid65 pageno is/should be:objid is/should be:
2007-07-26 08:16:31.93 spid65 (1:3435)/(1:3435)1573580644/18099105
2007-07-26 08:16:31.93 spid65 ... IAM indicates that page is NOT allocated to this object
2007-07-26 08:16:31.93 spid65 Error: 605, Severity: 21, State: 1
2007-07-26 08:16:31.93 spid65 Attempt to fetch logical page (1:3435) in database 'PDP' belongs to object 'EMP_SHIFT_DETAIL', not to object 'TRACKED_ITEMS'..

Here is the output of DBCC CHECKDB
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 852426752 owned by data record identified by RID = (1:110:19) id = 1925581898 and indid = 2.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:438), slot 3, text ID 852426752 is referenced by page (1:71), slot 4, but was not seen in the scan.
DBCC results for 'PDP'.
DBCC results for 'sysobjects'.
There are 652 rows in 11 pages for object 'sysobjects'.
DBCC results for 'sysindexes'.
There are 480 rows in 18 pages for object 'sysindexes'.
CHECKDB found 0 allocation errors and 2 consistency errors in table 'sysindexes' (object ID 2).
DBCC results for 'syscolumns'.
There are 3692 rows in 62 pages for object 'syscolumns'.
DBCC results for 'systypes'.
There are 26 rows in 1 pages for object 'systypes'.
DBCC results for 'syscomments'.
There are 381 rows in 120 pages for object 'syscomments'.
DBCC results for 'sysfiles1'.
There are 2 rows in 1 pages for object 'sysfiles1'.
DBCC results for 'syspermissions'.
There are 18 rows in 1 pages for object 'syspermissions'.
DBCC results for 'sysusers'.
There are 12 rows in 1 pages for object 'sysusers'.
DBCC results for 'sysproperties'.
There are 0 rows in 0 pages for object 'sysproperties'.
DBCC results for 'sysdepends'.
There are 1650 rows in 8 pages for object 'sysdepends'.
DBCC results for 'sysreferences'.
There are 0 rows in 0 pages for object 'sysreferences'.
DBCC results for 'sysfulltextcatalogs'.
There are 0 rows in 0 pages for object 'sysfulltextcatalogs'.
DBCC results for 'sysfulltextnotify'.
There are 0 rows in 0 pages for object 'sysfulltextnotify'.
Server: Msg 8951, Level 16, State 1, Line 1
Table error: Table 'TRACKED_ITEM_TOTAL_READING' (ID 2099048). Missing or invalid key in index 'TRACKED_ITEM_TTL_READNG_INDEX' (ID 2) for the row:
Server: Msg 8955, Level 16, State 1, Line 1
Data row (1:3280:54) identified by (RID = (1:3280:54) ) has index values (SITE_ID = '180180' and BUSINESS_DATE = 20070717 and BEGIN_TIME = 133000).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:0) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 191500) points to the data row identified by (RID = (1:3285:83)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:1) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 191500) points to the data row identified by (RID = (1:3285:84)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:2) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 191500) points to the data row identified by (RID = (1:3286:8)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:3) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 191500) points to the data row identified by (RID = (1:3286:9)).
DBCC results for 'sysfilegroups'.
There are 1 rows in 1 pages for object 'sysfilegroups'.
DBCC results for 'TRACKED_ITEM_TOTAL_READING'.
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:4) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 191500) points to the data row identified by (RID = (1:3286:27)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:6) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 193000) points to the data row identified by (RID = (1:3285:85)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:7) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 193000) points to the data row identified by (RID = (1:3285:86)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:8) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 193000) points to the data row identified by (RID = (1:3286:10)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:9) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 193000) points to the data row identified by (RID = (1:3286:11)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:10) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 193000) points to the data row identified by (RID = (1:3286:28)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:12) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 194500) points to the data row identified by (RID = (1:3285:87)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:13) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 194500) points to the data row identified by (RID = (1:3285:88)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:14) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 194500) points to the data row identified by (RID = (1:3286:12)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:15) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 194500) points to the data row identified by (RID = (1:3286:13)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:16) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 194500) points to the data row identified by (RID = (1:3286:29)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:17) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 194500) points to the data row identified by (RID = (1:3286:30)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:19) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 200000) points to the data row identified by (RID = (1:3285:89)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:20) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 200000) points to the data row identified by (RID = (1:3285:90)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:21) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 200000) points to the data row identified by (RID = (1:3286:14)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:22) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 200000) points to the data row identified by (RID = (1:3286:15)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:24) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 201500) points to the data row identified by (RID = (1:3285:91)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:25) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 201500) points to the data row identified by (RID = (1:3286:16)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:27) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 203000) points to the data row identified by (RID = (1:3285:92)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:28) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 203000) points to the data row identified by (RID = (1:3286:17)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:29) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 203000) points to the data row identified by (RID = (1:3286:31)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:30) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 203000) points to the data row identified by (RID = (1:3286:47)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:32) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 204500) points to the data row identified by (RID = (1:3286:32)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:33) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 204500) points to the data row identified by (RID = (1:3286:33)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:34) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 204500) points to the data row identified by (RID = (1:3286:48)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:35) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 204500) points to the data row identified by (RID = (1:3286:49)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:37) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 210000) points to the data row identified by (RID = (1:3286:34)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:38) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 210000) points to the data row identified by (RID = (1:3286:50)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:39) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 210000) points to the data row identified by (RID = (1:3286:51)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:41) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 211500) points to the data row identified by (RID = (1:3286:52)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:42) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 211500) points to the data row identified by (RID = (1:3286:53)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:44) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 213000) points to the data row identified by (RID = (1:3286:35)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:45) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 213000) points to the data row identified by (RID = (1:3286:36)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:46) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 213000) points to the data row identified by (RID = (1:3286:54)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:47) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 213000) points to the data row identified by (RID = (1:3286:55)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:49) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 214500) points to the data row identified by (RID = (1:3286:37)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:50) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 214500) points to the data row identified by (RID = (1:3286:38)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:52) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 220000) points to the data row identified by (RID = (1:3286:39)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:53) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 220000) points to the data row identified by (RID = (1:3286:40)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:55) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 221500) points to the data row identified by (RID = (1:3285:93)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:56) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 221500) points to the data row identified by (RID = (1:3285:94)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:57) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 221500) points to the data row identified by (RID = (1:3286:41)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:58) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 223000) points to the data row identified by (RID = (1:3285:95)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:59) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 223000) points to the data row identified by (RID = (1:3285:96)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:60) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 223000) points to the data row identified by (RID = (1:3286:56)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:61) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 223000) points to the data row identified by (RID = (1:3286:59)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:63) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 224500) points to the data row identified by (RID = (1:3286:42)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:64) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 224500) points to the data row identified by (RID = (1:3286:57)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:65) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 224500) points to the data row identified by (RID = (1:3286:61)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:67) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 230000) points to the data row identified by (RID = (1:3286:43)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:69) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 231500) points to the data row identified by (RID = (1:3286:44)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:70) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 231500) points to the data row identified by (RID = (1:3286:45)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:71) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 231500) points to the data row identified by (RID = (1:3286:60)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:73) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 233000) points to the data row identified by (RID = (1:3286:46)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3362:75) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070716 and BEGIN_TIME = 234500) points to the data row identified by (RID = (1:3286:58)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3364:40) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070717 and BEGIN_TIME = 130000) points to the data row identified by (RID = (1:3282:0)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3364:41) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070717 and BEGIN_TIME = 130000) points to the data row identified by (RID = (1:3282:1)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3364:47) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070717 and BEGIN_TIME = 131500) points to the data row identified by (RID = (1:3282:2)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3364:48) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070717 and BEGIN_TIME = 131500) points to the data row identified by (RID = (1:3282:3)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3364:52) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070717 and BEGIN_TIME = 133000) points to the data row identified by (RID = (1:3282:4)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3364:53) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070717 and BEGIN_TIME = 133000) points to the data row identified by (RID = (1:3282:5)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3364:55) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070717 and BEGIN_TIME = 133000) points to the data row identified by (RID = (1:3285:0)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3364:56) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070717 and BEGIN_TIME = 134500) points to the data row identified by (RID = (1:3280:54)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3364:57) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070717 and BEGIN_TIME = 134500) points to the data row identified by (RID = (1:3280:55)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3364:60) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070717 and BEGIN_TIME = 134500) points to the data row identified by (RID = (1:3282:6)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3364:61) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070717 and BEGIN_TIME = 134500) points to the data row identified by (RID = (1:3282:7)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3364:63) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070717 and BEGIN_TIME = 140000) points to the data row identified by (RID = (1:3280:56)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3364:64) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070717 and BEGIN_TIME = 140000) points to the data row identified by (RID = (1:3280:79)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3364:67) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070717 and BEGIN_TIME = 141500) points to the data row identified by (RID = (1:3280:80)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3364:68) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070717 and BEGIN_TIME = 141500) points to the data row identified by (RID = (1:3280:89)).
Server: Msg 8952, Level 16, State 1, Line 1
Table error: Database 'PDP', index 'TRACKED_ITEM_TOTAL_READING.TRACKED_ITEM_TTL_READNG_INDEX' (ID 2099048) (index ID 2). Extra or invalid key for the keys:
Server: Msg 8956, Level 16, State 1, Line 1
Index row (1:3364:71) with values (SITE_ID = '180180' and BUSINESS_DATE = 20070717 and BEGIN_TIME = 141500) points to the data row identified by (RID = (1:3282:8)).
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. Page (1:2669) is missing a reference from previous page (1:3126). Possible chain linkage problem.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. Page (1:2687) is missing a reference from previous page (1:3438). Possible chain linkage problem.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. Page (1:2842) is missing a reference from previous page (1:3439). Possible chain linkage problem.
Server: Msg 8981, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. The next pointer of (1:3124) refers to page (1:2844). Neither (1:2844) nor its parent were encountered. Possible bad chain linkage.
Server: Msg 8979, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. Page (1:2845) is missing references from parent (unknown) and previous (page (1:2843)) nodes. Possible bad root entry in sysindexes.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. Page (1:2912) is missing a reference from previous page (1:3437). Possible chain linkage problem.
Server: Msg 8979, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. Page (1:3054) is missing references from parent (unknown) and previous (page (1:2912)) nodes. Possible bad root entry in sysindexes.
There are 8402 rows in 87 pages for object 'TRACKED_ITEM_TOTAL_READING'.
CHECKDB found 0 allocation errors and 76 consistency errors in table 'TRACKED_ITEM_TOTAL_READING' (object ID 2099048).
DBCC results for 'CREDIT_LINE_ITEM'.
There are 0 rows in 0 pages for object 'CREDIT_LINE_ITEM'.
DBCC results for 'Stepped_Table_Header'.
There are 0 rows in 0 pages for object 'Stepped_Table_Header'.
DBCC results for 'TRACKED_ITEMS'.
Server: Msg 8979, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. Page (1:3121) is missing references from parent (unknown) and previous (page (1:2687)) nodes. Possible bad root entry in sysindexes.
Server: Msg 8979, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. Page (1:3123) is missing references from parent (unknown) and previous (page (1:3271)) nodes. Possible bad root entry in sysindexes.
Server: Msg 8936, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. B-tree chain linkage mismatch. (1:3054)->next = (1:3124), but (1:3124)->Prev = (1:2912).
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. Parent node for page (1:3124) was not encountered.
Server: Msg 8936, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. B-tree chain linkage mismatch. (1:3127)->next = (1:3125), but (1:3125)->Prev = (1:3148).
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. Parent node for page (1:3125) was not encountered.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. Page (1:3126) was not seen in the scan although its parent (1:3567) and previous (1:3125) refer to it. Check any previous errors.
Server: Msg 8979, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. Page (1:3127) is missing references from parent (unknown) and previous (page (1:3433)) nodes. Possible bad root entry in sysindexes.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. Page (1:3144) is missing a reference from previous page (1:3432). Possible chain linkage problem.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. Index node page (1:3567), slot 94 refers to child page (1:3148) and previous child (1:3433), but they were not encountered.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. Index node page (1:3567), slot 103 refers to child page (1:3150) and previous child (1:3434), but they were not encountered.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. Page (1:3151) is missing a reference from previous page (1:3664). Possible chain linkage problem.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. Page (1:3267) is missing a reference from previous page (1:3150). Possible chain linkage problem.
Server: Msg 8936, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. B-tree chain linkage mismatch. (1:3123)->next = (1:3485), but (1:3485)->Prev = (1:3271).
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. Parent node for page (1:3485) was not encountered.
Server: Msg 8979, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. Page (1:3486) is missing references from parent (unknown) and previous (page (1:3052)) nodes. Possible bad root entry in sysindexes.
Server: Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:3567), slot 79, in object ID 18099105, index ID 1, refers to page (1:3435), slot 0, in object ID 1573580644, index ID 2.
Server: Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:3567), slot 80, in object ID 18099105, index ID 1, refers to page (1:3439), slot 0, in object ID 1573580644, index ID 2.
Server: Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:3567), slot 83, in object ID 18099105, index ID 1, refers to page (1:3438), slot 0, in object ID 1573580644, index ID 2.
Server: Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:3567), slot 86, in object ID 18099105, index ID 1, refers to page (1:3436), slot 0, in object ID 1573580644, index ID 2.
Server: Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:3567), slot 91, in object ID 18099105, index ID 1, refers to page (1:3437), slot 0, in object ID 1573580644, index ID 2.
Server: Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:3567), slot 93, in object ID 18099105, index ID 1, refers to page (1:3433), slot 0, in object ID 1573580644, index ID 2.
Server: Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:3567), slot 99, in object ID 18099105, index ID 1, refers to page (1:3432), slot 0, in object ID 1573580644, index ID 2.
Server: Msg 8925, Level 16, State 1, Line 1
Table error: Cross object linkage: Page (1:3567), slot 102, in object ID 18099105, index ID 1, refers to page (1:3434), slot 0, in object ID 1573580644, index ID 2.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 18099105, index ID 1. Index node page (1:3567), slot 87 refers to child page (1:3664) and previous child (1:3436), but they were not encountered.
There are 23644 rows in 359 pages for object 'TRACKED_ITEMS'.
CHECKDB found 0 allocation errors and 32 consistency errors in table 'TRACKED_ITEMS' (object ID 18099105).
DBCC results for 'SAFE_CONFIG_DETAIL'.
There are 0 rows in 0 pages for object 'SAFE_CONFIG_DETAIL'.
DBCC results for 'Currency'.
There are 11 rows in 1 pages for object 'Currency'.
DBCC results for 'RECIPE_INGREDIENT_XML'.
There are 0 rows in 0 pages for object 'RECIPE_INGREDIENT_XML'.
DBCC results for 'LINE_ITEMS'.
There are 0 rows in 0 pages for object 'LINE_ITEMS'.
DBCC results for 'TMP_OVERSHORT'.
There are 0 rows in 0 pages for object 'TMP_OVERSHORT'.
DBCC results for 'SAFE_DETAILS'.
There are 0 rows in 0 pages for object 'SAFE_DETAILS'.
DBCC results for 'SchemaVersions'.
There are 1 rows in 1 pages for object 'SchemaVersions'.
DBCC results for 'TRANSFER'.
There are 0 rows in 0 pages for object 'TRANSFER'.
DBCC results for 'Stepped_Table_Step'.
There are 0 rows in 0 pages for object 'Stepped_Table_Step'.
DBCC results for 'SAFE_MANAGEMENT'.
There are 0 rows in 0 pages for object 'SAFE_MANAGEMENT'.
DBCC results for 'RECIPE_XML'.
There are 0 rows in 0 pages for object 'RECIPE_XML'.
DBCC results for 'RETURN_ITEM_DETAIL'.
There are 0 rows in 0 pages for object 'RETURN_ITEM_DETAIL'.
DBCC results for 'INI_CONFIGURATION'.
There are 0 rows in 0 pages for object 'INI_CONFIGURATION'.
DBCC results for 'RETURN_ITEM'.
There are 0 rows in 0 pages for object 'RETURN_ITEM'.
DBCC results for 'DEPOSIT_CONFIG'.
There are 0 rows in 0 pages for object 'DEPOSIT_CONFIG'.
DBCC results for 'INV_BATCH'.
There are 0 rows in 0 pages for object 'INV_BATCH'.
DBCC results for 'Scheduler_Settings'.
There are 0 rows in 0 pages for object 'Scheduler_Settings'.
DBCC results for 'DEPOSIT_CONFIG_DETAIL'.
There are 0 rows in 0 pages for object 'DEPOSIT_CONFIG_DETAIL'.
DBCC results for 'RM_RECON_CAL_MTD_XML'.
There are 0 rows in 0 pages for object 'RM_RECON_CAL_MTD_XML'.
DBCC results for 'WASTE_TEMPLATE'.
There are 0 rows in 0 pages for object 'WASTE_TEMPLATE'.
DBCC results for 'DEPOSIT_DETAILS'.
There are 0 rows in 0 pages for object 'DEPOSIT_DETAILS'.
DBCC results for 'WASTE_TEMPLATE_ITEM'.
There are 0 rows in 0 pages for object 'WASTE_TEMPLATE_ITEM'.
DBCC results for 'RM_UNIT_XML'.
There are 0 rows in 0 pages for object 'RM_UNIT_XML'.
DBCC results for 'PO_TEMPLATE'.
There are 0 rows in 0 pages for object 'PO_TEMPLATE'.
DBCC results for 'ACTION'.
There are 0 rows in 0 pages for object 'ACTION'.
DBCC results for 'AEIC_CODES'.
There are 5 rows in 1 pages for object 'AEIC_CODES'.
DBCC results for 'PO_TEMPLATE_DETAIL'.
There are 0 rows in 0 pages for object 'PO_TEMPLATE_DETAIL'.
DBCC results for 'DAILY_OVERTIME'.
There are 3 rows in 1 pages for object 'DAILY_OVERTIME'.
DBCC results for 'EMP_PUNCH'.
There are 0 rows in 0 pages for object 'EMP_PUNCH'.
DBCC results for 'SUBLOCATION_XML'.
There are 0 rows in 0 pages for object 'SUBLOCATION_XML'.
DBCC results for 'RM_TRAN_SUMMARY'.
There are 0 rows in 0 pages for object 'RM_TRAN_SUMMARY'.
DBCC results for 'Scheduler_Shifts'.
There are 0 rows in 0 pages for object 'Scheduler_Shifts'.
DBCC results for 'EMP_PUNCH_HISTORY'.
There are 0 rows in 0 pages for object 'EMP_PUNCH_HISTORY'.
DBCC results for 'EMPLOYEE_ACTION'.
There are 0 rows in 0 pages for object 'EMPLOYEE_ACTION'.
DBCC results for 'MIDEPT_TRAN_SUMMARY'.
There are 0 rows in 0 pages for object 'MIDEPT_TRAN_SUMMARY'.
DBCC results for 'EMPLOYEE_GROUP'.
There are 0 rows in 0 pages for object 'EMPLOYEE_GROUP'.
DBCC results for 'EMPLOYEE_HOUR'.
There are 0 rows in 0 pages for object 'EMPLOYEE_HOUR'.
DBCC results for 'VENDOR_RAWMAT_XML'.
There are 0 rows in 0 pages for object 'VENDOR_RAWMAT_XML'.
DBCC results for 'FIFO_BUCKET'.
There are 0 rows in 0 pages for object 'FIFO_BUCKET'.
DBCC results for 'EMPLOYEE_JOB_LABOR'.
There are 0 rows in 0 pages for object 'EMPLOYEE_JOB_LABOR'.
DBCC results for 'EMPLOYEE_LABOR'.
There are 0 rows in 0 pages for object 'EMPLOYEE_LABOR'.
DBCC results for 'INV_TRANSACTION'.
There are 158 rows in 2 pages for object 'INV_TRANSACTION'.
DBCC results for 'EMPLOYEE_TAX_DETAIL'.
There are 0 rows in 0 pages for object 'EMPLOYEE_TAX_DETAIL'.
DBCC results for 'ETHNIC_GROUP'.
There are 6 rows in 1 pages for object 'ETHNIC_GROUP'.
DBCC results for 'VENDOR_RM_DETAIL_XML'.
There are 0 rows in 0 pages for object 'VENDOR_RM_DETAIL_XML'.
DBCC results for 'INV_RECONCILIATION'.
There are 0 rows in 0 pages for object 'INV_RECONCILIATION'.
DBCC results for 'DCS_SUPPORT'.
There are 0 rows in 0 pages for object 'DCS_SUPPORT'.
DBCC results for 'JOB'.
There are 0 rows in 0 pages for object 'JOB'.
DBCC results for 'DCS_LABOR'.
There are 0 rows in 0 pages for object 'DCS_LABOR'.
DBCC results for 'LABOR'.
There are 0 rows in 0 pages for object 'LABOR'.
DBCC results for 'INV_THEO_USAGE'.
There are 0 rows in 0 pages for object 'INV_THEO_USAGE'.
DBCC results for 'LABOR_CONFIG'.
There are 11 rows in 1 pages for object 'LABOR_CONFIG'.
DBCC results for 'LABOR_DEPARTMENT'.
There are 0 rows in 0 pages for object 'LABOR_DEPARTMENT'.
DBCC results for 'VENDOR_XMl'.
There are 0 rows in 0 pages for object 'VENDOR_XMl'.
DBCC results for 'INV_WASTE_USAGE'.
There are 0 rows in 0 pages for object 'INV_WASTE_USAGE'.
DBCC results for 'LABOR_PERIOD'.
There are 0 rows in 0 pages for object 'LABOR_PERIOD'.
DBCC results for 'LABOR_REFERENCES'.
There are 5 rows in 1 pages for object 'LABOR_REFERENCES'.
DBCC results for 'INV_BUCKET_USAGE'.
There are 0 rows in 0 pages for object 'INV_BUCKET_USAGE'.
DBCC results for 'MARITAL_STATUS'.
There are 4 rows in 1 pages for object 'MARITAL_STATUS'.
DBCC results for 'OVERTIME_LAW'.
There are 17 rows in 1 pages for object 'OVERTIME_LAW'.
DBCC results for 'RANGE_ALERT'.
There are 0 rows in 0 pages for object 'RANGE_ALERT'.
DBCC results for 'PUNCH_EDIT_HISTORY'.
There are 0 rows in 0 pages for object 'PUNCH_EDIT_HISTORY'.
DBCC results for 'TMP_ONHAND'.
There are 0 rows in 0 pages for object 'TMP_ONHAND'.
DBCC results for 'PUNCH_EDIT_REASON'.
There are 0 rows in 0 pages for object 'PUNCH_EDIT_REASON'.
DBCC results for 'INV_DOCS'.
There are 0 rows in 0 pages for object 'INV_DOCS'.
DBCC results for 'SCHOOL'.
There are 0 rows in 0 pages for object 'SCHOOL'.
DBCC results for 'SCHOOL_TIMING'.
There are 0 rows in 0 pages for object 'SCHOOL_TIMING'.
DBCC results for 'COST_HISTORY'.
There are 0 rows in 0 pages for object 'COST_HISTORY'.
DBCC results for 'STATE'.
There are 1 rows in 1 pages for object 'STATE'.
DBCC results for 'W4_EXCEPTIONS'.
There are 4 rows in 1 pages for object 'W4_EXCEPTIONS'.
DBCC results for 'KEY_IDENTIFIER'.
There are 1 rows in 1 pages for object 'KEY_IDENTIFIER'.
DBCC results for 'TMP_WASTE'.
There are 0 rows in 0 pages for object 'TMP_WASTE'.
DBCC results for 'WAGE'.
There are 0 rows in 0 pages for object 'WAGE'.
DBCC results for 'WAGE_TYPE'.
There are 3 rows in 1 pages for object 'WAGE_TYPE'.
DBCC results for 'TMP_THEOUSAGE'.
There are 0 rows in 0 pages for object 'TMP_THEOUSAGE'.
DBCC results for 'WAITING_CALL'.
There are 0 rows in 0 pages for object 'WAITING_CALL'.
DBCC results for 'WEEKLY_OVERTIME'.
There are 3 rows in 1 pages for object 'WEEKLY_OVERTIME'.
DBCC results for 'TMP_EMP_TIPS'.
There are 0 rows in 0 pages for object 'TMP_EMP_TIPS'.
DBCC results for 'TMPGoodsReceived'.
There are 0 rows in 0 pages for object 'TMPGoodsReceived'.
DBCC results for 'TMP_OrderReceiptException'.
There are 0 rows in 0 pages for object 'TMP_OrderReceiptException'.
DBCC results for 'TMP_TheoCalc'.
There are 0 rows in 0 pages for object 'TMP_TheoCalc'.
DBCC results for 'RM_LOC_XML'.
There are 0 rows in 0 pages for object 'RM_LOC_XML'.
DBCC results for 'TMP_PurchaseOrderPoll'.
There are 0 rows in 0 pages for object 'TMP_PurchaseOrderPoll'.
DBCC results for 'TMP_ReceiptPoll'.
There are 0 rows in 0 pages for object 'TMP_ReceiptPoll'.
DBCC results for 'TMP_RetPoll'.
There are 0 rows in 0 pages for object 'TMP_RetPoll'.
DBCC results for 'TMP_STOCKDEMAND'.
There are 0 rows in 0 pages for object 'TMP_STOCKDEMAND'.
DBCC results for 'TMP_RECON'.
There are 0 rows in 0 pages for object 'TMP_RECON'.
DBCC results for 'TMP_DAILYITMVAR'.
There are 0 rows in 0 pages for object 'TMP_DAILYITMVAR'.
DBCC results for 'ALERT_INFO'.
There are 0 rows in 0 pages for object 'ALERT_INFO'.
DBCC results for 'WASTE_ITEMS'.
There are 0 rows in 0 pages for object 'WASTE_ITEMS'.
DBCC results for 'Tmp_RmCountSheet'.
There are 0 rows in 0 pages for object 'Tmp_RmCountSheet'.
DBCC results for 'ALERT_SUBSCRIBER'.
There are 0 rows in 0 pages for object 'ALERT_SUBSCRIBER'.
DBCC results for 'PREATTACH_LIST'.
There are 0 rows in 0 pages for object 'PREATTACH_LIST'.
DBCC results for 'BREAK_POINTS'.
There are 0 rows in 0 pages for object 'BREAK_POINTS'.
DBCC results for 'ALERT_TYPE'.
There are 0 rows in 0 pages for object 'ALERT_TYPE'.
DBCC results for 'CATEGORY'.
There are 0 rows in 0 pages for object 'CATEGORY'.
DBCC results for 'BREAK_TABLE'.
There are 0 rows in 0 pages for object 'BREAK_TABLE'.
DBCC results for 'BREAK_TABLE_RULES'.
There are 0 rows in 0 pages for object 'BREAK_TABLE_RULES'.
DBCC results for 'AMWS_BUTTON'.
There are 160 rows in 2 pages for object 'AMWS_BUTTON'.
DBCC results for 'CATEGORY_ITEMS'.
There are 0 rows in 0 pages for object 'CATEGORY_ITEMS'.
DBCC results for 'CONDIMENTS'.
There are 0 rows in 0 pages for object 'CONDIMENTS'.
DBCC results for 'PREATTACHED_LIST_DETAILS'.
There are 0 rows in 0 pages for object 'PREATTACHED_LIST_DETAILS'.
DBCC results for 'AMWS_CONFIGURATION'.
There are 1 rows in 1 pages for object 'AMWS_CONFIGURATION'.
DBCC results for 'CATEGORY_XML'.
There are 0 rows in 0 pages for object 'CATEGORY_XML'.
DBCC results for 'AMWS_Session'.
There are 83 rows in 1 pages for object 'AMWS_Session'.
DBCC results for 'AMWS_USER'.
There are 2 rows in 1 pages for object 'AMWS_USER'.
DBCC results for 'CATEGORY_ITEMS_XML'.
There are 0 rows in 0 pages for object 'CATEGORY_ITEMS_XML'.
DBCC results for 'AMWS_TRANS'.
There are 368 rows in 5 pages for object 'AMWS_TRANS'.
DBCC results for 'INV_EXPLODE_SUPPORT'.
There are 6 rows in 1 pages for object 'INV_EXPLODE_SUPPORT'.
DBCC results for 'TMP_DAILYSHIFT'.
There are 0 rows in 0 pages for object 'TMP_DAILYSHIFT'.
DBCC results for 'AMWS_TAB'.
There are 15 rows in 1 pages for object 'AMWS_TAB'.
DBCC results for 'TMP_EMPONCLOCK'.
There are 0 rows in 0 pages for object 'TMP_EMPONCLOCK'.
DBCC results for 'CATEGORY_TRANSACTIONS'.
There are 0 rows in 0 pages for object 'CATEGORY_TRANSACTIONS'.
DBCC results for 'TMP_EMPSUMMARY'.
There are 0 rows in 0 pages for object 'TMP_EMPSUMMARY'.
DBCC results for 'CALENDAR_METHOD'.
There are 16 rows in 1 pages for object 'CALENDAR_METHOD'.
DBCC results for 'TIME_SLOT'.
There are 96 rows in 1 pages for object 'TIME_SLOT'.
DBCC results for 'TMP_JOBCLASSSUMMARY'.
There are 0 rows in 0 pages for object 'TMP_JOBCLASSSUMMARY'.
DBCC results for 'TMP_JOBCLASSSUMMARYSUB'.
There are 0 rows in 0 pages for object 'TMP_JOBCLASSSUMMARYSUB'.
DBCC results for 'CLOSED_DAY'.
There are 0 rows in 0 pages for object 'CLOSED_DAY'.
DBCC results for 'BREAK_POINTS_XML'.
There are 0 rows in 0 pages for object 'BREAK_POINTS_XML'.
DBCC results for 'TMP_LABORHRS'.
There are 0 rows in 0 pages for object 'TMP_LABORHRS'.
DBCC results for 'RECON_SUSPEND_HIST'.
There are 0 rows in 0 pages for object 'RECON_SUSPEND_HIST'.
DBCC results for 'TMP_WKTIMECARD'.
There are 0 rows in 0 pages for object 'TMP_WKTIMECARD'.
DBCC results for 'CTILock_Detail'.
There are 0 rows in 1 pages for object 'CTILock_Detail'.
DBCC results for 'EMPLOYEE_TIME_OFF'.
There are 0 rows in 0 pages for object 'EMPLOYEE_TIME_OFF'.
DBCC results for 'RM_THEO_INFO'.
There are 0 rows in 0 pages for object 'RM_THEO_INFO'.
DBCC results for 'EMPLOYEE_SCHEDULE'.
There are 0 rows in 0 pages for object 'EMPLOYEE_SCHEDULE'.
DBCC results for 'CTILocks'.
There are 0 rows in 1 pages for object 'CTILocks'.
DBCC results for 'RECEIVE_TEMPLATE'.
There are 0 rows in 0 pages for object 'RECEIVE_TEMPLATE'.
DBCC results for 'BREAK_TABLE_RULES_XML'.
There are 0 rows in 0 pages for object 'BREAK_TABLE_RULES_XML'.
DBCC results for 'Purchase_order_report'.
There are 0 rows in 0 pages for object 'Purchase_order_report'.
DBCC results for 'BUDGET_EDITOR'.
There are 0 rows in 0 pages for object 'BUDGET_EDITOR'.
DBCC results for 'Purchase_order_report_details'.
There are 0 rows in 0 pages for object 'Purchase_order_report_details'.
DBCC results for 'Employee_Schedule_Summary'.
There are 0 rows in 0 pages for object 'Employee_Schedule_Summary'.
DBCC results for 'CURRENT_DAY'.
There are 1 rows in 1 pages for object 'CURRENT_DAY'.
DBCC results for 'Receive_Template_Detail'.
There are 0 rows in 0 pages for object 'Receive_Template_Detail'.
DBCC results for 'CURRENT_SITE_INFO'.
There are 1 rows in 1 pages for object 'CURRENT_SITE_INFO'.
DBCC results for 'DAY_PLANNER'.
There are 2 rows in 1 pages for object 'DAY_PLANNER'.
DBCC results for 'BREAK_TABLE_XML'.
There are 0 rows in 0 pages for object 'BREAK_TABLE_XML'.
DBCC results for 'TMP_COG'.
There are 0 rows in 0 pages for object 'TMP_COG'.
DBCC results for 'Tmp_SvrSales'.
There are 0 rows in 0 pages for object 'Tmp_SvrSales'.
DBCC results for 'DELIVERY_SCHEDULE'.
There are 0 rows in 0 pages for object 'DELIVERY_SCHEDULE'.
DBCC results for 'Emp_Schedule_option'.
There are 2 rows in 1 pages for object 'Emp_Schedule_option'.
DBCC results for 'IDVALUES'.
There are 89 rows in 1 pages for object 'IDVALUES'.
DBCC results for 'JOB_CONFIG'.
There are 0 rows in 0 pages for object 'JOB_CONFIG'.
DBCC results for 'CONDIMENTS_XML'.
There are 0 rows in 0 pages for object 'CONDIMENTS_XML'.
DBCC results for 'INV_CLASS'.
There are 0 rows in 0 pages for object 'INV_CLASS'.
DBCC results for 'MACRO'.
There are 2 rows in 1 pages for object 'MACRO'.
DBCC results for 'SHIFT'.
There are 0 rows in 0 pages for object 'SHIFT'.
DBCC results for 'INV_DEPT'.
There are 0 rows in 0 pages for object 'INV_DEPT'.
DBCC results for 'MACRO_TASK'.
There are 2 rows in 1 pages for object 'MACRO_TASK'.
DBCC results for 'EMPLOYEE_PREFS'.
There are 0 rows in 0 pages for object 'EMPLOYEE_PREFS'.
DBCC results for 'CLASS'.
There are 1045 rows in 9 pages for object 'CLASS'.
DBCC results for 'DELIVERY_SCHEDULE_XML'.
There are 0 rows in 0 pages for object 'DELIVERY_SCHEDULE_XML'.
DBCC results for 'INV_UNIT'.
There are 0 rows in 0 pages for object 'INV_UNIT'.
DBCC results for 'NAV_TEMPLATES'.
There are 1 rows in 1 pages for object 'NAV_TEMPLATES'.
DBCC results for 'DAYPART'.
There are 80 rows in 1 pages for object 'DAYPART'.
DBCC results for 'EXCLUDEDEPARTMENTS'.
There are 5 rows in 1 pages for object 'EXCLUDEDEPARTMENTS'.
DBCC results for 'DEPARTMENT'.
There are 880 rows in 8 pages for object 'DEPARTMENT'.
DBCC results for 'LOCATION'.
There are 0 rows in 0 pages for object 'LOCATION'.
DBCC results for 'DEPARTMENT_SALES'.
There are 14859 rows in 171 pages for object 'DEPARTMENT_SALES'.
DBCC results for 'LABOR_MONITOR'.
There are 0 rows in 0 pages for object 'LABOR_MONITOR'.
DBCC results for 'ROLE'.
There are 17 rows in 1 pages for object 'ROLE'.
DBCC results for 'DEPOSIT'.
There are 0 rows in 0 pages for object 'DEPOSIT'.
DBCC results for 'GLCATEGORY_XML'.
There are 0 rows in 0 pages for object 'GLCATEGORY_XML'.
DBCC results for 'MENU_ITEM'.
There are 0 rows in 0 pages for object 'MENU_ITEM'.
DBCC results for 'ROLE_MACRO'.
There are 4 rows in 1 pages for object 'ROLE_MACRO'.
DBCC results for 'DRAWER_PULL'.
There are 445 rows in 4 pages for object 'DRAWER_PULL'.
DBCC results for 'MENU_ITEM_INGREDIENT'.
Server: Msg 8926, Level 16, State 3, Line 1
Table error: Cross object linkage: Parent page (0:1), slot 0, in object ID 1573580644, index ID 2, and page (1:2915), slot 0, in object ID 18099105, index ID 1, next refer to page (1:3438) but are not in the same object.
Server: Msg 8926, Level 16, State 1, Line 1
Table error: Cross object linkage: Parent page (0:1), slot 0, in object ID 1573580644, index ID 2, and page (1:2913), slot 0, in object ID 18099105, index ID 1, next refer to page (1:3436) but are not in the same object.
Server: Msg 8926, Level 16, State 1, Line 1
Table error: Cross object linkage: Parent page (0:1), slot 0, in object ID 1573580644, index ID 2, and page (1:3122), slot 0, in object ID 18099105, index ID 1, next refer to page (1:3437) but are not in the same object.
Server: Msg 8926, Level 16, State 1, Line 1
Table error: Cross object linkage: Parent page (0:1), slot 0, in object ID 1573580644, index ID 2, and page (1:2912), slot 0, in object ID 18099105, index ID 1, next refer to page (1:3433) but are not in the same object.
There are 0 rows in 0 pages for object 'MENU_ITEM_INGREDIENT'.
DBCC results for 'DRIVE_THRU'.
There are 0 rows in 0 pages for object 'DRIVE_THRU'.
DBCC results for 'ROLE_TASK'.
There are 478 rows in 2 pages for object 'ROLE_TASK'.
DBCC results for 'EMP_SALES_DETAIL'.
There are 17488 rows in 219 pages for object 'EMP_SALES_DETAIL'.
DBCC results for 'GLSUBCATEGORY_XML'.
There are 0 rows in 0 pages for object 'GLSUBCATEGORY_XML'.
DBCC results for 'RAW_MATERIAL'.
There are 0 rows in 0 pages for object 'RAW_MATERIAL'.
DBCC results for 'EMP_SALES_MAIN'.
There are 515 rows in 3 pages for object 'EMP_SALES_MAIN'.
DBCC results for 'ROLE_USER'.
There are 2 rows in 1 pages for object 'ROLE_USER'.
DBCC results for 'EMP_SHIFT_DETAIL'.
Server: Msg 8926, Level 16, State 3, Line 1
Table error: Cross object linkage: Parent page (0:1), slot 0, in object ID 1573580644, index ID 2, and page (1:3271), slot 0, in object ID 18099105, index ID 1, next refer to page (1:3432) but are not in the same object.
Server: Msg 8926, Level 16, State 1, Line 1
Table error: Cross object linkage: Parent page (0:1), slot 0, in object ID 1573580644, index ID 2, and page (1:3487), slot 0, in object ID 18099105, index ID 1, next refer to page (1:3435) but are not in the same object.
Server: Msg 8926, Level 16, State 1, Line 1
Table error: Cross object linkage: Parent page (0:1), slot 0, in object ID 1573580644, index ID 2, and page (1:3052), slot 0, in object ID 18099105, index ID 1, next refer to page (1:3434) but are not in the same object.
Server: Msg 8936, Level 16, State 1, Line 1
Table error: Object ID 1573580644, index ID 2. B-tree chain linkage mismatch. (1:3271)->next = (1:3432), but (1:3432)->Prev = (1:2784).
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 1573580644, index ID 2. B-tree page (1:3432) has two parent nodes (0:1), slot 0 and (1:179), slot 1.
Server: Msg 8936, Level 16, State 1, Line 1
Table error: Object ID 1573580644, index ID 2. B-tree chain linkage mismatch. (1:2912)->next = (1:3433), but (1:3433)->Prev = (1:3460).
Server: Msg 8937, Level 16, State 1, Line 1
Table error: Object ID 1573580644, index ID 2. B-tree page (1:3433) has two parent nodes (0:1), slot 0 and (1:3432), slot 1.
Server: Msg 8936, Level 16, State 1, Line 1
Table error: Object ID 1573580644, index ID 2. B-tree chain linkage mismatch. (1:3052)->next = (1:3434), bu

View 13 Replies View Related

Sql 6.5: Error : 605, Severity: 21, State: 1

Oct 2, 1999

I have a big problem with a SQL 6.5 (no SP) running
in a production environment on NT 3.51 SP 4 since
2,5 years.

Suddenly Friday at 99/10/01 14:17:38.93 we started
having problems and we could'nt connect to the
DB from our client server application written in VB4.

We rebooted the server and we had other errors at
99/10/01 16:15:40.96.

The error code is 605-21-1 and it seems like the main
table (FILMS) of our db (VISPO) has phisical allocation
problems.

here is en extract from the SQLServer error log
of the first problem:

99/10/01 14:17:38.93 kernel udread: Operating system error 23(Data error (cyclic redundancy check)) on device 'E:MSSQLDATAvispodat.DAT' (virtpage 0x05000f35).
99/10/01 14:17:43.62 spid13 Buffer 9531a0 from database 'vispo' has page number -1 in the page header and page number 3893 in the buffer header
99/10/01 14:17:43.69 kernel mirrorproc: i/o error on primary device 'E:MSSQLDATAvispodat.DAT'

And here is what we had at 16:15

99/10/01 16:15:40.96 spid11 Getpage: bstat=0x1008/0, sstat=0x80010130, disk99/10/01 16:15:40.96 spid11 pageno is/should be:objid is/should be:99/10/01 16:15:40.96 spid11 0xffffffff(-1)0xffffffff(-1)99/10/01 16:15:40.96 spid11 0xf34(3892)0xe4e2b2e(240003886)99/10/01 16:15:40.96 spid11 ... retry bufget after purging bp 0x943a8099/10/01 16:15:40.98 spid11 Error : 605, Severity: 21, State: 1
99/10/01 16:15:40.98 spid11 Attempt to fetch logical page 3892 in database 'vispo' belongs to object '-1', not to object 'FILMS'.

We are thinking about restoring the BackUp of the previous night that should be OK,
but I would like what we can try to do in order to have the
db working properly.

Even if the restore would be fine, maybe we are starting
to have problems on the disk subsystems?

What can we check, something like scandisk in DOS?

I attach here in ZIP format the 2 log files and plese ignore the MAPI errors
that are "normal", we just don't care.
I don't know if it's possible to attach files to a newsgroup or a discussion
group but I will try

Any help would be appreciated.

Thanks in advance.

Eugenio La Mesa
Publisoft
Rome - Italy

View 1 Replies View Related

Help For Error: 602, Severity: 21, State: 4

Sep 14, 2007

Please help me the cause and solution for Error: 602, Severity: 21, State: 4 which is raised while trying to excute a select query on a particular table.

This does not occur every time i excute the query

thanks in advance

View 4 Replies View Related

Error 823, Severity 24, State 2 (Again)

Oct 1, 2004

I synch 4 databases everyday and on one of them I get the Error 823, Severity 24, State 2 error (Yes I know you have heard this before but I am a new, LOL). I have tried detaching the database and copying it, renaming that database and then copying back to the original name with the same error; therefore, I think the error is somewhere in the database structure. If it is the database structure would it still give the error above or is that simply a hardware error? I have been searching for solution and I am at a loss. Any help would be appreciated.

Thanks.

N. Adkins

View 3 Replies View Related

Error: 644, Severity: 21, State: 6

Nov 11, 2004

Hi All

Ignore the error below, It's got to do with isolation levels (nolock in this case): refer http://support.microsoft.com/?kbid=834290 for details.

Error: 644, Severity: 21, State: 6
Could not find the index entry for RID '1631393920202020202020202020202033392020202020202 020202020202019bcd3113230303037333120202020202020' in index page (1:420134), index ID 0, database 'DBName'..

What I'd like to know is how to get the table name that was affected out of this error message. Do I query sysindexes, sysobjects, use a function or something else?

Thanks in advance.

Graham

View 1 Replies View Related

Error: 0, Severity: 19, State: 0

Mar 31, 2008

Hi, i encounter a problem with my sql.
What my system does is that it restore/dump database from some backup.
it will then send email using the xp_sendmail. After that it will send out sms using a command line script.

The timing as per the attachment i put in here. Pls kindly help. production issue.

Here are some other events that caused the error

Using 'dbghelp.dll' version '4.0.5'
*Stack Dump being sent to C:Program FilesMicrosoft SQL ServerMSSQLlogSQLDump0003.txt

Error: 0, Severity: 19, State: 0

SqlDumpExceptionHandler: Process 55 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process..

Stack Signature for the dump is 0xF107CBA8

Pls let me know if you need any information

View 1 Replies View Related

Severity: 14, State: 8 Error... Need Help

Jan 9, 2007

Hello guys,

Error: 18456, Severity: 14, State: 8.
Login failed for user 'sa'. [CLIENT: <ip address>]

With what Ive searched.. State: 8 is wrong password. What Ive
encountered I believed is not State: 8 I guess... I have 2 pc..
PCX and PCY.. PCY has SQL Server 2005 so does PCX.. when I run my application that stores data to PCY DB it prompts me an error just
like the one above.. but what seems to be confusing me is both of them have the same DB password. Did I miss something... please help..

-------------------
Real Programmer dont document

If its hard to write Then
its easy to undertand.
End If

View 19 Replies View Related

Error:602,Severity:21,State:4

Sep 15, 2007

Hi,

In my application i used to do the take the backup of current

database and restore it with a backup which was taken earlier and

execute a select command on a particular table.

My problem is,backup & restore operations get completed

successfully but error is raised when tried to open a recordset

for a select statement.Following error was recorded in the sql

error log.

Error: 602, Severity: 21, State: 4

Could not find row in sysindexes for database ID 15, object ID

1109578991, index ID 1. Run DBCC CHECKTABLE on sysindexes..

After this i terminated my application and repeated the above

operation this time i got the same error but with index ID 0 but

the database id and object id remained the same.

When scanned the sysobjects for the particular objectid and i

found out that the id belong to a SP - dt_setpropertybyid_u

I have encountered the same problem three times,but after that i

did not get the problem

Regards

View 1 Replies View Related

Error: 0, Severity: 19, State: 0

Sep 5, 2007

While my production sql server was running, suddenly i got the error below and the connection was lost. Can anyone pls guide what is this error for, why this occured and how to resolve it. I got this error 2 times in two months.

Error: 0, Severity: 19, State: 0

SqlDumpExceptionHandler: Process 232 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.

I run SQL Server 2000 with SP4 with OS Win 2003. I found this error in event viewer. I am assuming that some procedure was running at this time.

Pls help me in troubleshooting this issue.

Help appreciated.

View 1 Replies View Related

Error: 18456, Severity

May 16, 2008

I am not sure if th is is the right place to post this error but I am at my wits end on how resolve this problem
My even viewer and log is logging this every min. This is happening on my MOSS 2007 production database server.
I have been loooking on line and have not been able to find a concrete answer has anyone run into this problem and can you point me in the righ direction. Machine is Sql Server Standard win2003 Server service pack2

2008-05-14 19:46:00.66 Logon Login failed for user 'Domainuseraccount'. [CLIENT: <local machine>]
2008-05-14 19:47:00.66 Logon Error: 18456, Severity: 14, State: 16.

Thanks in advance for any assistance

Neil Palmer

View 1 Replies View Related

How To Generate A Severity Error Of 10 Or Less?

Jul 25, 2007

Hello,

I'm studying SQL database and like to get an InfoMessage event raised by generating an error of severity level 10 or less.

How can I achieve this?

(I tried sql syntax errors, but they result in severity error levels 15 or 16)

thanks

View 3 Replies View Related

Error 5180 Severity 22 State 0

Mar 14, 2001

Hi,
I am working on a project where I have to corrupt the MS SqlServer database in a test environment and generate the following error in the NT Event log:

5180 22 1 Could not open FCB for invalid file ID %din
database '%.*ls'. Table or database may be corrupted.

Can some one tell me the sequence of steps that I need to follow to generate the above error messages.

I found one database corruption script in www.swynk.com. but that was not useful to generate the above error messages.

Please help.

Thanks
Sri

View 1 Replies View Related

Error: 17903, Severity: 18, State: 1

Mar 5, 2001

ERRORLOG has the below contents when I attempt to start the SQL Mail Supprot Service. I have verified that my mail profile is properly configured.

2001-03-05 10:23:48.98 ods Starting SQL Mail session...
2001-03-05 10:23:50.20 ods Error: 17903, Severity: 18, State: 1
2001-03-05 10:23:50.20 ods MAPI login failure..
2001-03-05 10:23:50.20 ods Error: 17951, Severity: 18, State: 1
2001-03-05 10:23:50.20 ods Failed to start SQL Mail session..

Thoughts,
Brian Kilby

View 1 Replies View Related

SQL Error : 1608, Severity: 21, State: 2

Feb 3, 1999

Hi,

Is there somone who can explain the error please?

DESCRIPTION:Error : 1608, Severity: 21, State: 2
A network error was encountered while sending results to the front end. Check the SQL Server errorlog for more information.

MESSAGE:(None)

TASK RUN:(None)

is this realy a network error??

View 1 Replies View Related

Error 1105, Severity: 17, State: 2

Feb 4, 1999

SQL Server version 6.5 pack 4 and Windows NT 4.0 pack 3

"Error 1105, Severity: 17, State: 2
Can't allocate space for object 'Syslogs' in Database 'TNGDB' because the
'logsegment' segment is full. If you run out of space in 'Syslogs', dump
the transaction log. Otherwise use Alter database or sp_extendsegment to
increase the size of the segment"
The database size was 20 and the log size 15. Yesterday after I got the
same message I went to edit the database and expanded the database size and
log to DB 23 and log 20. Backup of the log and maintenance was done last
night. However, the error message is still there. Also I went to edit the
database device and for the DB device I see -795 and I am not able to
change the size at all. The same with the log it shows -798 and no option
to change the size. Please advice.
Shashu

View 1 Replies View Related

SQL Error: 9003, Severity: 20, State: 1.

May 26, 2006

Please, help me.
I haven't a backup.

2006-05-26 11:35:22.76 server Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
May 31 2003 16:08:15
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.2 (Build 3790: Service Pack 1)

2006-05-26 11:35:22.76 server Copyright (C) 1988-2002 Microsoft Corporation.
2006-05-26 11:35:22.76 server All rights reserved.
2006-05-26 11:35:22.76 server Server Process ID is 1868.
2006-05-26 11:35:22.76 server Logging SQL Server messages in file 'C:Program FilesMicrosoft SQL ServerMSSQL$MSFWLOGERRORLOG'.
2006-05-26 11:35:22.85 server SQL Server is starting at priority class 'normal'(2 CPUs detected).
2006-05-26 11:35:23.65 server SQL Server configured for thread mode processing.
2006-05-26 11:35:23.68 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
2006-05-26 11:35:24.01 spid3 Starting up database 'master'.
2006-05-26 11:35:24.31 spid3 Error: 9003, Severity: 20, State: 1.
2006-05-26 11:35:24.45 spid3 Cannot recover the master database. Exiting.

THX
MaX

View 3 Replies View Related

Error : 60004, Severity: 10, State: 1 - What Does This Mean?

Jun 8, 2001

TechNet has nothing on the following error:

Error : 60004, Severity: 10, State: 1
Update routine finished OK

which is showing up in both the SQL Error log and the NT Event Viewer.

Can anyone help?

View 1 Replies View Related

Severity Level 19, SqlDumpExceptionHandler Error Please Need Help

Mar 22, 2002

I am getting the following error, Do you any suggesions?
Thanks
Rau
SqlDumpExceptionHandler: Process 62 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process..

View 1 Replies View Related

Error:17805,Severity 20:State 3

Jul 23, 2002

Hi ,
I am getting this error message in my SQL Server logs.
SQL2k/SP1/Win2k.

Error:17805,Severity 20:State 3
Invalid buffer received from client..

Any thoughts!
Thanks!

View 1 Replies View Related

Error: 1203, Severity: 20, State: 1

Aug 21, 2002

We have a customized package which uses 2 middle layers before it hits the database.
yesterday the sqlserver rebooted all of sudden and I got this error

Process ID 96 attempting to unlock unowned resource KEY: 7:167671645:4 (8d021bb2cdf2)..

Error: 1203, Severity: 20, State: 1

Error 1203
Severity Level 20
Message Text
Process ID %d attempting to unlock unowned resource %.*ls.

Explanation
This error occurs when Microsoft� SQL Server� is engaged in some activity other than normal post-processing
cleanup and it finds that a particular page it is attempting to unlock is already unlocked. The
underlying cause for this error may be related to structural problems within the affected database. SQL Server manages
the acquisition and release of pages to maintain concurrency control in the multi-user environment. This mechanism is maintained
through the use of various internal lock structures that identify the page and the type of lock present. Locks are acquired
for processing of affected pages and released when the processing is completed.

Action
Execute DBCC CHECKDB against the database in which the object belongs. If DBCC CHECKDB reports no errors, attempt to reestablish the connection and execute the command.

Important If executing DBCC CHECKDB with one of the repair clauses does not correct the index problem, or if you are unsure what effect DBCC CHECKDB with a repair clause has on your data, contact your primary support provider

Can anyone help with this.DBCC checkdb returned without errors.

View 1 Replies View Related

Error: 9003, Severity: 20, State: 1

Dec 4, 2005

Hi All,

I'm stuck with "Error: 9003, Severity: 20, State: 1" in MS-SQL Server 2000..I dont want to re-install the sql server ..since..i have other dependent s/w..!
I guess..the Master DB is corrupted....!!

When I tried to rebuild the Master db, i dont find the exe for rebuilding....it...!!

================================================== =======
Error log:
--------

C:Program FilesMicrosoft SQL ServerMSSQLBinn>sqlservr -c -T3608
2005-12-05 09:56:50.81 server Microsoft SQL Server 2000 - 8.00.760 (Intel X8
6)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

2005-12-05 09:56:50.82 server Copyright (C) 1988-2002 Microsoft Corporation.

2005-12-05 09:56:50.82 server All rights reserved.
2005-12-05 09:56:50.82 server Server Process ID is 5548.
2005-12-05 09:56:50.82 server Logging SQL Server messages in file 'C:Program
FilesMicrosoft SQL ServerMSSQLlogERRORLOG'.
2005-12-05 09:56:50.84 server SQL Server is starting at priority class 'norma
l'(2 CPUs detected).
2005-12-05 09:56:50.88 server SQL Server configured for thread mode processin
g.
2005-12-05 09:56:50.90 server Using dynamic lock allocation. [2500] Lock Bloc
ks, [5000] Lock Owner Blocks.
2005-12-05 09:56:50.90 server Attempting to initialize Distributed Transactio
n Coordinator.
2005-12-05 09:56:52.93 spid4 Recovering only master database
2005-12-05 09:56:52.95 spid4 Starting up database 'master'.
2005-12-05 09:56:53.07 spid4 Error: 9003, Severity: 20, State: 1.
2005-12-05 09:56:53.07 spid4 Cannot recover the master database. Exiting.

View 2 Replies View Related

Log Entry - 7105, Severity: 22, State: 6

Jan 28, 2004

Following error on server running

SQL Server 2000 - SP3
No clustering or log sharing

From SQL Server Log

Error: 7105, Severity: 22, State: 6
Page (1:111315), slot 26 for text, ntext, or image node does not exist..

From Event Viewer - Application Log

The description for Event ID ( 17052 ) in Source ( MSSQLSERVER ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: Error: 7105, Severity: 22, State: 6
Page (1:111315), slot 26 for text, ntext, or image node does not exist..

View 1 Replies View Related

Sql Server Severity And Exception Handling

May 29, 2007

I'm creating a class that will wrap a SqlException and will offer the developer a way of determining how to proceed in handling the exception by offering a suggestion of retrying, revalidating the data, and/or calling the entire process a no go.

One of the ways i've come up with to accomplish this is by using the severity (SqlException.Class) to assist in making a suggestion to the developer.

I'm hoping to get some feedback from the developers who use this forum if they feel severity is or is not the way to go, and also to offer any other ways of accomplishing that they can come up with.

Thanx

AJ

View 3 Replies View Related

Error: 18456, Severity: 14, State: 11.

Apr 4, 2008

This error has come up time and again and I can't seem to find a solution.

Specs: SQL Server 2005 v9.00.3054 on x64, Windows Server 2003 SP2

The user is a member of an active directory group. When he connects from his workstation via Management Stuidio, the error is:

Login failed for user '<domain><user>'. [CLIENT: xx.xx.xx.xxx]

I've dropped and re-created the login for the group, but to no avail. I've tried

SELECT * FROM sys.server_principals
and I get a valid entry
<domain>/<user> 81 0x0105... G WINDOWS_GROUP 0 2008-04-04 13:05:00.667 2008-04-04 13:05:00.673 <dbname> us_english NULL

I've verified that the user is a db_owner in the database and that this database is the default for the group.

I also tried
SELECT endpnt.name,

suser_name(perms.grantee_principal_id) as grantee_principal,

perms.permission_name, perms.state_desc

FROM

sys.server_permissions perms,

sys.endpoints endpnt

WHERE

suser_name(perms.grantee_principal_id) = '<domain><user>''

and get
Dedicated Admin Connection <domain><user> CONNECT SQL GRANT
TSQL Local Machine <domain><user> CONNECT SQL GRANT
TSQL Named Pipes <domain><user> CONNECT SQL GRANT
TSQL Default TCP <domain><user> CONNECT SQL GRANT
TSQL Default VIA <domain><user> CONNECT SQL GRANT

Any ideas? Thanks in advance

View 5 Replies View Related