none
Service Management Automation Bug RRS feed

  • Question

  • We are creating virtual machine via azure pack API. Virtual machine is defined by our custom VM Role template.

    After POST request get's response we are calling service management automation API, and we get this error at random ( 1 of a 10 cases ) :

    
    Exception     The
     invocation of the constructor on type 
    'Microsoft.PowerShell.DynamicActivities.Activity_324674801_Nested' that 
    matches the specified binding constraints threw an exception. (Cannot 
    set unknown member 
    '{clr-namespace:Microsoft.VisualBasic.Activities;assembly=System.Activities}VisualBasic.Settings'.)

    Our api call looks like this :

    Request Type : POST

    BODY

    ############################################

               {
                "parameters": [{"__metadata": {"type": "Orchestrator.ResourceModel.NameValuePair"},
                                "Name": "vmName",
                                "Value": vmName
                                },
                               {"__metadata": {"type": "Orchestrator.ResourceModel.NameValuePair"},
                                "Name": "vmmJobID",
                                "Value": jobId
                                },
                               {"__metadata": {"type": "Orchestrator.ResourceModel.NameValuePair"},
                                "Name": "vmTag",
                                "Value": vmTag
                                },
                               {"__metadata": {"type": "Orchestrator.ResourceModel.NameValuePair"},
                                "Name": "vlanID",
                                "Value": vlanID
                                }]
            }

    Where values in this body are parameters which are different every call.

    ############################################


    HEADER

    ############################################

     {'Accept': 'application/atom+xml,application/xml','Content-Type': 'application/json;odata=verbose'}

    ############################################

    URI :

    ############################################

    https://uri:9090/00000000-0000-0000-0000-000000000000/Runbooks(guid'GUID')/Start

    Where uri, and GUID are values for our env.

    ############################################

    Our SPF, and SMA service are on the same server which are balanced by NLB with 4GB's of RAM and 2vCPU (we do not have much load on this servers, we are in testing faze.. )

    Azure Pack API's and portal are on the same server with 4GB's of RAM and 2vCPU

    Thursday, November 22, 2018 4:21 PM

All replies

  • to continue with this issue, please open a support request. If you do not have a support plan, please Email me at AzCommunity@microsoft.com with your SubscriptionID and a link to this post, and I will create a one-time free support request for you to continue troubleshooting this issue. 
    Tuesday, December 4, 2018 11:33 PM
  • Hi

    I also had this error today with a scheduled SMA runbook.
    Did you find the cause or a solution for this?


    • Edited by smeury Wednesday, February 20, 2019 5:59 AM
    Wednesday, February 20, 2019 5:59 AM
  • Hi,

    Thank you for answering,

    Since this was going on too long and we need to fix it so we can continue with our projects, we removed sma auto triggering by spf, and now we are using sma api calls to activate sma runbooks. Works much nicer, and requests are way lighter, and faster.

    Thursday, March 14, 2019 7:55 PM