@BethBowers we ran into this a couple weeks ago. Our customer was setting up a new remote server for some of their users and while they were testing it, anyone who left their system idle for awhile would get that error. We checked the DEP settings and changed the old opportunistic locking setting with no luck, Eventually, Sage support had us set the shortcut to run as administrator and we made a registry change to one of the keys. It was somewhere like Local_Machine->Software->Sage . I'm trying to get the specifics from our help desk person who actually handled the issue.