Friday, June 14, 2013

Tips to resolve error "Unable to load workflow actions from the server"

Recently, we have run into  "Unable to load workflow actions from the server" multiple times when users try to create or modify a workflow using SharePoint designer. Here is the error message.
 

It seems worth to summarize the major possible reason that might cause the issue and the procedure to fix it.
  
First, missing feature is the most common reason. You could follow Ian Hayse’s blog to use Fiddler verifying any missing feature. We had removed Bamboo PM suit from our environment but some reference still remained on app server. The Fiddler captures the missing feature error as in the following screenshot. The action is to clean up the feature or add back the feature if needed.


You can identify the exactly missing feature is as highlighted. The solution is to clean up the Bamboo features and components in our case. If you still need the missing feature, you should install again to avoid such issue.

<?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><soap:Body><soap:Fault><faultcode>soap:Server</faultcode><faultstring>Exception of type 'Microsoft.SharePoint.SoapServer.SoapServerException' was thrown.</faultstring><detail><errorstring xmlns="http://schemas.microsoft.com/sharepoint/soap/">Failed to find the XML file at location '14\Template\Features\ProjectCentralContentTypes\feature.xml'</errorstring><errorcode xmlns="http://schemas.microsoft.com/sharepoint/soap/">0x80131600</errorcode></detail></soap:Fault></soap:Body></soap:Envelope>

Second, corrupted workflow action file is the second common reason. You could verify the procedure form Microsoft site. The action is to copy the correct workflow action file and bounce IIS. We had corrupted file on one of the WFEs and it was fixed by coping the file from another server.

Third, corrupted SharePoint designer cache. You can delete the designer cache as described in this blog

There may be some other reasons that might cause the same issue. You should always try to IISRESET and clean up designer cache as the first two steps.



 

3 comments:

  1. I read, enjoy and learn from your blog. Thanks! Keep on posting.

    Say
    www.imarksweb.org

    ReplyDelete
  2. I am very happy to visit your site and i did like it. I was able to get some informative topics. keep it up and you can also visit my site for your reference. Thank you and have a good day.

    n8fan.net

    www.n8fan.net

    ReplyDelete
  3. Life is full of many challenges. Challenges that will make you or break you depending on how you handle it. Visit my site for more updates. God Bless to your site.

    n8fan.net

    www.n8fan.net

    ReplyDelete