topic Failed to connect to the specified DBMS instance. Bad login user (SQL Server) in ArcGIS Enterprise Questions

Failed to connect to the specified DBMS instance. Bad login user (SQL Server)

TimHayes2021 — Thu, 14 Apr 2022 16:25:46 GMT

I have created an Enterprise GDB in SQL Server 2019. I used OS Authentication (dbo, not sde) and the Create Enterprise Geodatabase Tool. There were no problems. But, I also want to do DB Authentication. To do this I need to create a new login in SQL Server Management Studio. I created a new login, assigned the password. Then created the schema as same name as the login. Example:

Schema: gisadmin

I assigned the roles as well.

Seems like it would work, but when I try to add new database connection in Catalog, I get a Connection Error message that says: Failed to connect to the specified DBMS instance. A database connection exception has occurred. Bad user login.

I checked SSMS and it allows Remote Connection and mixed with Windows and SQL Server Authentication modes. So that is correct.

I added the user to new database in SSMS as well.

Does anyone have an idea why it cannot connect to the database using Database Connection in Pro? Seems like the issue is SQL Server is not accepting a new login. I am the sa of the instance.

Re: Failed to connect to the specified DBMS instance. Bad login user (SQL Server)

AndrewFarrar — Fri, 15 Apr 2022 16:01:08 GMT

Can you login with that new user using just SSMS? take Catalog/Pro out of the equation first.

Re: Failed to connect to the specified DBMS instance. Bad login user (SQL Server)

TimHayes2021 — Fri, 22 Apr 2022 20:41:35 GMT

I found the answer. Restart the database in SQL Server Management Studio (SSMS). I did this with a test database and it did not affect anything. If you have views and other items in the database, you better double check what impact a database restart would have on these.