key server uses only 12 to 13 who used the license error



All questions related to 1C:Enterprise licenses

#1
People who like this:0Yes/0No
Just came
Rating: 0
Joined: Nov 28, 2014
Company: 1vs.vn

I installed 1c: Enterprise, version 8.3.4.469 and postgres version 9.1.2.
I have installed the apache server to put the database on the website are then

HASP but I downloaded a linkhttp://www.safenet-inc.com/sentineldownloads/?s=&c=all&p=Sentinel+HASP&o=Linux&t=Runtime+%26+Device+Driver­&l=English#

and installed according to the instructions of the installer downloaded fr om the homepage

Sentinel® LDK and Sentinel HASP® RPM Installer Run-time Environment for Linux: Readme
Version 2.5.1

Sentinel® LDK and Sentinel HASP® Run-time Environment RPM Installer for Linux: Readme
Version 2.5.1
November 2014

--------------------------------------------------------------------------------

This document describes installation of the Run-time Environment for Sentinel LDK and Sentinel HASP, using RPM under the supported SUSE or RedHat operating systems. ("Sentinel LDK" is the next generation of the Sentinel HASP system.)

The following topics are discussed:
Operating Systems Supported
Changes in Terminology
Uninstalling the Earlier Run-time Environment
Installing the Run-time Environment
Uninstalling the Run-time Environment
Enhancements in This Release
Issues Resolved in This Release
Known Issues - Run-Time Environment
Upgrading HASP HL Key Firmware
Operating Systems Supported
OpenSUSE 12.3 (x86 and x86_64)
Red Hat EL 5.10, 6.5, 7.0 (x86 and x86_64)
CentOS 6.5 (x86 and x86_64)
The latest service packs and security updates must be installed.

Changes in Terminology
Sentinel Admin Control Center user interface and help files incorporate changes in terminology as follows:

The Sentinel HASP product is now referred to as Sentinel LDK.
SL keys that were created with Sentinel HASP Business Studio now appear in the user interface as "SL-Legacy" keys.
References to Sentinel EMS in the help files are also valid for Sentinel HASP Business Studio.
Uninstalling the Earlier Run-time Environment
An existing instance of the Run-time Environment that was installed using rpm cannot be upgraded. Before installing the new Run-time Environment, enter the following command as root to uninstall the existing Run-time Environment (if present):

rpm -e aksusbd

An existing Run-time Environment that was installed using the Run-time Environment installation script (dinst) does not have to be uninstalled.

Installing the Run-time Environment
Perform the following steps to install the Run-time Environment for Sentinel LDK or Sentinel HASP:

(For x64 distributions) Manually install the 32-bit support libraries (x86 compatibility packages) provided by your Linux distribution.

Note: You can use the script install_32bit_compatibility_package_for_x64.sh to install 32-bit support libraries. You can download this script fr om the Sentinel Customer Community Downloads page. Use chmod to add execute permissions to the script.


Disconnect your Sentinel HL key (if any) from the computer.


Open a terminal window and navigate to the directory containing the downloaded installation file.


As root, enter the command: rpm -i aksusbd-2.4-1.i386.rpm


Reconnect the Sentinel HL key.
Note: At this point, for older HASP HL keys, the firmware on the HL key may be automatically upgraded. During the upgrade process, the key will blink continuously. Do not remove the key while it is blinking. If you remove the key too soon, the key may no longer be visible in Admin Control Center. If the key is not visible, or if the upgrade does not occur, refer to "Upgrading HASP HL Key Firmware" below.

Uninstalling the Run-time Environment
Do the following if you want to uninstall the Run-time Environment:

As root, enter the command: rpm -e aksusbd
Enhancements in This Release
Reference Description
LDK-4468 The template for customizing entries for the Access log in Sentinel License Manager has been enhanced.

A new log element (functionparams2) is available.
Tags for special characters that could not be used in the template until now are provided.
Existing elements (sessioncount, logincount, loginlimit) that did not provide reliable results have been corrected.
The following events are now logged correctly: session timeout, orphaned session logout, manual disconnect, AdminAPI disconnect.
In addition, the template is now used for log entries generated by Embedded License Managers and External License Managers.

For information on the log template, see the Edit Log Parameters screen and related help screen in Admin Control Center. (Click the Edit Log Parameters button from the Configuration - Basic Settings screen.)
LDK-735 Admin Control Center now enables the user to generate a C2V file without the requirement of installing the RUS utility. This is supported for Windows, Mac and Linux platforms. The following limitations apply:

HL Basic keys are not supported.
C2V files fetched from HASP HL and Sentinel HL (HASP Configuration) keys will not work with Business Studio.
The C2V file can be generated for locally-connected Sentinel HL, HASP HL, and SL AdminMode keys.
LDK-5113 Stack usage in Sentinel Licensing API has been optimized. The vendor can use the maximum stack size. Sentinel Licensing API limits its stack usage to the minimum possible.

Issues Resolved in This Release
Reference Description
LDK-7900 The aksusbd daemon would crash when a defective Hardlock key was connected to the platform.

Known Issues - Run-time Environment
Reference Description
140898 Under the Linux operating system, Sentinel License Manager does not support the IPV6 network protocol.

Upgrading HASP HL Key Firmware
The HASP HL Key Firmware has been modified to support future planned security enhancements in Sentinel LDK and Sentinel HASP. Sentinel LDK and Sentinel HASP automatically upgrade the Firmware on HASP HL keys from v.3.21 to the latest version (v.3.25). This occurs:

when a HASP HL key with v.3.21 Firmware is present on a computer wh ere the Run-time Environment is being updated to v.1.14 or later.
when a customer connects a HASP HL key with v.3.21 Firmware to a computer wh ere the Run-time Environment v.1.14 or later has been previously installed.
(You can determine the Firmware version of your HL key by viewing the key on the Sentinel Keys page of the Admin Control Center.)
For HL keys with Firmware earlier than v.3.21, the upgrade does not occur automatically. Customers can upgrade the Firmware to v.3.25 by applying the Firmware Update V2C provided on the Sentinel HASP or Sentinel LDK Installation DVD v.5.0 and later.

During the Firmware upgrade, the relevant key will start to blink. Do not remove the key while it is blinking. If you remove the key too soon, the key may no longer be visible in Admin Control Center.

Note: In the event the key is no longer visible using the Linux Run-time Environment, do the following on a Windows computer:

Install the Run-time Environment using the enclosed installer script.
Connect the HL key.
Run the application FirmwareUpdate.exe, located on the DVD in \Windows\Installed\Redistribute\Firmware Update\.
The HL key is upgraded to v.3.25 Firmware and will now be visible in the Linux Admin Control Center.



Copyright © 2014 SafeNet, Inc. All rights reserved.

DocID 153i Revision 1412-1

key server uses only 12 to 13 who used the license error

 
#2
People who like this:0Yes/0No
Timofey Bugaevsky
Guest

Joined:
Company:

Hello, Lượng Nguyễn Đình!

You need to use HASP driver of version 4.X and license manager of version 8.3X

Try using this command to install it on RPM-based Linux:

Code
#yum install ./hasplm-redhat-8.30-1.i386.rpm

 
#3
People who like this:0Yes/0No
Just came
Rating: 0
Joined: Nov 28, 2014
Company: 1vs.vn

I did install the HASP driver version and license manager 4x version of 8.3X, the same way that original instructions, but the server still only have 12 key clients running normally, the 13 keys to 1C warned not found key clients

 
#4
People who like this:0Yes/0No
Timofey Bugaevsky
Guest

Joined:
Company:

Lượng Nguyễn Đình, USB keys for 1 workplace can not be shared over the network, you should plug them into PCs where users are going to use the application.

 
#5
People who like this:0Yes/0No
Just came
Rating: 0
Joined: Nov 28, 2014
Company: 1vs.vn

I have one computer server with plug 1 key server and 1 key client license 20 machine

 
#6
People who like this:0Yes/0No
Timofey Bugaevsky
Guest

Joined:
Company:

And you can use only for 12-13 client PCs, right?

You can download Aladdin monitor to see how much licenses you have and which PC use them in case of USB dongle licenses.

 
Subscribe