Remove From My Forums

VMM 2016 -- Error (20413) VMM encountered a critical exception and created an exception report at C:\ProgramData\VMMLogs\..

Question
0

Sign in to vote
I'm running the following infrastructure:

Server 2016 STD hosting:

VMM 2016 (4.0.1662.0)
SQL SRV2016 (13.1.4466.4)

vSphere 6.5.0 (7312210) hosting:

VMware ESXi, 6.5.0, (7388607) hosting:
   Win2012R2 VM

I have successfully added the ESXi servers and vSphere server into the VMM management server, however when I attempt to refresh a virtual machine that was created on the ESXi servers, I always get an error (20413) that is basically complaining that VMM doesn't understand the hardware being used by the ESXi server. I've tried several different configurations of VM's but nothing seems to make VMM happy. Is this expected behavior or should I be able to refresh virtual machines created on ESXi host from VMM? I thought this was the whole point of the VMM supporting vSphere.

Below is an example of the error string from one of the VM's I have running:

----------------------------------------------------
------------------- Error Report -------------------
----------------------------------------------------
Error report created 2/5/2018 5:09:20 PM
CLR is not terminating

----------------------------------------------------
--------------- Bucketing Parameters ---------------
----------------------------------------------------
EventType=VMM20
P1(appName)=vmmservice.exe
P2(appVersion)=4.0.2244.0
P3(assemblyName)=Engine.BitBos.dll
P4(assemblyVer)=4.0.2139.0
P5(methodName)=Microsoft.VirtualManager.Engine.BitBos.VMRefresherBase.UpdateAdditionalVMInfo
P6(exceptionType)=System.InvalidCastException
P7(callstackHash)=b5a

SCVMM Version=4.0.2244.0
SCVMM flavor=C-buddy-RTL-AMD64
Default Assembly Version=4.0.2244.0
Executable Name=vmmservice.exe
Executable Version=4.0.2244.0
Base Exception Target Site=140731448038400
Base Exception Assembly name=Engine.BitBos.dll
Base Exception Method Name=Microsoft.VirtualManager.Engine.BitBos.VMRefresherBase.UpdateAdditionalVMInfo
Exception Message=Unable to cast object of type 'Microsoft.Carmine.VMWareImplementation.VmwVMProcessorSetting' to type 'Microsoft.Carmine.VirtualizationAbstractionLayer.IVirProcessorSetting'.
EIP=0x00007fff0cbb3c58
Build bit-size=64

----------------------------------------------------
------------ exceptionObject.ToString() ------------
----------------------------------------------------
System.InvalidCastException: Unable to cast object of type 'Microsoft.Carmine.VMWareImplementation.VmwVMProcessorSetting' to type 'Microsoft.Carmine.VirtualizationAbstractionLayer.IVirProcessorSetting'.
   at Microsoft.VirtualManager.Engine.BitBos.VMRefresherBase.UpdateAdditionalVMInfo(IVMComputerSystem vmComputer, IVmmDbConnection dbConnection)
   at Microsoft.VirtualManager.Engine.BitBos.VMRefresherBase.UpdateFullVMObjectToCarmine(IVMComputerSystem vmComputer, VMData vmData, UpdateRequired updateRequired, Boolean vmObjectHasChanged, IVmmDbConnection dbConnection)
   at Microsoft.VirtualManager.Engine.BitBos.VMRefresherBase.RunOnDemandVmRefresh(Guid vmObjectId, VM tempVM, IVmmDbConnection dbConnection)
   at Microsoft.VirtualManager.Engine.BitBos.VMRefresherBase.UpdateHostAndVMs(VMRefresherType refresherType, Guid vmObjectId, VM tempVm, IVmmDbConnection dbConnection)
   at Microsoft.VirtualManager.Engine.VmOperations.RefreshVmSubtask.RunSubtask(IVmmDbConnection dbConnection)
   at Microsoft.VirtualManager.Engine.TaskRepository.SubtaskBase.Run(IVmmDbConnection dbConnection)
   at Microsoft.VirtualManager.DB.SqlContext.Connect(Action`1 action)
   at Microsoft.VirtualManager.Engine.TaskRepository.Task`1.SubtaskRun(Object state)

----------------------------------------------------
--------------- exception.StackTrace ---------------
----------------------------------------------------
at Microsoft.VirtualManager.Engine.BitBos.VMRefresherBase.UpdateAdditionalVMInfo(IVMComputerSystem vmComputer, IVmmDbConnection dbConnection)
   at Microsoft.VirtualManager.Engine.BitBos.VMRefresherBase.UpdateFullVMObjectToCarmine(IVMComputerSystem vmComputer, VMData vmData, UpdateRequired updateRequired, Boolean vmObjectHasChanged, IVmmDbConnection dbConnection)
   at Microsoft.VirtualManager.Engine.BitBos.VMRefresherBase.RunOnDemandVmRefresh(Guid vmObjectId, VM tempVM, IVmmDbConnection dbConnection)
   at Microsoft.VirtualManager.Engine.BitBos.VMRefresherBase.UpdateHostAndVMs(VMRefresherType refresherType, Guid vmObjectId, VM tempVm, IVmmDbConnection dbConnection)
   at Microsoft.VirtualManager.Engine.VmOperations.RefreshVmSubtask.RunSubtask(IVmmDbConnection dbConnection)
   at Microsoft.VirtualManager.Engine.TaskRepository.SubtaskBase.Run(IVmmDbConnection dbConnection)
   at Microsoft.VirtualManager.DB.SqlContext.Connect(Action`1 action)
   at Microsoft.VirtualManager.Engine.TaskRepository.Task`1.SubtaskRun(Object state)

----------------------------------------------------
------------- StackTrace from handler --------------
----------------------------------------------------
This is the call stack from where the exception was caught, not where it was thrown.
at Microsoft.VirtualManager.Utils.Diagnostics.WatsonReport.WriteReportTextFile(TextWriter reportFile)
   at Microsoft.VirtualManager.Utils.Diagnostics.WatsonReport.Send()
   at Microsoft.VirtualManager.Utils.Diagnostics.WatsonExceptionReport.Send()
   at Microsoft.VirtualManager.Utils.Diagnostics.WatsonCenter.ReportException(Exception e, WERReportOptions options, String& localReportPath)
   at Microsoft.VirtualManager.Engine.TaskRepository.Task`1.SubtaskRun(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()

----------------------------------------------------
-------------------- Assemblies --------------------
----------------------------------------------------
mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
    Location=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscorlib.dll
    Module=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscorlib.dll
    Version=4.7.2117.0
    BuildType=retail
    Product=Microsoft® .NET Framework

VMMService, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Location=C:\Program Files\Microsoft System Center 2016\Virtual Machine Manager\Bin\vmmservice.exe
    Module=C:\Program Files\Microsoft System Center 2016\Virtual Machine Manager\Bin\vmmservice.exe
    Version=4.0.2244.0
    BuildType=retail
    Product=System Center Virtual Machine Manager 2016

System.ServiceProcess, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
    Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceProcess\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.ServiceProcess.dll
    Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceProcess\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.ServiceProcess.dll
    Version=4.6.1586.0
    BuildType=retail
    Product=Microsoft® .NET Framework

System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
    Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System\v4.0_4.0.0.0__b77a5c561934e089\System.dll
    Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System\v4.0_4.0.0.0__b77a5c561934e089\System.dll
    Version=4.7.2110.0
    BuildType=retail
    Product=Microsoft® .NET Framework

TraceWrapper, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Location=C:\Program Files\Microsoft System Center 2016\Virtual Machine Manager\Bin\TraceWrapper.dll
    Module=C:\Program Files\Microsoft System Center 2016\Virtual Machine Manager\Bin\TraceWrapper.dll
    Version=4.0.1662.0
    BuildType=retail
    Product=System Center Virtual Machine Manager 2016

Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Location=C:\Program Files\Microsoft System Center 2016\Virtual Machine Manager\Bin\Utils.dll
    Module=C:\Program Files\Microsoft System Center 2016\Virtual Machine Manager\Bin\Utils.dll
    Version=4.0.2244.0
    BuildType=retail
    Product=System Center Virtual Machine Manager 2016

NativeMethods, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Location=C:\Program Files\Microsoft System Center 2016\Virtual Machine Manager\Bin\NativeMethods.dll
    Module=C:\Program Files\Microsoft System Center 2016\Virtual Machine Manager\Bin\NativeMethods.dll
    Version=4.0.2244.0
    BuildType=retail
    Product=System Center Virtual Machine Manager 2016

System.Core, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
    Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Core\v4.0_4.0.0.0__b77a5c561934e089\System.Core.dll
    Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Core\v4.0_4.0.0.0__b77a5c561934e089\System.Core.dll
    Version=4.7.2117.0
    BuildType=retail
    Product=Microsoft® .NET Framework

Engine.IndigoAccessLayer, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Location=C:\Program Files\Microsoft System Center 2016\Virtual Machine Manager\Bin\Engine.IndigoAccessLayer.dll
    Module=C:\Program Files\Microsoft System Center 2016\Virtual Machine Manager\Bin\Engine.IndigoAccessLayer.dll
    Version=4.0.2244.0
    BuildType=retail
    Product=System Center Virtual Machine Manager 2016

Engine.Common, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Location=C:\Program Files\Microsoft System Center 2016\Virtual Machine Manager\Bin\Engine.Common.dll
    Module=C:\Program Files\Microsoft System Center 2016\Virtual Machine Manager\Bin\Engine.Common.dll
    Version=4.0.2139.0
    BuildType=retail
    Product=System Center Virtual Machine Manager 2016

System.Configuration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
    Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Configuration\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Configuration.dll
    Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Configuration\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Configuration.dll
    Version=4.6.1586.0
    BuildType=retail
    Product=Microsoft® .NET Framework

System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
    Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Xml\v4.0_4.0.0.0__b77a5c561934e089\System.Xml.dll
    Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Xml\v4.0_4.0.0.0__b77a5c561934e089\System.Xml.dll
    Version=4.7.2612.0
    BuildType=retail
    Product=Microsoft® .NET Framework

Errors, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
    Location=C:\Program Files\Microsoft System Center 2016\Virtual Machine Manager\Bin\Errors.dll
    Module=C:\Program Files\Microsoft System Center 2016\Virtual Machine Manager\Bin\Errors.dll
    Version=4.0.2244.0
    BuildType=retail
    Product=System Center Virtual Machine Manager 2016

System.Data, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
    Location=C:\Windows\Microsoft.Net\assembly\GAC_64\System.Data\v4.0_4.0.0.0__b77a5c561934e089\System.Data.dll
    Module=C:\Windows\Microsoft.Net\assembly\GAC_64\System.Data\v4.0_4.0.0.0__b77a5c561934e089\System.Data.dll
    Version=4.7.2102.0
    Product=Microsoft® .NET Framework

System.Transactions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
    Location=C:\Windows\Microsoft.Net\assembly\GAC_64\System.Transactions\v4.0_4.0.0.0__b77a5c561934e089\System.Transactions.dll
    Module=C:\Windows\Microsoft.Net\assembly\GAC_64\System.Transactions\v4.0_4.0.0.0__b77a5c561934e089\System.Transactions.dll
    Version=4.6.1586.0
    Product=Microsoft® .NET Framework

System.EnterpriseServices, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
    Location=C:\Windows\Microsoft.Net\assembly\GAC_64\System.EnterpriseServices\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.EnterpriseServices.dll
    Module=C:\Windows\Microsoft.Net\assembly\GAC_64\System.EnterpriseServices\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.EnterpriseServices.dll
    Module=C:\Windows\Microsoft.Net\assembly\GAC_64\System.EnterpriseServices\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.EnterpriseServices.Wrapper.dll
    Version=4.6.1586.0
    BuildType=retail
    Product=Microsoft® .NET Framework

Microsoft.CSharp, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
    Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.CSharp\v4.0_4.0.0.0__b03f5f7f11d50a3a\Microsoft.CSharp.dll
    Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.CSharp\v4.0_4.0.0.0__b03f5f7f11d50a3a\Microsoft.CSharp.dll
    Version=4.6.1586.0
    BuildType=retail
    Product=Microsoft® .NET Framework

System.Dynamic, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
    Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Dynamic\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Dynamic.dll
    Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Dynamic\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Dynamic.dll
    Version=4.6.1586.0
    BuildType=retail
    Product=Microsoft® .NET Framework

----------------------------------------------------
--------- Extra Data for Watson Report -------------
----------------------------------------------------
Error Reporting Enabled=True

*** Extra Data ***
Process ID = 3852 (0x0f0c)
Managed Thread ID = 39
Native Thread ID = 6064 (0x17b0)
Monday, February 5, 2018 11:39 PM

All replies

0

Sign in to vote

Hi,

Since you are still running the RTM version of System Center Virtual Machine Manager 2016 I would suggest you to update to the latest RollUp.

Update Rollup 5 for System Center 2016 Virtual Machine Manager

Let me know how it goes!

Kind regards,
Leon
Blog: https://thesystemcenterblog.com LinkedIn:

Friday, May 18, 2018 3:36 PM
0

Sign in to vote

Even after UR5 on SCVMM 2016, this is still a problem with vSphere 6.5.

Thursday, August 9, 2018 1:58 PM
0

Sign in to vote

Having the same issue - connecting to servers running on VMWare 6.5. Some servers report correctly, but ones that have recent Windows Updates installed do not. Looks like there is a problem with a Windows Update?
Tim Starkenburg

Friday, August 31, 2018 3:29 PM
0

Sign in to vote

Hi,

The official documentation has not been updated since 04/26/2018 and currently according to the official documentation, ESX/ESXi 6.5 is not listed as supported for SCVMM 2016, although I do believe it is as I've heard many using it successfully.

See: https://docs.microsoft.com/en-us/system-center/vmm/system-requirements?view=sc-vmm-2016#vmware-servers-in-the-vmm-fabric

However SCVMM 1807 does indicate that it officially supports ESX/ESXi 6.5.

See: https://docs.microsoft.com/en-us/system-center/vmm/system-requirements?view=sc-vmm-1807#vmware-servers-in-the-vmm-fabric

Here's a guide also on how to add a vCenter 6.5 to SCVMM 2016:
http://www.cloudinspiration.com/add-vcenter-server-6-5-in-microsoft-scvmm-2016/

Best regards,
Leon
Blog: https://thesystemcenterblog.com LinkedIn:

Monday, September 3, 2018 6:48 AM
0

Sign in to vote

Hello,

I have the same or very similar issue,

I was addedd vcenter to vmm (vmm version 1807) and esx hosts.

esx hosts have been addedd and certificates imported.

First of all - how can I check which version do I have and which updates ?

Regarding VMM issues, some hosts have critical job during virtual machine refresh/host refresh job.

VMM error report:

https://1drv.ms/t/s!AqdJa_pamP_OgqJAxmNo3uOe52sidw?e=T0CK91

VMM Version:

https://1drv.ms/u/s!AqdJa_pamP_OgqJBgO16s5HBy3D4ZA?e=55yE4B

Regards

Thursday, May 30, 2019 11:01 AM

Products

Resources

Solutions

Updates

Trials

Related Sites

Training

Certifications

Other resources

Support options

More support

Not an IT pro?

Asked by:

VMM 2016 -- Error (20413) VMM encountered a critical exception and created an exception report at C:\ProgramData\VMMLogs\..

Question

All replies