Registration FAQ

When registering, the registration time, the number of data connections, the number of concurrent users, and the number of users will be limited. If the limit value is reached, an error or abnormal state will occur.

If the current system is registered, the super administrator can log in to the data decision system and access http://IP:port/webroot/decision/v10/register/info/license under the current page to view the limit value during registration. As shown below:

• If the number of data connections reaches the limit, the data connection cannot be added, and the newly added data connection will not be displayed.

• If the concurrent number reaches the limit, the IP address that logs in later will not be able to log in.

• If the registration is permanent, the expiration time is 100 years later. After 100 years expired, please contact FanRuan Business for free registration.

• If the server hardware is replaced, the machine code may be changed and the registration will be invalid.

• If the FineBI project name is changed, the project name will be inconsistent and the registration will be invalid.

• If the number of users reaches the limit, users will not be able to be added, and the newly added user will report the error "Conflict with other administrator operations, please refresh and try again".

• If the number of distributed nodes reaches the limit, new nodes will not be added, and the newly added nodes will not be displayed.

If you find that some functions are unavailable when using FineBI, you will directly report an error or cannot be opened.

A similar error occurred: You used an unregistered function or java.lang.NullPointException null pointer exception .

Note: For the impact of function points, please refer to: Registration Management

This is due to some feature points not being purchased at the time of registration. In "Decision-making System > Manage > Registration > Function List", you can view the registered function points, as shown in the following figure:

If you want to add some function points, please contact Fanruan Business, business email: business@fanruan.com

When upgrading the version, the user will worry about whether the original authorization file is available after the upgraded version.

1) Major version upgrades have an impact

Upgrading across major versions, such as upgrading from 4.1 to 5.1, will affect the authorization file and require re-registration or migration of authorization.

2) Small version upgrade has no effect

Upgrades between minor versions, such as from 5.1.5 to 5.1.6, have no effect on the authorization file.

The MAC address must be the MAC address of the server. For multi-NIC servers, you can choose any MAC address.

The MAC address format of Linux or Unix systems is different from the general MAC address format, such as 0*001F296EFD64.

When the server has both the license authorization file and the encryption lock, the license authorization file is the main one.

Because the server will read the license authorization file first, and the dongle will be read only if the authorization file does not exist, so the MAC address registration has a higher priority than the encryption lock registration.

After using the new license file, the designer preview diagram shows blank?

Because the obtained FanRuan.lic file is placed in the %FineBI-HOME%\webroot\WEB-INF\resources directory of the report project, and the Web server is not restarted, the chart cannot be previewed.

Therefore, to use the license file, the Web server must be restarted for the license to take effect.

When previewing a template under a registered application, it is prompted that registration is required.

• Reason 1: The server where the application is located has been changed, and the mac address of the server where the current application is located is different from the mac address at the time of registration.

• Reason 2: The report application has been upgraded, and re-registration is required to upgrade across major versions.

On the same server, FR and BI projects are deployed at the same time, and the license authorization is uploaded successively. When the license authorization is uploaded in the latter project, an error is reported indicating that the certificate has been used by other projects on the same server 

Check whether the previous license authorization was uploaded incorrectly. For example, upload the BI authorization to FR. If so, cancel the previously uploaded authorization and then upload it in the correct corresponding order. For cancellation of authorization, please refer to: Chapter 3 of Local Machine Information Authentication .