Hello,
A customer is experiencing a problem with remote users who print checks. I hope someone can point us toward a solution. The version is 7.0 FP1.
There is a home office that has no problems with checks, a New York office that has a problem about once per month, and a Chicago office that has a problem once or twice per week. When "the problem" occurs, the remote user prints checks, and the checks print fine. The AP Check Update screen never opens. There is no error. Sometimes the screen is frozen. Sometimes they have to disconnect in order to do anything more in SL. Approximately 4 out of 5 checks batches process fine in Chicago, which rules out access rights. It is the same person printing checks from the same remote workstation each time.
When the problem happens, the AP checks batch ends up with a V status, and temporary check records are left behind in the database.
The NY and Chicago offices connect to the server via a VPN and remote desktop connection. They have connected this way for a few years, and the problem started happening about 6 months ago, with increasing frequency. In each case, there is no error, and AP Check Update just doesn't open.
We don't think it's bandwidth - has happened during times of very low activity. They are all using the same set of databases.
What can we do to solve this?
Thanks!
Laura Barber
*This post is locked for comments