Error: 7105

Question

Post reply

Error: 7105

Jayakumar Krishnan

SSCarpal Tunnel

Points: 4710
More actions
February 20, 2006 at 5:26 am

#93645

Hi Folks,
I need your help, I'm experiencing the below mentioned error.
Error: 7105, Severity: 22, State: 6 Page (1:3754218), slot 81 for text, ntext, or image node does not exist.
warmest
Jayakumar K
Thanks
Jay
http://www.sqldbops.com

Viewing 15 posts - 1 through 15 (of 19 total)

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

Johan Bijnens SSC Guru Points: 135374 More actions · Answer 1

can you perform a dbcc checkdb ?

Read about it in Books Online to check the options?

Johan

Learn to play, play to learn !

Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:

- How to post Performance Problems
- How to post data/code to get the best help[/url]

- How to prevent a sore throat after hours of presenting ppt

press F1 for solution, press shift+F1 for urgent solution 😀

Need a bit of Powershell? How about this

Who am I ? Sometimes this is me but most of the time this is me

JP de Jong-202059 SSCommitted Points: 1674 More actions · Answer 2

Hi Jayakumar,

First of all:

Check your DB with the DBCC checkdb command. If the database is OK, then you can check on MS Support site for the error. The one you describe is listed twice on MS Support as being a bug that's resolved in SP2 and SP4.

At the moment my SQL 2000 Enterprise Server is running SP4 and I still have the annoying message a few times a month. I have already contacted MS Support services and we are investigating this issue.

What is the SP level you're running? If you're runing SP3 I suggest you investigate if it's possible to upgrade to SP4. (There are some applications that incorrectly check for SP3 or later... like MOM2005).

Also I will let you know what the results of the MS Support investgiation is, as soon as it is clear to them.

Regards,

JP de Jong

Soonyu-163551 SSC Eights! Points: 811 More actions · Answer 3

Kumar,

Any updated news? We also have this message quite frequent.

Ian-386680 Mr or Mrs. 500 Points: 509 More actions · Answer 4

Did anyone find a solution to this one? We have the same problem.

Ian

JP de Jong-202059 SSCommitted Points: 1674 More actions · Answer 5

Ian,

We tried to get MS Support to fix the problem, but unfortunately they didnt' succeed in finding any solutions. We're still getting the error on a almost daily basis....

JP

Darren-418986 SSC Veteran Points: 215 More actions · Answer 6

I am working with MS Support to try to fix our 7105 error, hopefully they will find something. We get it at least daily, if not multiple times, sometimes within minutes after a complete server power cycle. So my fingers are crossed hoping for some resolution..

Ian-386680 Mr or Mrs. 500 Points: 509 More actions · Answer 7

Thanks JP. I've been struggling to find a solution to this one for quite a while. It's good to know we're not the only ones with this issue.

Ian

Jayakumar Krishnan SSCarpal Tunnel Points: 4710 More actions · Answer 8

Hi Ian,

Based on the below article the above issue will occur if affinity mask enabled on the sql server. (Enabling affinity mask thru sp_configure is masking processors for process threads)

In order to resolve this 7105 issue, have to apply hotfix. Kindly check the same...http://support.microsoft.com/kb/890755

warmest

Jayakumar K.

Thanks
Jay
http://www.sqldbops.com

JP de Jong-202059 SSCommitted Points: 1674 More actions · Answer 9

Hi Jayakumar,

We're running on SP4 + fixes up to 2192 and the problem still occurs. This particular post is about a SP3 fix. This should be resolved in SP4.

JP

Erik Bitemo SSCrazy Points: 2062 More actions · Answer 10

Are you guys running queries with (nolock) clause or after in read uncommitted transaction isolation level? If this is the case, then no wonder - this is by design, just think it through...

(the credits goes to Paul Randal if it helped )

-- Erik http://blog.rollback.hu

JP de Jong-202059 SSCommitted Points: 1674 More actions · Answer 11

Erik,

Yes it is read uncommitted, that's for sure, but then again, why don't we get 'the other' error message? (There is a message stating that 'data chas changed due tot data movement' , which is based on a logical data error.(sorry, don't know the exact message). Now we're getting a physical data error (sev. 20 and a broken connection).

And yes, I am aware of the drawbacks of 'reading uncommitted', 'dirty reads', 'nolock hints' etc. Unfortunately, our application vendor isn't and even worse, they clame that reading uncommitted is 'best practice'.

JP

ps: If you have a message from Paul Randall stating 'uncommitted read' is responsible for this errormessage, I would love to receive a copy of that (in private message). Then I can go back to my application vendor ;-).

Erik Bitemo SSCrazy Points: 2062 More actions · Answer 12

JP,

Here's the URL, it was posted to another forum (hopefully I won't be banned for this ).

http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=69430

If you can migrate to 2005, then you can get rid of this problem by using the new SNAPSHOT transaction isolation level. It uses the same technique as Oracle for avoiding blocked readers during writes. If you can't, then, well, er, no idea.

-- Erik http://blog.rollback.hu

JP de Jong-202059 SSCommitted Points: 1674 More actions · Answer 13

Erik

Thanks, that's exactly what I needed. We will be moving that appliation to sql2005 in a few months so let's hope they've correctly implemented the new isolation level!

JP

Johan Bijnens SSC Guru Points: 135374 More actions · Answer 14

please keep us informed regarding your tests with the sql2005 snapshot isolation level to solve this issue

Also keep in mind you may have to provide a larger tempdb to support the snapshot isolation level. (check BOL)