- Method 1 Programmatically change the security context of the ASP.NET worker process to a user who has the correct SQL Server permissions.
- Method 2 Change the default configuration of ASP.NET so that the ASP.NET worker process starts and runs under the context of a user who has the correct permissions in SQL Server.
- Method 3 Grant the correct permissions in SQL Server so that the ASPNET account (or NetworkService account, for an application that runs on IIS 6.0) has the appropriate access to the required resources.
Note This method will make all the Web applications on the server have the corresponding right on the computer that is running SQL Server.
Steps to reproduce the issue
- Create a new Microsoft Visual Basic .NET Web application on a computer that is running both ASP.NET and SQL Server.
- Add the following code to the Page_Load event of the Webform1.aspx page that was created by using the project:
Dim con As New System.Data.SqlClient.SqlConnection("data source=localhost;integrated security=sspi;database=northwind")
- Build the project, and then open the Webform1.aspx page in the browser.
- You receive the error message that is mentioned in the "Symptoms" section.
Article ID: 316989 - Last Review: May 22, 2009 - Revision: 1