SafeNet Sentinel, Руководство разработчика

Страница: 247 / 282

Problems and Solutions
Sentinel Hardware Keys Developer’s Guide 229
■
This error could occur when the network is busy. To overcome this
error, you should re-try by calling the API function again. If the
customers are facing this error, recommend that they launch the
application again.
■
This error may also occur when the server port is already in-use. You
can verify this in the system EventLog or the Sentinel Keys Server
error log file. To troubleshoot this, you can set a non-busy port in the
server-side configuration file to run the Sentinel Keys Server. Make
sure that the same port is set in the client-side configuration file.
Problem: The application receives a
SP_ERR_PROTOCOL_NOT_INSTALLED error
The application receives a SP_ERR_PROTOCOL_NOT_INSTALLED error.
Solution:
This error is encountered when the protocol used for communication is not
installed on the client system. You can modify the protocol in the client-side
configuration file.
Note: Only TCP/IP is supported on Linux and Macintosh.
Problem: The Configuration File settings were not
applied
The Configuration File settings were not applied.
Solution:
■
The client-side configuration file must be present in the directory
where your application's executable resides. The server-side
configuration file must be present in the directory where the Sentinel
Keys Server is installed. The parameter settings will not be applied if
the file is moved to any other location.