1330624 - InfoView .NET displays "Server Error in /AnalyticalReporting" When Checking An Instance Details > Status in Business Objects Enterprise XI 3.1

• From the client:

Server Error in '/AnalyticalReporting' Application.

Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine. 

• When browser is used on the server (these errors are not displayed from a client browser): 

Server Error in '/AnalyticalReporting' Application.
Parser Error
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

Parser Error Message: Ambiguous match found.

Source Error:

Line 1:  <%@ Page language="c#" Codebehind="HistoryStatus.aspx.cs" AutoEventWireup="false" Inherits="BusinessObjects.AnalyticalReporting.PlatformActions.Shared_HistoryStatus.HistoryStatus" %>
Line 2:  <%@ Import Namespace="BusinessObjects.Enterprise.WebUtil.clientaction" %>
Line 3:  <%@ Import Namespace = "BusinessObjects.AnalyticalReporting.Shared" %>


Source File: /AnalyticalReporting/PlatformActions/Shared_HistoryStatus/HistoryStatus.aspx    Line: 1

Version Information: Microsoft .NET Framework Version:2.0.50727.1433; ASP.NET Version:2.0.50727.1433

• Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".
  
  
  <!-- Web.Config Configuration File -->
  
  <configuration>
      <system.web>
          <customErrors mode="Off"/>
      </system.web>
  </configuration>
  
  
  Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.
  
  
  <!-- Web.Config Configuration File -->
  
  <configuration>
      <system.web>
          <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
      </system.web>
  </configuration>
  

Server Error, /AnalyticalReporting, Instance Details error , KBA , BI-BIP-DEP , Webapp Deployment, Networking, Vulnerabilities, Webservices , Bug Filed