SOLVED

Version History broken in modern SharePoint "Sorry, something went wrong"

%3CLINGO-SUB%20id%3D%22lingo-sub-172098%22%20slang%3D%22en-US%22%3EVersion%20History%20broken%20in%20modern%20SharePoint%20%22Sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-172098%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20all%20-%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20are%20operating%20in%20SharePoint%20Online%2C%20using%20modern%20libraries.%20Versioning%20is%20turned%20on%2C%20but%20every%20time%20we%20click%20to%20check%20the%20version%20history%20on%20a%20documents%2C%20we%20are%20greeted%20with%2C%20%22Sorry%2C%20something%20went%20wrong%22%2C%20and%20no%20usable%20details%20provided.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAny%20ideas%20what%20is%20going%20on%3F%20It's%20a%20little%20scary%20not%20being%20able%20to%20access%20previous%20versions%20of%20our%20files.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-172098%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-286859%22%20slang%3D%22en-US%22%3ERe%3A%20Version%20History%20broken%20in%20modern%20SharePoint%20%22Sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-286859%22%20slang%3D%22en-US%22%3E%3CP%3EI%E2%80%99m%20with%20Caite%20on%20this%20one%2C%20I%20ended%20up%20having%20to%20re-migrate%20the%20content%20while%20deliberately%20making%20sure%20absolutely%20nothing%20else%20was%20migrated%20beyond%20the%20files%20and%20their%20versions.%20No%20customized%20forms%2Fviews%2C%20no%20required%20features%2C%20etc.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-286664%22%20slang%3D%22en-US%22%3ERe%3A%20Version%20History%20broken%20in%20modern%20SharePoint%20%22Sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-286664%22%20slang%3D%22en-US%22%3E%3CP%3EAfter%20weeks%20of%20research%20and%20troubleshooting%2C%20I%20just%20had%20to%20rebuild%20and%20remigrate%20my%20libraries.%20Supposedly%20it%20had%20something%20to%20do%20with%20the%20way%20my%20libraries%20were%20originally%20set%20up%2C%20but%20to%20this%20day%20I've%20never%20been%20able%20to%20pinpoint%20what%20that%20issue%20was.%20I%20am%20not%20the%20one%20who%20built%20the%20original%20libraries%2C%20so%20I%20don't%20know%20what%20weird%20nuance%20threw%20everything%20off.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20do%20know%20that%20attempts%20to%20add%20form%20types%20to%20the%20new%20libraries%20failed%20in%20SharePoint%20Designer%2C%20and%20this%20was%20the%20%231%20resolution%20that%20people%20sent%20my%20way.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-286655%22%20slang%3D%22en-US%22%3ERe%3A%20Version%20History%20broken%20in%20modern%20SharePoint%20%22Sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-286655%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20experiencing%20the%20same%20problem%20after%20a%20ShareGate%20migration..%26nbsp%3B%3CBR%20%2F%3EDid%20you%20solve%20the%20problem%3F%20If%20yes%2C%20how%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-179915%22%20slang%3D%22en-US%22%3ERe%3A%20Version%20History%20broken%20in%20modern%20SharePoint%20%22Sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-179915%22%20slang%3D%22en-US%22%3E%3CP%3ETurns%20out%20to%20be%20a%20little%20complicated.%20The%20library%20in%20question%20was%20created%20via%20a%20migration%20of%20an%20existing%20classic%20library%20using%20Sharegate.%20When%20the%20library%20migrated%20over%2C%20it%20omitted%20the%20default%20forms%20(apparently%20they%20were%20custom)%20-%20Edit.aspx%2C%20New.aspx%2C%20etc.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20was%20told%20to%20use%20SharePoint%20Designer%20to%20simply%20add%20these%20forms%20to%20the%20new%20modern%20library%2C%20but%20SPD%20won't%20let%20me%20do%20that%20on%20modern%20libraries%20(it%20throws%20an%20error)%2C%20and%20apparently%20this%20task%20is%20not%20possible%20using%20SharePoint%20Online.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESo%20end%20result%20is%20that%20I%20have%20to%20re-migrate%20all%20these%20libraries%20using%20brand-new-created-by-hand%20libraries%2C%20which%20I%20am%20not%20looking%20forward%20to.%20But%20the%20core%20issue%20is%20those%20missing%20default%20forms.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-179912%22%20slang%3D%22en-US%22%3ERe%3A%20Version%20History%20broken%20in%20modern%20SharePoint%20%22Sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-179912%22%20slang%3D%22en-US%22%3EI'm%20experiencing%20the%20exact%20same%20error.%20Was%20Support%20able%20to%20resolve%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-172209%22%20slang%3D%22en-US%22%3ERe%3A%20Version%20History%20broken%20in%20modern%20SharePoint%20%22Sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-172209%22%20slang%3D%22en-US%22%3E%3CP%3EYep%2C%20tried%20that%20too%2C%20and%20keep%20getting%20the%20same%20vague%20error.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-172204%22%20slang%3D%22en-US%22%3ERe%3A%20Version%20History%20broken%20in%20modern%20SharePoint%20%22Sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-172204%22%20slang%3D%22en-US%22%3EDid%20you%20switch%20back%20to%20classic%20view%20on%20your%20document%20libraries%20and%20tried%20it%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-172203%22%20slang%3D%22en-US%22%3ERe%3A%20Version%20History%20broken%20in%20modern%20SharePoint%20%22Sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-172203%22%20slang%3D%22en-US%22%3E%3CP%3ESounds%20like%20I'm%20going%20to%20have%20to%20open%20a%20ticket%20with%20Microsoft.%20Clearing%20the%20browser%20history%20didn't%20help%2C%20nor%20did%20switching%20back%20to%20the%20classic%20version%20of%20the%20library.%20Weird!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-172199%22%20slang%3D%22en-US%22%3ERe%3A%20Version%20History%20broken%20in%20modern%20SharePoint%20%22Sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-172199%22%20slang%3D%22en-US%22%3E%3CP%3EDose%20the%20version%20works%20if%20you%20temporary%20switch%20back%20to%20the%20classic%20experience%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-172193%22%20slang%3D%22en-US%22%3ERe%3A%20Version%20History%20broken%20in%20modern%20SharePoint%20%22Sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-172193%22%20slang%3D%22en-US%22%3EThis%20may%20sound%20a%20little%20basic%20but%20try%20clearing%20the%20browser%20history.%20Beyond%20that%20you%20should%20reach%20out%20to%20Microsoft%20Support.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-172192%22%20slang%3D%22en-US%22%3ERe%3A%20Version%20History%20broken%20in%20modern%20SharePoint%20%22Sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-172192%22%20slang%3D%22en-US%22%3E%3CP%3EVersioning%20is%20failing%20even%20with%20alternate%20browsers%20and%20computers.%20I%20even%20tried%20it%20on%20my%20home%20computer%20and%20got%20the%20same%20message.%20I%20double-checked%20that%20versioning%20is%20turned%20on%20in%20our%20libraries.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHere's%20the%20funny%20thing%20-%26nbsp%3BIt%20works%20on%20our%20old%20classic%20sites%2C%20just%20not%20our%20modern%20sites.%20I%20have%20no%20idea%20how%20to%20troubleshoot%20this.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Ethanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-172189%22%20slang%3D%22en-US%22%3ERe%3A%20Version%20History%20broken%20in%20modern%20SharePoint%20%22Sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-172189%22%20slang%3D%22en-US%22%3EI%20have%20just%20verified%20on%20one%20of%20my%20tenants%20that%20versioning%20is%20working%20as%20expected%20so%20it%20could%20be%20a%20problem%20of%20your%20tenant....have%20you%20tried%20to%20see%20the%20version%20of%20a%20document%20on%20another%20browser%20%2F%20PC%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-772693%22%20slang%3D%22en-US%22%3ERe%3A%20Version%20History%20broken%20in%20modern%20SharePoint%20%22Sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-772693%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F121378%22%20target%3D%22_blank%22%3E%40Caite%20Stevens%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20experiencing%20the%20same%20issue%20with%20a%20ShareGate%20migrated%20library.%3C%2FP%3E%3CP%3EWe%20used%20a%20workaround%20to%20access%20the%20document%20history%20by%20opening%20the%20file%20in%20Word%20and%20restoring%20the%20old%20version%20from%20there.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Echeers%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELewis%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-916968%22%20slang%3D%22en-US%22%3ERe%3A%20Version%20History%20broken%20in%20modern%20SharePoint%20%22Sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-916968%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F121378%22%20target%3D%22_blank%22%3E%40Caite%20Stevens%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Eif%20you%20were%20to%20run%20into%20this%20issue.%20Or%20wanting%20to%20make%20sure%20the%20forms%20are%20not%20%22custom%22%20but%20the%20true%20out%20of%20the%20box%20check%20this%20script%26nbsp%3B%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3E%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2Fbschlintz%2FScripts%2Fblob%2Fmaster%2FCreate-DefaultListForms.ps1%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2Fbschlintz%2FScripts%2Fblob%2Fmaster%2FCreate-DefaultListForms.ps1%3C%2FA%3E%3CBR%20%2F%3E%3C%2FFONT%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E(currently%20just%20for%20lists%20but%20can%20easily%20be%20adjusted%20for%20libraries%20as%20well)%3C%2FP%3E%0A%3CP%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3E%3CBR%20%2F%3ETC%26nbsp%3B%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3EAsia%3C%2FFONT%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1237575%22%20slang%3D%22en-US%22%3ERe%3A%20Version%20History%20broken%20in%20modern%20SharePoint%20%22Sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1237575%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F123714%22%20target%3D%22_blank%22%3E%40Asia%20Gandecka%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnyone%20confirms%20if%20this%20is%20resolved%3F%20any%20workaround%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20believe%20Solution%20is%20to%20re-create%20your%20library%20and%20upload%20data%20there.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Echeers!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1325939%22%20slang%3D%22en-US%22%3ERe%3A%20Version%20History%20broken%20in%20modern%20SharePoint%20%22Sorry%2C%20something%20went%20wrong%22%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1325939%22%20slang%3D%22en-US%22%3E%3CP%3EI%20resolve%20this%20issue%20by%20reset%20the%20DispForm.aspx%20page%20using%20SharePoint%20Designer.%3C%2FP%3E%3CP%3E-%20Open%20SharePoint%20Designer%20go%20to%20lyour%20site%3C%2FP%3E%3CP%3E-%20Click%20Lists%20and%20Libraries%3C%2FP%3E%3CP%3E-%20Click%20on%20your%20list%20or%20library%3C%2FP%3E%3CP%3E-%20on%20the%20right%20side%2C%20under%20forms%2C%20click%20New%20to%20create%20new%20%3CSTRONG%3EDispForm.aspx%3C%2FSTRONG%3E%20and%20set%20at%20default%3C%2FP%3E%3CP%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3Byou%20might%20have%20to%20rename%20this%20page%20or%20just%20rename%20the%20old%20DispForm.apsx%20for%20this%20to%20work%3C%2FP%3E%3CP%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B*%20rename%20by%20Click%20All%20Files%20on%20the%20left%2C%20then%20click%20your%20library%2C%20click%20Forms%2C%20the%20rename%20the%20file%3C%2FP%3E%3CP%3E-%20That's%20all%20this%20should%20restore%20your%20view%20history%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Contributor

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!

16 Replies
Highlighted
I have just verified on one of my tenants that versioning is working as expected so it could be a problem of your tenant....have you tried to see the version of a document on another browser / PC
Highlighted

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!

Highlighted
This may sound a little basic but try clearing the browser history. Beyond that you should reach out to Microsoft Support.
Highlighted

Dose the version works if you temporary switch back to the classic experience?

Highlighted

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!

Highlighted
Did you switch back to classic view on your document libraries and tried it?
Highlighted

Yep, tried that too, and keep getting the same vague error.

Highlighted
I'm experiencing the exact same error. Was Support able to resolve?
Highlighted

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. 

Highlighted

We are experiencing the same problem after a ShareGate migration.. 
Did you solve the problem? If yes, how?

Highlighted

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. 

Highlighted
Solution

I’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.

Highlighted

@Caite Stevens 

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

Highlighted

@Caite Stevens 

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

Highlighted

@Asia Gandecka 

 

Anyone confirms if this is resolved? any workaround?

 

I believe Solution is to re-create your library and upload data there.

 

cheers!

 

Highlighted

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