SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

After upgrading to sharepoint 2010. SharePoint Designer workflow is starting automatically on principal worklfow but not starting on secondary workflow on task list when the item is created by incoming email.

the problem is due to the system account used to create the item in the first library.

What solution can apply to solve this issue?

share|improve this question

migrated from Jun 21 '12 at 14:02

This question came from our site for professional and enthusiast programmers.

What do you mean by "principal" and "secondary" workflow? I'd guess you have a workflow set to run when an item is created, that executes another workflow at some point. Is that it? – Panagiotis Kanavos Jun 21 '12 at 11:00
the scenario is using incoming email an item is created in principal list which trigger principal workflow automatically then a task item is created in the task list. the workflow associated with the task list does not trigger in the log I see can't trigger declarative workflow with system account. – kadben Jun 21 '12 at 15:20

See this article, which says:

Install Infrastructure Update and pay close attention to one small line written in the notes part of the knowledgebase article:

To prevent the declarative workflows from impersonating the system account, the workflows will now impersonate the user who created the workflow association.

This basically means that you should create a special account not SHAREPOINT\SYSTEM, that is a site collection owner on the site collection where the workflow is hosted, open the workflow in SharePoint Designer while logged on as this new account and simply save the workflow without modifying anything.

It will effectively change the account that associated the workflow, which will allow it to start.

you should also run

stsadm -o setproperty -pn declarativeworkflowautostartonemailenabled -pv true

to enable workflows to start using the impersonation scheme

share|improve this answer
this solution is for wss 3.0 not sharepoint 2010 – kadben Jun 25 '12 at 10:37
up vote 0 down vote accepted

Finally I used an event receiver to start the workflow associated to the task list.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.