October 6, 2010 at 7:35 am
Hey all,
Recently brought up a new 2008 R2 x64 cluster on Windows 2008 x64. When the instance is running on the secondary node of the cluster, this job fails stating: Unable to start execution of step 3 (reason: The PowerShell subsystem failed to load [see the SQLAGENT.OUT file for details]; The job has been suspended). The step failed.. I then checked SELECT agent_exe FROM msdb.dbo.syssubsystems WHERE start_entry_point ='PowerShellStart', and it shows the location of D:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\SQLPS.exe. This location does not exist on the secondary node.
When I installed on my primary node, I selected my D: for both the installation directory and shared feature directory. On this server, I then had a Program Files and Program Files (x86) on the D: of this node. However, when I went to the secondary node and used the "add a node to a cluster" option and finished the install, it only installed the Program Files directory on the D: of this node, and not the (x86) directory.
I realize I can change the location of the agent_exe, but more so than anything, I'm concerned to as why the secondary node did not add that Program Files (x86) directory.
Any thoughts?
Thanks
October 6, 2010 at 8:04 am
I found a similar thread for 2008 ... that according to Microsoft, has been resolved with SP2 ... what about R2 though? http://www.sqlservercentral.com/Forums/Topic772839-146-1.aspx
I'm opening a ticket with Microsoft now.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply