So, recently, when working at a client site, a password expired. You can imagine the fun that ensued from that. Not all of the app pools got updated, so the account locked and the password became invalid. In the midst of all of this, 2013 Workflows stopped working.
I was getting a lot of unhelpful messages, starting with Scope can’t be found. Well, it is pretty puzzling when the Scope that was working yesterday now can’t be found.
The long and short of this, after stopping the workflow manager (stop-sbfarm) and then changing the worklow accounts back to their original account, and starting the workflow manager again (start-sbfarm)… I had to re-register the scope.
Register-SPWorkflowService -SPSite <Any site> -workflowhosturi https://WFServer:12290 -Force
The kicker here is the -Force. If you don’t use the -Force, you will get an error stating “Failed to register because the farm or partition is already registered with a workflow service”.
I will post more detailed commands later, as I’m still in the office and wanted to type this up before I forgot.
Also – coming soon, some REALLY in depth workflows about creating sites across site collections using SharePoint designer workflows, and updating list items in other site collections! They were really fun to make! I can’t wait to share them with you!
So – this is my first Tech post on the Bri Is SharePoint blog. I ran into an interesting situation today, and thought that I should post about it.
I have many clients on SharePoint Online. And I’ll admit, the features and capabilities are cool with the added bonus of not having to host, but that is a conversation for a different time. What I want to discuss is the hassle caused by the “New Experience” vs the “Classic Experience”. If you have been using SharePoint Online, you probably know that there is a “New Experience” being rolled out. This is great, but it seems to take away a lot of features – such as editing the library page. Another issue that I am running into is not being able to change back to the new experience once I have reverted to the old experience. I am still researching this issue… so I’ll keep you updated…
Now to the crux – Some libraries look like the new experience and some look like the classic experience. Another caveat… the client would like to have “Sticky” column headers… This is fine for the classic experience but not for the new one. And then, what if the libraries in classic mode somehow change back to the new experience. This could cause a whole host of problems.
I just wanted to pass this on in case anyone else was stuck in a similar situation.