Troubleshooting

Version: 2.4.1

This section describes some of the issues that you can encounter when using SIF and how to resolve them.

Internal server error

After a successful installation, the CM instance cannot be started and the following error is displayed:


HTTP Error 500.19 – Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.
Error Code 0x8007000d

To resolve this error, install the URL Rewrite module for IIS:

Error when you invoke the WebDeploy task

When you run Invoke-WebDeployTask, you might see the following error:

ERROR_SCRIPTDOM_NEEDED_FOR_SQL_PROVIDER

This error appears when the web deploy package uses the SQL DACFx framework to install the databases and the provider has not been registered.

To resolve this error, ensure that you have the components of the SQL Server correctly installed:

Note

If you are running the Sitecore installation from a 64-bit computer (x64), you must install both the 32-bit (x86) and 64-bit versions of the SQL Server components.

If you still receive the error after installing the SQL Server components, you must directly register the ScriptDom components.

To register the ScriptDom component:

  1. In Windows Explorer, go to the C:\Program Files (x86)\Microsoft SQL Server folder.

  2. The Microsoft SQL Server folder contains several subfolders. Click the subfolders (for example \90, \100, \110, \120, \130, \140) and find the \DAC\bin\Microsoft.SqlServer.TransactSql.ScriptDom.dll file.

  3. Copy or write down the path to the DLL file.

  4. Launch PowerShell and go to the C:\Program Files (x86)\Microsoft SDKs\Windows\v8.1A\bin\NETFX 4.5.1 Tools folder.

  5. Invoke the gacutil application and enter the path to the DLL file. For example:

    gacutil.exe /i C:\Program Files (x86)\Microsoft SDKs\Windows\v8.1A\bin\NETFX 4.5.1 Tools\120\DAC\bin\Microsoft.SqlServer.TransactSql.ScriptDom.dll

Missing modules

Some SIF features require that other modules are loaded as well. You might see warnings that certain tasks cannot be loaded when importing the module.

You can continue to use other features in the module, however, the features that displayed the warnings cannot be executed. For example, if the WebAdministration module is not available, you see the following warnings:

SIF-warnings.png

When this happens, the module is loaded but the following tasks are not available:

  • Invoke-AppPoolTask      
  • Invoke-WebBindingTask      
  • Invoke-WebsiteTask
Note

To install the WebAdministration module, you must first configure IIS on your computer. For more information about how to configure IIS, see the appropriate Sitecore XP Installation Guide.

Administrator permissions

To run SIF, you must run PowerShell as an administrator.

Important

If you try to use SIF in a non-administration window, you might see one of the following error messages and you will not be able to install Sitecore.

SIF-error-message1.png
SIF-error-message2.png

Sitecore installation failed while using Skype

If you are using Skype or another communication tool when you are installing Sitecore, the xConnect installation might fail. This happens because Skype and Sitecore xConnect both use port 443. If this happens, you must change your Skype configuration.

Another way to solve this issue is to update the default HTTP port, and if needed the HTTPS port.

Updating the default HTTP port

Updating the default HTTP port can be applied to the following Sitecore configurations:

  • All Sitecore configurations
  • All xConnect configurations

To update the default HTTP port:

  1. In a text editor, open the relevant configuration file, for example: sitecore-xp1.json.
  2. In the CreateWebsite task, add a Port property to the Params collection with the new value. For example: "CreateWebsite": {
If you have suggestions for improving this article, let us know!