Application fails on cluster failover

  • Hi everyone

    I had a problem with one of the Application/service in my cluster.

    Initially 4 of the 5 applications are recited on node 1. and rest 1 on node 2.

    For some reason failover happened.

    All the applications moved to node 2.

    here comes The problem, Every application is working fine unless one.

    When i failback to node 1. it is working well

    Both the nodes are possible owners for the application.

    Any ideas please......

    rookie here :hehe:

  • Are you saying that you have SQL server database instances on a cluster and a particular application that uses them only works when it's database instance is running on one of the nodes of the cluster but not the other?

    Or are you saying that one of the databse instances only works on one node and not the other?

    When the database instance fails over to the other node does it come up successfully? Are you able to connect to the database via management studio when it is on the other node? Are you using static ports or dynamic? Is the browser running on both nodes? Is the Windows firewall blocking the port on the other node?

    Sorry, a lot of questions but it will help to understand what is happening.

    If it is applications running on the cluster rather than database instances, you may have to contact the vendor for support.

  • It is perfectly coming UP when getting failed over.

    The application is the one couldnot connect to the databases when failed over to the another node.

    We are using Static Ports

    I am not sure whether Browser working or not. (Dont know how to check that. can you please let me know so that i can check that., it could be a possibility)

    Windows firewall is not blocking anything

    I am able to connect with Management studio when DB gets FO

    Rookie :hehe:

  • Here are couple of common ways to access the SQL Server Browser service.

    •Through Windows Services MMC. Access Windows services through the control panel or enter services.msc in the run box.

    •Through a command prompt

    •Through SQL Server Configuration Manager (SQL Server 2005/2008)

    •Through Surface Area configuration (SAC, SQL Server 2005 only)

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply