Sharepoint - UserAgent not available, file operations may not be optimized

This error has the most simplest answer. I saw that pages in my SharePoint 2007 environment was customized using SharePoint Designer, Once I reset the page to site definition everything started working (without any errors).

I suspect that when the pages are customized in Designer, the HTML scripts for pages are taken as it is through database migrations, and SharePoint 2013 is not smart enough to render the customized pages based on old definition.

Learning, reset Designer customized pages to site definition in case site throws error after migration. This means that you will have to lose all your customization.

Please feel free to post any better answer, in case you find one...

Weird but true...

Tags:

Related

Sharepoint - Sharepoint Server 2013 installation: why ArpWrite action fails? Sharepoint - Wrong counts for refiner values in SharePoint 2013, Enterprise Search Center Sharepoint - No way to stop sending a welcome email when granting permissions in SharePoint 2013 Sharepoint - Manage Site Content and Structure in SharePoint 2013 Missing? Sharepoint - Best practice for deploying Site Columns and Content Type Sharepoint - Get All Items in a Folder (including ALL subfolders) Sharepoint - How to get rid of the "Edit links" link in the top navigation (SharePoint 2013)? Sharepoint - How can I authenticate SharePoint REST calls from JavaScript? Sharepoint - Site collection locked & stucked in read only mode Sharepoint - Rich text Editor (ribbon based) in a webpart in SharePoint 2013 Sharepoint - How to set start and end date in Timeline webpart in SharePoint 2013? Sharepoint - Server Error in '/' Application. Runtime Error

Recent Posts