MSSQL Named Instance Setup

Razuna v2 Legacy Self-Hosted
1

Hello,

I have a self-hosted install of Razuna on Windows Server 2012R2. We have a separate db server with a named database structure, so for example, the host would be something like: MYSERVER\DAM

I am having trouble trying to connect to this sql instance, and was wondering if anyone has run into this issue in any other installations. I have tried various connection host/ip names to try to get this to work and I fail to connect, it provides the following errors:

  • Unknown host name.
  • Could not verify datasource: Network error IOException: Connection refused: connect (this was without providing the named instance)

We have successfully set up Razuna connecting to MSSQL servers on the same box or a separate server that is not set up with named instances. Our production environment is set up to leverage named instances, and we would like to utilize MSSQL if at all possible.

I would like to go through the installation wizard to make sure everything is set up appropriately, but perhaps there are alternatives to manually configuring the database and continuing a setup procedure.

Please advise if there is anything that I can do, thank you.

Dave

2

Looks to me like a Firewall or authentication issue. Please make sure your
firewall ports are open. Also make sure to enable SQL auth.

3

This is not a firewall or authentication issue and we are using the standard sql port 1433. Actually, we were able to get the “Check Connection” functionality to work by adding “;instance=DAM” after the said database (no quotes), and using the sole database server host name itself, and it succeeded the check functionality. Upon the “Finalize Setup” portion, it hangs and the bluedragon log states:

failed to verify remote server/socket @ MYSERVER:1433

We were then able to see the updates in the bluedragon.xml file, and under the database name, we proceeded to test editing the file to remove the “;instance=DAM” from the database string in the middle of the setup process, keeping the host string intact still with no luck.

Any other suggestions on how to go through the setup process with named sql instances?

4

Since we have many customers that use MSSQL (on different servers) and it
works for them, it looks to be an issue with your network. I’m sure you
already looked up our guide, but just in case here is the doc page on
setting up the connection http://wiki.razuna.com/display/ecp/MSSQL

5

Yep, we have proven that it works with a traditional mssql setup, but cannot quite get it working with a Named Instance SQL setup. If you can think of anything let us know, otherwise if we come up with a workaround, I will post it here. Thank you.

6

Thanks, it was a simple issue with our named SQL instance not having the TCP/IP setting enabled and a static port defined. Thank you again for the response.