June 24, 2009 at 5:47 am
Dear All,
I have win2003 server and I have install both ss2k5(default instance) and ss2k(named instance).
Now whenever I try to connect to ss2k from ss2k5 it gives me error:TITLE: Connect to Server
------------------------------
Cannot connect to ajayg\ajayg2000.
------------------------------
ADDITIONAL INFORMATION:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1&LinkId=20476
------------------------------
BUTTONS:
OK
------------------------------
Thanks
June 24, 2009 at 7:34 am
were you ever able to connect?
start->run-> type with quotes "cliconfg"
on right side box check to see both the named pipes and TCP/IP are enabled.
Goto Alias TAB
check to see if the instance names are listed for eg the 200 isntance is listed.
If No click on add button
with named pipes selected in the network libraries type the complete instance name with server server in the above box... and that's it..
If the name is already present... delete it and do teh procedure again.
exit out of the dialog box while saving everything...
now try to connect.
if the above doesnt work,,,
in the SSMS connect Dialog box: click on options button in bottom:
click the reset all button and try again:
if still it does not work...
in the SSMs connect dialog.. under options in the network protocols.. choose named pipes....
If the above does nt work... we can move to next steps...
Maninder
www.dbanation.com
June 24, 2009 at 11:39 pm
I have done it
Thancs a lot.....:-)
Thanks
June 26, 2009 at 3:12 am
The root cause may be that bot instances are trying to listen on port 1433.
One way to diagnose if this is a likely cause is:
a) Can you connect to instance A while instance B is stopped
b) Can you connect to instance B when instance A is stopped
c) Can you only connect to the first instance that is started when both are running
If all are true then you probably have this problem. A good way to cure this is to change the port settings for one of the instances. Books Online (BOL) can advise you on how to do this.
You should ask your Windows administrators to assign a port that can be dedicated to the second instance, or you risk that they will use the port you have chosen for something else and you cannot conect to SQL again.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
June 26, 2009 at 4:09 am
Thanx
No Edvassie both were on different port 1433 and 4806
Thanks
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply