For example, the configuration file might look like: This makes it easy to work with multiple people on the same project (unlike other competing solutions).
The account to add in SQL Server is "IIS AppPool" (here "IIS AppPool\DefaultAppPool"):ĬodeFluent Entities provides several ways to define a connection string ( see documentation ). You must add the account of the AppPool:įirst thing: look at the pool application used by the site (here "DefaultAppPool"): The account displayed corresponds to the name of the machine followed by the "$" sign, but it is not this account that must be authorized in SQL Server. Unfortunately, the error message, although accurate, is not as explicit as it could be. This error occurs when the account running the website can not connect to the database. In case of error, a complete error message is displayed: $conn.ConnectionString = "Server=(local) Database=Sample Integrated Security=True " $conn.Open()
If this option is not possible (for example with a Windows Server Core Edition), it is still possible to use PowerShell: $conn = New-Object Open the created file ⇒ A window to enter the login information opens.There are many cases where we want to verify that the connection string used by an application is valid (in production of course ?).