ASP.NET MVC应用连接本地SQL Server Express报错：连接尝试失败

Hey there, let's tackle this connection timeout issue you're hitting—this is a pretty common pain point with SQL Server Express and IIS setups, so let's go through the most likely fixes step by step:

• Double-check your connection string
  SQL Server Express uses the default instance name SQLEXPRESS, so make sure your connection string references it correctly. For local instances, valid server names are localhost\SQLEXPRESS, .\SQLEXPRESS, or your machine name followed by \SQLEXPRESS. Also, confirm if you're using Windows Authentication (Integrated Security=True) or SQL Authentication. If using Windows Auth, the IIS app pool's identity needs database access (more on that below).
  Example valid connection string snippet:

  Server=.\SQLEXPRESS;Database=YourTestDB;Integrated Security=True;
  

• Enable TCP/IP for SQL Server Express
  By default, SQL Server Express often has TCP/IP disabled, which can block connections even from local IIS. Here's how to fix it:

  1. Open SQL Server Configuration Manager
  2. Navigate to SQL Server Network Configuration > Protocols for SQLEXPRESS
  3. Right-click TCP/IP and select Enable
  4. Double-click TCP/IP, go to the IP Addresses tab
  5. Scroll to IPAll, set the TCP Port to 1433 (default SQL port)
  6. Restart the SQL Server (SQLEXPRESS) service from the Services app

• Grant IIS app pool identity access to SQL Server
  If your app is using Windows Authentication, the IIS app pool's built-in identity (like ApplicationPoolIdentity or Network Service) needs permissions to connect to your database:

  1. Open SQL Server Management Studio and connect to your SQLEXPRESS instance
  2. Expand Security > Logins, right-click and select New Login
  3. Click Search, enter IIS APPPOOL\[YourAppPoolName] (e.g., IIS APPPOOL\MyMvcTestApp) and click Check Names to validate
  4. Go to the User Mapping tab, select your test database, and assign the db_datareader and db_datawriter roles
  5. Click OK to save the changes

• Verify SQL Server service is running
  It sounds obvious, but sometimes the SQL Server Express service might be stopped or set to manual startup. Open the Services app, find SQL Server (SQLEXPRESS), ensure it's running, and set its startup type to Automatic.

• Test the connection outside of IIS
  To narrow down the issue, create a quick console app using the same connection string to try connecting to the database. If the console app works, the problem is likely with IIS permissions or app pool configuration. If it fails too, focus on SQL Server's network settings or connection string validity.

内容的提问来源于stack exchange，提问作者J Kaz