While installing a two node SQL Server 2008 Cluster on Windows 2008, I came across a problem with the syssubsystems table, PowerShell and the location of the SQLPS executable.
We have two local drives (C and D) on each node. Two folders are created on the D drive on Node 1:
D:\Program Files\Microsoft SQL Server D:\Program Files (x86)\Microsoft SQL Server
The shared components are installed here.
One folder is created on the Node 2 D: drive:
D:\Program Files\Microsoft SQL Server
And, on the C: drive:
C:\Program Files (x86)\Microsoft SQL Server
The PowerShell executable is located in the Program Files (x86)\Microsoft SQL Server folder.
If you query the syssubsytem table while Node 1 is active the agent_exe will point to the PowerShell exe on the D drive.
After moving the SQL Server resource to Node 2, the syssubsystems results will continue to point to the PowerShell exe on the D drive. The problem is that the path does not even exist on Node 2. The path to the exe is on the C drive.
Any process that requires PowerShell will now fail, as long as Node 2 is the active node of the cluster.
Has anyone else experienced this? I’ve tried to create the cluster using the Integrated Install, the Advanced/Enterprise Install and a command line install with always the same results.
Any additional information on this problem will be appreciated.