Web Server

This topic provides troubleshooting steps for Web Server issues.

Let's say you have two servers with SEI installed with their own Central Point:

Server 1 Server 2

  1. Save the same BI License data source on all Central Points:
    1. Log in to the Web Central Point Configurator on each Central Point (refer to Configuring the Central Points).
    2. Ensure that the BI License data source is exactly the same for all Central Points.
  1. Activate the license on the first server:
    1. Log in to the Web Server on SERVER_ONE (refer to Starting the SEI Web Server for the first time).
    2. Enter the serial number and validate. The license is now activated and registered in the BILicense database.
  1. Restart the BI Service on other servers (SERVER_TWO in this case):
    1. Press the Windows + R keys to open the Run window.
    2. Enter services.msc and press the Enter key.
    3. In the list, right-click on BI Service and select Restart.
    4. Log in to the Web Server (refer to Starting the SEI Web Server for the first time). You should access to the second Central Point by using the same license.

Repeat steps 1 and 3 for others SEI servers you want to link to.

Perform these steps:

  1. Go to the User options (refer to User Options).
  2. Click Profile and select Opening Parameters.
  3. Under the Landing Page section, click Delete.
  4. Click Save to apply changes.

Logging options are a very useful tool for optimizing SQL queries however, they can add a lot of excess data to your SEI database. For that reason, you will likely need to perform regular maintenance operations on your tables that utilize logging operations.

There are two log tables that are not activated by default—LOG_VIEW_USAGE and LOG_SQL_EXECUTION. Activating these log tables will give you a greater deal of insight into the current state of your SEI database.

To activate them:

  1. Navigate to your Web Central Point Configurator site. The URL is typically your web server's name followed by 8133, e.g., HTTP://YourWebServer:8133.

  2. You will need to log in to your Web Central Point Configurator using the appropriate login credentials. If you do not know the username or password for your server, please contact your organization's IT specialist or BI administrator for assistance.

    Important  

    If you cannot retrieve your Web Central Point Configurator password, you must completely re-install the Web Central Point Configurator. For information on how to accomplish that, see Installing the Central Point.

  3. Once you have logged in to your Web Central Point Configurator, locate the General pane and activate the two log tables by ticking the SQL Execution Logging and View usage logging checkboxes as shown below.


  4. Once both log tables have been activated, your log data will be stored in the [SEI].[dbo].[LOG_VIEW_USAGE] and [SEI].[dbo]. [LOG_SQL_EXECUTION] tables of your SEI database.

Log Table Product IDs

Both log tables contain a PRODUCT_ID field which lists a numeric code that corresponds with a SEI product.

You can reference the table below to understand which SEI product each product ID represents:

Product ID SEI Product
0801 Web Server
0811 OLAP Manager
0812 Distributions
0895 Excel Add-in

After configuring their SMTP (Simple Mail Transfer Protocol) settings, no emails are redirected to the specified email address as they should be. And, there is no error message to help the user understand what is wrong with their SMTP configuration.

Following steps outlined below will force SEI to show an error message, allowing the user to better troubleshoot the issue.

Solution

  1. Ensure that the SMTP is correctly configured in your Web Central Point Configurator. Make sure that your Sender Email and Username values match as shown in the image below:

  2. Check your SEI admin user configuration (Admin User > Profile > General > Email), and ensure that the email address in the Email field is identical to the one you are using for your SMTP configuration in the Web Central Point Configurator. If the email addresses are not the same, temporarily change them to the same email to troubleshoot this issue (shown below).

    Important  

    If you had to change either email address value, please remember to change it back to its original value after fixing this issue.

  3. Now, open a View in SEI then open the Settings menu in the side bar and click Sharing > Email.

  4. Fill out the Export and Email form (any email recipient will do) and click Confirm to send the export.

  5. If there is an issue with your SMTP configuration, you will receive a detailed onscreen error message (as well as one in the BIService.log) that will help you identify the problem. If you do not understand the error message that appears, you can share it with your SMTP point of contact or with the SEI support team to get clarification.

After setting up OAuth login, you have the option to remove the Basic Authentication. You can re-enable it using one of these options:

Option Steps
Security menu

  1. Click Administration in the upper right hand corner.

  2. Click the Security drop-down menu in the left pane.

  3. Select Authentication.

  4. On the top of the page, click the slider to the right to enable the Enable Basic Authentication option.
Web Central Point Configurator

  1. Log into the Web Central Point Configurator.

  2. Under the General section, select the Enable Basic Authentication option.

  3. Click Update configuration.
nec-centralpoint.xml

  1. Open the nec-centralpoint.xml file.

  2. Set the enabledBasicLogin parameter to True.

  3. Save the file.

This error may occur if the necessary dependencies for the Oracle.DataAccess.dll are not installed. To resolve this, ensure that the appropriate Microsoft Visual C++ redistributable package is installed based on the version of 'Oracle.DataAccess.dll' you are using:

Please note that these instructions are specific to resolving the 'System.DllNotFoundException' error related to the Microsoft Visual C++ redistributable packages. If you encounter any other issues or have further questions, we recommend consulting the Oracle documentation or reaching out to our support team for further assistance.

On your default WebServer URL, add /api/HealthCheck at the end. If you are doing the HealthCheck on another endpoint, the memory of your WebServer Application Pool could increase and make it crash.

Example

http://yourserver:81/api/HealthCheck/

or

https://yourcompany.com/api/HealthCheck/

  • In the Windows search menu, enter Edit local users and groups.

  • Click on the Users folder, right click on the user for which the password needs to be changed and click on Set Password.

  • Click on Proceed on the warning popup that appears.

  • Enter your new password in the New password and the Confirm password text boxes and click on OK.

  • If the password is valid, a popup will appear confirming that the new password has been set. Otherwise, an error popup will appear, and the last step need to be redone according to the issue reported by the error popup.

Since 2024 Release 3, we have merged BI Service and Web Client into one component as we have transitioned from Windows Services to Web API.