View Complete Post
I am working with SharePoint Server 2010 Beta 2, Visual Studio 2010 Ultimate RC and SharePoint Designer 2010 Beta.I built a custom Content Type based on the Item type with a few custom site columns. I also have built a custom Sequential Workflow using Visual Studio 2010. This is a relatively simple workflow that creates a task, waits for the task to complete, sets the workflow to complete. I am able to deploy this workflow to the site collection through VS 2010. The problem I have is that when I try to associate my custom Content Type with my custom workflow, that workflow is not listed in the workflow templates to select. There are only the OOTB SharePoint workflows to choose. However, if I create a list and associate a workflow to that list, my custom workflow is listed in the workflow template list. This makes sense since at the start of building a custom workflow in VS2010, one of the first questions is whether the workflow is a Site or a List workflow and I selected List. I did a little research and found some who wrote that Reusable Workflows may be attached to Content Types. In VS2010, there is no option to build a Reusable Workflow. That is only possible in SharePoint Designer. However, it is possible to import a SPD workflow into VS, so I tried that. Imported the WSP into VS201
I am facing a problem from last some days..
When I am trying to open/create/update workflows from Designer 2010, then designer giving me an error "Unable to load workflow actions from the server. Please contact your server administrator".
I researched on internet for this error and found some possible reason like
I have build a test solution in two parts :
1) WCF service which hosts a Windows Workflow (statemachine).
2) Console application which consumes the WCF Service.
It works well, but if I do a bad process, it crashes which is normal. Exemple : the client calls an event which is impossible to execute given the current state according to the workflow design. In this case, the client receives a WCF exception. This exception
is masked, which is normal (an option has to be set in WCF side to enable exception transmission).
The problem is that, althought I launched the console application with the debugger, with the WCF service project, the debugger doesn't break on Workflow errors in WCF error side. (However, I saw that non-Workflow errors in WCF side are still stopped by
How could I force the VS debugger to break on Workflow WCF errors ?
I have an issue on a SP2010 farm. When I try to open or create a workflow through SharePoint Designer, I get the error message "Unable to load workflow actions from server"
I have been through a number of threads here and elsewhere and have ruled out the following common causes: