SharePoint 2013 workflow deployment doens't update workflow definition

In Visual Studio 2013, we can develop SharePoint 2013 workflow and deploy directly in SharePoint. However, once a workflow is deployed and later modified and redeployed, the modified workflow definition doesn't take effects. Even if you retract the solution
and redeploy, the associated workflow with the sharepoint solution doesn't get updated in the SharePoint. Retracting the SharePoint solution then restarting the development server and finally redeploying will reset the workflow definition.

try this link:
https://connect.microsoft.com/VisualStudio/feedback/details/779905/sharepoint-2013-workflow-deployment-doenst-update-workflow-definition
http://www.sharepointeurope.com/blog/2011/8/30/5-easy-ways-to-turn-sharepoint-workflow-solution-into-a-failure-by-pawe%C5%82-wr%C3%B3bel-datapolis
http://ranaictiu-technicalblog.blogspot.in/2013/02/sharepoint-2013-workflow-manager.html
according to links workflow is cached in site so delete it from designer also.

Similar Messages

SharePoint 2013 - Team Foundation Server Dashboard Update job failed

Hi
I integrated TFS 2012 with SharePoint 2013 on Windows Server 2012. SharePoint 2013 farm have 3 WFE and 3 App servers
here what i did
Install TFS extension for SP 2013 on each of SP server and granted access of SP web application to TFS server successfully
in CA - I deployed TFS solutions (wsp) successfully) for wfe3 server
microsoft.teamfoundation.sharepoint.dashboards.wsp
microsoft.teamfoundation.sharepoint.dashboards15.wsp
microsoft.teamfoundation.sharepoint.wsp
I have a number of SC with TFS features activated and connect with TFS server project site working but I really don't know much about TFS.
What I see is there are 2 TFS timer jobs "Team Foundation Server Dashboard Update" for each of the web application (web1 and web2)
running every 30 minutes.
All jobs on web1 are running and succeed and ran on wfe1 and app3
but all jobs on web2 are failed and ran on wfe2, wfe3 and app1, app2 with the following error "An exception occurred while scanning dashboard sites. Please see the SharePoint
log for detailed exceptions"
I looked into the log file and it is show the same error but nothing more.
If anyone experience this or have any advice on how to resolve this, please share
Thanks
Swanl

Hi Swanl,
It seems that the Dashboard Update timer job will loop through the existing site collection, regardless if it is associated to a TFS site.
If one or more of this site collection is down/corrupted, this will cause the job to fail.
You can try the following step to check if the sites are good:
1. Go to Central Administration > Application Management > View all Site Collections. Proceed to click on each Site collection, and notice the properties for the site on the right hand site.
If the properties does not show up or errors out, this will need to be fixed.
2. Detach the SharePoint content database and reattach it to see if the issue still occurs.
Thanks,
Victoria
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Victoria Xia
TechNet Community Support

Sharepoint 2013 - Group task assignment from a workflow

I have designed a workflow, that can be started manually on a folder in SharePoint documents on a team site.
I would like the workflow to start, assign a task to a SharePoint group, and then have that task show up in the members of that groups Outlook.
I am able to assign tasks to a single user and have the task show up in an outlook task list.
However, when assigning to a SharePoint group, the tasks do not seem to show up in the outlook task lists.
Is this an impossibility, or is there a way to make this work?
Thanks,
Products in Use:
SharePoint Designer 2013
Visio 2013
(If needed I have visual studio, but would rather avoid it if possible. I am a programmer, but new to visual studio)

Hi Brandon,
If you are using “Start a task process” in workflow, please make sure that the “ExpandGroup” is Set to yes. Then the task will be generated for every member in the group. Please check if the task has been generated with members.
Here are some settings you should ensure:
All members have mailbox enabled in Exchange side.
The setting for “task show up in an Outlook task list” is the same for all members.
If it still doesn’t work, try it on SharePoint 2010 workflow. And also provide more information about your workflow and settings.
Regards,
Rebecca Tu
TechNet Community Support

Sharepoint 2013 (Danish): Deploying site from a custom template fails with error "Duplicate content type"

I cannot create a site-template in my own language (danish) and deploy a site based on the template.
I created a template from a "fresh" SharePoint project site with no tampering.
When trying to deploy a new site based on the templat I get the following error:
In Danish:
Beklager, men noget gik galt
Det blev fundet et navn på en dubletindholdstype "billede".
Tekniske oplysninger
Fejlfinding af problemer med Microsoft SharePoint Foundation.
Korrelations-id: 96646c9c-3213-a088-c6c4-537b0815313c
Dato og klokkeslæt: 21-06-2014 10:23:36
In English:
Sorry, something went wrong
A duplicate content type name "billede" was found.
Technical Details
Troubleshoot issues with Microsoft SharePoint Foundation.
Correlation ID: 0b656c9c-52ee-a088-c6c4-5132070e3c4e
Date and Time: 21-06-2014 10:31:35

Need details from ULS logs about Correlation ID: 0b656c9c-52ee-a088-c6c4-5132070e3c4e
Check below:
http://social.technet.microsoft.com/Forums/sharepoint/en-US/e955e737-e12e-4afa-b446-bb6e0f05e9b1/duplicated-content-type-error-creating-a-sharepoint-2010-site-from-a-custom-site-template?forum=sharepointgeneralprevious
http://aramacciotti.wordpress.com/2012/04/04/the-case-of-the-duplicated-contenttype/
http://community.office365.com/en-us/f/154/t/69416.aspx
If this helped you resolve your issue, please mark it Answered

Sharepoint 2013 Content Deployment Issue

I configured content Deployment from source farm to destination. The content is migarated from source to destionation and updates are went well. But when i update the attachement in Source, it is not getting updated in destination. I can find the below message
from import log
[2/18/2015 3:49:03 PM] [ListItem] [1_.000] Warning: Cannot add attachments because: The specified name is already in use.
The document or folder name was not changed. To change the name to a different value, close this dialog and edit the properties of the document or folder.
Please suggest me

Hello,
Looking at the last error message:
"The remote upload Web request failed"
there are a couple of possible reasons for this.
1. No space available on the destination web server
There needs to be enough disk space for the content to be uploaded to on the destination server. This is done in two stages - the first stage zips and copies the content to the destination server, and the second stage extracts the zip files and adds the
content to the destination server. You need enough space on the destination server to store the zip files and the extracted content.
2. Permissions on the destination server
The content deployment job needs to use a security account that has permission to the destination server farm to perform the deployment task.
3. Firewall/network settings
The destination server needs to be accessible by the source server.
Regards,
Gavin McKay

What Has Happened to Workflow in SharePoint 2013

I am at a loss to get workflow 2013 to work with SharePoint 2013. I am astonished that workflow (other than the broken and buggy 2010 version) is not part of SharePoint 2013. What on earth were they thinking. as if that is not bad enough they have managed
to break the installation of WorkFlow 2013. This has been reported numerous times by numerous people and needless to say the response from Microsoft has been complete silence.
In desperation I have just created a virtual machine with 2012R2 standard edition. I have installed (using the SharePoint 2013 +sp1 disk) the SharePoint Prerequisites. Next I follow the link they have provided to "optional software" where it
lists workflow manager. Instead of running an MSI or EXE they run the Web Platform Installer 5.0. After a bit of downloading and installing it tells me: "We're sorry. The following products have failed to install.
Microsoft Windows Fabric V1 RTM
This product did not install successfully: Invalid command line argument"
So SharePoint 2013 doesn't have workflow and this bug has been present since it came out and the web is filled with people asking about it.
Does anyone know how to fix this?

Thank you for that. You missed my point. I don't care whether it is embedded in SharePoint or a separate system. What I care about is that the installation/configuration is not included in the SharePoint installation. It is an optional extra.
We don't have to create the individual tables and databases in SQL and that is also a separate system. We don't have to configure IIS and that is a separate system so why is the installation and configuration of workflow not treated in the same way? That
is what I was getting at.
I most certainly have followed their instructions. Lets be honest they are very straight forward.
Microsoft's instructions are clear:
1. Download and run the Microsoft Web Platform Installer
2. Type "workflow" in the search box.
3. Click "Add" for the Workflow Manager V1 RTM
4. Click "Install"
Even if you download the workflowmanager.msi that just runs the web platform installer and searches for "workflow". Regardless of which you choose; now all you have to do is wait for the error message which comes shortly after this. I have just
typed this from memory after several hours in the pub so it is not that difficult. If you would care to point out where I have not "specifically follow[ed] the directions" I would be most grateful.
Now let me tell you what I have found. If I create a virtual machine with Windows 2012R2 and follow the instructions as outlined above it installs perfectly well. If I create another machine and install the SharePoint pre-requisites and then follow the instructions
as outlined above it does not install at all. Do you think this is because I am not running the web platform installer correctly? My latest experiment is to install it first and then install SharePoint. That seems to hold some promise of actually working
but if that works then the Microsoft installation instructions are wrong because they don't mention any of this until after SharePoint is installed.
Looking at the response from Dai Webb below it would seem that there is quite a lot that needs to be done that isn't mentioned in any Microsoft instructions or anywhere else that I have found. Perhaps that is the problem but if it is how come all those organizations
you mentioned have installed it? Did they know about this or is there yet another way of installing it?

Association Columns in Sharepoint 2013 Reusable Workflow

at http://msdn.microsoft.com/en-us/library/jj728659.aspx it says Association columns are not available in Sharepoint 2013 Workflow
But http://msdn.microsoft.com/en-us/library/dn292551.aspx#bkm_07 is suggesting to use Association columns in Sharepoint Server 2013. Doesn't Sharepoint Server 2013 uses Sharepoint 2013
Workflows?
Cheers, IXI solution

Hi,
According to your description, my understanding is that you want to know if the Association Columns can be used in SharePoint 2013 workflow.
Per my knowledge, the Association Columns feature is available only on the SharePoint 2010 Workflow platform.
The article in the link
http://msdn.microsoft.com/en-us/library/dn292551.aspx#bkm_07 introduces the best practices for developers using Visual Studio to create workflows in SharePoint 2013.
We can create 2010 workflows in SharePoint 2013 and we can use the
Association Columns feature in SharePoint 2010 workflows.
We can also integrate features from the SharePoint 2010 Workflow platform into the new SharePoint 2013 Workflow platform.
To do this, create a SharePoint 2010 Workflow by choosing the SharePoint 2010 Workflow platform; create a SharePoint 2013 Workflow by choosing the SharePoint 2013 Workflow platform; and then use the
Start a list workflow and Start a site workflow actions in the SharePoint 2013 Workflow to call the SharePoint 2010 Workflow.
If you have any questions, please feel free to reply.
Thanks
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Sharepoint 2007 Sharepoint Designer Workflow migrate to Sharepoint 2013

SharePoint 2007 sites migration to SharePoint 2013, in SP2007 I have several workflows created using SharePoint Designer. Is it possible to migrate those Workflows to SharePoint 2013? If so, is SharePoint 2013 Workflow
Manager needed to run those Workflows?
BTW, I will be using third party migration tools to migrate SP2007 content to SP2013.

Hi John
I know one third party tool which is best in migration and it migrates designer workflows also
http://en.share-gate.com/sharepoint-migration
http://en.share-gate.com/
Please mark it as answer if it helps you finding your answer
Amit Kotha

Team Foundation Server 2013.2 - SharePoint 2013 SP1 - Missing Server Side Dependencies

Environment:
TFS 2013.2 (update 2) on Windows Server 2012 R2, with MS SQL Server 2014 on the same machine;
SharePoint 2013 SP1 (with April 2014 update) on Windows Server 2012 R2
MS SQL Server 2014 on Windows Server 2012 R2 (Used by SharePoint)
Title
Missing server side dependencies.
Severity
1 - Error
Category
Configuration
Explanation
[MissingSetupFile] File
[Features\TfsDashboardAgileReports\Reports\Bug Progress.xlsx] is referenced [6] times in the database [WSS_Content_Internal], but exists only under Microsoft SharePoint Foundation 2010 setup folder. Consider upgrading the feature/solution which contains this
file to the latest version. One or more setup files are referenced in the database [WSS_Content_Internal], but are not installed on the current farm. Please install any feature or solution which contains these files.
[MissingSetupFile] File
[Features\TfsDashboardAgileReports\Reports\Bug Reactivations.xlsx] is referenced [6] times in the database [WSS_Content_Internal], but exists only under Microsoft SharePoint Foundation 2010 setup folder. Consider upgrading the feature/solution which contains
this file to the latest version. One or more setup files are referenced in the database [WSS_Content_Internal], but are not installed on the current farm. Please install any feature or solution which contains these files.
[MissingSetupFile] File
[Features\TfsDashboardAgileReports\Reports\Bug Trends.xlsx] is referenced [6] times in the database [WSS_Content_Internal], but exists only under Microsoft SharePoint Foundation 2010 setup folder. Consider upgrading the feature/solution which contains this
file to the latest version. One or more setup files are referenced in the database [WSS_Content_Internal], but are not installed on the current farm. Please install any feature or solution which contains these files.
And dozen more similar entries
The server is not in production, so I don't know if this error would cause any problems or not.
How to resolve this?
Thanks!
Fat Dragon

Hi
A colleague and I are looking at a similar issue on TFs 2010 upgraded to TFS 2013 which I guess is slightly different mssing dependencies given the project template. we're using
[MissingSetupFile] File [Features\TfsDashboardBaseUI\default.aspx] is referenced [1] times in the database [WSS_Content], but exists only under Microsoft SharePoint Foundation 2010 setup folder. Consider upgrading the feature/solution which contains this
file to the latest version. One or more setup files are referenced in the database [WSS_Content], but are not installed on the current farm. Please install any feature or solution which contains these files.
[MissingSetupFile] File [Features\TswaWebParts\WebParts\CompletedBuilds.webpart] is referenced [1] times in the database [WSS_Content], but exists only under Microsoft SharePoint Foundation 2010 setup folder. Consider upgrading the feature/solution which contains
this file to the latest version. One or more setup files are referenced in the database [WSS_Content], but are not installed on the current farm. Please install any feature or solution which contains these files.
[MissingSetupFile] File [Features\TswaWebParts\WebParts\GoToWorkItem.webpart] is referenced [1] times in the database [WSS_Content], but exists only under Microsoft SharePoint Foundation 2010 setup folder. Consider upgrading the feature/solution which contains
this file to the latest version. One or more setup files are referenced in the database [WSS_Content], but are not installed on the current farm. Please install any feature or solution which contains these files.
Will logon in a couple of days to test "Fat Dragon's" approach ( unless someone tells me different)
Daniel
Freelance consultant

SharePoint 2013 - document libraries and newsfeeds are visible when viewed using Internet Explorer running on the server but not from any other machine

On a single Windows 2012 R2 server I have installed SQL 2012 and SharePoint 2013 SP1 with the latest update roll ups. When I remote desktop to the server using the farm and site collection admin account and open page http://server_name_here using
Internet Explorer, I'm able to see newsfeeds and document libraries.
If I connected to a separate Windows 7 machine as the farm and site collection admin account and open page http://server_name_here using Internet Explorer, I'm able to view the SharePoint pages except I cannot see any newsfeeds or document libraries.
There's just blank space where they should be. I have repeated this process on several other machines that are not the server and get the same result on every machine (I've tried other servers, desktops, adding the SharePoint site to the trusted sites list
in IE, even using firefox). I'm using the same account as I did when I logged onto the server directly. Any thoughts as to what's going on?
Thanks!

Thanks for the idea, Harsh. What am I looking for?
It is currently set to the default of http://server_name and http://server_name:port_number (the latter is for Central Admin).
When I have access to the server, I have always done so the same way, using http://server_name. This was true when I access it from the desktop of the server itself and when I tried to access it from other desktops and servers (the machines where I had the
issues with the libraries and feeds not showing up). Are there other values I should add?
I have not tried to add http://server_FQDN as we don't plan on using that to access it but if you think it will help I would be happy to add it.

Modify Excel sheet from the sharepoint 2013 by remote event receiver

Hi,
I am new in sharepoint 2013.Actually i want to update excel sheet (that are stored in sharepoint library) by remote event receiver.
Please help me how to do this.
Thanks
Sanjeev Tiwari
Sanjeev Tiwari

The proper response is that it's not possible because Excel Interops are not supported running on a server. The technical answer is that you could find work-arounds including treating it as an Open XML object. In either case, I think you need to develop
the Excel processing component first and then connect to that the external event receiver.
Dimitri Ayrapetov (MCSE: SharePoint)

SharePoint 2013 Workflow Not Updating on Deployment

Developing a 2013 Workflow on SharePoint 2013 using Visual Studio 2012, deploying workflow changes does not update the workflow that runs. This has already been posted on the SP 2013 dev forum, but I wanted to check here with the workflow folks. Anyone run
into this issue before and/or have tips for solving?
Thanks.
http://social.msdn.microsoft.com/Forums/en-US/sharepointdevelopment/thread/cd543a00-f3ab-4a4a-8682-b81d8330b677
http://blog.randomdust.com

This issue is reported and I'll post about it once I have an update. For now to workaround this issue, you can try these steps
Change the default deployment option to “No Activation”
Retract the solution using Visual Studio
Deploy the solution. This time feature will not be activated by default as we have changed to “No Activation”
Open the SharePoint designer and click on the “Workflow” section. You will see your workflow already present there. Delete the workflow which you have created.
Activate the feature manually.
Now you should see your updated version.
Chandrasekar Natarajan

Updating In-Flight SharePoint 2013 Workflows (Visual Studio)

Is there any guidance on the best strategy for upgrading in-flight SharePoint 2013 Workflows? I am currently developing a SharePoint 2013 Workflow using Visual Studio 2012. The workflow has 6 phases and may take up to a month to complete.
I need a plan for when I will inevitably need to make a change to the workflow.
I am concerned that simply deploying a new version of a WSP with new XAML might cause a breaking change to in-flight workflows. This was a major problem in 2007/2010, and in the past I have created a new version of the workflow when deploying a change.
SharePoint 2013 designer workflows automatically create a new version when published, but unfortunately with Visual Studio workflows this is not the case. Updating the WSP and reactivating the feature will force new workflow code to run, but I think
this could cause issues when the workflow state data is de-serialized.

Hi,
According to your post, my understanding is that you want to update in-flight SharePoint visual studio workflow.
To update the in-flight workflow, such as in the production environment, we can do the steps as below(Make sure you test this first on a DEV server).
Updated the solution (Update-SPSolution)
Disabled the feature(Disable-SPFeature)
Enabled the feature again (Enable-SPFeature)
Then the existing workflow would use the old version workflow, the new workflow instances would use the new version workflow definition.
For more information:
https://social.technet.microsoft.com/Forums/en-US/f3ae607b-a16c-477e-9c2f-f0dc76f6849f/updating-sharepoint-2013-workflow-in-production-environment-not-during-development?forum=sharepointdevelopment
More reference:
http://sp2013workflows.blogspot.com/2014/06/update-workflow-definition-in.html
Thanks,
Jason
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Jason Guo
TechNet Community Support

Update Managed Metadata field in SharePoint 2013 Designer Workflow for O365

Hi Guys,
I need to update the managed metadata field in SharePoint Custom List using Workflow but its not working. I have also tried to use the HTTP WebService POST Operation but no luck.
Am doing this for a SharePoint Online (O365) Site.
Has anyone worked on something similar and was able to get it running ?
I saw a post to create a custom Workflow Activity but I don't have a choice to go with the custom code option.
http://patrickboom.wordpress.com/2013/07/23/workflow-activity-set-managed-metadata-column/
I was able to achieve this by creating a SP 2010 based Workflow for O365. Which means that it worked well with SP 2010.
Is there a different way to do it in 2013 ? I tried almost all options apart from creating custom Activity but nothing worked out.
Any help would be great.
Thanks,
Nutan
Nutan Sharma

Hi Nutan,
According to your description, my understanding is that you want to update Managed Metadata field with SharePoint 2013 Designer for SharePoint Online.
As far as I know, there is not an OOB action to achieve your requirement with SharePoint 2013 Designer for SharePoint 2013. Customizing a workflow action is a better option to achieve it. Why didn’t you customize a workflow action as Patrick’s blog?
In addition, please take a look at the article about Nintex workflow, check whether it is useful for you:
http://habaneroconsulting.com/insights/setting-managed-metadata-fields-in-a-nintex-workflow#.UykBSf6KDHo
As this issue is about SharePoint Online, I suggest you create a new thread on SharePoint Online forum:
http://social.technet.microsoft.com/Forums/en-US/home?forum=onlineservicessharepoint . More experts will assist you.
I hope this helps.
Thanks,
Wendy
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Wendy Li
TechNet Community Support

Update Column value after current item is Approved and then publish major version using Sharepoint 2013 designer workflow

Hi,
We have a requirement to update a column value once the item has been approved.
Following settings have been made in the publishing articles list:
Require content approval for submitted items : yes
Create major and minor (draft) versions
Who should see draft items in this document library? :Only users who can edit items
Require documents to be checked out before they can be edited? : yes
I have createdatu a Sharepoint 2013 workflow to check if Approval sts of current item = 0 i.e. Approved , then check out and update the item and finally checkin the item. Everything works fine till this point except that the minor version of the item is
checked in. Due to this the updated columns are not published to others.
Also, I created a Sharepoint 2010 workflow to SET CONTENT APPROVAL = APPROVED and started this workflow from my list workflow above, but the item does not get checked-in and always shows "In Progress" status with comment "The item is currently
locked for editing. Waiting for item to be checked in or for the lock to be released.".
Please let me know where I am missing out so that once the item is approved, column value gets updated and current item is still in Approved status.
Thanks

Hi,
According to your post, my understanding is that you want to update Column value after current item is Approved and then publish major version using Sharepoint 2013 designer workflow.
You will get into this kind of Catch-22 situation trying to set the Content Approval Status in SharePoint Designer workflow:
- You must check out the document before you can change the Content Approval Status
- You can't change the Content Approval Status once the document in checked out
Since you set the Require documents to be checked out before they can be edited=Yes, you will need to check out the document when run the workflow on the item. But you cannot approve a document when it is checked
out. So the logic in workflow conflicts.
As a workaround, you can use the Start Another Workflow action to start the normal Approval workflow on the document. The built-in Approval workflow can work with a document that’s not checked out.
The designer approval workflow also can work with a document that’s not checked out.
You can create two workflow using SharePoint Designer 2013.
First, create a SharePoint 2010 platform workflow.
Then, create a SharePoint 2013 platform workflow.
Then when the SharePoint 2013 platform workflow start, it will start the SharePoint 2010 platform workflow to set content approval status, then the SharePoint 2013 platform workflow will update current item value.
More information:
SharePoint Designer Workflow Content Approval Issue
SharePoint 2010 Approval Workflow with Content Approval
Best Regards,
Linda Li
Linda Li
TechNet Community Support

SharePoint 2013 workflow deployment doens't update workflow definition

Similar Messages

Maybe you are looking for