Migrations from an older version to a newer always can bring up some nice behaviour, which leads some Admins to bang his head on the table. Let me tell you that this won’t help you to resolve your issues. Especially if you getting an issue with Missing Server Side Dependencies in which a Site Template of the BICenterSite is missing something like the mossbisample.aspx. It tells you that the features are not installed in the SharePoint 2013 farm but it’s existing in the database.
Well, you enduser tells you that he cannot access the site, cause something went wrong.
After analyzing and googling you may find a forum like this, in which somebody made up a case with MSFT and wroted that it is due to a SharePoint Server bug. Well, if you tell this your enduser, i bet they will bang your head on the table.
Before that might happen, you should try the following.
In the site collection settings there is a point Site Collection Output Cache
If you click on this you can use those settings:
It might be enabled. Disable it and try to get on to the page again.
Hope it helps you.The article or information provided here represents completely my own personal view & thought. It is recommended to test the content or scripts of the site in the lab, before making use in the production environment & use it completely at your own risk. The articles, scripts, suggestions or tricks published on the site are provided AS-IS with no warranties or guarantees and confers no rights.