VMware Cloud Community
Spectrum1981
Enthusiast
Enthusiast
Jump to solution

PowerCLI Update Manager not working

Hi all.

i have a problem with the update manager PowerCLI addon.

I am having a vcenter 5.5 (installed on a Server 2012 R2) latest version and VMware-PowerCLI-5.5.0-1295336 and VMware-UpdateManager-Pscli-5.5.0-1302474 installed on it.

Every time i call a vum cmdlet the powershell stopp working. Error is Process is terminated due to StackOverflowException

Problem signature:

  Problem Event Name:    APPCRASH

  Application Name:    powershell.exe

  Application Version:    6.3.9600.16384

  Application Timestamp:    5215ef23

  Fault Module Name:    ntdll.dll

  Fault Module Version:    6.3.9600.16408

  Fault Module Timestamp:    523d5305

  Exception Code:    c0000005

  Exception Offset:    0000000000055a0b

  OS Version:    6.3.9600.2.0.0.272.7

  Locale ID:    1031

  Additional Information 1:    ba05

  Additional Information 2:    ba05ba065b7271e9ac272dfe3756584e

  Additional Information 3:    5c6f

  Additional Information 4:    5c6f680ba1c900288b9bf1202b7d9156

Read our privacy statement online:

  http://go.microsoft.com/fwlink/?linkid=280262

If the online privacy statement is not available, please read our privacy statement offline:

  C:\Windows\system32\en-US\erofflps.txt

What ca i do to get Update Manager cmdlet working?

0 Kudos
1 Solution

Accepted Solutions
Spectrum1981
Enthusiast
Enthusiast
Jump to solution

Hi LucD,

i found the problem. It looks like that there was a problem with .net

This fix http://www.microsoft.com/en-us/download/details.aspx?id=30135 found the problem and solved it. Now everything workes fine.

Big thanks for your support!

Rainer

View solution in original post

0 Kudos
15 Replies
LucD
Leadership
Leadership
Jump to solution

Have a look at StackOverflowException with Update Manager PowerCLI and WMF v3


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

0 Kudos
Spectrum1981
Enthusiast
Enthusiast
Jump to solution

That sounds good, but in "normal" powershell:

Name                           Value                                                                                  

----                           -----                                                                                  

PSVersion                      4.0                                                                                    

WSManStackVersion              3.0                                                                                    

SerializationVersion           1.1.0.1                                                                                

CLRVersion                     4.0.30319.34003                                                                        

BuildVersion                   6.3.9600.16394                                                                         

PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0}                                                                   

PSRemotingProtocolVersion      2.2                                                                                    

And now startet with %SystemRoot%\system32\WindowsPowerShell\v1.0\powershell.exe -version 2


Name                           Value                                          

----                           -----                                          

PSVersion                      4.0                                            

WSManStackVersion              3.0                                            

SerializationVersion           1.1.0.1                                        

CLRVersion                     4.0.30319.34003                                

BuildVersion                   6.3.9600.16394                                 

PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0}                           

PSRemotingProtocolVersion      2.2                                            

No Change an VUM cmdlets still not working. PowerShell 2.0 und .net are installed.

0 Kudos
LucD
Leadership
Leadership
Jump to solution

What memory is defined for a PS session, can you check with.

Get-Item wsman:localhost\Shell\MaxMemoryPerShellMB

And perhaps try increasing the value with (the example changes the value to 2GB)

Set-Item wsman:localhost\Shell\MaxMemoryPerShellMB 2048


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

0 Kudos
Spectrum1981
Enthusiast
Enthusiast
Jump to solution

Set to 2048 but still the same problem.

0 Kudos
LucD
Leadership
Leadership
Jump to solution

Coming back, in my test I do see PS v2 when I start with the -Version 2 parameter.

psv2.png


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

0 Kudos
Spectrum1981
Enthusiast
Enthusiast
Jump to solution

pastedImage_0.png

0 Kudos
LucD
Leadership
Leadership
Jump to solution

What OS is this ?


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

0 Kudos
Spectrum1981
Enthusiast
Enthusiast
Jump to solution

It is Windows Server 2012 R2

0 Kudos
LucD
Leadership
Leadership
Jump to solution

So is the platform where I did my tests.

Confused about the difference in build numbers.

Is this an installation with a regional MUI ?

What does Get-Host return ?


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

0 Kudos
Spectrum1981
Enthusiast
Enthusiast
Jump to solution

No, it is an installation with english os and no language pack oder something else.

Name             : ConsoleHost

Version          : 4.0

InstanceId       : fc5a4174-03a0-49b6-ac4d-933dab1ccea8

UI               : System.Management.Automation.Internal.Host.InternalHostUserI

                   nterface

CurrentCulture   : de-DE

CurrentUICulture : en-US

PrivateData      : Microsoft.PowerShell.ConsoleHost+ConsoleColorProxy

IsRunspacePushed : False

Runspace         : System.Management.Automation.Runspaces.LocalRunspace

0 Kudos
LucD
Leadership
Leadership
Jump to solution

A wild guess, did you already try changing the culture for en-US ?


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

0 Kudos
Spectrum1981
Enthusiast
Enthusiast
Jump to solution

No. On other win 2012 R2 server it will work. And they all come from the same image :smileyshocked:

0 Kudos
LucD
Leadership
Leadership
Jump to solution

And do you see the same PowerShell build number on that other server ?

Could they be at different patch levels ?


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

0 Kudos
Spectrum1981
Enthusiast
Enthusiast
Jump to solution

Hi LucD,

i found the problem. It looks like that there was a problem with .net

This fix http://www.microsoft.com/en-us/download/details.aspx?id=30135 found the problem and solved it. Now everything workes fine.

Big thanks for your support!

Rainer

0 Kudos
LucD
Leadership
Leadership
Jump to solution

Great, thanks for sharing the solution


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

0 Kudos