![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
OK, here is the scenario. We have bought some nice new servers to replace our 3 year old ones. Also, we are migrating to Win2K3. Managed to upgrade the current active/active cluster to Win2K3 and all is well. Following a Microsoft whitepaper on how to upgrade, it tells us that we need to evict a node by running SQL Server setup and entering the name of the virtual server. This is where we get the problem. We have two SQL servers in the cluster, they are named SQL_SERVER1 AND SQL_SERVER2\SQL_SERVER2. As you can see the second server is running as a named instance (to avoid cluster conflicts) When entering the virtual server name in SQL server setup it tells me that "The format of the virtual server name is invalid" After some hours of research, the only possible reason I can come up with for this is that the virtual server names have underscores on them. We get the same message when running SP3a. This only occurs on Win2K3 and not NT4. Has anybody come across this problem or has a solution? Thanks, Freddy |
#3
| |||
| |||
|
|
OK, here is the scenario. We have bought some nice new servers to replace our 3 year old ones. Also, we are migrating to Win2K3. Managed to upgrade the current active/active cluster to Win2K3 and all is well. Following a Microsoft whitepaper on how to upgrade, it tells us that we need to evict a node by running SQL Server setup and entering the name of the virtual server. This is where we get the problem. We have two SQL servers in the cluster, they are named SQL_SERVER1 AND SQL_SERVER2\SQL_SERVER2. As you can see the second server is running as a named instance (to avoid cluster conflicts) When entering the virtual server name in SQL server setup it tells me that "The format of the virtual server name is invalid" After some hours of research, the only possible reason I can come up with for this is that the virtual server names have underscores on them. We get the same message when running SP3a. This only occurs on Win2K3 and not NT4. Has anybody come across this problem or has a solution? Thanks, Freddy |
#4
| |||
| |||
|
|
OK, here is the scenario. We have bought some nice new servers to replace our 3 year old ones. Also, we are migrating to Win2K3. Managed to upgrade the current active/active cluster to Win2K3 and all is well. Following a Microsoft whitepaper on how to upgrade, it tells us that we need to evict a node by running SQL Server setup and entering the name of the virtual server. This is where we get the problem. We have two SQL servers in the cluster, they are named SQL_SERVER1 AND SQL_SERVER2\SQL_SERVER2. As you can see the second server is running as a named instance (to avoid cluster conflicts) When entering the virtual server name in SQL server setup it tells me that "The format of the virtual server name is invalid" After some hours of research, the only possible reason I can come up with for this is that the virtual server names have underscores on them. We get the same message when running SP3a. This only occurs on Win2K3 and not NT4. Has anybody come across this problem or has a solution? Thanks, Freddy |
#5
| |||
| |||
|
|
OK, here is the scenario. We have bought some nice new servers to replace our 3 year old ones. Also, we are migrating to Win2K3. Managed to upgrade the current active/active cluster to Win2K3 and all is well. Following a Microsoft whitepaper on how to upgrade, it tells us that we need to evict a node by running SQL Server setup and entering the name of the virtual server. This is where we get the problem. We have two SQL servers in the cluster, they are named SQL_SERVER1 AND SQL_SERVER2\SQL_SERVER2. As you can see the second server is running as a named instance (to avoid cluster conflicts) When entering the virtual server name in SQL server setup it tells me that "The format of the virtual server name is invalid" After some hours of research, the only possible reason I can come up with for this is that the virtual server names have underscores on them. We get the same message when running SP3a. This only occurs on Win2K3 and not NT4. Has anybody come across this problem or has a solution? Thanks, Freddy |
![]() |
| Thread Tools | |
| Display Modes | |
| |