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

KB438703: In MicroStrategy Web 10.4 Hotfix 4, a report, document, or dashboard with the character ampersand “&” that is exported to Excel, PDF, or Print will encounter “Server Error”


Community Admin

• Strategy


In MicroStrategy 10.x when the user attempts to export a document, report or dashboard with the ampersand character “&”, the user will encounter an error “Server Error – System.Web.HttpException: A potentially dangerous Request.Path value was detected from the client”

STEPS TO REPRODUCE:
1) Create a report with attribute “Year” and metrics “Cost” and “Profit”, as shown below:
 

ka04W000000ObaAQAS_0EM44000000Q0SO.jpeg

 
2) Execute and Save Report with name including ampersand (Ex. Cost & Profit) .
 
3) Export the saved report by going to “Report Home> Export > PDF”, as shown below:

ka04W000000ObaAQAS_0EM44000000Q0ST.jpeg

 
4) Select exporting options in the next page.
 
5) Export the report to encounter the error message “Server Error in ‘/Strategy’ Application – System.Web.HttpException. A potentially dangerous Request.Path value was detected from the client”.
 

ka04W000000ObaAQAS_0EM44000000Q0SY.jpeg

         
CAUSE:
This is a known issue in Strategy 10.4 Hotfix 4, when a user uses certain characters to name their report or document. Certain characters are considered XML escape characters and are handled and processed by the web server differently. Because the ampersand (&) is considered an XML escape character and is a special reserved character within XML, it is treated differently and not purely as a string character.
 
WORKAROUND:
Renaming the report or document without the special characters will resolve the issue; the defect has also been addressed in the version 10.4 hotfix 5 release.
 
ACTION:
This issue has been reviewed by Strategy and addressed in the version 10.4 hotfix 5 release. Please upgrade to take advantage of the fix.
  KB438703


Comment

0 comments

Details

Knowledge Article

Published:

October 12, 2017

Last Updated:

November 9, 2018