InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comSun, 19 May 2013 04:05:24 GMT20http://www.sqlservercentral.com/Forums/Topic1401327-1549-1.aspx[quote][b]Perry Whittle (1/2/2013)[/b][hr]what is the exact version of your sql server instance?There was a small bug with the shared tools install on a cluster, you would install the new instance on the first node and set the tools install location to H:\whateverSubsequent add node installs however would use the default of the c drive, I believe this may be what you are experiencing[/quote]ThanksSQL 2008 Service Pack 3 (10.0.5500)I am aware of that bug, it's been pointed out at [url]http://connect.microsoft.com/SQLServer/feedback/details/559435/log-shipping-stops-working-on-clustered-instance-if-failed-over-to-another-node[/url]My situation is a bit different. We have always used H:\whatever as our installation folder and we have failed over between nodes a few times, with no issues. The sqllogship.exe location always reflected as H:\whatever in the Job Step properties and it always worked after failover.After our last failover, SQL has replaced the sqllogship.exe location in the Job Step properties from H:\whateverto c:\program files\microsoft sql server\100\tools\binn In our case, the H: drive is not Clustered and is local to both nodes.ThanksWed, 02 Jan 2013 05:28:27 GMTSQLSACThttp://www.sqlservercentral.com/Forums/Topic1401327-1549-1.aspxwhat is the exact version of your sql server instance?There was a small bug with the shared tools install on a cluster, you would install the new instance on the first node and set the tools install location to H:\whateverSubsequent add node installs however would use the default of the c drive, I believe this may be what you are experiencingWed, 02 Jan 2013 05:19:41 GMTPerry Whittlehttp://www.sqlservercentral.com/Forums/Topic1401327-1549-1.aspxHi AllEnvironment: 2 Node Cluster, Win2008 Ent, SQL 2008 Sp3 EntLog Shipping was always working fine, even after failover between nodes.After the last failover, the backup job started failing with error "Log Shipping job failed with error: The process could not be created for step 1"I checked the step properties of the backup job and it seems that the path to the sqllogship.exe has changed in the job. Why would this happen?We don't use the usual C: drive for our installations. Up until now, the location always reflected in the job step properties as "h:\Services\Microsoft SQL Server\100\Tools\Binn\sqllogship.exe". Now it shows as "C:\Services\Microsoft SQL Server\100\Tools\Binn\sqllogship.exe"Any Ideas why this happened?ThanksMon, 31 Dec 2012 02:55:41 GMTSQLSACT