Cluster Issue

Hello,
I have a Wndows 2003 Sql 2005 Cluster consisting of two servers, on Failover
from node2 to node1 the application user is unable to login until the sql
server is restarted, on failover all the resourses come online but the user
is unable to access the database and if I look in SQl Server management
studio I am unable to see the properties of the DB, if I initiate a failure
of SQL server in the cluster I am still unable to access the DB but if I
restart SQL server in management studio the database comes online.
Also when I do a failover to node2, it shows all resourses are online but
the application cannot access the DB like it is not there, but I can access
the Quorum and the shared DB drive.
Thanks in advance,
Bob Smith
Definitely a problem. Check the Application log on either node (Event
logging on a cluster is cluster-wide to each node) to see if SQL is
complaining about starting up.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Bob Smith" <BobSmith@.discussions.microsoft.com> wrote in message
news:F586AE13-D88E-4893-A6A3-0465392C13F2@.microsoft.com...
> Hello,
> I have a Wndows 2003 Sql 2005 Cluster consisting of two servers, on
> Failover
> from node2 to node1 the application user is unable to login until the sql
> server is restarted, on failover all the resourses come online but the
> user
> is unable to access the database and if I look in SQl Server management
> studio I am unable to see the properties of the DB, if I initiate a
> failure
> of SQL server in the cluster I am still unable to access the DB but if I
> restart SQL server in management studio the database comes online.
> Also when I do a failover to node2, it shows all resourses are online but
> the application cannot access the DB like it is not there, but I can
> access
> the Quorum and the shared DB drive.
> Thanks in advance,
> Bob Smith
|||Hi Geoff,
Thanks for the reply, the only thing I can see is logwriter errors, which I
googled and found more questions than answers, let me ask this: Can the
Quroum and the physical disk be in different groups or should the be in the
same, mine is set the the Quorum is in the Cluster group and the Physical
disk is in group 0. By the way I see these errors on both nodes. What is best
practice for the cluster group, what resourses should exist in it: Cluster
IP, Cluster Name, MSDTC -?, Quorum -?
Thanks again,
Bob Smith
"Geoff N. Hiten" wrote:

> Definitely a problem. Check the Application log on either node (Event
> logging on a cluster is cluster-wide to each node) to see if SQL is
> complaining about starting up.
> --
> Geoff N. Hiten
> Senior SQL Infrastructure Consultant
> Microsoft SQL Server MVP
>
> "Bob Smith" <BobSmith@.discussions.microsoft.com> wrote in message
> news:F586AE13-D88E-4893-A6A3-0465392C13F2@.microsoft.com...
>
|||Quorum must be in the cluster group. It is the reason the group exists.
The Quorum disk prevents split-brain problems. The Cluster group should
also have an IP Address and a Network Name Resource.
You can put the MSDTC resource in there too, but it can cause problems on
some very high volume systems.
All SQL resources should be in a different group. Note that disks are
physical resources. Logical OS partitions of the same disk cannot be split
into multiple groups.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Bob Smith" <BobSmith@.discussions.microsoft.com> wrote in message
news:1BD77D34-DC9D-4CB6-8325-9D32F50C9B58@.microsoft.com...[vbcol=seagreen]
> Hi Geoff,
> Thanks for the reply, the only thing I can see is logwriter errors, which
> I
> googled and found more questions than answers, let me ask this: Can the
> Quroum and the physical disk be in different groups or should the be in
> the
> same, mine is set the the Quorum is in the Cluster group and the Physical
> disk is in group 0. By the way I see these errors on both nodes. What is
> best
> practice for the cluster group, what resourses should exist in it: Cluster
> IP, Cluster Name, MSDTC -?, Quorum -?
> Thanks again,
> Bob Smith
> "Geoff N. Hiten" wrote:
|||Geoff,
Thanks, that is how it is setup Cluster group (Cluster IP, Cluster Name,
Disk Q and MSDTC) all other resourses are in another group, I am still
confused as too why SQL says it is online but the user/app cannot connect,
by restarting SQL server in studion management it comes online.
Thanks again,
Bob Smith
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:%23VBACR5VIHA.4140@.TK2MSFTNGP04.phx.gbl...
> Quorum must be in the cluster group. It is the reason the group exists.
> The Quorum disk prevents split-brain problems. The Cluster group should
> also have an IP Address and a Network Name Resource.
> You can put the MSDTC resource in there too, but it can cause problems on
> some very high volume systems.
> All SQL resources should be in a different group. Note that disks are
> physical resources. Logical OS partitions of the same disk cannot be
> split into multiple groups.
> --
> Geoff N. Hiten
> Senior SQL Infrastructure Consultant
> Microsoft SQL Server MVP
>
>
> "Bob Smith" <BobSmith@.discussions.microsoft.com> wrote in message
> news:1BD77D34-DC9D-4CB6-8325-9D32F50C9B58@.microsoft.com...
>
|||Maybe an IP address conflict or a dependency error. Again, the application
log should say something.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Bob Smith" <bob@.neconsulting.net> wrote in message
news:4E7A31CB-2900-4ED3-A7A9-1B0800B2128C@.microsoft.com...
> Geoff,
> Thanks, that is how it is setup Cluster group (Cluster IP, Cluster Name,
> Disk Q and MSDTC) all other resourses are in another group, I am still
> confused as too why SQL says it is online but the user/app cannot connect,
> by restarting SQL server in studion management it comes online.
> Thanks again,
> Bob Smith
> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
> news:%23VBACR5VIHA.4140@.TK2MSFTNGP04.phx.gbl...
>

Cllient Unable to establish connection

Hi Am using a SQL 2k server and have been regularly logging into other SQL 2K servers in the network using the SQL Query Analyser/Enterprise Manager. After suffering a BSD yesterday, unable to log in to any server from my Query Analyser/Enterprise Manager - get this error: "Client Unable to Establish Connection".
Others are also not able establish connection - they get a General Network error when trying to connecting to my server.
Think the Blue screen death corrupted some SQL driver in the process. Now am apprehensive about uninstalling and re-installing the SQL server since am unable to backup the databases.
Can anybody help please?SQL 2k?

I find it very unlikely...did you bounce the box?

Did and admin revoke your rights?

Blue screen of death? Haven;'t seen that in a loong while.

What o/s and what patches?|||SQL 2K with SP 3. Running on Win 2k (SP4) Server. There has been no change in the admin rights. it just stopped working after the crash.
that's why its confusing.. not much help from Miscrosoft either.

Originally posted by Brett Kaiser
SQL 2k?

I find it very unlikely...did you bounce the box?

Did and admin revoke your rights?

Blue screen of death? Haven;'t seen that in a loong while.

What o/s and what patches?|||Check your Client Config utility ? Try creating an alias using TCP/IP ..

What SQl Client you are using from where you accessing SQL Server ..?|||Tried the Client Network Utility - the TCP/IP option is not enabled when i try to add an alias. Only the Multiple Protocol, Apple Talk, VIA and "Other" options are enabled.
The server is installed in my laptop and am accessing from the same machine using the SQL Query Analyser. The laptop is a Win2k Server (SP4).

Originally posted by aashu
Check your Client Config utility ? Try creating an alias using TCP/IP ..

What SQl Client you are using from where you accessing SQL Server ..?

Client unable to establish connection Encryption not supported on SQL Server. (Microsoft SQL Nat

On Windows XP systems I get the following issue when trying to browse the MSDB folder in SSIS

Client unable to establish connection
Encryption not supported on SQL Server. (Microsoft SQL Native Client)

I have noticed another post where several others have noticed the same issue. It appears to only occur on Windows XP installations. Is there a workaround or fix for this?

Is the SQL 2005 instance the default or named instance? If it is named instance you need to edit SSIS service configuration file to point to appropriate instance. The process is described in SQL Books Online.|||It is the default instance.

Client connection error while trying to create maintenane plans

Error: Ole db error 0x80004005 Client unable to establish connection

This happens when trying to create a maintenance plan in sql 2005 sp 1

It has now happend with 3 installs - one fresh install and two upgrades from 2000 to 2005. The startup account for sql server is a domain user account and has not been changed. This happens on both windows 2000 and windows 2003.

This however does not happen if the sql startup account is in the local admin group for the machine

Any help is greatly appreciated

Thanks

KR

Refer this link , i hope it will solve u r problem.

http://support.microsoft.com/kb/253500/

also upgrade to SP2 , there are lot of enhancement done Maintenance plan wizards in SP2

Refer : http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1266171&SiteID=1

Madhu

|||

This happens when the client is on the same machine, so the first link would probably not apply in this case as it deals with remote connections.

Thanks

KR

Client Acces thru Router

SQL Client PC attached to LAN port of cisco 1721 router at
remote T1 site unable to access port 1433 on SQL Server on
LAN port of a cisco 1721 router on the local site.
NETSTAT showed the Local Address port 1042 accessing
SQL Server port 1433 State of TIME_WAIT.
Same PC can ping and access files on the SQL Server.
Moved PC to local site with SQL server and it worked with
no problems.
There is no firewall being used.
What could cause the 1721 router to block access to a SQL
Server port 1433.
Thanks, KenYou'll need to make network traces at the client and server to determine
where the problem is.
You could also try telneting to the same port to verify that the traffic is
going thru.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Thanks for your reply
I am able to telent into the SQL Server as you suggested.
I also did a ping with 1500 byte packet size for 3 min
and it ran 100% with average time of 170ms. I will see
about setting up a trace on both ends.
Any other thoughts since we know traffic is getting thru.
Thanks Ken
>--Original Message--
>You'll need to make network traces at the client and
server to determine
>where the problem is.
>You could also try telneting to the same port to verify
that the traffic is
>going thru.
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and
confers no rights.
>
>.
>|||I found my human error to this problem.
I misspelled the domain name in the dns configuration
on the remote Windows 98 pc.
Thanks for your time and thoughts.
Ken

>--Original Message--
>You'll need to make network traces at the client and
server to determine
>where the problem is.
>You could also try telneting to the same port to verify
that the traffic is
>going thru.
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and
confers no rights.
>
>.
>|||No problem.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Client Acces thru Router

SQL Client PC attached to LAN port of Cisco 1721 router at
remote T1 site unable to access port 1433 on SQL Server on
LAN port of a Cisco 1721 router on the local site.
NETSTAT showed the Local Address port 1042 accessing
SQL Server port 1433 State of TIME_WAIT.
Same PC can ping and access files on the SQL Server.
Moved PC to local site with SQL server and it worked with
no problems.
There is no firewall being used.
What could cause the 1721 router to block access to a SQL
Server port 1433.
Thanks, Ken
You'll need to make network traces at the client and server to determine
where the problem is.
You could also try telneting to the same port to verify that the traffic is
going thru.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||Thanks for your reply
I am able to telent into the SQL Server as you suggested.
I also did a ping with 1500 byte packet size for 3 min
and it ran 100% with average time of 170ms. I will see
about setting up a trace on both ends.
Any other thoughts since we know traffic is getting thru.
Thanks Ken
>--Original Message--
>You'll need to make network traces at the client and
server to determine
>where the problem is.
>You could also try telneting to the same port to verify
that the traffic is
>going thru.
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and
confers no rights.
>
>.
>
|||I found my human error to this problem.
I misspelled the domain name in the dns configuration
on the remote windows 98 pc.
Thanks for your time and thoughts.
Ken

>--Original Message--
>You'll need to make network traces at the client and
server to determine
>where the problem is.
>You could also try telneting to the same port to verify
that the traffic is
>going thru.
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and
confers no rights.
>
>.
>
|||No problem.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.