SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

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

Since a few days I have the above error message flooding my trace logs. I noticed that my Workflow timer job is stuck on "initialized". Any idea how I can determine which workflow is causing this issue?

I tried increasing the logging level, there is also nothing to see in the eventlogs on the server.

share|improve this question
up vote 3 down vote accepted

A running workflow wanted to get information from an account that did not exist anymore. I was able to solve this by cancelling the workflow and then running

stsadm -o migrateuser -oldlogin domain\olduser -newlogin domain\newuser -ignoresidhistory

to change the old login in all content databases to the new login. See for more info.

share|improve this answer
Solved my issue also. Thanks a ton! – neo269 Feb 1 '12 at 8:54

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.