The list of workflow actions on the server references an assembly that does not exist

In this post, we will be fixing “The list of workflow actions on the server references an assembly that does not exist” error that you may face when creating a new workflow using SharePoint Designer 2013.

You might also like to read Else Branch Disabled SharePoint Designer 2013

---

The list of workflow actions on the server references an assembly that does not exist

When I tried to create a SharePoint 2010 workflows via SharePoint Designer 2013, I got the below error

The list of workflow actions on the server references an assembly that does not exist. Some actions will not be available. The assembly strong name is Microsoft.SharePoint.WorkflowActions, Contact your server administrator for more information.

---

Cause

This “The list of workflow actions on the server references an assembly that does not exist” error usually occurs in case of

• The Server/PC does not have enough memory,
• ShareCache issue,
• In some cases, This error comes up if the current account doesn’t have local privileges.
• “WSS.Actions” file contains a reference to a custom action.

---

Solution

The Server/PC does not have enough memory

This error may occur if the system does not have enough memory,

• Try to close some programs to free some memory space.
• If you are working on VM, you will need to check its memory allocation.
  • if the memory is less than 6 GB, try to scale it up.

---

Clear SharePoint Designer Cache 

Try to clear the SharePoint Designer Cache of the following folders

• %USERPROFILE%\AppData\Local\Microsoft\WebsiteCache
• %USERPROFILE%\AppData\Roaming\Microsoft\SharePoint Designer\ProxyAssemblyCache
• %USERPROFILE%\AppData\Roaming\Microsoft\Web Server Extensions\Cache

Restart the SharePoint Designer

---

The current account doesn’t have local privileges.

If you are working on the Server, try to add the current user to Local Administrator Group.

---

“WSS.Actions” file contains a reference to a custom action.

If the problem still exists that means the Workflow actions has been extended with a custom action that developed in Visual Studio, These custom actions are loaded when your workstation reads the WSS.ACTIONS file on the server.

So to overcome this issue, try to delete “WSS.Actions” file as the following:

• Go to The file location in the 14/15 hive under Template\1033\workflow.
• Take a “WSS.Actions” file backup then remove it.

• Restart SharePoint Designer that should be working properly now.

---

Applies To

• SharePoint.
• SharePoint Designer 2013.
• SharePoint Designer 2010.

See Also

• SharePoint Workflow App Step disabled.
• Missing SharePoint 2013 Workflow – Project Server in SharePoint Designer.
• SharePoint Designer workflow Access denied