This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(224.00000000000003, 88%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJJ%3C/text%3E%3C/svg%3E)
I have an ASP.NET app, and when I launch the app and try to list items from a table by accessing the corresponding route, I get this error: SqlException: Cannot open database "appointments" requested by the login. The login failed. Login failed for user 'DESKTOP-KRBN07G\juan_'.
The database exists, and so do all the tables. I can connect to the database from SSMS and the 'Server Explorer' view in Visual Studio. I am using the connection string provided by the Server Explorer in Visual Studio. I also did a clean installation of Windows, Visual Studio, SQL Server, and SSMS. Currently, I have only one DB server and one database.
My VS and connection string:
And finally the error:
Please help me; this error is driving me mad. If you need any extra info, please let me know.
EDIT 1: I forgot to mention that I disabled my Windows firewall.
I'm glad to hear that you've found a solution to the problem.
I would like to suggest that you 'accept' the answer in the Thread. Doing so will conclude this Thread, increase its relevance, and better assist friends who have similar problems.
We will appreciate everything you have done. ^_^
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 61%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBS%3C/text%3E%3C/svg%3E)
you need to give the user "DESKTOP-KRBN07G\juan_" access to the database. I assume you are running VS as admin, which gives you back door access.
Thanks for answering. I didn't take that into account, but I just tried it and, sadly, I get the same error.
So you did not do in the right way.
CREATE LOGIN "DESKTOP-KRBN07G\juan_" FROM WINDOWS
USE appointments
CREATE USER "DESKTOP-KRBN07G\juan_"
Then you also need to grant the user the permissions needed to run the application. But with the above commands you will get a different error.
When I run that script, I get two errors: the first says that a login name 'DESKTOP-KRBN07G\juan_' already exists, and the second says that a user is already associated with that login name, which is 'dbo'.
I found out by using:
SELECT CURRENT *USER;
GO
that in both SSMS and VS, the user connecting to the database is 'dbo'. I deleted the database, created it again, and I* thought I successfully set 'DESKTOP-KRBN07G\juan' as the owner (check the picture). Then I ran the previous script again, hoping to see 'DESKTOP-KRBN07G\juan_', but that wasn't the case—it returned 'dbo' again. The app still fails and throws the same error of course.
Why VS connect as 'dbo' and not as 'DESKTOP-KRBN07G\juan_'?
The actions are being executed in the context of 'dbo' because the current user has 'dbo' level permissions. This is similar to the effect of 'SELECT CURRENT_USER'; it doesn't mean you didn't log in as 'DESKTOP-KRBN07G\juan_', it's just that your operations in the database are executed in the context of 'dbo'. If you want to see the actual login name, you should use 'SELECT SYSTEM_USER' or 'SELECT ORIGINAL_LOGIN()', which will return the Windows username you used to log in to SQL Server, rather than the user context at the database level.
If you are the owner of the database, or you are in the server role sysadmin, you username in the database is always dbo. And as dbo, you always have permission to connect to the database. (But the connection will fail if the database is in single-user mode, and there is already a connection to it. However, that does not seem to be the case.)
In one of your screenshots it looks funny, since you actually have a database user DESKTOP-KRBN07G\juan in parallel with dbo. It also seems funny, since it has a default schema of db_owner, rather than the usual dbo.
If you open a command line prompt and type:
sqlcmd -d appointments
What happens?
Anyway, I'm starting to lean towards that there is an issue in your source code, like an invisible character has sneaked into the database name in the connection string. So delete that line and re-type it to see what happens.
Also, I see that you are running an old build of SQL 2022 without any cumulative updates. You should download and install the most recent Cumulative Update to get access to many bug fixes and enhancements. You seem to have some GDRs installed. You may have to uninstall these to apply the CU.
Well, guys, I found the problem, it was a wrong and 'hidden' Connection String.
I created a new database with a different name, but the error in the browser after launching the app in my localhost kept pointing to the old database name.
After that, I searched for the old database name throughout the project and discovered that my colleague had added a partial class inside the DataAccess project of the ASP.NET application, which runs in development mode and contains his connection string.
I changed that, and now everything is working fine. All I knew was that the connection string should be in Program.cs or appsettings.json, and no other places.
Thank you @Erland Sommarskog and @MikeyQiaoMSFT-0444 for your time and guidance..¡
Well, guys, I found the problem, it was a wrong and 'hidden' Connection String.
I created a new database with a different name, but the error in the browser after launching the app in my localhost kept pointing to the old database name.
After that, I searched for the old database name throughout the project and discovered that my colleague had added a partial class inside the DataAccess project of the ASP.NET application, which runs in development mode and contains his connection string.
I changed that, and now everything is working fine. All I knew was that the connection string should be in Program.cs or appsettings.json, and no other places.
Thank you @Erland Sommarskog and @ MikeyQiaoMSFT-0444 for your time..¡
Well, guys, I found the problem, it was a wrong and 'hidden' Connection String.
I created a new database with a different name, but the error in the browser after launching the app in my localhost kept pointing to the old database name.
After that, I searched for the old database name throughout the project and discovered that my colleague had added a partial class inside the DataAccess project of the ASP.NET application, which runs in development mode and contains his connection string.
I changed that, and now everything is working fine. All I knew was that the connection string should be in Program.cs or appsettings.json, and no other places.
Thank you @Erland Sommarskog and @MikeyQiaoMSFT-0444 for your time..¡
Well, guys, I found the problem, it was a wrong and 'hidden' Connection String.
I created a new database with a different name, but the error in the browser after launching the app in my localhost kept pointing to the old database name.
After that, I searched for the old database name throughout the project and discovered that my colleague had added a partial class inside the DataAccess project of the ASP.NET application, which runs in development mode and contains his connection string.
I changed that, and now everything is working fine. All I knew was that the connection string should be in Program.cs or appsettings.json, and no other places.
Thank you guys for your time..¡
Well, guys, I found the problem, it was a wrong and 'hidden' Connection String.
I created a new database with a different name, but the error in the browser after launching the app in my localhost kept pointing to the old database name.
After that, I searched for the old database name throughout the project and discovered that my colleague had added a partial class inside the DataAccess project of the ASP.NET application, which runs in development mode and contains his connection string.
I changed that, and now everything is working fine. All I knew was that the connection string should be in Program.cs or appsettings.json, and no other places.
Thank you all for your time..¡
Well, guys, I found the problem, it was a wrong and 'hidden' Connection String.
I created a new database with a different name, but the error in the browser after launching the app in my localhost kept pointing to the old database name.
After that, I searched for the old database name throughout the project and discovered that my colleague had added a partial class inside the DataAccess project of the ASP.NET application, which runs in development mode and contains his connection string.
I changed that, and now everything is working fine. All I knew was that the connection string should be in Program.cs or appsettings.json, and no other places.
Thank you @Erland Sommarskog and @MikeyQiaoMSFT-0444 for your time and your guidance..¡
Well, guys, I found the problem, it was a wrong and 'hidden' Connection String.
I created a new database with a different name, but the error in the browser after launching the app in my localhost kept pointing to the old database name.
After that, I searched for the old database name throughout the project and discovered that my colleague had added a partial class inside the DataAccess project of the ASP.NET application, which runs in development mode and contains his connection string.
I changed that, and now everything is working fine. All I knew was that the connection string should be in Program.cs or appsettings.json, and no other places.
Thank you @Erland Sommarskog and @MikeyQiaoMSFT-0444 for your time..¡
Well, guys, I found the problem, it was a wrong and 'hidden' Connection String.
I created a new database with a different name, but the error in the browser after launching the app in my localhost kept pointing to the old database name.
After that, I searched for the old database name throughout the project and discovered that my colleague had added a partial class inside the DataAccess project of the ASP.NET application, which runs in development mode and contains his connection string.
I changed that, and now everything is working fine. All I knew was that the connection string should be in Program.cs or appsettings.json, and no other places.
Thank you @Erland Sommarskog and @MikeyQiaoMSFT-0444 for your time..¡