Fixing SharePoint

Since there is no major updates in Workflow Manager installation process for last couple of years, the offline installation became really difficult. Microsoft recommends to install it through WPI  tool, however sometimes the online installation also becomes a nightmare. This is what happened recently. Problem Description: For one of our client, we had to prepare environment with following. SharePoint Server Enterprise 2019 Window Server 2019 Standard Workflow Manager 2013 As usual I followed the same installation guide which ran fine few weeks ago with another different environment but here we faced the below error while installing Workflow Manager Refresh 1.0 (CU2). "The product did not install successfully. Download file failed signature verification and may have been tampered with" Tried to run the setup multiple times but nothing helped. Checked all the available discussion threads on Microsoft's and other forums but nothing helped much. However I must thanks PeterFle...

Microsoft SharePoint Server 2016 encountered an error during setup The Error: While installing SharePoint Server 2016 RTM version downloaded directly from Microsoft's website, We faced below error and wasted our days in troubleshooting. Tried almost every solution we found on Internet till date including increasing the cores of servers and virtual processors as well. However, this error was a nightmare as there was no sufficient details about error. Microsoft SharePoint Server 2016 encountered an error during setup Solution: There could be several other reasons for this error, however in my case, this was the dumbest thing I have ever seen with installation. We were trying to install SharePoint 2016 from its ISO by right click > Mount and then install using normal splash. Extracting SharePoint 2016 files to a separate directory and then installing it fixed the problem. May be the SharePoint didn't like the mounted drive letter. :) Hope it helps...!

Lesson Learned: Never leave your servers to automatically download and install the updates. We had a SharePoint farm where Workflow manager is configured on one of its server and rest of them are just using WFM client to connect with the server. Everything was running smooth until some updates got installed on the servers over night and the next morning Workflows stuck and start giving errors. As initial check, I verified SharePoint services and WFM services, noticed that the Service Bus Gateway service is struck at Starting state. This was very generic thing but at least a point to start thinking... Troubleshooting: 1. Tried manual restart, but no luck. 2. Tried Leaving and Joining the WFM Farm again. But the timeout error. Error message received during rejoining:  “Starting Service bus gateway on machine <servername> failed: timeout has expired and the operation has not been completed” 3. Tried ULS check and noticed below error. "  Service cannot be started. Micr...