Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

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

Posted on 2006-10-26
5
Medium Priority
?
649 Views
Last Modified: 2012-08-14
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)

0
Comment
Question by:jmestep
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
5 Comments
 
LVL 10

Expert Comment

by:AaronAbend
ID: 17816513
It looks like a client process is making a sql request via  odbc to a nonexistent database. check your odbc data sources
0
 

Author Comment

by:jmestep
ID: 17822699
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
 

Author Comment

by:jmestep
ID: 17997138
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
 
LVL 1

Accepted Solution

by:
Computer101 earned 0 total points
ID: 18189484
PAQed with points refunded (300)

Computer101
EE Admin
0

Featured Post

How Blockchain Is Impacting Every Industry

Blockchain expert Alex Tapscott talks to Acronis VP Frank Jablonski about this revolutionary technology and how it's making inroads into other industries and facets of everyday life.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Windocks is an independent port of Docker's open source to Windows.   This article introduces the use of SQL Server in containers, with integrated support of SQL Server database cloning.
An alternative to the "For XML" way of pivoting and concatenating result sets into strings, and an easy introduction to "common table expressions" (CTEs). Being someone who is always looking for alternatives to "work your data", I came across this …
This video shows, step by step, how to configure Oracle Heterogeneous Services via the Generic Gateway Agent in order to make a connection from an Oracle session and access a remote SQL Server database table.
Using examples as well as descriptions, and references to Books Online, show the different Recovery Models available in SQL Server and explain, as well as show how full, differential and transaction log backups are performed

721 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question