SharePoint Soup

Tag: SharePoint 2013

New Way to Install Workflow Manager On-Premises

With Web Platform Installer riding off to the sunset, the old ways of installing Workflow Manager no longer apply.

I recently encountered this while trying to install Workflow Manager on SharePoint 2019 on-prem. As of the new year (2023), we no longer have access to the product installers in WebPI. More information on that can be found here: https://learn.microsoft.com/en-us/answers/questions/429383/web-platform-installer-end-of-support-and-sunsetti

After some research I found that Microsoft actually released a new package that simplifies the old process. They call it SharePoint Workflow Manager. It is what now powers the SharePoint 2013 Workflow platform and replaces Microsoft Workflow Manager 1.0 and Service Bus 1.1.

The installation was straightforward and only requires the prerequisite of downloading and installing Azure Service Fabric Runtime and then running a PowerShell command to create an Azure Service Fabric Cluster.

January 26, 2023
SharePoint 2013 – Sign Out/Sign in as a different user

As many of you know, SharePoint 2013 no longer has the “Sign in as a different user” option like SharePoint 2010 offered. Many of you also know that you can just add “_layouts/closeConnection.aspx?loginasanotheruser=true” to the end of your main site url to do it or log into IE as a different user. This can become a hassle though to have to do it each time.

Recently, I came across this site that had a neat trick to include the javascript in an html file and create a bookmark for it from the link in the html file. (more…)

November 11, 2014
SharePoint 2013 – Error deleting web application

Yesterday, I was performing a database attach and upgrade from 2010 to 2013 SharePoint instances. I have done it previously without an issue but this time, I had to delete the prior application and recreate it (as a classic authentication application) before attaching and upgrading the database. The reason for that was being the current application was already converted to claims based authentication and when I first tried to attach the database from the 2010 “classic authentication” app, it was giving me an error. The classic authentication SharePoint site is currently a production site and we did not want to convert to claims BEFORE migration so I needed to create a classic authenticated app in SharePoint 2013.

After attempting to create the classic authentication application in SharePoint 2013, I received an error (this error will be discussing in another blog post). I tried deleting the web application and receive an error. It stated:

Sorry, something went wrong

An object of the type Microsoft.SharePoint.Administration.SPIisWebsiteUnprovisioningJobDefinition named “Unprovisioning (AppName)” already exists under the parent Microsoft.SharePoint.Administration.SPWebService named “”. Rename your object or delete the existing object.

(more…)

March 11, 2014