Issue for creating a Microsoft Sever

Ignition
1

Had this pop up when I was trying to create a sever according to the Inductive University, anyone have any ideas?

Cannot create PoolableConnectionFactory (Login failed for user 'admin'. ClientConnectionId:c64ce8ea-fca2-4a24-b69e-05bf6875f138)

2

I mean... Is the password correct?

Login failed is pretty unambiguous.

3

Keep in mind that with SQL Server, you have to create a "login" and then associate that login to a database via a "user".

4

image
image1082×466 46.1 KB

Yes, I even copy paste to ensure it was

5

I was able to login on the SQL Server Management Studio a couple of times, but the Igntion never had a Valid status.

6

Another thing to check is in SQL Server Configuration Manager, make sure that TCP/IP protocol is enabled. I think that some installations of SQL Express may not default to enabling TCP/IP.

7

thank you for letting me know, yes, I have it set to enable already.

8

Not sure if OP ever got this working, but I'll share another simple reason that I've missed on multiple installs which results in this same error. By default, server authentication only supports Windows Authentication, which does not allow credentials created within SQL Server/SSMS.

In SQL Server Management Studio:

  1. Open up Server Properties (right click on server, top level, in your object explorer and select properties).
  2. Select the Security page within the resulting pop-up.
  3. Under Server Authentication, make sure SQL Server and Windows Authentication mode is selected.
  4. OK

You'll need to restart the DB in order for this change to take effect.

  1. Open SQL Server Configuration Manager software (must be on the host machine)
  2. Go to SQL Server Services page in the left explorer.
  3. Right click SQL Server (YOURSERVER) and choose restart.

Assuming you have a valid credential identical between Ignition and MS SQL Server and your other settings are correct, you'll likely have a valid database connection in Ignition. Hope this helps OP or anyone else in the future who also cannot yet use @pturmel's advice to avoid all this and just use PostgreSQL instead....

image
image711×257 9.83 KB

3 Likes
9

Some more info - useful if you need to connect via a Windows Login instead of a SQL Login

3 Likes