Jump to content

Recommended Posts

Posted

Our Library system has taken to throwing errors after a few minutes of inactivity, saying it has lost database connectivity. After some testing, the suppliers have said they think it is a Windows 7 issue (although they are sometimes quick to blame local problems in error). What we know is this:

 

* logged in as normal user, the connection drops

* logged in as a user with local admin, it doesn't

* logged in as normal user but running the application in "run as administrator" mode, it drops

* we've tried three computers, all are affected

* running the application on the server itself is fine

* the supplier cannot replicate the problem in their test environment

* this problem is relatively recent, it used to work fine

* a different client-server application on the same server doesn't exhibit problems

 

So, I can certainly see why they're suspecting Windows issues, but... I'm not aware of anything I've enabled which would keep persistent server connections for one user but not another. So, my question is this: where should I look for this setting, and what else could be causing this?

Posted
Although it's not likely something that would have set itself, have you checked the properties on the network card? Wondering if the "allow computer to turn off this device to save power" thing is activated.
Posted (edited)
Although it's not likely something that would have set itself, have you checked the properties on the network card? Wondering if the "allow computer to turn off this device to save power" thing is activated.

 

No, but... that setting would apply to a local admin user too, wouldn't it?

 

To clarify, I mean proper AD user who also is a member of a group to give them local admin rights, not the native .\administrator account.

Edited by enjay
Posted
No, but... that setting would apply to a local admin user too, wouldn't it?

 

To clarify, I mean proper AD user who also is a member of a group to give them local admin rights, not the native .\administrator account.

 

Good point; you'd think so. Only a couple of minutes to check, though!

Posted
So, the setting was enabled but disabling it didn't help. Also, the database drops out even if you continue using the computer in a different application.
Posted
What kind of database is it? There might be a setting to kick idle connections in MS SQL (or whatever it is), as to why it used to work fine.. maybe the default changed in an update? No idea.
Posted
What kind of database is it? There might be a setting to kick idle connections in MS SQL (or whatever it is), as to why it used to work fine.. maybe the default changed in an update? No idea.

 

It is a Firebird database. We've tried updating to the latest version of Firebird, but that didn't help. Also, again anything in the application or database which is set to kick idle connections would surely kick all users out. This really does seem to be dependent on the user who is logged in to the PC.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...