Error: 7105, Severity: 22, State: 6

My SQL server logs this in Application log:
Error: 7105, Severity: 22, State: 6
Page (1:952446), slot 39 for text, ntext, or image node does not exist.
MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS for
a hot fix for this problem.
I believe this call is free because this is a bug. Can anyone confirm this?
Thanks.
Make the call, they will tell you up front if it will be a covered (free)
call.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"ME" <ME@.mail.com> wrote in message
news:%23OovmtT$GHA.3344@.TK2MSFTNGP03.phx.gbl...
> My SQL server logs this in Application log:
> Error: 7105, Severity: 22, State: 6
> Page (1:952446), slot 39 for text, ntext, or image node does not exist.
> MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS
> for
> a hot fix for this problem.
> I believe this call is free because this is a bug. Can anyone confirm
> this?
> Thanks.
>
|||Hotfix calls are always free. Issues that are determined to be bugs are
free, even if no hotfix yet exists.
If you call the 800 number with the KB article # ready, tell them you are
looking for the hotfix, they will code it as "professional unpaid" and
transfer you to the support engineer.
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
http://kevin3nf.blogspot.com
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:eepBp5T$GHA.1760@.TK2MSFTNGP02.phx.gbl...
> Make the call, they will tell you up front if it will be a covered (free)
> call.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
> You can't help someone get up a hill without getting a little closer to
> the top yourself.
> - H. Norman Schwarzkopf
>
> "ME" <ME@.mail.com> wrote in message
> news:%23OovmtT$GHA.3344@.TK2MSFTNGP03.phx.gbl...
>

Error: 7105, Severity: 22, State: 6

My SQL server logs this in Application log:
Error: 7105, Severity: 22, State: 6
Page (1:952446), slot 39 for text, ntext, or image node does not exist.
MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS for
a hot fix for this problem.
I believe this call is free because this is a bug. Can anyone confirm this?
Thanks.it is a SQL 2000 with SP4 on Windows server 2003 SP1.
"ME" <ME@.mail.com> wrote in message news:...
> My SQL server logs this in Application log:
> Error: 7105, Severity: 22, State: 6
> Page (1:952446), slot 39 for text, ntext, or image node does not exist.
> MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS
> for
> a hot fix for this problem.
> I believe this call is free because this is a bug. Can anyone confirm
> this?
> Thanks.
>|||The affinity mask is set as default. The server is 2 dual core CPUs. SQL
sees and uses all of 4 CPUs.
"ME" <ME@.mail.com> wrote in message
news:egU%23OuT$GHA.1224@.TK2MSFTNGP04.phx.gbl...
> it is a SQL 2000 with SP4 on Windows server 2003 SP1.
>
> "ME" <ME@.mail.com> wrote in message news:...
>|||Make the call, they will tell you up front if it will be a covered (free)
call.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"ME" <ME@.mail.com> wrote in message
news:%23OovmtT$GHA.3344@.TK2MSFTNGP03.phx.gbl...
> My SQL server logs this in Application log:
> Error: 7105, Severity: 22, State: 6
> Page (1:952446), slot 39 for text, ntext, or image node does not exist.
> MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS
> for
> a hot fix for this problem.
> I believe this call is free because this is a bug. Can anyone confirm
> this?
> Thanks.
>|||Hotfix calls are always free. Issues that are determined to be bugs are
free, even if no hotfix yet exists.
If you call the 800 number with the KB article # ready, tell them you are
looking for the hotfix, they will code it as "professional unpaid" and
transfer you to the support engineer.
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
http://kevin3nf.blogspot.com
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:eepBp5T$GHA.1760@.TK2MSFTNGP02.phx.gbl...
> Make the call, they will tell you up front if it will be a covered (free)
> call.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
> You can't help someone get up a hill without getting a little closer to
> the top yourself.
> - H. Norman Schwarzkopf
>
> "ME" <ME@.mail.com> wrote in message
> news:%23OovmtT$GHA.3344@.TK2MSFTNGP03.phx.gbl...
>

Error: 17805, Severity: 20, State: 3

1 system transfer from a server (Win2k SP4,SQL2k SP3) to a server (Win2k
SP4,SQL2k SP4), the system can not run and got the error message in log
Error: 17805, Severity: 20, State: 3
Invalid buffer received from client.
Is this SQL2k SP4 new bug?
Hi
No, I've seen those errors since SQL Server 6.0. If a packet gets messed up
at network level, you end up with SQL Server receiving bad packets.
Setup SQL Server to only listen on TCP/IP and see if your problem goes away
(In EM, Server Properties. Network Configuration, Restart the server)
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"HB" <HB@.discussions.microsoft.com> wrote in message
news:50B3B161-06D7-4311-8D92-A3E13A5592C4@.microsoft.com...
>1 system transfer from a server (Win2k SP4,SQL2k SP3) to a server (Win2k
> SP4,SQL2k SP4), the system can not run and got the error message in log
> Error: 17805, Severity: 20, State: 3
> Invalid buffer received from client.
> Is this SQL2k SP4 new bug?
|||We have this exact issue to, we have got around one issue with inserting or
updating text/image columns by specifying an explicit SQLDbType. But we are
now getting the same issue with other stored procedures. If we amend the sql
client to talk named pipes the the problem goes away, but this is not an
option for us. Any help much appreciated.
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> No, I've seen those errors since SQL Server 6.0. If a packet gets messed up
> at network level, you end up with SQL Server receiving bad packets.
> Setup SQL Server to only listen on TCP/IP and see if your problem goes away
> (In EM, Server Properties. Network Configuration, Restart the server)
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "HB" <HB@.discussions.microsoft.com> wrote in message
> news:50B3B161-06D7-4311-8D92-A3E13A5592C4@.microsoft.com...
>
>

Error: 17805, Severity: 20, State: 3

1 system transfer from a server (Win2k SP4,SQL2k SP3) to a server (Win2k
SP4,SQL2k SP4), the system can not run and got the error message in log
Error: 17805, Severity: 20, State: 3
Invalid buffer received from client.
Is this SQL2k SP4 new bug?Hi
No, I've seen those errors since SQL Server 6.0. If a packet gets messed up
at network level, you end up with SQL Server receiving bad packets.
Setup SQL Server to only listen on TCP/IP and see if your problem goes away
(In EM, Server Properties. Network Configuration, Restart the server)
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"HB" <HB@.discussions.microsoft.com> wrote in message
news:50B3B161-06D7-4311-8D92-A3E13A5592C4@.microsoft.com...
>1 system transfer from a server (Win2k SP4,SQL2k SP3) to a server (Win2k
> SP4,SQL2k SP4), the system can not run and got the error message in log
> Error: 17805, Severity: 20, State: 3
> Invalid buffer received from client.
> Is this SQL2k SP4 new bug?|||We have this exact issue to, we have got around one issue with inserting or
updating text/image columns by specifying an explicit SQLDbType. But we are
now getting the same issue with other stored procedures. If we amend the sql
client to talk named pipes the the problem goes away, but this is not an
option for us. Any help much appreciated.
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> No, I've seen those errors since SQL Server 6.0. If a packet gets messed u
p
> at network level, you end up with SQL Server receiving bad packets.
> Setup SQL Server to only listen on TCP/IP and see if your problem goes awa
y
> (In EM, Server Properties. Network Configuration, Restart the server)
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "HB" <HB@.discussions.microsoft.com> wrote in message
> news:50B3B161-06D7-4311-8D92-A3E13A5592C4@.microsoft.com...
>
>