Timeout expired
-
Hi I have written a project in C#.Net 2005 that is connected to SQL Server 2000. The SQL Server Engine is on a server and there are three clients connecting to this server. The application is running on clients. Each minute many requests such as select, insert and ... are sent to the server, through transactions. The default timeout of the SQL Server has not been changed. After 200 requests, for example (the number is random, sometimes more, sometimes less), an error occurs which is: "Timeout expired, the timeout period elapsed prior to the completion of the operation or the server is not responding" With no changes in the server name, firewall, network protocol or whatever, the next request after this error, will be sent correctly and the response will be got correctly. Can anyone help me to solve this problem? Thanks in advance
-
Hi I have written a project in C#.Net 2005 that is connected to SQL Server 2000. The SQL Server Engine is on a server and there are three clients connecting to this server. The application is running on clients. Each minute many requests such as select, insert and ... are sent to the server, through transactions. The default timeout of the SQL Server has not been changed. After 200 requests, for example (the number is random, sometimes more, sometimes less), an error occurs which is: "Timeout expired, the timeout period elapsed prior to the completion of the operation or the server is not responding" With no changes in the server name, firewall, network protocol or whatever, the next request after this error, will be sent correctly and the response will be got correctly. Can anyone help me to solve this problem? Thanks in advance
I Dont knoq much about MSSQL, i know more MySQL Do the uses have high response rate to each query? How many connection can connect to MSSQL simutanosly? Do you use Windows XP as OS? (Profesional version has a limit to 10 connections. there are some patches to increase that number)
-
Hi I have written a project in C#.Net 2005 that is connected to SQL Server 2000. The SQL Server Engine is on a server and there are three clients connecting to this server. The application is running on clients. Each minute many requests such as select, insert and ... are sent to the server, through transactions. The default timeout of the SQL Server has not been changed. After 200 requests, for example (the number is random, sometimes more, sometimes less), an error occurs which is: "Timeout expired, the timeout period elapsed prior to the completion of the operation or the server is not responding" With no changes in the server name, firewall, network protocol or whatever, the next request after this error, will be sent correctly and the response will be got correctly. Can anyone help me to solve this problem? Thanks in advance
Is your application connected to the database server on Local / remote environment?
Thanks Md. Marufuzzaman
Don't forget to click [Vote] / [Good Answer] on the post(s) that helped you. I will not say I have failed 1000 times; I will say that I have discovered 1000 ways that can cause failure – Thomas Edison.
-
Hi I have written a project in C#.Net 2005 that is connected to SQL Server 2000. The SQL Server Engine is on a server and there are three clients connecting to this server. The application is running on clients. Each minute many requests such as select, insert and ... are sent to the server, through transactions. The default timeout of the SQL Server has not been changed. After 200 requests, for example (the number is random, sometimes more, sometimes less), an error occurs which is: "Timeout expired, the timeout period elapsed prior to the completion of the operation or the server is not responding" With no changes in the server name, firewall, network protocol or whatever, the next request after this error, will be sent correctly and the response will be got correctly. Can anyone help me to solve this problem? Thanks in advance
Have you forgotten to close the DB connection when done, so the connection pool would get exhausted pretty soon? :)
Luc Pattyn
I only read code that is properly indented, and rendered in a non-proportional font; hint: use PRE tags in forum messages
Local announcement (Antwerp region): Lange Wapper? Neen!
-
Hi I have written a project in C#.Net 2005 that is connected to SQL Server 2000. The SQL Server Engine is on a server and there are three clients connecting to this server. The application is running on clients. Each minute many requests such as select, insert and ... are sent to the server, through transactions. The default timeout of the SQL Server has not been changed. After 200 requests, for example (the number is random, sometimes more, sometimes less), an error occurs which is: "Timeout expired, the timeout period elapsed prior to the completion of the operation or the server is not responding" With no changes in the server name, firewall, network protocol or whatever, the next request after this error, will be sent correctly and the response will be got correctly. Can anyone help me to solve this problem? Thanks in advance
Are you maing the HUGE mistake of opening a connection to the database in your app when it starts and never closing it until your app closes??
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008
But no longer in 2009...