SharePoint 2013 Workflow Manager error when I register workflow service
Hi. I think, that issue depends on SharePoint Developer tools Preview for VS 12. I had the same problem. When I uninstalled tool then after restarted server I tried to run Register-SPWorkflowService. My problem was resolved.Sergey A Belskiy - Microsoft Most Valuable Professional Sharepoint Server, MCP, MCTS, MCPD || My blog || My Twitter || My Facebook || My Video
November 7th, 2012 11:24am
Hi Sergey, Thank you very much. That solved it for me as well. Thanks again. Stu
November 7th, 2012 11:41am
Thanks Sergey!! That fixed it
November 7th, 2012 11:53am
You are welcome Sergey A Belskiy - Microsoft Most Valuable Professional Sharepoint Server, MCP, MCTS, MCPD || My blog || My Twitter || My Facebook || My Video
November 7th, 2012 2:29pm
Small add-on to Segey post. 1. Uninstall tools - no reboot needed. 2. Register workflow. 3. Reinstall tools from direct link (web installer fails due to dependancy on Beta version of workflow) - http://go.microsoft.com/fwlink?LinkID=256248 - SharePoint Designer is not able to create a new workflow. 4. Unistall again - no SharePoint tools in VS, but SharePoint Desinger works. Anybody has hint how to setup dev. env. for SharePoint 2013 RTM, including workflows?
November 11th, 2012 7:44am
Hi, I have the same situation. However, I believe the solution to that is: Wait for the RTM version of the VS 2012 tools before we can have both abilities; i.e workflow in both SPD2013 and VS2012. Someone please correct me if I am missing a solution here. Thanks. Stu
November 11th, 2012 10:05am
I am getting the same error. Do you have a work around?
November 11th, 2012 11:23am
Hello, Me too. 1. I can hit the url in IE and get the <DefaultWorkflowConfiguration> XML for the Root Scope. 2. Get-WFFarm returns everything as expected. 3. All services are running. I have followed the documentation to the letter (a couple of times) with the same result; i.e the following error: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information. Anyone know if this is a Known Issue, and/or if there is any workaround? Thanks. Stu
November 11th, 2012 3:39pm
Update: The Workflow Manager PowerShell shows the service as running. In SharePoint 2013 CA, the WF Service is listed as Not Running or Not Configured, It is both. Finally, the page at the "this link" blind link is mysteriously gone (page not found). It was found a few days ago.
November 11th, 2012 4:16pm
When I try to register the workflow service according to http://technet.microsoft.com/en-us/library/jj658588%28v=office.15%29 by the folloing command: Register-SPWorkflowService SPSite "http://mysharepointserver" WorkflowHostUri "http://localhost:12291" AllowOAuthHttp I got this error: Register-SPWorkflowService : Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information. At line:1 char:1 + Register-SPWorkflowService SPSite "http://mysharepointserver" WorkflowHostUri "h ttp:/ ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~ + CategoryInfo : InvalidData: (Microsoft.Share...WorkflowService: RegisterSPWorkflowService) [Register-SPWorkflowService], ReflectionTypeLoa dException + FullyQualifiedErrorId : Microsoft.SharePoint.WorkflowServices.PowerShell .RegisterSPWorkflowService Is there any idea?
November 11th, 2012 8:22pm
I'm hitting the exact issue with a clean install: Server 2012 Standard SQL Server 2012 Web SharePoint 2013 Enterprise Programs: SharePoint Designer 2013 Visual Studio 2012 Professional Service Bus 1.0 Workflow Manager Client 1.0 Workflow Manager 1.0 Any progress? At this point, I'm thinking a dll references in the powershell cmd is incorrect. Either pointing to a missing dll, a renamed dll or maybe a different dll version. Thoughts? Thanks, Jon $Error.Exception.ToString() System.Reflection.ReflectionTypeLoadException: Unable to load one or more of th e requested types. Retrieve the LoaderExceptions property for more information. at System.Reflection.RuntimeModule.GetTypes(RuntimeModule module) at System.Reflection.RuntimeModule.GetTypes() at System.Reflection.Assembly.GetTypes() at Microsoft.SharePoint.WorkflowServices.ActivityBuilderAssembly.GetBuilderI nfoCollection() at Microsoft.SharePoint.WorkflowServices.StoreWorkflowDeploymentProvider.<>c __DisplayClassb.<UploadLocalActivities>b__9(ActivityBuilderAssemblyCollection c ollection, ActivityBuilderAssembly builderAssembly) at Microsoft.SharePoint.WorkflowServices.StoreWorkflowDeploymentProvider.Enu merateBuilderAssemblies(Boolean sorted, BuilderAssemblySink sink) at Microsoft.SharePoint.WorkflowServices.StoreWorkflowDeploymentProvider.Upl oadLocalActivities(String serviceAddress, ICredentials workflowServiceCredentia ls, String activityName, Boolean force) at Microsoft.SharePoint.WorkflowServices.PowerShell.RegisterSPWorkflowServic e.InternalProcessRecord() at Microsoft.SharePoint.PowerShell.SPCmdlet.ProcessRecord()
November 12th, 2012 12:56am
Hi, I have come to the same issue. I guess that it is caused by different version of workflow client (rtm) and workflow client things (content types etc. - preview) installed by workflow client in SharePoint. When you install: 1. SharePoint. 2. Visual Studio. 3. Tools for SharePoint and Office (preview) - install preview version of workflow client and also preview version of content types and other stuff in SharePoint. 4. Uninstall Workflow client - probably does not uninstall things from SharePoint. 5. Install RTM version of workflow client (still the SharePoint's workflow things are in preview version). So, when you try to connect workflow with SharePoint you got this nice error. I will try to install this in other order (visual studio tools last) and check up if it's working. This a bit tricky as those tools cannot be installed without dependency like workflow client (preview), but I have found workaround for this. I will come back with my findings tomorrow.
November 12th, 2012 5:01am