There are three possible ways to resolve this issue (for more recent versions of Windows Server, all three solutions may be necessary):
Solution 1 - Add the agent service's user to local administrators:
- Open the properties of the Nolio Agent service.
- Click the "Log On" tab.
- Verify the user account used to start the service.
- Add that user to the local Administrators group.
- Stop and restart the agent.
Solution 2 - Grant Local Security Policy permissions to the
domain user the action is impersonating:
- In Windows, open the Control Panel.
- Navigate to: System and Security -> Administrative Tools -> Local Security Policy.
- In Security Settings, go to: Local Policies -> User Rights Assignment.
- Add the user account to the policy "Replace a process level token privilege".
- Add the user account to the policy "Adjust memory quotas for a process".
Solution 3 - Verify agent folder permissions:
- Navigate to the agent installation directory. If the agent was installed in the default location, this will be "C:/.../ReleaseAutomationServer/NolioAgent/".
- Right-click the "NolioAgent" folder and select "Properties".
- Click the Security tab.
- Ensure the user that the action is impersonating has both read and write permissions to this directory.