June 2, 2009 at 10:55 am
Hello there,
My question is, does SQL and/or ODBC have a long timeout value?
We have an application running on a MS SQL database connected by ODBC on Windows XP machines and were plagued by 08s01 communication link failure errors. They always occurred between 5:30 and 6:45 in the evening and we completely upgraded the network to remove potential network issues. Some users continued to get the error, and always in the late afternoon/early evening, and so we asked them to reboot their machines at lunchtime. Hey presto, the errors no longer happen. Accordingly I am wondering if there is a setting to kick out clients after they have been connected for eight or nine hours or so? I don't believe it to be inactivity because the users are reporting the error whilst working on the app, and the error is consistently occurrinig at a set number of hours after they have first logged into the app.
Am I barking up the wrong tree here or is there a hidden setting somewhere?
Any help would be greatly appreciated.
Thanks,
Pete.
July 22, 2009 at 2:01 am
Hello again,
Further to my last post, the application involved was updated by the programmers, and the connection errors have magically disappeared. They have, of course, denied changing anything that might have had an impact, and still maintain it's a network thing.
There's another update coming along in a week or so (there's updates more than monthly), and so we'll see if the next version breaks it again or not.
Thanks for anyone who looked at this - if anything further exciting happens on it, I'll let you know.
Pete.
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply