January 18, 2008 at 11:06 am
hi do any one have solution for this error..
[Microsoft ODBC driver] Communication link failure
i am at client side.. domain controller (OS - server 2000) is on server and sql server 2000 enterprise edition (server 2003) is on another server.
my client pc is always getting disconnect due to this error..... i have installed MDAC 2.8 still i am not able to solve problem.... can any one help me......
January 18, 2008 at 11:48 am
Is this a intermittent error or always?
1)Check if the network connection is primestable
2)Check the integrity of your database. An integrity fault due corruption can cause an aborted connection.
More things to check.
3) The server is momentarely down
4) ..
January 18, 2008 at 9:11 pm
-this is not intermittent error.
1)Check if the network connection is primestable
yes... i have checked. i have look for long time on server. everything is ok. infact when i m getting disconnected with client, i have to restart the client computer and the connection gets eshtablished again...........
2)Check the integrity of your database. An integrity fault due corruption can cause an aborted connection.
-can you help me in this regards.... i am not sure what exactly should do for database intigity.
More things to check.
3) The server is momentarely down
-no, i never seen this problem..... server is running fine....
4) ..
January 18, 2008 at 9:13 pm
one more thing, i am running my own software on client and server.... db is attached to the server... and 5 clients are accessing that. and while running the programe, i am getting this error.. again and again....
January 19, 2008 at 3:10 am
infact when i m getting disconnected with client, i have to restart the client computer and the connection gets eshtablished again...........
That sounds fishy.
What method do you use when to connect to the server?
Windows authentication?
TCP/IP or named pipes?
Is there Active Directory / Novell involved?
Do you use connection pooling?
January 19, 2008 at 3:04 pm
What method do you use when to connect to the server?
its ODBC - connectivity from INI file. my application is developed in VB.
in INI file i have entered details of server, username,password,db name.... from vb code i am accessing that and through adodb i am opeing connection
Windows authentication?
no, its SQL Server authantication......username = sa
TCP/IP or named pipes?
in Client network utility - first is TCP/IP and second is named pipes
in server network utility - first is named pipes and second is TCP/IP
Is there Active Directory / Novell involved?
Active Directory is on main Server (Domain controller) with OS - windows Server 2000...Sql Server is on another server which is having windows server 2003 operating syatem
Do you use connection pooling?
i am really not aware with this.........
January 20, 2008 at 1:25 am
offtopic:
I recommend not to use the sa-account for software.
A. It is a well known superadministrator account.
Because of that:
*There exist alot of program's to crack passwords, having the account name helps.
*Sometimes sa doesn't even has a password, which is a free joyride:
I am no longer responsible of the server and its data, do as you please.
Known by the SQL-Slammer worm.
Determine if your application needs full-server control, or just the database, or just for installation.
If it needs full server contol, try to use another account with sysadmin rights.
on topic:
I did some searches on the net.
*there is a text-field, memofield involved
http://www.dbforums.com/t898053.html
http://www.15seconds.com/faq/ODBC/692.htm
*There are troubles with the connection timeout
http://support.microsoft.com/kb/128884
*A new feature of windows 2003: TCP chimney
http://www.forumtopics.com/busobj/viewtopic.php?p=456939
Connection pooling:
http://en.wikipedia.org/wiki/Connection_pool
Regular applications regulary connect/disconnect to the "other side".
Connection pooling helps keeping the OS at pace with the new connections creating, amongst other things.
March 10, 2008 at 10:13 pm
hi! Guys! check out this site from microsoft:
http://support.microsoft.com/kb/942861
i think it will help us a bit with the our problem. It tells something about the new feature in microsoft 2003 server: TCP Chimney Offload
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply