No Failover and client crashes ODBC DSN Setting for Failover in connection String

We have set up Mirroring with a witness server and everything works fine when we failover from the SQL Management console.

However, if we failover when our Maccola client is connected, the client blows up - clearly because it can no longer connect to the database.

The ODBC DSN used by the Maccola client shows a checkbox for the 'select a failover server' but the checkbox is grayed out.

Also the summary of settings for the DSN at the end of the wizard reveals that the failover to server (y/N) option is set to N.

The default setting for this DSN is 'populate the remaining values by querying the server' but it doesn't appear to be getting the settings for failover from the server or any other interactive DSN settings either. The server is clearly set for mirroring.

Another suspicious item is that the DSN cannot connect to the server with SA permissions, even though the server is set to mixed security and we use the correct authentication.

Is it possible that the client MACHINE is not authenticating with the domain or sql server properly. We are logged into the client with the domain account that is the SQL admin account on the sql server box.

We should be able to interact with the sql server settings through the ODBC DSN on the client shoulnd't we?

Are we missing a service pack on the client?

Thanks,

Kimball

Have you referred to Maccola vendor in this case about the compatibility, I would guess this is to with that drivers.

No Failover and client crashes ODBC DSN Setting for Failover in connection String

We have set up Mirroring with a witness server and everything works fine when we failover from the SQL Management console.

However, if we failover when our Maccola client is connected, the client blows up - clearly because it can no longer connect to the database.

The ODBC DSN used by the Maccola client shows a checkbox for the 'select a failover server' but the checkbox is grayed out.

Also the summary of settings for the DSN at the end of the wizard reveals that the failover to server (y/N) option is set to N.

The default setting for this DSN is 'populate the remaining values by querying the server' but it doesn't appear to be getting the settings for failover from the server or any other interactive DSN settings either. The server is clearly set for mirroring.

Another suspicious item is that the DSN cannot connect to the server with SA permissions, even though the server is set to mixed security and we use the correct authentication.

Is it possible that the client MACHINE is not authenticating with the domain or sql server properly. We are logged into the client with the domain account that is the SQL admin account on the sql server box.

We should be able to interact with the sql server settings through the ODBC DSN on the client shoulnd't we?

Are we missing a service pack on the client?

Thanks,

Kimball

Have you referred to Maccola vendor in this case about the compatibility, I would guess this is to with that drivers.

NLB Web App accessing Cluster SQL 2005

Hello Friends
I have a project that will use Failover Cluster for SQL 2005 and NLB for the
web server front-end (using IIS).
That web application will be developed in-house. there are any special
programming considerations that the programmers must embed in the application
in order to support the special features of Failover and NLB clusters?
Does the web App Server must be Cluster-Aware to interact to SQL 2005
Failover Cluster?
Can you please give me any links to some documents that reflect these
situations?
Thanks for Help
Bruno
No. If it can connect to the SQL Server, you are set for the application.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Bruno" <Bruno@.discussions.microsoft.com> wrote in message
news:D6B04BF1-9730-46AA-A6E9-EBFC5C6B4C2D@.microsoft.com...
> Hello Friends
> I have a project that will use Failover Cluster for SQL 2005 and NLB for
> the
> web server front-end (using IIS).
> That web application will be developed in-house. there are any special
> programming considerations that the programmers must embed in the
> application
> in order to support the special features of Failover and NLB clusters?
> Does the web App Server must be Cluster-Aware to interact to SQL 2005
> Failover Cluster?
> Can you please give me any links to some documents that reflect these
> situations?
> Thanks for Help
> Bruno
|||Any SQL client application can connect to a SQL Cluster with no changes. I
recommend using non-persistent connections so the web app can recover in
case of a cluster failover, but that has been general programming practice
for a while now. Your NLB session model and the application session model
will need to work together. I.E. if you only support local sessions in IIS,
you will need to make sure your NLB sessions are "sticky". Your Network
Engineer can help with this.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Bruno" <Bruno@.discussions.microsoft.com> wrote in message
news:D6B04BF1-9730-46AA-A6E9-EBFC5C6B4C2D@.microsoft.com...
> Hello Friends
> I have a project that will use Failover Cluster for SQL 2005 and NLB for
> the
> web server front-end (using IIS).
> That web application will be developed in-house. there are any special
> programming considerations that the programmers must embed in the
> application
> in order to support the special features of Failover and NLB clusters?
> Does the web App Server must be Cluster-Aware to interact to SQL 2005
> Failover Cluster?
> Can you please give me any links to some documents that reflect these
> situations?
> Thanks for Help
> Bruno
|||You need to have reconnect logic built into the application. Whenever a
failover occurs, you will loose connectivity. The advantage of this
solution, however, is that the failover happens automatically, and is
relatively brief.
On the NLB, you need to program "stateless" apps. That is, you can not
guarantee that recovered session are redirect to the same web server during
each pass. If only one server is aware of the state, you find the user
orphaned if redirected to one of the other servers.
Also, to keep your solution clean and to harden security, consider using
some sort of middleware, either through dedicated application hosts, or some
sort of messaging platform.
Sincerely,
Anthony Thomas

"Bruno" <Bruno@.discussions.microsoft.com> wrote in message
news:D6B04BF1-9730-46AA-A6E9-EBFC5C6B4C2D@.microsoft.com...
> Hello Friends
> I have a project that will use Failover Cluster for SQL 2005 and NLB for
the
> web server front-end (using IIS).
> That web application will be developed in-house. there are any special
> programming considerations that the programmers must embed in the
application
> in order to support the special features of Failover and NLB clusters?
> Does the web App Server must be Cluster-Aware to interact to SQL 2005
> Failover Cluster?
> Can you please give me any links to some documents that reflect these
> situations?
> Thanks for Help
> Bruno

nic failover

Hello,
when i purposely cuase a failure of the public nics, why doesnt my node1
failover over to node2? is this by design or is there something i can set in
cluster administrator to do this?
thank you
calvin
Hi
Did you unplug the cable or did you disable the adaptor?
For a failover, the private and public NIC need to be lost.
If a failover were to be initiated by a NIC failure, there might be
scenarios where you loose communications for a few seconds, and it starts to
ping-pong the servers.
You may want to look at redundant NIC's if this is an issue for you.
Regards
Mike
"Calvin Do" wrote:

> Hello,
> when i purposely cuase a failure of the public nics, why doesnt my node1
> failover over to node2? is this by design or is there something i can set in
> cluster administrator to do this?
> thank you
> calvin
>
>