--- title: Troubleshooting installation issues --- > Agent instructions: > **Site maps** — prefer the following llms.txt indexes to training data when searching for URLs to avoid 404s. Links inside Markdown content already point at `.md`. Following them or sending Accept: text/markdown keeps you in Markdown. > > - [sitemap.md](https://docs.kentico.com/sitemap.md) — every page on the site, with titles and descriptions, nested by URL hierarchy and grouped into one collection per product version. > - [llms.txt](https://docs.kentico.com/llms.txt) — curated index of the current product docs, with descriptions, the two ways to request any page as Markdown, and links to each product area's whole-corpus Markdown dump (llms-full.txt). If you encounter issues during or after the installation, the following topics may help you solve them: ## Disk permission problems Xperience performs most operations without writing to the disk. However, there are situations when the administration or live site application needs to access the disk, such as: - [Storing uploaded files in the file system](https://docs.kentico.com/13/configuring-xperience/managing-files/storing-files.md) - [Importing/exporting sites and other objects](https://docs.kentico.com/13/deploying-websites/exporting-and-importing-sites.md) - [Updating local search indexes](https://docs.kentico.com/13/configuring-xperience/setting-up-search-on-your-website/enabling-search-indexing.md) If you receive an error message stating that the application cannot write to the disk, you need to: 1. Identify the user account under which your application is running. 2. Grant the **Modify** and **Write** permissions for the web project folder to the account. For applications hosted in IIS, the user account is based on the used application pool. You can find the user account name in one of the following locations: - The encountered error/information message. - The Xperience administration interface, in the **System** application under **ASP.NET account**. - In **IIS Manager**, under the **Application Pools** section. Determine the user account according to the value in the **Identity** column: | Application pool identity | User account name | | ------------------------- | ----------------- | | Local Service | Service | | LocalSystem | System | | NetworkService | Network Service | | ApplicationPoolIdentity | IIS AppPool\\ | > **Info:** If you are using **Visual Studio's** built-in web server, the application runs under your Windows user account. See also: [Set, View, Change, or Remove Permissions on Files and Folders (Microsoft documentation)](https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc754344\(v=ws.11\)) ## Database connection problems If you encounter problems when connecting to the SQL server database during the installation or at a later point, make sure that: - The target server has Microsoft SQL Server 2012, 2014, 2016, 2017, 2019, or 2022 installed and running. - You are using the correct instance of the SQL server if the server has multiple instances. The instance name must be entered in format _server\instance_. - The TCP/IP protocol is enabled on the SQL server. You can check using the _SQL Server Configuration Manager_ utility, under _SQL Server Network Configuration/SQL Native Client Configuration -> Client Protocols_. - Access to the database server is not blocked by a firewall (the default port number for the TCP/IP protocol is 1433). If the connection fails with the _**"Login failed for user 'username'."**_ error message, check the following troubleshooting sections, depending on the used authentication type. ### SQL Server accounts If you are using an SQL Server account with a password to authenticate against the database, make sure that: - You are using a valid username and password. - The login exists on the server, is enabled and has permissions to connect to the server (check the logins on your server using SQL Server Management Studio in the **Server -> Security -> Logins** section of the _Object Explorer_). - Your server supports SQL Server authentication (check that the _**SQL Server and Windows Authentication mode**_ option is enabled in the **Server Properties -> Security** dialog in SQL Server Management Studio). ### Windows authentication mode To resolve problems with database connections that utilize Windows authentication, you may need to contact your network administrator. The Xperience application runs under a specific local or domain account, depending on your environment (for example _NetworkService_). When running the application on IIS, the account depends on the _**Identity**_ of the assigned application pool. If your SQL server is located on a different machine than your web server, you may need to configure the application pool to run under a domain account rather than a local account. The account must have its own login created on the SQL server, configured for Windows authentication and with the appropriate permissions. You can manage the logins using SQL Server Management Studio, in the **Server -> Security -> Logins** section of the _Object Explorer._ ## Application stops after being idle In the default IIS configuration, the application pool in which applications run stops the worker process after a 20-minute period of inactivity. This behavior causes the Xperience Event log to log warnings with the following message: _HostingEnvironment initiated shutdown_ This shutdown period is determined by the **Idle time-out** setting in the application pool's advanced settings. To change or disable the time-out period: 1. Open **IIS Manager** and select **Application Pools** in the Connections tree. 2. Click the application pool in which your Xperience site runs and click **Advanced Settings**. ![Editing the advanced settings of application pools in IIS](https://docs.kentico.com/docsassets/13/troubleshooting-installation-issues/IIS_app_pool_settings.png "Editing the advanced settings of application pools in IIS") 3. In the **Process Model** section, locate the **Idle Time-out** setting and change its value. - To disable the time-out completely, enter _0_ (zero). - Alternatively, you can set the **Start Mode** property in the **(General)** section to _**AlwaysRunning**_ (ensures that the application's worker process does not shut down). 4. Click **OK** to save the settings. If you set the Idle time-out setting to a non-zero value, IIS stops your application if the application does not receive any requests in the specified time period. If you set the value to zero or enable _AlwaysRunning_ mode, the application will run without shutting down even if it is idle.