Hello Harry and Sarah,
Thank you for posting to Community.
The error message itself states that the Unity Client is attempting to access a registry location that it does not have access to. Usually this means that the Identity Impersonation account or the account running the Application Pool that Unity Client is using does not have proper rights to the registry location. Something like Process Monitor (procmon.exe) can be used to determine which registry location we are being denied access to. If this was the case, I would expect that any Unity Client connecting through that particular Application Pool would be experiencing the issue.
If it is only happening for a specific user then it is possible there might be an issue with the User's profile. It would also be a good idea to verify if this is specific to only one machine (if occurs to any user logged into that machine but not to the same user on a different machine). If it is only occurring on one workstation, I would recommend comparing the affected machine to a non-affected machine to see if possibly something is missing (a pre-req maybe) on the affected machine or possibly something extra being installed that is not on the non-affected machine.
Your First Line of Support can help you with troubleshooting further if you get to a point where you don't know where to go from here.
Thanks.
Jonathan Finney
Team Leader
Hyland Software Technical Support Department
