Great Plains Error Message
-
Great Plains Error Message
Posted by Deana Davis on March 21, 2017 at 2:07 pm-
HI,
I have a number of users that keep getting the error message attached and then their session boots them out but they can go log back in. Any ideas why?
——————————
Deana Davis
Atlantic Corporation Limited
Halifax
—————————— -
Steve Burney
MemberMarch 21, 2017 at 3:27 PM
Hi Deana,
We have seen this message occur when the remote server connection for the user becomes unattached.
Once they log back in then they are good to go.
Check your remote server activity and see if your IT group can help eliminate this challenge.
Steve——————————
Steve Burney
Senior Financial Systems Administrator
Correct Care Solutions
Nashville, TN United States
sburney@correctcaresolutions.com
615-312-7272
Twitter @SteveBurney
——————————
——————————————- -
Hi Deana
Do you have a addon products or external processes which could remove records from the ACTIVITY SQL table?
For example: something that is trying to remove inactive sessions?
Or are users kicking themselves out by starting a second session and deleting their activity record while they were already logged in.
The message you are receiving is caused by the record in the Activity table either being removed or that it exists but the login date and time are different from the original values for the session. If true, the session will exit with the message you are seeing.
David
——————————
David Musgrave MVP, GPUG All-StarManaging Director
Winthrop Development ConsultantsPerth, Western Australia
http://www.winthropdc.com
——————————
——————————————- -
According to Dave’s description above, it could also be a problem with time synchronization. If you are using a remote server for access such as Citrix, etc. it can sometimes be challenging to keep both servers’ system times close enough to avoid this error. I would check to make sure the Windows Time Service is running and pointed to a valid national time service (and make sure it is the same one for all your servers).
Additionally, I would check the time zones on all your servers. The Daylight Savings change occurred recently. If one of your servers updated and the other didn’t it could easily lead to the problem you are seeing.
——————————
Blair Christensen
Database Administrator
Oppenheimer Companies, Inc.
Boise ID
——————————
——————————————- -
Lou Spevack
MemberMarch 23, 2017 at 10:32 AM
I have also seen instances where maxing out on SQL Server licenses has been a factor. But most of the time I have found that lost network connections to the SQL Server have been the culprit.——————————
Lou Spevack
Systems Accountant | Dynamics Credentialed Professional
American Council on Education
Washington DC
——————————
——————————————-
Deana Davis replied 6 years, 6 months ago 1 Member · 0 Replies -
-
0 Replies
Sorry, there were no replies found.