Comments on: Moving a sharepoint workflow between solutions – “Failed on Start (retrying)”

By: Sanket Shah

Sanket Shah — Mon, 09 Nov 2009 21:30:05 +0000

Nice Post and good information.

It didn’t resolve my problem somehow.

I am getting same error while starting of workflow, FYI: I am not using WSPBuilder, I created workflow using VS 2008 (SharePoint 2007 Sequential workflow template), when I put “While” activity OR “If” activity with “declaration code”, it’s giving me above error.

I already checked into my project file, I have below highlighted line as per your post.

It seems that some DLL got corrupt or something else or I am missing some code

If you have any idea related to this, can you please help me to resolve this error?

Thank you!
Sanket

By: Gowtham

Gowtham — Mon, 13 Jul 2009 18:09:03 +0000

I’m having the same error and my .csproj file has the two lines that you mentioned above at the end of the file. Is there any other way to get rid of this error?

By: Stuart

Stuart — Tue, 07 Apr 2009 06:13:30 +0000

Thank you Greg! I was pulling my hair out over this one, and your post cleared it up nicely. My problem was the missing target in the .csproj file, just like you suggested.

By: SharePoint - WSPBuilder Workflow Failed On Start « Stuart Cox’s Tech Punch

Tue, 07 Apr 2009 05:57:36 +0000

[...] to Greg G’s post here that pointed me in the right [...]

By: Zohaib

Zohaib — Mon, 11 Aug 2008 09:37:19 +0000

I also have the same problem but my .csproj file is fine i am using only feature.xml, workflow.xml and workflow assembly to deploy to another system but encountering the same “Failed on Start (retrying)” problem. can any one help me urgent…

By: Greg Galipeau

Greg Galipeau — Wed, 16 Jul 2008 12:53:39 +0000

Thanks for the comment Tom. This blog was suppose to be just something for people to look for when moving workflows around. I never thought it would be something every workflow needed.
My situation was actually because of the fact I was moving a .net 3.5 workflow around. That is why I needed those imports. I have seen other blogs that refer specifically to .net 3.0, so I wanted to put something out there to help people on the 3.5 framework.
Anyways, this is more of a bug fix blog than a “how to” blog. Guess I should have been more clear. Thanks for you comment. Greg.

By: Tom Clarkson

Tom Clarkson — Wed, 16 Jul 2008 01:11:31 +0000

There may be more to it than that – I have a state machine workflow that is working without that import.

I did need to change the targeted framework from 2.0 to 3.0 to get the designer to show up properly though, this was fairly obvious when building a workflow from scratch (no designer and errors on the workflow assembly references), but may be easy to miss if you are just copying and rebuilding.

By: kelly

kelly — Thu, 19 Jun 2008 19:27:13 +0000

THANKS. You are a life-saver, AGAIN. I have spent much of the last two days tearing files apart to see what I did wrong (differently). It seemed to work when I did not have an if/else and only had an activated and a code block. Once I put the if/else it “failed”. It seems like I was doing something wrong since it would work part of the time.

By: Links (5/22/2008) « Steve Pietrek - Everything SharePoint

Links (5/22/2008) « Steve Pietrek - Everything SharePoint — Fri, 23 May 2008 01:20:50 +0000

[...] Moving a sharepoint workflow between solutions [...]