Forum Discussion
Excel/Word crashing when co authoring
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.
42 Replies
- I'm still having this issue on a weekly basis in 2022, we're on version 2002 (Build 12527.21104). My coworkers use the cloud versions of Word, Excel, Powerpoint - so it is only affecting me in the desktop apps. It would be great if Microsoft could resolve this thing for us.
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.
Hello gbrown481
We're having the same issue with PowerPoint when our users tried to co-authoring.
Environment :
- Microsoft Office 365 ProPlus v1902 build 11328.20138 Semi-annual targeted
- Microsoft Teams v1.2.00.17057 (64bit) last update on 27th of June 2019
- OneDrive 2019 19.033.0218.0012The user opens the file from Microsoft Teams with the client PowerPoint and after 5-6 mins It crashes.We opend a ticket to Microsoft and we're still wating for their answer.Do you have any idea to fix this issue please ?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?
Thanks
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.
I should hopefully be getting 1904 this week. I'll test things out.
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.
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.
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.
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.
Summary:-
- We produce large documents in a collaborative fashion, by finding a document in a SharePoint Online document library using the 'Edit in Word' feature.
- We have done this for a long time (co-authoring documents is a large part of what we do) and the issue has only started occurring (and with multiple people) within the last four weeks or so.
- We all use Windows 7, SharePoint Online, and Microsoft Office downloaded from Office365
- Within a random amount of time (sometimes a few seconds, sometimes an hour), Word just closes.
- End users do not have OneDrive installed or configured.
- Tested with multiple users, multiple computers, multiple documents, multiple document libraries and sites.
- Microsoft recorded a screen and was able to witness and acknowledge the behaviour twice. Hoping the issue gets escalated; we have a lot of angry users - which is frustrating when we have spent considerable efforts trying to build confidence in using SharePoint Online as a suitable platform for document collaboration
gbrown481 We face the same issue while we are now in the pilot stage of migrating to Office365.
Do you have any update?We are windows 10 / proplus monthly channel.
Thanks!
- Same issue still with Powerpoint, Excel and Word...
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.
Hi
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 :-(
