remote connection stops after a while [modified]
-
hi all does any one know or guess what happens to my application connection while dialing with sql server 2008 standard? in fact it works for a week and after that it stops establishing connection to server remotely 1) i can ping the server from the computer witch my application installed on 2) sql server service is running 3) only one instance is installed on the server computer (sql server 2008) 4) my application will works about a week and dialing with sql server remotely more than 10000 times per a week and suddenly it stops 5) it will be ok after restart computer witch my application installed on :doh: :wtf: :confused: :~ X| :suss: .....!!!!!??????
modified on Monday, February 28, 2011 7:55 AM
-
hi all does any one know or guess what happens to my application connection while dialing with sql server 2008 standard? in fact it works for a week and after that it stops establishing connection to server remotely 1) i can ping the server from the computer witch my application installed on 2) sql server service is running 3) only one instance is installed on the server computer (sql server 2008) 4) my application will works about a week and dialing with sql server remotely more than 10000 times per a week and suddenly it stops 5) it will be ok after restart computer witch my application installed on :doh: :wtf: :confused: :~ X| :suss: .....!!!!!??????
modified on Monday, February 28, 2011 7:55 AM
reza assar wrote:
in fact it works for a week and after that it stops establishing connection to server remotely
Did you mean that your database-server doesn't accept any new incoming connections after that week, or that it drops the current existing connection?
reza assar wrote:
my application will works about a week and dialing with sql server remotely more than 10000 times per a week and suddenly it stops
That's not much to go on; there's no known bugs in Sql Server that occur after a week. You could;
- Check the Windows EventLog (under Start, Configuration, Administrative Tools) for any errormessages relating to the database and/or the network
- Check your Global Exception Handler (you did implement one?) for relevant exceptions
- Add a lightweight trace to Sql Server - might give a clue on the offending Sql Statement and conditions under which this statement is run
- Did you install all service-packs? Updated Windows?
- Try to replicate it "at home" by pumping a lot of data to your development-server - see if you can reproduce the crash
The EventLog and the trace will be your best bets on hunting down the cause. Good luck :)
I are Troll :suss:
-
reza assar wrote:
in fact it works for a week and after that it stops establishing connection to server remotely
Did you mean that your database-server doesn't accept any new incoming connections after that week, or that it drops the current existing connection?
reza assar wrote:
my application will works about a week and dialing with sql server remotely more than 10000 times per a week and suddenly it stops
That's not much to go on; there's no known bugs in Sql Server that occur after a week. You could;
- Check the Windows EventLog (under Start, Configuration, Administrative Tools) for any errormessages relating to the database and/or the network
- Check your Global Exception Handler (you did implement one?) for relevant exceptions
- Add a lightweight trace to Sql Server - might give a clue on the offending Sql Statement and conditions under which this statement is run
- Did you install all service-packs? Updated Windows?
- Try to replicate it "at home" by pumping a lot of data to your development-server - see if you can reproduce the crash
The EventLog and the trace will be your best bets on hunting down the cause. Good luck :)
I are Troll :suss:
dear Eddy i am using exception handling the error is the same as when you can`t establish a connection. good suggestion about eventlog i completely forgot about this. by the way my application can`t establish a connection but meanwhile another applications "that developed by myself" can connect and dial with sql server remotely from other computers at the same time.
Eddy Vluggen wrote:
Did you mean that your database-server doesn't accept any new incoming connections after that week, or that it drops the current existing connection?
yes i think there is no any connection object in the pool " and database-server doesn't accept any new incoming connections" and it does not allow establish a new fresh connection but after restarting the client computer everything working ok!
-
dear Eddy i am using exception handling the error is the same as when you can`t establish a connection. good suggestion about eventlog i completely forgot about this. by the way my application can`t establish a connection but meanwhile another applications "that developed by myself" can connect and dial with sql server remotely from other computers at the same time.
Eddy Vluggen wrote:
Did you mean that your database-server doesn't accept any new incoming connections after that week, or that it drops the current existing connection?
yes i think there is no any connection object in the pool " and database-server doesn't accept any new incoming connections" and it does not allow establish a new fresh connection but after restarting the client computer everything working ok!
reza assar wrote:
yes i think there is no any connection object in the pool " and database-server doesn't accept any new incoming connections" and it does not allow establish a new fresh connection but after restarting the client computer everything working ok!
Sounds like you got some connections that don't get closed/disposed properly. Any code that could leak connections/readers?
I are Troll :suss:
-
reza assar wrote:
yes i think there is no any connection object in the pool " and database-server doesn't accept any new incoming connections" and it does not allow establish a new fresh connection but after restarting the client computer everything working ok!
Sounds like you got some connections that don't get closed/disposed properly. Any code that could leak connections/readers?
I are Troll :suss:
thanks Eddy yes maybe . i will check it and fix it (if there is any) and get the result back hear. any other suggestion?
-
thanks Eddy yes maybe . i will check it and fix it (if there is any) and get the result back hear. any other suggestion?
reza assar wrote:
any other suggestion?
It might speed up things if you search (Ctrl-F) the entire solution for "SqlConnection" and add a using-block to each instance found. That would, in theory, dispose of your connection once processing exits the defined scope, and thus, also close it.
I are Troll :suss: