Hi,
I installed on a failover cluster, one default virtual sql
server installation named SERVER1 and a other one
installation of virtual server with instance name called
server2\ufa.
When I try to connect true a firewall on SERVER1 with an
UDL file the connection is OK, but When I'm trying the
same test on SERVER2\ufa I've got this error :
[DBNETLIB][ConnectionOpen (Invalid Instance()).]
When I pinging SERVER1 it's OK, When I trying a telnet
command on IP adresse 1433 it's also OK
But on virtual SERVER2 the port 1433 is on the name
SERVER2 so when I try a command telnet SERVER2 1433 it's
OK but SERVER2\UFA is not recognize.
On the firewall the port 1433 is open for Both IP adresses
and we openned also the ports 139 and 445 for the Netbios.
( Name Pipes )
Someone can help me ?You probably need to open up port 1434 or better yet, open the Server
Network Utility on SERVER2 and set the port explicity to something other
than 1433 or 1434, then connect using the port number rather than the
instance name. This is well documented in Books on Line under firewalls.
"Pierre" <anonymous@.discussions.microsoft.com> wrote in message
news:bfde01c4086c$a9472a00$a501280a@.phx.gbl...
> Hi,
> I installed on a failover cluster, one default virtual sql
> server installation named SERVER1 and a other one
> installation of virtual server with instance name called
> server2\ufa.
> When I try to connect true a firewall on SERVER1 with an
> UDL file the connection is OK, but When I'm trying the
> same test on SERVER2\ufa I've got this error :
> [DBNETLIB][ConnectionOpen (Invalid Instance()).]
> When I pinging SERVER1 it's OK, When I trying a telnet
> command on IP adresse 1433 it's also OK
> But on virtual SERVER2 the port 1433 is on the name
> SERVER2 so when I try a command telnet SERVER2 1433 it's
> OK but SERVER2\UFA is not recognize.
> On the firewall the port 1433 is open for Both IP adresses
> and we openned also the ports 139 and 445 for the Netbios.
> ( Name Pipes )
> Someone can help me ?
>|||To be able to connect to a named instance, (both clustered and stand alone)
1) If the client has MDAC 2.5 or lower, then you have to specify the port
number when connecting and make sure this port is open at the firewall.
2)If the client has MDAC 2.6 or higher, then specify the port number when
connecting or make sure UDP port 1434 is open at the firewall (This is true
even if the named instance is listening on port 1433)
The following articles maybe helpful.
286303 INF: Behavior of SQL Server 2000 Network Library During Dynamic Port
http://support.microsoft.com/?id=286303
287932 INF: TCP Ports Needed for Communication to SQL Server Through a
Firewall
http://support.microsoft.com/?id=287932
286303 INF: Behavior of SQL Server 2000 Network Library During Dynamic Port
http://support.microsoft.com/?id=286303
265808 INF: How to Connect to an SQL Server 2000 Named Instance with the
http://support.microsoft.com/?id=265808
Thanks
Deepali
This posting is provided "AS IS" with no warranties, and confers no rights
Showing posts with label cluster. Show all posts
Showing posts with label cluster. Show all posts
Sunday, March 25, 2012
Thursday, March 22, 2012
Connectivity Issues
We’re having a problem with our web applications connecting to the SQL DB
virtual server cluster. We are running SQL 2000 an '03 Server Cluster. The
front-end web servers are Win2K, IIS 5. The web servers and the database
server reside on the same LAN and the front end can ping the backend using
either IP or SQL cluster name successfully.
The clustering is functioning properly and has passed all failover testing
scenarios including the SQL Server resources. The ASP code is using a
Globaldb include file to point to a production database. When I point any of
3 web servers to a single SQL server offering the same exact databases,
users, logins, etc., IE makes the connections with no problem. When
attempting to do the same to the clustered virtual server, we get either a
“500 Internal Server” error or a blank page that says “Done” on the IE status
bar at the bottom of the window. No connection to the database is completed
Is there something we are missing to make this connection work? What can I
look at?
Thank you very much.
Apply MDAC 2.8 to all your client machines. Early versions of MDAC were not
instance aware. Cluster names (VitrualServerName\InstanceName) use the same
syntax as multi-instance SQL servers and look the same on an network.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Fonkberry" <Fonkberry@.discussions.microsoft.com> wrote in message
news:296ABC73-4A0B-44BC-8221-F5498C903DDD@.microsoft.com...
> We're having a problem with our web applications connecting to the SQL DB
> virtual server cluster. We are running SQL 2000 an '03 Server Cluster. The
> front-end web servers are Win2K, IIS 5. The web servers and the database
> server reside on the same LAN and the front end can ping the backend using
> either IP or SQL cluster name successfully.
> The clustering is functioning properly and has passed all failover testing
> scenarios including the SQL Server resources. The ASP code is using a
> Globaldb include file to point to a production database. When I point any
of
> 3 web servers to a single SQL server offering the same exact databases,
> users, logins, etc., IE makes the connections with no problem. When
> attempting to do the same to the clustered virtual server, we get either a
> "500 Internal Server" error or a blank page that says "Done" on the IE
status
> bar at the bottom of the window. No connection to the database is
completed
> Is there something we are missing to make this connection work? What can I
> look at?
> Thank you very much.
>
virtual server cluster. We are running SQL 2000 an '03 Server Cluster. The
front-end web servers are Win2K, IIS 5. The web servers and the database
server reside on the same LAN and the front end can ping the backend using
either IP or SQL cluster name successfully.
The clustering is functioning properly and has passed all failover testing
scenarios including the SQL Server resources. The ASP code is using a
Globaldb include file to point to a production database. When I point any of
3 web servers to a single SQL server offering the same exact databases,
users, logins, etc., IE makes the connections with no problem. When
attempting to do the same to the clustered virtual server, we get either a
“500 Internal Server” error or a blank page that says “Done” on the IE status
bar at the bottom of the window. No connection to the database is completed
Is there something we are missing to make this connection work? What can I
look at?
Thank you very much.
Apply MDAC 2.8 to all your client machines. Early versions of MDAC were not
instance aware. Cluster names (VitrualServerName\InstanceName) use the same
syntax as multi-instance SQL servers and look the same on an network.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Fonkberry" <Fonkberry@.discussions.microsoft.com> wrote in message
news:296ABC73-4A0B-44BC-8221-F5498C903DDD@.microsoft.com...
> We're having a problem with our web applications connecting to the SQL DB
> virtual server cluster. We are running SQL 2000 an '03 Server Cluster. The
> front-end web servers are Win2K, IIS 5. The web servers and the database
> server reside on the same LAN and the front end can ping the backend using
> either IP or SQL cluster name successfully.
> The clustering is functioning properly and has passed all failover testing
> scenarios including the SQL Server resources. The ASP code is using a
> Globaldb include file to point to a production database. When I point any
of
> 3 web servers to a single SQL server offering the same exact databases,
> users, logins, etc., IE makes the connections with no problem. When
> attempting to do the same to the clustered virtual server, we get either a
> "500 Internal Server" error or a blank page that says "Done" on the IE
status
> bar at the bottom of the window. No connection to the database is
completed
> Is there something we are missing to make this connection work? What can I
> look at?
> Thank you very much.
>
Wednesday, March 7, 2012
Connection to Lan fails and locks server
Morning,
We have two nodes in a sql cluster. The "Lan" connection on one of the
servers fails at different times and I can't track down the problem and I am
not sure where to start.
I have changed NIC's Cables, Switches and still no luck..
Any suggestions where to start would be appreciated.
Thanks
Firmware? BIOS? Drivers? Called the vendors?
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog
"James" <James@.discussions.microsoft.com> wrote in message
news:C32C79C1-AE2F-4F80-B425-F038C789D0F8@.microsoft.com...
> Morning,
> We have two nodes in a sql cluster. The "Lan" connection on one of the
> servers fails at different times and I can't track down the problem and I
> am
> not sure where to start.
> I have changed NIC's Cables, Switches and still no luck..
> Any suggestions where to start would be appreciated.
> Thanks
|||Actually we had a DELL rep come out and set this up because we did not want
to mess with the SAN LUN's. He couldn't figure it out either. I will take a
look at the BIOS. We are running a Win 2003 with sql 2000 cluster.
I noticed earlier that Network DTC was not installed on both servers so I
installed that see if maybe that will make a difference.
"Rodney R. Fournier [MVP]" wrote:
> Firmware? BIOS? Drivers? Called the vendors?
> Cheers,
> Rod
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering
> http://msmvps.com/clustering - Blog
> "James" <James@.discussions.microsoft.com> wrote in message
> news:C32C79C1-AE2F-4F80-B425-F038C789D0F8@.microsoft.com...
>
>
|||"James" <James@.discussions.microsoft.com> wrote in message
news:9E080491-54A2-43AF-9E79-45B388030ACE@.microsoft.com...
> Actually we had a DELL rep come out and set this up because we did not
want
> to mess with the SAN LUN's. He couldn't figure it out either. I will
take a
> look at the BIOS. We are running a Win 2003 with sql 2000 cluster.
>
To ask the obvious... SP3a installed?
[vbcol=seagreen]
> I noticed earlier that Network DTC was not installed on both servers so I
> installed that see if maybe that will make a difference.
> "Rodney R. Fournier [MVP]" wrote:
the[vbcol=seagreen]
and I[vbcol=seagreen]
|||SP3 A is installed. Server failed again after 3 day. Network cards pass all
test? I will post some logs see if anyone has seen it before.
"Greg D. Moore (Strider)" wrote:
> "James" <James@.discussions.microsoft.com> wrote in message
> news:9E080491-54A2-43AF-9E79-45B388030ACE@.microsoft.com...
> want
> take a
> To ask the obvious... SP3a installed?
>
> the
> and I
>
>
|||Ok Here is the Cluster Log as soon as it fails I cannot figure this out. We
have had this problem for 3 weeks now, the amount of time it takes to fail
varies. Any help would be appreciated.
000003c0.00000508::2004/12/30-14:53:44.063 INFO [NM] Reporting connectivity
to leader for network 4acd10cf-f965-42a4-b597-14d61d286b4c.
000003c0.00000508::2004/12/30-14:53:44.063 INFO [NM] Connectivity report
completed successfully for network 4acd10cf-f965-42a4-b597-14d61d286b4c.
000003c0.00000508::2004/12/30-14:53:44.063 INFO [NM] Connectivity report
worker thread finished.
000003c0.00000804::2004/12/30-14:53:46.531 INFO [GUM] s_GumUpdateNode:
dispatching seq 8884type 2 context 15
000003c0.00000804::2004/12/30-14:53:46.531 INFO [NM] Received update to set
state for network 4acd10cf-f965-42a4-b597-14d61d286b4c.
000003c0.00000804::2004/12/30-14:53:46.547 WARN [NM] Interface
8a0a2f09-80e0-46a1-ae1f-663f765f414b is unreachable (node: Server1, network:
LAN).
000003c0.00000804::2004/12/30-14:53:46.547 WARN [NM] Interface
09b7cff6-2020-43ba-bb7e-23f36d09f7c4 is unreachable (node: Server2, network:
LAN).
000003c0.00000804::2004/12/30-14:53:46.547 WARN [NM] Network
4acd10cf-f965-42a4-b597-14d61d286b4c (LAN) is down.
000003c0.00000804::2004/12/30-14:53:46.547 INFO [GUM] s_GumUpdateNode:
completed update seq 8884type 2 context 15
000003c0.00000804::2004/12/30-14:53:50.405 INFO [NM] Received request to get
online address enum for interface 09b7cff6-2020-43ba-bb7e-23f36d09f7c4.
000003c0.00000804::2004/12/30-14:53:50.499 INFO [NM] Found address
10.40.0.91 for interface 09b7cff6-2020-43ba-bb7e-23f36d09f7c4.
000003c0.00000804::2004/12/30-14:53:50.499 INFO [NM] Received request to get
ping address enum for interface 09b7cff6-2020-43ba-bb7e-23f36d09f7c4.
000003c0.00000804::2004/12/30-14:53:50.515 INFO [NM] Received request to
ping targets for interface 09b7cff6-2020-43ba-bb7e-23f36d09f7c4.
000003c0.00000804::2004/12/30-14:53:50.515 INFO [NM] Pinging targets for
interface 09b7cff6-2020-43ba-bb7e-23f36d09f7c4.
000003c0.00000804::2004/12/30-14:53:50.515 INFO [NM] Pinging host 10.40.0.1
000003c0.00000804::2004/12/30-14:53:54.139 INFO [NM] Ping of host 10.40.0.1
failed.
000003c0.00000804::2004/12/30-14:53:54.139 INFO [NM] Pinging host 10.40.0.182
000003c0.00000804::2004/12/30-14:53:58.138 INFO [NM] Ping of host
10.40.0.182 failed.
000003c0.00000804::2004/12/30-14:53:58.138 INFO [NM] Pinging host 10.40.0.2
000003c0.00000804::2004/12/30-14:54:02.138 INFO [NM] Ping of host 10.40.0.2
failed.
000003c0.00000804::2004/12/30-14:54:02.138 INFO [NM] Pinging host 10.40.0.7
000003c0.00000804::2004/12/30-14:54:06.137 INFO [NM] Ping of host 10.40.0.7
failed.
000003c0.00000804::2004/12/30-14:54:06.137 INFO [NM] Pinging host 10.40.0.39
000003c0.00000804::2004/12/30-14:54:10.136 INFO [NM] Ping of host 10.40.0.39
failed.
000003c0.00000804::2004/12/30-14:54:10.136 INFO [NM] Finished pinging
targets for interface 09b7cff6-2020-43ba-bb7e-23f36d09f7c4.
000003c0.00000688::2004/12/30-14:54:10.136 INFO [GUM] s_GumUpdateNode:
dispatching seq 8885type 2 context 15
000003c0.00000688::2004/12/30-14:54:10.136 INFO [NM] Received update to set
state for network 4acd10cf-f965-42a4-b597-14d61d286b4c.
000003c0.00000688::2004/12/30-14:54:10.136 INFO [NM] Interface
8a0a2f09-80e0-46a1-ae1f-663f765f414b is up (node: Server1, network: LAN).
000003c0.00000688::2004/12/30-14:54:10.136 WARN [NM] Interface
09b7cff6-2020-43ba-bb7e-23f36d09f7c4 failed (node: Server2, network: LAN).
000003c0.00000688::2004/12/30-14:54:10.136 WARN [NM] Network
4acd10cf-f965-42a4-b597-14d61d286b4c (LAN) is up.
000003c0.00000688::2004/12/30-14:54:10.136 INFO [GUM] s_GumUpdateNode:
completed update seq 8885type 2 context 15
"James" wrote:
> Morning,
> We have two nodes in a sql cluster. The "Lan" connection on one of the
> servers fails at different times and I can't track down the problem and I am
> not sure where to start.
> I have changed NIC's Cables, Switches and still no luck..
> Any suggestions where to start would be appreciated.
> Thanks
We have two nodes in a sql cluster. The "Lan" connection on one of the
servers fails at different times and I can't track down the problem and I am
not sure where to start.
I have changed NIC's Cables, Switches and still no luck..
Any suggestions where to start would be appreciated.
Thanks
Firmware? BIOS? Drivers? Called the vendors?
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog
"James" <James@.discussions.microsoft.com> wrote in message
news:C32C79C1-AE2F-4F80-B425-F038C789D0F8@.microsoft.com...
> Morning,
> We have two nodes in a sql cluster. The "Lan" connection on one of the
> servers fails at different times and I can't track down the problem and I
> am
> not sure where to start.
> I have changed NIC's Cables, Switches and still no luck..
> Any suggestions where to start would be appreciated.
> Thanks
|||Actually we had a DELL rep come out and set this up because we did not want
to mess with the SAN LUN's. He couldn't figure it out either. I will take a
look at the BIOS. We are running a Win 2003 with sql 2000 cluster.
I noticed earlier that Network DTC was not installed on both servers so I
installed that see if maybe that will make a difference.
"Rodney R. Fournier [MVP]" wrote:
> Firmware? BIOS? Drivers? Called the vendors?
> Cheers,
> Rod
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering
> http://msmvps.com/clustering - Blog
> "James" <James@.discussions.microsoft.com> wrote in message
> news:C32C79C1-AE2F-4F80-B425-F038C789D0F8@.microsoft.com...
>
>
|||"James" <James@.discussions.microsoft.com> wrote in message
news:9E080491-54A2-43AF-9E79-45B388030ACE@.microsoft.com...
> Actually we had a DELL rep come out and set this up because we did not
want
> to mess with the SAN LUN's. He couldn't figure it out either. I will
take a
> look at the BIOS. We are running a Win 2003 with sql 2000 cluster.
>
To ask the obvious... SP3a installed?
[vbcol=seagreen]
> I noticed earlier that Network DTC was not installed on both servers so I
> installed that see if maybe that will make a difference.
> "Rodney R. Fournier [MVP]" wrote:
the[vbcol=seagreen]
and I[vbcol=seagreen]
|||SP3 A is installed. Server failed again after 3 day. Network cards pass all
test? I will post some logs see if anyone has seen it before.
"Greg D. Moore (Strider)" wrote:
> "James" <James@.discussions.microsoft.com> wrote in message
> news:9E080491-54A2-43AF-9E79-45B388030ACE@.microsoft.com...
> want
> take a
> To ask the obvious... SP3a installed?
>
> the
> and I
>
>
|||Ok Here is the Cluster Log as soon as it fails I cannot figure this out. We
have had this problem for 3 weeks now, the amount of time it takes to fail
varies. Any help would be appreciated.
000003c0.00000508::2004/12/30-14:53:44.063 INFO [NM] Reporting connectivity
to leader for network 4acd10cf-f965-42a4-b597-14d61d286b4c.
000003c0.00000508::2004/12/30-14:53:44.063 INFO [NM] Connectivity report
completed successfully for network 4acd10cf-f965-42a4-b597-14d61d286b4c.
000003c0.00000508::2004/12/30-14:53:44.063 INFO [NM] Connectivity report
worker thread finished.
000003c0.00000804::2004/12/30-14:53:46.531 INFO [GUM] s_GumUpdateNode:
dispatching seq 8884type 2 context 15
000003c0.00000804::2004/12/30-14:53:46.531 INFO [NM] Received update to set
state for network 4acd10cf-f965-42a4-b597-14d61d286b4c.
000003c0.00000804::2004/12/30-14:53:46.547 WARN [NM] Interface
8a0a2f09-80e0-46a1-ae1f-663f765f414b is unreachable (node: Server1, network:
LAN).
000003c0.00000804::2004/12/30-14:53:46.547 WARN [NM] Interface
09b7cff6-2020-43ba-bb7e-23f36d09f7c4 is unreachable (node: Server2, network:
LAN).
000003c0.00000804::2004/12/30-14:53:46.547 WARN [NM] Network
4acd10cf-f965-42a4-b597-14d61d286b4c (LAN) is down.
000003c0.00000804::2004/12/30-14:53:46.547 INFO [GUM] s_GumUpdateNode:
completed update seq 8884type 2 context 15
000003c0.00000804::2004/12/30-14:53:50.405 INFO [NM] Received request to get
online address enum for interface 09b7cff6-2020-43ba-bb7e-23f36d09f7c4.
000003c0.00000804::2004/12/30-14:53:50.499 INFO [NM] Found address
10.40.0.91 for interface 09b7cff6-2020-43ba-bb7e-23f36d09f7c4.
000003c0.00000804::2004/12/30-14:53:50.499 INFO [NM] Received request to get
ping address enum for interface 09b7cff6-2020-43ba-bb7e-23f36d09f7c4.
000003c0.00000804::2004/12/30-14:53:50.515 INFO [NM] Received request to
ping targets for interface 09b7cff6-2020-43ba-bb7e-23f36d09f7c4.
000003c0.00000804::2004/12/30-14:53:50.515 INFO [NM] Pinging targets for
interface 09b7cff6-2020-43ba-bb7e-23f36d09f7c4.
000003c0.00000804::2004/12/30-14:53:50.515 INFO [NM] Pinging host 10.40.0.1
000003c0.00000804::2004/12/30-14:53:54.139 INFO [NM] Ping of host 10.40.0.1
failed.
000003c0.00000804::2004/12/30-14:53:54.139 INFO [NM] Pinging host 10.40.0.182
000003c0.00000804::2004/12/30-14:53:58.138 INFO [NM] Ping of host
10.40.0.182 failed.
000003c0.00000804::2004/12/30-14:53:58.138 INFO [NM] Pinging host 10.40.0.2
000003c0.00000804::2004/12/30-14:54:02.138 INFO [NM] Ping of host 10.40.0.2
failed.
000003c0.00000804::2004/12/30-14:54:02.138 INFO [NM] Pinging host 10.40.0.7
000003c0.00000804::2004/12/30-14:54:06.137 INFO [NM] Ping of host 10.40.0.7
failed.
000003c0.00000804::2004/12/30-14:54:06.137 INFO [NM] Pinging host 10.40.0.39
000003c0.00000804::2004/12/30-14:54:10.136 INFO [NM] Ping of host 10.40.0.39
failed.
000003c0.00000804::2004/12/30-14:54:10.136 INFO [NM] Finished pinging
targets for interface 09b7cff6-2020-43ba-bb7e-23f36d09f7c4.
000003c0.00000688::2004/12/30-14:54:10.136 INFO [GUM] s_GumUpdateNode:
dispatching seq 8885type 2 context 15
000003c0.00000688::2004/12/30-14:54:10.136 INFO [NM] Received update to set
state for network 4acd10cf-f965-42a4-b597-14d61d286b4c.
000003c0.00000688::2004/12/30-14:54:10.136 INFO [NM] Interface
8a0a2f09-80e0-46a1-ae1f-663f765f414b is up (node: Server1, network: LAN).
000003c0.00000688::2004/12/30-14:54:10.136 WARN [NM] Interface
09b7cff6-2020-43ba-bb7e-23f36d09f7c4 failed (node: Server2, network: LAN).
000003c0.00000688::2004/12/30-14:54:10.136 WARN [NM] Network
4acd10cf-f965-42a4-b597-14d61d286b4c (LAN) is up.
000003c0.00000688::2004/12/30-14:54:10.136 INFO [GUM] s_GumUpdateNode:
completed update seq 8885type 2 context 15
"James" wrote:
> Morning,
> We have two nodes in a sql cluster. The "Lan" connection on one of the
> servers fails at different times and I can't track down the problem and I am
> not sure where to start.
> I have changed NIC's Cables, Switches and still no luck..
> Any suggestions where to start would be appreciated.
> Thanks
connection to cluster admin
I was trying to move the msdtc resource to the msdtc group and I have messed
up the cluster by taking too much offline in an attempt to move it. now I
don't have access to the cluster as the cluster ip, network name are
offline.
Can I tweak the registry somehow to regain access to it?
Stupid Stupid error.
Start Cluster Admin, but instead of using the cluster name, open it with a
period. Then start the resources.
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"Wayne" <watkinson@.sd43.bc.ca> wrote in message
news:O7gBmC6VHHA.5092@.TK2MSFTNGP03.phx.gbl...
>I was trying to move the msdtc resource to the msdtc group and I have
>messed up the cluster by taking too much offline in an attempt to move it.
>now I don't have access to the cluster as the cluster ip, network name are
>offline.
> Can I tweak the registry somehow to regain access to it?
> Stupid Stupid error.
>
|||Thank you...I was sweating bullets for awhile!
Nice trick to remember...
"Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
message news:%23iTaiN6VHHA.1200@.TK2MSFTNGP02.phx.gbl...
> Start Cluster Admin, but instead of using the cluster name, open it with a
> period. Then start the resources.
> Cheers,
> Rodney R. Fournier
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering Website
> http://msmvps.com/clustering - Blog
> http://www.clusterhelp.com - Cluster Training
> ClusterHelp.com is a Microsoft Certified Gold Partner
>
> "Wayne" <watkinson@.sd43.bc.ca> wrote in message
> news:O7gBmC6VHHA.5092@.TK2MSFTNGP03.phx.gbl...
>
up the cluster by taking too much offline in an attempt to move it. now I
don't have access to the cluster as the cluster ip, network name are
offline.
Can I tweak the registry somehow to regain access to it?
Stupid Stupid error.
Start Cluster Admin, but instead of using the cluster name, open it with a
period. Then start the resources.
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"Wayne" <watkinson@.sd43.bc.ca> wrote in message
news:O7gBmC6VHHA.5092@.TK2MSFTNGP03.phx.gbl...
>I was trying to move the msdtc resource to the msdtc group and I have
>messed up the cluster by taking too much offline in an attempt to move it.
>now I don't have access to the cluster as the cluster ip, network name are
>offline.
> Can I tweak the registry somehow to regain access to it?
> Stupid Stupid error.
>
|||Thank you...I was sweating bullets for awhile!
Nice trick to remember...
"Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
message news:%23iTaiN6VHHA.1200@.TK2MSFTNGP02.phx.gbl...
> Start Cluster Admin, but instead of using the cluster name, open it with a
> period. Then start the resources.
> Cheers,
> Rodney R. Fournier
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering Website
> http://msmvps.com/clustering - Blog
> http://www.clusterhelp.com - Cluster Training
> ClusterHelp.com is a Microsoft Certified Gold Partner
>
> "Wayne" <watkinson@.sd43.bc.ca> wrote in message
> news:O7gBmC6VHHA.5092@.TK2MSFTNGP03.phx.gbl...
>
Friday, February 24, 2012
Connection String has Semicolon (;) - how on earth can I get this working?
Ok, here's my setup. I've got a named instance in a SQL 2000 cluster. I only have dbo rights on my database, because it is a shared infrastructure. Here's my current web.config connection string (the meat, anyway):
When I'm at the office, this is my connection string, pretty normal:
connectionString="Data Source=ServerName\InstanceName;Initial Catalog=blah..."
But, when I connect through the VPN, I can't just connect through the named instance - I have a specific port. This is where things get odd.
First, if I try to connect through SQL Server Management Studio (2005), i get nothing. If I try to connect using"ServerName\InstanceName, (comma) Port Number" it connects, but not to my instance. I get a seperate set of databases that I believe are in the default instance. So, I changed the comma to a semicolon (;) - and it still connected to the same thing - connected to the database, but to the wrong set of databases. So, on a whim, I tried plunking my string, which was now"ServerName\InstanceName;(semicolon) PortNumber" into the SQL 2000 Tools and it worked in both Query Analyzer and in Enterprise Manager. So, I thought, I'll just slam this into my connection string and all will be well. No. I can't use a semicolon in my connection string, and I can't find an escape character to use. Double semicolons don't work, a comma doesn't connect me properly, double colons don't work, the JDBC brackets don't work {} - so I'm at a loss. I'm out of ideas. I've set up aliases, and those don't work earlier.
I'm using ASP.net 2 with VB & C# and Visual Studio 2005 Professional. Thanks for any help anyone can give on this!
Have you tried with a Colon instead of a semicolon?
|||I have - no dice. I've tried a colon after the servername but before the instance name (i.e.ServerName:Port\InstanceName) as well as at the end of the entire name (ServerName\InstanceName:Port).
|||Hi jdandison,
The standard format to conifgure your port number in connection string is:string connectionString = "Server=Servername\InstanceName;port=your port number;"
So, try to change your connection string to :connectionString="Data Source=ServerName\InstanceName;port=NewPortNumber;Initial Catalog=blah..."and try again.
Tell us if you have any further questions. thanks
Sunday, February 12, 2012
Connection Prodlem-with instance node
Hi
I have an active/passive sql server 2000 cluster. Most of the time I remote-login into the server and use the enterprise manager to work. But now when I click on either of the node I get the following error:
Encryption not supported on SQL Server ConnectionOpen (PreLoginHandshake())
But I'm able to connect to the server from my desktop.
Any help in this regard?
Thanks,
This means that the "Enable Protocol Encryption" option was set on the
machine you're using as a client.
Use the SQL Client Network Utility to uncheck this.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||Hi Kevin
Thank you so much it worked.
Razi
"Kevin McDonnell [MSFT]" wrote:
> This means that the "Enable Protocol Encryption" option was set on the
> machine you're using as a client.
> Use the SQL Client Network Utility to uncheck this.
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>
|||You're welcome!
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
I have an active/passive sql server 2000 cluster. Most of the time I remote-login into the server and use the enterprise manager to work. But now when I click on either of the node I get the following error:
Encryption not supported on SQL Server ConnectionOpen (PreLoginHandshake())
But I'm able to connect to the server from my desktop.
Any help in this regard?
Thanks,
This means that the "Enable Protocol Encryption" option was set on the
machine you're using as a client.
Use the SQL Client Network Utility to uncheck this.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||Hi Kevin
Thank you so much it worked.
Razi
"Kevin McDonnell [MSFT]" wrote:
> This means that the "Enable Protocol Encryption" option was set on the
> machine you're using as a client.
> Use the SQL Client Network Utility to uncheck this.
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>
|||You're welcome!
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
Connection Prodlem-with instance node
Hi
I have an active/passive sql server 2000 cluster. Most of the time I remote-
login into the server and use the enterprise manager to work. But now when I
click on either of the node I get the following error:
Encryption not supported on SQL Server ConnectionOpen (PreLoginHandshake())
But I'm able to connect to the server from my desktop.
Any help in this regard?
Thanks,This means that the "Enable Protocol Encryption" option was set on the
machine you're using as a client.
Use the SQL Client Network Utility to uncheck this.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Hi Kevin
Thank you so much it worked.
Razi
"Kevin McDonnell [MSFT]" wrote:
> This means that the "Enable Protocol Encryption" option was set on the
> machine you're using as a client.
> Use the SQL Client Network Utility to uncheck this.
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>|||You're welcome!
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
I have an active/passive sql server 2000 cluster. Most of the time I remote-
login into the server and use the enterprise manager to work. But now when I
click on either of the node I get the following error:
Encryption not supported on SQL Server ConnectionOpen (PreLoginHandshake())
But I'm able to connect to the server from my desktop.
Any help in this regard?
Thanks,This means that the "Enable Protocol Encryption" option was set on the
machine you're using as a client.
Use the SQL Client Network Utility to uncheck this.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Hi Kevin
Thank you so much it worked.
Razi
"Kevin McDonnell [MSFT]" wrote:
> This means that the "Enable Protocol Encryption" option was set on the
> machine you're using as a client.
> Use the SQL Client Network Utility to uncheck this.
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>|||You're welcome!
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
Friday, February 10, 2012
Connection problem to SQL 2000 cluster
Hello all! I have set up a SQL 2000 cluster and I have installed SQL 2000
Reporting Services on another server. Both servers are on the same IP subne
t
(10.10.100.x/24) and both connected to the same network switch. I cannot
connect to port 1433 of the SQL cluster from the RS server. However, I can
connect to port 1433 on the RS server from the cluster. Also, I can connect
to port 1433 on the cluster from some web servers in the DMZ. There is no
firewall software running on the cluster. I'm not sure where to start
looking next. Any help would be appreciated. Thanks!Ports are meaningful per IP address, and there are a number of different IP
addresses or network names in a cluster. Can you verify that you are using
the right network name or IP address for the SQL Server instance?
Linchi
"mdap" wrote:
> Hello all! I have set up a SQL 2000 cluster and I have installed SQL 2000
> Reporting Services on another server. Both servers are on the same IP sub
net
> (10.10.100.x/24) and both connected to the same network switch. I cannot
> connect to port 1433 of the SQL cluster from the RS server. However, I ca
n
> connect to port 1433 on the RS server from the cluster. Also, I can conne
ct
> to port 1433 on the cluster from some web servers in the DMZ. There is no
> firewall software running on the cluster. I'm not sure where to start
> looking next. Any help would be appreciated. Thanks!|||Linchi,
Thanks for the reply. Yes, I have confirmed that I am attempting to connect
to the right IP and network name of the SQL server instance.
At any rate, I can occasionally connect to the SQL server from the RS
server. I did a packet trace, and I found that I've got a problem with ARP.
(The cluster sees traffic coming from the MAC address of the network firewal
l
instead of from the RS server.) Anyway, when I clear the ARP cache on both
servers, I can establish a connection for a few minutes. After that, the
problem resurfaces. I think that the problem is the network switch, so I'm
going to replace that tomorrow and see if it helps.
"Linchi Shea" wrote:
[vbcol=seagreen]
> Ports are meaningful per IP address, and there are a number of different I
P
> addresses or network names in a cluster. Can you verify that you are using
> the right network name or IP address for the SQL Server instance?
> Linchi
> "mdap" wrote:
>
Reporting Services on another server. Both servers are on the same IP subne
t
(10.10.100.x/24) and both connected to the same network switch. I cannot
connect to port 1433 of the SQL cluster from the RS server. However, I can
connect to port 1433 on the RS server from the cluster. Also, I can connect
to port 1433 on the cluster from some web servers in the DMZ. There is no
firewall software running on the cluster. I'm not sure where to start
looking next. Any help would be appreciated. Thanks!Ports are meaningful per IP address, and there are a number of different IP
addresses or network names in a cluster. Can you verify that you are using
the right network name or IP address for the SQL Server instance?
Linchi
"mdap" wrote:
> Hello all! I have set up a SQL 2000 cluster and I have installed SQL 2000
> Reporting Services on another server. Both servers are on the same IP sub
net
> (10.10.100.x/24) and both connected to the same network switch. I cannot
> connect to port 1433 of the SQL cluster from the RS server. However, I ca
n
> connect to port 1433 on the RS server from the cluster. Also, I can conne
ct
> to port 1433 on the cluster from some web servers in the DMZ. There is no
> firewall software running on the cluster. I'm not sure where to start
> looking next. Any help would be appreciated. Thanks!|||Linchi,
Thanks for the reply. Yes, I have confirmed that I am attempting to connect
to the right IP and network name of the SQL server instance.
At any rate, I can occasionally connect to the SQL server from the RS
server. I did a packet trace, and I found that I've got a problem with ARP.
(The cluster sees traffic coming from the MAC address of the network firewal
l
instead of from the RS server.) Anyway, when I clear the ARP cache on both
servers, I can establish a connection for a few minutes. After that, the
problem resurfaces. I think that the problem is the network switch, so I'm
going to replace that tomorrow and see if it helps.
"Linchi Shea" wrote:
[vbcol=seagreen]
> Ports are meaningful per IP address, and there are a number of different I
P
> addresses or network names in a cluster. Can you verify that you are using
> the right network name or IP address for the SQL Server instance?
> Linchi
> "mdap" wrote:
>
Connection problem to SQL 2000 cluster
Hello all! I have set up a SQL 2000 cluster and I have installed SQL 2000
Reporting Services on another server. Both servers are on the same IP subnet
(10.10.100.x/24) and both connected to the same network switch. I cannot
connect to port 1433 of the SQL cluster from the RS server. However, I can
connect to port 1433 on the RS server from the cluster. Also, I can connect
to port 1433 on the cluster from some web servers in the DMZ. There is no
firewall software running on the cluster. I'm not sure where to start
looking next. Any help would be appreciated. Thanks!
Ports are meaningful per IP address, and there are a number of different IP
addresses or network names in a cluster. Can you verify that you are using
the right network name or IP address for the SQL Server instance?
Linchi
"mdap" wrote:
> Hello all! I have set up a SQL 2000 cluster and I have installed SQL 2000
> Reporting Services on another server. Both servers are on the same IP subnet
> (10.10.100.x/24) and both connected to the same network switch. I cannot
> connect to port 1433 of the SQL cluster from the RS server. However, I can
> connect to port 1433 on the RS server from the cluster. Also, I can connect
> to port 1433 on the cluster from some web servers in the DMZ. There is no
> firewall software running on the cluster. I'm not sure where to start
> looking next. Any help would be appreciated. Thanks!
|||Linchi,
Thanks for the reply. Yes, I have confirmed that I am attempting to connect
to the right IP and network name of the SQL server instance.
At any rate, I can occasionally connect to the SQL server from the RS
server. I did a packet trace, and I found that I've got a problem with ARP.
(The cluster sees traffic coming from the MAC address of the network firewall
instead of from the RS server.) Anyway, when I clear the ARP cache on both
servers, I can establish a connection for a few minutes. After that, the
problem resurfaces. I think that the problem is the network switch, so I'm
going to replace that tomorrow and see if it helps.
"Linchi Shea" wrote:
[vbcol=seagreen]
> Ports are meaningful per IP address, and there are a number of different IP
> addresses or network names in a cluster. Can you verify that you are using
> the right network name or IP address for the SQL Server instance?
> Linchi
> "mdap" wrote:
Reporting Services on another server. Both servers are on the same IP subnet
(10.10.100.x/24) and both connected to the same network switch. I cannot
connect to port 1433 of the SQL cluster from the RS server. However, I can
connect to port 1433 on the RS server from the cluster. Also, I can connect
to port 1433 on the cluster from some web servers in the DMZ. There is no
firewall software running on the cluster. I'm not sure where to start
looking next. Any help would be appreciated. Thanks!
Ports are meaningful per IP address, and there are a number of different IP
addresses or network names in a cluster. Can you verify that you are using
the right network name or IP address for the SQL Server instance?
Linchi
"mdap" wrote:
> Hello all! I have set up a SQL 2000 cluster and I have installed SQL 2000
> Reporting Services on another server. Both servers are on the same IP subnet
> (10.10.100.x/24) and both connected to the same network switch. I cannot
> connect to port 1433 of the SQL cluster from the RS server. However, I can
> connect to port 1433 on the RS server from the cluster. Also, I can connect
> to port 1433 on the cluster from some web servers in the DMZ. There is no
> firewall software running on the cluster. I'm not sure where to start
> looking next. Any help would be appreciated. Thanks!
|||Linchi,
Thanks for the reply. Yes, I have confirmed that I am attempting to connect
to the right IP and network name of the SQL server instance.
At any rate, I can occasionally connect to the SQL server from the RS
server. I did a packet trace, and I found that I've got a problem with ARP.
(The cluster sees traffic coming from the MAC address of the network firewall
instead of from the RS server.) Anyway, when I clear the ARP cache on both
servers, I can establish a connection for a few minutes. After that, the
problem resurfaces. I think that the problem is the network switch, so I'm
going to replace that tomorrow and see if it helps.
"Linchi Shea" wrote:
[vbcol=seagreen]
> Ports are meaningful per IP address, and there are a number of different IP
> addresses or network names in a cluster. Can you verify that you are using
> the right network name or IP address for the SQL Server instance?
> Linchi
> "mdap" wrote:
Subscribe to:
Posts (Atom)