Quantcast
Channel: ฟอรัม Getting started with SQL Server
Viewing all articles
Browse latest Browse all 8428

Strange Connection Issues with Instance Name

$
0
0

I have set up two instances on a server (SQL 2014 Enterprise). One instance is named DW, the other one is name DW1.

I am able to connect to Analysis server using Server1\DW and Server1\DW1 remotely. However, I can't connect to the database engine using Server1\DW but able to connect to Server1\DW1. 

I have tried to use both dynamic ports and static ports with DW instance. Neither works. I can connect to the instance using "Server1, portnumber" or"Server1\DW, portnumber". However, when I connect with "Server1\DW", it gave me the typical error 26 message. 

Browser service is running properly on the machine because it is able to find the ports correctly for the other instance DW1. For DW1, I tried to use both dynamic ports and static port that were used in DW too. Both cases work properly.

We used Wireshark to look at the packets. Browser service just had trouble identifying the port for the instance DW no matter if it is set up to use either dynamic or static ports. But on the same server, browser service is working properly for the DW1 instance... 

This is such a strange issue. People might say, why don't you just use the port number? Our standard practice is just use the instance name. This is a server migration so we have to stick to the DW name. 

I am just so curious why it works for DW1 but not DW...



Viewing all articles
Browse latest Browse all 8428

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>