03-11-2019 04:29 AM
03-11-2019 04:29 AM
we run a SharePoint Online site, where we have a number of workflows (2010) running mainly to generate documents etc in our automated workflows. All has been working fine, till today, when we had some modifications we wanted to execute on some of the 2010 workflows. We are using Sharepoint designer 2013. When saving the workflow, there are no issues, but when we try to publish we get an error (see attached) [Unexpected error on server associating the workflow]
Right now, we´re at a standstill, and I can not find any real relevant information online on this. Some "older" stuff on temporary files etc have been reviewed, but without success.
Pretty desperate now to get some help - Everything is much appreciated.
03-11-2019 06:41 AM
Our Service Health Dashboard has an entry for this:
03-11-2019 09:00 PM
Do we have any updates to this issue? few workflows in our production system are impacted.
03-11-2019 10:28 PM
+1 can we please have an update on resolving this. I've spent half a day isolating the issue to "not me" and was fortunate enough to find this post through Google.
These types of major issues deserve broader visibility to the affected people. It first occurred on Friday last week.
03-12-2019 12:29 AM
We have the same problem on our tenant.
I can't edit any 2010 workflow or publish new ones. I really hope that MS solve soon this problem.
03-12-2019 03:31 AM
It's actually worse for us - I have broken a business critical workflow by attempting to publish an updated version of it last week - due to the outage it is now no longer associated to the list, and cannot be run (it just gives a blank page with a "\" at the top of it).
03-12-2019 03:35 AM
This has/is been extremely poorly managed by Microsoft. We´ve got business critical workflows as well that are now no longer operational. And, there is very Little Comfort in the data shared by Microsoft on when this issue is fixed. Makes us reconsider using Sharepoint onward, as our financial loss for this outtage is quite considerable.
03-12-2019 03:37 AM
i find it remarkable that this type of issue can occur. I Believe not only our business but many other is also getting damaged by this kind of outtage. We´ve got business critical processes that are at standstill, causing significant financial/business damage.
03-12-2019 03:47 AM
To his credit, I don't think that @Kelly Jones works for Microsoft, but he does have access to Microsoft's service health dashboard (which I don't have and they don't publish online that I know of).
It is very poor service and service integration that there can be a global outage of this, which has lasted so long (coming up to a week now) with neither a public disclosure nor a private disclosure that permeates down to me as a business user / site collection admin (which is a service management integration issue between my support organisation and Microsoft, which exists in most if not all of their large corporate customers).
I also still don't understand why there is still a core functionality gap between SharePoint 2010 workflows and their replacements (2013 workflows and Flow) which also means we can't avoid relying on them to function - and have no possible workaround during this outage.
03-12-2019 03:50 AM
Google has now indexed another page with more details on this outage:
03-12-2019 04:32 AM
And not chasing @Kelly Jones - meerly venting frustation :)
03-12-2019 04:37 AM
03-12-2019 04:51 AM
No change in status that I can see. Still basically "we are working on it" and that's it.
03-12-2019 05:05 AM
Hey everyone - @DenisCheong is right. I'm just a Microsoft customer like the rest of you. :)
What I shared was the message that I saw in our Office 365 tenant's service health dashboard.
Currently, the message I see has this as the current status (Updated: 2019-03-11 19:08 (UTC)):
Current status: Our work to develop a mitigation solution is progressing as expected and is being treated at the highest priority. We'll provide a timeline for mitigation as soon as it becomes available.
03-12-2019 05:47 AM
03-12-2019 01:06 PM
Nothing changes. Any other news about the timing about the resolution of this issue?
I'm just migrate an intranet from on premise to cloud and tomorrow I'll start the training to the staff. It's not a good starting point what is happening. I hope MS guys understand soon as possible that for us who work with Sp it's difficult to explain to the rest of the world what is happening. Im sure that the trouble will be solved. But it's not a good thing that no one of us knows why that was happen and when MS will solve the problem. We have to explain it to other people. All the best. D.
03-12-2019 11:32 PM
03-13-2019 07:27 AM
Also disappointed with the management of this issue. I do have access to the Health Service for our tenant and there is nothing posted about this incident. Being unaware of the current situation, we tried to publish updates to several SP2010 workflows, which are now broken.
Feels very much like Microsoft is trying to hide this issue, which is having a huge impact on many businesses. And we do still need SP2010 workflows since both Flow and SP2013 are lacking some of the same functionality.
03-13-2019 02:39 PM
03-14-2019 04:16 AM
Well it's now officially a full week without this working, and we have ... nothing. No update, no ETR, just crickets, and nothing from my own organisation's "support" function.
I'm keen to understand how everyone else is dealing with the outage, what workarounds have you implemented - and how successful have they been?
Why are you still relying on SharePoint 2010 workflows?
For us - these are all new workflows developed in the last 12 months that require functionality that is only available in SharePoint 2010 workflows - creation of Document Sets (actually of content types derived from document sets, not document sets per se) and InfoPath forms-based input (for which there is still no sensible replacement available to me).
03-14-2019 11:46 AM
My team/organization is in the same boat as you...we just discovered this issue yesterday. This morning, we had a crucial business demonstration for a solution that leverages SPD2010 workflows due to the limitations of creating Document Sets within SPD2013. Luckily for us...we did not edit the previously published workflow to create Document Sets...no there was no issue with republishing. However, many other workflows for the same solution had to be re-written using SPD2013...took my team member literally all of yesterday and into the hours of early today to get the solution to a place where we could demonstrate functionality.
I've alerted my organizations regarding the issue at hand...hoping people are not foolish enough to go and edit their existing/published workflows in SPD2010.
03-14-2019 02:51 PM
03-18-2019 02:50 AM
Another problem with the publishing workflow to Content Type is that after the error during publishing the Workflow Settings page of the Content Type also returns an error.
03-18-2019 02:56 AM
@SlavaGorbunovIt's pretty abysmal to see that:
1. It's taking Microsoft TWO WEEKS to resolve this issue, even though they already have the fix after one (which in of itself is too long).
2. Microsoft are still only treating this as a "business day" priority - no updates to the record over the weekend, not important enough for 24x7 support?
I'm presuming that it didn't take them two weeks to break it in the first place, and it was their own change which caused it (which clearly means they have inadequate testing in place), and also ... if their own changed caused it, then why did they have no backout plan to roll back their change?
So much for agile.
03-18-2019 03:10 AM
Agree, this has been extremely poorly managed, and, especially as some workflow functionality just does not operate on the 2013 platform. This has definately been an event that has had tremendous impact on our business, and we´re looking at alternative ways forward, as a 2 week outtage with Little/no information is just not acceptable.
03-18-2019 02:39 PM
OK, the problem is still here.
This is unbelievable!
03-18-2019 02:48 PM
@Dahai FangThe link that I posted above is the only place I have found where the issue and resolution details are publicly available (and it is live updated each day). Current status (unchanged since Saturday):
######################################## Mar 18, 2019 05:27 PM UTC ######################################## Title: Unable to edit existing workflows or create new workflows User Impact: Users are unable to edit workflows or create new workflows in SharePoint 2010 using Designer and other protocols. More info: Users may receive the error: "Unexpected error on server associating the workflow," and "Errors were found when compiling the workflow. The Workflow files were saved but cannot run." As a result of this problem, you may be unable to execute the following tasks: - Activating features that contain out-of-the-box or custom 2010 workflows - Provisioning out-of-the-box or custom site templates that contain 2010 workflows Additionally, attempting to edit existing workflows may cause those workflows to become dissociated with their SharePoint list. We've developed a fix for this issue and are preparing to apply it across the affected environment. Affected customers are encouraged to refrain from attempting to edit existing workflows until our fix is deployed. Current status: We successfully deployed the fix to a test environment and have validated that our solution is effective. We're proceeding with deployment to the affected environment and are on track to complete this process by Saturday, March 23, 2019. Scope of impact: Impact is specific to SharePoint 2010 workflows. Any user attempting to edit existing workflows or create new workflows may be affected by this event. Estimated time to resolve: Based on current deployment progress, we expect this problem to be resolved by Saturday, March 23, 2019. Next update by: Wednesday, March 20, 2019, at 8:00 PM UTC
03-20-2019 03:58 PM
03-21-2019 02:38 AM
it´s still not functional on my end. Same errors as before. :\
03-21-2019 02:52 AM
03-21-2019 02:54 AM
i'll post an update here the minute our workflows can be deployed..
03-21-2019 09:58 AM
Was thrilled to see this blog. We are having the same issue and as of 1:00 PM 3/21/19 - it has not been corrected. I'll keep you posted
03-21-2019 03:24 PM
Incredible...my eyes may be deceiving me but I believe the fix has been deployed to my tenant/environment. I was able to edit and publish a SPD2010 workflow!
03-21-2019 03:29 PM
@Chih-Ang LinThat's great to hear ... it still doesn't work for us :(
03-22-2019 01:38 AM
we´ve managed to publish our workflow, and are now conducting functionality tests Before Rolling them out again. Man, this was one for the books..
03-22-2019 04:56 AM
@DenisCheong I was able to create and publish a SP 2010 workflow.
03-22-2019 06:47 AM
WOO HOO! We are finally up and running with 2010 workflows
03-22-2019 08:25 AM
@CindiCostello can you please tell us what you have done? tnk!
03-22-2019 02:11 PM
07-14-2019 09:23 PM
07-16-2019 05:37 PM