Debug cloud service in emulator

Hi:
I have an Azure web site that calls a cloud service. The cloud service places a request on an Azure storage-based queue. Then a web role retrieves the request from the queue, and does its work. This all works great when deployed to Azure,
but I want to debug everything locally in the emulator. The problem I am having is that I can't figure out how to make the local service run in the emulator. In the .svc.cs file, with the following line of code:
CloudStorageAccount sa = CloudStorageAccount.Parse(
RoleEnvironment.GetConfigurationSettingValue( "DataConnectionString" ) );
theGetConfigurationSettingValue() call returns a 'System.Runtime.InteropServices.SEHException' exception. If I include a RoleEnvironment.IsAvailable call, it returns false regardless of what I set as the service as the startup project.
So the service is running, and my web role can call it, but evidently the service is not running in the emulator. How can I fix this?
Thanks in advance,
Terry
TerryL

Dear Terry,
The error 'System.Runtime.InteropServices.SEHException' means you attempted to access the RoleEnvironment without running in the dev fabric or Azure fabric. In general, this may because
you didn't set cloud project as a startup project, just as VIJAYAMANIKANDAN said. Your application was running in the emulator but didn’t work, this was very strange, and thus it is hard for us to reproduce this issue.
By the way, thank you for sharing another method to us, I will mark the above post as the answer.
If you have any other issues, please feel free to ask.
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.

Similar Messages

Can't Debug Cloud Service w/Visual Studio

I have used the instructions on the following link to no avail. Trying to debug a web application.
http://msdn.microsoft.com/en-us/library/ff683670.aspx#BK_Debugging_Cloud_Azure
I am using SDK version 2.3 with Visual Studio 2013 Ultimate.
Yes, remote debugging is turned on.
Yes, project is compiled in Debug mode.
When I attach debugger the default process that comes up selected is "clouddrivesvc.exe". When I attach the process is debugging in Native mode. So I'm guessing this is not the right process to attach to. Based on the screen shots
in the aforementioned link I have tried attaching to "WallSHost.exe", this doesn't work either though. I'm assuming I must be attaching to the wrong process. Instructions state that the correct process should be selected by default...?

Hi,
The debugger automatically attaches to the appropriate host process for your role. Depending on what the role is, the debugger attaches to w3wp.exe, WaWorkerHost.exe, or WaIISHost.exe. To verify the process to which the debugger is attached, expand the instance
node in Server Explorer.
Best Regards
Jambor
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.

'role discovery data is unavailable' cloud service (staging)

This has been posted on stackoverflow, so apologies for the cross post, but I'm trying to gain traction on fixing this and losing time.
I currently have a production cloud service working. I moved a project dependency from being a direct dll reference to local nuget package and after some re-factoring, decided to deploy my efforts to the staging site.
Locally, the changes with the dependency appears to be working correctly; the site loads and works well using the azure compute emulator.
However, when I deploy to the staging environment (via visual studio publish to azure option) the deployment fails as it detects multiple cycles of the instance which points to a spin up issue. When I've jumped on the box to try and find the route cause, I
can see the dreaded role discovery data is unavailable exception.
My gut hunch is nuget has updated a package which caused this but can't see what and why it would work locally but not in the cloud. I thought it might be the azure caching but it looks as though I'm using the same version as the live (working) site.
- Does anyone have a fix for this?
- If this works locally (cuts out many answers I've seen when you see this using the emulator), what am I missing or including to prevent this working in the cloud?
- Is there a way I can debug this further to find out why I'm getting the exception
Many, many thanks in advance to anyone who spares any time reading this

Hi Sir,
Base on my experience, if we implement the references using NuGet, we could see those DLL files from "References". I recommend you could set those DLL files "Copy Local" to "true". And try to deploy project
again. And I wondered know what error details when you deployed project. The link below is about how to remote debug cloud service, please try it.
http://msdn.microsoft.com/en-us/library/azure/ff683670.aspx
Sample:
http://code.msdn.microsoft.com/windowsazure/Remote-Debugging-Windows-dedaaec9
For this error information, you could see the similar thread:http://stackoverflow.com/questions/11547855/azure-role-discovery-data-is-unavailable-error-when-switching-from-iisexpress
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.

"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.

Cloud service created works fine in local Azure Emulator. But doesnot work when deployed to actual azure and says Restarting (Role has encountered an error and has stopped. Unhandled Exception: System.IO.FileNotFoundException)

Hi,
I have a created a cloud service and when i run locally in azure emulator it works fine. But when I am trying to deploy that to azure it says: Restarting (Role has encountered an error and has stopped.
Unhandled Exception: System.IO.FileNotFoundException)
Can anyone please help me on this.
Thanks,
Satya Chenna

Any specific reason you are having timer on role start up? are you using thread.sleep for longer duration in the method?
If you are using azure diagnostics - make sure these things
1. Azure storage connection string is set to correct storage account and not to the development storage.
2. Check session state provider - local is not supported on azure.
Also you can refer this for more information
http://blogs.msdn.com/b/kwill/archive/2013/09/06/troubleshooting-scenario-3-role-stuck-in-busy.aspx
Bhushan | Blog |
LinkedIn | Twitter

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

How do I configure Azure to let my cloud service make an outbound API call

My cloud service works locally when I debug it, but when I deploy it, I know it has database access because database updates are taking place.
It seems like the service is not able to call make calls to the Yammer API on port 443 for SSL (is that right?)
https://www.yammer.com/api/v1/messages.xml?older_than=[MinMessageID]
That is one example, but all the calls start with everything up to
https://www.yammer.com/api/v1
Is there a firewall setting I need to create so that my cloud service can make outbound calls?
Thank you for any help.

Hi,
I am glad to hear that you have solved your issue. If you have any difficulty in future programming, we welcome you to post in forums again.
Thanks for your posting.
Best Regards,
Jambor
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.

Change basicHttpBinding to wsHttpBinding in azure cloud service web role

So I created a cloud service project in visual studio and added wcf service web role to cloud service.
By default wcf service web role binding is set to basicHttpBinding.
Currently my web.config looks like this:
<?xml version="1.0"?>
<configuration>
<system.diagnostics>
<trace>
<listeners>
<add type="Microsoft.WindowsAzure.Diagnostics.DiagnosticMonitorTraceListener, Microsoft.WindowsAzure.Diagnostics, Version=2.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
name="AzureDiagnostics">
<filter type="" />
</add>
</listeners>
</trace>
</system.diagnostics>
<system.web>
<compilation debug="true" targetFramework="4.0" />
</system.web>
<system.serviceModel>
<behaviors>
<serviceBehaviors>
<behavior>

<serviceMetadata httpGetEnabled="true"/>

<serviceDebug includeExceptionDetailInFaults="false"/>
</behavior>
</serviceBehaviors>
</behaviors>
<serviceHostingEnvironment multipleSiteBindingsEnabled="true" />
</system.serviceModel>
<system.webServer>
<modules runAllManagedModulesForAllRequests="true"/>
<directoryBrowse enabled="true"/>
</system.webServer>
</configuration>
How do I change my config to use wsHttpBinding?

Hi,
Please refer to
http://msdn.microsoft.com/en-us/library/ms733099.aspx. From my experience, in Windows Azure, we cannot use Windows authentication (the default configuration for WSHttpBinding), unless we use WAAD and let the cloud server join the local domian. So it is
needed to turn off authentication, or use an alternative authentication mechanism (such as username and password).
Best Regards,
Ming Xu
<THE CONTENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, WHETHER EXPRESS OR IMPLIED>
Thanks
MSDN Community Support
Please remember to "Mark as Answer" the responses that resolved your issue. It is a common way to recognize those who have helped you, and makes it easier for other visitors to find the resolution later.

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.

Cloud Service has suddenly started calling itself repeatedly.

I have a cloud service. I have an OperationContract method, the first line of which logs "START" to a database.
The method is called from a web page (however after discovering the problem, I am now calling from a Unit Test method. The web site logs only showed that it was calling the cloud service once anyway).
The cloud service creates two appointment records in Dynamics CRM. Recently we found that the service calendar was filing up.
Looking at the SQL log I mentioned earlier, it appears that the OperationContract method is being called over and over again until an error is hit (calendar full or NULL exception) at which time the issue stops. The method can be called 2 or 3 times
a second.
START is showing in the log over and over again as if the method is being called over and over again. I have checked that I am not calling myself in a loop from inside the cloud service.
It does FEEL like the web site is calling the method over and over but it is NOT. IIS logs and Unit Test call show this.
How can this method be running over and over again?
My thought was perhaps the service was crashing and restarting and thus restarting a job that it has already done. I don't understand this mechanism nor how to stop it if it exists.
Does this behaviour make sense to anyone. It is driving me mad. The behaviour goes away from time to time and then comes back without any code or config update so it is frustrating to debug.
[OperationContract]
AppointmentSearchResponse AppointmentSearch(AppointmentSearchQuery Query);
public AppointmentSearchResponse AppointmentSearch(AppointmentSearchQuery Query)
this._Log.InstanceId = Guid.NewGuid();
this._Log.InfoFormat("{0} AppointmentSearch START \"{1}\"", Configuration.Platform.ToUpper(), Query.Postcode);
try
The creation of the appointments happens towards the end of the try catch so I know that the logic of the method is executed and reaches the end. However AppointmentSearch looks to be called again and again and again.
I should add that it happens in DEV and UAT azure environments with two 2015 CRM instances. Live is using old code and is still 2013. Have tried winding the cloud service code back but the behaviour still happens. I cant see how CRM could
feed back an error and cause a restart but I can't rule that out.
Also, is there a way to examine the host server logs for a cloud service?

Okay. More info.
I commented out a line that generates the appointment in CRM. My logic needs a guid so I am mocking one.
So far it looks like the problem has gone although it may return.
UAT and DEV are CRM 2015 online wile LIVE is 2013 still. I am wondering if this is a CRM issue.
Even so, my logic is wrapped in a TRY CATCH and I know that the Appointments do get generated. I am wondering if CRM returns some form of catastrophic error that circumvents the TRY CATCH and causes the cloud service to restart the method.
I still do not understand the mechanism by which this could happen.
CRM does have a number of Processes and Plugins hanging off the Appointment creation which may contribute to the problem. It is a process of elimination now.
However I wonder if there is a setting in the cloud to prevent this sort of thing. Any ideas?

Problem to publish my azure cloud service

Hello,
my goal is to deploy an exe on a web service then create a http client (c++) that uses that service. First I began with this tutorial
http://azure.microsoft.com/en-us/documentation/articles/cloud-services-dotnet-get-started/ then I use this one to run my exe in the worker role
http://www.codeproject.com/Articles/331425/Running-an-EXE-in-a-WebRole-on-Windows-Azure.
I was able to run my app on localhost. The worker role excecute the .exe I deployed and the output of my exe are settled in document folder. The problem is when I publish my app, the exe do not work!!!
any suggestions please?
thanks.

Hi sir,
Thanks for your post.
Something need to confirm:
1.Did you add some library into your project?
Non .NET EXE : C, C++, etc. If CPP EXE we need to add CPP runtime libraries like
msvcp100.dll, msvcr100.dll.
2.Did you try to debug your project on cloud service?
You could debug your cloud service on your local, please refer to this tutorials(http://msdn.microsoft.com/en-us/library/azure/ff683670.aspx ). I think you could share error information
via debug your project for the future support.
Thanks & 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.

Cloud service monitor data lagging back 20 minutes and only 5 minutes granularity

Hello,
is it normal that the charts and data in the monitor panel is 15 to 20 minutes old, and granularity is only 5 minutes? I'm trying to use the monitor page to debug and configure autoscaling, but this lag is making this really difficult.

hi sir,
The Chart data source is form Azure platform. We only can add/ remove some metrics into chart. If you want to monitor your service metrics, I suggest you can enable Azure diagnostic feature and get the metrics data from table storage . In other words, you
can custom the performance count using code. I suggest you can refer to this official document:
http://azure.microsoft.com/en-us/documentation/articles/cloud-services-dotnet-diagnostics/
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.

Unable to login from IE to Azure hosted cloud service

Hi
We have hosted cloud service on azure and not able to login with the existing users in it.
While if we add SSL to the same service we can able to login to the site.
Will you please let us know what is the issue cause? Is azure restrict to login?
Do we need to add some code changes for the IE login?
We have faces same problem on our local server but have resolved by installing patch from microsoft link "http://www.microsoft.com/en-in/download/details.aspx?id=39257"
So please help us.
Thanks,
Rohit Jagtap.

Hi,
As you said, you have face the same problem on local server, so I think this issue is more related to your application, as far as I know, it is nothing to do with azure.
To resolve this issue, I think the detail error message is necessary, I suggest you use diagnostics to log errors, refer to
http://azure.microsoft.com/en-us/documentation/articles/cloud-services-dotnet-diagnostics/ for more details, or use remote debug to find issue, see more at:
http://blogs.msdn.com/b/cie/archive/2014/01/24/windows-azure-remote-debugging.aspx
Best Regards,
Jambor
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.

Cloud Service Not Running

Hi There,
I am new to azure but I hope someone can help me. I have an asp.net web application that I am currently trying to move to azure as a cloud service. I have it set up in Visual Studio and converted it to a windows azure cloud service. This all works fine and
I can build and run the application in visual studio 2013 no problem using the azure emulator. 2 days I deployed this to windows azure and it worked just fine.
Now today, I have made changes to my application and I am trying to publish from Visual studio once again. This is failing every time whether I try to publish to staging or production. So to try and fix this I deleted everything from windows azure account
through the portal so I could start again.
Now when I create a new cloud service it creates okay but under production and staging there is a dash. I believe it is meant to say "running here". I am unable to publish to my cloud service, my application uploads from visual studio but then
i get an error telling me that i cannot publish (sorry i don't have the exact error message, but it is not very informative anyway, something like "unable to publish"). I have been googling and people are mentioning certificates and storage accounts
and editing the config files.
I cannot understand why it worked for me on my first attempt and now i cannot successfully create a cloud service.
Any help would be greatly appreciated. I would normallly give much better information to trouble shoot something, but having little knowledge of azure, i have no idea what other information you might need to help me, but please ask and I will tell you. Oh
I am on the free trial, I do still have credits.
Thank You
David

Hi,
I have solved the problem and I want to inform you how I did it.
The problem was that after i created my first azure cloud service and successfully published it, i then made some changes on my computer with visual studio and created a new project and copied over the files from the old project to the new project.
Somewhere along the way my certificates got lost. I now know that cloud services will create in azure without certificates but they will never run and deployments will fail.
To fix the issue i right clicked on my application in visual studio, i clicked publish, and then clicked the previous button twice to go back to the sign in, there it showed me my subscription, i clicked on the down arrow and clicked manage. I forget exactly,
but somehow i managed to sign out and delete existing subscriptions from my computer. Then i had to sign in again, and then click manage once more, then i had to go to certificates and remove the existing certificate, then click import and then you are given
a link to click on to download the certificate from azure, I downloaded it to my desktop, then imported that file, and then i proceeded to publish. Before i clicked finish it was still remembering my old storage account so at the top in the profiles drop down
menu i had to delete my profile (maybe i had to click manage or something first), then once i deleted my profile it researched and found the correct storage account. I have learned that without an already created storage account in azure that the publish will
fail too.
So for me, i had to fix my certificates, and then i had to make sure that i had a storage account in azure.
I hope this information helps someone else. I have been in IT and software development for many years and i must say, i am not finding azure cloud to be very easy.

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.

Debug cloud service in emulator

Similar Messages

Maybe you are looking for