Howdy All,
I do not know if this is a MS-SQL 2005 issue or a Dynamics Great Plains issue.
Back end: Windows 2003 Standard Edition SP1, SQL Server 2005 Standard Edition Runtime latest service packs installed.
End Users: 100% Windows XP, SP2, Great Plains 9.0 SP 2 (Exact Version is 9.00.0281).
We migrated from an older out of warranty machine in July and at the same time upgraded the back end to have SQL 2005 instead of SQL 2000.
Since the upgrade, if users are idle on their machines more than about 10 minutes, they get a message that their session has timed out and they have to close Great Plains and log back in. The problem with this is even if the user is not idle, just working on a long journal entry when they go to save the journal entry they get the time out message and lose that entry. Stepping away from the computer for several minutes, etc. All of my accounting users are complaining about this daily. I have checked every option I can find and can't find a time out setting.
All clients are using the SQL 2005 Native driver and a system DSN pointing to the DYNAMICS database on the backend server. I have verified that they have the latest available native driver.
Any leads and/or thoughts?
Mark L.
I do not know if this is a MS-SQL 2005 issue or a Dynamics Great Plains issue.
Back end: Windows 2003 Standard Edition SP1, SQL Server 2005 Standard Edition Runtime latest service packs installed.
End Users: 100% Windows XP, SP2, Great Plains 9.0 SP 2 (Exact Version is 9.00.0281).
We migrated from an older out of warranty machine in July and at the same time upgraded the back end to have SQL 2005 instead of SQL 2000.
Since the upgrade, if users are idle on their machines more than about 10 minutes, they get a message that their session has timed out and they have to close Great Plains and log back in. The problem with this is even if the user is not idle, just working on a long journal entry when they go to save the journal entry they get the time out message and lose that entry. Stepping away from the computer for several minutes, etc. All of my accounting users are complaining about this daily. I have checked every option I can find and can't find a time out setting.
All clients are using the SQL 2005 Native driver and a system DSN pointing to the DYNAMICS database on the backend server. I have verified that they have the latest available native driver.
Any leads and/or thoughts?
Mark L.