Common issues

I get a 403.16 Forbidden error

• Check that your root certificate is in the Trusted Root Certificates Authority store of the Local Computer, not the current user and that the Issued To and Issued By properties of the root certificate match.

• Ensure you imported the certificates into the Local Computer’s certificate store, not the current user’s certificate store.

• Ensure the certificate you created in IIS has a name that matches the site.

  For example, CM_test.

• Ensure you pasted your thumbprint into a PowerShell command line window, and that you removed the hidden character at the start of the string.

• Ensure your thumbprint is in uppercase letters.

  For example: 3D703B5198D6D3CEE1D0C1B1BC9ECB6D34989BA4.

  You can find the thumbprint in the following locations:

  • Sitecore\App_Config\ConnectionStrings.config
  • XConnect\App_Config\ConnectionStrings.config
  • XConnect\App_Data\jobs\continuous\AutomationEngine\App_Config\ConnectionStrings.config

• Ensure the self-signed certificate you created in IIS has the same name as your xConnect instance.

• Ensure the client authentication certificate (under the local machine’s Personal store) has read permissions for the IIS_IUSR group and the NETWORK SERVICE group.

My Solr index is empty

If you have an error that says your remote certificate is invalid according to the validation procedure, ensure that the indexer’s ConnectionStrings.config file is using localhost rather than 127.0.0.1 for the Solr core URL.

Microsoft.SqlServer.TransactSql.ScriptDom.dll is not installed

If this happens, you can see the following error: The SQL provider cannot run with dacpac option because of a missing dependency. To resolve this issue, see this Knowledge Base article.

My Sitecore installation failed while I was using Skype

If you use Skype while you are installing Sitecore Experience Platform, it is possible that your xConnect installation may fail. This occurs because Skype and Sitecore xConnect both use port 443, which interferes with the installation.

If this happens, change your Skype configuration as described in Microsoft’s documentation.

Failed installations

If an installation fails for any reason, you must clean up the partial installation before attempting another installation.

To clean up a partial installation, run the configurations again with the Uninstall-SitecoreConfiguration command with the same parameters as you used for the installation.

The createcert.json configuration file does not contain uninstallation tasks that remove certificates because it is highly likely that the certificates, particularly the root certificates, are used elsewhere.

To remove an incorrect certificate:

1. To open the Certificate Management console, in the Windows command prompt, enter certlm.msc and press Enter.

   To open the Certificate Management console for the Current User, enter certmgr.msc.

2. In the left pane, in the tree, expand the Personal node and select Certificates.

3. Select the incorrect certificate, right click it and then click Delete.

4. To remove the Root certificates, in the console, in the left hand pane, expand Certificates, Trusted Root Certification Authorities, Certificates and select the incorrect certificate, right click it and then click Delete.

After you have removed the failed installation, correct the errors in the launch script or configuration files before attempting a new installation.

The Indexing Manager shows no results after rebuilding the indexes

This can happen if the Solr managed schema is not populated properly during deployment.

To solve this problem, re-populate the Solr schema.

My Solr Schema is not populated

To populate the Solr schema:

1. On the Sitecore Launchpad, click Control Panel, and in the Indexing section, click Populate Solr Managed Schema.
2. In the Schema Populate dialog box, click Select all, and then click Populate.