SALES: 1-800-867-1380
Troubleshooting API Operations
Collapse the table of content
Expand the table of content

Troubleshooting API Operations


Updated: June 29, 2016

The following sections offer troubleshooting tips for API operations:

Failed Request Tracing

The x-ms-request-id Header

The development environment supports the use of the Internet Information Services (IIS) 7.0 Failed Request Tracing feature to log information about requests. Failed Request Tracing produces detailed trace logs according to filters established within a web role’s configuration.

Windows Azure outputs trace log files to the default IIS directory for failed request logs. This directory by default is %SystemDrive%\inetpub\logs\FailedReqLogFiles.

Each web role must enable tracing by using rules placed in the project's web.config file. To enable tracing, place the following in the system.webServer section of your web.config file:

    <add path="*">
        <add provider="ASP" verbosity="Verbose" />
        <add provider="ASPNET" areas="Infrastructure,Module,Page,AppServices" verbosity="Verbose" />
        <add provider="ISAPI Extension" verbosity="Verbose" />
        <add provider="WWW Server" areas="Authentication,Security,Filter,StaticFile,CGI,Compression,Cache,RequestNotifications,Module" verbosity="Verbose" />
      <failureDefinitions statusCodes="400-599" />

To disable tracing, remove this section from the web.config file.

Every request made against the storage services returns a response header named x-ms-request-id. This header contains an opaque value that uniquely identifies the request.

If a request is consistently failing and you have verified that the request is properly formulated, you may use this value to report the error to Microsoft. In your report, include the value of x-ms-request-id, the approximate time that the request was made, the storage service against which the request was made, and the type of operation that the request attempted.

© 2016 Microsoft