SPD 2013 Workflow not working

Hello,
I'm running into a very interesting issue, we have a 2013 custom list that has some 2010 and 2013 workflows associated with it. Just until recently the workflows were working fine, but now only 2010 workflows are working.
I updated one of the 2013, tried to publish it but then I canceled the process of publishing it because I had to make a new update.... not sure if this flipped the switch on these but now even if I create new ones in SPD they will not run. Also if
I try to run in manually I get a message - "Something went wrong. To try again, reload the page and then start the workflow"(the option for start manually is enabled in SPD 2013). Any help on this will be greatly appreciated!

Hi Ghabib05,
According to your description, my understanding is that you got an error when you ran a SharePoint 2013 workflow.
Afer you made some change in your workflow, whether you re-published the workflow. if not, please publish it, then test again, compare the result.
Please create a new SharePoint 2013 workflow on the list, then test, compare the result.
If this issue only occurred on the specifical workflow, I suggest you create a new workflow instead of the problematic one.
If this issue occurred on all SharePoint 2013 workflow, you can try to re-register workflow service.
Best Regards,
Wendy
Wendy Li
TechNet Community Support

Similar Messages

2013 Workflow not working for tenant admin

Hi
I've been struggling with an issue developing a site for a client. They have their own SharePoint 2013 tenancy, which we can manage as a partner. I can log in to the site with my own company account linked to Office 365, and can do everything I need to in
terms of site administration.
However, I've run into a problem whereby although I can create and publish SharePoint 2013 workflows, I cannot run them successfully. If there is anything in the workflow such as writing to the history list, the workflow hangs with the status "Started"
and "Activity in progress" (no error message).
I've got around the problem by testing the workflow as a user from our client's tenancy, but I'm curious as to why my user doesn't work for this. It works fine for everything else, including SharePoint 2010 workflows. Is there some permission somewhere that
needs to be set, or is this by design?
Duncan

Hi Ganesh,
Based on your description, I recommend you verify the things below:
Check if the SharePoint search service account is added in the Windows Authorization Access Group in Active Directory.
Check if the non-admin users have permission to view the results searched.
Check if the inline search can work in lists’ pages or libraries’ pages.
Best regards.
Thanks
Victoria Xia
TechNet Community Support

SharePoint 2013 Workflows not working

Hi All,
I am currently attempting to get SharePoint 2013 workflows working, i have installed the workflow manager and linked it to SharePoint but when i run any 2013 workflow i get the following error:
RequestorId: 26c49394-eb06-737a-7fde-d5bbfe4f6505. Details: System.ApplicationException: HTTP 401 The remote server returned an
error: (500) Internal Server Error. {"SPRequestGuid":["8c76bcc4-3979-41a9-ae18-7221aa418528"],"request-id":["8c76bcc4-3979-41a9-ae18-7221aa418528"],"X-FRAME-OPTIONS":["SAMEORIGIN"],"SPRequestDuration":["24"],"SPIisLatency":["0"],"Server":["Microsoft-IIS\/8.0"],"WWW-Authenticate":["Bearer
realm=\"8de50181-fbf8-48a5-9cd6-5edb37403fbd\",client_id=\"00000003-0000-0ff1-ce00-000000000000\",trusted_issuers=\"00000005-0000-0000-c000-000000000000@*,[email protected]37403fbd\"","NTLM"],"X-Powered-By":["ASP.NET"],"MicrosoftSharePointTeamServices":["15.0.0.4569"],"X-Content-Type-Options":["nosniff"],"X-MS-InvokeApp":["1;
RequireReadOnly"],"Date":["Thu, 04 Sep 2014 09:46:31 GMT"]} at Microsoft.Activities.Hosting.Runtime.Subroutine.SubroutineChild.Execute(CodeActivityContext context) at System.Activities.CodeActivity.InternalExecute(ActivityInstance
instance, ActivityExecutor executor, BookmarkManager bookmarkManager) at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)
Its worth noting that 2010 workflow run without a problem.
Any help would be greatly appreciated
Thanks
Jamie

Hi,
Based on your description, my understanding is that when you ran SharePoint 2013 workflow, an error occurred.
You can try to re-register the Workflow Service.
Here is
a link about how to configure workflow for SharePoint Server 2013, you can use as a reference:
http://technet.microsoft.com/en-us/library/jj658588(v=office.15).aspx
Best Regards,
Lisa Chen

SPD 2013 Workflow - Create list item with people picker in other site collection

Hi all,
I read a lot of blogs and forum posts the last couple of days, but I seem to be stuck as to why my workflow is not working as expected - thus, I thought I would ask the experts :-)
Setup:
2 lists in 2 different site collections
http://svr-url/servicedesk/tickets
http://svr-url/projects/requests
SharePoint 2013 on Prem
I try to create a SPD 2013 workflow that creates a new item in list "requests" once a certain trigger is set in list "tickets". One of the fields I need to copy is the requestor = People picker field.
I did a web service call with a REST call to create a list item. All works well as long as I just stick to Title and other text fields, but filling in the "Requestor" fails with "Bad request".
I learned I need to use the "RequestorID" field and in a blog I read I need to put in the user id as Int32. So I set the parameters in the dictionary to integer. Still I get "bad request".
Another issue: as I have lists from 2 site collections, the user id differs for the same user.
/servicedesk: ID = 9
/projects: ID = 22
Additionally, the possibility exists that the user I try to set is not already existent in the /projects user information list.
How can I deal with that?

check this
http://community.office365.com/en-us/f/154/t/127887.aspx

Customer Workflows Not Working from SRM Inbox

Hi everyone,
We are upgrdaing our EBP v3.5 system to SRM 5.0 (SRM SERVER 5.5 SP 5).
We are using integrated ITS and have many bespoke workflows which need to executeable in the SRM inbox via the integrated ITS and ultimately the portal (EP 7.0).
We have various issues with our bespoke workflows not working. The 2 errors we have found are:
1. When the users click on the workitem from the SRM inbox they sometimes see 'Service Cannot be Reached' error.
2. Other times they see the workitem details with no user decision buttons shown.
3. Other times the user decision buttons are shown but if the user clicks on one, they see a blank page with text "workitem currently locked by user WF_BATCH" at the top. This is an 'advance with dialog' task which works fine via SAPGUI.
Any ideas on any of the specific issues, or anything which we need to do generally to get custom workitems to be executeable via the ITS?
Thanks a lot,
Nick

Hi abhijit,
I checked that but I set it to blank in debug mode..but its still disappearing...the button disappears after pressing enter on error message.
actually the BADI when I implemented there is one method where I set E_ADD_ON_ACTIVE flag to 'X' to bring that button(recommended by SAP). that method is not getting called...

SPD 2013 WorkFlow Status Column: Status Not Updated

We are having an issue with the status display of the SPD Designer Workflow status column which is a read only column added by SharePoint to show the status of the workflow. We have some SharePoint 2013 Workflows built using SharePoint Designer that are
attached to specific SharePoint Document Libraries. The expected behavior is for this column to show the workflow statuses (Not Started, Starting Workflow, In Progress and Completed.
Based on our observation this status is showing up although the column does get added for the Workflow that we have. Is there any other dependency for SPD Workflows that are attached to Document Libraries to show the status correctly? Any other settings/configurations
to be made?
Regards,
Vikram
Blog: http://dotnetupdate.blogspot.com |

Hi Venkadesh,
It is by design that 2013 workflow will show stage name in the workflow status column when
Automatically update the workflow status to the current stage name is checked.
And the workflow status column will be blank when Automatically update the workflow status to the current stage name is unchecked.
For existing workflows, the workflow status will still exists with the previous values after unchecking Automatically update the workflow status to the current stage name.
We can use Set Workflow Status action to update the workflow status value based on our needs.
Best regards,
Victoria
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Start a Task Process Action in SPD 2013 does not expand SharePoint Groups

I created a site workflow in SPD 2013, and added a "start a task process". I specified that the participants would be a group, the tasks would be created in parallel and "Assign a task to each member with groups" is checked.
I did check after the fact that "ExpandGroup" is "Yes" in the properties.
However, when executed, the group gets assigned a task, not individual users within the group.
I have seen other postings where others have the same issue, but no resolutions besides MS is investigating. Is this some issue with my setup? I have tried this in multiple environments with the same results.

Hi wangsy101,
According to your description, you create a workflow with “Start a task process” in SharePoint 2013 Designer, and the participants was a group, and you had make sure that the “ExpandGroup” was “Yes”. However, when executed, the workflow didn’t assign
the task to individual users within the group.
I reproduced the process, and in my testing , everything worked well.
When you start the workflow and view the workflow, you will see the Assigned to field is the group. And when you open the related tasks, you will note that there are some new tasks related to individual users within the group. It means that the “ExpandGroup”
works correctly.
If the issue still exists, please create an approval workflow with SharePoint 2010 Designer platform, and set the same configuration to test.
I hope this helps.
Thanks,
Wendy
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 2013 Workflow not available on Site created from Sharepoint 2013 Foundation Solution Template

If I create a template on SharePoint 2013 Foundation, then create a site on SharePoint Enterprise (or Office/365) fully configured to support SharePoint 2013 workflows. When I access the site through SharePoint Designer 2013, and attempt to create a workflow
SharePoint 2013 Workflows are not available -- you get message that SharePoint 2013 Workflow platform is not available because it is not configured on the server. This appears to be a bug in SharePoint Designer as the 2013 Workflows are available on the team
site on the same site collection. There is no reason that a site created from a SharePoint 2013 foundation template should have this restriction.   To make matters worse if you then save that site as a template on the SharePoint 2013 Enterprise (or
Office/365) system and create a new site from the that template you get the same issue.
Anyone know a workaround/fix to this issue.   Have imported the template into Visual Studio but I can not find any way in Visual Studio to enable SharePoint 2013 workflows.   A solution that involves Visual Studio import would work fine
for me.
Earllibby

Apparently you did not read my question very carefully.   The workflow manager is configured properly on this server and for the basic Team site in this site collection the full SharePoint 2013 workflows are available in SharePoint Designer 2013.
BUT they are not available on another site in the SAME SITE COLLECTION that was created from a solution template that was created on a SharePoint Foundation server.
Earllibby

Save conflict while trying to save or publish a SPD 2013 workflow (SP 2013 version)

Hi all, I have a problem while trying to develop a SharePoint 2013 workflow. I'm able to create a new workflow for a list (to save it) and I can confirm that it can run. Unfortunatelly, when I try to modify It (either just after creation or when opening
it later) I get an error while saving or publishing:
Errors were found when compiling the workflow. The workflow files were not saved.
Save conflict
Your changes conflict with those made concurrently by another user. If you want your changes to be applied, click Back in your Web browser, refresh the page, and resubmit your changes.
ULS doesn't show anything helpful but the same message with lots of stack trace pointing to a file save conflict.
Today, by accident I discovered that the workflow could be saved after it was open in SPD for nigth so I expect there may be some time lockout like when you access a document in a library from another domain (hope it's only 30 minutes).
I tried to re register the workflow service and even reinstalling and reconfiguring the workflow manager. This problem was present without the service bus and workflow CU, but now I have them installed as well.
Any suggestions?
Update:
I managed to publish the workflow after performing following steps:
1. Open the workflow and make modifications (save conflict occurs when trying to publish)
2. Reset IIS
3. Publish workflow (the workflow is saved successfuly)
Best Regards Wojciech Wróblewski Visit my blog (in polish):
http://wojciechwroblewski.wordpress.com/

Hi,
According to your post, my understanding is that you got “save conflict” error while trying to save or publish a SharePoint Designer 2013 workflow.
Please check whether the Central Admin > Manage Service Application-> “App Management Service” is started.
Please check whether the “Configure service application associations”, ”App Management Service” is already associated.
Then please check whether the “Manage Services on server” and the “App Management Service” is started.
If all the service are started, add executionTimeout property in web.config file to increase the timeout interval(Make a copy of the web.config file before editing anything).
For more information, please refer to this site:Fixed: SharePoint Designer Error - Unexpected error on server associating the workflow
In addition, if you develop a too complex workflow and try to compile it in SharePoint Designer then you might get the error if your workflow exceeds the complexity limit. To fix the error you will have to redesign and break them into multiple workflows
to achieve the business functionality.
More information:
http://wp.ahcheng.com/2013/03/23/error-were-found-when-compiling-the-workflow-the-workflow-files-were-saved-but-cannot-be-run/
http://www.sharepointpals.com/post/How-To-Identify-Complexity-of-SharePoint-2013-or-2010-Workflow-to-fix-errors-while-compilation
Best Regards,
Linda Li
Linda Li
TechNet Community Support

PowerView In Project Server 2013 is not working

Hi All,
I am working on environment with Project Server 2013. In report part i am not able to see or view only power view reports.
I am testing this with default report provided by Microsoft, where other reports (power pivot) are working fine.
My power view report is not showing any error, it is simply gets opened as blank sheet.
Quick replies and help will be appreciated.
Note: I have installed silver light latest version too.
Thanks
Abbas

I am also experiencing issues with this. After the approval task is completed, the Workflow gets cancelled with the following message
RequestorId: 60d96368-4cb4-b059-8086-604972a92e60. Details: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary. at Microsoft.Activities.Hosting.Runtime.Subroutine.SubroutineChild.Execute(CodeActivityContext context)
at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager) at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager
bookmarkManager, Location resultLocation)
All other desired workflow actions work as expected. Emails are sent, project is moved from stage to stage, however as soon as the workflow approval task is completed, either Approved or Rejected, the Internal Status is changed to Canceled and the
workflow fails.
What is interesting is when the Approval task is completed, the approver will receive an email notification that the task was CANCELLED or DELETED....
not COMPLETED, which is what would be expected.
Has anyone seen this - any potential resolution?

SharePoint Designer 2013 Workflow not sending e-mails

Hello everyone, it's me again.
I have a problem with my custom workflow. A simple workflow made in SharePoint Designer 2013 with a "Send Mail" action isn't actually sending any e-mails.
I am able to send mails with SharePoint 2013 with out-of-the-box workflows or alerts when sharing a page. The simple workflow is: Send Mail to TestUser after a new item has been created.
1) SMTP server has been configured and tested successfully, I am able to send mails
2) The workflow gets "Completed" status even though I didn't actually receive a mail
3) I double checked User Profiles and the e-mails are correct (I also checked in Active Directory)
4) The User Profile Sync. Service is running and I even did a full sync
5) Out of the box workflows are work perfectly fine
I have no explanation why custom workflows won't send a mail. I can perform other actions like "change workflow status".
Any help please?

Hi Ali,
Please check if "send mail" action does not work in both SharePoint workflow 2010 platform and SharePoint 2013 platform.
Please add the actions "log to history" before and after action "send mail" to check if the send mail action is performed.
And you can also add "pause for a duration" before the "send mail" action, see if it could help.
You may also check if there are some related ULS log.
Thanks
Daniel Yang
TechNet Community Support

Microsoft Office 2013 is not working on Windows 8

I downloaded Microsoft office 2 days ago. Since then Window 8.1 update has basically attempted to ruin my life. Since I attempted to download the update (which will not download properly no matter how many times I try) Microsoft office will not
open on my computer. All the apps are still there. But they simply will not open. I have tried going to the start and typing the stuff in safe mode, still nothing happens! Can someone please help me? I am beyond frustrated with my brand new computer,
Windows 8.1, Microsoft, and everything about this situation.

Hi,
Did only the Office suits not open or all the apps after you upgrading to Windows 8.1? Please do the following tests to narrow down the issue:
First test:
If only the Office suits could not be opened, please go to Office 2013 installed folder, such as C:\Program Files (x86)\Microsoft Office\Office15 and double click apps to open them.
If all the apps could not be opened, please press win+R and copy the path:
%windir%\explorer.exe shell:::{4234d49b-0245-4df3-b780-3893943456e1} to Windows 8 app folder double click apps to open them.
If they are both opened in folder, please try to unpin and repin apps on start screen.
If they still do not work, do the second test.
Second test:
If only the Office suits could not be opened, please try to re-install the Office 2013 to test.
If all the apps could not be opened, Please follow these steps to check the issue.
Step 1: Try App troubleshooter:
http://download.microsoft.com/download/F/2/4/F24D0C03-4181-4E5B-A23B-5C3A6B5974E3/apps.diagcab
Step 2: Re-register app files:
Run the following in a Command Window (CMD) to re-register the Store App:
powershell -ExecutionPolicy Unrestricted Add-AppxPackage -DisableDevelopmentMode -Register $Env:SystemRoot\WinStore\AppxManifest.XML
For your reference:
Fix Store App in Windows 8.1 (AppxManifest.XML)
http://blogs.msdn.com/b/notime/archive/2013/10/18/fix-store-app-in-windows-8-1.aspx
Step 3: If the issue still persists, please try to log on with local account and re-bind your Microsoft account in Windows Store to see what’s going on.
Hope these could be helpful.
Regards,
George Zhao
TechNet Community Support

Purchase order release strategy Workflow not working

Hi All,
I am working on PO Approval release strategy and it is not working fine . The release strategy set up is configured by my functional consultant . I just copied the standard workflow template WS20000075 and making changes to my custom workflow template . When ever po is created an event "RELEASESTEPCREATED" get triggered and the first approver receives an workitem and when he approves it goes to Second Approver and it is working fine . But when rejected then a notification email goes to initiator . Now when an initiator login into ME22N and made any changes ( even material text change ) in it then again "RELEASESTEPCREATED" event getting triggered . But I need to trigger my workflow only when there is change in PO Net value .
Kindly help me how to achieve this functionality .
Thanks and regards
Dilip

Hi Vikram,
There is already an existing entry for BUS2012 with event CHANGED against the change doc EINKBELEG .
Acutlly when login as initiator and try to change PO through ME22N here are my observations :
case 1: When Buyer click on " Cancel Reject " button and do any changes ( even text change ) then RELEASESTEPCREATED and CHANGED events are triggering . But since the event linkaged is set to RELEASESTEPCREATED workflow get restarted again.
Even the CHANGE event does'nt have 'RELEASECODE' as parameter to restart workflow .
Case 2: When Buyer doesn't click on " Cancel Rejection" buttion and do any changes then only CHANGE event get triggered
which do nothing since there is no event linkage .
Is to click on " Cancel Reject" button mandatory ? . But even though we make " Cancel Reject" as Button mandatory then RELEASESTEPCREATED Button triggering for any change but we need to trigger it for only net Value change .
Thanks and regards,.
Dilip Kumar

Workflow not working in Background Processing

Hi All,
I am relatively new to Workflow. Currently, I am creating Deliveries (preferably in background) once a Sales Order is created. I am using an ABAP Class as the object method to submit the sales order number to the delivery processing method (which just submits basic information to standard SAP transaction VL04). I found that if the execution of the delivery creation task is not in Background Processing (the user manually kicks off the Delivery creation in SBWP) the workflow works as expected and creates the deliveries. However, if the Background Processing is checked, the workflow does not process and does not create a delivery. Is there any specific reason as to why the workflow will not work in background?
Any help you can give would be greatly appreciated. Thanks.
John

Hi,
John
See to process a Back ground task, there should be a proper parameter flow.
Please look at the import parameters in the method you are using to process the back ground task..
If proper import parameters are passed then the task will work
This should help..
Thanks,
Shanky

Exchange 2013 ActiveSync not working

Hello everyone,
We seem to be having problems with our ActiveSync not working anymore. Users with mobile devices can not access their mailboxes. We have checked just about every setting and the IIS logs and can't find an answer to this issue. Microsoft's Remote Connectivity
Analyzer shows the following error which we can not find an answer for anywhere.
An ActiveSync session is being attempted with the server.
    Errors were encountered while testing the Exchange ActiveSync session.
   Test Steps
   Attempting to send the OPTIONS command to the server.
    Testing of the OPTIONS command failed. For more information, see Additional Details.
   Additional Details
    A Web exception occurred because an HTTP 400 - BadRequest response was received from IIS7.
Thanks!

Hi,
Did you ever find a solution to your problem? I have exactly the same problem with a fresh install of exchange 2013. Can access mailboxes via outlook 2010 and owa but can't connect any mobile device. I'm stumped...
a 400 IIS Bad Request error indicates token bloat. Are you proxying to 2010 mailboxes?
The usual fix is to set the following reg keys on the CAS receiving the requests following the first step described in this article that is similar:
http://support.microsoft.com/kb/2491354
Create the following registry keys on all CAS servers (both Exchange Server 2007 CAS servers and Exchange Server 2010 SP1 CAS servers) in the Active Directory site:
Path: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters
Name: MaxFieldLength
Type: DWORD
Value data: 65534
Path: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters
Name: MaxRequestBytes
Type: DWORD
Value date: 16777216
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

SPD 2013 Workflow not working

Similar Messages

Maybe you are looking for