The version of Access being used is installed at the Server level, therefore the version of Excel is also installed at the Server level. There is no communication with local user installations of Access or Excel. With this in mind, we looked at the elements of server permissions.
1.) Active Directory: Is the user in Active Directory with proper permissions
2.) With user in Active Directory and having proper missions... Identify where permissions are stored for each user (Originally assumed they are stored in group policy -- not true) the permissions are stored in the user folder.
3) Does the user have a local user folder? If no, then rebuild the user profile and a new folder will be built as the user logs in for the first time. Requires
-deleting user from Active Directory,
-forced Active directory cleanup, and
-adding the user to Active Directory, and logging in as the user.
Once completed the RDP session now has the proper permission to use the full access of the Server, and all software on the server as permissions allow.
Why does this happen? Unsure as to the reason, however, we can speculate that a windows update caused an issue, or the local Windows Server profile for the user became corrupted.