Sorry, something went wrong: can't load the application on this page

%3CLINGO-SUB%20id%3D%22lingo-sub-638849%22%20slang%3D%22en-US%22%3ESorry%2C%20something%20went%20wrong%3A%20can't%20load%20the%20application%20on%20this%20page%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-638849%22%20slang%3D%22en-US%22%3E%3CP%3EHello...hoping%20to%20get%20some%20assistance%20with%20an%20error%20reported%20this%20morning.%20An%20end%20user%20is%20unable%20to%20reach%20any%20of%20our%20newly%20created%20site%20pages%20within%20a%20Communications%20site.%20The%20site%20collection%20has%20been%20in%20production%20for%20quite%20some%20time%2C%20no%20other%20users%20are%20reporting%20the%20following%20error%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESorry%2C%20something%20went%20wrong%3C%2FP%3E%3CP%3ECan't%20load%20the%20application%20on%20this%20page.%20Use%20the%20browser%20Back%20button%20to%20retry.%20If%20the%20problem%20persists%2C%20contact%20the%20administrator%20of%20the%20site%20and%20give%20them%20the%20information%20in%20Technical%20Details.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETechnical%20Details%3C%2FP%3E%3CP%3EError%20details%3A%20Error%3A%20Flights%20are%20not%20initialized.%20Flight%20requested%3A%201338%3C%2FP%3E%3CP%3ECorrelation%20ID%3A%20a281df9e-d036-0000-3af2-a11fbe6b05e6%3C%2FP%3E%3CP%3EDate%20and%20Time%3A%205%2F23%2F2019%2011%3A21%3A35%20AM%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20had%20the%20end%20user%20reset%2Fclear%20out%20IE%20and%20Chrome%20browser%20cookies%2Fcache...still%20no%20go.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-638849%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-638912%22%20slang%3D%22en-US%22%3ERe%3A%20Sorry%2C%20something%20went%20wrong%3A%20can't%20load%20the%20application%20on%20this%20page%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-638912%22%20slang%3D%22en-US%22%3EDo%20you%20have%20by%20chance%20a%20custom%20WebPart%20in%20your%20home%20page%3F%20Is%20this%20error%20happening%20just%20in%20the%20home%20page%20or%20in%20all%20the%20site%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-639062%22%20slang%3D%22en-US%22%3ERe%3A%20Sorry%2C%20something%20went%20wrong%3A%20can't%20load%20the%20application%20on%20this%20page%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-639062%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F60%22%20target%3D%22_blank%22%3E%40Juan%20Carlos%20Gonz%C3%A1lez%20Mart%C3%ADn%3C%2FA%3EFrom%20what%20I%20could%20gather%2C%20the%20site%20pages%20in%20question%20has%20a%20web%20part%20for%20text%20and%20another%20for%20a%20small%20image.%20No%20other%20web%20parts%20are%20on%20the%20page.%20The%20pages%20resides%20within%20a%20sub-site.%20We%20are%20using%20these%20site%20pages%20are%20%22news%22%20article%20pages.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-658880%22%20slang%3D%22en-US%22%3ERe%3A%20Sorry%2C%20something%20went%20wrong%3A%20can't%20load%20the%20application%20on%20this%20page%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-658880%22%20slang%3D%22en-US%22%3EI%20have%20a%20similar%20error%20popping%20up%20in%20my%20tenant.%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20user%20is%20using%20a%20Page%20Viewer%20web%20part%20to%20display%20a%20page%20from%20a%20Modern%20SP%20Team%20Site%20on%20a%20classic%20SharePoint%20publishing%20page.%20The%20error%20is%20only%20showing%20up%20in%20IE11%2C%20the%20iframe%20is%20working%20fine%20in%20Chrome.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20noticed%20if%20you%20switch%20the%20IE11%20Document%20Mode%20emulator%20to%20Edge%20and%20reload%20the%20page%20this%20resolves%20the%20issue.%3CBR%20%2F%3E%3CBR%20%2F%3EChih-Ang%20-%20is%20your%20error%20only%20showing%20up%20in%20IE%3F%3CBR%20%2F%3E%3CBR%20%2F%3EThis%20method%20was%20working%20fine%20in%20IE%20and%20Chrome%20up%20until%20a%20couple%20of%20weeks%20ago.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-734452%22%20slang%3D%22en-US%22%3ERe%3A%20Sorry%2C%20something%20went%20wrong%3A%20can't%20load%20the%20application%20on%20this%20page%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-734452%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F229180%22%20target%3D%22_blank%22%3E%40Colin%20Steger%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F229180%22%20target%3D%22_blank%22%3E%40Colin%20Steger%3C%2FA%3E%26nbsp%3BI%20have%20the%20same%20issue%20trying%20to%20display%20a%20news%20page%20on%20a%20SharePoint%20page%20-%20any%20ideas%20on%20how%20to%20correct%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-734532%22%20slang%3D%22en-US%22%3ERe%3A%20Sorry%2C%20something%20went%20wrong%3A%20can't%20load%20the%20application%20on%20this%20page%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-734532%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F229180%22%20target%3D%22_blank%22%3E%40Colin%20Steger%3C%2FA%3EFrom%20what%20I%20could%20deduct%2C%20after%20spending%20some%20time%20with%20the%20end%20user%20who%20was%20experiencing%20the%20issue%2C%20it%20would%20appear%20to%20be%20browser%20and%2For%20operating%20system%20(OS)%20related.%20Until%20I%20was%20able%20to%20conduct%20a%20Skype%20screen%20sharing%20session%20with%20the%20end%20user%2C%20I%20was%20not%20aware%20that%20the%20person%20in%20question%20had%20Windows%207%20and%20IE10%20on%20their%20machine.%20After%20I%20cleared%20the%20end%20user's%20IE10%20cache%20and%20reset%20the%20browser%20settings%2C%20IE10%20still%20displayed%20the%20same%20error.%20However%2C%20Chrome%20started%20to%20work%20after%20the%20reset.%20It%20is%20also%20worthwhile%20to%20note%20that%20the%20end%20user%20in%20question%20had%20many%20legacy%20applications%20that%20depends%20on%20Windows%207%20and%2For%20IE10%20so%20that%20is%20why%20they%20never%20upgraded%20their%20machine%20like%20the%20rest%20of%20the%20enterprise.%20I%20also%20suspect%20that%20the%20end%20user%20may%20be%20missing%20some%20updates%20on%20their%20machine%2C%20which%20could%20have%20also%20contributed%20to%20the%20issue%20at%20hand.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-754704%22%20slang%3D%22en-US%22%3ERe%3A%20Sorry%2C%20something%20went%20wrong%3A%20can't%20load%20the%20application%20on%20this%20page%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-754704%22%20slang%3D%22en-US%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F314146%22%20target%3D%22_blank%22%3E%40MichaelMartin1%3C%2FA%3E%26nbsp%3Bare%20you%20using%20a%20custom%20master%20page%20on%20your%20site%3F%20I%20traced%20the%20issue%20back%20to%20a%20line%20of%20code%20in%20our%20master%20page%20that%20was%20forcing%20the%20pages%20within%20that%20site%20collection%20to%20open%20in%20IE10%20doc%20mode.%3CBR%20%2F%3E%3CBR%20%2F%3E%26lt%3Bmeta%20http-equiv%3D%22%22X-UA-Compatible%22%22%20content%3D%22%22IE%3D10%22%22%20%2F%26gt%3B%3CBR%20%2F%3E%3CBR%20%2F%3EChanging%20this%20to%20Edge%20seemed%20to%20have%20resolved%20the%20issue%20%26lt%3Bmeta%20http-equiv%3D%22%22X-UA-Compatible%22%22%20content%3D%22%22IE%3DEdge%22%22%20%2F%26gt%3B%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-840385%22%20slang%3D%22en-US%22%3ERe%3A%20Sorry%2C%20something%20went%20wrong%3A%20can't%20load%20the%20application%20on%20this%20page%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-840385%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F229180%22%20target%3D%22_blank%22%3E%40Colin%20Steger%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi%20was%20this%20issue%20ever%20solved%3F%20We've%20got%20the%20exact%20same%20situation.%3C%2FP%3E%3CP%3EIt%20just%20doesn't%20load%20the%20modern%20Sharepoint%20pages.%20The%20older%20ones%20are%20working%20just%20fine.%3C%2FP%3E%3CP%3EThe%20issue%20occurs%20in%20Chrome%2C%20IE%2C%20FF%20and%20Edge.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Hello...hoping to get some assistance with an error reported this morning. An end user is unable to reach any of our newly created site pages within a Communications site. The site collection has been in production for quite some time, no other users are reporting the following error:

 

Sorry, something went wrong

Can't load the application on this page. Use the browser Back button to retry. If the problem persists, contact the administrator of the site and give them the information in Technical Details.

 

Technical Details

Error details: Error: Flights are not initialized. Flight requested: 1338

Correlation ID: a281df9e-d036-0000-3af2-a11fbe6b05e6

Date and Time: 5/23/2019 11:21:35 AM

 

I had the end user reset/clear out IE and Chrome browser cookies/cache...still no go.

7 Replies
Highlighted
Do you have by chance a custom WebPart in your home page? Is this error happening just in the home page or in all the site?
Highlighted

@Juan Carlos González MartínFrom what I could gather, the site pages in question has a web part for text and another for a small image. No other web parts are on the page. The pages resides within a sub-site. We are using these site pages are "news" article pages.

Highlighted
I have a similar error popping up in my tenant.

The user is using a Page Viewer web part to display a page from a Modern SP Team Site on a classic SharePoint publishing page. The error is only showing up in IE11, the iframe is working fine in Chrome.

I noticed if you switch the IE11 Document Mode emulator to Edge and reload the page this resolves the issue.

Chih-Ang - is your error only showing up in IE?

This method was working fine in IE and Chrome up until a couple of weeks ago.
Highlighted

@Colin Steger @Colin Steger I have the same issue trying to display a news page on a SharePoint page - any ideas on how to correct?

Highlighted

@Colin StegerFrom what I could deduct, after spending some time with the end user who was experiencing the issue, it would appear to be browser and/or operating system (OS) related. Until I was able to conduct a Skype screen sharing session with the end user, I was not aware that the person in question had Windows 7 and IE10 on their machine. After I cleared the end user's IE10 cache and reset the browser settings, IE10 still displayed the same error. However, Chrome started to work after the reset. It is also worthwhile to note that the end user in question had many legacy applications that depends on Windows 7 and/or IE10 so that is why they never upgraded their machine like the rest of the enterprise. I also suspect that the end user may be missing some updates on their machine, which could have also contributed to the issue at hand.

Highlighted
@MichaelMartin1 are you using a custom master page on your site? I traced the issue back to a line of code in our master page that was forcing the pages within that site collection to open in IE10 doc mode.

<meta http-equiv="X-UA-Compatible" content="IE=10" />

Changing this to Edge seemed to have resolved the issue <meta http-equiv="X-UA-Compatible" content="IE=Edge" />

Highlighted

@Colin Steger 

 

Hi was this issue ever solved? We've got the exact same situation.

It just doesn't load the modern Sharepoint pages. The older ones are working just fine.

The issue occurs in Chrome, IE, FF and Edge.