[posted and mailed, please reply in news]
Greg M. (gm********@insightbb.com) writes:
I have a client using SQL 2k, SP2 (due application requirements, SP3 is
not an option - the application vendor will not specify why). We are
receiving:
[Microsoft][ODBC SQL Server Driver]Unknown token received from SQL Server
Connection Broken
There doesn't appear to be any rhyme or reason as to why this is
happening. And...it shows it's ugly head at random places during
execution. Has anyone experienced this also, or have any ideas on what
to look for? I have seen numerous suggestions stating to upgrade from
MDAC 2.6 to 2.7. At this point, I'm not sure if thats an option based
on the vendors application (which by the way they no longer support!).
The message itself indicates a protocol violation. That is, SQL Server
sends something which is not to be expected according to the TDS protocol
that server and client communicate over.
However, in many cases, the message just indicates that the process for
the connection inside SQL Server went belly-up, because of an access
violation, stack overflow or similar bad thing. In this case, you will
find a stack dump in the SQL Server errorlog. Possibly you can then connect
the dump to a certain statement.
But if it is random as you say, then the errorlog may not make you
any wiser. In such case, the best would be to open a case with Microsoft.
Since some sort of bug appears to be involved here, you should get
any initial expenses refunded.
--
Erland Sommarskog, SQL Server MVP,
so****@algonet.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp 
