StarQuest Technical Documents

StarLicense Troubleshooting

Last Update: 24 December 2019
Product: StarLicense
Version: 1.2 or later
Article ID: SQV00SL007

Abstract

This technical document describes some of the issues that may be encountered when using StarQuest's licensing products.

The following topics are covered:

• Determining if starlicense.dll is in use (Windows clients)
• Multihome Server
• Restricting StarLicense Server to local clients
• Using a non-root user (StarLicense/UNIX server)
• StarSQL for Java Licensing (StarSQL for Java JDBC driver)

Solution

Determining if starlicense.dll is in use (Windows clients)

Changes made with starlic.exe (StarLicense Configuration) on Windows clients do not take affect if starlicense.dll is in use. THe changes will take affect when the process using the DLL ends and the DLL is unloaded.

To check whether starlicense.dll is in use:

1. Download Process Explorer from Microsoft
2. Unpack the zip and run procexp.exe as Administrator
3. Select "Find Handle or DLL.." from the Find menu
4. Enter the string starlicense.dll

If the DLL is in use, the process using it will be displayed. The process may be a service, such as SQDRSVC (StarQuest Data Replicator), Microsoft SQL Server (if you are using a Linked Server with StarSQL), or Oracle (if you are using the Oracle Database Gateway for ODBC with StarSQL).

Multihomed Server

If the system has more than one IP address, make sure that the listener is configured for 0.0.0.0, or configure the listener for a particular IP address and make sure that the client is configured for that same IP address.

Restricting StarLicense Server to local clients

To restrict access to a StarLicense Server to only client applications running on the local system, use the local interface (127.0.0.1) for the listener, the client-server connection, and the Failover listener. This setup can be used on UNIX systems to provide functionality equivalent to node-locked licensing available for Windows. It may be also be used in place of node-locked licensing on Windows when access to the management and logging tools provided by StarLicense Server is desired.

For instance, on UNIX, edit /etc/starlicense.rc:
[ServerListener0]
IP=127.0.0.1
Port=4999

[ClientServer0]
ProdID=SQ
IP=127.0.0.1
Port=4999
Pri=1

[Global]
PrimaryFailoverListenIP=127.0.0.1