'Method not registered' error when attempting to create session via REST API on HPC cluster hosted inside Azure RRS feed

  • Question

  • Hi,

    We have an HPC cluster installed within a Windows Azure virtual network (i.e. we have a domain controller VM, a VM for the head node, and VM/s for the compute node/s). HPC Pack 2008 R2 SP4 is the version installed and the VMs are all Windows 2008 R2 SP1, and the REST API has been installed and configured. The diagnostics from within cluster manager run successfully. A 'HelloWorld' SOA service has been deployed to the cluster.

    From an on-premises client, when trying to create a HPC session using the WebAPI transport scheme (code shown below), we are getting a (500) Internal Server Error when trying to create the session and the detailed HpcWebServiceFault error message is “The method with Uri https://theheadnode.cloudapp.net/WindowsHPC/theheadnode/sessions/Create?durable=False is not registered”.

    Logging has been turned on at a verbose level on the head node VM in Azure, but no errors or messages corresponding to the failed REST call seem to be logged in the HPC/event/SOA-service log files.

    Any ideas on how to troubleshoot this issue?




    The POST request made to the cluster from the on-premises client is included below, as well as the HPC Web Service Fault message that comes back in the response.

    var info = new SessionStartInfo("theheadnode.cloudapp.net", "HelloWorld");            
    info.TransportScheme = TransportScheme.WebAPI;
    info.Secure = true;
    info.Username = "hpcdemo\theadmin";
    info.Password = "Nottherealp@ssw0rd";
    using (Session session = Session.CreateSession(info))
    POST https:// theheadnode.cloudapp.net/WindowsHPC/TWHN3/sessions/Create?durable=False HTTP/1.1
    Content-Type: application/xml
    Accept: application/xml
    api-version: 2011-11-01
    Authorization: Basic aHBjZGVtb1xhZG1pbnNiOkRldmlzZSMhISE=
    Host: theheadnode.cloudapp.net


    <WebSessionStartInfo xmlns="http://hpc.microsoft.com/" xmlns:i="http://www.w3.org/2001/XMLSchema-instance"><AdminJobForHostInDiag>false</AdminJobForHostInDiag><AllocationGrowLoadRatioThreshold i:nil="true"/><AllocationShrinkLoadRatioThreshold i:nil="true"/><CanPreempt>true</CanPreempt><ClientConnectionTimeout i:nil="true"/><ClientIdleTimeout i:nil="true"/><DiagnosticBrokerNode i:nil="true"/><Environments xmlns:a="http://schemas.microsoft.com/2003/10/Serialization/Arrays"/><ExtendedPriority i:nil="true"/><JobTemplate i:nil="true"/><MaxMessageSize i:nil="true"/><MaxUnits>128</MaxUnits><MessagesThrottleStartThreshold i:nil="true"/><MessagesThrottleStopThreshold i:nil="true"/><MinUnits>1</MinUnits><NodeGroupsStr/><Password>Nottherealp@ssw0rd</Password><Priority i:nil="true"/><RequestedNodesStr/><ResourceUnitType>0</ResourceUnitType><Runtime>-1</Runtime><ServiceJobName i:nil="true"/><ServiceJobProject i:nil="true"/><ServiceName>HelloWorld</ServiceName><ServiceOperationTimeout i:nil="true"/><ServiceVersion i:nil="true" xmlns:a="http://schemas.datacontract.org/2004/07/System"/><SessionIdleTimeout i:nil="true"/><ShareSession>false</ShareSession><UseSessionPool>false</UseSessionPool><Username>hpcdemo\theadmin</Username></WebSessionStartInfo>

    HTTP/1.1 500 A generic error has occurred on the server.

    <HpcWebServiceFault xmlns="http://schemas.microsoft.com/HPCS2008R2/common" xmlns:i="http://www.w3.org/2001/XMLSchema-instance"><Code>267386880</Code><Message>The method with Uri https://theheadnode.cloudapp.net/WindowsHPC/theheadnode/sessions/Create?durable=False is not registered.</Message><Values i:nil="true" xmlns:a="http://schemas.datacontract.org/2004/07/System.Collections.Generic"/></HpcWebServiceFault>

    Sanjeev Bhutt

    Monday, July 15, 2013 7:29 PM

All replies

  • I am wondering if you ever got an answer on this problem.  I am seeing the exact same think on my cluster.  I posted a new question at http://social.microsoft.com/Forums/en-US/8afab1ec-6fe7-4983-9e6f-13f06d36575c/hpc-cluster-on-azure-vms-iaas-and-the-rest-api


    Thursday, September 26, 2013 8:33 PM
  • SOA REST API calls fail in IAAS (On-Premises) installs:

    The problem is that the SOA REST API is not available for "On-Premises" installs of the HPC stack.  It is only available in the (discontinued) Windows Azure HPC Scheduler (WAHS).  An IAAS install of the (full/normal) HPC sku is an "On-Premises" install.

    There is a confusing name clash between "Running the 'Scheduler' in Azure VMs" and "Windows Azure HPC Scheduler". 

    The Scheduler REST API is available in both install topologies... so the error that is returned is the Scheduler REST API seeing a request for a SOA URI.  Without the SOA REST listener installed, all SOA URIs will be unrecognized.

    SOA REST API is only available in WAHS (v3sp3 to v4rtm.  Discontinued in v4sp1).


    Wednesday, October 9, 2013 5:49 PM