July 22, 2013 at 11:28 pm
I have two node windows cluster on which SQL2008 R2 is running. When I execute SQLPS, it throws error "Drive root "E:\" does not exist or it's not a folder.". If I execute same on other node it throws error for different drive. I know since it is cluster, these drives are owned by respective nodes and wont be available from other nodes. Because of this, I can not execute SQLPS in windows scheduler as well as in SQL Agent job. It is failing before it is processing the PS1 file itself.
I dont know there is any switches or command parameter which will bypass this error.
Chandu
July 23, 2013 at 1:58 am
What version and patch level of SQL are you running?
There is a connect issue related to 2008 SP3 where sqlps is not working properly in a clustered environment:
Could be something similar. You could work around the issue by installing powershell seperately and calling that as a CmdExec step from SQL agent.
July 23, 2013 at 4:32 am
Andrew,
Thanks for your response.
It is SQL2008 RTM. You mean this behavour is been taken care in Service pack and this is know issue with SQLPS ???? Even this is happening with Powershell as well. It is checking for drives available in my computer. Since these drives are owned by other node, it is not accessible.
Chandu
July 24, 2013 at 1:52 am
Actually since you get the error with normal Powershell as well, it's not patch related.
Very unusual.. I havent seen that issue on any clustered SQL servers.
The only related problem I could find is this:
http://www.vistax64.com/powershell/24567-provider-health-how-turn-if-off.html
but that's powershell v1 and is from 2006, same error though.
You should take this query to a powershell forum or directly with a Microsoft support.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply