Software License States

Software License States - Overview

The following licence states are supported by SBC. The licence status icon in SBC's top bar reflects the current state by its colour. For more details on required actions for each state, refer to section Software License States | Detailed License State Reference.

Detailed License State Reference

1. OK

• Explanation: The licence state is OK. All required licences are available.

• Required Action: None.

• Restart Possible: Yes

• Config Changes Possible: Yes

2. Disconnected

• Explanation: The communication to the licence server has been interrupted. The SBC services will continue to run until the connection to the Licence Server is re-established — there is no time limit on how long SBC can remain in this state.

• Required Action:

  The communication to the Licence Server has been interrupted. Verify the following in order to identify and solve the disconnect issue:

  • Check if the application is connected to the correct machine where the Licence Server is installed.

  • Check if the License Server CLM version is equal to or higher than the CLM version on the Spider Suite application machine.

  • Check if FLEXnet services are started: FLEXnet License Server, FlexNet Licensing Service (FlexNet Licensing Service 64).

  Make sure the Licence Server host machine is available:

  • Check if the machine is running.

  • Check if the TCP/IP communication is possible. Please contact your IT network specialist.

  • Check if the firewall settings do not block the communication between SBC and the Licence Server. Check if by disabling the firewall, the connection to the Licence Server is possible.

  Spider Suite application restart is possible; SBC remains in Disconnected state after the restart. All pages and the API are read-only until the communication issue is resolved. After each action, please refresh licence information using the button from the Licence State page. No SBC configuration changes are possible until you resolve the communication issues.

  All features that were already in use before the connection was lost stay active. The exception is Real Time Status: if the SBC services are restarted while still disconnected, Real Time Status becomes temporarily unavailable; it becomes available again once the connection is re-established.

• Restart Possible: Yes

• Config Changes Possible: No

3. Invalid (Exceeded Features Count)

• Explanation: One or more counted features are exceeded. SBC will continue to operate unless a restart of the SBC services is done. Configuration changes are not possible.

• Required Action:

  You have enabled an invalid number of features. Verify the following in order to identify and solve the exceeded count issue:

  • Check if valid licences are installed on the Licence Server.

  • Check if one of the licences has been rehosted.

  • Check if another machine is using one of the licences.

  • Check if one of the licences has expired.

  Resolve the licensing issue by disabling the required number of users who have subscriptions assigned (subscription owner), by reducing the number of active X-pos sites, or by deactivating the affected feature (e.g. Usage Reporting or an X-pos service). Services restart will lead to SBC stop operating. After each action, refresh licence information using the Refresh button from the Licence State page. All pages and the API are read-only until the exceeded feature count is resolved.

• Restart Possible: No

• Config Changes Possible: No

4. Invalid (Missing Basic Licence)

• Explanation: SBC has entered into invalid state due to a missing basic licence or the maintenance date being invalid for the installed software version. The connection to the Licence Server is possible, but no valid license could be found. Configuration changes are not possible.

• Required Action:

  The basic licence is missing, or the maintenance date is expired. The connection to the Licence Server is possible, but no valid licence could be found.

  Verify the following in order to identify and solve the invalid licence issue:

  • Check if the application is connected to the correct machine where the Licence Server is installed.

  • Check if valid licences are installed on the Licence Server.

  • Check if the licences have been rehosted.

  Services restart will lead to Spider Suite application stop operating. After each action, please refresh licence information using the button from the Licence State page. All pages and the API are read-only until the licensing issue is resolved.

• Restart Possible: No

• Config Changes Possible: No

5. Failed

• Explanation: SBC has entered into failed state due to a missing or invalid basic licence, or invalid Spider Web Maintenance Date, detected at service start; or after a services restart while the application was in the exceeded count state.

• Required Action:

  At application startup, the maximum count of features is exceeded, or the basic license/maintenance date is invalid. Verify the following in order to identify and solve the Failed state of the Spider Suite application:

  • Check if the application is connected to the correct machine where the Licence Server is installed.

  • Check if valid licences are installed on the License Server.

  • Check if the licences have been rehosted.

  • Check if one of the licences has expired.

  After each action, please refresh licence information using the button from the License State page. No SBC configuration changes are possible until you resolve the licensing issues.

  While in Failed state, the GUI is redirected to the Licence State page and licensed features cannot be used, although the configuration itself is not changed. New rover authentication requests are rejected, and the API returns HTTP 402. Users with access to the License State page are guided to resolve the licensing issue; all other users are informed to contact their service provider.

• Restart Possible: No

• Config Changes Possible: No