Clever Geek Handbook

How to view errors generated by Azure Compute Emulator

I have a WCF service solution that contains a WCF service and an Azure Cloud Service project.

When running a cloud service project in Azure Compute Emulator (version 2.5 on my PC), all I see in the output for each role is

[fabric] Role status Busy

[fabric] Role State Aborted

I changed the logging level in the Compute Emulator for logging Warning

or Error

and even tried it Critical

, but no more verbose messages are displayed. I went to Google to see if there are any event log entries or log files on disk that I can look at to see why the cloud service is not working, to no avail.

What can I do to learn more about what causes the cloud service role to be interrupted and replayed?

+3


source to share


2 answers


Diagnostic logs are not collected in the Azure Compute Emulator . For projects targeting the Azure SDK 2.5, the Azure Compute Emulator no longer supports collecting diagnostic logs, including performance counters, infrastructure logs, IIS logs, and event logs. Also, the logs are no longer stored in vault or Azure storage. You can continue viewing the application logs in the Visual Studio Output window or the Compute Emulator. This only affects projects targeting the Azure SDK version 2.5; projects that still target the Azure SDK 2.4 are not affected.



Source: http://msdn.microsoft.com/en-us/library/azure/dn873976.aspx

+5


source


In my case, it turned out to be a startup task defined in ServiceDefinition.csdef

, which was the problem. After I uninstalled <Task>

, my service ran fine in Compute Emulator.



+1


source






More articles:


All Articles