On startup and logging in to Foresight Analytics Platform in some cases the following errors may occur.
Problem
On Foresight Analytics Platform startup the platform integrity violation is detected, the following error message is displayed instead of the login dialog box:
Files integrity is violated: <file name>.
Cause
This problem may occur if executable files or libraries are missing or do not correspond with the standard.
Solution
In this case contact your administrator.
On Foresight Analytics Platform startup error message does not appear but the application shuts down
Problem
On Foresight Analytics Platform startup error message does not appear but Foresight Analytics Platform shuts down.
If the user clicks the Cancel button in the login dialog box, error message does not appear, and Foresight Analytics Platform shuts down.
Cause
Possible causes:
On working with the 64-bit operating system the DeviceLock software solution of the version earlier than 7.1 is used.
Framework installation errors occurred.
Solution
Below are the variants of solving the problem. If the variant does not work, go to the next variant.
Check correspondence of the DeviceLock version with the system type, install DeviceLock software solution of the later version, for example, 7.1 or later.
Reinstall Microsoft .NET Framework, having previously removed Microsoft .NET Framework Client 4 Profile and Microsoft .NET Framework 4 Extended.
Application initialization error
Problem
On Foresight Analytics Platform startup one of the messages is displayed:
Foresight Analytics Platform settings contain necessity of version autoupdate.
Unable to update version because executing of <'C:\Program Files\Foresight\Foresight Analytics Platform 9.2\Studio.exe'> completed with error code -1073741515.
Studio.exe - Could not find component.
Application could not start because mfc110u.dll was not found. Reinstall the application to resolve this problem.
Studio.exe - Application error.
Application initialization error (0xc0000135). To exit the application, click the OK button.
Cause
This problem may occur if the workstation does not contain necessary prerequisites.
Solution
Start the installer again and on the Program Maintenance page select the Repair option.
File api-ms-win-crt-runtime-l1-1-0.dll not found
Problem
On Foresight Analytics Platform startup the message is displayed:
The program cannot start, because the file api-ms-win-crt-runtime-l1-1-0.dll is missing. Try re-installing the program.
Cause
This problem may occur if the workstation does not contain or has incorrectly installed the Microsoft Visual C++ 2015 Redistributable Package prerequisite.
Solution
Start the Microsoft Visual C++ 2015 Redistributable Package installer, installer bitness must match that of Foresight Analytics Platform. The installer is located in the ISSetupPrerequisites folder in the same folder with the installer of Foresight Analytics Platform.
Installation of Microsoft Visual C++ 2015 Redistributable Package on Windows 8.1 or Windows Server 2012 R2 requires updates KB2975061 and KB2919355.
Repository version is earlier/later than version of Foresight Analytics Platform
Problem
On authorization in Foresight Analytics Platform the following message is displayed in the login dialog box:
Repository version is earlier/later than Foresight Analytics Platform version.
Cause
This problem may occur if the repository version mismatches the platform version.
Solution
In this case contact your administrator.
Problem
On Foresight Analytics Platform startup, the following error message is displayed:
Error connecting to the database. The <Oracle 11.x\12.x> client is not found.
Cause
Possible causes:
Oracle DBMS front end is not installed.
Bitness of Foresight Analytics Platform and Oracle DBMS front mismatch.
Solution
Check if Oracle DBMS front end is installed, and if its bitness matches with that of Foresight Analytics Platform.
Error calling Oracle function. ORA-06413: Connection not open
Problem
On using the Oracle DBMS earlier than 10.2.0.3 version, connecting to the database returns the following message:
Error calling Oracle function.
ORA-06413: Connection not open.
Error class: EExternal.
Source: Som\SomPackStd.cpp, string 2297.
Cause
This problem may occur if Oracle DBMS versions earlier than version 10.2.0.3 are used, and the install path of Foresight Analytics Platform contains round brackets. This feature of the Oracle DBMS was fixed in 10.2.0.3 version.
Examples of install path of Foresight Analytics Platform:
Solution
Solution variants:
Reinstall Foresight Analytics Platform to the folder, which path does not contain round brackets.
Update Oracle DBMS client to 10.2.0.3 version or later.
Apply to DBMS documentation and install 5059238 update.
Error connecting to PostrgreSQL DBMS based repository
Problem
Connecting to the repository may return the error:
Error loading library of PostgreSQL functions. Perhaps the driver is not installed.
Cause
Installed PostgreSQL driver is missing or driver bitness differs from that of Foresight Analytics Platform. The error may also occur if there is no Microsoft Visual C++ Runtime Library package on the user computer even if a DBMS driver is correctly installed.
Solution
Check if the installed driver exists and its bitness. If the required driver is installed, download and install the vcredist file of the appropriate bitness at the site www.microsoft.com.
It is also recommended to add the path to the folder with installed PostgreSQL DBMS drivers to the PATH variable.
Error "Connection to Database Failed. Oracle 11.x/12.x is not found»
Problem
On connecting to Oracle DBMS based repository via BI server the error may occur:
Connection to database failed. Oracle 11.x/12.x is not found.
Cause
The ISS web server interacts with the Oracle client under the Network Service and IUSR users instead of the user who addresses the web server. The user may be denied to access the Oracle client, if the Network Service and IUSR users do not have appropriate access permissions.
Solution
To solve the problem, allow the Network Service and IUSR users access to the folder with the Oracle client.
Invalid User Name/Password and User Name Field is Empty/Password is not Set errors
Problem
On authorization in Foresight Analytics Platform the following error message is displayed in the login dialog box:
Invalid user name/password.
The User Name field is empty/The password is not set.
Cause
On authorization, user name or password were not specified or were specified incorrectly.
Solution
Reenter user name and password in the login dialog box.
Problem
On authorization in Foresight Analytics Platform the following message is displayed in the login dialog box:
Security policy prescribes password change.
If the new password is not set or the Cancel button is clicked, the following error message is displayed:
User must change the password.
Cause
This problem may occur if the maximum password age set in the policy editor is expired.
Solution
Password change is required. To do this, enter the password in the window with the notification about password change requirement and click the Yes button.
If a new password does not satisfy password policy requirements, the appropriate information appears below the edit boxes. Select password in accordance with the rules. After the password is changed, the web application session is finished. To log in to the system, open a new browser window.
Problem
On authorization in Foresight Analytics Platform the following message is displayed:
User <User> is locked.
Cause
Possible causes:
Password errors limit is overrun.
User is locked by the administrator.
Solution
In this case contact your administrator.
Problem
On authorization in Foresight Analytics Platform one of the following messages is displayed in the login dialog box:
Access to system for the <user name> user is denied.
Access to system from this workstation <workstation address> for this user is denied.
Access to system for the <user name> user is denied.
Access to system from the station with the <workstation IP address> IP address for the <user name> user is denied.
Access to system for the <user name> user is denied.
Access to system from the workstation with the <workstation MAC address> MAC address for the <user name> user is denied.
Access to system for the <user name> user is denied.
Access to system for the <user name> user now is denied. Prohibition period end - HH:MM:SS.
Cause
User access is denied:
From this workstation.
From the station with definite IP address.
From the station with definite MAC address.
On this day.
In this period.
Solution
In this case contact your administrator.
The user has insufficient permissions to access object navigator
Problem
On authorization in Foresight Analytics Platform the following message is displayed in the login dialog box:
The <user name> user does not have permissions to access object navigator.
Cause
This problem may occur, if the user does not have the Login to Object Navigator permission.
Solution
In this case contact your administrator.
The "Access Denied" error message on authorization in the web application
Problem
Authorization in the web application returns the following message:
Access denied.
Contact administrator.
Registration in the desktop application is executed without errors.
Cause
This problem may occur if parameters of the SQLNET.ORA configuration file are incorrectly specified. The file is located in the S\network\admin\, where S is the Oracle installation path.
Solution
For the correct password authentication in the SQLNET.ORA configuration file replace SQLNET.AUTHENTICATION_SERVICES = (NTS) with SQLNET.AUTHENTICATION_SERVICES = (NONE).
Services not found on authorization in the web application
Problem
After installation of the web application on the authorization attempt the system shows the error that services are not found (ServiceNotFound).
Cause
The address for web services is specified in basic settings of the web application in the PP.xml file. Services address is case-sensitive, if the case is incorrect, the error appears.
Solution
The path of the files depends on the type of the web server in use:
ASP.NET: S\Config.
Java: S\pp\WEB-INF.
where S is the path to the folder with installed web application.
When opening the PP.xml file for edit, it is necessary to check the correctness of the address of services considering the case in the "service url="S1" />" string. Where S1 is the path to BI server.
Default paths on using IIS server:
http://<BI server>/fpBI_App_v9.2x64/axis2/services/PP.SOM.Som
Where <BI server> is the name or IP address of the server where the BI server works.
When Apache server is used, the path where BI server is located, is set up via configuration file.
After saving changes it is necessary to open the web application and repeat authorization.
Invalid repository identifier on authorization in the web application
Problem
After installation of the web application on the authorization attempt the system shows the error that the repository identifier is invalid.
Solution
Close the browser window and start the Foresight Analytics Platform desktop application with Administrator permissions on the server and web services installed.
Click the Settings button in the dialog box. From the list of available repositories select the one, which is used on authorization attempts in the web application, and click the Edit button.
In the dialog box that opens select the Anyone Who Uses This Computer checkbox to make the repository available for all users an enable the web services to interact with Foresight Analytics Platform repository.
After saving changes restart the web server with the web services, open the web application and repeat the authorization procedure.
Error Creating/Updating User on Working in Repository Based on PostgreSQL DBMS
Problem
On creating or updating user, the On Granting Permissions To DBMS Objects Error Occurred. Update Users error occurs.
Solution
If the Public default scheme is used on working with PostgreSQL DBMS, all repository users will be able to create tables. This behavior is linked to the PostgreSQL DBMS work specific. It can lead to problems of user updates and taking into account access permissions of users that are repository administrators. To avoid error it is recommended to create all objects only under users included into Administrators group.
See also:
Solving Possible Problems in Foresight Analytics Platform