SetAclPermissions S...
Clear all

SetAclPermissions Server was unable to process request

6 Posts
6 Users
0 Reactions
Posts: 95
Topic starter
Trusted Member
Joined: 6 years ago

Dont know if the error is the same as some other here, thats why open a new post.

Can anyone help me to fix it ?

Server was unable to process request. ---> This access control list is not in canonical form and therefore cannot be modified.
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) 
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) 
at SolidCP.EnterpriseServer.OrganizationController.CreateOrganization(Int32 packageId, String organizationId, String organizationName, String domainName)

5 Replies
Posts: 1964
Noble Member
Joined: 9 years ago


The 1.4.4 release should of addressed this issue for everyone which does not have advanced dsHeuristics applied.

If your still experiencing the issue please check if you have any Deny rules on the root of the domain. if “Exchange Trusted Subsystem” has a deny rule there please remove it.

(We are working to automate the pernament fix for people with advanced dsheuristics aswell, which will be released as a seperated patch, meanwhile this manual change should work).



2 Replies
Joined: 2 years ago

New Member
Posts: 1

@m-tiggelaar Hey Marco, was there ever a patch released for this? We have dsHeuristics applied and we're attempting to deploy v1.4.8 but running into problems where the "Exchange Trusted Subsystem" deny permission exists- but we're not in a position to remove the permission. Was there another way around this?

Appreciate any assistance- Thank you,


Joined: 9 years ago

Noble Member
Posts: 1456

@r0gu At the moment there is no work around released and removing the permission is the best method to fix this issue.

Posts: 4
New Member
Joined: 7 years ago

Hi, I had the same issue today in version 1.4.7.

After removing a "Deny" at root level for Exchange Trusted Subsystem" as you mention, it worked.

best regards,


Posts: 9
Active Member
Joined: 8 years ago

Hi, With version 1.4.7 , After removing a "Deny" at root level for Exchange Trusted Subsystem" as Marco mention, it worked for me as well ..

Thanks for the tip Marco..

best regards,