You are currently offline, waiting for your internet to reconnect

Your browser is out-of-date

You need to update your browser to use the site.

Update to the latest version of Internet Explorer

FIX: Shared components are installed in the wrong location when you implement a SQL Server 2008 or SQL Server 2012 Failover Cluster installation

Microsoft distributes Microsoft SQL Server 2008 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release.
Symptoms
Consider the following scenario in Microsoft SQL Server 2008 or SQL Server 2012:
  • You start the implementation of a SQL Server 2008 or SQL Server 2012 Failover Cluster installation.
  • You add a node to the failover cluster.
  • You install the shared components for the node to a nondefault location. For example, you install the shared components in the following path if the operating system is installed on the drive C:
    D:\Program Files\Microsoft SQL Server
  • You add a second node to the failover cluster.
In this scenario, you experience the following symptoms:
  • The installation ignores the nondefault location and installs the shared components to the default location.
  • When a failover occurs in the cluster, the log shipping fails, and then you receive an error message that resembles the following:
    Job Step: "C:\Program Files\Microsoft SQL Server\100\Tools\Binn\sqllogship.exe" -Backup 11988AF6-DCC1-4785-90A5-978568E6C562 -server GVS10001 Message after failover on the copy job Message Executed as user: DOMAIN1\SQLService. The process could not be created for step 1 of job 0x3329AA27908BB548B5D78A9EA3D6A3DD (reason: The system cannot find the file specified). The step failed.
  • If the cluster has a PowerShell job when the failover occurs, or if you have a clear job that is created by SQL Server Policy Based Management (PBM) when the failover occurs, the job fails. Additionally, you receive the following error message:
    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. Log SQL Server Agent Message [125] Subsystem 'PowerShell' could not be loaded (reason: The system cannot find the path specified)
  • When you failover a job that references the Bcp.exe component, the job fails.
Cause
This problem occurs because the following components are installed in the wrong location:
  • SQL Powershell (Sqlps.exe)
  • Log shipping executable (SQLLogship.exe)
  • Bcp.exe and other components
The jobs that are created by using one of these components are located in different locations on both nodes. Therefore, when you failover the job, the job fails.

Note A clear job that is created by PBM has a PowerShell step. Therefore, the job references the Sqlps.exe component.
Resolution

Service Pack 2 information for SQL Server 2012

To resolve this issue, obtain the Service Pack 2 for SQL Server 2012. For more information, see Bugs that are fixed in SQL Server 2012 Service Pack 2 and How to obtain the latest service pack for SQL Server 2012

SQL Server 2008 Service Pack 1

The fix for this issue was first released in Cumulative Update 10 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2279604 Cumulative update package 10 for SQL Server 2008 Service Pack 1
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
970365 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released
Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

SQL Server 2008 Service Pack 2

The fix for this issue was first released in Cumulative Update 1 for SQL Server 2008 Service Pack 2. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2289254 Cumulative update 1 for SQL Server 2008 Service Pack 2
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2402659 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
For more information about failover clustering, visit the following Microsoft Developer Network (MSDN) website: For more information about Shared components, visit the"Shared Features" section in the following MSDN website:For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499New naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Properties

Article ID: 2028830 - Last Review: 02/10/2015 07:20:00 - Revision: 3.0

  • Microsoft SQL Server 2008 Developer
  • Microsoft SQL Server 2008 Enterprise
  • Microsoft SQL Server 2008 Standard
  • Microsoft SQL Server 2012 Developer
  • Microsoft SQL Server 2012 Enterprise
  • Microsoft SQL Server 2012 Standard
  • kbqfe kbfix kbsurveynew kbexpertiseadvanced KB2028830
Feedback
://c1.microsoft.com/c.gif?DI=4050&did=1&t="> var varCustomerTracking = 1; var Route = "76500"; var Ctrl = ""; document.write(" ')[0].appendChild(m);" onload="var m=document.createElement('meta');m.name='ms.dqp0';m.content='false';document.getElementsByTagName('head')[0].appendChild(m);" src="http://c1.microsoft.com/c.gif?"> >>