SharePoint Experts, Information Architects, Expert Witness

We provide consulting in a broad array of business and technology from architecture to design to deployment of global systems with a focus on surfacing data in the enterprise. Specialists in Microsoft, we are a premier provider of SharePoint Expertise (including 2016 and Office 365). We also provide Expert Witness/Legal Expert in eDiscovery, source discovery, patent infringement, piracy and more! We also have established SICG DLDS s.a. - our counterpart in Costa Rica that specializes in water systems (http://www.crwatersolutions.com) - Contact me direct: david_sterling@sterling-consulting.com or call 704-873-8846 x704.

Search This Blog

Wednesday, August 25, 2010

SharePoint Designer 2010 Error - The list of workflow actions on the server references an assembly that does not exist

When attempting to create a new workflow using SharePoint Designer 2010, I've encountered the error:

"The list of workflow actions on the server references an assembly that does not exist. Some actions will no be available. The assembly strong name is Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c. Contact your administrator for more information."

In investigating this, I did find a post answered by Paul Stork on the Microsoft site - in his reply to the problem, he inidcated that this would typically happen when someone had added a custom workflow DLL to the WSS.ACTIONS or MOSS.ACTIONS files located in the hive under Template\1033\Workflow.

That said, as you can see by the error above, "Microsoft.SharePoint" is hardly a custom DLL. I got the above to occur when trying to create a workflow in a team site type site collection in a full instance of SharePoint (Standard or Enterprise).

I found two ways that seem to fix this:

1) Close Designer and run an IISReset - reopen Designer and try again
2) Use Designer to open an existing SharePoint publishing site (or create one if necessary) and create a new workflow (you should not get the error). Don't save it, just simply close Designer. Reopen the original site and try again.

8 comments:

Khaniya said...

I have try way you suggested. Still I am facing same issue.

David M. Sterling said...

I double checked another system with the same problem and it worked. The only suggestion would be to check permissions - verify the issue through the System Application Event log (you won't see anything in the ULS logs).

John Doe said...

Would removing the custom DLL in WSS.ACTIONS be an option?

Muhammad Hawasly said...

create a new web and site collection and create a new a new workflow for the new site. you'll get the error message. don't save the work flow. and close the SPD. reopen the designer and create a new work flow it'll solve the problem.

Muhammad Hawasly said...

create a new web and site collection and create a new a new workflow for the new site. you'll get the error message. don't save the work flow. and close the SPD. reopen the designer and create a new work flow it'll solve the problem.

David M. Sterling said...

No - it's not a custom DLL - just a bug.

Shan said...

This is not correct solution.

David M. Sterling said...

So why do you say "not correct solution" - what is YOUR solution? Do tell.