visual-studioazureazure-cloud-services

Azure "No deployments were found" error message


I went to deploy over an existing Cloud Service (in staging) and received the following message:

"Error: No deployments were found. Http Status Code: NotFound"

Does anyone know what this means?

I am looking at the Cloud Service, and it surely exists.

UPDATE:
Been using the same deploy method as prior (successful) efforts. However, I simply right click the cloud service in Visual Studio 2013. In the Windows Azure Publish Summary, I set to: the correct cloud service name, to staging, to realease ... and press publish. Nothing special really...which is why I am perplexed


Solution

  • Since I had this problem and none of the answers above were the cause... I had to dig a little bit more. The RoleName specified in the Role tag must of course match the one in the EndpointAcl tag.

    <Role name="TheRoleName">
        <Instances count="1" />
    </Role>
    <NetworkConfiguration>
        <AccessControls>
          <AccessControl name="ac-name-1">
            <Rule action="deny" description="TheWorld" order="100" remoteSubnet="0.0.0.0/32" />
          </AccessControl>
        </AccessControls>
        <EndpointAcls>
          <EndpointAcl role="TheRoleName" endPoint="HTTP" accessControl="ac-name-1" />
          <EndpointAcl role="TheRoleName" endPoint="HTTPS" accessControl="ac-name-1" />
        </EndpointAcls>
    </NetworkConfiguration>
    

    UPDATE

    It seems that the previous situation is not the only one causing this error. I ran into it again now due to a related but still different mismatch.

    In the file ServiceDefinition.csdef the <WebRole name="TheRoleName" vmsize="Standard_D1"> tag must have a vmsize that exists (of course!) but according to Microsoft here (https://azure.microsoft.com/en-us/documentation/articles/cloud-services-sizes-specs/) the value Standard_D1_v2 should also be accepted.

    At the moment it was causing this same error... once I removed the _v2 it worked fine.

    Conclusion: everytime something is wrong in the Azure cfgs this error message might come along... it is then necessary to find out where it came from.