OutOfMemory Exception on remote execution using Powershell Invoke-Command

Question

I am trying to execute an exe on a remote computer using invoke-command. Executing the exe on the remote machine after logging into the machine using remote desktop takes 1GB of memory and executes to completion after a minute. Whereas when I execute the same exe using Invoke-Command on the same machine, the process returns an OutOfMemoryException and ends suddenly. My invoke command is as simple as Invoke-Command -Session $someSessionVariable -ScriptBlock {Invoke-Expression "abc.exe --arg arg"} -AsJob.

Am I missing something regarding the restrictions on remote invocation?

Thanks in Advance.

Why do you even use iex for calling a native program? PowerShell is a shell. Executing commands is what it does. — Joey
– Joey, Commented Mar 12, 2012 at 11:54
@Joey - while that is true, powershell has so MANY problems with passing the arguments to an external program that it is at times easier to just use iex — manojlds
– manojlds, Commented Mar 12, 2012 at 16:39
But iex ist just a layer above all that problems, at least how I understand it. You just add a layer of indirection while solving no problem at all. — Joey
– Joey, Commented Mar 12, 2012 at 18:49

EM0 · Accepted Answer · 2016-02-24 13:08:46Z

12

Complete PowerShell script, based on mjolinor's answer, for anyone who wants to skip the reasons and just make it work:

Set-Item WSMan:\localhost\Shell\MaxMemoryPerShellMB 1000000
Set-Item WSMan:\localhost\Plugin\Microsoft.PowerShell\Quotas\MaxMemoryPerShellMB 1000000
Restart-Service WinRM

answered Feb 24, 2016 at 13:08

EM0

6,5558 gold badges62 silver badges101 bronze badges

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

Comments

mjolinor · Accepted Answer · 2012-03-12 13:02:25Z

7

From:

http://msdn.microsoft.com/en-us/library/windows/desktop/aa384372(v=vs.85).aspx

The defult memory limit on remote shells is 150MB

MaxMemoryPerShellMB Specifies the maximum amount of memory allocated per shell, including the shell's child processes. The default is 150 MB.

answered Mar 12, 2012 at 13:02

mjolinor

68.7k7 gold badges118 silver badges141 bronze badges

2 Comments

manukranthk Over a year ago

Thanks for your reply. The page has many more default parameters that one using winrm has to checkout.

mjolinor Over a year ago

Using remote/background jobs means you're going to be dealing with constrained runspaces and deserialized objects being returned. What works in a local/unconstrained runspace may need to be re-factored to work in that enviroment.

Sasquatch · Accepted Answer · 2014-11-13 18:25:35Z

0

As an addition to mjolinor's answer, you can change the MaxMemoryPerShellMB by running:

sl WSMan:\localhost\Shell
Set-Item MaxMemoryPerShellMB 300

Ref: http://blogs.technet.com/b/heyscriptingguy/archive/2013/07/30/learn-how-to-configure-powershell-memory.aspx

answered Nov 13, 2014 at 18:25

Sasquatch

491 silver badge4 bronze badges

Collectives™ on Stack Overflow

OutOfMemory Exception on remote execution using Powershell Invoke-Command

3 Answers 3

Comments

2 Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

Comments

2 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related