So we need to give a proper rights to that user not ASPNET user. And If we sepcified It will run under the user name specified. If we specified in web.config file, by default It will run under IUSER_MACHINENAME if we allow anonymouse user. So to resolve this issue we need to create a user machinenameASPNET in database if not exists and need to give a proper rights to that user.
#Sql server connection string integrated security windows 10
System OS: Windows 10 64bit SQL Server: (LocalDB)MSSQLLocalDB (SQL Server ) Visual Studio: Visual Studio Community 2019 (v16.4.0) Iss. So by default It will run under the ASPNET Account. Related 5076 I apologize, I did not add enough details to explain myself on the prior issue. So there is no meaning to specified username & pwd in connection string if we are using windows authentication for sql server. But thats a bad idea.Īctually If we specified a username & pwd in connection string and we are using Integrated Security=SSPI (means windows authentication for SQL Server), its not gonna be used anywhere. If we change it to be the group of administrator account, It would work. When I ran the project I was getting Login Failed for machinenameASPNET. To do this I specified connection string “Data Source=EIISSQL1 initial Security=SSPI”.
Actually I wanted to connect the database using windows authentication. The advantage of this approach is that you are able to use the underlying.
Instead of SSPI, you can also use true (both are same). It means that you want to use your Windows Account to access SQL Server. Let me explain what I wanted to do and what I was doing. Answer: This is typically when connecting to SQL Server. I ran into an issue in my current projet when I set Integrated Security = SSPI in connection string.
0 kommentar(er)
