Problems on Setting Up Foresight Analytics Platform on ASP.NET

Open the IIS service manager and select the Connections root element of the tree, double-click the ISAPI and CGI Restrictions:

For the ASP.NET v4.0.30319 and Axis2 v9.2 x64 strings the Restriction column must display Allowed:

 

If it is not, open the editing dialog box and select the Allow Extension Path to Execute checkbox for each string.

If the ASP.NET v4.0.30319 strings are missing, set up Microsoft .NET Framework 4.5.2.

If the Axis2 v9.2 x64 string does not exist, the Foresight Analytics Platform library has not been registered, add it manually:

Open the IIS Manager and double-click the Handler Mappings icon for the BI server's virtual directory:

The list that opens must contain the string:

If it is missing, create it manually as shown below:

Check if the Anyone Who Uses This Computer checkbox is selected in the server repository connection settings in the desktop application of Foresight Analytics Platform.

Install the static content support in IIS.

Open Server Manager, go to the Roles - Web Server (IIS) section and click the Add Role Services link. In the dialog box that opens select the Static Content checkbox:

Click the Install button.

Set advanced options in IIS7.

Open Server Manager, go to the Web Server (IIS) section and click the Add Roles and Components link. Select the checkboxes on the components as it is sown on screenshots on the Server Roles page:

After the required components are selected at the end of installation wizard, click the Install button and wait when the component installation is finished.

On opening the web application the message "Value cannot be empty" is displayed, provided that the BI server is working correctly.

Solutions:

• In server repository connection settings select the Anyone Who Uses This Computer radio button:
  

• The IIS takes an information about the existing repositories only at the start of the process. If connection parameters were determined later, restart the IIS process:

• If the first two options do not work, check if the settings are entered in the registry branch: [HKEY_LOCAL_MACHINE\SOFTWARE\Foresight\Foresight Analytics Platform\9.0\Metabases].

Set up Microsoft .NET Framework 4.5.2.

An error appears during the authorization in the web application: HTTP 500.21 - Internal Server Error IIS 7 and WCF. The ppService handler contains the ManagedPipelineHandler damaged module in the module list.

Solution: set up Microsoft .NET Framework 4.5.2.

If the web application is worked with at a computer that is remote from BI server, the web application may display the error "The page cannot be displayed because an internal server error has occurred" instead of BI server error text. In order the error text of BI server is displayed instead of this text, determine the following IIS settings:

1. Run IIS explorer and go to the Error Pages section.

2. Select the context menu item Change Parameters for the string with error 500.

3. In the dialog box that opens select the Detailed Errors radio button.

During the authorization process the web application returns the Access Denied message, while authorization in the desktop application is successful.

Solution: on using the password authorization replace in the SQLNET.ORA configuration file located at S\oracle\ora92\network\admin\, where S is a path to the folder with installed Oracle, SQLNET.AUTHENTICATION_SERVICES = (NTS) with SQLNET.AUTHENTICATION_SERVICES = (NONE).

If BI server and back end of designer of business applications are located in one domain, and the back end is addressed from another domain, the error may occur: "Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource."

To correct the error, execute the following operations at the IIS web server:

1. Open the IIS Manager and select an application corresponding to the BI server in the connection tree - fpBI_App_v9.2x64.

2. Select the HTTP Response Headers among the available functions.

3. Add the following headers:

• Access-Control-Allow-Headers with the value "content-type, accept-language, get-ppbi-time, cache-control, soapaction"

• Access-Control-Allow-Origin with the value *. To get access only from specific domains, specify names of necessary domains instead of *: http://www.a.com http://www.b.com.

4. Restart the IIS web server.

If BI server and back end of designer of business applications are located in one domain, and the back end is addressed from another domain, the error may occur: "Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource."

To correct the error, execute the following operations at the Apache web server:

1. Open the httpd.conf configuration file for edit.

2. Uncomment the following strings:

• LoadModule rewrite_module modules/mod_rewrite.so

• LoadModule headers_module modules/mod_headers.so

3. Set the All value in the <Directory />...</Directory> block for the AllowOverride directive, and also add the following strings inside the block:

    Header always set Access-Control-Allow-Headers "content-type, accept-language, get-ppbi-time, cache-control, soapaction"

    Header always set Access-Control-Allow-Origin "*"

    RewriteEngine On

    RewriteCond %{REQUEST_METHOD} OPTIONS

    RewriteRule ^(.*)$ $1 [R=200]

4. Restart the Apache web server.