# Ignition 8.1 MSSQL Express database connection issues **URL:** \ **Category:** Ignition\ **Tags:** database, ignition81\ **Created:** [August 2, 2024, 2:30pm UTC](https://forum.inductiveautomation.com/t/ignition-8-1-mssql-express-database-connection-issues/94115 "2024-08-02T14:30:02Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![Jeremy\_Lester](https://avatars.discourse-cdn.com/v4/letter/j/a587f6/32.png) [@Jeremy\_Lester](https://forum.inductiveautomation.com/u/Jeremy_Lester)\ **Post date:** [August 2, 2024, 2:30pm UTC](https://forum.inductiveautomation.com/t/ignition-8-1-mssql-express-database-connection-issues/94115/1 "2024-08-02T14:30:02Z")
I am having trouble connecting to my new blank sql database through the ignition gateway. I receive this error : Cannot create PoolableConnectionFactory (Login failed for user 'ignition'. ClientConnectionId:06f66d20-db57-4c34-b7a9-29a9146fc73a) I first attempted to setup the gateway using the default sa user on MSSQL but after having the issues I created and new user named "ignition" but the problem persist. The password is correct and I am wondering if there is a setting in the SQL database that may be wrong. Does anyone have any experience with this? ---
**Author:** ![YF129701](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/yf129701/32/60498_2.png) [@YF129701](https://forum.inductiveautomation.com/u/YF129701)\ **Post date:** [August 2, 2024, 2:45pm UTC](https://forum.inductiveautomation.com/t/ignition-8-1-mssql-express-database-connection-issues/94115/2 "2024-08-02T14:45:11Z")
Are you able to connect to it through SSMS? One thing I can think of is that when you use MS SQL Express, the service name is not MSSQLSERVER - it's something like SQLEXPRESS (I can't remember exactly). [Windows Services] ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/b/3b22b74faccf148bba035967ad7bb94e3d76202a.png) Here is where it comes in on the gateway (Connect URL): ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/b/6/b6d7695cc29397dc11b0536617d631892d361774.png) Also, if the database is truly empty, you may want to leave the Extra Connection Properties field blank until there is a database. ---
**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\ **Post date:** [August 2, 2024, 2:51pm UTC](https://forum.inductiveautomation.com/t/ignition-8-1-mssql-express-database-connection-issues/94115/3 "2024-08-02T14:51:38Z")
Also make sure you are not using LocalDB, and that you are conecting over TCP/IP > [@Database Connection - SQL Server 2017 Express LocalDB](https://forum.inductiveautomation.com/t/database-connection-sql-server-2017-express-localdb/31904/2): > > LocalDB does not accept TCP/IP connections which is what Ignition needs to use, even if it’s on the same computer. Use the standard version of Express. ---
**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\ **Post date:** [August 2, 2024, 3:12pm UTC](https://forum.inductiveautomation.com/t/ignition-8-1-mssql-express-database-connection-issues/94115/4 "2024-08-02T15:12:36Z")
Make sure in SQL Server Configuration Manager that under SQL Server Network Configuration/Protocols for (INSTANCE NAME) that TCP/IP is enabled. Also check under other tree sections that under client protocols that TCP/IP is enabled, but I think the server config is the most critical of those. ---
**Author:** ![Jeremy\_Lester](https://avatars.discourse-cdn.com/v4/letter/j/a587f6/32.png) [@Jeremy\_Lester](https://forum.inductiveautomation.com/u/Jeremy_Lester)\ **Post date:** [August 2, 2024, 3:15pm UTC](https://forum.inductiveautomation.com/t/ignition-8-1-mssql-express-database-connection-issues/94115/5 "2024-08-02T15:15:00Z")
![mssql](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/0/e0e2eb5c0a17edbc57d2ed2d5eb9493c29b057ea.png) ![ignitionsql](https://us1.discourse-cdn.com/inductiveautomation/original/3X/c/8/c8f0732f726c6dfd1352dbeb0d758c35a8f3aee3.png) I have attached snapshots of my sample database as well as the ignition config. The socket connection seems to be made but the error persist. I am wondering if my "name" field has the wrong info in it? ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [August 2, 2024, 3:17pm UTC](https://forum.inductiveautomation.com/t/ignition-8-1-mssql-express-database-connection-issues/94115/6 "2024-08-02T15:17:47Z")
You should also plan on regretting your choice of SQL Express. You will run out of space if trying to use this for production. You will suffer long-term performance problems if running this on the same server as the Ignition gateway. If you need a dev environment compatible with SQL Server, just use Microsoft's actual SQL Server, the free Developer edition (on a separate machine). If you need something free, use PostgreSQL or MariaDB. Really. ---
**Author:** ![YF129701](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/yf129701/32/60498_2.png) [@YF129701](https://forum.inductiveautomation.com/u/YF129701)\ **Post date:** [August 2, 2024, 3:20pm UTC](https://forum.inductiveautomation.com/t/ignition-8-1-mssql-express-database-connection-issues/94115/7 "2024-08-02T15:20:16Z")
No, the Name field should be fine. When you created the `ignition` user, did you assign the appropriate permissions so that that user can access the `CBTProduction` database? Also, as other folks pointed out, if you enable TCP/IP (which you must), you also will need to restart the SQLEXPRESS services. I don't know if you are able to do that / have already done it. If its a local DB, that's easy - if not, it can take some coordination. Here is how-to video from IU: [link](https://inductiveuniversity.com/videos/connecting-to-microsoft-sql-server-express/8.1). ---
**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\ **Post date:** [August 2, 2024, 3:31pm UTC](https://forum.inductiveautomation.com/t/ignition-8-1-mssql-express-database-connection-issues/94115/8 "2024-08-02T15:31:17Z")
You can't use the developer edition for production though, so unless this is a development system, stick with SQL Standard at a minimum for production (if you're required to use MS SQL, otherwise, there's better free options) ---
**Author:** ![Jeremy\_Lester](https://avatars.discourse-cdn.com/v4/letter/j/a587f6/32.png) [@Jeremy\_Lester](https://forum.inductiveautomation.com/u/Jeremy_Lester)\ **Post date:** [August 2, 2024, 3:31pm UTC](https://forum.inductiveautomation.com/t/ignition-8-1-mssql-express-database-connection-issues/94115/9 "2024-08-02T15:31:49Z")
Yes my ignition user has the same permissions as the sa user. My TCP/IP is also currently enabled and running. ---
**Author:** ![Jeremy\_Lester](https://avatars.discourse-cdn.com/v4/letter/j/a587f6/32.png) [@Jeremy\_Lester](https://forum.inductiveautomation.com/u/Jeremy_Lester)\ **Post date:** [August 2, 2024, 3:33pm UTC](https://forum.inductiveautomation.com/t/ignition-8-1-mssql-express-database-connection-issues/94115/10 "2024-08-02T15:33:43Z")
Yes this is just an in house proof of concept test which is why I went with SQL Express. If/when we decide to go live, we will be using full version. ---
**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\ **Post date:** [August 2, 2024, 3:34pm UTC](https://forum.inductiveautomation.com/t/ignition-8-1-mssql-express-database-connection-issues/94115/11 "2024-08-02T15:34:00Z")
You can always try using the SA user temporarily, but it looks like you may have not enabled mixed mode (sa account is disabled). You'll need to enable mixed mode for the logins to work. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/6/e69179b3efc23ae70a3eec887dcd3efb7ae94136.png) ---
**Author:** ![YF129701](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/yf129701/32/60498_2.png) [@YF129701](https://forum.inductiveautomation.com/u/YF129701)\ **Post date:** [August 2, 2024, 3:34pm UTC](https://forum.inductiveautomation.com/t/ignition-8-1-mssql-express-database-connection-issues/94115/12 "2024-08-02T15:34:10Z")
After you enabled it, did you restart the services? That's a key part of this as well. This will have to be done on the machine that SQL Server Express is installed. Hopefully this is a dev box on your local machine. Go to Start Menu -\> Services -\> SQL Server [Express] -\> Right-click -\> Restart (or Stop/Start). ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/1/a/1a6a2858a8335844a27f3e234b17aa2fc303dc67.png) ---
**Author:** ![Jeremy\_Lester](https://avatars.discourse-cdn.com/v4/letter/j/a587f6/32.png) [@Jeremy\_Lester](https://forum.inductiveautomation.com/u/Jeremy_Lester)\ **Post date:** [August 2, 2024, 3:49pm UTC](https://forum.inductiveautomation.com/t/ignition-8-1-mssql-express-database-connection-issues/94115/13 "2024-08-02T15:49:52Z")
Yes, I restarted after and have verified that my SQL server is "Running" and my SQL server browser is "Running". I did notice my SQL server agent is "Stopped" is that an issue? ---
**Author:** ![Jeremy\_Lester](https://avatars.discourse-cdn.com/v4/letter/j/a587f6/32.png) [@Jeremy\_Lester](https://forum.inductiveautomation.com/u/Jeremy_Lester)\ **Post date:** [August 2, 2024, 3:58pm UTC](https://forum.inductiveautomation.com/t/ignition-8-1-mssql-express-database-connection-issues/94115/14 "2024-08-02T15:58:40Z")
This was the issue. Thank you!