Troubleshooting installation and upgrade
Updated: December 9, 2016
Applies To: Dynamics 365 (on-premises), Dynamics CRM 2016
This section describes how to troubleshoot installation and known issues.
Setup creates log files that can be reviewed and used for troubleshooting. The log files are produced in clear unstructured text or xml and can be viewed by a basic text editor, such as Notepad. By default, the location of the log files, where User is the account of the user who ran Setup, is as follows:
By default, Windows Server hides the folders where the log files are located. To view these folders, go to Folder Options in Control Panel to change the setting so you can view these folders.
Microsoft Dynamics 365 Server Setup generates several distinct log files, depending on whether the installation is for a new deployment or an upgrade from a previous version.
Crmserversetup.log. The file that contains most of the Microsoft Dynamics 365 Server installation or upgrade activity.
Crmsetup.log. The file that contains Setup update (self-healing Setup) activity.
LegacyFeatureCheck.xml. During Microsoft Dynamics 365 Server upgrade, Setup analyzes the deployment for outdated (legacy) customization and extensibility features, such as Microsoft Dynamics CRM 4.0 plug-ins or solutions that use the 2007 web services endpoint. This file contains the results.
SrsDataConnectorSetup.log. The file that contains most of the Microsoft Dynamics 365 Reporting Extensions installation activity.
© 2016 Microsoft. All rights reserved. Copyright