ReportPortal
ReportPortal
Home | Profile | Register | Active Topics | Members | Search | FAQ
 All Forums
 ReportPortal General Forum
 Report Portal General Issues
 Build 195 Excel Export Error

Note: You must be registered in order to post a reply.
To register, click here. Registration is FREE!

Screensize:
UserName:
Password:
Message:

* HTML is ON
* Forum Code is OFF
Smilies
Smile [:)] Big Smile [:D] Cool [8D] Blush [:I]
Tongue [:P] Evil [):] Wink [;)] Clown [:o)]
Black Eye [B)] Eight Ball [8] Frown [:(] Shy [8)]
Shocked [:0] Angry [:(!] Dead [xx(] Sleepy [|)]
Kisses [:X] Approve [^] Disapprove [V] Question [?]

 
Check here to subscribe to this topic.
   

T O P I C    R E V I E W
kevindwhite Posted - 08/31/2017 : 13:48:36
When I attempt to export an OLAP result to Excel the application responds with the following error message

Server Error in '/ReportPortal' Application. A potentially dangerous Request.Form value was detected from the client (hdnExcel=" or: 2) Add the following section to the configuration file of your application: Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode. Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario. Stack Trace: [HttpRequestValidationException (0x80004005): A potentially dangerous Request.Form value was detected from the client (hdnExcel="
5   L A T E S T    R E P L I E S    (Newest First)
admin Posted - 09/01/2017 : 20:22:28
1. Download and unzip: http://www.reportportal.com/download/rp_195_Web.config.zip
2. Backup old file and copy the unzipped file to : "C:\inetpub\wwwroot\ReportPortal(_195)\Web.config"
kevindwhite Posted - 09/01/2017 : 11:37:02
We did not alter the web.config file. However we did upgrade from a much earlier build which did require .Net 2.x. I suspect this setting was not changed during the upgrade.

Would switching the application to .Net 4.6 solve the issue? Would we still have to alter the web.config as well as the Excel.aspx file?
admin Posted - 09/01/2017 : 10:20:31
Starting with build 194 .net 2.0 is no longer supported. You have build 195. So "Target .NET Version" should not be "2.0". Did you manually modify the web.config file?
kevindwhite Posted - 09/01/2017 : 09:24:17
The following is a copy of the contents of the version information from within our instance of Report Portal

Build Number:
ReportPortal 5.0, Build 195, Jan 19, 2017
Target .NET Version:
2.0
Current .NET Version:
4.0.30319.18444
OS Version:
Microsoft Windows NT 6.1.7601 Service Pack 1
64 bit:
True
Culture
en-US

I have asked my system administration team to procure the remaining two items you have requested.
admin Posted - 08/31/2017 : 20:07:56
Please go to Admin > Settings > Version. What is the "Current .NET Version" and "Target .NET Version"?

Does the first line of file: C:\inetpub\wwwroot\ReportPortal\olap\Excel.aspx have
validateRequest="false" ?

Did you modify Web.config? It needs to have:
httpRuntime requestValidationMode="2.0

https://stackoverflow.com/questions/81991/a-potentially-dangerous-request-form-value-was-detected-from-the-client?page=2&tab=active#tab-top

ReportPortal © 2000-2002 Snitz Communications Go To Top Of Page