Skip to main content

SharePoint Designer Workflow Failed to Start - Cancelled by System Account

I was working on a List workflow the other day in SharePoint Designer 2010. This list already had a workflow which was working perfectly fine and I needed another manual workflow in it.

No matter what I tried the workflow would fail and would log a message in the history list that Workflow failed to start and it was cancelled by System Account. I observed that the same happened with new workflows in that list, new workflows in other lists and I even tried creating new subsites and workflows were behaving the same way.

I googled for a while and there were many suggestions to clear SPD cache which did not help me. I played with SPD 2010 for a while and observed that the workflow xml and xoml files were checked out. I read in some blogs that this could cause this issue as well. I tried to check those files in but then I was greeted with a new error!

"Cannot perform this operation. The file is no longer checked out or has been deleted."

I had no clue what was happening because I could see the green arrow beside the workflow file and so it meant file was checked out. But then SPD did not allow me to check in the file. I tried the undo check out option but that did not work either. I was going crazy here because this didn't make much sense.

After spending some hair pulling moments reading lots of blogs and google searches I came across this Microsoft KB article:
SharePoint Designer 2007 workflows files can go into a checked out state and users will not be able to 
check them back in

It said that there is a hidden document library called Workflow and it should basically have only three columns:
  1. Created By
  2. Modified By
  3. Checked Out To
My workflow library had an additional column called Title and it was marked as required. According to Microsoft KB article this column or any new column apart from the above three if present should be optional. That was it, that worked like a charm. I made the Title column optional and I could check in my workflow files!

Once the workflow files were checked in my workflow worked fine and there was no error while running the workflow.

So in a nutshell, if you receive the error which I received (given in red coloured font) check if your Workflow library in your site has any required fields. If you have make them optional.

Note: Although the above KB article is for SPD 2007 it works fine with SPD 2010 as well. Navigate to your site in SPD 2010 - All Files - Workflow - Right click & select Properties and select the option to manage permission and your Workflow library settings page opens in browser from where you can copy the List ID. Follow the rest of the steps from the MS KB article.


Comments

Anonymous said…
Thank you - this helped me!
-Courtney
Anonymous said…
How do we access this workflow library in SP 2010?
Manoj said…
Hi,

Its mentioned here in this MS article on, how to find the Workflow library:
http://support.microsoft.com/kb/2273439

..Manoj
Anonymous said…
OMG, thanks Manoy !! You really saved my life. I lost 2 days looking for a solution...
Aamir said…
Similar thing is happening on SP2013. but the changes I make to the Title column are not being saved.
Anonymous said…
you saved my butt - I had been to (what felt like) a thousand sites trying to figure this out. By making the Title optional and then checking in the file that fixed it!!!!! Thanks.

Nick
PeaceBeUponYou said…
Thanks Manoj for putting this together.
I ran into the issue you described - problem is in this case I can't navigate to the 'All Files' from Designer for this particular subsite (nothing shown in the view). Even though I have enabled all SharePoint Designer Settings from Web app and Site collection levels. Is there any other way of getting to Workflow settings page?
Many thanks in advanced!
Eric Fontaine said…
Thank you very much, you saved me a lot of time! :)
Unknown said…
This solved my problem!


Thanks!
Unknown said…
Now, the big question is: why suddenly the hidden Workflow library had the Title field added/or set to Required?

We didn't do any SharePoint update in the last weeks but seems like this ocurred just a few days ago.

My concern is that I may need to go to every site and perform the trick you mentioned above.

Cheers,

Marco

Popular posts from this blog

"Cannot impersonate user for data source" - SSRS reports

We were getting this strange error while viewing our reports in SharePoint that was deployed using BIDS 2005: An error has occurred during report processing. Cannot impersonate user for data source 'datasource' Logon failed I tried many things but nothing worked. I did some research and found many blog posts which suggested me to reapply the password on the datasource file specified in the error message and save it again. That didn't work for me. I saw some check boxes in the data source file that read "Use as Windows Credentials" and "Set Execution Context to this report" and I didn't know what they meant. I unchecked those in my data source and then when the refreshed the page the report started displaying.

Users do not show up in SharePoint People Search or People Picker

I had this issue with people picker in a classic mode web application in SharePoint 2013 and this site is in 2010 mode - users in certain sub-domains would not show up in People Picker. I was aware of stsadm commands to fix this and we ran the stsadm command to hook up people picker with another domain some time back. The latest issue was that people picker was not returning users from the root domain and few sub domains. After researching on the internet I found (contrary to my thoughts) that we could use PowerShell and not just stsadm to map People Picker to domains. It is a good idea to first check what domains are added/mapped to the web application using the following commands: $wa = Get-SPWebApplication -Identity http://mywebapp.com #List the Domains $wa.PeoplePickerSettings.SearchActiveDirectoryDomains This will list the domains currently People Picker is looking up for that web application. I used the following script to map our AD forest to People Picker:

Report Server has encountered a SharePoint error. ( rsSharePointError)

I was receiving this error on the "Report Server Web Service URL" on our SharePoint farm: Report Server has encountered a SharePoint error. ( rsSharePointError) Access to this Web Site has been blocked. Please contact the administrator to resolve this problem. This site URL is configured via Central Administration > Configure Reporting Services Integration > Reporting Services Integration if Reporting Server feature/Add-in is installed on the farm. After doing some research I found out that this page somehow enumerates through entire site collections before it throws this error. As part of troubleshooting step I checked if the domain user configured for reporting service is has sufficient privileges in the farm and also as local admin of the sql box, but this did not solve the issue. We raised this issue with the vendor and they made us update our SQL Server 2005 to latest SP and CU; still we had the error. The reason was nobody was sure if this er