SQL Server errors after deploy of 3rd server in wlbs setting

We have 3 web servers for an ecommerce site and the db is on another box using SQL Server 2005, but the db is running in 2000 compatibility mode.
Two of the servers have been running a couple of years using Windows Server 2003 web editiion. The third server is newer and is running Windows Server 2003 standard edtion. It used to be the SQL Server, but we have stopped SQL on it and moved the db. We have tried twice to deploy it as web server #3, but every time we have tried, we start getting SQL Server error messages in an error email that is sent from code in the global.asax. Here are some of the errors- can anyone suggest where to start looking? It is definitely the #3 server because the machine name are in the error messages.
Error Message: ERROR [24000] [Microsoft][ODBC SQL Server Driver]Invalid cursor state Error Source: SQLSRV32.DLL Error Target Site: System.Object QueryValue(System.String)

Error Message: The connection is dead.
Error Source: System.Data

Error Message: ERROR [HYT00] [Microsoft][ODBC SQL Server Driver]Timeout expired Error Source: SQLSRV32.DLL Error Target Site: Void HandleError(System.Runtime.InteropServices.HandleRef, SQL_HANDLE, RETCODE)

Error Message: ERROR [HY010] [Microsoft][ODBC SQL Server Driver]Function sequence error Error Source: SQLSRV32.DLL Error Target Site: System.Object QueryValue(System.String)

Error Message: ERROR [HY000] [Microsoft][ODBC SQL Server Driver]Protocol error in TDS stream ERROR [HY000] [Microsoft][ODBC SQL Server Driver]Protocol error in TDS stream ERROR [HY000] [Microsoft][ODBC SQL Server Driver]TDS buffer length too large ERROR [HY000] [Microsoft][ODBC SQL Server Driver]TDS buffer length too large ERROR [HY000] [Microsoft][ODBC SQL Server Driver]TDS buffer length too large ERROR [HY000] [Microsoft][ODBC SQL Server Driver]TDS buffer length too large ERROR [HY000] [Microsoft][ODBC SQL Server Driver]TDS buffer length too large Error Source: SQLSRV32.DLL Error Target Site: System.Data.DataSet QueryDataset(System.String, System.String)

jmestepAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

 
AaronAbendCommented:
It looks like a client process is making a sql request via  odbc to a nonexistent database. check your odbc data sources
0
 
jmestepAuthor Commented:
The ODBC data sources are OK. We are now getting similar messages from web server #1, where we never had the messages before. We have thousands of page requests that go thru OK.
0
 
jmestepAuthor Commented:
This ended up being a setting on a switch that the isp had done wrong.
Sorry, I can't figure out how to close this.
0
 
Computer101Commented:
PAQed with points refunded (300)

Computer101
EE Admin
0

Experts Exchange Solution brought to you by ConnectWise

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.