| Author |
 Topic  |
|
tkizer
Almighty SQL Goddess
USA
35007 Posts |
 Posted - 10/01/2004 : 14:24:39
|
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 |
 |
|
|
tkizer
Almighty SQL Goddess
USA
35007 Posts |
Posted - 10/01/2004 : 14:27:00
|
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 |
|
|
|
ricky_newbee
Posting Yak Master
126 Posts |
Posted - 10/01/2004 : 14:56:53
|
| Some one has any solution for this problem |
|
|
|
ricky_newbee
Posting Yak Master
126 Posts |
Posted - 10/01/2004 : 14:59:00
|
| Tara!! Do you have any other solution for this issue? |
|
|
|
tkizer
Almighty SQL Goddess
USA
35007 Posts |
Posted - 10/01/2004 : 14:59:52
|
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 |
|
|
|
ricky_newbee
Posting Yak Master
126 Posts |
Posted - 10/01/2004 : 15:18:56
|
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.... |
|
|
|
ricky_newbee
Posting Yak Master
126 Posts |
Posted - 10/01/2004 : 15:28:02
|
| But, i don't under stand the key point behind this... |
|
|
|
tkizer
Almighty SQL Goddess
USA
35007 Posts |
Posted - 10/01/2004 : 15:30:41
|
I think it has to do with the locked down features of Windows 2003.
Tara |
|
|
|
ricky_newbee
Posting Yak Master
126 Posts |
Posted - 10/01/2004 : 15:40:43
|
| Yeah! May be. Your help was appriciable tara. Thanks |
|
|
|
ricky_newbee
Posting Yak Master
126 Posts |
Posted - 10/05/2004 : 11:22:04
|
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 |
|
|
|
tkizer
Almighty SQL Goddess
USA
35007 Posts |
Posted - 10/05/2004 : 12:30:16
|
You need to create an alias to it using Client Network Utility.
Tara |
|
|
|
ricky_newbee
Posting Yak Master
126 Posts |
Posted - 10/05/2004 : 12:57:50
|
Create an alias in Client machine? I have that alias created.
It gave me same error. |
|
|
|
tkizer
Almighty SQL Goddess
USA
35007 Posts |
Posted - 10/05/2004 : 13:00:02
|
Please describe what options you select when you created the alias. And please post the error message.
Tara |
|
|
|
ricky_newbee
Posting Yak Master
126 Posts |
Posted - 10/05/2004 : 13:04:52
|
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 |
|
|
|
tkizer
Almighty SQL Goddess
USA
35007 Posts |
Posted - 10/05/2004 : 13:09:18
|
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 |
|
|
|
ricky_newbee
Posting Yak Master
126 Posts |
Posted - 10/05/2004 : 13:11:45
|
I did try that. It wouldn't work....
Any Ideas? |
Edited by - ricky_newbee on 10/05/2004 13:30:49 |
|
|
|
ricky_newbee
Posting Yak Master
126 Posts |
Posted - 10/06/2004 : 09:39:16
|
| Guys!! Any Ideas on how to resolve this issue? |
|
|
|
tkizer
Almighty SQL Goddess
USA
35007 Posts |
Posted - 10/06/2004 : 12:33:25
|
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 |
|
|
|
ricky_newbee
Posting Yak Master
126 Posts |
Posted - 10/06/2004 : 15:04:53
|
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 |
|
|
|
tkizer
Almighty SQL Goddess
USA
35007 Posts |
Posted - 10/06/2004 : 15:09:04
|
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 |
|
|
|
Topic |
|
Multiple SQL Server 2000 Instances
