Powershell script is changing the filepath to C:\Windows\system32

Question

I have Powershell ISE open as Administrator. When I execute the script from the desktop (e.g. C:\Users\myUser\Desktop\CompareScripts\runCompareScript.ps1), the script works fine. However, when I execute from the C:\CompareScripts\runCompareScript.ps1 the script changes the file path to C:\Windows\system32\runCompareScript.ps1. Why is this occurring and how can I prevent this from happening?

Note: This is happening during the execution of a invoke-sqlcmd statement.

It is not clear how you execute your script and it shouldn't change to C:\windows..., you can use $pwd for the current directory, to access data files in the user directory use: $env:UserProfile\Desktop\CompareScripts\foo.sql You may need to show more of your script for us to see what's going wrong. — Peter Hahndorf
– Peter Hahndorf, Commented Aug 3, 2017 at 2:43

user2674513 · Accepted Answer · 2017-08-03 01:34:54Z

2

The current working directory is changing as you change contexts. Use the absolute file path.

Invoke-Sqlcmd -InputFile "C:\Users\myUser\Desktop\CompareScripts\---.sql"

answered Aug 3, 2017 at 1:34

user2674513

Sign up to request clarification or add additional context in comments.

4 Comments

phil o.O Over a year ago

Why can't I do something a little more dynamic? Right now I'm using the following $rootDir = split-path -parent $MyInvocation.MyCommand.Definition; to get the current working directory. I know the statement works, because the extractRSPath in the above screenshot is correct yet the error thrown is not.

user2674513 Over a year ago

If you put a breakpoint on line 128 and run $extractPath when execution pauses, I guarantee the output is 'C:\Windows\system32\---.sql'. I can't explain why that is without seeing the script. With the information available, the best solution is to use an absolute path.

Ansgar Wiechers Over a year ago

@PhiL $rootDir is the location of your script, not your working directory. Compare the output of $rootDir and $PWD.Path. You can build an absolute path for the invoked script like this: Join-Path $rootDir 'something.sql'.

phil o.O Over a year ago

Thanks guys!. When Powershell ISE is initially opened the default working directory is C:\Windows\system32 and the statement that was causing the issue was in terms of a relative path (e.g. $sqlPath = $sqlScript). To resolve the issue, I changed it to $sqlPath = $rootDir + $sqlScript.

Collectives™ on Stack Overflow

Powershell script is changing the filepath to C:\Windows\system32

1 Answer 1

4 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

4 Comments

Your Answer

Sign up or log in

Post as a guest

Related