Vista - Stdout Redirection Causes the Exception "The OS handle's position

04-28-2008

My PowerShell script is failing with this error: Write-Host : The OS handle's
position is not what FileStream expected. Do not use a handle simultaneously
in one FileStream and in Win32 code or another FileStream.

You will see this problem if the following conditions are all true:

1) The console output of a PowerShell script is redirected.
2) The PowerShell script outputs information to the console (write-host).
3) The PowerShell script creates another process that also contains console
output statements (for example, runs a .vbs script that outputs to the
console using wscript.echo).

C:\TempFolder>powershell ./test.ps1 > output.txt

After further testing it appears this issue only surfaces when the
PowerShell script is spawned from a Command Shell (see Cmd_Example.gif). The
issue does not surface when the script is spawned within PowerShell.

Is anyone aware of a workaround for this issue?

Thanks in advance.

05-06-2008

Unfortunately, this still appears to be an issue in PowerShell CTP2. Any
hopes of getting this corrected?

"javacavaj" wrote:

Quote:

> My PowerShell script is failing with this error: Write-Host : The OS handle's
> position is not what FileStream expected. Do not use a handle simultaneously
> in one FileStream and in Win32 code or another FileStream.
>
> You will see this problem if the following conditions are all true:
>
> 1) The console output of a PowerShell script is redirected.
> 2) The PowerShell script outputs information to the console (write-host).
> 3) The PowerShell script creates another process that also contains console
> output statements (for example, runs a .vbs script that outputs to the
> console using wscript.echo).
>
> C:\TempFolder>powershell ./test.ps1 > output.txt
>
> After further testing it appears this issue only surfaces when the
> PowerShell script is spawned from a Command Shell (see Cmd_Example.gif). The
> issue does not surface when the script is spawned within PowerShell.
>
> Is anyone aware of a workaround for this issue?
>
> Thanks in advance.
>
>

04-28-2008	#1 (permalink)
javacavaj n/a posts	Stdout Redirection Causes the Exception "The OS handle's position My PowerShell script is failing with this error: Write-Host : The OS handle's position is not what FileStream expected. Do not use a handle simultaneously in one FileStream and in Win32 code or another FileStream. You will see this problem if the following conditions are all true: 1) The console output of a PowerShell script is redirected. 2) The PowerShell script outputs information to the console (write-host). 3) The PowerShell script creates another process that also contains console output statements (for example, runs a .vbs script that outputs to the console using wscript.echo). C:\TempFolder>powershell ./test.ps1 > output.txt After further testing it appears this issue only surfaces when the PowerShell script is spawned from a Command Shell (see Cmd_Example.gif). The issue does not surface when the script is spawned within PowerShell. Is anyone aware of a workaround for this issue? Thanks in advance.
My System Specs

05-06-2008	#2 (permalink)
javacavaj n/a posts	RE: Stdout Redirection Causes the Exception "The OS handle's position Unfortunately, this still appears to be an issue in PowerShell CTP2. Any hopes of getting this corrected? "javacavaj" wrote: Quote: > My PowerShell script is failing with this error: Write-Host : The OS handle's > position is not what FileStream expected. Do not use a handle simultaneously > in one FileStream and in Win32 code or another FileStream. > > You will see this problem if the following conditions are all true: > > 1) The console output of a PowerShell script is redirected. > 2) The PowerShell script outputs information to the console (write-host). > 3) The PowerShell script creates another process that also contains console > output statements (for example, runs a .vbs script that outputs to the > console using wscript.echo). > > C:\TempFolder>powershell ./test.ps1 > output.txt > > After further testing it appears this issue only surfaces when the > PowerShell script is spawned from a Command Shell (see Cmd_Example.gif). The > issue does not surface when the script is spawned within PowerShell. > > Is anyone aware of a workaround for this issue? > > Thanks in advance. > >
My System Specs

Similar Threads
Thread	Forum
Exception calling "CreateInstance" with "2" argument(s): for Microsoft.Update.UpdateColl	PowerShell
PS Bug: The OS handle's position is not what FileStream expected.	PowerShell
redirect powershell stdout to objShell.Exec.Stdout.ReadAll()(	PowerShell
stdout redirection	PowerShell
Redirection of stdout adding lots of empty lines	PowerShell