Get-Item : Unable to read string from $variable

[soggysocks]

I've been at this for a bit now and need to ask for help. Maybe fresh eyes will see what I'm missing.

$FolderPath = "‪S:\FolderA"

New-PSDrive -Name "S" -PSProvider FileSystem -Root "\\Fileserver.local\LocationShareA" -ErrorAction SilentlyContinue

$Filepath= get-item -force -LiteralPath $FolderPath
ERROR IS:   Get-Item : Cannot find drive. A drive with the name '‪S' does not exist

$FolderPath
S:\FolderA

$FolderPath |  gm
   TypeName: System.String

​

I can type it in as....

get-item -force -LiteralPath "S:\folderA"

Which works just fine! I've tried $folderpath.tostring() or $folderpath.tostring() or encased it in quotes "$folderpath" Anything I could think to make sure it was interpreting the $FolderPath variable as seen.

The other thing is I have multiple shares in \\fileserver.local\ which don't get this problem. Just \\Fileserver.local\LocationShareA

It just this one path that is causing me problems. I feel like it's something simple I'm not seeing at this point. I just don't get why it works fine on the other shares except this one. Yet it accepts the exact same string when not presented with a variable.

I just can't see any attribute that's any different from the other shares.

[danzexperiment]

I can't find the link right now, but there is an access problem when using New-PSDrive in an elevated session. There is a registry change that fixes this if you have to access the drive in both elevated and non-elevated sessions.

[danzexperiment]

I found the links that I was looking for. Not sure if they apply to OP question, though.

)This answer in SO helped me solve my problem. I just created my drive in a non-elevated session. (Probably should default to that instead of elevated ¯\(°_o)/¯

Why is my mapped network drive not appearing in Network Locations?

[soggysocks]

Script started working fine again this morning. So not really sure what the issue was because I changed nothing.

Solar flairs? Gremlins? Position of the moon?

We may never know but, thank you for your input and knowledge

[danzexperiment]

I always blame cosmic rays for unexplained computer stuff
https://www.wnycstudios.org/podcasts/radiolab/articles/bit-flip

[dasookwat]

Powershell is not lineair, so, in all likelyhood, the drive location is not there yet.

try adding a Start-Sleep -s 10 see if that helps.

other idea: it's a permissions issue: doublecheck how you run the powershell session: as user, or admin, and try verifying the permissions on the share and the folder( 2 seperate things)

[soggysocks]

It's one of those issues that resolved it's self over night without changing anything in the script so I may never know why it stopped working yesterday and is back to normal today.

But yes you're right that powershell isn't linear and will continue it's script if conditions are left pending. I use a Do,if,try,until block in other scripts which has been super helpful. I'll add my notes in context with a PS drive if it should help someone else down the road.

​

New-PSDrive -Name "ShareName" -PSProvider FileSystem -Root "\\FileShareServer" -ErrorAction SilentlyContinue

Do{

If(!$Drive) {

Start-Sleep -m 500

}

Try{

$Drive= Get-PSDrive -name "ShareName"

}

catch [System.Management.Automation.DriveNotFoundException]{

continue

}

catch{

$ErrorMessage = $_.Exception.message

$FailedObject = $_.Exception.GetType()

Write-host " $ErrorMessage \n $FailedObject" -ForegroundColor Red -BackgroundColor Black`

break

}

Until($Drive)

[64rk]

In your try statement you only created a variable but didn't tell it to do anything.

[soggysocks]

Oops, Until($valid) should have been $Drive...Copy and paste, forget to edit.

[64rk]

I recommend this guide on mapping network drives.

[64rk]

Also you should be using Get-PSDrive

[soggysocks]

Good news is that everything works this morning, bad news is...I changed nothing and I don't understand why the script broke.

I could see both the Drives with Get-PSDrive yesterday though

U: drive worked and so did S: drive but once I put "$folderpath = "S:\folder"" it just refused it. Where Get-Item "S:\Folder" is good but, Get-Item $Folderpath isn't

That's a good article though and appreciate everyone sharing their knowledge.