"Failed to create virtual machine" error message when you try to create a new virtual machine in Windows Azure Pack with Update 2

Gilt für: Windows Azure Pack (on Windows Server 2012 R2)Microsoft System Center 2012 R2 Virtual Machine Manager

Symptoms


When you try to create a new virtual machine in Windows Azure Pack after you apply Microsoft System Center 2012 R2 Virtual Machine Manager (VMM) Rollup Update 2 to your VMM server, you may receive an error that resembles the following in the tenant portal:

Failed to create virtual machine 'vmname'.
Failed to submit operation request.

Note In this message, the placeholder 'vmname' represents the name of the virtual machine that you are trying to create.

The error details are displayed as an error that resembles the following:

Error:JsonException: An error occurred while processing this request.

<Exception>
  <Type>JsonException</Type>
  <Message>An error occurred while processing this request.</Message>
  <StackTrace><![CDATA[
]]></StackTrace>
  <HttpContext>
    <User IsAuthenticated="true" Name="test@contoso.local" />
    <Request>
      <RawUrl>/VM/QuickCreateVMInstance</RawUrl>
  <UserHostAddress>10.0.0.1</UserHostAddress>
      <Headers>
        <Header Key="Cache-Control" Value="no-cache" />
        <Header Key="Connection" Value="Keep-Alive" />
        <Header Key="Content-Length" Value="275" />
        <Header Key="Content-Type" Value="application/json" />
        <Header Key="Accept" Value="application/json, text/javascript, */*; q=0.01" />
        <Header Key="Accept-Encoding" Value="gzip, deflate" />
        <Header Key="Accept-Language" Value="en-US" />
        <Header Key="Host" Value="server.contoso.local:30081" />
        <Header Key="Referer" Value="https://aiwwv1518.bellprod.local:30081/#Workspaces/VMExtension/ComputeResources" />
        <Header Key="User-Agent" Value="Mozilla/5.0 (Windows NT 6.3; WOW64; Trident/7.0; ) like Gecko" />
        <Header Key="x-ms-client-session-id" Value="b6917835-48c3-4552-b061-81ee449428a6" />
  <Header Key="x-ms-client-antiforgery-id" Value="3sXUyXPYBxIS9tbxqLY3JpHwZ/PnIrHlFNDp19Vcr2HVv2wDoMQoqVxzJ3qVR7a6BUXs/deCKzAx3xMIrGq11LKsE8JPb8A7qeEkfichmrpANCYD/SXYJOBZR3sKJSw2rTS0N2aJaIQUo962d5FNtw==" />
  <Header Key="x-ms-client-request-id" Value="6ba38252-cc41-4c3e-87a9-d89cx11abc11-2014-07-04 11:25:09Z" />
        <Header Key="X-Requested-With" Value="XMLHttpRequest" />
        <Cookies>
          <Cookie Name="sub" Secure="false" Expires="0001-01-01T00:00:00Z" Domain="" Path="/" Value="Redacted (4 characters)" />
          <Cookie Name="__RequestVerificationToken_MemebershipAuthentication" Secure="false" Expires="0001-01-01T00:00:00Z" Domain="" Path="/" Value="Redacted (128 characters)" />
          <Cookie Name="MembershipSiteFedAuth" Secure="false" Expires="0001-01-01T00:00:00Z" Domain="" Path="/" Value="Redacted (1688 characters)" />
          <Cookie Name="__RequestVerificationToken_Tenant" Secure="false" Expires="0001-01-01T00:00:00Z" Domain="" Path="/" Value="Redacted (128 characters)" />
          <Cookie Name="TenantSiteFedAuth" Secure="false" Expires="0001-01-01T00:00:00Z" Domain="" Path="/" Value="Redacted (1372 characters)" />
          <Cookie Name="__aux" Secure="false" Expires="0001-01-01T00:00:00Z" Domain="" Path="/" Value="Redacted (152 characters)" />
        </Cookies>
      </Headers>
    </Request>
  </HttpContext>
</Exception>, operationName:VM.QuickCreateVMInstance, version:, accept language:en-US, subscription Id:80c852e9-57af-4025-8eac-d4a8b480bb20, client request Id:6ba38252-cc41-4c3e-87a9-d89c5011abc3-2014-07-04 11:25:09Z, principal Id:test@contoso.local, page request Id:b6917835-48c3-4552-b061-81ee449428a6, server request id:

Additionally, you may receive an error that resembles the following in the Event Viewer\Applications and Service Logs\Microsoft Windows \ManagementODataService\Operations event log:

Log Name:   Microsoft-Windows-ManagementOdataService/Operational channel
EventID: 20006
Level: Error
Description:

Web Service has got a callback from OData framework about an error. 
Exception message = An error occurred while processing this request.
Inner exception message = The property 'DynamicMemoryMinimumMB' does not exist on type 'VMM.VirtualMachine'. Make sure to only use property names that are defined by the type.
Response status code = 400
Response content type = application/xml;charset=utf-8
Response written = false
Use verbose error = true

Cause


This issue may occur if the following conditions are true:
  • Windows Azure Pack was updated to Update 2. 
  • System Center Virtual Machine Manager was not updated to Update Rollup 2.  
Dynamic Memory support for virtual machines in Windows Azure Pack is introduced in Update Rollup 2 for System Center 2012 R2 Virtual Machine Manager.

Resolution


To resolve this error, apply Update Rollup 2 to System Center 2012 R2 Virtual Machine Manager. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2932926  Description of Update Rollup 2 for System Center 2012 R2 Virtual Machine Manager  

Important For Windows Azure Pack to work correctly after you apply this update rollup, you must run the SQL script that is provided the article that is mentioned here.