Here's our issue
We have a windows 2012 MSCS Failover cluster consisting of 2 nodes. The cluster has several windows generic service resources setup all of which are dependent on the cluster name/IP. In each of the cluster services we set it to not use the cluster name (clustered service properties -> Use network name for computer name). For some reason, one of the services is still registering its connection (this is a proprietary connection record in our application) in the database as the cluster name. I am looking for help/ideas why this could be happening. It is causing clients to connect using the record in our database (proprietary connection record) and due to application limitations there is some data corruption. We cannot recompile the application to fix it with code.
In our test environment we can make the issue happen and mitigate it by simply checking / unchecking the box to use the cluster name (the setting noted above). For some reason, in production that check box doesn't seem to make difference.
We have a windows 2012 MSCS Failover cluster consisting of 2 nodes. The cluster has several windows generic service resources setup all of which are dependent on the cluster name/IP. In each of the cluster services we set it to not use the cluster name (clustered service properties -> Use network name for computer name). For some reason, one of the services is still registering its connection (this is a proprietary connection record in our application) in the database as the cluster name. I am looking for help/ideas why this could be happening. It is causing clients to connect using the record in our database (proprietary connection record) and due to application limitations there is some data corruption. We cannot recompile the application to fix it with code.
In our test environment we can make the issue happen and mitigate it by simply checking / unchecking the box to use the cluster name (the setting noted above). For some reason, in production that check box doesn't seem to make difference.