Access Violation; Stack Trace error

Access Violation; Stack Trace error

Normally when Access Violation happens, it might be caused by many factors and usually kills the client session.
For example, if another user is taking one payment from a Patient, and you are also trying to take a payment for the same patient - or you have two tabs open or a locked user session and don't notice, you will get the error:

If you have a look at both tabs, you'll see that there is a Receive Payments open in one, and the Patient in another. Is the same information open in both?


Also, you could look at the Active User Sessions on the Main menu to see if you have a locked session or an open session in the same function.You can kill any locked sessions if you can't see them on your screen.
If it isn't you, and if you have access to ALL user sessions you can search on the user name to see all open sessions to narrow down who is also in Payments.
Ask that User if they are entering a payment for the same client. You can kill their session if they say they aren't in that function.


These types of errors normally disappear as users exit functions.

Try it again. If you can't replicate it, all good.
If you can replicate after taking the steps above, please provide similar information including Steps Taken and let us know the USER initials, the Patient or Document Number and other relevant information so we can replicate it.