Introduction
The steps detailed below can be used to fault find on issues where the following products cannot utilise network licences hosted on the Sentinel Server:
- S3GRAF, including S3GRAF3D, S3GRAFHPG and S3GRAFLE
- S3control, including S3optima
- S3schedule
- S3sector
- S3chembuild
- S3quickbuild
- Meteo
Although these applications differ in their usage, they access the Sentinel server using the same method.
Application Checks
Ensure each application has the appropriate Sentinel Server entered in the ''Contact Server List field'. The following images demonstrate the required settings. These are accessible from the Licence unavailable dialogs
S3GRAF
If there is an issue accessing the Sentinel Server from an installation of S3GRAF, the following dialog will be displayed:
In this case, to check the Sentinel Server name entered, select the Licence Button to display:
Followed by the Network button to display:
Ensure the Sentinel Server name entered in the 'Contact Server List' field matches the Sentinel Server name.
In addition ensure the 'Override Standalone Licence' check box is selected.
Any changes here require to be applied by clicking on OK and relaunching the application.
S3control
If there is an issue accessing the Sentinel Server from an installation of S3control, the following dialog will be displayed:
In this case, to check the Sentinel Server name entered, select the Licence Button to display:
Followed by the Network tab to display:
Ensure the Sentinel Server name entered in the 'Contact Server List' field matches the Sentinel Server name.
In addition ensure the 'Override Standalone Licence' check box is selected.
Any changes here require to be applied by clicking on OK and relaunching the application.
Note this dialog will also display the licence for S3match.
S3schedule
If there is an issue accessing the Sentinel Server from an installation of S3schedule, the following dialog will be displayed:
In this case, to check the Sentinel Server name entered, select the Licence Button to display:
Followed by the Network tab to display:
Ensure the Sentinel Server name entered in the 'Contact Server List' field matches the Sentinel Server name.
In addition ensure the 'Override Standalone Licence' check box is selected.
Any changes here require to be applied by clicking on OK and relaunching the application.
S3sector
If there is an issue accessing the Sentinel Server from an installation of S3sector, the following dialog will be displayed:
In this case, to check the Sentinel Server name entered, select the Licence Button to display:
Followed by the Network button to display:
Ensure the Sentinel Server name entered in the 'Contact Server List' field matches the Sentinel Server name.
In addition ensure the 'Override Standalone Licence' check box is selected.
Any changes here require to be applied by clicking on OK and relaunching the application.
Sentinel Server Checks
On the hardware running the Sentinel RMS Licence Manager software, check the following items:
- Ensure the application licences are installed on the Sentinel Server using the WlmAdmin application as detailed here:
- What version of the Sentinel Server is running? This can be found on the WlmAdmin on the right side. For example:
- Using the Services.msc, check the Sentinel 'RMS License Manager'service is Started:
- Restart the Sentinel RMS License Manager service.
- Check the Sentinel LM service is not running if it is there. This service uses the same executable as the Sentinel RMS License Manager service.
Note: Licenses from different vendors should work on the same lservnt.exe, providing the version of these licenses are not greater than the version of lservnt.exe - Are other workstations available to access the Application network licences?
Workstation Checks
The following checks can be made on the workstation:
- Can you launch a Command prompt and enter ping <sentinelservername> (note <sentinelservername> enter your Sentinel Server name here) at the prompt. For example:
A response similar to the RH-LEWIS entry above, should be displayed.
Can you confirm the IP address matches the IP address displayed on the Wechoid?
Can you ping the IP address of the Sentinel Server?
Can you ping the full hierarchical name? - Can you check the following article in our Support portal with regard to Firewall settings:
Firewall-Rules
To allow communication between our applications and the Sentinel Server, UDP port 5093 requires to be open on both the client and server. Although this is a standard port, it may be blocked in your infrastructure for IT security reasons.
Is it possible to temporarily disable the Firewall or AntiVirus software to test connectivity? - Copy the Wlmadmin application to the workstation and launch it. Enter the Sentinel server details in the ‘Defined Servers’ field (under Edit in the drop down menu). Can you access the Sentinel server from the workstation using the Wlmadmin?
- Create an Environment Variable called LSFORCE and give it the value of the sentinel server (suggest usage of the full hierarchical name here). Reboot the workstation and try launching the application?
- In addition to the above, the ping –l 1500 <machine – name> can be used to test for MTU issues. The MTU should be set at 1474 or above by default. The following should be entered at a command prompt to display the current Local Area Network interface.
- Is a VPN client being used? We have found issues where VPN clients set the MTU at less than the 1474 required by Sentinel. To test this try the following command when connected over VPN:
ping -l 1500 <Sentinel server name>
For example: - To check the MTU settings, enter the following:
netsh interface ipv4 show subinterface
as demonstrated on the above image. - Is it possible to change this MTU value to say 1500?
The following command should allow this to be changed:
netsh interface ipv4 set subinterface “Local Area Connection” mtu=1500 store=persistent. - The IPCONFIG /FLUSHDNS command can be used to clear the DNS settings from the workstation. Please contact your local IT for further details on this procedure.
- Is it possible to log onto the workstation with an account that has local administrative access, then navigate to the application installation path using a Command Prompt? the lsinit<application>.exe should be run. Note nothing will appear to have happened, but files are registered in the background.
Additional Application
Download the Slmdemo 8.4 folder from the ftptransfer site login provided earlier and place this on the workstation. SLMDEMO tests the communication between the workstation and the Sentinel server.
Please follow these steps to use this tool:
- Launch the tool and click on the ‘Connect To’ menu item. Enter the Sentinel server full hierarchical name, < sentinelserver.domain>, and press enter.
- Enter Application (in this case S3GRAF) in the ‘Feature’ field and 2019 (for example) in the ‘Version’ field:
When using this Slmdemo the most recent Feature names and Versions are:
This list is dependent on the products installed in the local infrastructure.Product Available Features Version S3GRAF S3GRAF, S3GRAF3D, S3GRAFHPG, S3GRAFLE 2019 S3control S3control, s3optima 2019 S3sector S3sector 7.1 S3schedule S3schedule 2019 S3chembuild S3chembuild 2019 S3quickbuild quickbuildSECTOR, quickbuildBUILDER, quickbuildALLExport 2019 Meteor Meteor. MeteorEngine 2019
Note the Available Features are case sensitive. - Press ‘Get Licence’. If this is successful, the entry ‘call returned a success..’ will be seen in the ‘API Call History’ box and the ‘Release History’ button will become active:
- Click on ‘Release Licence’:
- What alert is being displayed for your system?
This can be repeated for each application
Note:
- The SLMDEMO application can be run on the system running the Sentinel server as well as the workstations that will be using our applications
- There is a know issue when running SLMDEMO on windows 10 operating systems as per the following Microsoft Article: https://support.microsoft.com/en-in/help/4054150/issues-when-windows-10-calls-createwindowex-for-s