I was debugging a cloud service and was using azure storage and compute emulator. Suddenly I noticed I began receiving SEHException when accessing a cloud table, and the emulator icon is not there anymore in the notification area.
I remember I checked don't show this window again sort of option, so that the annoying window of loading the emulator is not displayed.
I restarted my computer and ran VS2013 as admin with no luck.
I followed this article: http://msdn.microsoft.com/en-us/library/azure/hh403989.aspx
You just need to go to start -> search: Windows Azure Storage Emulator
This will run the storage emulator only, but you can run the compute emulator through the notification area icon which displays when you start the storage emulator.
Edit:
The above mentioned solution did not actually solve my problem, I found later that I have to set the cloud service as the startup project, not the web role.
Edit 2:
It can be also because of running a BitTorrent client. windows azure development storage blob service not starting
Related
I am trying to get Azure offline sync for mobile apps working. I'd like to use that API with the "Azure Storage Emulator".
Do these two things work together? There is no mention of whether this is the case.
Offline data sync cannot use the storage emulator - you need to think of the storage emulator simply as a test endpoint for Azure Storage. Offline sync works with SQLite and Core Data.
Also remember that the Azure storage emulator runs specifically on a Windows development machine; you cannot install it on an Android / iOS / Windows Phone device.
I'm getting the following error while trying to publish an Azure cloud service (classic) from Visual Studio:
There's so little information in that error that I have no idea what to start fixing. Is there a more detailed log somewhere, and what steps (if any) need to be taken to enable it?
The solution for me that works is to refresh the Azure connection. I use for that the Server Explorer - expand the needed service branch lead to the solution.
The solution can be refresh the credentials as well. It may be connected with the Visual Studio or Azure SDK versions, so it is worth to try to start from reinstalling at least Azure SDK.
I have a WorkerRole running as a Cloud Service. I want to debug it because when I call the service on Azure the calling application hangs.
I tried attaching the debugger to the remote service but it times out after 90 minutes of doing nothing. So, my next step is to run the service locally with the emulator, which I am now doing.
I have the emulator running but I have no idea how to connect to this local service and what the endpoint is. Can someone help?
To be able to debug your Azure cloud service (running in the cloud), you first need to make sure it is built with the Debug configuration and that the remote debugger feature is enabled, then you'll be able to attach to the role from Visual Studio as if you were running it locally.
To do the debugging locally, with the Azure Emulator, all you need to do is to run your cloud service project (F5 (if it is the default project) or right click -> Debug -> Start new instance).
You can follow these steps to enable the debugger and attach to the service (both locally and in the cloud): https://msdn.microsoft.com/en-us/library/azure/ff683670.aspx
I have a WCF service solution which contains the WCF service and a Azure Cloud Service project.
When running the cloud service project in the Azure Compute Emulator (version 2.5 on my PC), all I see in the output for each role is
[fabric] Role state Busy
[fabric] Role state Aborted
I've tweaked the logging level in Compute Emulator to log Warning, or Error and even tried Critical, but no more detailed messages are displayed. I have been Googling to see if there are any event log entries, or log files on disk, that I can view to find out why the cloud service is not working, but to no avail.
What can I do to find out more about what is causing the Cloud Service role to abort and and retry?
Diagnostics logs are not collected in the Azure compute emulator – For projects that target the Azure SDK version 2.5, the Azure compute emulator no longer supports the collection of diagnostics logs, including performance counters, infrastructure logs, IIS logs, and event logs. In addition, logs are no longer stored in Azure storage or development storage. You can continue to view application logs in the Visual Studio Output window or the compute emulator. This only affects projects that target Azure SDK version 2.5; projects that continue to target Azure SDK 2.4 are not affected.
Source: http://msdn.microsoft.com/en-us/library/azure/dn873976.aspx
In my case, it turned out to be a startup task defined in ServiceDefinition.csdef that was the problem. After I removed the <Task> my service ran fine in Compute Emulator.
I'm trying run my first Azure web role. Storage Emulator starts, Compute Emulator starts, but the deployment takes a lot of time. VS asks if I want to continue try to deploy. In the Compute Emulator UI states "Role State Unknown". No further information.
What could cause the deployment to the emulator to hang and where can I find more information on what happened?