Adx Plugin Permissions error following upgrade to CRM 2016 on premis

(0) Share

Report

Posted on by Community Member

Hi,

I'd appreciate any help on a problem we've having with an Adx Studio plugin following a recent upgrade to CRM 2016 8.2 from CRM 2015. The system fails on the creation of a new Service Request giving the following error;

<ErrorDetails xmlns:d2p1="schemas.datacontract.org/.../System.Collections.Generic" />
<Message>Unexpected exception from plug-in (Execute): Adxstudio.Xrm.Plugins.ServiceRequest.UpdateServiceRequestPlugin: System.Security.SecurityException: Request for the permission of type 'System.Security.Permissions.SecurityPermission, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.</Message>

The system creates the service request but fails when trying to update the service request number on the newly created record.

If anyone else has encountered this issue, I'd appreciate any suggestions on how to resolve it.

Many thanks

*This post is locked for comments

I have the same question (0)

All responses (3)

Answers (0)

Arpit Shrivastava 7,518 User Group Leader on at

Like (0)

Report

Hi Tim,

Did you recently make any changes in Web Notification URLs (Settings > Web Notification URL). If yes, then you need to disable and then enable the AdxStudio plugins. This issue might be due to this.

If found useful, please mark the answer as verified.

Cheers
Arpit
https://arpitmscrmhunt.blogspot.com

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi,

Thanks for taking the time to reply. The odd thing is when we disabled the plugin we were able to start creating service requests again. Re-enabling the plugin and the problem re-appeared.

Was this reply helpful? Yes No
Suggested answer

Arpit Shrivastava 7,518 User Group Leader on at

Like (0)

Report

Hey Tim,

Seems, there is an issue in UpdateServiceRequestPlugin plugin.

Could you please check, in which User Context this plugin is running (highlighted below)? If it is set to 'Calling User', then change it's value to 'System Administrator' or any user who is having Admin access and try.

Hope it helps.

If found useful, please mark the answer as verified.

Cheers
Arpit
https://arpitmscrmhunt.blogspot.com

Was this reply helpful? Yes No