Liew,

No, I have not seen this before. I would still bump the timeout value so at least the program start without an error. Then you could tell the client if the application slows down that they need to restart the service.

You may also want to post a thread in the SQL category for advise on SQL tuning. You could also search the history. I found this thread on pooling that may be helpful:

http://www.levelextreme.com/wconnect/wc.dll?2,15,1054786

Kind Regards,

Mat


>Hi Mat, thanks for your advice. Supposely the SQL is just a very simple query and normally it just take about 2 seconds to login, I'm just curious why it will exceed the default timeout setting, and this only happens to 1 of my client and not others.
>
>The application was working fine in last two weeks, and the problem just started few days ago. Whenever this problem occurs, restarting the SQL service will resolve the problem, but it will just happen again after sometimes. I read some articles mentioned that the pooling does matter, any idea? Thanks.