In azure cloud service with Location West Europe, why the IP address shows the server is locate in United States?

We have 9 projects in azure cloud service, and all are use West Europe location, but with different subscription, and we found that one of those cloud service which its IP address is United
States(Why?) and others are all in Amsterdam(this is correct)
Can someone explain why? the server which it's ip located in United
States is very slow, BTW i'm in Amsterdam.

Hi LH,
I have saw the same problem on Brazil. There has some comments about this issue, you can refer to it:
Microsoft owns large ranges of IP addresses which are typically registered in Redmond, so usually Azure IP addresses around the world show up as being
physically located in Redmond when using these types of tools.
It's more or less an issue with the way our IP are registered. They all "belong" to Microsoft in the US and Brasil
IP locator tools like whatismyip are sometimes incorrect. Some will give the real location, some will give the location of the ISP, etc …
IP geo lookup tools typically rely on a static database of IP address range registrations.
It's a Microsoft issue in the sense that we may publish the correct location for our datacenters
(eg. Amsterdam should locate in Europe and not in Redmond…) – but it's also a 3rd party tools issue.
If you want to be sure – use
http://msdn.microsoft.com/en-us/library/windowsazure/dn175718.aspx 
 And you could also  see this blog about this issue :
http://azure.microsoft.com/blog/2014/06/11/windows-azures-use-of-non-us-ipv4-address-space-in-us-regions/
Regards,
Will
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Similar Messages

  • Windows Azure Cloud Service with MVC4WebRole template giving "Not running in a hosted service or the Development Fabric." Error.

    Azure SDK used - 1.7 & 2.0
    When we create new project for Windows Azure Cloud Service with MVC4WebRole template & try to run it locally its giving error as "Not running in a hosted service or the Development Fabric."
    We are aware that making Azure project as start up project will resolve this error but we want to run the application locally before testing it with cloud.
    It’s not working with Cassini so we have tried with IIS but still it’s giving the same error.
    In another project when we added ASP.Net MVC4 Application & then for that project we have generated the Azure cloud service project using "Add Windows Azure Cloud Service Project". By this way debugging it locally works fine.
    Is there something additional settings present in Windows Azure Cloud Service with MVC4WebRole template which is causing this issue?

    hello,
    According your description, I try to reproduce it in my PC.
    >1. I create a could project and add a MVC4 web role into project.
    >2. I set the azure project as a start project and run, it works fine.
    >3. I change the MVC4 web role as a startup project and run, it works fine too. Of course before this, I exited the Azure Simulator.
    But this project was a empty project. It didn't included azure DLL file, such as Diagnostics file. So I think you could comment out the "system.diagnostics" node and try again. Also, you could refer to this same thread:http://stackoverflow.com/questions/13879443/not-running-in-a-hosted-service-or-the-development-fabric-production-not-debug
    Regards,
    Will
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Allow desktop interaction within Azure Cloud Service with third-party desktop app (automated via code)

    Hello,
    I am developing a wrapper service as Worker Role which will take request from Service Bus and automate a third-party desktop app to produce an output file and then upload result back to our web server.  The automation is accomplished with the app's
    built-in .Net remoting based API.  This all works on my local development machine.  I am using code as below to start the desktop app.  In Azure:
    If I am not logged on to RDP and run the app as SYSTEM (or whatever the default WorkerRole account is), it waits forever for the MainWindowHandle.
    if I start the app manually in the RDP and try to get a reference to the running process (again as SYSTEM), I get Access Denied from WaitForInputIdle.
    if I start the app from code as the RDP user (ProcessStartInfo assign user/pass), I get InvalidOperationException - the app might not have a graphical interface from the WaitForInputIdle.
    Could anyone suggest the proper strategy for starting processes in a Worker Role that must create a window?
    For reference, I only care about the window to the extent that I need to make sure it's there.  All other interaction with the process is via the .Net Remoting API.
    private void GetOrStartThirdPartApp()
    _process = Process.GetProcessesByName("ThirdPartApp").FirstOrDefault();
    if (_process == null)
    _process = new Process();
    _process.StartInfo.Arguments = string.Format(@"-I ""{0}""", config.GetSetting("RolePath"));
    _process.StartInfo.WorkingDirectory = config.GetSetting("WorkingFolder");
    _process.StartInfo.FileName = config.GetSetting("ExecutablePath");
    _process.StartInfo.LoadUserProfile = true;
    _process.StartInfo.UseShellExecute = false;
    if (config.GetSettingAsBoolean("StartThirdPartAppWithRunAs", false))
    _process.StartInfo.UserName = "user";
    var password = new SecureString();
    foreach (var c in "thepassword".ToCharArray())
    password.AppendChar(c);
    _process.StartInfo.Password = password;
    _process.Start();
    while (_process.MainWindowHandle == IntPtr.Zero) Thread.Sleep(50);
    _process.WaitForInputIdle();
    _process.Exited += _process_Exited;

    I'd keep the app with the UI and the queue reader in the same process and account - not a worker role.  On start up you launch the desktop application and the queue reader in the same account, one after another.
    From what I've experienced, two users don't have the same
    Window Stations, so you can't pass a window handle in a different logged-in account across that boundary.  Read the Window Station documentation - you may find something that helps.
    You could use other techniques like sockets to communicate cross-process and cross-window station, too.
    Darin R.

  • Is there a way for converting WCF service into Azure Cloud Service without dealing with project files.

    Here is my situation.
    We provide Platform and SDK to other people where they can build WCF services and deploy that on site. We have a  many ISVs who has built wcf services, packaged them and ship them.
    Packaging consist of couple of manifest file and .dll file that make up wcf service. Now we want to go on cloud with our platform.
    Long story short - I have all the dlls for my wcf service but no project file.
    Is there a way to generate cloud service package from this dll files?

    Hi,
    You can't simply package your dlls and deploy it as a azure cloud service deployment package - you will need to have your project as well as service definition file which will define your role and instances.
    You can read more about packaging an Application by Using the CSPack Command-Line Tool here -http://msdn.microsoft.com/en-us/library/azure/gg433133.aspx
    another way to go to cloud platform is by making use of azure web sites, however you will still need your service files do deploy.
    If you have the dlls and the service files with you - then you can simply use the web site publish wizard and deploy to azure web site.
    Read more about it here - http://azure.microsoft.com/en-us/documentation/articles/web-sites-deploy/
    Bhushan | Blog |
    LinkedIn | Twitter

  • WCF Service hosted in Azure Cloud Service errors after published

    I have a project with several WCF services (mix of REST and SOAP).  The project has been running On-Prem for 6 months without an issue.  We are moving this to Azure but have run into an issue that will prevent us from going live.
    The project uses Autofac for it's IOC.  We are gonig to host this in a Cloud Service in Azure.  Everything appears to work correctly when running locally in the Azure Emulator however once we deploy using the Cloud Service project, everything builds
    and deploys correctly, but we receive the following error when trying to access a service.
    Server Error in '/' Application.
    Value cannot be null. Parameter name: key
    Description:
    An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the
    code. Exception Details: System.ArgumentNullException: Value cannot be null. Parameter name: key
    Source Error:
    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using
    the exception stack trace below.
    Stack Trace:
    [ArgumentNullException: Value cannot be null.
    Parameter name: key]
       System.ThrowHelper.ThrowArgumentNullException(ExceptionArgument argument) +48
       System.Collections.Generic.Dictionary`2.FindEntry(TKey key) +38
       System.Collections.Generic.Dictionary`2.TryGetValue(TKey key, TValue& value) +20
       System.ServiceModel.Dispatcher.WebHttpDispatchOperationSelector..ctor(ServiceEndpoint endpoint) +2459
       System.ServiceModel.Description.WebHttpBehavior.GetOperationSelector(ServiceEndpoint endpoint) +125
       System.ServiceModel.Description.WebHttpBehavior.ApplyDispatchBehavior(ServiceEndpoint endpoint, EndpointDispatcher endpointDispatcher) +1955
       System.ServiceModel.Description.DispatcherBuilder.InitializeServiceHost(ServiceDescription description, ServiceHostBase serviceHost) +4245
       System.ServiceModel.ServiceHostBase.InitializeRuntime() +119
       System.ServiceModel.ServiceHostBase.OnOpen(TimeSpan timeout) +45
       System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout) +553
       System.ServiceModel.HostingManager.ActivateService(ServiceActivationInfo serviceActivationInfo, EventTraceActivity eventTraceActivity) +350
       System.ServiceModel.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath, EventTraceActivity eventTraceActivity) +1614
    [ServiceActivationException: The service '/Event/Calendar' cannot be activated due to an exception during compilation.  The exception message is: Value cannot be null.
    Parameter name: key.]
       System.Runtime.AsyncResult.End(IAsyncResult result) +925
       System.ServiceModel.Activation.HostedHttpRequestAsyncResult.End(IAsyncResult result) +528
       System.ServiceModel.Activation.AspNetRouteServiceHttpHandler.EndProcessRequest(IAsyncResult result) +107
       System.Web.CallHandlerExecutionStep.OnAsyncHandlerCompletion(IAsyncResult ar) +151
    It appears that it's having an issue with the service configuration endpoint.  That is registered through Autofac WCF integration using the OOTB RouteTable here:
    RouteTable.Routes.Add(new ServiceRoute("Event/Calendar", new AutofacWebServiceHostFactory(), typeof(CalendarSvc)));
    All of this works fine in IIS and the local Azure emulator, but once deployed to the cloud service is where we get an issue.

    I don't know Autofac. What is it doing? If you use a normal WCF REST service, or ASP.NET Web API, do you see the same issue? If it does work, you may want to post a question on Autofac's forum:
    https://github.com/autofac/Autofac/issues.

  • Having trouble with creation of a cloud service with multiple virtual machines using java sdk.

    I am creating a cloud service on azure with 2 virtual machines using java sdk API. Service created successfully.
    My input endpoint details are as follows.
    INPUT ENDPOINTS
    Head : 191.238.144.47:2400
    Head : 191.238.144.47:22
    Node0 : 191.238.144.47:43211
    For Head instance port 2400 is for HTTPS and port 22 is for SSH and for Node0 instance port 43211 is for SSH.
    But I am having problem with doing a ssh on Head instance. Sometimes it works sometimes doesn't. Same problem with HTTPS also.
    I have some application running over there but when i try to access it thru browser sometimes it works but most of the time doesn't. When I restart the instances from azure portal, its works after
    that(not always but most of the time). 
    Now I am confused what is going on there. I am creating cloud service and virtual machines using java sdk and setting input endpoints also. After creation of all instances i restart every instance programmatically .
    I am not sure whether restart is required or not. It must be something to do with input endpoints only but not able to get the right thing i guess. When i do the same thing thru azure portal(creation of cloud service with virtual machines and setting up input
    end points) everything works fine but not achieving the result when implementing it by java sdk API. Please help me.

    HI Nithin,
    Thanks for your reply. I am setting the endpoints after creating my instances using update call. Here's the code snippet.
    AzureService aServ = new AzureService(session);
     if(aServ.checkNameAvailability(clusterName)) {
               aServ.createHostedService(clusterName, "dbX cluster");         
             // Creating head instance
             aServ.createHead(clusterName, imgName, headType, userName, pswd);  
            // Setting end points for head node
             String name = "ssh";
             int port = 22;
             aServ.updateVMInputEndpoint(clusterName, "Head", name, port);
             // Restarting head instance
             aServ.restartVM(clusterName, "Head");
           String roleName = "Node";
           String tmpRoleName = "";
           for(int i=0; i<noi; i++) {
                      port = 43210+(i+1);
                      tmpRoleName = roleName + i;
                   // Creating node instance
                    aServ.createVM(clusterName, tmpRoleName, imgName, nodeType, userName, pswd);
                  // Setting end points for node instance
                   aServ.updateVMInputEndpoint(clusterName, tmpRoleName, name, port);
                  // Restarting node instance
                 aServ.restartVM(clusterName, tmpRoleName);
          // Method to update the input endpoint details 
          public void updateVMInputEndpoint(String clusterName, String vmName, String name, int port)
            throws Exception {
                    VirtualMachineGetResponse resp = computeManagementClient.getVirtualMachinesOperations().
                                                            get(clusterName, clusterName, vmName);
                    VirtualMachineUpdateParameters updateParameters = new VirtualMachineUpdateParameters();
                    //get the configuration list
                    ArrayList<ConfigurationSet> configlist = resp.getConfigurationSets();
                    //get inputendpoint list and update it
                    ArrayList<InputEndpoint> endpointlist = configlist.get(0).getInputEndpoints();
                    InputEndpoint inputEndpoint = new InputEndpoint();
                    inputEndpoint.setEnableDirectServerReturn(false);
                    inputEndpoint.setPort(port);
                    inputEndpoint.setLocalPort(port);
                    inputEndpoint.setName(name);
                    inputEndpoint.setProtocol(InputEndpointTransportProtocol.TCP);
                    endpointlist.add(inputEndpoint);
                    // Open port for https on head node
                    if(vmName.equals("Head")) {
                            inputEndpoint = new InputEndpoint();
                            inputEndpoint.setEnableDirectServerReturn(false);
                            inputEndpoint.setPort(2400);
                            inputEndpoint.setLocalPort(2400);
                            inputEndpoint.setName("https");
                            inputEndpoint.setProtocol(InputEndpointTransportProtocol.TCP);
                            endpointlist.add(inputEndpoint);
                    updateParameters.setConfigurationSets(configlist);
                    //required for update
                    OSVirtualHardDisk osVirtualHardDisk = resp.getOSVirtualHardDisk();
                    updateParameters.setOSVirtualHardDisk(osVirtualHardDisk);
                    updateParameters.setRoleName(resp.getRoleName());
                    OperationResponse updtResp = computeManagementClient.getVirtualMachinesOperations().update(clusterName, clusterName, resp.getRoleName(), updateParameters);
    And every time i am creating a new cloud service along with head and node instances. Region is "South Central US".
    I am setting ProvisionGuestAgent field to true at instance creation time. Thank you.

  • "Failed to debug the Windows Azure Cloud Service project. The Output directory .... does not exist" - Looking for Solution Config Name Folder?

    Good evening,
    I've been working on and with a VS2013 Update 2 / Azure SDK 2.3 Cloud Service project for a while now and never had a problem debugging it (setting the .ccproj Project as Startup Project) but at the moment I cannot Debug it anymore - I always get the following
    error message:
    Failed to debug the Windows Azure Cloud Service project.  The output directory 'D:\Workspace\Development\Sources\AzureBackend\csx\Backend - Debug' does not exist.
    Now what's odd here, is the last part - the "Backend - Debug" is the Solution configuration name, ALL projects in that particular solution configuration are set to the Debug Configuration. The .ccproj file also only specifies Debug|Any CPU (and
    Release|Any CPU respectively) as its output folder(s). Why is the Solution config appearing up there?
    And more importantly.. why is this happening and what can I do?!
    Thanks,
    -Jörg
    Ps: there seems to be a related
    connect bug and these sorts of issues do appear around the forums but none contains a solution (neither reinstalling the Azure SDK nor cloaking the workspace/re-retrieving & building everything worked).

    Good morning Jambor,
    I already tried de-installing everything Azure-Tooling related including the Azure SDK, Restarting my machine and re-installing the SDK.
    Same result. I can build the .ccproj perfectly fine and the cspack file IS generated perfectly fine, only debugging does not work and there's NO information in the VS output window (again - all projects succeed to build).
    I tried explicitely running VS as Administrator, no change. I removed all IIS Express sites (as the ccproj has one web worker role), remapped my local TFS workspace.. nothing helped.
    As building works, deploying to Azure Cloud Service (manually and via Publish inside VS) all works -perfectly-, I am pretty sure this IS a bug and I'd LOVE to help to get this fixed. As I said, currently I cannot debug and/or run & test my work, hence
    I cannot do ANY work.

  • Is it possible to do Continuous deployment for azure cloud services(website,web and worker roles) using VSO Release management?

    Hi,
    I am trying to do continuous deployment using visual studio online and release management for Azure cloud services. But not able to find the way to do it(with the help of different blogs, those are describing using VM only).
    I tried using Release management visual studio extension also. But no Luck.
    Please help me if it is possible to do continuous deployment using release management.
    Thanks,
    Phani

    Hi,
     Please refer to the following Forum Thread with similar question which has been answered. Let us know if this helps.
     https://social.msdn.microsoft.com/Forums/en-US/9d8322f6-36e5-4cca-a982-d420d34d2072/realease-management-deployment-to-azure-websites-webworker-roles?forum=tfsbuild
    Regards,
    Nithin Rathnakar

  • Is there a list of best practices for Azure Cloud Services?

    Hi all;
    I was talking with a Sql Server expert today and learned that Azure Sql Server can take up to a minute to respond to a query that normally takes a fraction of a second. This is one of those things where it's really valuable to learn it when architecting as
    opposed to when we go live.
    Cloud Services are not Sql Server (obviously) but that led to the question - Is there a list of best practices for Azure Cloud Services? If so, what are they?
    We will be placing the cloud services in multiple datacenters and using traffic manager to point people to the right one. The cloud service will set between an IMAP client & server, pretending to be the mail client to the server, and the server to the client.
    Mostly it will pass all requests & responses across from one to the other.
    thanks - dave
    What we did for the last 6 months -
    Made the world's coolest reporting & docgen system even more amazing

    hi dave,
    >>Cloud Services are not Sql Server (obviously) but that led to the question - Is there a list of best practices for Azure Cloud Services? If so, what are they?
    For this issue, I have collected some blogs and document about best practices for azure cloud service, you can view them, but I am not sure they are your need.
    http://msdn.microsoft.com/en-us/library/azure/xx130451.aspx
    http://gauravmantri.com/2013/01/11/some-best-practices-for-building-windows-azure-cloud-applications/
    http://www.hanselman.com/blog/CloudPowerHowToScaleAzureWebsitesGloballyWithTrafficManager.aspx
    http://msdn.microsoft.com/en-us/library/azure/jj717232.aspxhttp://azure.microsoft.com/en-us/documentation/articles/best-practices-performance/
    >>The cloud service will set between an IMAP client & server, pretending to be the mail client to the server, and the server to the client. Mostly it will pass all requests & responses across from one to the other.
    For your scenarioes, If you'd like to communicate with each instances, I recommend you refer to this document (
    http://msdn.microsoft.com/en-us/library/azure/hh180158.aspx ). And generally, if we want connect the client to server on Azure, the service bus is a good choice (http://azure.microsoft.com/en-us/documentation/articles/cloud-services-dotnet-multi-tier-app-using-service-bus-queues/
    If I misunderstood, please let me know.
    Regards,
    Will
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • How to develop and deploy multiple worker roles in single azure cloud services?

    I am Manikandan, From Myeasydocs.com.
    We have developed our application as web projects.  Now we are going to move to azure cloud services, i have successfully migrated our application in cloud services and it worked fine. I am having difficulties with back ground task. i have nearly 12
    schedule tasks in our applications. I need assist on creating multiple worker role creation and deployment.
    Is there is any site on explaining the worker role process in details?
    Thanks in advance .. !!

    Hi,
    In Worker role, Applications hosted within worker roles can run asynchronous, long-running or perpetual tasks independent of user interaction or input. It is a service component that is useful for generalized development, and may perform background processing
    for a web role. A worker role is frequently used for long-running tasks that are non-interactive, but you can host any type of workload.
    I suggest you to follow the below article which explains about Creating and Deploying of Web Roles and Worker Roles in Azure Cloud Service using Visual Studio.
    https://msdn.microsoft.com/en-us/magazine/jj618299.aspx
    Hope this helps !
    Regards,
    Sowmya

  • Windows Azure Cloud Service Downtime alert

    Hi,
    One of the Cloud services that we have deployed on Windows Azure Cloud services using Azure Worker role is unexpectedly transitioning to Stopped state. There doesn't appear to be any valid reason behind this  and it runs normally after we switch to
    running state from portal. 
    Is it possible to develop some alert service which informs the Administrator or configured alert users that the Cloud service has shut down ? We tried to configure the Windows Azure alert but the metrics & logging doesn't seem to match with Cloud service
    downtime. Please let us know what is the diagnositics or logging option which we should make use to come up an optimal design for the Alert system.
    Thanks in advance,
    Deepesh
    Thanks & Regards, Deep

    Hi,
    From my experience, several operations in the Service Management API permit you to manage your cloud service either by referencing a deployment by its deployment name, or by referencing the deployment environment (staging or production) in
    which the deployment is running. Refer to
    http://msdn.microsoft.com/en-us/library/windowsazure/ee460812.aspx for more information about Operations on Cloud Services, we can do lots of things via this API, in “Get Cloud Service Properties” section, it has a “RoleInstanceList” property, refer to
    http://msdn.microsoft.com/en-us/library/windowsazure/ee460806.aspx#bk_roleinstancelist for more information about
     RoleInstanceList. In this article it has PersistentVMDowntime property, the detail information as following.
    PersistentVMDowntime
    Specifies information about when the Virtual Machine has been started and stopped.
    The PersistentVMDowntime element is only available using version 2012-03-01 or higher.
    Hope this helps, if this didn’t give you help, please feel free to let me know.
    Best Regards
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • What are the differences between Azure(Cloud) Service Bus and On-Premises Service Bus (Windows Service Bus 1.0)?

    Hi,
    I want to know the exacts differences between Windows Azure(Cloud) Service Bus and On-Premises Service Bus (Windows Service Bus 1.0)
    Thanks
    mit

    Might ask them over here.
    http://social.technet.microsoft.com/Forums/en-us/home?category=biztalkserver
    http://social.msdn.microsoft.com/Forums/windowsazure/en-US/home?forum=windowsazuremanagement%2Cservbus%2Cazuremobile&filter=alltypes&sort=lastpostdesc
    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]
    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

  • Azure Cloud Services

    Hello i think Microsoft Azure Cloud Services is going to help many companies to manage more eficiently their business, but i dont like your PAY-AS-YOU-GO Subscritions i think you should provide certain basic services with commercial ads, and more advanced
    with a price.

    Filinto.  Thanks for your feedback here.
    I understand what you're asking for.  Let me check if you are aware of some of the other ways to pay for or consume Azure Services. 
    First of there are the 30 day free trials http://azure.microsoft.com/en-us/pricing/free-trial/
    second MSDN is another way to pay for and consume Azure services.
    We don't have any plans to have an advertisement-funded model for Azure SQL Database.
    Thanks Guy

  • Visual Studio cannot remote debug Azure cloud service: There was a failure to launch the remote debugger

    I am trying to invoke remote debugger on an Azure worker role cloud service, following the example of
    http://msdn.microsoft.com/en-us/library/azure/ff683670.aspx
    But on attaching the remote debugger for the cloud service instance
    Microsoft Visual Studio
    There was a failure to launch the remote debugger.
    OK  
    According to somebody else's extra coverage on the topic, there are extra ports 4016/4017 that need to be taken care of (but do they have to be exposed externally)?
    http://developers.de/blogs/damir_dobric/archive/2014/02/04/behind-windows-azure-remote-debugger.aspx
    So servicedefinition.csdef gets
        <Endpoints>
          <InputEndpoint name="Endpoint1" protocol="http" port="80" />
          <InputEndpoint name="RemoteDebugger" protocol="tcp" port="4016" localPort="4016" />
          <InputEndpoint name="RemoteDebugger2" protocol="tcp" port="4017" localPort="4017" />
          <InstanceInputEndpoint name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.Connector" protocol="tcp" localPort="30398">
            <AllocatePublicPortFrom>
              <FixedPortRange min="30400" max="30424" />
            </AllocatePublicPortFrom>
          </InstanceInputEndpoint>
          <InstanceInputEndpoint name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.Forwarder" protocol="tcp" localPort="31398">
            <AllocatePublicPortFrom>
              <FixedPortRange min="31400" max="31424" />
            </AllocatePublicPortFrom>
          </InstanceInputEndpoint>
        </Endpoints>
    Serviceconfiguration.cscfg gets
          <Setting name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.Connector.Enabled" value="true" />
          <Setting name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.Connector.Version" value="2.3" />
          <Setting name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.ClientThumbprint" value="THUMBNAIL" />
          <Setting name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.ServerThumbprint" value="THUMBNAIL" />
        </ConfigurationSettings>
        <Certificates>
          <Certificate name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.TransportValidation" thumbprint="THUMBNAIL" thumbprintAlgorithm="sha1"
    />
        </Certificates>
    But all these are to no avail; the same error still pops for Visual Studio 2013 Update 4; Azure SDK 2.3
    Anybody regularly perform remote debugging for Azure cloud services?
    The melody of logic will always play out the truth. ~ Narumi Ayumu, Spiral

    And, how do I control that in Visual Studio?
    All I get is the Attach Debugger... context menu option in the Azure cloud service nodes in Server Explorer. That is where it is failing. There are no customisable options.
    Because of that, the Attach to Process dialog box is unable to retrieve the list of processes (to debug) in the remote worker role instance server.
    I tested a blank-template worker role project and published to a new cloud project, and this simplistic copy had no problems with the Remote debugger.
    Now the question is, what is it about this real-world project/cloud service that is different from blank sample? From what I compare between what I think are the relevant settings, there are none.
    ServiceDefinition.csdef
    <Imports>
    <Import moduleName="Diagnostics" />
    <Import moduleName="RemoteAccess" />
    <Import moduleName="RemoteForwarder" />
    <Import moduleName="RemoteDebuggerConnector" />
    </Imports>
    <Contents>
    <Content destination=".\">
    <SourceDirectory path="D:\Projects\experiments\workerrole1\workerrole1\rcf\Debug\RemoteDebuggerContent\" />
    </Content>
    </Contents>
    <Endpoints>
    <InstanceInputEndpoint name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.Connector" protocol="tcp" localPort="30398">
    <AllocatePublicPortFrom>
    <FixedPortRange min="30400" max="30424" />
    </AllocatePublicPortFrom>
    </InstanceInputEndpoint>
    <InstanceInputEndpoint name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.Forwarder" protocol="tcp" localPort="31398">
    <AllocatePublicPortFrom>
    <FixedPortRange min="31400" max="31424" />
    </AllocatePublicPortFrom>
    </InstanceInputEndpoint>
    </Endpoints>
    ServiceConfiguration.cscfg
    <ConfigurationSettings>
    <Setting name="Microsoft.WindowsAzure.Plugins.Diagnostics.ConnectionString" value="DefaultEndpointsProtocol=https;AccountName=storage;AccountKey=" />
    <Setting name="Microsoft.WindowsAzure.Plugins.RemoteAccess.Enabled" value="true" />
    <Setting name="Microsoft.WindowsAzure.Plugins.RemoteAccess.AccountUsername" value="" />
    <Setting name="Microsoft.WindowsAzure.Plugins.RemoteAccess.AccountEncryptedPassword" value="" />
    <Setting name="Microsoft.WindowsAzure.Plugins.RemoteAccess.AccountExpiration" value="2015-12-31T23:59:59.0000000+08:00" />
    <Setting name="Microsoft.WindowsAzure.Plugins.RemoteForwarder.Enabled" value="true" />
    <Setting name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.Connector.Enabled" value="true" />
    <Setting name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.Connector.Version" value="2.4" />
    <Setting name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.ClientThumbprint" value="" />
    <Setting name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.ServerThumbprint" value="" />
    </ConfigurationSettings>
    <Certificates>
    <Certificate name="Microsoft.WindowsAzure.Plugins.RemoteAccess.PasswordEncryption" thumbprint="" thumbprintAlgorithm="sha1" />
    <Certificate name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.TransportValidation" thumbprint="" thumbprintAlgorithm="sha1" />
    </Certificates>
    The melody of logic will always play out the truth. ~ Narumi Ayumu, Spiral

  • Windows Azure cloud service stuck / hangs on deploying

    Today I tried to upload a package to the Windows Azure staging cloud service enviroment. The service hangs on deploying.
    I can not delete or update this. I get this error 
    The staging deployment could not be updated for cloud service .......
    Completed Uploading the package to the staging environment...
    Completed Successfully uploaded the package to the staging environment.
    Error The staging environment could not be updated.
    Windows Azure is currently performing an operation with x-ms-requestid 13d49febc06f60b4bc36f3330274f68d on this deployment that requires exclusive access.
    Do anyone knows how to fix this?

    Yes, You may need wait  some minutes,EG. http://social.msdn.microsoft.com/Forums/windowsazure/en-US/eb76c4c1-dcd0-427b-adfd-da6dd373beb8/azure-deployment-stuck-in-updating-state?forum=windowsazuretroubleshooting
    Regards,
    -billgiee

Maybe you are looking for