02-13-2019 06:18 AM - edited 02-13-2019 06:19 AM
02-13-2019 06:18 AM - edited 02-13-2019 06:19 AM
Has anyone had any issues when co authoring in either excel or word? Both programs crash unexpectedly, but with no warning or error message. Nothing shows in the event logs as to what happened. This only happens when co authoring, and only one user is removed from the doc, when they are removed, they still appear to be in the document to the other users in the doc at that time. Reopening the doc picks up where they left off, but its massively affecting production!
I currently have a ticket open with 365 support (Ticket #:12768014) but we dont seem to be getting anywhere at the moment.
Thanks in advance, Gary.
02-14-2019 11:59 AM
Yes, my coworkers and I have been having this issue for weeks. I've had to change my auto save setting to every minute so I don't lose any data when Word, Excel or PowerPoint crashes.
02-15-2019 07:58 AM
02-20-2019 02:21 AM
02-20-2019 04:38 PM
Yes, we have a client that has been having this issue. Here is what I've been able to find:
The underlying problem appears to be the Auto-Save feature added to OneDrive for Business in the fall coupled with having OneDrive sync to SharePoint enabled and allowed. All the documentation on coauthoring I have seen indicates that you need a shared source for the files, and on-prem SharePoint, O365 SharePoint, One Drive and OneDrive for Business are all candidates, but nothing says anything about if you have SharePoint synced with OneDrive.
That said, I also opened a ticket with Microsoft, and was verbally told, definitely opening from two different locations, (i.e. SharePoint and OneDrive) definitely WILL break coauthoring and cause the applications to crash. But there is NOTHING in print as of this writing that officially states that.
I think this is a scenario that Microsoft didn't think of, and didn't test, and the Office Suite has no error handling for.
Our only solution at the moment is to disable OneDrive sync to SharePoint, but I have one client that doesn't accept that answer, and getting detailed information involving all the possible parameters from end users is nigh on impossible.
02-22-2019 02:09 AM
02-22-2019 06:51 AM
Yes! I'm not the only one! My co-worker and I are having the exact same issue. Hopefully MS gets a fix out soon.
03-01-2019 02:57 AM
03-01-2019 08:02 AM
@gbrown481 Did you disable OneDrive sync? The issue seems to occur either when one user opens a file from OneDrive rather than Sharepoint AND/OR if "Use Office to sync files I open" is enabled in OneDrive.
Also, one of my colleagues was told by Microsoft yesterday that in order for Coauthoring to be fully supported, MS Office needs to be in the "monthly" update channel rather than "semi-annual targeted" because the feature set pushed out is different.
03-02-2019 02:16 AM
03-04-2019 01:27 AM
So glad to hear that we aren´t the only ones with this problem. My Word/Powerpoint crashes, whenever I am co-authoring with my colleagues. We have had the problem for about 2 months.
The app can run for 1 hour, then crash, then run for 1 min before crash. No pattern I can find.
I am getting desperate, thinking about going back to the old days, where you had local copies that was put together in the end.
I am still experiencering the problem :(
03-25-2019 11:04 AM
I've been having the same issue with two of my users. They are using co-authoring on excel and they always click 'open in excel' since not all the features they need are available on excel online. I have set them up on the same version. Both are on the semi-annual 1808 channel and on Ver. 10730.20304 and they still experience this issue.
04-23-2019 02:15 AM - edited 04-23-2019 02:36 AM
We have had the same issue now for about four weeks, and have raised the issue with Microsoft last week. We have navigated the tier 1 support and now are waiting to hear back.
04-23-2019 09:37 AM
I'm curious to see if this affects organizations who are 100% in the cloud or like mine that are in a transition state and have some on prem stuff along with some being in the cloud.
04-23-2019 09:49 AM
04-23-2019 09:58 AM
@gbrown481 I'd bet they just aren't reporting it anymore.
Our clients are still having the issue and we have an open ticket with Microsoft. They've had us recording the issue with a tool called the Problem Steps Recorder. Their next step is to do remote support of two users simultaneously while they are co-authoring so they can see the issue first hand.
Based on some of the responses above it seems like even when OneDrive isn't in play coauthoring is still buggy and unreliable.
I look forward to seeing a fix, but I'm not holding my breath.
05-03-2019 02:27 AM
Has anyone received *anything* tangible from MS yet? More users are complaining, senior mostly...
The reputation of SharePoint has taken a large battering at our organisation. I could have done without this.
05-07-2019 04:29 AM
Update... Microsoft have advised that they have released a new build of Office last week and that we should:
* Install the new build of Office
* Then perform an online repair
We are going to test this with one user who is commonly affected and will report back our findings.
05-10-2019 03:01 AM
Hi All - we have been testing this version new build of Office for a few days now, and we haven't been able to replicate the Word closing issue since. The user we were testing with was previously heavily affected, with documents almost always closing within an hour.
We are cautiously optimistic that this particular build has resolved the issue at hand, and will now begin to test further by installing this Office build for another two affected users.
07-29-2019 02:38 AM
We're having the same issue with PowerPoint when our users tried to co-authoring.
08-08-2019 05:01 PM
We had the same issue until last week, Powerpoint and Word files were crashing regularly for several users. We did log a case with Microsoft and they also didn't find anything substantial yet.
Last week, there was an Office 365 client update which got installed on the users' machine and since then no one has reported any issue with the file crashing. We tried to reproduce the issue with a couple of frequent users but still not finding it.
Version we are using: Semi-Annual Channel (Targeted): Version 1902 (Build 11328.20368)
Did anyone has the same behaviour, we are trying to find what fixed this issue and what exactly caused it?
08-18-2019 11:56 PM
Thank you @DC11604 for the feedback.
We've the same version of yours but we still have the same issue with PowerPoint.
We opened a ticket at Microsoft but they didn't fix the issue.
We'll check if we've an update on our client or we will try to force it in order to fix the bug.
08-22-2019 03:13 PM
It looks this issue has fixed by Microsoft in their recent Office 365 client update - https://docs.microsoft.com/en-us/officeupdates/semi-annual-channel-targeted-2019#version-1902-august...
Our MS engineer on the case informed the same and after the pilot deployment, the issue has fixed for all users.
11-21-2019 08:24 AM
The same here. We have 8 people to work together. All of us kept crashing. It was before an assignment and there were a lot of mistakes due to MS conversion error. At last, the document was unable to be opened any more. All of our work has lost!!! Well done, good for light co-work but bad for large team co-working. If MS still not solved it, Sharepoint is only for very small groups with up to 3 people. The productivity at this point is pretty low. Hopefully, we can see the updates many years later. Hehe @gbrown481
Anyone upvote the PO to let MS see this issue.
01-15-2020 06:59 AM
Hello all, @DC11604
I've been reading this topic with great interest since we are having the same issue as described here : as soon as you collaborate on a document, Word crashes unexpectedly.
I've seen that the Version 1902 (Build 11328.20392) patch should resolve the issue.
The problem is that we are one patch level ahead (Version 1902 (build 11328.20438)) and we still encounter this issue...
Is there something else I'm missing ?
Afaik, we are not using one drive (which seems to be a reason for crashing)
Thank you for your help.
02-19-2020 01:00 AM
@lknight-sjvh I wasn't able to resolve it yet, I'm lacking time to conduce some testings.
But I did contact Microsoft support who told me to upgrade to latest semi annual update.
The Version 1902 (Build 11328.20392) fixed the issue in the monthly channel update.
I'm on the semi annual update channel and it's possible that this channel didn't get the patch until a recent release I've yet to install.
So, it seems that the monthly channel fixed the issue in Version 1902 (Build 11328.20392), but the semi annual channel seems to still contain the issue in the Version 1902 (build 11328.20438)) I'm using
I still have to upgrade to latest semi annual channel release to see if it fixes the issue.