Hi Ronald Nissley it sounds like something has gone wrong with the User Authorizations in your ISAM database files.  For this to just happen though is exceptionally unusual.  Is it possible the query the user was running was a change to user permissions or security groups?  Have you tried scheduling a restart of the Application Server to see if it fixes it?  After this simple troubleshooting step I would check the Security Groups used previously still exist, check all Company Databases in Database Setup are linked to valid databases (this will break propagation) then re-propagate permissions across all databases.  Finally if that doesn't work, try going to each existing user, allocate them a different Security Group for each module, then re-allocate the previous correct Security Group for each module as this often fixes it.  I.e.:

1. Open Administrative Services -> Security Groups -> Check the Security Groups allocated to users previously still exist for each module.
2. Open Database Setup and double-click on each Company Database and click OK ensuring each screen closes without error.  Broken database connections will break the propagation of any permissions changes.
3. Again in Database Setup, double-click the System Database and click Propagate.
   1. Note if there was a broken database link in step 2, start by opening each company database and click Propagate then open the System Database last and click Propagate.
   2. 
4. *Wait while all Security Groups and User Authorizations are re-propagated across all company databases*
5. Check if the issue is still resolved.  If not...
6. Open Administrative Services -> User Authorizations -> select a broken user -> change their Security Group ID's for each module to something different then back to the original Group ID
7. Let us know how you go.

All the best...Tim

Propagating permissions for the System database resolved the problem. Thank you, Tim!

That's great news Ronald, thanks for the update.  Glad we could assist.