Visual Basic application return connection timed out

We are using SQL Server 2000 in my company. My software development team has developed an application.

We encouter problem whereby sometime all the clients' application return connection timed out. We have wireless client as well as wired client. But, the problem occurs the wired client also faced the same problem.

We checked the sqlserver task manager when the problem occured but found that CPU and RAM usage are normal. CPU is around 40% sometime. We also performed a check on network connectivity between the SQL Server and the wired client and it is very good.

We have been trying to check what went wrong but really get out of idea now after try for different methods.

THe database is only around 200mb and our server is pentium xeon 933MHz with 1Gb RAM. We do not think the hardware is the bottlenet but we couldn't find where the bottlenet is.

Hence, maybe any of you have any idea that we can look into the problem. I personally suspect the connection string for the application might need to change to fit the wireless enviroment as the connection can go off anytime.

Thank you so much



Answer this question

Visual Basic application return connection timed out

  • oshea00

    Hi cgraus,

    thanks for your prompt response.

    I suspect other wireless client might have dropped out and cause the sqlserver have too many lock and blocking. This is because we have almost 50 wireless clients uses the application to access the database besides those web application.

    if we can't change the connection string to stop the error, can we do something on application

    Is that true that the SQL server will remain the connection session even the physical connection has dropped It is kind of like DoS attack. I think I read an article somewhere in the Internet but I couldn't find it anymore.


  • btrabon

    I don't see how a client dropping out would cause a lock, in fact it would free a possible connection. Perhaps the connection pool needs to be made bigger

    I don't see why SQL Server would keep a connection open when it's been physically dropped. There is a lot of FUD on the web.



  • Padvit

    If the connection drops out, no change to your connection string will stop this error.



  • Visual Basic application return connection timed out