This is caused by either:
The user not having full read/write permissions to the Service Manager library file.
The library file being set to read-only.
📌 **Note:** You may not have the permissions needed for the steps below. If not, ask your IT team to help.
Check library file permissions:
Open **C:\Program Files (x86)\Access Applications\Service Manager**.
Right-click the file **SME.lbr**.
Click **Properties**.
Click the **Security** tab.
Click **Edit**.
Modify the user's permissions (or a security group the user belongs to) to have **Full Control** of the file, or add the user and give them full control.
Click **Add**, search for the user, select **Full Control**, then click **OK**.
Click **OK** to apply the changes.
The above may also need to be applied to a second location. Check for another SME.lbr file at:
C:\Users\\AppData\Local\VirtualStore\Program Files (x86)\Access Applications\Service Manager
Replace with the username of the person unable to log in.
Follow the above steps again to check user permissions.
If the above is complete and the user still can't log in, the SME.lbr file may be set to read-only. Follow these steps to check and fix this:
Open **C:\Program Files (x86)\Access Applications\Service Manager**.
Right-click the file **SME.lbr**.
Click **Properties**.
Clear the **Read only** checkbox.
Click **OK** to save.
Repeat the read-only check for C:\Users\\AppData\Local\VirtualStore\Program Files (x86)\Access if needed. If nothing works, delete the SME.lbr file in that folder and run Service Manager again — this recreates the file and resolves the issue.