Link to home
Start Free TrialLog in
Avatar of telliot79
telliot79

asked on

SharePoint upgrade workflow "There are no workflows currently available to start on this item. "

Experts,

I'm currently upgrading my SP platform to 2010 to 2013. I have a custom workflow built in Visual Studio which appears to be deployed to my list, but doesn't trigger when a new item. I'm running my SP site in 2010 compatibility mode still, and when a new item is created I don't see an option "Start a new Workflow" oin my list items. The list item just states "There are no workflows currently available to start on this item. " when I take a look at the workflows on the list, my custom workflow is there and is set to trigger on new items or modified items or by authenticated users with Edit Item perms.

has anyone experienced this problem with upgrading custom visual studio workflows from 2010 to 2013? and any idea how to fix it?

Many thanks in advance,
Avatar of Bembi
Bembi
Flag of Germany image

Hello,

for SharePoint Workflows, there are three options.
- Start on create
- Start on update
- Allow to start manually...

Have you had a look into SharePoint designer, if the workflows are there and correctly assigned to the list?

Also have in mind, that SharePoint has different workflow engines..
For 2007 workflows, you have a feature, which needs to be activated in 2010 and above.
For 2010 you have the 2010 engine
For 2013, you have the 2010 engine and 2013 workflows as far as the 2013 engine is installed (optional setup via Web Platform Installer or download).

You may also review your workflow to see, which objects you have touched and if an update is needed.
So possibly it is triggered, but doesn't do anything.
Dependent from the content of the workflow, a recreation may needed.
Also a republish may help.

2007, 2010 and 2013 have different workflow engines / workflow foundation relations...
You may have a look here:

Converting 2007 workflows to 2010
http://sharepoint.stackexchange.com/questions/9521/how-to-migrate-workflows-from-sp-2007-to-sp-2010

Converting 2010 workflows to 2013
https://blogs.msdn.microsoft.com/chandru/2013/04/13/upgrading-spd-2010-workflows-to-spd-2013-workflows/
Avatar of telliot79
telliot79

ASKER

Thanks Bembi for your response. My workflow was built in VS not SPD, and my problems appear to be that the workflow type is depreciated in .net 4.5. I've taken a closer look at my solution in VS and am receiving the following error when I try and deploy it:

'System.Workflow.Activities.StateMachineWorkflowActivity' is obsolete: 'The System.Workflow.* types are deprecated.  Instead, please use the new types from System.Activities.*'

The workflow is pretty complicated so I'm hoping I can avoid recreating it. Do you know if MS has a solution that can migrate machine state workflows now that they're depreciated.

Many thanks,
ASKER CERTIFIED SOLUTION
Avatar of Bembi
Bembi
Flag of Germany image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
thanks bembi.

you're correct in that these are only warnings I'm receiving. However, when I try to deploy the solution from visual studio I receive the following error:

Error      11      Error occurred in deployment step 'Activate Features': Feature with Id 'ee97edfb-ba48-4c7c-8a25-99f017633be2' is not installed in this farm, and cannot be added to this scope.
            0      0      SharePointProject2


I've been deploying the wsp file through powershell to both the 14 and 15 hive and it appears to deploy correctly. but then the workflow doesn't work from my list. I've assumed it's due to these warnings, but I may be wrong.
Many thanks for the help. you helped me get to the bottom of my problem which was pure stupidity on my part - I forgot to activate my feature for the site.....

I'm still not able to deploy the solution from VS which is a problem for another day. I just need to activate it from Central Admin and then activate the feature on the site and I'm good to go. Hopefully my troubles save others time in the future.
Hi,

just another comment....
Deploying Solution from VS depend on some permissions on the one side and the correct VS Version on the other side...
SharePoint 2013 needs at least VS 2012 with some customizing or a higher version.
VS 2010 and VS 2012 supports  SharePoint 2010 while the higher versions do not anymore...
At least not our of the box.

Also VS should be installed on the machine with SharePoint.

Creating a deployment package and deploy it separately on SharePoint should work with all versions..., but you have to take care, for which  NET version you compile the package, as SPS 2010 uses NET 2.0 while SPS 2013 uses NET 4.0