Troubleshooting Steps for Crow Canyon Custom Actions

Applies to:

SharePoint On-Premises

Symptom 1

When a ‘Generate Document Action’ is being added to a Custom Action then a UI error message is received as shown below:

Cause

The above error message is received when the web application (Application Pool Account) account does not have farm admin permissions in the local environment.

Resolution

  1. Add application pool account to ‘Farm Administrators’ group.

a) Navigate to SharePoint Central Administration -> Security -> Users -> ‘Manage the farm administrators group’ as shown below:

b) Click ‘New’ -> ‘Add Users’ -> Add the web application account (Application Pool account) to this group.

c) Restart the SharePoint Server.

    If the issue persists after following the steps given in #1 above, then follow the steps given in #2 below.

    2. Grant full control permissions to everyone on “Avalon.Graphics” registry key and change impersonation settings in IIS and web.config file.

    a) Grant full control permissions to everyone on “Avalon.Graphics” registry key by following the below path:

    i. Open the ‘Run’ command -> Type ‘regedit’ -> Click ok to open ‘Registry Editor’.

    ii. Navigate to ‘HKEY_CURRENT_USER\Software\Microsoft\Avalon.Graphics’ -> Right-click the ‘Avalon.Graphics’ key -> Click ‘Permissions…’ from the menu as shown below:

    iii. Click “Add…” -> Grant “Full Control” permissions to “Everyone” as shown below:

    b) Change impersonation settings in IIS and ‘web.config’ file as below:

    i. Open ‘Internet Information Services (IIS) Manager’ -> Select the server from left-hand panel -> Expand ‘Sites’ -> Select the web application where the issue is experienced -> Click ‘Authentication’ under IIS section -> Disable ‘Anonymous Authentication’ and ‘ASP.NET Impersonation’ as shown below:

    To disable the authentication items, right-click the name and click ‘Disable’.

    Note: In some cases, disabling and then re-enabling the ‘Anonymous Authentication’ can also help in negating the error.

    ii. Edit ‘web.config’ file of the web application that has this issue in all SharePoint servers in the farm -> Change “aspnet.AllowAnonymousImpoersonation” value to “false” as shown below:

      Path of the ‘web.config’ file: C:\inetpub\wwwroot\wss\VirtualDirectories\<<portnumber>>\web.config