Configure Workflow Manager on a server that is NOT part of the SharePoint 2013 farm

Note: For configuring Workflow Manager on a server that is NOT part of the SharePoint 2013 farm, you must install the Workflow Manager Client on each server in the SharePoint farm before you run the pairing cmdlet.

For downloading and installing the Workflow Manager Client go here

To configure Workflow Manager on a server that is NOT part of the SharePoint 2013 farm and on which communication takes place by using HTTP

1. Log on to each server in the SharePoint Server 2013 farm.

2. Install the Workflow Manager Client on each server in the SharePoint farm.

3. Open the SharePoint Management Shell as an administrator. This is accomplished by right-clicking the SharePoint 2013 Management Shell command and choosing Run as administrator.

4. Run the Register-SPWorkflowService cmdlet. The cmdlet should be run only once and can be run from any of the servers in the SharePoint farm.

Register-SPWorkflowService -SPSite "http://myserver/mysitecollection" -WorkflowHostUri "http://workflow.example.com:12291" -AllowOAuthHttp

To configure Workflow Manager on a server that is NOT part of the SharePoint 2013 farm and on which communication takes place by using HTTPS

1. Determine whether you need to install Workflow Manager certificates in SharePoint 2013.

2. Log on to each server in the SharePoint Server 2013 farm.

3. Install the Workflow Manager Client on each server in the SharePoint farm.

4. Open the SharePoint Management Shell as an administrator. This is accomplished by right-clicking the SharePoint 2013 Management Shell command and choosing Run as administrator.

5. Run the Register-SPWorkflowService cmdlet.

Register-SPWorkflowService -SPSite "https://myserver/mysitecollection" -WorkflowHostUri "https://workflow.example.com:12290"

Reference

Configure Workflow Manager on a server that is part of the SharePoint 2013 farm

To configure Workflow Manager on a server that is part of the SharePoint 2013 farm and on which communication takes place by using HTTP

1. Log on to the computer in the SharePoint Server 2013 farm where Workflow Manager was installed.

2. Open the SharePoint Management Shell as an administrator. This is accomplished by right-clicking the SharePoint 2013 Management Shell and choosing Run as administrator.

3. Run the Register-SPWorkflowService cmdlet.

Register-SPWorkflowService -SPSite "http://myserver/mysitecollection" -WorkflowHostUri "http://workflow.example.com:12291" -AllowOAuthHttp

4. Log on to each server in the SharePoint Server 2013 farm. Each server in the SharePoint Server 2013 farm must have the Workflow Manager Client installed.

5. Install the Workflow Manager Client on each server in the SharePoint farm.

To configure Workflow Manager on a server that is part of the SharePoint 2013 farm and on which communication takes place by using HTTPS

1. Determine if you need to install Workflow Manager certificates in SharePoint.

2. Log into the computer in the SharePoint Server 2013 farm where Workflow Manager was installed.

3. Open the SharePoint Management Shell as an administrator. This is accomplished by right-clicking the SharePoint 2013 Management Shell and choosing Run as administrator.

4. Run the Register-SPWorkflowService cmdlet.

Register-SPWorkflowService -SPSite "https://myserver/mysitecollection" -WorkflowHostUri "https://workflow.example.com:12290"

5. Log on to each server in the SharePoint Server 2013 farm. Each server in the SharePoint Server 2013 farm must have the Workflow Manager Client installed.

6. Install the Workflow Manager Client on each server in the SharePoint farm.

For downloading and installing the Workflow Manager Client go here

Reference

Install and configure workflow for SharePoint Server 2013

1. Install and configure SharePoint Server 2013

2. Install and configure Workflow Manager

3. Configure Workflow Manager to work with the SharePoint Server 2013 farm

The following two key factors needs to be considered before configuring Workflow Manager to work with SharePoint Server 2013.

1. Is Workflow Manager installed on a server that is part of the SharePoint farm?

2. Will communication between Workflow Manager and SharePoint Server 2013 use HTTP or HTTPS?

These factors translate into four scenarios. Each scenario configures a SharePoint Server 2013 farm to communicate and function with the Workflow Manager farm.

1: Workflow Manager is installed on a server that is part of the SharePoint 2013 farm. Communication takes place by using HTTP.

2: Workflow Manager is installed on a server that is part of the SharePoint 2013 farm. Communication takes place by using HTTPS.

3: Workflow Manager is installed on a server that is NOT part of the SharePoint 2013 farm. Communication takes place by using HTTP.

4: Workflow Manager is installed on a server that is NOT part of the SharePoint 2013 farm. Communication takes place by using HTTPS.

Reference

SharePoint 2013 Crawl job will not stop

When you are unable to stop a crawl (full or incremental) using the Central Administration UI, you can try one of the below steps

Approach 1 (Restart Search services)

1. Stop and start the SharePoint Server Search 15 service

2. Go to services.msc -> SharePoint Server Search 15 -> Restart

Run the PowerShell script on the SharePoint server

Approach 2 (Using net start command)

net stop OSearch15

net start OSearch15

Approach 3 (Using PowerShell command)

Stop-Service -name OSearch15

Start-Service -name OSearch15

Approach 4 (PowerShell script to stop the SharePoint Crawl Job)

Add-PSSnapin "Microsoft.SharePoint.PowerShell"

Get-SPEnterpriseSearchCrawlContentSource -SearchApplication "Search Service Application" | ForEach-Object {

     if ($_.CrawlStatus -ne "Idle")

     {

         Write-Host "Stopping currently running crawl for content source $($_.Name)..."

         $_.StopCrawl()

       

         do { Start-Sleep -Seconds 1 }

         while ($_.CrawlStatus -ne "Idle")

     }

}

Approach 5 (Perform an Index rest)

Browse to Central Administration -> Search Service Application -> Crawling-> Index Reset -> Reset Now

Note: Resetting the crawled content will erase the content index. After a reset, search results will not be available until crawls have been run.

How to change the URL for SharePoint Central Administration site

If you extend the Central Administration web application (using GUI or psconfig command) to run on multiple servers, and when you click on SharePoint Central Administration icon you're still redirected to the first SharePoint server where Central Administration is hosted.

The URL has to be changed via registry on all SharePoint servers to fix this.

To change the URL for SharePoint Central Administration URL:

1) Open Registry editor

2) Backup the registry before making changes

3) Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\14.0\WSS and change the value of CentralAdministrationURL to the new URL

Common Office Web Apps PowerShell commands

Get-SPWOPIBinding

The Get-SPWOPIBinding returns a list of bindings that were created by using New-SPWOPIBinding on the current SharePoint farm.

Get-SPWOPIBinding

Remove-SPWOPIBinding

The Remove-SPWOPIBinding removes all bindings on the current SharePoint farm.

Remove-SPWOPIBinding -All:$true

New-SPWOPIBinding

The New-SPWOPIBinding creates bindings for all the applications and file name extensions that the WOPI application supports on the current SharePoint farm

New-SPWOPIBinding -ServerName "Server.corp.Contoso.com"

Related Posts – 1 , 2

Configuration Failed - Failed to connect to the configuration database: Error during decryption. Ensure the passphrase is correct.

Issue Description

1. I was trying to connect a SharePoint server to an existing farm after entering the farm passphrase.

The configuration wizard fails and gives me the below error message

Configuration Failed

Failed to connect to the configuration database: 

An exception of type System.ArgumentException was thrown. Additional exception information: Error during decryption. Ensure the passphrase is correct.

2. I tried putting in a garbage passphrase and it gave an error message: The passphrase you entered is incorrect. Please try again

3. But when I tried putting in the correct farm passphrase, it went past this stage and the configuration wizard failed.

Fix

1. Clear SharePoint Configuration Cache on all SharePoint servers

2. Run the configuration wizard on the new server

SharePoint 2016 : WSS Usage Application proxy in Stopped State

Issue Description

I was working on installing and configuring a SharePoint 2016 farm and I noticed that the Usage and Health Data Collection Proxy was in Stopped State

Fix

Get-SPServiceApplicationProxy

Copy the ID for the WSS Usage Application and use it in your PowerShell command

$UsageApp = Get-SPServiceApplicationProxy | Where {$_.ID -eq "14804966-1b85-4538-b25b-2a15269147a4"}

$UsageApp.Provision()

SharePoint 2013: The server was unable to save the form at this time. Please try again.

Error Description

When I am trying to save data on any list in the farm I got the below error

The server was unable to save the form at this time. Please try again.

Fix

An IISRESET fixed the issue.

Setsitelock: Stsadm operation

Sets a value that specifies whether the site collection is locked and unavailable for read or write access. This operation should be used in conjunction with the Getsitelock operation. For more information, see the Examples section.

Syntax

stsadm -o setsitelock

   -url <URL name>

   -lock {none | noadditions | readonly | noaccess}

None: Sets the site collection to unlock.

Noadditions: Permits changes that reduce the size of the data.

For example, if you had an announcement list item whose body consisted of 50 characters, you could successfully edit the list item so that the body was reduced to 25 characters. However, if you tried to edit the list item so that they body was increased to 100 characters, that would be blocked.

Readonly: Sets the site collection to read-only.

Noaccess: Sets the site collection unavailable to all users.

Examples

To determine the lock status of the site, you can use the following getsitelock syntax:

stsadm -o getsitelock -url http://server_name

Once the lock status of the site collection is determined, you can use the noaccess parameter of the setsitelock operation to lock out all users to the site:

stsadm -o setsitelock -url http://server_name -lock noaccess

Reference