EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB300388: "AM.getResponseHeader is not a function" error occcurs when interacting with Visual Insight using MicroStrategy Web


Community Admin

• Strategy


A user encounters an error message when interacting with Visual Insight in a way that involves long running requests, e.g. adding several attributes or metrics to visualizations at once, interacting with filters, etc: AM.getResponseHeader is not a function.

SYMPTOM
A user encounters an error message when interacting with Visual Insight in a way that involves long running requests, e.g. adding several attributes or metrics to visualizations at once, interacting with filters, etc.
The following error may be encountered:

ka04W000000Oe3dQAC_0EM4400000025Uq.jpeg


An error has occurred
We are sorry for the inconvenience. Please contact your administrator for help.

AM.getResponseHeader is not a function

 
CAUSE
This is a generic error whenever the HTTP response of the HTTP request triggering the current interaction with Visual Insight is not properly handled by Visual Insight error handling. The most common cause for this error is a HTTP request timeout.
 
ACTION
In order to verify if the occurrence of this error is caused by a request timeout, Fiddler can be used:
1. Run Fiddler and monitor the HTTP request that is triggered by the interaction causing the error:
2. The HTTP request would typically fail with a HTTP 500 error

ka04W000000Oe3dQAC_0EM4400000025Us.jpeg

3. Review the HTTP response body to identify further details on the root cause of the error. In this case, the executionTimeout setting in IIS has been reached before the request could be completed  as seen in the Fiddler HTTP response body

ka04W000000Oe3dQAC_0EM4400000025Up.jpeg

 
As environment infrastructure may vary between deployments, the above is an example only for this issue occurring on a Strategy Web ASP deployments using IIS. However, the request timeout can occur on different parts of the network infrastructure. If a HTTP server is configured to forward requests to the application server, the HTTP server may close the request before the application server completed the execution in which case the request timeout on the HTTP server side would need to be reviewed. Therefore the exact root cause should be investigated on an individual basis using Fiddler and/or access and error logs of the respective HTTP and web application servers.


Comment

0 comments

Details

Knowledge Article

Published:

March 30, 2017

Last Updated:

March 30, 2017