[Microsoft][ODBC SQL Server Driver]Timeout expired

Our IT department made an application that connects to my SQL server. It updates the record in the SQL server and then updates a corresponding record in another server.

It was working great until earlier in the afternoon. Now, when it tries to update the record, it produces that error message.

I've done everything I could think of and IT has helped me as far as their willing. I can't think of anything else at the moment. I checked the ODBC connections to make sure they were working. I checked the user mapping and everything. I even made a quick a simple app to update one of those records, bypassing ODBC altogether and it works just fine.

I've Googled this issue and their seems to be a lot of people who have this problem, but no one with a concrete solution.

Does anyone have any ideas on what I could do to maybe fix this?

Why are you using ODBC as a driver to talk to MS SQL server?

Show some code.

Quote:

---

Originally Posted by szlamany

Why are you using ODBC as a driver to talk to MS SQL server?

Show some code.

---

It's my IT department. They chose to do it this way and I don't have access to the code. I was hoping for some advice more related to systematic issues.

This is for two reasons. Like I just mentioned, I don't have access to the code and two, it's been working just fine. As far as I know, nothing's changed. Then all of a sudden, it stops working.

Sorry - I've got nothing to go on here.

ODBC is for connecting to ACCESS - so that's a bad idea.

I'm not sure how you could even google for the error in a meaningful fashion - you'll end up getting a lot of links to confused people that never resolved there problems...

Timeouts happen because something is taking longer than allowed - usually the default is 30 seconds. If it stopped today and it worked yesterday than you have reached some plateau in SQL that's now making it take longer that 30 seconds - maybe...

Do you have disk space issues? Is your log file too large? Is the table being inserted into fragmented because of constant inserts? Is the architecture of the table problematic?

Good luck!

Quote:

---

Originally Posted by szlamany

Sorry - I've got nothing to go on here.

ODBC is for connecting to ACCESS - so that's a bad idea.

I'm not sure how you could even google for the error in a meaningful fashion - you'll end up getting a lot of links to confused people that never resolved there problems...

Timeouts happen because something is taking longer than allowed - usually the default is 30 seconds. If it stopped today and it worked yesterday than you have reached some plateau in SQL that's now making it take longer that 30 seconds - maybe...

Do you have disk space issues? Is your log file too large? Is the table being inserted into fragmented because of constant inserts? Is the architecture of the table problematic?

Good luck!

---

I know we shouldn't be using ODBC. I explained that I had no control over that. I would never use it. But I did speak with my IT manager and he agrees with me on this, so hopefully he'll make the other guy change it.

I know what a timeout indicates. The problem isn't understanding what it means. The problem is trying to understand what could cause it to no longer connect.

No disk issues, no space issues, no fragmentation and I used DBCC on the database and tables. Found no problems.

This seems like one of those generic errors that could mean a million things. I knew coming here would be a long shot, but I've been working on this for hours, so I became a bit desperate.

Thanks for the help tough.

ODBC is not only for Access btw.An example of need is if you want to create a php forum to IIS with SQL.Are they using asp.net or they are using winforms?I'm asking because if they use asp.net then there is probably an IIS issue.

Quote:

---

Originally Posted by sapator

ODBC is not only for Access btw.An example of need is if you want to create a php forum to IIS with SQL.Are they using asp.net or they are using winforms?I'm asking because if they use asp.net then there is probably an IIS issue.

---

WinForms

Can't help then.Your company is doing some weird stuff over and over btw.