Diagnosing MobileServiceInvalidOperationException - azure

I'm calling an Azure Mobile Service from a Windows Phone 8 emulator.
Sometimes I receive a MobileServiceInvalidOperationException with no InnerException property. In Fiddler, I see the response contains only 400 - Bad Request. No further details.
How do I diagnose these problems? Are there any server-side logging tools on Azure Mobile Services to aid me?

I found the answer myself. I'll share it with you in case another Azure Mobile Services beginner is looking for this.
On the Azure management portal, go to your mobile service. There is a "Logs" tab which records server-side errors. That's all I needed:

Related

How can I access LogStream of Managed Application App Service?

We have a managed application published in Microsoft Partner Center, for preview audience.
We have both publisher and client tenants.
After installing the app into the client's tenant I can't access the log steam of the installed app from either publisher nor client tenants.
Adding Roles in Access Control IAM doesn't help.
When I'm trying to open Log Stream i can see only "connecting....".
If i turn on developer tools and open Network i see the "/api/logstream/" requests and "403 Forbidden" response. Adding a screenshot: .
How can i fix this?
Any help would be much appreciated, thanks in advance.
Looks like it's some sort of a bug as LogStream doesn't work on web portal, however it works in the VisualStudio Code.
Who might have thought, right ?
First, you should install Azure Tools. Next step is to sign-in with your account.
After that, you can open log stream:
Subscription / AppServices / Your App / Logs / Connect To Log Stream

Unable to Create web app bot from Azure portal using free subscription

Unable to Create web app bot from Azure portal.
Getting error like this "We're having problems communicating with the server. Click to contact Azure Support."
I have tried near 5 different location but the result is same.
Can anyone help me in this.
The issue was mitigated. Could you please re-try and let us know?
Kindly review the Service health page on the Azure Portal to find more details on this issue.
The ‘Service Health’ -Service issues view shows any ongoing problems in Azure services that are impacting your resources. You can understand when the issue began, and what services and regions are impacted. You can also read the most recent update to understand what Azure is doing to resolve the issue.

Azure Web Application Raising Internal Server Error when talking to API Web Application

I have an solution that consists of a web gui front end and a web api backend. Both use Azure AD for auth with the former passing a token to the latter.
This all works fine on both a localhost and an OnPrem server, but when I push the release to Azure, I get a 500 Internal Server error when the GUI attempts to utilise the API.
At the moment, I am unable to obtain any further error detail.
I know this is a little vague, but I am pretty new to the whole Azure platform and am unsure how to diagnose the issue further.
Any assistance or pointers that people can give would be greatly appreciated.
Cheers
I know this is a little vague, but I am pretty new to the whole Azure platform and am unsure how to diagnose the issue further.
Per my understanding, you could follow the steps below to troubleshoot this issue:
For .NET web application, you could add customErrors flag in the Web.config file and set the value to On or RemoteOnly to see the detailed error message. Also, you could enable diagnostics logging for web apps to retrieve more details about the error message. Or you could just leverage Remote debugging web apps for a simple way to locate the specific issue. For more details, you could follow this official tutorial about troubleshooting azure web apps.
For .NET Core web application, you could refer to this similar issue. Additionally, for php, you could refer to nfo About PHP Fatal Error and Error Log on Azure Website and Change the built-in PHP configurations to troubleshoot this issue.

Azure alert: The portal is having issues getting authentication tokens for Microsoft_Azure_Compute, SqlAzureExtension

I'm getting this alert but I can't seem to find any information related to it online. I seem to be getting it 4 times every 6 hours. I have a SQL database up and running with Microsoft's test AdventureWorks db on it, and 5 test VMs that are all deallocated. Anyone had this and solved it, or know where to guide me to get this resolved?
Only other thing I can find is this, which doesn't seem to apply, as I have no web apps or services installed: https://social.technet.microsoft.com/Forums/en-US/f2a8b549-3be7-413e-a233-cf66acf9fd8b/portal-is-having-issues-getting-authentication-token-in-azure?forum=windowsazuremanagement
App Service Authentication/Authorization is exposed in the Azure Preview Management Portal. To enable it, navigate the Settings blade of any Web or Mobile App and select Authentication/Authorization. Flip the switch to On to view the options for protecting your site.
For more information, kindly refer the link given below:
click here
Hope this helps.

Azure Website - Web API Swallowing Errors

I have a asp.net web api application deployed as an azure web app. One of the endpoints occasionally throws an exception. Normally this isn't an issue for us. We have an ExceptionLogger attached to the api services. This has been in place for sometime and normally works fine.
Currently we see that a 500 response comes back from the server, but nothing is logged. I have tried setting GlobalConfiguration.Configuration.IncludeErrorDetailPolicy to IncludeErrorDetailPolicy.Always, but the response always comes back with no body content.
What else can I do to track the source of the problem?
If you have a consistent repro, then you can use remote debugging to attach to your web app and debug it (https://azure.microsoft.com/en-us/documentation/articles/web-sites-dotnet-troubleshoot-visual-studio/).
Failing that, you can enable better diagnostic logs using the web app settings. Information on how to do so is here:
https://azure.microsoft.com/en-us/documentation/articles/web-sites-configure/ under the section "Enabling diagnostic logs".
In your case you should have application logging enabled, and perhaps failed request tracing would be useful (FREB).
For even more tools you can use the Support Site Extension (http://azure.microsoft.com/blog/2014/12/01/new-updates-to-support-site-extension-for-azure-websites/) which would allow you to look at live event logs and HTTP traffic. For a deeper dive into debugging in Azure App Service see: https://channel9.msdn.com/Events/Ignite/2015/BRK4704.

Resources