Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

Upon opening a workflow in SharePoint Designer 2010 I receive the following notification in SharePoint Designer:

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.Office.Workflow.Actions, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c. Contact your server administrator for more information.

I'm running SharePoint 2010.

Does anyone know how to solve this notification?

Relevant articles:

share|improve this question
add comment

3 Answers

Go to your hive folder:

Then into Template\1033\workflow

and find WSS.ACTIONS

Inside there will be a reference to a custom DLL, find it and remove it and your designer should start working again.

Make sure you take a backup of the file first.

Happy hunting.

share|improve this answer
    
I should locate this DLL file on the SharePoint server or on my client computer where SharePoint Designer is installed? –  TempaC May 28 '13 at 8:05
1  
Just need to remove it from the WSS.ACTIONS file really, the point is the DLL is missing. –  Hugh Wood May 28 '13 at 8:11
    
But it's unclear to me on which computer. –  TempaC May 28 '13 at 8:25
1  
It is most likely the local copy, not sure if this issue effects remote servers. I'm afraid I would say look locally first. Internally created DLLs are easy enough to spot. –  Hugh Wood May 28 '13 at 8:39
1  
It's not removing a file, it's removing a bad reference to a file. The WSS.ACTIONS file is pointing to a DLL that doesn't exist on the server so you are receiving a workflow error. The entire issue is a file HAS been removed somehow and not by the method that was used to place it on the server. –  Hugh Wood May 28 '13 at 13:42
show 1 more comment

I think the quick fix for your problem is to download the assembly. and deploy this in the gac using GACUTIL

share|improve this answer
    
Yeah', i'm not planning on implementing DLL files found on the internet. –  TempaC Jun 6 '13 at 11:49
    
yeah, I wont do that myself either. I'm just suggesting quick thing and as you know quick thing usually is not the best track to take. Maybe you can try to reinstall your SharePoint then maybe repair or something :) –  Ranjoe Santos Jun 6 '13 at 13:32
add comment

Try to clear the SharePoint Designer caches:

  • %USERPROFILE%\AppData\Local\Microsoft\WebsiteCache
  • %USERPROFILE%\AppData\Roaming\Microsoft\SharePoint Designer\ProxyAssemblyCache
  • %USERPROFILE%\AppData\Roaming\Microsoft\Web Server Extensions\Cache
share|improve this answer
    
I cleared "%USERPROFILE%\AppData\Local\Microsoft\WebsiteCache" and "%USERPROFILE%\AppData\Roaming\Microsoft\SharePoint Designer\ProxyAssemblyCache" the last line did not exist. Requested feedback from end-user. –  TempaC May 28 '13 at 13:01
    
Clearing these caches did not resolve the error. –  TempaC May 28 '13 at 13:59
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.