Mar 15 2018 05:04 AM
Hi all -
We are operating in SharePoint Online, using modern libraries. Versioning is turned on, but every time we click to check the version history on a documents, we are greeted with, "Sorry, something went wrong", and no usable details provided.
Any ideas what is going on? It's a little scary not being able to access previous versions of our files.
Thanks!
Mar 15 2018 08:22 AM
Mar 15 2018 08:27 AM
Versioning is failing even with alternate browsers and computers. I even tried it on my home computer and got the same message. I double-checked that versioning is turned on in our libraries.
Here's the funny thing - It works on our old classic sites, just not our modern sites. I have no idea how to troubleshoot this.
thanks!
Mar 15 2018 08:27 AM
Mar 15 2018 08:35 AM
Dose the version works if you temporary switch back to the classic experience?
Mar 15 2018 08:44 AM
Sounds like I'm going to have to open a ticket with Microsoft. Clearing the browser history didn't help, nor did switching back to the classic version of the library. Weird!
Mar 15 2018 08:46 AM
Mar 15 2018 08:53 AM
Yep, tried that too, and keep getting the same vague error.
Apr 05 2018 01:30 PM
Apr 05 2018 01:50 PM
Turns out to be a little complicated. The library in question was created via a migration of an existing classic library using Sharegate. When the library migrated over, it omitted the default forms (apparently they were custom) - Edit.aspx, New.aspx, etc.
I was told to use SharePoint Designer to simply add these forms to the new modern library, but SPD won't let me do that on modern libraries (it throws an error), and apparently this task is not possible using SharePoint Online.
So end result is that I have to re-migrate all these libraries using brand-new-created-by-hand libraries, which I am not looking forward to. But the core issue is those missing default forms.
Nov 14 2018 07:31 AM
We are experiencing the same problem after a ShareGate migration..
Did you solve the problem? If yes, how?
Nov 14 2018 07:40 AM
After weeks of research and troubleshooting, I just had to rebuild and remigrate my libraries. Supposedly it had something to do with the way my libraries were originally set up, but to this day I've never been able to pinpoint what that issue was. I am not the one who built the original libraries, so I don't know what weird nuance threw everything off.
I do know that attempts to add form types to the new libraries failed in SharePoint Designer, and this was the #1 resolution that people sent my way.
Nov 14 2018 11:29 AM
SolutionI’m with Caite on this one, I ended up having to re-migrate the content while deliberately making sure absolutely nothing else was migrated beyond the files and their versions. No customized forms/views, no required features, etc.
Jul 24 2019 06:20 PM
We are experiencing the same issue with a ShareGate migrated library.
We used a workaround to access the document history by opening the file in Word and restoring the old version from there.
cheers
Lewis
Oct 16 2019 11:15 AM - edited Oct 16 2019 11:37 AM
if you were to run into this issue. Or wanting to make sure the forms are not "custom" but the true out of the box check this script https://github.com/bschlintz/Scripts/blob/master/Create-DefaultListForms.ps1
(currently just for lists but can easily be adjusted for libraries as well)
TC
Asia
Mar 19 2020 02:49 AM
Anyone confirms if this is resolved? any workaround?
I believe Solution is to re-create your library and upload data there.
cheers!
Apr 21 2020 10:44 AM
I resolve this issue by reset the DispForm.aspx page using SharePoint Designer.
- Open SharePoint Designer go to lyour site
- Click Lists and Libraries
- Click on your list or library
- on the right side, under forms, click New to create new DispForm.aspx and set at default
you might have to rename this page or just rename the old DispForm.apsx for this to work
* rename by Click All Files on the left, then click your library, click Forms, the rename the file
- That's all this should restore your view history
Apr 14 2021 01:42 AM
Apr 14 2021 07:52 AM
@Peter2wxinWhen I experienced the issue, it was modern online SharePoint.
Jun 16 2021 03:46 AM - edited Jun 16 2021 03:52 AM
I managed to get my migrated libraries version history working again.
My library is called "ORMS" and the version history was broken after we migrated using ShareGate
Here is what i did to fix it...
This worked for me so i am interested to hear if it works for others.
Nov 14 2018 11:29 AM
SolutionI’m with Caite on this one, I ended up having to re-migrate the content while deliberately making sure absolutely nothing else was migrated beyond the files and their versions. No customized forms/views, no required features, etc.