Friday 22 April 2016

SharePoint 2013 – Workflow Manager 1.0 offline download & Installation

I want to create SharePoint 2013 workflow in SharePoint Designer. But it is not showing SharePoint 2013 workflow option. So we need to first setup workflow manager.

There is no direct download to the Workflow manager and required components that need to Install and Configure Workflow Manager 1.o with SharePoint 2013.

If the server have Internet connection “Web Platform Installer” does the job for you. This is good for quick setup of development environment but what if we want to setup on a server that don’t have internet connection. Also for consistent builds (Dev/QA/production) we need to download and install the same software across all the environments.


Below steps provide how to download the required Workflow Manager 1.0 components.

Here is the instructions from Microsoft link :

(Note: Please do not confuse with the below Microsoft link to download Workflow manager 1.0, again this is not full version).

Step 1: Log on to the machine where you have internet connection and down load the web platform installer “WebPlatformInstaller_amd64_en-US.msi” from here

Step 2: Extract the files from “WebPlatformInstaller_amd64_en-US.msi” to a folder. There are different ways to extract files from msi. below is the example using msiexec utilty.

Open Command prompt or powershell run as administrator and enter the below command:

msiexec /a <msi location with folder path> /qb TARETDIR = <folder location where the files needs to be extracted>


msiexec /a C:\SharePoint\SP2013\Tools\WebPlatformInstaller_amd64_en-US.msi /qb TARGETDIR=C:\

It will extract the folder structure as below.

Required “WebpiCmd.exe” available under <above target location>/Microsoft/Web Platform Installer

Step 3: Download Workflow Manager components using WebpiCmd.exe

In the command prompt or powershell

webpicmd.exe /offline /Products:WorkflowManager /Path:<folder directory to download>

Lets Install and configure workflow manager with SharePoint Server 2013…

Step1: The Workflow Components are downloaded as below folder structure..

Step 2: Run the below command to invoke the Workflow Manager Configuration Manager screen..

WebpiCmd.exe /Install /Products:WorkflowManager
/XML:<directory of workflow manager downloads>
Eg: below..

Step 3: Workflow Manager Configuration Wizard screen starts...

Step 4: Click on Configure Workflow Manager with Default settings (Recommended). New Farm Configuration wizard opens and enter the required fields.  (Here I am talking about minimum required fields for configuration, there are advanced option parameters for setup a production farm)

SQL Server Instance: i.e The Database server for the Workflow Manager databases

Configure Service account: a dedicated domain service account for work flow manager

Certificate Generation Key: similar to Passphrase in SharePoint a password for securing the workflow manager farm. this is required when workflow manager farm extended..

Step 5: On clicking Right arrow bottom of the screen, configuration starts

Step 6: Upon successful installation all the check marks are passed with green

Step 7: Workflow manager is setups a IIS web site on the box hosting on port 12290 (for ssl) and 12291 for http (non ssl). you can add host url for the ports that are of interest in configuration such as workflowmanager (This way we can avoid using the server FQDN name while configure with SharePoint site collection)
you can verify the workflow manager Installation by accessing http://localhost:12291 or http://<host url>:12291 (if host url configured). XML file with configuration detail opens..
Step 8: Now run the below SharePoint PowerShell command to configure the workflow manager with a SharePoint 2013 site collection
Register-SPWorkflowService –SPSite “http://myserver/mysitecollection&#8221;
–WorkflowHostUri “;
Step 9: Verify the Workflow Manager configured successfully with the site collection by using SharePoint Designer 2013

Register-SPWorkflowService Failed to query the OAuth S2s metadata error


You have followed all the specified TechNet requirements/permissions in setting up SharePoint 2013 and Workflow Manager 1.o farm but when Registering Workflow manager with SharePoint site collection you might have got the below error:

Register-SPWorkflowService : Failed to query the OAuth S2S metadata endpoint at URI ‘http://xxxx/_layouts/15/metadata/json/1&#8217;. Error details: ‘An error occurred while sending the request.’. HTTP headers received from the server – ActivityId: 5b035802-7a59-4235-acb5-943a0e21e942. NodeId:
xxxx. Scope: /SharePoint. Client ActivityId : 66bd6434-9778-4a6f-b275-63a399d73c8c.


Basically it is trying to connect to the SharePoint url end point (http://xxxx/_layouts/15/metadata/json/1 . In my case the SharePoint url (which has host header) was not accessible from Workflow Manager server (as I have not dns published the url). I added the SharePoint url to the Workflow manager server host file and can access the SharePoint url.

Now the Register-SPWorkflowservice command runs without issue.

Key here is that make sure that both SharePoint and workflowhost urls are accessible from the SharePoint / Workflow Manager server.

Hope this helps.

Friday 8 April 2016

Scheduling Search Crawl in SharePoint

If you want to configure Full/Incremental/Continuous search crawl, follow below steps:

  • On the Configure Search Settings page, in the Crawl Settings section, click Content sources and crawl schedules.
  • On the Manage Content Sources page, right click the content source for which you want to schedule an incremental crawl and then click Edit.
  • On the Edit Content Source page, in the Crawl Schedules section, do the following:

Incremental/Full crawl setup:

  • If an Incremental/Full crawl has never been created for this content source, click the Create schedule link below the Incremental/Full Crawl list.    -or-
  • If you are changing the Incremental/Full-crawl schedule, click the Edit schedule link below the Incremental Crawl list.
  • In the Manage Schedules dialog box, in the Type section, select Daily, Weekly, or Monthly.
  • In the Settings section, do the following:

  1. In the Run every box, type the number of days between crawls. For example, to schedule an incremental crawl to start every other day, type 2.
  2. In the Starting time list, select the time of the day from which to start the scheduled crawl.
  3. If you want to crawl more frequently than once a day, select the Repeat within the day box and type the number of minutes to wait between crawls in the Every box and type the total number of minutes in which to repeat the crawl within the same day in the For box. For example, if you select Repeat within the day and type 60 in the Every box and 720 in the For box, an incremental crawl of the content source you are configuring starts every 60 minutes up to 720 minutes (12 hours) after the first scheduled incremental crawl for this content source ran.
  4. Click OK.

  • Click OK in  Content Source page.

Continuous crawl setup:

  • Select the continuous crawl radio button in Crawl Schedule Section.
  • Click OK in  Content Source page.

Unlike an incremental crawl, which starts at a particular time and repeats regularly at specified times after that, a continuous crawl automatically starts at predefined time intervals. The default interval for continuous crawls is every 15 minutes.

To Change the Continuous crawl time do the following steps:


  • Verify that the user account that is performing this procedure is a member of the Farm Administrators group.


  • Start a SharePoint 2013 Management Shell.
  • At the Windows PowerShell command prompt, type the following commands:

        $ssa = Get-SPEnterpriseSearchServiceApplication


        Where: n is the regular interval in minutes at which you want to continuous crawls to start. The default interval is every 15 minutes. The shortest interval that you can set is 1 minute.


If you reduce the interval, you increase the load on SharePoint and the crawler. Make sure that you plan and scale out for this increased consumption of resources accordingly.