Hi,
Recently got the below error while updating a record. It was surprising as we were just saving the record to which we had full access.
The good thing was that the log file had the correct message\information about the error
The error was because of access denied error while trying to write something to a text file inside plugin code.
Unhandled Exception: System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]: Access is denied.Detail:
<OrganizationServiceFault xmlns:i=”http://www.w3.org/2001/XMLSchema-instance” xmlns=”http://schemas.microsoft.com/xrm/2011/Contracts”> <ErrorCode>-2147187707</ErrorCode>
<ErrorDetails xmlns:d2p1=”http://schemas.datacontract.org/2004/07/System.Collections.Generic” />
<Message>Access is denied.</Message>
<Timestamp>2011-11-02T14:13:28.7922199Z</Timestamp>
<InnerFault i:nil=”true” />
<TraceText>
[testPlugin: testPlugin.Class1]
[7e507fe4-3605-e111-9e2c-00155d2a49c7: testPlugin.Class1: Update of lead]
</TraceText>
</OrganizationServiceFault>
Few days back also one friend of mine was getting the same issue, however it was while importing the solution. Not sure how it was fixed for them. It might be some custom code throwing exception.
Bye.
Nishant Rana's Weblog 
Hi,
I have the same issue. When I try to change the domain name or create a new user, I get the same unable to change domain logon name error.
That error started when I, accidently, moved two AD Groups from one domain to another. Then I moved them back. The groups were UserGroup {f7ed63a3-e7c6-4a07-9c8b-5369506bcdd5} e ReportingGroup {f7ed63a3-e7c6-4a07-9c8b-5369506bcdd5}.
Is there a workarround to solve this problem?
thank you very much,
Joao
LikeLike
So you say it was file access error, but not what you did to fix it?
LikeLike
I think you may actually need the System Administrator role in order to make changes to the logon name.
LikeLike
Hi,
I had the same problem, i solved it with the following:
Change “AutoGroupManagementoff” value set to 1 (false) in your registry (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM)
It fixed my issue, and the error is the same as above 🙂
LikeLike