Software License States

The following license states are supported by SBC. With version 6.0 these states have been consistently introduced to GNSS and SpiderQC and SBC.

State Explanation Required action Restart possible Config. changes Colour
OK
 The License State is OK. All required licenses are available. None.
Yes
Yes
Disconnected The communication to the license server has been interrupted. The SBC services will continue to run until the end of grace period.

The communication to the license 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 License Server is installed.
  • Check if the License Server is started (either in CLM License Manager, or in Windows services: CLM Remote Daemon (svr)).
  • Check if FLEXnet services are started: FLEXnet License Server, FlexNet Licensing Service (FlexNet Licensing Service 64).

Make sure the License 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 License Server. Check if by disabling the firewall, the connection to the License Server is possible.

SBC service restart is possible.

After each action, please refresh license information, using the button from the License State dialog.

No SBC configuration changes are possible until you resolve the communication issues.
Yes
No
Invalid
 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.

You have enabled an invalid number of features.

Verify the following in order to identify and solve the exceeded count issue:

  • Check if valid licenses are installed on the License Server.
  • Check if one of the licenses has been rehosted.
  • Check if another machine is using one of the licenses.
  • Check if one of the licenses has expired.

Resolve the licensing issue by disabling the required number of user who have subscriptions assigned (subscription owner)

Services restart will lead to SBC stop operating.

After each action, refresh license information, using the Refresh button from the License State dialog.

Configuration changes are possible after resolving the exceeded feature count.
No
No
Invalid
 SBC has entered into invalid state due to missing basic license, or the maintenance date is expired. The connection to the License Server is possible, but no valid license could be found. Configuration changes are not possible.

SBC has entered into invalid state due to:

1. The communication to the license 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 License Server is installed.
  • Check if the License Server is started (either in CLM License Manager, or in Windows services: CLM Remote Daemon (svr)).
  • Check if FLEXnet services are started: FLEXnet License Server, FlexNet Licensing Service (FlexNet Licensing Service 64).

Make sure the License 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 License Server. Check if by disabling the firewall, the connection to the License Server is possible.

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

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

  • Check if the application is connected to the correct machine where the License Server is installed.
  • Check if valid licenses are installed in the License Server.
  • Check if the licenses have been rehosted. Services restart will lead to Spider Suite application stop operating.

After each action, please refresh license information, using the button from the License State dialog.

No SBC configuration changes are possible until the communication issues are resolved.
No
No
Failed
 SBC has entered into failed state due to services restart in case of missing or invalid Spider Web Maintenance Date, or after services restart when the application is in exceeded count state.

At application startup, the maximum count of features is exceeded, or the maintenance date has expired.

Verify the following in order to identify and solve the Failure state of the Spider Suite application:

  • Check if the application is connected to the correct machine where the License Server is installed.
  • Check if valid licenses are installed in the License Server.
  • Check if the licenses have been rehosted.

After each action, please refresh license information, using the button from the License State dialog.

No SBC configuration changes are possible until you resolve the licensing issues.

No
No