System Management Troubleshooting

Email Sending Failure

Issue description:

Email sending fails with the error message: "535 Error: authentication failed."

Solution:

Enter the authorization code in the password field instead of the email password. For details, see Mailbox.

Test Email Sending Failure Due to Not Being Added to the Java Trusted List

Issue description:

On the internal network server, sending SSL-encrypted emails using Foxmail works fine, but the sending fails when you switch to FineReport. Emails can be sent when you change to port 25 with no encryption.

An error message is displayed: "Could not connect to SMTP host: SMTP.fanruan.cn, port: 465, response: -1."

Cause analysis:

You did not add the certificate of the mail server that you set up on the internal network to the trusted certificate list in Java. Emails cannot be sent using certificates that are not included in the list. For clients that have their own trusted certificate system, for example, Firefox, the emails can be sent normally.

Solution:

Import the certificate into the Java trusted certificate list.

Anti-Spam Mechanism

Problem: An error is reported in the log: "com.sun.mail.smtp.SMTPSendFailedException: 554 DT:SPM 163."

Cause: This error occurs because, with the anti-spam mechanism of the 163 mail server, the test email with the subject "test" is flagged as spam and fails to be sent.

Solution:You can avoid using words like "test" in the subject of test emails. If the email is then sent successfully, the configuration is correct, and the issue is caused by restrictions of the server itself.

Error When Getting Verification Code

If you send emails frequently within one minute, an error message "Failed to get verification code." will be displayed.

You can wait for one minute and then try again.

Error in Using Port 465

Issue description:

An error message is displayed: "Could not connect to SMTP host: SMTP.exmail.qq.com, port: 465, response: -1'."

Cause analysis:

Port 465 is open for the SMTPS (SMTP over SSL) protocol, which secures SMTP by wrapping SMTP inside TLS.

However, the email service of FineDataLink requires the SSL protocol.

Solution:

You can switch to port 25.

App Name Validation Error

Issue description:

An error is displayed when you create a new application in Open Platform: "The name must be unique."

Cause analysis:

fanruan.log shows that the length of the secret field in the fr_open_app table is insufficient.

Solution:

Increase the length of the secret field.

For the built-in FineDB:

ALTER TABLE "PUBLIC"."FR_OPEN_APP" ALTER secret VARCHAR(1000);

For FineDB migrated to MySQL:

ALTER TABLE PUBLIC.FR_OPEN_APP MODIFY COLUMN secret VARCHAR(1000);

Exception When Importing All Selected Scheduled Tasks

Issue description:

In FineDataLink V4.0.28, when you import scheduled tasks through Resource Migration and select all tasks in the list, it will display "0 items imported successfully and 0 items imported unsuccessfully." If you select only some scheduled tasks for import, the import succeeds.

Cause analysis:

Some subtasks are missing from the scheduled tasks to be imported.

Solution:

Ensure the tasks to be imported include all subtasks.

External Database Plugin Expiration Issue

Issue description:

The following operations fail in User Management: 

• Add/Edit/Delete/Disable/Import a user. 

• Add/Edit/Delete a department. 

• Add/Edit/Delete a position.

And a prompt message is displayed, indicating that the external database plugin has expired, the current operation will not take effect. This feature is currently affected, please register promptly.", as shown in the following figure.

Cause analysis:

The project uses an external FineDB database of the information innovation version. The function point license for this type of database has expired, which prevents the User Management function from working properly.

Solution:

You can contact FanRuan's sales personnel to renew or purchase the usage license related to this type of database.

User Synchronization Failure Due to NoClassDefFoundError

Issue description:

User synchronization fails after you set the custom encryption method. An error message occurs: NoClassDefFoundError: com/fr/privilege/Base64PasswordValidator (wrong name: com/fr/decision/privilege/encrpt/Base64PasswordValidator).

Cause analysis:

The custom encryption class file is saved in the wrong path.

Solution:

In the error message, the path after "wrong name:" is the correct path. Move the class file to the correct path and reset the encryption method.

Inaccurate Last Login Information

Issue description:

When you log in to the FineDataLink data platform, the last login information is inaccurate.

Cause analysis:

Login information is captured on the login page. If you bypass the login page and directly access the FineDataLink data platform, the current login information will not be recorded and displayed as the last login information upon your next login.

For example, if you tick Keep Logged In on the login page and enter the FineDataLink data platform (with Last Login Prompt enabled), the last login time is displayed as Time 1. Close the browser completely.

When you access the FineDataLink data platform again without going through the login page, the login time is recorded as Time 2, but the last login time is still displayed as Time 1.

Last Login Information Not Displayed

Issue description:

Last Login Prompt is enabled, but the last login information is not displayed upon a login.

Cause analysis:

The IP address and location in the login information are obtained from the FanRuan cloud center at https://cloud.fanruan.com/api/query/ip?timeout=10000.

If the server cannot connect to this address, the last login information cannot be retrieved successfully. However, this does not affect logging.

Platform Login Failure for All Users

Issue description:

The NGINX reverse proxy is used in the project, and Lock Object is set to IP. In this case, when the password error count exceeds the error count limit, the account is locked, and all users are unable to log in to the FineDataLink data platform.

Cause analysis:

With the NGINX reverse proxy used, the user's login request first goes to the reverse proxy and is then forwarded to the FineDataLink project by the proxy.

Therefore, the IP address of the server (where NGINX is located) is obtained and locked by the project, causing all subsequent users to be unable to log in.

Solution:

You can add request headers in NGINX proxy configurations to pass the user's real IP address to the FineDataLink project.

1. Single-Layer NGINX Proxy

You can edit the nginx.conf file and add the following code in the location module, as shown in the following figure.

proxy_set_header X-Forwarded-For $remote_addr;

2. Multi-layer NGINX Proxy

For the NGINX proxy server that can directly receive the client requests, you can edit the nginx.conf file and add the following code in the location module, as shown in the following figure.

proxy_set_header X-Forwarded-For $remote_addr;

For the inner-layer NGINX proxy server, you can edit the nginx.conf file and add the following code in the location module, as shown in the following figure.

proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

Unexpected Tomcat Exit with No Tomcat Process

Issue description:

After you modify the Tomcat memory through the Quick Fix function of Health Inspection, Tomcat exits, and no Tomcat process appears when you start the project with the command ./startup.sh.

Cause analysis:

The system memory is insufficient.

Solution:

Delete the setenv.sh file (a configuration file generated when a quick fix is conducted) in the path Tomcat installation directory/bin.

Menu Icons Missing

Issue description:

The menu icons on the System Management page of FineDataLink are missing.

Cause analysis:

The project is deployed in an HTTPS environment, which causes a loading mechanism issue with the Internet Explorer browser.

Solution:

Log in to FineDataLink as the admin, choose System Management > Security Management > Advanced Setting, and disable Disable Browser Cache, as shown in the following figure.

MySQL Network Component Check Error

Issue description:

When you perform the network component check on the MySQL database, an error occurs:

if you are using the mysql client program,it's default max_allowed_packet variable is 16MB.To set a large value

At this time, you can modify and increase the value of max_allowed_packet. For details about how to modify it, you can refer to the relevant online materials.

Cause analysis:

The amount of data transmitted during the check exceeds the limit of the MySQL database.

This is because the value of max_allowed_packet of the MySQL database is too small.

Solution:

One:

In the my.ini file in the MySQL installation directory, change the value of max_allowed_packet in mysqld to 500 MB and restart the MySQL database.

Two:

1. Use the statement set global max_allowed_packet = 524288000; to set the value of max_allowed_packet to 500 MB.

2. Check whether the modification is successful through the statement show VARIABLES like '%max_allowed_packet%';.

Error When Using the DROP Statement

Issue description:

From FineDataLink V4.0.28, using a DROP statement in an SQL query results in an error indicating that the keyword cannot be used, and the SQL injection prevention feature cannot be disabled.

Cause analysis:

SQL injection prevention validation has been added to the Data Synchronization and Data Transformation nodes.

Solution:

The DROP statement can be used in SQL Script. It is not supported in Data Synchronization, Parameter Assignment, or Data Transformation.

Excessively Long Data in the fine_conf_entity Table

Issue description:

The backup fails with an error message "java.sql.SQLDataException: data exception: string data, right truncation; table: FINE_CONF_ENTITY column: VALUE."

Cause analysis:

There exists excessively long data in the fine_conf_entity table, causing backup failure.

Solution:

One: Filter out and delete excessively long data fields.

Two: This solution can only be used in MySQL external databases.

The super admin can adjust the maximum length limit by modifying the value of the parameter BackupConfig.customValueLength through Fine_Conf_Entity Visualization Configuration. The setting takes effect after you restart the server. The following table describes specific content.

Failure to Write Entity GlobalParamEntity

Issue description:

Platform configuration backup fails with the error: "Fail to write entity GlobalParamEntity."

Cause analysis:

The length limit of the debug value set in the Parameter Assignment node is 255 by default. If you have manually modified the length limit because the limit-exceeding debug value cannot be stored in the database, the external database will be backed up as the internal database during FineDB backup, causing an error.

Solution:

Locate the FINE_DP_DEV_GLOBAL_PARAM table in the FineDB database and modify the length of the value field to no more than 255 characters.