December 13, 2007 at 3:10 pm
We have recently migrated our database to a brand new server and upgraded SQL to 2005 64bit. The server is running Windows Server 2K3 Enterprise Edition SP2. The problem we are having is that the two programs we use through the day Macola our ERP system and Goldmine our CMS are both throwing general network errors throughout the day. I have been troubleshooting this problem for the past two weeks and still can't figure it out.
A list of things we have tried include switching NICs on the server, replacing all cabling between the server and the main switch closet (which was working fine prior to the upgrade but to be thorough we replaced anyways.).
I have also installed the SQL connectivity tools on the workstations using the SQL 2000 cd not the 2005 because the 2005 that we have is for 64bit OS only. Maybe an issue?
We are still getting connection errors with both Macola and Goldmine and all other applications touching our SQL server. I'm leaning more and more towards a SQL configuration problem after doing all of the checking on the physical hardware / cabling.
The complete error from Macola:
MSL Technical Error Info:
An error occured in MacMSS.dll (ver. 76.400.00.6)
DB Provider Error:
COM Error: Error
Code = 0x80004005
Code meaning = Unspecified error
Source = Microsoft OLE DB Provider for SQL Server
Description = [DBNETLIB][ConnectionWrite (send()).]General network error. Check your network documentation.
Op : DA, fhReadRandomLock
Table or Script: [MERCURY].[DATA].DBO.[OEORDHDR_SQL]
I would love to hear any other suggestions or things I can try. I've got Network tracer running and SQL Profiler running all day so I'll have a full days worth of monitoring I can review although I'm not positive what I should be looking for in the logs.
December 13, 2007 at 4:15 pm
Are your NICs set to auto-negotiate or set to a fixed speed/duplex? I've had problems with auto-negotiate in the past.
MARCUS. Why dost thou laugh? It fits not with this hour.
TITUS. Why, I have not another tear to shed;
--Titus Andronicus, William Shakespeare
December 14, 2007 at 7:09 am
It is currently set to Auto Negotiate. I was going to set the speed but there doesn't appear to be a gigabit option in the dropdown list. The only options I have listed are:
10 Mb Full
10 Mb Half
100 Mb Full
100 Mb Half
Auto
If it is a gigabit card shouldn't I also see 1000 Mb Full / Half?
December 16, 2007 at 1:35 pm
Some earlier Gb cards didn't have the option to set Gb speed/duplex directly, you had to set it to auto-neg. Not sure if that can be fixed by an updated driver or not.
That being the case, leave it at auto-neg (assuming the other end is supporting Gb as well.....).
Are there any network-related errors appearing on the SQL Servers? Are there any application servers involved or are all the apps in question being run from the workstations?
Check your OEM network drivers - I recently had an issue with Windows 2003 SP2 and a network teaming driver which caused the server to BSOD about once a week. The OEM released a new driver which cleared things up.
MARCUS. Why dost thou laugh? It fits not with this hour.
TITUS. Why, I have not another tear to shed;
--Titus Andronicus, William Shakespeare
October 8, 2008 at 6:13 am
Was a resolution to this problem ever found? We too are experiencing the same problem. Migrated to SQL Server 2005, app resides in 2000 SP4 environment. Now, intermittently, we receive the following:
Database server error number: '11', server: '01000[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionWrite (send()). ** AND ** [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error. Check your network documentation.', severity: '-1', message: 'SQL call failed.'
Any thoughts?
October 9, 2008 at 7:42 am
As Scott mentioned, I would suggest seeking the latest drivers from your NIC vendor to ensure that you're up to the latest revs. Additionally, I would check the following KB article (http://support.microsoft.com/kb/942861) to determine if you have the NIC mentioned in the article (Broadcom 5708 chipset).
Jonathan
December 16, 2009 at 8:06 am
We too have been getting the same MACMSL.dll errors. We are running MS Server 2003 64 bit with SQL2005 and Macola. It's a new server with dual Quad Core CPUs and 16GB of RAM.
Some of our users get the disconnect everyday between 4:00 and 4:30 pm. No network backups or anything else is running. We've swapped NICs, cables and switch ports. Fopr some people the problem goes away after a few weeks. For others is never goes away and for still others, they never have the problem. We stay current with all MS server and desktop patches.
February 23, 2010 at 1:15 am
I have had the same issue with HP BL680c G5's.
HP have come back and said that the onboard nics NC326i are not allowed to be set to full/1000 this is at hardware/manufacturer level and have now recomended I open a case with Microsoft as they cannot do anything for me.
On other SQL blades I am not using the nc326i but the NC373i these are allowed to be set even though it is 2.5/full?
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply