DIY Microsoft Azure Troubleshooting (MP4) - Channel 9

This video shows how to fix the Error ACS50008 in the context of Microsoft Azure Access Control Service. This error usually is displayed as an Inner Message like this: An error occurred while processing your request.HTTP Error Code: 401Message: ACS20001: An error occurred while processing a WS-Federation sign-in response.Inner Message: ACS5008:SAML token is invalid.Trace ID: 903f515f-3196-40c9-a334-71277700aca6Timestamp: 2014-03-02 10:16:16Z Links: How to fix Error ACS50008 https://msdn.microsoft.com/en-us/library/windowsazure/jj571618.aspx ACS Error Codes https://msdn.microsoft.com/en-us/library/windowsazure/gg185949.aspx ACS Documentation https://msdn.microsoft.com/acs

This video shows you how to automatically collect Microsoft Azure Storage Analytic logs. Storage Analytics are key to diagnosing issues with blob, table and queue storage. You can run the Windows Azure Storage Analytics Diagnostics package (.DiagCab) to automatically collect the logs previously generated. Before using this package, you will need to enable Windows Azure Storage Analytics. Links: Download .DiagCab http://dsazure.blob.core.windows.net/azuretools/AzureStorageAnalyticsLogs_global.DiagCab How to use .DiagCab https://blogs.msdn.com/b/kwill/archive/2014/02/06/windows-azure-storage-analytics-sdp-package.aspx Storage Analytics Video https://channel9.msdn.com/Series/DIY-Windows-Azure-Troubleshooting/Storage-Analytics Storage Analytics Documentation http://msdn.microsoft.com/en-us/library/windowsazure/hh343270.aspx Storage Analytics Billing http://msdn.microsoft.com/en-us/library/windowsazure/hh360997.aspx Storage Analytics Log Format http://msdn.microsoft.com/en-us/library/windowsazure/hh343259.aspx Storage Analytics Logging - How to Enable and Where to Find the logs. http://blogs.msdn.com/b/cie/archive/2013/10/10/storage-analytics-logging-how-to-enable-and-where-to-find-the-logs.aspx Note: This package will only work on a Windows 7 or later, or Windows Server 2008 R2 or later computer. You will need to have Microsoft Excel installed on the machine where you run this package in order to see the charts.

This video is part four of a four part video series on diagnostics in Microsoft Azure Web Sites. In this video, you'll learn how to use application logging and how you can troubleshoot a crash in your application. Other Videos: Part 1: Troubleshooting ErrorsPart 2: Remote DebuggingPart 3: Failed Request Tracing Additional Resources: Enable Diagnostic Logging for Microsoft Azure Web SitesTracing in ASP.NET MVC Razor Views Quick Time Links for this Video: [00:27] Adding Instrumentation to Code[01:06] Adding Configuration to Web.config File for Tracing[02:29] Enabling Application Logging[03:27] Using the Log Streaming Service[04:35] Reviewing the Application Log[05:04] Troubleshooting a Crash[05:53] Signs of an Application Crash[06:29] Reviewing EventLog.xml to Troubleshoot a Crash

This video is part three of a four part video series on diagnostics in Microsoft Azure Web Sites. In this video, you'll learn how to use Failed Request Tracing to narrow down a problem with a slow page in your application. Other Videos: Part 1: Troubleshooting ErrorsPart 2: Remote DebuggingPart 4: Application Logging and Crashes Additional Resources: Troubleshooting Slow Requests in Microsoft Azure Web SitesHow to FTP Into a WAWS Site Quick Time Links for this Video: [00:24] Reproducing a Slow Request[01:06] Enabling Failed Request Tracing[01:36] Configuring Failed Request Tracing for Successful Requests[03:11] Reviewing a Failed Request Tracing File

This video is part two of a four part video series on diagnostics in Microsoft Azure Web Sites. In this video, you'll learn how to use Visual Studio to remote debug your application running in Microsoft Azure Web Sites. Other Videos: Part 1: Troubleshooting ErrorsPart 3: Failed Request TracingPart 4: Application Logging and Crashes Additional Resources: Troubleshooting Microsoft Azure Web Sites in Visual Studio Quick Time Links for this Video: [00:37] Reviewing a Detailed Error Message for an Application Error[02:15] Enabling Remote Debugging[03:05] Attaching the Debugger[03:53] Breaking Into the Process When an Exception Occurs

This video is part one of a four part video series on diagnostics in Microsoft Azure Web Sites. In this video, you'll learn how to troubleshoot application errors in Microsoft Azure Web Sites. Other Videos: Part 2: Remote DebuggingPart 3: Failed Request TracingPart 4: Application Logging and Crashes Additional Resources: How to Monitor Web Sites Quick Links for this Video: [00:49] Configuring Detailed Error Messages[02:07] Logging into Your Site with FileZilla[04:37] Downloading the Detailed Error Message[05:15] Using Web Matrix to Edit a File

Visual Studio 2013 makes it easy to enable and visualize diagnostics in a Microsoft Azure cloud service. You can configure the collection of standard Microsoft Azure diagnostic data such as application logs, event logs, performance counters and infrastructure logs. Just make sure to pick a reasonable transfer period so as not to impact performance, and keep the total information collected under the 4096 overall diagnostic quota. We will also demonstrate how to easily add diagnostic trace messages in your code which will appear in the WADLogsTable in your storage account. Useful links: Configuring Microsoft Azure Diagnostics Introduction to Microsoft Azure Diagnostics Microsoft Azure Diagnostics Runtime Configuration Troubleshooting Best Practices for Developing Microsoft Azure Applications

Visual Studio 2013 enables you to modify the collection of diagnostic data after a cloud service is deployed to Microsoft Azure. This is a useful technique to collect troubleshooting information from a single instance or to temporarily increase the logging level in order to diagnose a problem. Changes that you made via the Visual Studio Server Explorer will persist until you do a full re-deployment of your cloud service because the diagnostic configuration is written to the wad-control-container in your storage account. These are the links shared at the end of the video: Configuring Microsoft Azure Diagnostics Introduction to Microsoft Azure Diagnostics Troubleshooting Best Practices for Developing Microsoft Azure Applications

If you have a Access Control Service (ACS) namespace you will periodically see email indicating your certificate, key or password is about to expire. This video will guide you through what to check for to ensure all you certificates, keys and passwords are up to date. The code references it this presentation can downloaded at https://aka.ms/P4rzx3 Links ACS: Certificates and KeysACS Management Service API ReferenceCode Sample: ACS Management Service

Microsoft Azure Storage Analytics generates logs to trace requests, analyze usage trends. Storage Analytics logs contain detailed information for authenticated requests and successful anonymous requests to a storage service. Logs are stored in block blobs in a container named $logs which is automatically created when you enable analytics on a given storage account. It is very useful to enable Storage analytics to diagnose issues with storage accounts. Links: Storage Analytics http://msdn.microsoft.com/en-us/library/windowsazure/hh343270.aspx Storage Analytics Billing: http://msdn.microsoft.com/en-us/library/windowsazure/hh360997.aspx Storage Analytics Log Format: http://msdn.microsoft.com/en-us/library/windowsazure/hh343259.aspx Azure Storage Explorer(Preview 5.1) http://azurestorageexplorer.codeplex.com/releases/view/89713 Storage Analytics Logging - How to Enable and Where to Find the logs. http://blogs.msdn.com/b/cie/archive/2013/10/10/storage-analytics-logging-how-to-enable-and-where-to-find-the-logs.aspx This link has the attachment for the Analytics.xlsx file referenced in the demo.