I'm having trouble adding an additional SQL Server 2012 node on a Server 2012R2 failover cluster, but only for one instance.
Installing a new node succeeds, and installing the second node to a new instance succeeds, but the installer hangs indefinitely with a "please wait" at the "specify service accounts" screen. The only way to exit/kill the installer is to use task manager to kill the ScenarioEngine process. I've even let the installer stay in this "please wait" state for two straight days. No network traffic, no open connections, and no processes appear in "wait state" that I can see. Domain authentication is verified to be okay on both nodes of this failover cluster.
This particular instance was installed on the failover cluster when it only had one node (the second node was down and the cluster had only one node configured at the time).
The installer does see the existing failover cluster instance and all checks pass with the exception of one warning about the non-clustered DTC.
It doesn't matter what we enter for credentials on the service account screen. Leaving all passwords blank or entering verified correct passwords gives the same result. The actual service account the existing instance was installed with: SQL Full-Text filter daemon account is LocalSystem, and the SQL Server accounts use a specific domain user.
Again, adding a new instance using the same credentials succeeds and adding a second node to that instance succeeds. I don't know what's unique about this particular existing instance that is causing the installer to lock up.
I've come across other people having this same issue, but the solutions they arrived at don't seem to my particular installation.
Is there an installation logfile/statefile that I can inspect or supply to this thread?
(submitted by Erik S, using MSDN role account)