December 19, 2012 at 7:59 pm
Greetings,
I have a script that was executing a powershell script from within a batch file with the following syntax:
"“powershell.exe -NoLogo -Noninteractive -Command "& \"%~dp0ScriptName.ps1\" %1; exit "
Everything was working fine until the OS team patched the server and upgraded Powershell to version 3 (it had version 2). After Powershell was upgraded the script failed with the error:
"powershell.exe' is not recognized as an internal or external command, operable program or batch file"
For the time being I have "fixed" the issue by executing powershell with an explicit path:
"C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe -NoLogo -Noninteractive -Command "& \"%~dp0ScriptName.ps1\" %1; exit"
Now, this change may make my script functional again, but I don't understand what exactly is going on. What changed when Powershell was upgraded that made the way I was calling the script invalid?
Any information or good links to information would be greatly appreciated.
Thanks!
Kim
December 24, 2012 at 1:47 pm
Chances are the path "%systemroot%\System32\WindowsPowerShell\v1.0\" was removed from the PATH system environment variable. Removing the path to powershell.exe from the PATH variable made it impossible for you to refer to powershell.exe from any random command line location without fully qualifying it.
As a side note the explicit path you decided to prefix your command with, "C:\Windows\SysWOW64\WindowsPowerShell\v1.0\", is the path to the 32-bit version of powershell.exe on 64-bit OS'es. Prior to the upgrade it is likely you were executing your script using the 64-bit version. Chances are it is not making a difference since you said the script is working but I thought it was worth pointing out.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply