Unable to allocate required address spaces

Question

When I deploy a new web role to Windows Azure, I get this error: Failed to allocate the necessary address spaces for deployment on a new or predefined subnet that is contained in the specified virtual network. I searched for a solution but did not find it. Does anyone have any ideas?

My cscfg file looks like this:

<?xml version="1.0" encoding="utf-8"?> <ServiceConfiguration serviceName="Application.Cloud" xmlns="http://schemas.microsoft.com/ServiceHosting/2008/10/ServiceConfiguration" osFamily="3" osVersion="*" schemaVersion="2013-03.2.0"> <Role name="WebApplication" vmName="vm001"> <Instances count="1" /> <ConfigurationSettings> ... </ConfigurationSettings> <Certificates> <Certificate name="Microsoft.WindowsAzure.Plugins.RemoteAccess.PasswordEncryption" thumbprint="..." thumbprintAlgorithm="sha1" /> </Certificates> </Role> <Role name="Application.ServiceOpdrachten" vmName="vm002"> <Instances count="1" /> <ConfigurationSettings> ... </ConfigurationSettings> <Certificates> <Certificate name="Microsoft.WindowsAzure.Plugins.RemoteAccess.PasswordEncryption" thumbprint=".." thumbprintAlgorithm="sha1" /> </Certificates> </Role> <NetworkConfiguration> <VirtualNetworkSite name="VirtualNetwork" /> <!-- The virtual network name must match the name of the vvirtual network configured in your subscription. --> <AddressAssignments> <!-- You must map each role in your cloud service to a subnet or a collection of subnets which were defined in your network.--> <InstanceAddress roleName="WebApplication"> <Subnets> <Subnet name="Subnet-1" /> </Subnets> </InstanceAddress> </AddressAssignments> </NetworkConfiguration> </ServiceConfiguration> 

In the same cloud project, I have another instance that deploys perfectly.

 <?xml version="1.0" encoding="utf-8"?> <ServiceConfiguration serviceName="Ecare.Acasa.Cloud" xmlns="http://schemas.microsoft.com/ServiceHosting/2008/10/ServiceConfiguration" osFamily="3" osVersion="*" schemaVersion="2013-03.2.0"> <Role name="WebApplication"> <Instances count="1" /> <ConfigurationSettings> ... </ConfigurationSettings> <Certificates> <Certificate name="Microsoft.WindowsAzure.Plugins.RemoteAccess.PasswordEncryption" thumbprint="..." thumbprintAlgorithm="sha1" /> </Certificates> </Role> <Role name="Ecare.Acasa.ServiceOpdrachten"> <Instances count="1" /> <ConfigurationSettings> ... </ConfigurationSettings> <Certificates> <Certificate name="Microsoft.WindowsAzure.Plugins.RemoteAccess.PasswordEncryption" thumbprint="..." thumbprintAlgorithm="sha1" /> </Certificates> </Role> <NetworkConfiguration> <VirtualNetworkSite name="Ecare" /> <!-- The virtual network name must match the name of the vvirtual network configured in your subscription. --> <AddressAssignments> <!-- You must map each role in your cloud service to a subnet or a collection of subnets which were defined in your network.--> <InstanceAddress roleName="WebApplication"> <Subnets> <Subnet name="Subnet-1" /> </Subnets> </InstanceAddress> </AddressAssignments> </NetworkConfiguration> </ServiceConfiguration> 

Answer 1

We had the same problem about three months ago. Then maybe after some updating, new IP addresses were not assigned or when the role or vm were deleted, their IP address was not reused.

We could not get help from Microsoft Support, as it was in Preview.

What worked for us: We deleted the entire virtual network and created it again.

If this is possible for you, see if it works.

Answer 2

I ran into this problem and found that the problem could be fixed. Here is described here .