SPD workflow fails to start

This issue has been raised few times before. I followed the solution to check in / check out workflow and made Title as optional column but I am not able to still solve the problem.
I have list based on custom content types. Created very simple workflow which just logs to the history. when I start the workflow I received this error message in the logs.
06/13/2012 13:57:28.22 w3wp.exe (0x10F8) 0x0C84 SharePoint Foundation Workflow Infrastructure 72fs Unexpected RunWorkflow: System.ArgumentException: Item does not exist. It may have been deleted by another user. at Microsoft.SharePoint.SPList.GetItemById(String strId, Int32 id, String strRootFolder, Boolean cacheRowsetAndId, String strViewFields, Boolean bDatesInUtc) at Microsoft.SharePoint.Workflow.SPWorkflowNoCodeSupport.LoadWorkflowBytesElevated(SPWeb web, Guid docLibID, Int32 fileID, Int32 fileVer, Int32& userid, DateTime& lastModified) at Microsoft.SharePoint.Workflow.SPWorkflowNoCodeSupport.<>c__DisplayClass1.<LoadWorkflowBytes>b__0(SPSite elevatedSite, SPWeb elevatedWeb) at Microsoft.SharePoint.Workflow.SPWorkflowNoCodeSupport.LoadWorkflowBytes(SPWeb web, Guid docLibID, Int32 fileID, Int32 fileVer, Int32& userid) at Microsoft.SharePoint.Workflow.SPNoCodeXomlCompiler.Load... 625ae924-be53-4091-aaec-9085e152d586
06/13/2012 13:57:28.22* w3wp.exe (0x10F8) 0x0C84 SharePoint Foundation Workflow Infrastructure 72fs Unexpected ...XomlAssembly(SPWorkflowAssociation association, SPWeb web) at Microsoft.SharePoint.Workflow.SPWinOeHostServices.LoadDeclarativeAssembly(SPWorkflowAssociation association) at Microsoft.SharePoint.Workflow.SPWinOeHostServices.CreateInstance(SPWorkflow workflow) at Microsoft.SharePoint.Workflow.SPWinOeEngine.RunWorkflow(SPWorkflowHostService host, SPWorkflow workflow, Collection`1 events, TimeSpan timeOut) at Microsoft.SharePoint.Workflow.SPWorkflowManager.RunWorkflowElev(SPWorkflow workflow, Collection`1 events, SPWorkflowRunOptionsInternal runOptions) 625ae924-be53-4091-aaec-9085e152d586
06/13/2012 13:57:28.28 w3wp.exe (0x10F8) 0x0C84 SharePoint Foundation Workflow Infrastructure 98d8 Unexpected System.ArgumentException: Item does not exist. It may have been deleted by another user. at Microsoft.SharePoint.SPList.GetItemById(String strId, Int32 id, String strRootFolder, Boolean cacheRowsetAndId, String strViewFields, Boolean bDatesInUtc) at Microsoft.SharePoint.Workflow.SPWorkflowNoCodeSupport.LoadWorkflowBytesElevated(SPWeb web, Guid docLibID, Int32 fileID, Int32 fileVer, Int32& userid, DateTime& lastModified) at Microsoft.SharePoint.Workflow.SPWorkflowNoCodeSupport.<>c__DisplayClass1.<LoadWorkflowBytes>b__0(SPSite elevatedSite, SPWeb elevatedWeb) at Microsoft.SharePoint.Workflow.SPWorkflowNoCodeSupport.LoadWorkflowBytes(SPWeb web, Guid docLibID, Int32 fileID, Int32 fileVer, Int32& userid) at Microsoft.SharePoint.Workflow.SPNoCodeXomlCompiler.LoadXomlAssembly(... 625ae924-be53-4091-aaec-9085e152d586
06/13/2012 13:57:28.28* w3wp.exe (0x10F8) 0x0C84 SharePoint Foundation Workflow Infrastructure 98d8 Unexpected ...SPWorkflowAssociation association, SPWeb web) at Microsoft.SharePoint.Workflow.SPWinOeHostServices.LoadDeclarativeAssembly(SPWorkflowAssociation association) at Microsoft.SharePoint.Workflow.SPWinOeHostServices.CreateInstance(SPWorkflow workflow) at Microsoft.SharePoint.Workflow.SPWinOeEngine.RunWorkflow(SPWorkflowHostService host, SPWorkflow workflow, Collection`1 events, TimeSpan timeOut) at Microsoft.SharePoint.Workflow.SPWorkflowManager.RunWorkflowElev(SPWorkflow workflow, Collection`1 events, SPWorkflowRunOptionsInternal runOptions) 625ae924-be53-4091-aaec-9085e152d586

Hi,
My workflow fails to start and is cancelled this happens on
one subsite, it is a custom workflow created in SPD on a custom list. I
am the site wide administrator so I have rights to everything. I have looked at the logs filtering by workflow and I get this error below.
RunWorkflow: System.ArgumentException: Item does not exist. It may have been deleted by another user.
I see anything about the page being check in or checked out.
Everything is sharepoint 2010.
Could you please direct me to an answer or some help please.
Thanx

Similar Messages

The workflow failed to start due to an internal error

My approval workflow never work in my machine before. It was a newly installed machine. when i start the Approval workflow, it stated "The workflow failed to start due to an internal error'. What other circumtances might lead to this problems?or you can email me @ [email protected]

hi
Finally it worked for me after reinstalling the features on the site collection. deactivating and reactivating didnt help. once i uninstalled and re installed them it worked.
Here are the steps i performed.
OffWFCommon
stsadm -o deactivatefeature -id C9C9515D-E4E2-4001-9050-74F980F93160 -url <url> -force
stsadm -o uninstallfeature -id C9C9515D-E4E2-4001-9050-74F980F93160 -force
ExpirationWorkflow
stsadm -o deactivatefeature -id C85E5759-F323-4EFB-B548-443D2216EFB5 -url <url> -force
stsadm -o uninstallfeature -id C85E5759-F323-4EFB-B548-443D2216EFB5 -force
ReviewWorkflows
stsadm -o deactivatefeature -id 02464C6A-9D07-4F30-BA04-E9035CF54392 -url <url> -force
stsadm -o uninstallfeature -id 02464C6A-9D07-4F30-BA04-E9035CF54392 -force
SignaturesWorkflow
stsadm -o deactivatefeature -id 6C09612B-46AF-4B2F-8DFC-59185C962A29 -url <url> -force
stsadm -o uninstallfeature -id 6C09612B-46AF-4B2F-8DFC-59185C962A29 -force
translationWorkflow
stsadm -o deactivatefeature -id C6561405-EA03-40A9-A57F-F25472942A22 -url <url> -force
stsadm -o uninstallfeature -id C6561405-EA03-40A9-A57F-F25472942A22 -force
install & activate
OffWFCommon
stsadm -o installfeature -name offwfcommon -force
stsadm -o activatefeature -id C9C9515D-E4E2-4001-9050-74F980F93160 -url <url> -force
ExpirationWorkflow
stsadm -o installfeature -name Expirationworkflow -force
stsadm -o activatefeature -id C85E5759-F323-4EFB-B548-443D2216EFB5 -url <url> -force
ReviewWorkflows
stsadm -o installfeature -name ReviewWorkflows -force
stsadm -o activatefeature -id 02464C6A-9D07-4F30-BA04-E9035CF54392 -url <url> -force
SignaturesWorkflow
stsadm -o installfeature -name SignaturesWorkflow -force
stsadm -o activatefeature -id 6C09612B-46AF-4B2F-8DFC-59185C962A29 -url <url> -force
TranslationWorkflow
stsadm -o installfeature -name Translationworkflow -force
stsadm -o activatefeature -id C6561405-EA03-40A9-A57F-F25472942A22 -url <url> -force

Custom SharePoint Designer 2010 Workflows "Failed on Start"

Good morning everyone!
I have created a library using a custom Document Sets based content type that allows an additional custom Document based content type. I add a Document Set approval workflow using SharePoint Designer, but it constantly fails to start with these results:
Event Type
User ID
Description
Workflow Cancelled
System Account
Workflow [Workflow Name] was cancelled by System Account
Error
System Account
[Workflow Name] failed to start
I decided to test an OOTB workflow on the library to see if it would work and it did! An OOTB Approval Workflow functioned as expected. Also, other custom workflows on the site collection are running normally.
I've looked around for fixes, but haven't quite seen this exact scenario, so I figured I'd check here first before I started messing around with anything else.
Any help would be greatly appreciated!
Toni Marie

Hi Toni,
According to your description, my understanding is that only the custom workflow containing "Start Document Set approval process" could not get be started.
Whether you tried to create a new workflow only containing "Start Approval Process" action via SharePoint Deisgner 2010. If not, please test again, compare the result.
Please create a new library, and add the document set into this library, then enable content approval for this library in library advanced settings. After that, re-create a new workflow only containing "Start Document Set Approval process" action,
compare the result.
Please test with another user, compare the result.
In addition, please check whether SharePoint 2007 Workflow feature and Workflow feature are enabled. If yes, please disable and re-enable them. If not, please enable them.
There is a similar post, please check if it is useful for you:
http://chayadigital.wordpress.com/2012/07/16/sharepoint-2010-custom-workflow-failed-to-start-error/
Best Regards,
Wendy
Wendy Li
TechNet Community Support

Out of the box workflow failed on start when started programatically

I have an approval workflow (out of the box) associated with a list and need to start it for some items programmatically when some conditions are met.
My application runs under an account which is a farm admin. I do have another user dedicated to start workflows. I'm using the code below but it always results in a 'failed on start' with these errors
2/27/2015 4:54 PM
Workflow Cancelled
System
Account
Workflow 'WorkflowName' was canceled by System Account.
2/27/2015 4:54 PM
Error
System
Account
'WorkflowName' failed to start.
Code is :
SPUserToken userToken = null;
using (SPSite site = new SPSite("SiteName"))
using (SPWeb web = site.OpenWeb())
site.AllowUnsafeUpdates = true;
web.AllowUnsafeUpdates = true;
userToken = web.AllUsers["WorkflowAccount"].UserToken;
site.AllowUnsafeUpdates = false;
web.AllowUnsafeUpdates = false;
using (SPSite site = new SPSite("SiteName", userToken))
using (SPWeb web = site.OpenWeb())
site.AllowUnsafeUpdates = true;
web.AllowUnsafeUpdates = true;
SPWorkflowManager workflowManager = web.Site.WorkflowManager;
SPList list = web.Lists["LibName"];
SPListItem item = list.Items[1];
SPWorkflowAssociationCollection associationCollection = list.WorkflowAssociations;
foreach (SPWorkflowAssociation association in associationCollection)
if (association.Name == "WorkflowName")
association.AutoStartChange = true;
association.AutoStartCreate = false;
association.AssociationData = string.Empty;
site.WorkflowManager.StartWorkflow(item, association, association.AssociationData);
break;
site.AllowUnsafeUpdates = false;
web.AllowUnsafeUpdates = false;
Is there any requirement on who can create the workflow? I can control who creates if I absolutely have to
Any help/clues/directions appreciated.

Hi LNFei,
To troubleshooting the issue, I recommend to follow the steps as below:
1.Start the workflow manually to check whether it works.
2.Use another account not System Account to check whether it works.
3.Publish the workflow as a different user (rather than System Account).
4.Deactivate and Reactive the “Workflow” Feature.
5.Check other workflows on other lists/libraries could work well.
6.Create a simple workflow having only one activity which will log history only, check if it works well.
Best Regards,
Wendy
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Workflow failed to start

Hi,
We are having a Visual Studio 2010 workflow which is working fine in production. I made some minor changes in the code and deployed the DLL for the workflow in the test server.
The workflow is not running and throwing the below errors
1. Workflow XYZ was cancelled by System Account.
2. XYZ failed to start.
Due to these errors, I didn't deploy the changes in production. Can anyone please help on this?
Thanks,
Kunal

Hi Kunal,
To update the visual studio workflow, we need to deploy a new version of the workflow assembly and a new version of Workflow Element.xml, re-register (deactivate and then activate) the workflow Feature, and recreate or add the workflow association so that
SharePoint can connect to the new version of workflow assembly.
So the workflow Element.xml file, workflow feature and the workflow association are needed to be updated in addition to the workflow assembly.
More references:
http://sharepoint497.blogspot.com/2012/09/upgrading-or-redeploying-sharepoint.html
http://blogs.msdn.com/b/yardman/archive/2010/04/14/versioning-a-visual-studio-sharepoint-workflow.aspx
Best regards.
Victoria
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Workflow Failed on Start (workflow was cancelled by System Account

I have created a Workflow in SP Designer and attached to the library. It works fine in Dev but failing to run in Prod. getting the error Workflow was cancelled by System account and failed on Start.
Can anyone help me in this regard.
Thanks

Hi,
What is SharePoint server’s version?
Check if the account who start the workflow has enough permission.
If you were using SharePoint server 2007, all Visual Studio workflows (including SharePoint OOB workflow and customized workflows) run as the System Account and have
full rights to everything in SharePoint Products and Technologies.
SharePoint Designer workflows, on the other hand, still run as the System Account, but they do so with their permissions trimmed down to those of the account that
initiates the workflow.
In other words, SharePoint Designer workflows always run impersonating the user who initiates the workflow.
For more information about troubleshoot workflow errors, check out the following article:
http://office.microsoft.com/en-us/sharepoint-designer-help/troubleshoot-workflow-errors-HA010237912.aspx
(SharePoint 2007)
http://technet.microsoft.com/en-us/library/cc298927.aspx
(SharePoint 2010)
Thanks,
Rock Wang
Regards, Rock Wang Microsoft Online Community Support

SharePoint Designer Workflow 'Failed on Start', SP Logs has WorkflowValidationFailedException, works ok when recycle IIS App Pool and restart

Hi there,
I know there are a lot of posts about "Failed to Start" errors, but I have yet to see one that describes our problem.
We have workflows built with SharePoint Designer 2007
Normally these workflows start ok and work completely
Occasionally though they will all fail to start, instead showing "Failed on Start (retrying)" in the Workflow Status and the following exception in the SP Logs:
01/16/2015 15:43:27.28 w3wp.exe (0x15D4) 0x1A00 Windows SharePoint Services Workflow Infrastructure 936l High Engine RunWorkflow: System.Workflow.ComponentModel.Compiler.WorkflowValidationFailedException: The workflow failed validation. at System.Workflow.Runtime.WorkflowDefinitionDispenser.ValidateDefinition(Activity root, Boolean isNewType, ITypeProvider typeProvider) at System.Workflow.Runtime.WorkflowDefinitionDispenser.LoadRootActivity(Type workflowType, Boolean createDefinition, Boolean initForRuntime) at System.Workflow.Runtime.WorkflowDefinitionDispenser.GetRootActivity(Type workflowType, Boolean createNew, Boolean initForRuntime) at System.Workflow.Runtime.WorkflowRuntime.InitializeExecutor(Guid instanceId, CreationContext context, WorkflowExecutor executor, WorkflowInstance workflowInstance) at System.Workflow.Runtime.WorkflowRuntime.Load(Guid key, CreationContext con...
01/16/2015 15:43:27.28* w3wp.exe (0x15D4) 0x1A00 Windows SharePoint Services Workflow Infrastructure 936l High ...text, WorkflowInstance workflowInstance) at System.Workflow.Runtime.WorkflowRuntime.GetWorkflowExecutor(Guid instanceId, CreationContext context) at System.Workflow.Runtime.WorkflowRuntime.InternalCreateWorkflow(CreationContext context, Guid instanceId) at System.Workflow.Runtime.WorkflowRuntime.CreateWorkflow(Type workflowType, Dictionary`2 namedArgumentValues, Guid instanceId) at Microsoft.SharePoint.Workflow.SPWinOeHostServices.Send(SPWinOeWorkflow winoeworkflow, SPWorkflowEvent e) at Microsoft.SharePoint.Workflow.SPWinOeEngine.RunWorkflow(Guid trackingId, SPWorkflowHostService host, SPWorkflow workflow, Collection`1 events, TimeSpan timeOut)
What is strange, is that if I recycle the App Pool for the SharePoint site and then restart the workflows, they all work fine for a time. Until the next time they don't =)
The workflows must be configured ok since they do work complete at time, but I wonder if there is something with the memory usage of the app pool or something that is being re-compiled when the App Pool is recycled
The App Pool is set to recycle nightly, and when virtual memory > 1700MB or memory > 1000MB
Is anyone able to shed any light on this problem?? Or what steps I can take to debug the problem further.
Thanks in advance
Miguel Clark =)

Hi Sudip,
Thanks for the link.
The workflows in question are SharePoint Designer workflows using standard actions, so unsure exactly how to check the 'correlation tokens' and 'DLLs', plus the workflow works fine as soon as I recycle the IIS App Pool, so do not see how these could be the
problem
As to the 'lodctr' commands, we have tried these in the past, to no effect. Though may try them again next time the issue comes up just to see if it does the same thing as recycling the app pool.
My big question here is "why would it suddenly work after recycling the app pool??" I feel like it must be something memory related, since recycling the app pool releases the resources used by the IIS worker process.
Miguel =)

SPD Workflow will not start automatically for the first entry in a list on any given day (subsequent entries start just fine)

Hi. I have various workflows on various lists that share a common issue. The first entry of the day on that list will not start the workflow automatically. We have SharePoint 2013 Foundation. This same issue occurred when we had SharePoint 2010
as well. Interestingly, I had read about a 'fix' by adding a 5 minute pause at the start of every workflow which worked fine for a while. Now I happened to find that this is no longer working (after I see a bunch of workflows that didn't fire over the past
month - ugh!).
I know I'm not the only one with this issue as I ran across others with the issue when I first researched it and found the 'pause fix' a year or so ago and I also talked with someone else during a SP seminar who used this same fix. NOTE: These
are end users creating the items. It is not logged as a system account.
Any help would be appreciated. I have a SharePoint developer I can hire if this is beyond my ability to fix. I just need some guidance (last time I inquired they weren't aware of this issue).

Can you also advise if these are complicated workflows or high traffic lists?
Steven Andrews
SharePoint Business Analyst: LiveNation Entertainment
Blog: baron72.wordpress.com
Twitter: Follow @backpackerd00d
My Wiki Articles:
CodePlex Corner Series
Please remember to mark your question as "answered" if this solves (or helps) your problem.

How to notify admin/some user if in list/library workflow fails?

How to send notification to admin if workflow fails to start or some error occurs in workflow?
i tried creating workflow on workflow history list but it is not running automatically as items are created with system account.
Is there any other way to notify admin ?

if you are trying to notify admin when an entry added to workflow history list, you can create alerts for that list.
http://office.microsoft.com/en-001/sharepoint-foundation-help/create-an-alert-or-subscribe-to-an-rss-feed-HA010378197.aspx
My Blog- http://www.sharepoint-journey.com|
If a post answers your question, please click Mark As Answer on that post and Vote as Helpful

Workflow does not start when PowerShell Script is run from Task Scheduler

I have a PS script that updates an item in a SP2010 list so that a workflow will be started. When I run the PS script manually from the PS window on the server it resides, the script runs flawlessly. If I set a scheduled task on the same server
to run the script with the same credentials as are being used in the PS window, the script runs, updated the info on the list, but DOES NOT start the workflow. As we know, SPD workflows cannot be started by anonymous or system accounts. It is as
if the task scheduler adds a bit of information that makes the SP2010 list think the information was updated by one of these accounts even though the field in the list for the item being updated shows the correct account.
HELP!!!
D

Hi,
The issue might be related to the script or schedule task settings your configured. You’d better check the settings.
For example, which option do you set to run the scheduled task? You may select “Run whether user is logged on or not” instead of “run only when user is logged on” as shown in this article:
http://blog.pointbeyond.com/2010/04/23/run-powershell-script-using-windows-server-2008-task-scheduler/
Hope it helps.
Best Regards,
Sally Tang

SharePoint 2013 Workflow (SPD 2013) fails for Active Directory Group members

Hi
I have a SharePoint 2013 site called "Team Meetings". There are a number of lists and an InfoPath form library.
The site's SharePoint Group "Team Meeting Members" has two Active Directory groups (All Club Managers and All Club Police) as members. Those two AD groups contain all the people that I want to have access to the library and list, except for
a few additional folk who I have made individual members.
My PROBLEM:
I have created a SharePoint 2013 Workflow using SPD 2013 associated with the Form Library. Workflow is set to start on new or modified item. The first action is to write to history list, then determine the status (Submitted or Pending) of
the form and go to different Stages depending on that status.
The workflow works perfectly for any user who has been added directly to the SharePoint group (Team Meetings Members) BUT FAILS at the very first action for anyone who is a member of one of the AD groups. I know the Workflow is fine because I've tested it
with numerous people who are direct members of the SharePoint Group, but whenever a person who is a member of the AD group tries it the Workflow just fails.
Here's a print of the info from the Workflow Status page (I don't have access to server logs):
RequestorId: 4494760f-92ff-2e8c-90d2-cc7df0e6baa4. Details: System.ApplicationException: HTTP 401 {"Transfer-Encoding":["chunked"],"X-SharePointHealthScore":["0"],"SPRequestGuid":["4494760f-92ff-2e8c-90d2-cc7df0e6baa4"],"request-id":["4494760f-92ff-2e8c-90d2-cc7df0e6baa4"],"X-FRAME-OPTIONS":["SAMEORIGIN"],"MicrosoftSharePointTeamServices":["15.0.0.4420"],"X-Content-Type-Options":["nosniff"],"X-MS-InvokeApp":["1;
RequireReadOnly"],"Cache-Control":["max-age=0, private"],"Date":["Mon, 10 Mar 2014 01:31:42 GMT"],"Server":["Microsoft-IIS\/8.0"],"WWW-Authenticate":["NTLM"],"X-AspNet-Version":["4.0.30319"],"X-Powered-By":["ASP.NET"]}
The HTTP response content could not be read. 'Error while copying content to a stream.'. at Microsoft.Activities.Hosting.Runtime.Subroutine.SubroutineChild.Execute(CodeActivityContext context) at System.Activities.CodeActivity.InternalExecute(ActivityInstance
instance, ActivityExecutor executor, BookmarkManager bookmarkManager) at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor
Members of the SharePoint Group "Team Meetings Members" have Contribute Access to both the form library and another list that the workflow writes to as well as the Workflow History list (which in SP 2013 uses the credentials of the
user who started the workflow, unlike 2010 which used System Account).
All members of the Team Meetings Members group, whether they are individual members or part of one of the AD groups, have no problems opening and saving forms etc. It's just the Workflow that doesn't like them...
I am stumped. I've spent many hours searching for a reason for this. There are about 200 people in the two AD groups so I really don't want to have to add them all individually - especially when these groups are managed in AD for a whole bunch of other reasons
and using the AD groups means I'll basically never have to worry about modifying the SharePoint access permissions.
Does anyone have any ideas why this is happening and what I can try to fix it?
Mark

Hi Lars,
I'm afraid not so far but we are trying a few things today so I will post back with results.
First thing we are doing is making the AD Group universal because one of our (external provider) gurus remembers seeing something about that. He also sent me a link to a post where they were talking about earlier
versions but having similar issues and their solution was to make sure the app pool account has sufficient permissions in AD::
http://social.msdn.microsoft.com/Forums/sharepoint/en-US/27a547da-5cc0-49d7-8056-6eb40b4c3242/failed-to-start-workflow-access-is-denied-exception-from-hresult-0x80070005-eaccessdenied
This part of that thread looks interesting but we haven't checked it yet as were trying the universal setting first:
"If the users participating in the workflows have been added to the SharePoint site via Active Directory groups, SharePoint has to update the user’s security token periodically by connecting to
the domain controller. By default, the token times out every 24 hours. But if the application pool account did not have the right permissions on the domain controller to update the user’s token, user will keep getting the access denied error. The error was
intermittent because when the user browsed to any page other than the workflow form, the token was getting updated successfully.
You can try to fix it through granting the application pool account the appropriate permission by adding the account to the group “Windows Authorization Access Group” in Active Directory."
I'll update when we try these ideas. If you have any luck please do the same.
Mark
(sorry about formatting - using my phone....)
Mark

Workflow error Failed on Start (retrying)

When I run my custom workflow, it gives error Failed on Start (retrying) each time. It was working properly, but now it gives the mentioned error. Even I have created two more very simple custom workflow on testing list, they even did not work and gave the same error. How to rectify this error.

Hi,
I am also facing this same issue and I have been scratching my head since last 2 days.
I have created a blog site. There is a SPD workflow attached to the Post list and Comments list with a few number of activities like Build Dynamic String, Send Email etc. Both the lists (Post & Comments) have content approval set. Point is whenever I
am creating a new post or new comments, the workflow column is showing "Failed on Start (retrying)". Then after a few moments it's getting completed, activities are working and sometimes getting stopped.
Checking the log files under 12 hive I got :
System.ArgumentException: Value does not fall within the expected range.
RunWorkflow: System.ArgumentException: Value does not fall within the expected range. at Microsoft.SharePoint.Workflow.SPWorkflowActivationProperties..ctor(SPWorkflow workflow, Int32 runAsUserId, String associationData, String initiationData)
at Microsoft.SharePoint.Workflow.SPWinOEWSSService.MakeActivation(SPWorkflow workflow, SPWorkflowEvent e) at Microsoft.SharePoint.Workflow.SPWinOeEngine.RunWorkflow(Guid trackingId, SPWorkflowHostService host, SPWorkflow workflow,
Collection`1 events, TimeSpan timeOut) at Microsoft.SharePoint.Workflow.SPWorkflowManager.RunWorkflowElev(SPWorkflow originalWorkflow, SPWorkflow workflow, Collection`1 events, SPRunWorkflowOptions runOptions)
I don't know what is the issue. But still it's not getting resolved.
I have already tried the below tricks following various forums and blogs.
Checked removing the Send Email & Build Dynamic String activity.
Checked the app pool account (IIS) and service account (Central Admin) and changed them both to NETWORKSERVICE account.
Checked and compared all the entries in web.config and GAC
Tried repairing the perfCounters
Tried this blog - http://sharepoint.indigoreality.com/2013/01/14/sharepoint-designer-2010-error-could-not-publish-the-workflow-because-the-workflow-configuration-file-contains-errors/
Tried deactivating the features with the word "workflow"
Tried another workflow with another custom list. Same thing is happening.
Also tried an OOB approval workflow. Task is getting created and mail is coming. But workflow column is showing "Failed on Start (retrying)".
Please help me out. I am using MOSS 2007 and SPD 2007.
Thanks a lot in advance.
- Brushaketu

Out of the box approval workflow suddenly failed on start (retrying)

SharePoint 2010. I've been using out of the box approval workflow for several month now. I did some minor changes to it, like to who and when emails should be send, but that's all.
Then out of a sudden it stopped working. New request status is "Failed on start (retrying)". Sometimes (!) status is "In Progress", but no tasks are created. In both cases there is nothing on workflow history and error report is also empty
(it even cause an error "Report contains no data").
I'm sure that I didn't change anything in a workflow. The only think that I changed was an InfoPath form, but I only added there field "Created By", so I would see in calendar later who created this request. I couldn't see how this might affect workflow
process.
I'm confused as I don't even know where to start searching for the solution. Why this might happen? Any ideas are very welcome!

In my list I have a multiple choice field which is not required. When it was
blank my workflow was failing on start! This field was not involved in a workflow directly, I included it only in the email to approver. When I deleted it from an email everything was fine.

Failed to start workflow. The workflow cannot access the item that it has been applied to.

I have a quick question for you and it would be great if you can answer me on this.
I'm working through SharePoint Workflow issue (developed using Nintex) that started recently where people are getting workflow error and I don't see issues if I submit it myself. Current error. - "Failed to start workflow. The workflow cannot access
the item that it has been applied to."
I haven't made any major changes to Workflow except for changing email notification content and publishing it. My question is, do I need to publish the rest of the workflows too that are associated to the list after I publish changes of one workflow? Looks
like users have required permissions to submit the form. Please let me know how to get rid of this error.
smith

Hi Smithspd,
According to your description, my understanding is that your users got a workflow error, and the workflow is created by Nintex.
For SharePoint Designer workflow, once we do any change in a workflow, we need to re-publish the workflow.
For your issue, I suggest you re-publish the workflow, compare the result.
In addition, as your workflow is created by Nintex and this forum is for SharePoint Designer, I suggest you ask Nintex support or forum for better help. Thanks for your understanding.
Best Regards,
Wendy
Wendy Li
TechNet Community Support

Sharepoint Designer 2010 Workflows Struck in "starting" status after Sharepoint 2010 SP2 upgrade(KB2687453 - June 2013)

We have SPD workflows and Nintex workflows which are configured to start automatically on a Document Library which have content type. After we have been installed KB2687453
(sp2) , all the workfows running on documnet library with content type got strucked and always saying" starting". Please help us.,... highly apprciated as it's urgnet. Thanks in advance.

Hi nart ,
It is a known issue. Please install the June 2013 CU to solve the problem.
June 2013 CU:
http://blogs.technet.com/b/stefan_gossner/archive/2013/06/12/june-2013-cu-for-sharepoint-2010-has-been-released.aspx
For more information, you can refer to the thread:
http://blogs.msdn.com/b/chaun/archive/2013/05/16/if-your-sp2010-workflows-are-stuck-in-the-starting-state.aspx
http://social.technet.microsoft.com/Forums/sharepoint/en-US/5a6e6e83-b59f-4099-a86f-a07723ff2b98/workflow-stuck-in-starting-state-after-applying-sharepoint-2010-cu-december-2012?forum=sharepointadminprevious
Best Regards,
Eric
Eric Tao
TechNet Community Support

SPD workflow fails to start

Similar Messages

Maybe you are looking for