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

    Question

  • hi,

    I have a query. I tried creating a workflow using the Microsoft Sharepoint Designer. But when i click on New - Workflows, its showing the following 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"

    Does any one came accross these sort of issues?

    Plz help me..... Thx in advance

    Regards
    Abul
    • Edited by Mike Walsh FIN Monday, March 15, 2010 7:02 AM overdid the "
    • Moved by Mike Walsh FIN Monday, March 15, 2010 7:03 AM workflow questions go to the workflow forum (From:SharePoint - Development and Programming (pre-SharePoint 2010))
    Sunday, March 14, 2010 7:07 PM

Answers

  • Normally you would see that error because someone has extended the Workflow actions available in SPD with a custom action developed in Visual Studio.  These custom actions are loaded when your workstation reads the WSS.ACTIONS file on the server.  The file is located in the 12 hive under Template\1033\workflow.  Your WSS.Actions file contains a reference to a custom action .dll which is not available on the server.
    Paul Stork SharePoint Server MVP
    Monday, March 15, 2010 12:07 PM

All replies

  • Normally you would see that error because someone has extended the Workflow actions available in SPD with a custom action developed in Visual Studio.  These custom actions are loaded when your workstation reads the WSS.ACTIONS file on the server.  The file is located in the 12 hive under Template\1033\workflow.  Your WSS.Actions file contains a reference to a custom action .dll which is not available on the server.
    Paul Stork SharePoint Server MVP
    Monday, March 15, 2010 12:07 PM
  • Normally you would see that error because someone has extended the Workflow actions available in SPD with a custom action developed in Visual Studio. 

    I am having this same problem, being the person that created the workflow and dropped it out in the c:\windows\assembly folder on the server, updated the web.config and created a new .ACTIONS file with my updated action in it.

    I swear I got this to work once, using all the same settings, correct token, all that.  I was originally having problems with the DLL reporting a generic 'object reference not set' to the workflow.  I've made changes to the DLL, uninstalled it and re-copied it out to the assembly and restarted everything, and it is still coming up with this error.

    Is there anything else I can look at to get this DLL registered properly so I have access to me new workflow step?


    • Edited by Mike Walsh FIN Saturday, July 16, 2011 7:12 AM full quote wastes screen space - don't use it
    Monday, April 26, 2010 4:09 PM
  • When you create a custom workflow activity you should create a separate ACTIONS file.  Editing the WSS.ACTIONS file is trouble.

    Generally the message "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 ..." occurs because the ACTIONS file doesn't match the assembly it references. 

    If you have verified that the assembly strong name is correct, verify that the ACTIONS file parameters match the assembly's activity properties.  Be sure to check the "DependencyProperty.Register" methods too.

    Monday, September 13, 2010 12:56 AM