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...

New year, new challenges...! I'll try to be quick and to the point for this post. For one of our clients, we have FBA implemented on their portals with custom SQL database. When we login with a user account, it works fine. The user can login, move around different pages and settings, However, when user try to Logout or Sign out, the page crashes. Exactly similar problem as with this mate. However I couldn't put a comment there due to thread locked. I checked the ULS logs and the Unexpected entry said. Unexpected: Claim identity is not from a trusted login provider. identity name #.f0.blahblahDomains\blahblachAccount Struggled around for few hours but no results. Finally something tricked in mind and I added below entry in my web application's web.config before   </system.web> <? xml version= "1.0" encoding= "UTF-8" ?> < sessionState mode = "SQLServer" timeout = "60" allowCustomSqlDatabase = "true" sqlCon...

Although its a great experience working with Microsoft products but sometimes they surprises you with bugs that being a developer you would not expect. You may come across the problem that PowerApps SubmitForm is not updating data in SharePoint list, specially the People Picker type field (could be the same case with datetime type as well. Same thing I have experienced that while working on a PowerApps form which is connected with simple SharePoint list, I was unable to update the value of People Picker control which was having no special settings in SharePoint, just simple out of the box list with Title and a People Picker column. Spent hours on it but no gain. Finally the Google, a friend who can help you to find the right thing if you search for it. I came across this and this post and found similarity. Made the same changes and boom...! It worked..! You just need to turn ON the Fomula level error management under the Advance Settings. Below is the settings which I set to Yes. Have...

This was really challenging however at the end we were able to achieve this. I would like to mention my manager Mr. Yamen Hmidan for his extra ordinary thinking level that helped me to get this done. Problem Statement: We want to approve or reject Nintex Tasks using its web service API and using its ProcessTaskResponse2 method in C# by creating another web service. The C# web API will call the Nintex web API and approve or reject the task. Solution: I have created a new Web Service API Project in Visual Studio 2019 and added the Nintex service reference in my project. All the operations provided by Nintex are now available in my project under Connected Services. I called the reference as  NintexServiceReference in my code. Here is my C# code of Approve class.  Note: This code might not work 100% for you as this is just a direct copy paste and have dependencies on my other classes. This is just to give you the idea of my Get method. using ...