• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3483
  • Last Modified:

Exception: : [DBNETLIB][ConnectionRead (recv()).]General network error. Check your network documentation.

Moved my app from a windows 2003 server to windows 2008.  App gets the following exception when running off of the timer event.  Ran fine most of the day, then started failing.

: [DBNETLIB][ConnectionRead (recv()).]General network error. Check your network documentation.

All the posts I see are SQL Server oriented.  I am getting this error in my asp.net app,(possible when doing a database operation).
0
No1Coder
Asked:
No1Coder
  • 16
  • 16
1 Solution
 
13598Commented:
'All the posts I see are SQL Server oriented' => If not SQL what is your database engine?
0
 
No1CoderAuthor Commented:
I am using sql server, but the problem appears to be related to the Web server.  When I switch from a windows 2008 server to a windows 2003 server it works fine.  Must be something in the config of my web server?
0
 
13598Commented:
Do you have  Microsoft 'SynAttackProtect' feature enabled on the SQL server?
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
No1CoderAuthor Commented:
I don't see this in the serve feature summary wiindow.  I have no recolection of turning this on.
0
 
13598Commented:
where was your web server before? You say it was Windows Server 2003 but was it in the same server as the sql server and now you separated them or was it always on its own?
0
 
No1CoderAuthor Commented:
Oops - Sorry.  I missed teh SQL sever thing.  How would I tell?

Also, this runs find from one web server, but not another.  Woulddn't seem to be a sql server option causing this.
0
 
No1CoderAuthor Commented:
I have two web servers in a NLB cluster.  Currently, I trun one on, and the other off.  When I enable the 2008 server, I have this problem.  When I enable the 2003 server, works fine.
0
 
13598Commented:
Look for related entries in your sql server ERRORLOG and see if we get a little more detail on the error.
Also check your protocols do you have tcp/ip and named pipes enabled. also make sure that both local and remote connection are enabled.
0
 
No1CoderAuthor Commented:
I have shared memory, names pipes, and tcp enabled.

I looked through SQL Server, Agent, and "windows NT:" log from the console.  (it probably failed 100 times yesterday) and I don't see eny messages pertaining to this.
0
 
13598Commented:
In that order? Did you try TCP/IP and  named pipes?
0
 
13598Commented:
What sql do you have? 2005, 2008,...??
0
 
13598Commented:
Is there a reason to have shared memory enabled? If not I would try to disable it from both servers (sql and web).
0
 
13598Commented:
It could be due to an mdac mismatch.
Could you run the component checker on your sql and web server 2008 to see?
And maybe even on both of your web servers to see any differences?
http://support.microsoft.com/kb/307255/ 
0
 
No1CoderAuthor Commented:
sql 2005.  No reason to have shared memory on.  Must be default.  I don;t really want to change anything unless I have a good reason to.

The web server is on a different physical box, so shared memory is not in play.
0
 
No1CoderAuthor Commented:
Not familiar with mdac mismatch.  More details please.
0
 
13598Commented:
Maybe this will help=>
http://en.wikipedia.org/wiki/Microsoft_Data_Access_Components
Do you have mdac 2.8 on your new web server and lower version perhaps on your sql server?
What about your old web server, what mdac version is there?
0
 
13598Commented:
0
 
No1CoderAuthor Commented:
I really appreaciate your assistance...

Its there an easy way to determine if the version match?  I really don;t want to install stuff on eiother server (these are production boxes).  Also, both are running .net version 2, and version 4.  Those verstions are the same.  WOuldn't the data access components come from .net?  This is an asp.net application.
0
 
13598Commented:
The error you are getting is more than likely mdac related. I do understand your hesitation about installing/uninstalling in production servers and I do agree with it.
I would start by comparing the mdac versions on your web servers since one of them works and the other doesn't. Now if I understand it correctly you only use one or the other so if one was to let's say go down you would still be 'live' with the other one, correct?
Start by comparing mdac versions on your web servers 2003 & 2008.
Are you saying you don't want to install the com checker to check versions or by installing you are referring to mdac? If you don't want to install the component checker then I can check the instructions to look for the registry keys but going about it that way may miss some dependencies.  You may already have the com checker installed on your 2008 machine.
 
0
 
13598Commented:
Another thing to do is to check the SQL client configuration on your new web server. Is it set correctly? Is it using TCP/IP?
0
 
No1CoderAuthor Commented:
What you said about the servers is correct.  Using NLB, I turn one on, and the other off.

BTW: The 2008 server that was failing (I had it in production all day yesterday) only failed in one particular way...When runing a task off of the timer thread.  Everything else seemed to work okay.

Please provide instructions for getting the versions without installing the com checker.

How would I tell if comcheck is already installed.  I tried running from a command window but it was not found.
0
 
13598Commented:
Could you look at this registry value in your SQL server and let me know what it is?

key:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\SynAttackProtect
 
0
 
13598Commented:
Did you  check the SQL client configuration on your new web server?
What do you have in the General and Alias tabs?
0
 
13598Commented:
Is your connection for the task using ODBC?
0
 
No1CoderAuthor Commented:
On sql server, there is no key for SynAttackProtect

There is no sql client installed on the web server.  The application uses OleDB for database connections.  I know, it could use SQLDB, but this is a carrover from when I suported Oracle.

ASP.NET app.

Not using ODBC
0
 
13598Commented:
On your web server what happens if you go to run and type cliconfg    (NOTICE no i only confg NOT config)?
0
 
No1CoderAuthor Commented:
I ran this on both working and failing web servers.  results seem to eb teh same.

Nothing enabled on general tab.
Noting on alias tab
Libraries same on both boxes
0
 
No1CoderAuthor Commented:
I appreciate your assistance - this is still an issue for me.  Any more ideas?
0
 
No1CoderAuthor Commented:
MS thinks its a sp issue.  Am workig wthrough it.  Willl update once I have a solution.
0
 
No1CoderAuthor Commented:
I am wqorking with microsoft on this issue.  I will update the case once a resolution is found.
0
 
Amandeep Singh BhullarCommented:
do close this question, once you are done.
0
 
No1CoderAuthor Commented:
The cisco ASA5500 firewall that i am using was causing the problem.  I turned off "proxy arp" and the prolem is solved.  The ASA was responding to an arp request from the w2008 server.  According to ms, it didn't fail in w2003 because of a change to the protocol stack.
0
 
No1CoderAuthor Commented:
problem solved
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 16
  • 16
Tackle projects and never again get stuck behind a technical roadblock.
Join Now