Hello:
We are on GP 2013 R2, with many international divisions.
Overseas and very early this morning Pacific Time, one of our users posted a batch that--monthly--takes only 2 - 3 minutes to post. Instead, her posting this batch took nearly 3 hours.
And, while the posting was happening, none of our overseas users could access or use GP. And, when our East Coast and Central US users reported for work, they could not access GP either.
After the posting process was finished, GP was available for use again and all was well.
Upon first hearing about this early in the morning, I created a new GP user ID for her. She was then able to post, without causing any issues. She did have trouble with one batch, but I advised her to review the edit list and if necessary post the transactions individually to see which one is the culprit or move the transactions to a new batch ID for posting.
Our SQL DBA who traced the GP freezing to this user's batch posting suggested, for the next time this happens, implementing a program called "auto cleanup" that would kick a user out of GP and allow for everyone to access GP.
This issue with not being able to access and use GP caused our overseas users to not be able to work and made them miss important deadlines.
Should this auto cleanup program be used? Has anyone ever heard of it?
If it should not be used, does anyone have any suggestions? We cannot have this happen, again.
Thanks!
John
*This post is locked for comments