SQL Server Forums
Profile | Register | Active Topics | Members | Search | Forum FAQ
 
Register Now and get your question answered!
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 Multiple SQL Server 2000 Instances
 New Topic  Reply to Topic
 Printer Friendly
Previous Page | Next Page
Author Previous Topic Topic Next Topic
Page: of 4

tkizer
Almighty SQL Goddess

USA
37143 Posts

Posted - 10/01/2004 :  14:24:39  Show Profile  Visit tkizer's Homepage  Reply with Quote
So now you are using TCP/IP according to the error message. So you are sure that MSSQLSERVER and MSSQL$InstanceName are started? And you are sure that you are using the correct ServerName\InstanceName names? Can you poing ServerName from that box? If not, use the IP address in the alias instead of the server name.

Tara
Go to Top of Page

tkizer
Almighty SQL Goddess

USA
37143 Posts

Posted - 10/01/2004 :  14:27:00  Show Profile  Visit tkizer's Homepage  Reply with Quote
Ah, Win2k3. I wonder if port 1434 is blocked by default. I haven't installed multiple instances on Win2k3 yet. You might need to google this and check the MS knowledge base:

http://support.microsoft.com

Tara
Go to Top of Page

ricky_newbee
Posting Yak Master

126 Posts

Posted - 10/01/2004 :  14:56:53  Show Profile  Reply with Quote
Some one has any solution for this problem
Go to Top of Page

ricky_newbee
Posting Yak Master

126 Posts

Posted - 10/01/2004 :  14:59:00  Show Profile  Reply with Quote
Tara!! Do you have any other solution for this issue?
Go to Top of Page

tkizer
Almighty SQL Goddess

USA
37143 Posts

Posted - 10/01/2004 :  14:59:52  Show Profile  Visit tkizer's Homepage  Reply with Quote
Consider using a different port other than 1434. You'll need to change the port number in Server Network Utility, restart the MSSQL$InstanceName service, and modify your alias in Client Network Utility for this new port.

Tara
Go to Top of Page

ricky_newbee
Posting Yak Master

126 Posts

Posted - 10/01/2004 :  15:18:56  Show Profile  Reply with Quote
Wow!! Tara
You are Invincible. It did work. Changed port number and changed alias. I gave my instance name as my alias. Its working. Thanks somuch Tara....
Go to Top of Page

ricky_newbee
Posting Yak Master

126 Posts

Posted - 10/01/2004 :  15:28:02  Show Profile  Reply with Quote
But, i don't under stand the key point behind this...
Go to Top of Page

tkizer
Almighty SQL Goddess

USA
37143 Posts

Posted - 10/01/2004 :  15:30:41  Show Profile  Visit tkizer's Homepage  Reply with Quote
I think it has to do with the locked down features of Windows 2003.

Tara
Go to Top of Page

ricky_newbee
Posting Yak Master

126 Posts

Posted - 10/01/2004 :  15:40:43  Show Profile  Reply with Quote
Yeah! May be. Your help was appriciable tara. Thanks
Go to Top of Page

ricky_newbee
Posting Yak Master

126 Posts

Posted - 10/05/2004 :  11:22:04  Show Profile  Reply with Quote
Hello Tara,
Hope you could answer to this question. Following with the same problem, i could able to see both instances in the database server. But when i am trying to connect from other remote system, it doesn't connect. Also i cannot see the instance neither Server in New SQL Server Registration window. Can you help me with this? Thanks Rick
Go to Top of Page

tkizer
Almighty SQL Goddess

USA
37143 Posts

Posted - 10/05/2004 :  12:30:16  Show Profile  Visit tkizer's Homepage  Reply with Quote
You need to create an alias to it using Client Network Utility.

Tara
Go to Top of Page

ricky_newbee
Posting Yak Master

126 Posts

Posted - 10/05/2004 :  12:57:50  Show Profile  Reply with Quote
Create an alias in Client machine? I have that alias created.
It gave me same error.
Go to Top of Page

tkizer
Almighty SQL Goddess

USA
37143 Posts

Posted - 10/05/2004 :  13:00:02  Show Profile  Visit tkizer's Homepage  Reply with Quote
Please describe what options you select when you created the alias. And please post the error message.

Tara
Go to Top of Page

ricky_newbee
Posting Yak Master

126 Posts

Posted - 10/05/2004 :  13:04:52  Show Profile  Reply with Quote
Yes!! I selected TCP/IP, Servername, and checked default port in client network utility. Alias name i gave was Servername\Instance.
I was trying to connect from my client machine to the server and i get this error:
[Microsoft][ODBC SQL SErver Driver][TCP/IP Sockets]SQL Server does not exist or access denied (08001,17)

Edited by - ricky_newbee on 10/05/2004 13:07:49
Go to Top of Page

tkizer
Almighty SQL Goddess

USA
37143 Posts

Posted - 10/05/2004 :  13:09:18  Show Profile  Visit tkizer's Homepage  Reply with Quote
You can not use the default port as that isn't what you selected for this server. Use the port that you selected last Friday.

Tara
Go to Top of Page

ricky_newbee
Posting Yak Master

126 Posts

Posted - 10/05/2004 :  13:11:45  Show Profile  Reply with Quote
I did try that. It wouldn't work....

Any Ideas?

Edited by - ricky_newbee on 10/05/2004 13:30:49
Go to Top of Page

ricky_newbee
Posting Yak Master

126 Posts

Posted - 10/06/2004 :  09:39:16  Show Profile  Reply with Quote
Guys!! Any Ideas on how to resolve this issue?
Go to Top of Page

tkizer
Almighty SQL Goddess

USA
37143 Posts

Posted - 10/06/2004 :  12:33:25  Show Profile  Visit tkizer's Homepage  Reply with Quote
All I can say is make sure that the port is the same in Server Network Utility on the database server and Client Network Utility on the client machine.

On the client machine, you could try connecting to Query Analyzer using ServerName,PortNumber. If that works, then the problem is with your alias.

Tara
Go to Top of Page

ricky_newbee
Posting Yak Master

126 Posts

Posted - 10/06/2004 :  15:04:53  Show Profile  Reply with Quote
Tara,
Now i have repeated problem. I had to restart the server which has two instances. After rebooting i could only see one instance in EManager and i could able to connect to 2 instances through Query Analyzer. I tried every thing.
Error: SQL Server does not exist or access denied.
I am having same error from client machines also.

Edited by - ricky_newbee on 10/06/2004 15:05:59
Go to Top of Page

tkizer
Almighty SQL Goddess

USA
37143 Posts

Posted - 10/06/2004 :  15:09:04  Show Profile  Visit tkizer's Homepage  Reply with Quote
Sounds like your port was changed on the database server. Open up Server Network Utility to view the port for that instance.

Is the MSSQL$InstanceName service started on the database server? Is it set to automatic? If not, that's your problem.

Tara
Go to Top of Page
Page: of 4 Previous Topic Topic Next Topic  
Previous Page | Next Page
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.12 seconds. Powered By: Snitz Forums 2000