Cancel all workflows in SharePoint 2010

If you've ever had a glitch where custom workflows are all in an error state or other circumstances where you just need to wipe the slate clean of the workflows genreated in SharePoint, use this PowerShell command from the SharePoint 2010 Management Shell:

foreach ($wf in $web.Workflows){[Microsoft.SharePoint.Workflow.SPWorkflowManager]::CancelWorkflow($wf)}

Comments

Post a Comment

Popular posts from this blog

Exchange 2010 Product Keys and Licensing

As part of the post installation tasks, the first two immediate steps include verifying the installation and then registering a product key on the server. The former step requires a little experience on installing Exchange servers. The primary step recommended by Microsoft is to view the Exchange Setup Logs which will be in a folder of similar name on the installation drive. These logs should reveal any problems encountered during the installation. With my failed installation attempt, I can tell you there are other indicators to consider. The System and Application event logs and the services should be examined. The Exchange Management Console (EMC) and Exchange PowerShell should be open as well. Both the EMC and Powershell hung with my installation. If the EMC opens correctly, poking around the gui and running PS commandlets such as get-exchangeserver develop a warm fuzzy that things were placed in the correct order. The product key relates very closely to your choice of editi...
Read more

Renaming a SharePoint server

Image
How to change the server computer name with MOSS These instructions relate specifically to my VM configuration. I found many references on the internet for doing this and most omitted a step or included other steps. It was extremely frustrating spending the time doing this to have it fail. Finally I discovered another reference that indicated “stsadm updatefarmcredentials” was required. This was missing in other recipes. In addition, this recipe includes changing IIS identities, very possibly the problem that was occurring before. The error I was getting after unsuccessful attempts: “some or all identity references could not be translated”. This occurred when navigating to the operations page, for example. Old server name: SHAREPNTSERVER New server name: OMITTED User name: administrator Password: password Server name change steps 1. Change alternate access mappings Go to Operations in Central Administration. Select Alternate access mappings. Change them all to referen...
Read more

Migration of Novell to Microsoft

I have performed a ga-zillion Novell to Microsoft migrations. Here are some tips to use from my experience: When to use a third-party migration tool: To boil down if you need to purchase a migration tool, such as Quest Software's NDS Migrator, answer these questions: Is your eDirectory tree in good shape? Do you wish to maintain all those user accounts? Are the groups relatively well-maintained? Will you need to build an Active Directory forest? Do you have several hundred or thousands of user objects? Do you have dozens or more NetWare volumes? Is maintaining file ownership important? Will your client PCs need to join an Active Directory domain? Is it important that the Novell Client be removed from the PCs? Do you need to transfer Macintosh files? If you answered "yes" to any of the above questions, do yourself a favor and purchase a migration tool. DISCLAIMER: I have experience with Quest's NDS Migrator. I will make reference to it in this post, but I don...
Read more