May 8, 2009 at 6:33 am
Hi All,
Yesterday we moved out of our 5 year old Server to a new powerful HP DL585 with 2 Quad Core CPU with 36 GIG RAM system. 26 GIG has been reserved for SQL Server. Everything is working fast but I am getting way too many General Network errors.
Please keep in mind that nothing was changed on the application layer. Only the Database server has been changed. We use both ASP and .NET. Mixed Authentication. I think I am missing some setting in the Database server. Either in the SQL Level or in the OS / Network level. Does anybody know what can be done regarding this?
Thanks
-Roy
May 8, 2009 at 7:46 am
Roy, can you post the exact error messages you are getting please.
May 8, 2009 at 7:52 am
[Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error. Check your network documentation.
Unfortunately this is a generic error that is thrown for quite some scenarios.
-Roy
May 8, 2009 at 7:55 am
Since you posted this in the 2000 forum I'm guessing this is a SQL 2000 db on the new server. Any chance you upgraded from Windows 2000 to 2003/08? If so you could be seeing some of the issues in the below blog posting.
http://blogs.msdn.com/sql_protocols/archive/2006/04/12/574608.aspx
-Luke.
May 8, 2009 at 8:05 am
Yes, it is SQL 2000. We had the same OS in the old server as well.
-Roy
May 8, 2009 at 8:10 am
I read that Blog post yesterday and interestingly that registry key is not there on our Server. Both the Old and the new server
-Roy
May 8, 2009 at 8:38 am
Roy, did that blog help?
Also, where are the errors occurring? First connection, randomly while people are working? Do you get any errors from the local connections like from Agent?
May 8, 2009 at 8:39 am
Hi Roy
Just to ensure, did you check:
* Network traffic?
* Network card vs. switch configuration (half/full duplex)?
Greets
Flo
May 8, 2009 at 8:41 am
Steve, there were some errors fro, the Agent as well with GNEs
Florian, The network card vs Switch with Half/duplex was checked. They match.
But when I do netstat -s
tcp statistics for ipv4 Failed Connection Attempts is pretty high
-Roy
May 8, 2009 at 8:54 am
Roy Ernest (5/8/2009)
Yes, it is SQL 2000. We had the same OS in the old server as well.
I stand corrected here, The SP level is high in the new server.
-Roy
May 8, 2009 at 9:01 am
Roy Ernest (5/8/2009)
[Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error. Check your network documentation.Unfortunately this is a generic error that is thrown for quite some scenarios.
Don't you love that error? Have you checked your "network documentation" to see if it helps? 🙂
The Redneck DBA
May 8, 2009 at 9:34 am
It almost sounds like a hardware issue with the new NIC.
May 8, 2009 at 9:53 am
Was it a restore or reinstall of software, the only reason I ask is something is nudging me to MDAC version imcompatibility. Dunno why, probably not and a long shot but it was tied to Service Packs.
Sorry I cannot help further :blush:
Far away is close at hand in the images of elsewhere.
Anon.
May 8, 2009 at 11:01 am
I'm going to ask a potentially stupid question: Have you tried swapping out the new server's network card?
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
May 8, 2009 at 11:12 am
And network cable.
I've been bitten by both of those, and usually they're something I think about after a few days of pulling my hair.
Viewing 15 posts - 1 through 15 (of 21 total)
You must be logged in to reply to this topic. Login to reply