Contents
Even after you test the upgrade process to identify potential issues, you might experience unexpected issues during an upgrade from SharePoint 2010 Products to SharePoint 2013. If you experience issues after upgrade, the sooner you detect and fix them, the better the end-user experience will be.
For example, additional style sheets that you must have for SharePoint 2010 Products should be installed in the /14 path, not the new /15 path so that site collections that you have not upgraded can use them. Also, make sure that that you transfer all unique settings from the Web.config files for each web application to the new servers.
How to restart database upgrade in SharePoint 2013?
For more information about how to resume upgrade, see Restart a database-attach upgrade or a site collection upgrade to SharePoint 2013. Check the upgrade status to see where upgrade stopped (if it did stop), and check log files to find errors or warnings. Next, address the issues that you find before you resume the upgrade.
Here are all the CSS reference charts I have encontered so far. http://blog.sharepointexperience.com/2013/05/sharepoint-2013-css-classes-that-suck-and-save-the-day/ We might be able to get it together! It’s help you ? Thanks for contributing an answer to SharePoint Stack Exchange! Please be sure to answer the question.
For example, a missing server-side file can cause many seemingly unrelated errors at the site level. Address issues in the following order: Missing server-side files or customizations, such as features or Web Parts. Be sure to install all server-side customizations, such as features, Web Parts, and so on.
Can a site upgrade fail because of an operational problem?
A site upgrade can fail because of existing operational problems. Before you upgrade a site, install any critical software updates for each applicable site system. If an update that you install requires a restart, restart the applicable computers before you start the upgrade.