Migrated 2013 workflows are not working in new server
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
We had our SP 2013 applications in old server, so we migrated to new server with content DB approach. Now I see the 2013 designer workflows are having problem in executing the actions inside APP Step.I tried below steps to resolve but no luck.
Deactivated and reactivated 'Workflow Can use app permission' feature.Provided the Full control permission to Workflow app over appinv.aspx. Republished the WFs .
But If I create new test workflows inside in the site having App steps. Then it executes fine. Only the existing migrated WFs are having problem.
Please suggest me.
2013 sharepoint-enterprise designer-workflow app-step
add a comment |
We had our SP 2013 applications in old server, so we migrated to new server with content DB approach. Now I see the 2013 designer workflows are having problem in executing the actions inside APP Step.I tried below steps to resolve but no luck.
Deactivated and reactivated 'Workflow Can use app permission' feature.Provided the Full control permission to Workflow app over appinv.aspx. Republished the WFs .
But If I create new test workflows inside in the site having App steps. Then it executes fine. Only the existing migrated WFs are having problem.
Please suggest me.
2013 sharepoint-enterprise designer-workflow app-step
add a comment |
We had our SP 2013 applications in old server, so we migrated to new server with content DB approach. Now I see the 2013 designer workflows are having problem in executing the actions inside APP Step.I tried below steps to resolve but no luck.
Deactivated and reactivated 'Workflow Can use app permission' feature.Provided the Full control permission to Workflow app over appinv.aspx. Republished the WFs .
But If I create new test workflows inside in the site having App steps. Then it executes fine. Only the existing migrated WFs are having problem.
Please suggest me.
2013 sharepoint-enterprise designer-workflow app-step
We had our SP 2013 applications in old server, so we migrated to new server with content DB approach. Now I see the 2013 designer workflows are having problem in executing the actions inside APP Step.I tried below steps to resolve but no luck.
Deactivated and reactivated 'Workflow Can use app permission' feature.Provided the Full control permission to Workflow app over appinv.aspx. Republished the WFs .
But If I create new test workflows inside in the site having App steps. Then it executes fine. Only the existing migrated WFs are having problem.
Please suggest me.
2013 sharepoint-enterprise designer-workflow app-step
2013 sharepoint-enterprise designer-workflow app-step
asked Apr 1 at 12:40
Kailash SahooKailash Sahoo
474
474
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
You need to republish Workflows in the new site. WF2013 is not migrating with SP content DB they have their own DBs. You can either republish the workflows or try WF Scope Restore to new farm.
add a comment |
For workflow 2010, it is integrated with SharePoint Server and stored in content database. So you can automatically restore it by restoring the content database.
For workflow 2013, it requires Workflow Manager and must be installed separately and then configured to work with your SharePoint Server. SO you need to migrate the workflow manager.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "232"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsharepoint.stackexchange.com%2fquestions%2f260290%2fmigrated-2013-workflows-are-not-working-in-new-server%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
You need to republish Workflows in the new site. WF2013 is not migrating with SP content DB they have their own DBs. You can either republish the workflows or try WF Scope Restore to new farm.
add a comment |
You need to republish Workflows in the new site. WF2013 is not migrating with SP content DB they have their own DBs. You can either republish the workflows or try WF Scope Restore to new farm.
add a comment |
You need to republish Workflows in the new site. WF2013 is not migrating with SP content DB they have their own DBs. You can either republish the workflows or try WF Scope Restore to new farm.
You need to republish Workflows in the new site. WF2013 is not migrating with SP content DB they have their own DBs. You can either republish the workflows or try WF Scope Restore to new farm.
answered Apr 1 at 13:45
Marek SaradMarek Sarad
2,3951617
2,3951617
add a comment |
add a comment |
For workflow 2010, it is integrated with SharePoint Server and stored in content database. So you can automatically restore it by restoring the content database.
For workflow 2013, it requires Workflow Manager and must be installed separately and then configured to work with your SharePoint Server. SO you need to migrate the workflow manager.
add a comment |
For workflow 2010, it is integrated with SharePoint Server and stored in content database. So you can automatically restore it by restoring the content database.
For workflow 2013, it requires Workflow Manager and must be installed separately and then configured to work with your SharePoint Server. SO you need to migrate the workflow manager.
add a comment |
For workflow 2010, it is integrated with SharePoint Server and stored in content database. So you can automatically restore it by restoring the content database.
For workflow 2013, it requires Workflow Manager and must be installed separately and then configured to work with your SharePoint Server. SO you need to migrate the workflow manager.
For workflow 2010, it is integrated with SharePoint Server and stored in content database. So you can automatically restore it by restoring the content database.
For workflow 2013, it requires Workflow Manager and must be installed separately and then configured to work with your SharePoint Server. SO you need to migrate the workflow manager.
edited Apr 2 at 9:13
answered Apr 2 at 8:52
Michael Han_MSFTMichael Han_MSFT
2393
2393
add a comment |
add a comment |
Thanks for contributing an answer to SharePoint Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsharepoint.stackexchange.com%2fquestions%2f260290%2fmigrated-2013-workflows-are-not-working-in-new-server%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown