Blog

Automatically moving SharePoint site collections to separate databases


05 June, 2015

I had a requirement to move site collections into separate databases after a large migration. For this to work, I have one content database that is created as default with maximum number of sites set to 5000. My script will then create new databases with a site limit of 1 and move the site collections to that database.

Read More...

SharePoint 2013 Workflow Gotcha: Unable to start workflow on lists with forced checkout


04 February, 2015

When you try to start the workflow you get an error similar to Activity in progress. Retrying last request. Next attempt scheduled in less than one minute. Details of last request: HTTP InternalServerError to http://SERVER/_vti_bin/client.svc/web/lists/… Check your versioning settings on the list. Does it enforce checkouts using “Require documents to be checked out before they can be edited”? Check your workflow. Is it set to update the stage name? It will not be able to do this.

Read More...

Creating SharePoint Designer reusable workflow with base content type


04 February, 2015

When creating a reusable SharePoint 2013 workflow from SharePoint Designer using the Ribbon, you are unable to bind it to a content type. The (very silly) workaround to this is to create the workflow from the File menu as follows. Doh…!

Read More...

Troubleshoot: Workflow Manager Errors in SharePoint


04 February, 2015

Here are a few errors and solutions that I have found when working with Workflow Manager. Failed to register because the farm or partition is already registered with a workflow service If you reconfigure a site that is already configured, you might get this error. There does not seem to be an “unregister” function, so instead use the –Force attribute during registration, such as: Register-SPWorkflowService -SPSite http://spdemo.lekman.com –WorkflowHostUri http://wf.lekman.

Read More...

SharePoint High Trust Apps and ADFS/SAML


01 February, 2015

A high trust app requires several things in order to work: an S2S trust configuration that generates the OAuth token, a private certificate for decrypting the OAuth token and a registered issuer ID and client ID. If this is in place, then the OAuth token will contain the claim that allows an app to talk to SharePoint will be sent to the app. However, the user portion of the token is not sent by SharePoint – it must be generated on the app side.

Read More...