Login
Register
Contact
That typically means that the environment for the datasource hasn’t been configured quite right. Often the credentials aren’t correct or sometimes the MSSQL server hasn’t been configured correctly for IP traffic. A great way to quickly test this is to open up the environment file you are working with and navigate to the Data Source Connections tab. Select the Relational Database Connection that contains the datasource that is giving you trouble (in this case the Conversation datasource). On the General tab for the Relational Database Connection you will see the “Test Connection button. Press it and it will try to connect to the database. What you want to see is “Test connection successful”. If there is a problem, you will immediately see an appropriate error, helping you to diagnose the problem quickly without having to start the server over and over. Some example issues are:
|
1 2 |
Error: err.pool.resource.create Login failed for user nexjw. |
Probably your username or password used to connect is incorrect
|
1 2 |
Error: err.pool.resource.create Network error IOException: Connection refused: connect |
The NexJ Model Server can’t find the MSSQL Server. Your host or port may be incorrect. Also, if you haven’t configured MSSQL properly to allow IP traffic, you will receive this message. Launch the SQL Server Configuration Manager and ensure that TCP/IP is enabled for your server under Client Protocols. The setup of a SQL Server database is also described in our “funamentals” training materials.
|
1 2 |
Error: err.pool.resource.create Cannot open database analytics13 requested by the login. The login failed. |
You probably have the database name wrong or you haven’t created it yet.
Some useful documentation can also be found at Configuring a Relational Database Connection