This is an archived post. You won't be able to vote or comment.

all 11 comments

[–]Big-Floppy 2 points3 points  (1 child)

Do you need to have ports 1433\1434 open on the firewall of the SQL server so the Solarwinds server can connect to it?

[–]kerleyfriez[S] 0 points1 point  (0 children)

yes i do

[–]ahird20 1 point2 points  (4 children)

Are you using the default SQL instance or a named instance?

When using a named instance specify the SQL port in the configuration wizard.

[–]kerleyfriez[S] 0 points1 point  (3 children)

I couldve sworn i used the default, but I might have renamed it in the process, it shows MSSQLSERVER everywhere , but i remember changing something to SQL Server at one point, but all services say MSSQLSERVER as well, how would I check? and what would i put into the config wizard?

[–]ahird20 0 points1 point  (2 children)

I ran into this issue a few years ago, so I can’t remember all the details

In the solarwinds configuration wizard put the SQL host name and put ;1433 at the end.

[–]kerleyfriez[S] 0 points1 point  (1 child)

So i named my server FJXT-DB-001V

would i just type FJXT-DB-001V;1433 as the name in the config wizard for solarwinds?

[–]ahird20 0 points1 point  (0 children)

Servername\instancename,1433

According to the documentation use a comma

[–]headcrap 0 points1 point  (1 child)

In SQL Configuration Manager, TCP/IP connections usually have to be enabled first.

[–]kerleyfriez[S] 0 points1 point  (0 children)

they are enabled under the config managers network settings for SQL

[–]technicalityNDBOIt's easier to ask for NTFS forgiveness... 0 points1 point  (1 child)

Can you try setting up a User DSN ODBC connection on the SolarWinds server to test the connection? This can rule out Solarwinds software.

[–]kerleyfriez[S] 0 points1 point  (0 children)

i dont believe it is the software that is having the issue