RUNTIME ERROR 2147467259(80004005)

Question

Post reply

RUNTIME ERROR 2147467259(80004005)

MANJUG05

SSC Veteran

Points: 246
More actions
March 13, 2008 at 2:35 am

#93336

we have a win 2003 teminal server is running. we have installed sql 2k and the databasE package is having vb6 as front end. when we try to execute a query one user is getting the RUNTIME ERROR 2147467259(80004005). can anyone help please

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply

Grant Fritchey SSC Guru Points: 398878 More actions · Answer 1

That error could be a lot of things:

http://support.microsoft.com/kb/180843

http://support.microsoft.com/kb/304070

There are more. You'll need to investigate more on your end and send more information around the error to narrow it down.

"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt

Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning

MANJUG05 SSC Veteran Points: 246 More actions · Answer 2

i traced to the recordset which was giving the error. the error was occurring when that particular query was run even in sql query analyzer.

the error isfrom backend and not from frontend as thought earlier. when the query is run in query analyzer the error was "the process id 68 tried to open an unknown pg:1065001". number is different at different times.

can u shed some light onto this.

thanks in advance

Grant Fritchey SSC Guru Points: 398878 More actions · Answer 3

Sounds like you might have a corrupt database. Can you try running DBCC checkdb() against it?

"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt

Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning

MANJUG05 SSC Veteran Points: 246 More actions · Answer 4

thanks for the response. all other users are not facing this problem. how come database is corrupt.

Grant Fritchey SSC Guru Points: 398878 More actions · Answer 5

Sunspots, seismic activity, who knows. If a page gets written over in some manner, you're probably only going to see it in two calls, the one that wants the page that was written over and the page that did the writing over. But it will likely get worse. However, have you run the DBCC, because I could be wrong on this.

"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt

Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning

MANJUG05 SSC Veteran Points: 246 More actions · Answer 6

hi

thanks for the support. i ran dbcc and found no problems. i was trying all possibilities. the problem got solved but i donno why was the problem occurring only for that query.

actually what i did was this.

the tables in question had a composite pk. we were trying to get rows that had same composite primary key.

suppose table1 has feilds id, name both being pk.

table2 has id, name, address

the query we were using query like

'select address from table2 t2, table1 t1 where t1.id = t2.id and t1.name = t2.name '

i changed the query to

'select address from table2 t2, table1 t1 where t1.id + t1.name = t2.id + t2.name'

thats it. it was working. but still i donno how? the actual structure is more complex, but this is the idea i implemented

thanks in advance

Grant Fritchey SSC Guru Points: 398878 More actions · Answer 7

Sure. Sorry I couldn't help.

You might run into problems with those non-ansi joins too.

Instead of "FROM X, Y WHERE X.Id = Y.Id" you would use "FROM X INNER JOIN Y ON X.Id = Y.Id."

"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt

Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning