SharePoint In Action

An attempt to share my day-to-day SharePoint experience

Archive for the month “January, 2014”

ValidateCredentialClaims – Access Denied: Claims stored in the credentials did not match with the group claim for a group app.

Users were getting an error when they were trying to access the SharePoint site content. I checked the logs and found below errors:

ValidateCredentialClaims – Access Denied: Claims stored in the credentials did not match with the group claim for a group app.
Access is denied to the Secure Store Service.

In my case this was related to the members of my “Target Application” in my “Secure Store Service”. To fix it I went to Central Admin > Application Management > Manage Service Applications > Secure Store Service and edited the Target Application ID. I went to the third page by hitting Next.
I just added my members(or groups) to my target application’s member section.



Nader Heshmat


SharePoint 2013 Workflow is not enabled in SharePoint Designer 2013

I had created a Workflow Manager Farm but I was still unable to see the “SharePoint 2013 Workflow” in my SharePoint 2013 Designer.


Here is what I did to make it work:

On my SharePoint server(s) I executed the PowerShell command below to register my workflow:


Register-SPWorkflowService –SPSite –WorkflowHostUri -ScopeName [-PartitionMode] [-AllowOAuthHttp] [-Force]

an example of abow syntax would be:

Register-SPWorkflowService –SPSite "" –WorkflowHostUri "" –AllowOAuthHttp -force

or in my case since it was a dev box(no SSL):

Register-SPWorkflowService –SPSite "" –WorkflowHostUri "<strong>http:</strong>//" –AllowOAuthHttp -force

Please note that the “Workflow Service EndPoint URL” can be found in your SharePoint Server’s IIS Manager:


Please pay a close attention to the protocol your Workflow Service is using. By mistake I put http:// instead of https:// and I was getting error below:

Register-SPWorkflowService : The underlying connection was closed: An unexpected error occurred on a receive.


After running the Powershell command you would need to go to your Central Admin and check the “Workflow Services Application” under “Manage Service Applications”. The Workflow Service Status should read “Workflow is connected”. Once the workflow is connected you should be able to see the “SharePoint 2013 Workflow” in your SharePoint Designer.




Nader Heshmat

Uninstalling/Removing SharePoint 2013 Workflow Manager Farm

These are the steps you would need to take to uninstall your Workflow manager 1.0:

For each node in your workflow farm:

  1. Leave the workflow farm (Remove the node from the farm using “Leave Workflow Manager Farm” option)






     2.      Uninstall the following programs in the program list in the Control Panel window, under Programs select Uninstall a Program.

  • Service Bus 1.0
  • Windows Fabric
  • Workflow Manager 1.0
  • Workflow Manager 1.0 Client


Once you are sure all nodes have left the workflow farm, you can delete below databases from you SharePoint SQL Server: (Backing them up beforehand might be a wise choice!)

  • SBMessageContainer01
  • SbGatewayDatabase
  • SBManagementDB
  • WFInstanceManagementDB
  • WFManagementDB
  • WFResourceManagementDB



Post Navigation