Error 845 running backup of one database

I have one database that I keep getting an error 845: Time out ocurred while
waiting for buffer latch type 3 for page (0:0), database ID 15, object ID
569352192, Index ID 0..
This only started happening last week. The database has not changed (other
than normal data entry) in over a year. Does anyone have any ideas of what
should be checked?
Thanks in advanceDid you see the specific recommendations in Books Online for this?
Error 845
Severity Level 17
Message Text
Time-out occurred while waiting for buffer latch type %d for page %S_PGID, d
atabase ID %d.
Explanation
When under a heavy stress load or high I/O conditions, your system may produ
ce this message.
Action
This message can usually be ignored; however, if you receive repeated messag
es where the wait time
increases, it may indicate an internal server problem. Contact your system a
dministrator. The system
administrator should check the waittype, waittime, lastwaittype, and the wai
tresource columns of
sysprocesses to see what activities each SPIDs is performing.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Connie" <cfelt@.ga.wa.gov> wrote in message news:OcwIz0TWEHA.1144@.TK2MSFTNGP10.phx.gbl...[vb
col=seagreen]
> I have one database that I keep getting an error 845: Time out ocurred whi
le
> waiting for buffer latch type 3 for page (0:0), database ID 15, object ID
> 569352192, Index ID 0..
> This only started happening last week. The database has not changed (othe
r
> than normal data entry) in over a year. Does anyone have any ideas of wha
t
> should be checked?
> Thanks in advance
>[/vbcol]

Error 845 running backup of one database

I have one database that I keep getting an error 845: Time out ocurred while
waiting for buffer latch type 3 for page (0:0), database ID 15, object ID
569352192, Index ID 0..
This only started happening last week. The database has not changed (other
than normal data entry) in over a year. Does anyone have any ideas of what
should be checked?
Thanks in advance
Did you see the specific recommendations in Books Online for this?
Error 845
Severity Level 17
Message Text
Time-out occurred while waiting for buffer latch type %d for page %S_PGID, database ID %d.
Explanation
When under a heavy stress load or high I/O conditions, your system may produce this message.
Action
This message can usually be ignored; however, if you receive repeated messages where the wait time
increases, it may indicate an internal server problem. Contact your system administrator. The system
administrator should check the waittype, waittime, lastwaittype, and the waitresource columns of
sysprocesses to see what activities each SPIDs is performing.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Connie" <cfelt@.ga.wa.gov> wrote in message news:OcwIz0TWEHA.1144@.TK2MSFTNGP10.phx.gbl...
> I have one database that I keep getting an error 845: Time out ocurred while
> waiting for buffer latch type 3 for page (0:0), database ID 15, object ID
> 569352192, Index ID 0..
> This only started happening last week. The database has not changed (other
> than normal data entry) in over a year. Does anyone have any ideas of what
> should be checked?
> Thanks in advance
>
sql

Error 845 running backup of one database

I have one database that I keep getting an error 845: Time out ocurred while
waiting for buffer latch type 3 for page (0:0), database ID 15, object ID
569352192, Index ID 0..
This only started happening last week. The database has not changed (other
than normal data entry) in over a year. Does anyone have any ideas of what
should be checked?
Thanks in advanceDid you see the specific recommendations in Books Online for this?
Error 845
Severity Level 17
Message Text
Time-out occurred while waiting for buffer latch type %d for page %S_PGID, database ID %d.
Explanation
When under a heavy stress load or high I/O conditions, your system may produce this message.
Action
This message can usually be ignored; however, if you receive repeated messages where the wait time
increases, it may indicate an internal server problem. Contact your system administrator. The system
administrator should check the waittype, waittime, lastwaittype, and the waitresource columns of
sysprocesses to see what activities each SPIDs is performing.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Connie" <cfelt@.ga.wa.gov> wrote in message news:OcwIz0TWEHA.1144@.TK2MSFTNGP10.phx.gbl...
> I have one database that I keep getting an error 845: Time out ocurred while
> waiting for buffer latch type 3 for page (0:0), database ID 15, object ID
> 569352192, Index ID 0..
> This only started happening last week. The database has not changed (other
> than normal data entry) in over a year. Does anyone have any ideas of what
> should be checked?
> Thanks in advance
>

error 823

Hello all,
I am fighting this error for a month now.I will explain:It started with the followying steps:

1 Could not allocate space for object '(SYSTEM table id: -789977678)' in database 'TEMPDB' because the 'DEFAULT' filegroup is full..Error: 1105, Severity: 17, State: 2

2 SQL Server Assertion: File: <p:\sql\ntdbms\storeng\drs\include\record.inl>, line=1447
Failed Assertion = 'm_SizeRec > 0 && m_SizeRec <= MAXDATAROW'.
Error: 3624, Severity: 20, State: 1.

3 I/O error (bad page ID) detected during read at offset 0x000000bf074000 in file 'f:\SQL data files\data files\dw_prod.mdf'..
Error: 823, Severity: 24, State: 2

4 DBCC CHECKDB (dw_prod) executed by sa found 7 errors and repaired 0 errors.

5 DBCC CHECKDB (dw_prod, repair_rebuild) executed by sa found 7 errors and repaired 0 errors.

6 DBCC CHECKDB (dw_prod, repair_allow_data_loss) executed by sa found 7 errors and repaired 7 errors.

-- AFTER DBCC CHECKB--therefore in reality the error wasnot corrected--

7 I/O error (bad page ID) detected during read at offset 0x00000091d3a000 in file 'f:\SQL data files\data files\dw_prod.mdf'..
Error: 823, Severity: 24, State: 2

8 SQL Server Assertion: File: <p:\sql\ntdbms\storeng\drs\include\record.inl>, line=1447
Failed Assertion = 'm_SizeRec > 0 && m_SizeRec <= MAXDATAROW'.
Error: 3624, Severity: 20, State: 1.

9 I/O error (bad page ID) detected during read at offset 0x00000091d36000 in file 'f:\SQL data files\data files\dw_prod.mdf'..

10 DBCC CHECKDB (dw_prod, repair_allow_data_loss) executed by sa found 24 errors and repaired 24 errors.

11 I/O error (bad page ID) detected during read at offset 0x000000f6994000 in file 'f:\SQL data files\data files\dw_prod.mdf'..
Error: 823, Severity: 24, State: 2

12 I finally had no other solution than to recover from a good backup (100 G database) - BUT my network admin considers that his hardware is well and WE DID NOT CHECK THE damn HARDWARE!!!!

13 24 H after again I/O error (bad page ID) detected during read at offset 0x0000009d456000 in file 'f:\SQL data files\data files\dw_prod.mdf'..

14 another recovery OK

15

1313 Could not allocate space for object '(SYSTEM table id: -219347948)' in database 'TEMPDB' because the 'DEFAULT' filegroup is full..

14 I/O error (bad page ID) detected during read at offset 0x000000440d0000 in file 'f:\SQL data files\data files\dw_prod.mdf'..

15 dbcc checkdb finds nothing

My question is:

- what I am going to do next? I have recovered now, all went well till the tempdb was not running out of space... I am in the process of checking the hardware

- please say what you think about this.I have never experienced such a pain!

Thanks

LMT|||I had the infamous 823 errors not long ago. In our case, it was a bad raid controller. Poke through your System event logs for error number 50 or 55. Thes can mean some disk problem. Unfortunately, some disk problem can be anything from the mainboard up to the spindle of the disk itself. Since the only moving part is the disk, you should start there, and do a full disk check for bad sectors and such. There are usually vendor specific utilities that should be used for that, so I am afraid I can not help you much further than that. Good luck.|||thanks

is it possible that this 832error to be determined partly bi a tempdb running out of space??

in my case most of errors came after the temdb ran out of space

lmt|||is tempdb also sitting on f: drive?

check your system log in event viewer. that's a darn good place to start. keep a log of dates and times from sql errorlog in front of you while going through system log and see if there were any io subsystem-related errors.

also, put tempdb onto a different drive. always a good idea to keep that bad boy separate. raid-0 for this guy is more than enough. i'd put it on a separate controller as well, preferrably a faster one.

Error 7874 Can't find the object tableName

I have an an MSAccess data project front end linked to an SQL Server Database.
I keep getting Error number 7874: database cannot find the object tblname
when I look however the table is there.
I am calling a procedure which deletes all records in the table and then repopultates it with new records.
so the table is never deleted and recreated.
Once the procedure has run, then I transfertext the table to a local directory.

this works when I run it. However when I try and get the user to do it, they get the error - which doesn't make any sense, because the table is still there, and the procedure call has worked because the table has the selected information in there, it just won't transfer it?

Can anyone help out on this please?

thanks.This should probably be a SQL Server thread rather than Access, but unless I miss my guess, this is a permissions issue. A table may well not be visible to the user unless they have been set up to access SQL Server.
As a developer, it's almost certainly been done for your account.|||Hi,
have checked permissions everywhere I can think of, for the user, and all looks fine.
I don't think you can use t transfertext method in access data project. there doesn't seem to be a way of creating a specification/template for export format, where I can tell it to use tab as a delimiter.
triedtput to method, but that does not give the required result in the text file.

any other ideas of how to get a table out into a text file delimited by tabs?|||Would it surprise you to know I still think it's a permissions issue?
I can move this over to the SQL Server forum if you like. I can't see other ideas as helping at all if the access to the SQL Server table is denied anyway. Sorry.|||

Quote:

Originally Posted by Sami Ward

I have an an MSAccess data project front end linked to an SQL Server Database.
I keep getting Error number 7874: database cannot find the object tblname
when I look however the table is there.
I am calling a procedure which deletes all records in the table and then repopultates it with new records.
so the table is never deleted and recreated.
Once the procedure has run, then I transfertext the table to a local directory.

this works when I run it. However when I try and get the user to do it, they get the error - which doesn't make any sense, because the table is still there, and the procedure call has worked because the table has the selected information in there, it just won't transfer it?

Can anyone help out on this please?

thanks.

What version SQL Server are you using? what version Access are you using?.. on what basis are you logging into SQL server from the client machines are you logging in using Windows integrated security? or standard SQL server permissions?. Are your users assigned to roles? if so what permissions do those roles have for your users compared with yourself who I would guess... is sysadmin role yes? Is this 'procedure' as you call it a 'stored procedure' on the server

These questions are necessary to try and assess your situation in that objects in SQL server rely on the owner creating them. The default owner is 'dbo' in SQL server. You can see this in enterprise manager the standard SQL Server GUI

You will appreciate without sufficient info any advice is blind here... my first simple question or statement would be this:

"If your user opens an Access data project and when they see the tables to which they have permissions do the tables show themselves in the database window with a 'dbo' suffix or not? because if it does then that is where your error lies basically. ADP files are terribly unforgiving when you do not reference a table with the actual owner ie: dbo.tblName in things like listboxes, comboboxes and other routines within code, this is particularly so in a multi user environment"

Why is this? you may ask well the simple answer is this users in SQL server can 'create tables' and other objects ie views having the same name essentially and SQL server distinguishes between them by reference to the OWNER hence the 'dbo' owner prefix in SQL server (cum 'suffix' in an ADP frontend yes confusing isnt it?).

If your SQL server is version 2000 and you do NOT have service pack 1 installed then your table objects for your non sysadmin users will be suffixed with a figure 1. This was a known issue and was fixed in Service pack 1.

(I am not saying this is your answer by the way I am merely illustrating that there can be more reasons than you might think as to why the Access project frontend file the ADP cannot see an explicitly named table called tblName for any users other than yourself who will have the correct permissions.

My suspicions are that you need to look at your 'roles' if you have any and the permissions assigned to the role again more closely and users assigned to those roles.

In terms of getting your data out to tab delimited in a way other than transfertext then yes that can be done at your frontend ADP file using VBA using open file for output methods where you write out your recordset very quickly indeed to a disk text file. Alternatively you could SQL Server BCP out your data super fast to a text file to a specified location on the server side.

It largely depends on what you need to do what your strategies are and where you need your data to go. if its a local directory then if that local directory is also mapped to the server then the BCP option server side could be scheduled to a job on a timer with no user intervention at all.

I use ADP project files extensively so if you get stuck get back to me, but at the moment your information, for me, is too generic and sketchy to enable me to target any one specific thing for you. What I do know is whatever the case this is resolvable... its just a matter of tracking the issue of non recognition down and it will most probably be a simple tick or two here or there on the permissions side.


Regards

Jim :)|||Hi Jim,

thank you very much for your reply. we SQL Server 2000, and I have created an Access 2003 adp to link to the database in sql Server.
there is a group set up, which all relevant users are added to.
the group has access to read, write and execute queries.
everything works fine. all procedures seem to work ok, and users can create tables and update no problem.
the only issue I had was using the transferText method to get the table out into a text file. I have since found another way, by adding a line at the end of the stored procedure that populates the table,
the line is

exec master..xp_cmdshell 'bcp "SELECT * FROM MyDatabase.dbo.MyTable" queryout FileName.txt -c'

This executes a shell, and gets all the records in the table out to the specified text file. the default delimiter is tab which is just what I wanted. there was no way of specifying this in Access because I couldn't use an Export Specification, it just had no option to save it there.

Now the problem is the stored procedure runs fine the table is populated, but the text file is not created - but there are no errors, when the user runs it.
but works ok when I run it and the text file is created.|||Hi,
you can move this to SQL Server forum if you like, I don't mind.

thanks.

Quote:

Originally Posted by NeoPa

Would it surprise you to know I still think it's a permissions issue?
I can move this over to the SQL Server forum if you like. I can't see other ideas as helping at all if the access to the SQL Server table is denied anyway. Sorry.

|||I'll do that Sami. It seems appropriate.|||

Quote:

Originally Posted by Sami Ward

Hi Jim,

thank you very much for your reply. we SQL Server 2000, and I have created an Access 2003 adp to link to the database in sql Server.
there is a group set up, which all relevant users are added to.
the group has access to read, write and execute queries.
everything works fine. all procedures seem to work ok, and users can create tables and update no problem.
the only issue I had was using the transferText method to get the table out into a text file. I have since found another way, by adding a line at the end of the stored procedure that populates the table,
the line is

exec master..xp_cmdshell 'bcp "SELECT * FROM MyDatabase.dbo.MyTable" queryout FileName.txt -c'

This executes a shell, and gets all the records in the table out to the specified text file. the default delimiter is tab which is just what I wanted. there was no way of specifying this in Access because I couldn't use an Export Specification, it just had no option to save it there.

Now the problem is the stored procedure runs fine the table is populated, but the text file is not created - but there are no errors, when the user runs it.
but works ok when I run it and the text file is created.

Sami,

Your problem is going to be with the running of the xp_cmdshell process which is an extended sproc held in the MASTER database and runnable ONLY by people having sysadmin role permissions of which I can assume your users are not members of.

I take it obviously not all your users have sysadmin permissions therefore in order to actually run this process you will need to setup a PROXY account in SQL Server that impersonates a sysadmin and runs the process on their behalf.

Rather than me reinvent the wheel here, below is a couple of web references that explain the way you need to go directionally so to speak

http://msdn2.microsoft.com/en-us/li...00(SQL.80).aspx

http://www.novicksoftware.com/Artic...dshell-Woes.htm

As an aside... (because you say you have rectified your text file write out by invoking BCP on the server) if you DO need to write out the text file tab delimited locally and wish to control that at the client side enabling users to save it to a drive/folder of their choice then I can advise and provide you with the VBA to do that if necessary if the server side BCP write out ended up being a compromise.

Regards

Jim :)|||Hi Jim,

Thank you very much for your reply. I tried looking at the proxy thing, but after much fiddling about couldnot get the thing to work. Set up a DTS instead and called that from the procedure by using the
EXEC msdb.dbo.sp_start_job @.job_name = 'dtsPackageName'

and the same happened worked for me but not the user - because this need to use a proxy account too.
in the end I went to the Security section in the SQL Enterprise Manager, went to Logins, and found the relevant group, clicked on Properties, and went to the Server Roles tab, and ticked the box that said System administrator. That got everything working nicely thank you.

The users are not going to be doing anything in the system, they would just be using the front end application - so that has solved the problem.

hooray!
--------------------

Quote:

Originally Posted by Jim Doherty

Sami,

Your problem is going to be with the running of the xp_cmdshell process which is an extended sproc held in the MASTER database and runnable ONLY by people having sysadmin role permissions of which I can assume your users are not members of.

I take it obviously not all your users have sysadmin permissions therefore in order to actually run this process you will need to setup a PROXY account in SQL Server that impersonates a sysadmin and runs the process on their behalf.

Rather than me reinvent the wheel here, below is a couple of web references that explain the way you need to go directionally so to speak

http://msdn2.microsoft.com/en-us/li...00(SQL.80).aspx

http://www.novicksoftware.com/Artic...dshell-Woes.htm

As an aside... (because you say you have rectified your text file write out by invoking BCP on the server) if you DO need to write out the text file tab delimited locally and wish to control that at the client side enabling users to save it to a drive/folder of their choice then I can advise and provide you with the VBA to do that if necessary if the server side BCP write out ended up being a compromise.

Regards

Jim :)

|||

Quote:

Originally Posted by Sami Ward

Hi Jim,

Thank you very much for your reply. I tried looking at the proxy thing, but after much fiddling about couldnot get the thing to work. Set up a DTS instead and called that from the procedure by using the
EXEC msdb.dbo.sp_start_job @.job_name = 'dtsPackageName'

and the same happened worked for me but not the user - because this need to use a proxy account too.
in the end I went to the Security section in the SQL Enterprise Manager, went to Logins, and found the relevant group, clicked on Properties, and went to the Server Roles tab, and ticked the box that said System administrator. That got everything working nicely thank you.

The users are not going to be doing anything in the system, they would just be using the front end application - so that has solved the problem.

hooray!
--------------------

Thanks for posting your result Sami. (It benefits others viewing)

By doing that you are giving total server permissions to those users and therefore there is nothing to stop any one of them deleting objects and doing anything they like on the server but I'm sure you realise security risk anyway.

Jim :)

Error 7303 Could not initialize data source object of OLE DB provi

I am trying to link to an AS400 server. When I set up the link I am getting
Error 7303 Could not initialize data source object of OLE DB provider.
I know that there are problably parameters that I need to add to the
connection but am not sure where to start. Can someone help me troubleshoot
this issue?
Install Client Access on the SQL Server box and make sure
you have the client updated with whatever service pack level
based on updates to the AS400. Then configure the linked
server as described in books online under Linked Servers,
configuring.
For data source, use the IP address of the AS400.
For provider string, you need to include the library you are
using, connect timeout setting and code page. There is some
documentation for the settings in the Client Access help
files.
You'd set the provider string somewhat like:
InitCat=YourLibrary;CCSID=37;PCCodePage=1252;
Data Source=xxx.xxx.xxx.xxx
Settings will depend on how your AS400 is configured. Again,
the Client Access help files have information on the
necessary connection string settings.
-Sue
On Fri, 14 Oct 2005 08:22:11 -0700, Linda Ibarra
<LindaIbarra@.discussions.microsoft.com> wrote:

>I am trying to link to an AS400 server. When I set up the link I am getting
>Error 7303 Could not initialize data source object of OLE DB provider.
>I know that there are problably parameters that I need to add to the
>connection but am not sure where to start. Can someone help me troubleshoot
>this issue?

Error 7303 Could not initialize data source object of OLE DB provi

I am trying to link to an AS400 server. When I set up the link I am getting
Error 7303 Could not initialize data source object of OLE DB provider.
I know that there are problably parameters that I need to add to the
connection but am not sure where to start. Can someone help me troubleshoot
this issue?Install Client Access on the SQL Server box and make sure
you have the client updated with whatever service pack level
based on updates to the AS400. Then configure the linked
server as described in books online under Linked Servers,
configuring.
For data source, use the IP address of the AS400.
For provider string, you need to include the library you are
using, connect timeout setting and code page. There is some
documentation for the settings in the Client Access help
files.
You'd set the provider string somewhat like:
InitCat=YourLibrary;CCSID=37;PCCodePage=
1252;
Data Source=xxx.xxx.xxx.xxx
Settings will depend on how your AS400 is configured. Again,
the Client Access help files have information on the
necessary connection string settings.
-Sue
On Fri, 14 Oct 2005 08:22:11 -0700, Linda Ibarra
<LindaIbarra@.discussions.microsoft.com> wrote:

>I am trying to link to an AS400 server. When I set up the link I am getting
>Error 7303 Could not initialize data source object of OLE DB provider.
>I know that there are problably parameters that I need to add to the
>connection but am not sure where to start. Can someone help me troubleshoot
>this issue?

Error 605, 823

Does anyone see these errors before? How did you fixed it?
Attempt to fetch logical page (4:27456) in database 'tempdb' belongs to
object '0', not to object '#1AB78AA5'..
Error: 605, Severity: 21, State: 1
... IAM indicates that page is allocated to this object
(4:27456)/(4:27456) 0/448236197
pageno is/should be: objid is/should be:
Getpage: bstat=0x9, sstat=0x4800, cache
I/O error (bad page ID) detected during read at offset 0x000000b6ec4000 in
file 'I:\MSSQL\Data\tempdb1.mdf'..
Error: 823, Severity: 24, State: 2
Thanks,
LijunGeneral recommendations for corrupt or suspect databases:
http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Lijun Zhang" <nospam@.nospam.nospam> wrote in message news:usIUpWzdFHA.2736@.TK2MSFTNGP12.phx.gbl...
> Does anyone see these errors before? How did you fixed it?
> Attempt to fetch logical page (4:27456) in database 'tempdb' belongs to
> object '0', not to object '#1AB78AA5'..
> Error: 605, Severity: 21, State: 1
> ... IAM indicates that page is allocated to this object
> (4:27456)/(4:27456) 0/448236197
> pageno is/should be: objid is/should be:
> Getpage: bstat=0x9, sstat=0x4800, cache
> I/O error (bad page ID) detected during read at offset 0x000000b6ec4000 in
> file 'I:\MSSQL\Data\tempdb1.mdf'..
> Error: 823, Severity: 24, State: 2
>
> Thanks,
> Lijun
>

Error 605 when checkin a 6.5 db

I am getting an Error 605:
'Attempt to fetch logical page <page#> in database <db> belongs to object 0, not to object <table1>'

Does anyone know if this is data corruption or if it is a problem worse than that, and how to begin to address it?

Any help will be much appreciated.
Thank youDo you know what is causing this error ? When is this error generated ?|||Generally that indicates data and / or index corruption, from your specific message most probably corruption in object <table1>.

Q1 Have you at least run dbcc checktable ('table1') WITH ALL_ERRORMSGS on table1?

Normally one would also subsequently perform a dbcc checkdb ('DBName') WITH ALL_ERRORMSGS to make sure there are not issues with / in other objects. (Depending on the results you may need to either perform repairs, restore from backup dumps, etc.)|||Which service pack do you have installed ? There are other less common causes for error 605 - that is why I asked when does the error occur. If it is related to system table(s), you can use sp_fixindex to correct index pages - if the errors exist within data pages you may have to restore from a backup. Otherwise, if you think that it is a corruption then run dbcc checkdb/checkalloc.|||A good point, (certainly if checktable, checkdb, etc. have already indicated that the objects are error free? then the cause(s) likely lie elsewhere).

In any case, more information in such circumstances, (what has been done, some level of system information, etc.), usually makes it much easier to diagnose issue(s) and give you more useful / helpful feedback.|||Thank you all for your replies, we ended up creating a new table and inserting (by chunks) into the new table until the process hung, then trying to find the problem record. Once pinpointed, we selected everything before and after into a new table, dropped the old table and renamed the new table.|||You are welcome.

It is fortunate that not much data was corrupt; Sql Server version. 6.5 supported table level restores (something you may wish to consider implementing to save time, if more row corruption issues arise in the table again). You may also wish to consider periodically running a dbcc checkdb ('DBName') WITH ALL_ERRORMSGS to make sure there are not similar issues with other objects.|||Happy to help.

I remember a time with sql server 7 a similar situation. We had 1 bad pointer (text field) and had to isolate it just as you did. Replication kept bombing during the bcp. It was difficult to find since the table had hundred of thousands of records and the bad field was near the end - replication did not specify a problem with the bcp and as you watched bcp run it appeared it had processed all the records (since the corruption was at the end).

Error 605

Our SQL Server 2000 database had an error last week:
Table error: Database ID 12, object ID 1909581841, index
ID 0. Chain linkage mismatch. (1:154654)->next = (1:228873), but (1:228873)->prev = (1:228872).
We sort of fixed the problem by running dbcc checkdb with
repair_rebuild clause.
It was fine for a week, then yesterday sql server gave us
an error 605:
Server: Msg 605, Level 21, State 1, Line 1
Attempt to fetch logical page (1:123632) in
database 'afsa_ecaps' belongs to object 'employer', not to
object 'consolidation_activity_log'.
Connection Broken
We ran dbcc checkdb again to fix the problem.
My concern is, why does this keep happening? Any thing I
can do to prevent these totally? Any input will appreciate.
Thanks.
PeterI dealt with this problem for a while. Error 605 is still
on my favorites page in BOL because of the frequency.
Finally I noticed this paragraph:
Finally, be sure that your system does not have write
caching enabled on the disk controller. If you suspect
this to be the problem, contact your hardware vendor.
That fixed it for me. Havent had it since.
>--Original Message--
>Our SQL Server 2000 database had an error last week:
>Table error: Database ID 12, object ID 1909581841, index
>ID 0. Chain linkage mismatch. (1:154654)->next =>(1:228873), but (1:228873)->prev = (1:228872).
>We sort of fixed the problem by running dbcc checkdb with
>repair_rebuild clause.
>It was fine for a week, then yesterday sql server gave us
>an error 605:
>Server: Msg 605, Level 21, State 1, Line 1
>Attempt to fetch logical page (1:123632) in
>database 'afsa_ecaps' belongs to object 'employer', not
to
>object 'consolidation_activity_log'.
>Connection Broken
>We ran dbcc checkdb again to fix the problem.
>My concern is, why does this keep happening? Any thing I
>can do to prevent these totally? Any input will
appreciate.
>Thanks.
>Peter
>.
>|||... Also, make sure you don't compress the database files.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"chris" <anonymous@.discussions.microsoft.com> wrote in message
news:001401c3c0d3$5dee8110$a401280a@.phx.gbl...
> I dealt with this problem for a while. Error 605 is still
> on my favorites page in BOL because of the frequency.
> Finally I noticed this paragraph:
> Finally, be sure that your system does not have write
> caching enabled on the disk controller. If you suspect
> this to be the problem, contact your hardware vendor.
>
> That fixed it for me. Havent had it since.
>
> >--Original Message--
> >Our SQL Server 2000 database had an error last week:
> >
> >Table error: Database ID 12, object ID 1909581841, index
> >ID 0. Chain linkage mismatch. (1:154654)->next => >(1:228873), but (1:228873)->prev = (1:228872).
> >We sort of fixed the problem by running dbcc checkdb with
> >repair_rebuild clause.
> >
> >It was fine for a week, then yesterday sql server gave us
> >an error 605:
> >Server: Msg 605, Level 21, State 1, Line 1
> >Attempt to fetch logical page (1:123632) in
> >database 'afsa_ecaps' belongs to object 'employer', not
> to
> >object 'consolidation_activity_log'.
> >Connection Broken
> >
> >We ran dbcc checkdb again to fix the problem.
> >
> >My concern is, why does this keep happening? Any thing I
> >can do to prevent these totally? Any input will
> appreciate.
> >
> >Thanks.
> >Peter
> >
> >.
> >

Error 602: Could not find row in sysindexes for....HELP HELP HELP

Hi,
I am getting following error in SQL Server (SQL Server 6.5) Log.
"Could not find row in sysindexes for database ID %d, object ID %ld, index
ID %d. Run DBCC CHECKTABLE on sysindexes"
I have checked on MSDN but no help. The MSDN artical is saying that there
could be some SP that is uding either a dropped table or dropped index but i
n
my case neither a table is drooped not an index...
Further more (if it helps..)...My application has an inbuild error logger
which logs the error into out table whenever it occurs which tells us the
error line number in VB code. This error line number is defined by me and
logged as well. So in this case it it pointing to the SQL which is a left
join between 2 tables which doesn't join on the column specified by index ID
specified in the error.
Please help me in solving this...as this has stopped our one of the live
site and its not working ny more and my manager is behind me...
I am really on my nees...
All the help are appriciated...but please helpIn addition to the following details, I think one more information may also
helpful. I am getting this error in the interval of every 3 to 4 minutes and
I don't know how SQL server writes this message in log with a consistant
interval.
Any ideas or help?
"Prateek Baxi" wrote:

> Hi,
> I am getting following error in SQL Server (SQL Server 6.5) Log.
> "Could not find row in sysindexes for database ID %d, object ID %ld, index
> ID %d. Run DBCC CHECKTABLE on sysindexes"
> I have checked on MSDN but no help. The MSDN artical is saying that there
> could be some SP that is uding either a dropped table or dropped index but
in
> my case neither a table is drooped not an index...
> Further more (if it helps..)...My application has an inbuild error logger
> which logs the error into out table whenever it occurs which tells us the
> error line number in VB code. This error line number is defined by me and
> logged as well. So in this case it it pointing to the SQL which is a left
> join between 2 tables which doesn't join on the column specified by index
ID
> specified in the error.
> Please help me in solving this...as this has stopped our one of the live
> site and its not working ny more and my manager is behind me...
> I am really on my nees...
> All the help are appriciated...but please help

Error 602: Could not find row in sysindexes for....HELP HELP HELP

Hi,
I am getting following error in SQL Server (SQL Server 6.5) Log.
"Could not find row in sysindexes for database ID %d, object ID %ld, index
ID %d. Run DBCC CHECKTABLE on sysindexes"
I have checked on MSDN but no help. The MSDN artical is saying that there
could be some SP that is uding either a dropped table or dropped index but in
my case neither a table is drooped not an index...
Further more (if it helps..)...My application has an inbuild error logger
which logs the error into out table whenever it occurs which tells us the
error line number in VB code. This error line number is defined by me and
logged as well. So in this case it it pointing to the SQL which is a left
join between 2 tables which doesn't join on the column specified by index ID
specified in the error.
Please help me in solving this...as this has stopped our one of the live
site and its not working ny more and my manager is behind me...
I am really on my nees...
All the help are appriciated...but please helpIn addition to the following details, I think one more information may also
helpful. I am getting this error in the interval of every 3 to 4 minutes and
I don't know how SQL server writes this message in log with a consistant
interval.
Any ideas or help?
"Prateek Baxi" wrote:
> Hi,
> I am getting following error in SQL Server (SQL Server 6.5) Log.
> "Could not find row in sysindexes for database ID %d, object ID %ld, index
> ID %d. Run DBCC CHECKTABLE on sysindexes"
> I have checked on MSDN but no help. The MSDN artical is saying that there
> could be some SP that is uding either a dropped table or dropped index but in
> my case neither a table is drooped not an index...
> Further more (if it helps..)...My application has an inbuild error logger
> which logs the error into out table whenever it occurs which tells us the
> error line number in VB code. This error line number is defined by me and
> logged as well. So in this case it it pointing to the SQL which is a left
> join between 2 tables which doesn't join on the column specified by index ID
> specified in the error.
> Please help me in solving this...as this has stopped our one of the live
> site and its not working ny more and my manager is behind me...
> I am really on my nees...
> All the help are appriciated...but please help

Error 602: Could not find row in sysindexes for....HELP HELP HELP

Hi,
I am getting following error in SQL Server (SQL Server 6.5) Log.
"Could not find row in sysindexes for database ID %d, object ID %ld, index
ID %d. Run DBCC CHECKTABLE on sysindexes"
I have checked on MSDN but no help. The MSDN artical is saying that there
could be some SP that is uding either a dropped table or dropped index but in
my case neither a table is drooped not an index...
Further more (if it helps..)...My application has an inbuild error logger
which logs the error into out table whenever it occurs which tells us the
error line number in VB code. This error line number is defined by me and
logged as well. So in this case it it pointing to the SQL which is a left
join between 2 tables which doesn't join on the column specified by index ID
specified in the error.
Please help me in solving this...as this has stopped our one of the live
site and its not working ny more and my manager is behind me...
I am really on my nees...
All the help are appriciated...but please help
In addition to the following details, I think one more information may also
helpful. I am getting this error in the interval of every 3 to 4 minutes and
I don't know how SQL server writes this message in log with a consistant
interval.
Any ideas or help?
"Prateek Baxi" wrote:

> Hi,
> I am getting following error in SQL Server (SQL Server 6.5) Log.
> "Could not find row in sysindexes for database ID %d, object ID %ld, index
> ID %d. Run DBCC CHECKTABLE on sysindexes"
> I have checked on MSDN but no help. The MSDN artical is saying that there
> could be some SP that is uding either a dropped table or dropped index but in
> my case neither a table is drooped not an index...
> Further more (if it helps..)...My application has an inbuild error logger
> which logs the error into out table whenever it occurs which tells us the
> error line number in VB code. This error line number is defined by me and
> logged as well. So in this case it it pointing to the SQL which is a left
> join between 2 tables which doesn't join on the column specified by index ID
> specified in the error.
> Please help me in solving this...as this has stopped our one of the live
> site and its not working ny more and my manager is behind me...
> I am really on my nees...
> All the help are appriciated...but please help

error 4606 Granted or Revoked privilege

I am recieving error 4606 Granted or revoked privilege SELECT is not compatiable with object.

Canot read the next data row for the dataset BEEP.

However when I use the same userid/pwsd in Crystal to access the same stored proceedure I have no problems accessing the data.

We have already tried re-granting the permissions to the userid to no avail.

Are there any other suggestions?

Phread

We have tried using the SA account also to no avail within SRS.

Both accounts work under Crystal.

Phread

ERROR 229: SELECT permission denied on object sysobjects, database ....

Hi,

I granted all the rights on the database to the user (db_owner, public, db_datawriter, etc...) However, I didn't grant the "System Administrators" role. I also specifically granted the select on those tables (sysobjects and sysindexes) for the user and checked through sp_helprotect sysobjects command whether there are no specific revokes for for that user.

However, the user is still getting the below error while trying to expand the "Tables" view in the Enterprise Manager.

ERROR 229: SELECT permission denied on object 'sysobjects', database 'My_test', owner 'dbo', SELECT permission denied on object 'sysindexes', database 'My_test', owner 'dbo'.

Also, the user claims that he cant seem to do anything with the database, he cant view any objects, and, when he goes to Query Analyzer, if he tries to run a SELECT query on a table (that he know that this table exists), he gets this error:



SELECT permission denied on object 'tblBillingTrans', database 'My_Test', owner 'dbo'.

Any help would be greatly appreciated!
Thanks,
AllaPlease disregard this question... I granted the db_denydatareader option... :p

Error 208: Invalid object name 'syspublications'

Hi!
Before reinstalling sql server and restoring old system databases I
forgot to delete and replication that was no longer needed. Now,
Expired Subscriptions Clean Up job fails with the following error:
Error 208: Invalid object name 'syspublications'. I don't need this
replication and would like to delete that completed but everytime I
try I get the same error message.
Please advise how can I delete all manually.
Thank you,
T.
Hi
Have you checked out http://tinyurl.com/33ls84
John
"tolcis" wrote:

> Hi!
> Before reinstalling sql server and restoring old system databases I
> forgot to delete and replication that was no longer needed. Now,
> Expired Subscriptions Clean Up job fails with the following error:
> Error 208: Invalid object name 'syspublications'. I don't need this
> replication and would like to delete that completed but everytime I
> try I get the same error message.
> Please advise how can I delete all manually.
> Thank you,
> T.
>

Error 208: Invalid object name 'syspublications'

Hi!
Before reinstalling sql server and restoring old system databases I
forgot to delete and replication that was no longer needed. Now,
Expired Subscriptions Clean Up job fails with the following error:
Error 208: Invalid object name 'syspublications'. I don't need this
replication and would like to delete that completed but everytime I
try I get the same error message.
Please advise how can I delete all manually.
Thank you,
T.Hi
Have you checked out http://tinyurl.com/33ls84
John
"tolcis" wrote:
> Hi!
> Before reinstalling sql server and restoring old system databases I
> forgot to delete and replication that was no longer needed. Now,
> Expired Subscriptions Clean Up job fails with the following error:
> Error 208: Invalid object name 'syspublications'. I don't need this
> replication and would like to delete that completed but everytime I
> try I get the same error message.
> Please advise how can I delete all manually.
> Thank you,
> T.
>

Error 208: Invalid object name 'sysextendedarticlesview'

hi,
for maintainance tasks (converting database from SQL_Latin to Latin_General)
we scripted a working merge replication and removed it with Enterprise
Manager (3 servers, 1 database, SQL 2000 SP3 on all 3 Servers).
Now, when trying to reinstall the replication (via script or EM), the
publication seems to be installed ok, snapshot passed without error. But the
setup of a new subscription fails with the following error message (raw
translation from german message):
Error 208: Invalid object name 'sysextendedarticlesview'.
(Original Errormessage: Server: Nachr.-Nr. 208, Schweregrad 16, Status 1,
Prozedur sp_addmergesubscription, Zeile 325
Ungltiger Objektname 'sysextendedarticlesview'.)
This view indeed cannot be found on one of the participating servers, but on
a different set of servers, where the same kind of replication is still
running, this view can't be found either.
Any help / suggestions would we appreciated.
TIA
Frank Linde
find a server/database that has this view on. In EM, right click on the view
and select copy. Then connect to the database you are having this problem
using EM. select tools, Query Analyzer and then hit ctrl v.
Then run this script. You may encounter more missing object problems but
they can be solved in the same way.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"A.Hoff" <z100@.gmx.org> wrote in message
news:cbk6a5$j6m$01$1@.news.t-online.com...
> hi,
> for maintainance tasks (converting database from SQL_Latin to
Latin_General)
> we scripted a working merge replication and removed it with Enterprise
> Manager (3 servers, 1 database, SQL 2000 SP3 on all 3 Servers).
> Now, when trying to reinstall the replication (via script or EM), the
> publication seems to be installed ok, snapshot passed without error. But
the
> setup of a new subscription fails with the following error message (raw
> translation from german message):
> Error 208: Invalid object name 'sysextendedarticlesview'.
> (Original Errormessage: Server: Nachr.-Nr. 208, Schweregrad 16, Status 1,
> Prozedur sp_addmergesubscription, Zeile 325
> Ungltiger Objektname 'sysextendedarticlesview'.)
> This view indeed cannot be found on one of the participating servers, but
on
> a different set of servers, where the same kind of replication is still
> running, this view can't be found either.
> Any help / suggestions would we appreciated.
> TIA
> Frank Linde
>

Error 208: Invaild object name msdb.dbo.MSdistpublishers

Recently my msdb database became corrupt so I had to reinstall SQL Server 7.0. In doing so new system databases were created. I was able to restore all databases and system databases from backups except for the msdb database (unfortunately my backup overwrote the good database before I realized there was a problem). Because of this I have lost publication and subscriber info from my distribution tables that resided in the old msdb database.

What I would like to do is delete all references to previous publications and subscribers and create them all over again. But it does not allow me to create new or delete old publishers or subscribers. I get this and other errors...

Error 208: Invaild object name 'msdb.dbo.MSdistpublishers'

There is in fact no MSdistpublishers table in msdb because it is a new db. Can anyone help me reverse out of this?

Thanks in advance.

SteveIn future make sure to have regular backups for SYSTEM databases too.

I suggest to delete the replication and recreate it freshly which will re-enable the task. Make sure to check all jobs and tasks are scheduled properly after the MSDB restore.

Refer to SQL error log for any information.

Error 208, Missing Stats

Hi chaps

Just been having my head messed with...

I was running a trace capturing all errors and SQL. Had a bucket of
error 208's (invalid object name). Found the SQL that caused it - an
SP.

Ran the sp by hand, no messages come up - error 208 logged in the
trace.

Couldn't work it out. Then noticed stats missing on one column.
Created the stats manually - and suddenly the 208 error stops. Wtf?
Is this predicted/expected behaviour? Just me being a noob?

Thought I'd just share that. ta ;)
SQL2k, sp3a, w2k server.WangKhar (Wangkhar@.yahoo.com) writes:
> I was running a trace capturing all errors and SQL. Had a bucket of
> error 208's (invalid object name). Found the SQL that caused it - an
> SP.

Yes, this to be expected. This is because of deferred name resolution.
If the procedure creates temp tables, you'll get a lot of 208s. It could
be missing stastistics too. These are just signaled internally and inter-
cepted by some other module.

They are possibly of interest if they are causing recompiles for missing
tables, but then you should look for SP:Recompile instead.

And, true, missing statistics is another thing you could find. Then
again, with auto-statistics on, the statistics should come by time anyway.

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Erland Sommarskog <sommar@.algonet.se> wrote in message
> Yes, this to be expected. This is because of deferred name resolution.

Ta.