asked on

Time out issue

I have two different machines that are querying a backend database from Excel in EXACTLY the same way and on the same network.

One times out and the other doesn't.

Looking for suggestions on things to check.

ASKER CERTIFIED SOLUTION

eli411

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

patriotpacer

ASKER

>>set the connection string timeout in config file!

Changing the query is not an option at this point.

patriotpacer

ASKER

It's really 5 machines with NO issues and just one machine with an issue.

Wasn't sure if there's anything on the machine that doesn't work that could be checked? Network card, etc...?

eli411

Most likely is inside the coding with connection string opened. The SQL Server automatically drop the connection to conserve resource and caused timeout. I used to manage web servers and database servers and coding and had same issues. I finally found that the issue was in my coding one day because I forget to close the connection in my coding.

It is going to be painful to find that line of code or you can extending the SQL Server connection timeout setting!

patriotpacer

ASKER

thx, Eli.

I agree the timeout issue can be extended. But adjusting the code that connects is the last option at this point.

I want to know why 5 computers have no issues and only 1 computer has an issue. All on the same network. Again, only ONE will timeout. The other 5 have absolutely ZERO issue running the EXACT same query and the exact same time.

patriotpacer

ASKER

don't have time to leave this open.

Might have to go down extending the time out route.