ProcDump manually

Following command can be used to attach the debugger to a process of which you want to capture the memory dump:

C:\Tools\procdump> procdump.exe -ma -s 30 -n 3 <PID> <OutputFolder>

- ma: Write a dump file with all process memory. The default dump format only includes thread and handle information. -s: Consecutive seconds before dump is written (default is 10). -n: Number of dumps to write before exiting. -s:  Seconds between consecutive dumps. Change the parameter based on the slowness. <PID>: replace this with the IP of the process for which you want to capture the dump. You can use Task Manager to get PID of the process. <outputFolder>: Location where dump should be stored.

ProcDump automated / consecutive

Following command will capture 3 consecutive memory dumps of process with id 5844 each after 5 seconds when CPU of that process reach 70% and save the dumps at c:\dumps\

C:\Tools\procdump> procdump -ma -c 70 -s 5 -n 3 5844 c:\dumps\

-ma: Write a dump file with all process memory. The default dump format only includes thread and handle information. -c: CPU threshold at which to create a dump of the process. -s: Consecutive seconds before dump is written (default is 10). Change the parameter based on slowness -n: Number of dumps to write before exiting.

IIS Logs

Location for collecting IIS logs C:\Resources\Directory\{DeploymentID}.{Rolename}.DiagnosticStore\LogFiles\Web Collect the log files which are relevant to the time of issue

Freb Logs

Location for Collecting FREB logs C:\Resources\Directory\{DeploymentID}.{Rolename}.DiagnosticStore\FailedReqLogFiles

NOTE: This is not turned on by default in Windows Azure and is not frequently used.  But if you are troubleshooting IIS/ASP.NET specific issues you should consider turning FREB tracing on in order to get additional details. How to enable Failed Request Tracing

PerfView manually

• Open the perfview tool, go to Collect Menu and click on Collect option
• Select Zip, Merge, thread time check box as below and Click on Start Collection.

• Leave it for few seconds and stop the collection. (It will take a minute or so to create a compressed file)

PerfView automated

Following command can be used to capture 5 Perfview logs, 1000 MB each for w3wp.exe when it reached 60% CPU

C:\Tools\perfview> Perfview /NoGui collect "/StartOnPerfCounter=Process:% Processor Time:w3wp>60" -ThreadTime -CircularMB:1000 -CollectMultiple:5 –accepteula  

-ThreadTime: Is a parameter that monitors the CPU Thread Time -accepteula: specifies to automatically accept the Microsoft Software License Terms.   Example:

If you're seeing 80% to 90% CPU utilization by w3wp.exe then this threshold value should be 80.

Ok, I have captured the data. What do I do with that?

How to analyze a memory dump using Debug Diag

Process Crash analysis from a memory dump

How to analyze Memory Leak with memory dump using  WinDBG

How to use PerfView to diagnose Memory Leak

Channel9 Tutorial on Memory investigation using PerfView

Channel9 Tutorial on CPU Performance investigation using PerfView

• Container names must start with a letter or number, and can contain only letters, numbers, and the dash (-) character.
• Every dash (-) character must be immediately preceded and followed by a letter or number; consecutive dashes are not permitted in container names.
• All letters in a container name must be lowercase. Please note that the name of a container must always be lowercase. If you include an upper-case letter in a container name, or otherwise violate the container naming rules, you may receive a 400 error (Bad Request).
• Container names must be from 3 through 63 characters long.

container_status = blob_service.create_container(CONTAINER_NAME, public_access=PublicAccess.Container)

print("Container %s"%CONTAINER_NAME + " creation success status: %s"%container_status)

except:

print("Container %s"%CONTAINER_NAME + " creation failed")

local_file = join(LOCAL_DIRECT, local_file_list[i])

blob_name = local_file_list[i]

try:

blob_service.create_blob_from_path(CONTAINER_NAME, blob_name, local_file)

print("File upload successful %s"%blob_name)

except:

print ("Something went wrong while uploading the files %s"%blob_name)

blob_service.get_blob_to_path(CONTAINER_NAME, BLOB_TO_BE_DOWNLOADED , file_path = "<Local Path>\<File Name>.<extension of the original blob>")

print("Blob has been downloaded")

print("Blob download failed")

blob_names = blob_service.list_blobs(CONTAINER_NAME)

for blob in blob_names:

print(blob.name)

print("Blob listing failed")

blob_service.delete_blob(CONTAINER_NAME, BLOB_TO_BE_DELETED)

print("Blob has been deleted successfully")

print("Blob deletion failed")

$schedulerJobs= Get-AzureRmSchedulerJobCollection -ResourceGroupName SchedulerIbiza -JobCollectionName testscheduler | Get-AzureRmSchedulerJob
foreach($job in $schedulerJobs) 
{
if($job.JobAction.JobActionType -eq "StorageQueue")
 {
     $jobAction = [Microsoft.Azure.Commands.Scheduler.Models.PSStorageJobActionDetails]$job.JobAction; 
     Write-Output 'Storage Account ' 
     Write-Output '----------------' 
     Write-Output  $jobAction.StorageAccount;
 }
elseif(($job.JobAction.JobActionType -eq "ServiceBusQueue") -or ($job.JobAction.JobActionType -eq "ServiceBusTopic"))
 {
     $jobActionSB = [Microsoft.Azure.Commands.Scheduler.Models.PSServiceBusJobActionDetails]$job.JobAction; 
     Write-Output 'Service Bus Queue ' 
     Write-Output '----------------  ' 
     Write-Output $jobActionSB.ServiceBusQueueName;
 }
 else
 {
    $jobActionHttp = [Microsoft.Azure.Commands.Scheduler.Models.PSHttpJobActionDetails]$job.JobAction; 
    Write-Output 'Job Name ' 
    Write-Output '-------- ' 
    Write-Output $jobActionHttp.Uri;
  }
}

• Navigate to https://resources.azure.com/
• On the left-hand side panel expand the subscriptions tab as shown below

• Under the subscriptions, expand the subscription under which Cloud service is created, and then Expand the resourceGroups tab as below

• Select and expand the Cloud Service that you are facing the Issue with.
• Expand the provider’s tab and then the Microsoft.insights tab under provider’s tab as below, to list autoscale profiles created under cloud service

• Select the obsolete profile and delete it using the tab on the main panel as shown below

2. Make Testclientapp application with following parameters: [Type: Native App]
   1. Name: Testclientapp
   2. Client ID: yyyyyyyy-5659-4cf6-87bd-ad8d176521d2 (assuming)
   3. redirectURI: https://kalpitsinghtest.portal.azure-api.net/docs/services/57d0xxxxxxxxx208bce4386c/console/oauth2/authorizationcode/callback (can be taken from the publisher portal with respect to your API or for time being it can be anything)
   4. Add Permission: 1- Access echo backend 2-Check the last permission.

3. Change the security to OAuth2.0 in developer portal:
   1. Make Authorization end point url: https://login.microsoftonline.com/374bxxxxxxx-4b92-a9c9-8bea4b16f35a/oauth2/authorize
   2. Add one Additional body parameters named resource with value web app Uri-  resource : https://kalpitsinghtest.azure-api.net/
   3. Client authentication method: basic
   4. Clinet ID: yyyyyyyy-5659-4cf6-87bd-ad8d176521d2
   5. Authorization endpoint url and Token endpoint URL: as per AD tenant.
   6. Use the redirect_uri as testclientapp.