It is well known that a license is required to work in 1C. 1C supplies various protection keys: local and network. A local key can be used only on one computer, having the appearance of a familiar flash drive.
Network keys can provide licenses for multiple users depending on their series. At large enterprises, keys for 300 and 500 connections are most often used, but if necessary, you can purchase fewer. Please note that one computer cannot have more than one key of the same series.
In this article, we will look step by step at how to configure the 1C 8.3 license manager so that the network protection key is on one computer. Users from other computers will receive licenses from him. Simply put, there is only one key, and user sessions a bunch of.
Setting up a HASP license manager
Let's start by installing a license manager on the computer that will distribute licenses. In what follows we will call this computer license server. All required software is included in the 1C:Enterprise package.
You can download Alladin HASP License Manager for Windows x64 and x32 from the link.
For the manager to work properly, you need to make some preliminary settings. The file where you will produce them is called nhsrv.ini. Most often it can be found at "C:\Program Files\Aladdin\HASP LM" if the license manager is installed as an application. Otherwise (installed as a service) it will be in the operating system's system directory.
Open the file you found in any text editor, for example, in notepad and add the line there:
NHS_IP_LIMIT = 192.168.*.*
Instead of asterisks, you can enter any number from 0 to 254. Also, if you leave the “*” signs, this will mean that the licenses will be “seen” by all computers on the network whose address begins with 192.168.
For example, if you have the NHS_IP_LIMIT = 192.168.1.* add-on specified in the nhsrv.ini file, then licenses will only be available to computers with an IP in the range from 192.168.1.0 to 192.168.1.254.
Settings on client PCs
After you have done everything necessary settings on the 1C license server, you need to configure the client computers themselves.
When running 1C on a user's PC, the program makes a request for a license to the address specified in the nethasp.ini file. You can find it in the “conf” folder of the directory where the 1C platform is installed. In our case, the address is as follows: “d:\Program Files (x86)\1cv8\conf\”.
Without any additional settings, the 1C program will search for licenses throughout local network. To speed up this process we can independently specify the IP address of the license server in this file by adding the text highlighted in the figure below.
In the organization where I work, everything software licensed, incl. and 1C. Therefore, every time you install 1C, you need to install the protection driver in order for the program to start.
Once they asked me to install the platform on a laptop. I took the distribution kit and went to install the program. The installation went quickly as usual, after which I clicked the “Install protection driver” menu item. An installer information window with the installation progress status appeared on the screen. After waiting a couple of seconds, the installer displays a message that the driver could not be installed:
Failed start the Aladdin Device Driver.
Failed to start a service in the Service Control Manager Database 0x2008007 0x0.
I forgot to say that the laptop has Windows XP SP2. My further installation attempts
drivers led to the same result. I tried rebooting the laptop, logging in as an administrator, and directly copying the driver files to the disk - all to no avail.
I decided to download the Hasp driver from its native site, that is, from www.aladdin.com (there is also a Russian site www.aladdin.ru). I downloaded it, started the installation... I'm waiting... Hurray! Installed! I'm launching 1C... waiting... We've arrived! "The security key was not found!"
What to do? After all, everything should work. Maybe the network? I check the connection with the server where the license manager is located - everything is fine. Strange... I return to the Aladdin website, download diagnostic utilities that scan the network for the presence of Hasp's, check - the key is visible on the network. I try to change the settings of the Nethasp.ini driver initialization file, where I specify the IP address, port and sending method packages didn't help either. There was only one option left - yandex, rambler, google.
After a short search, I open another link and see a description of my situation. Fortunately, in addition to describing the problem, there was also a hint on how to solve it. So, the fact is that this situation may occur on some computers with Windows XP Service Pack 2.
Let's just say that the problem is solved "in two moves." Find the boot.ini file in boot disk(usually drive C, we MUST do it backup copy. Then remove the “read-only” and “hidden” attribute, open it, add a line that looks something like this:
multi(0)disk(0)rdisk(0)partition(1)\WINXP="Windows XP RU" /fastdetect /NoExecute=OptIn
Replace the parameters /fastdetect /NoExecute=OptIn in this line with /fastdetect /Execute=OptIn
/noguiboot /NOPAE, resulting in a line that looks something like this:
multi(0)disk(0)rdisk(0)partition(1)\WINXP="Windows XP RU" /fastdetect /Execute=OptIn
/noguiboot/NOPAE
This means that the system will boot without the driver signature verification service.
I reboot the system with the changed parameters, install the driver again - everything is fine, it’s installed! RESTORED the boot.ini file to the initial state, rebooted the laptop, started 1C - again “The security key was not detected!”.
I return to Yandex, Rambler, Google. I find something similar again. They advise changing some parameters of the Nethasp.ini file. Namely, set NH_USE_BROADCAST to Disabled, which means disabling broadcast messages. I did as recommended, launched 1C... HERE IT IS! FINALLY! WORKS!
This is how a whole day (!) was spent on installing 1C, which usually takes
maximum 20 minutes.
17.02.13 — 19:18
Good evening. This is the problem: there are 2 computers, each of which has network keys installed for 5 users. Hasp LM is installed on one of them as a service, and Alladin Monitor is also installed on this computer. Well, this Alladin Monitor shows only the keys of the computer on which it is installed, it does not see the keys of another computer. Why?
P.S. The computers, of course, are on the same local network.
1 — 17.02.13 — 19:20
hasp ini configured?
2 — 17.02.13 — 19:21
(1) Yes, it shows the IP addresses of these 2 computers.
3 — 17.02.13 — 20:25
How is HASP LM installed on the second computer?
4 — 17.02.13 — 20:36
http://safenet-sentinel.ru/helpdesk/faq/
5 — 17.02.13 — 20:39
(4) “The monitor itself can only show the presence of a license manager at a particular address. He will be able to see the key only after the protected application successfully opens at least one session with the key.”
Those. It turns out that in order for this key to be displayed in the Aladdin monitor, you must first use all the licenses of the local computer.
6 — 17.02.13 — 20:41
(3) the license manager is not installed on the second computer.
7 — 17.02.13 — 20:46
(6) Well, put it like that.
8 — 17.02.13 — 20:52
(7) Why is it even needed on the 2nd computer? As far as I remember, one license manager is enough for one local network, please correct me if I'm wrong.
9 — 17.02.13 — 20:55
(8)[one license manager is enough for one local network]
Aladdin doesn't think so
10 — 18.02.13 — 09:43
(7) Installed, no changes.
By the way, here’s a question: the license manager installed it as a service, I go to “Services” and I can’t find it there. Why? What is it called?
11 — 18.02.13 — 13:02
(10) Sentinel HASP License Manager.
In nethasp.ini, which is in the folder for the monitor, specify the addresses of these computers. Two license managers should appear in the monitor.
12 — 18.02.13 — 13:22
(11) Strange, this service (Sentinel HASP License Manager) is not in the list of Windows services.
I edited nethasp.ini in the monitor folder - it didn’t help.
13 — 18.02.13 — 13:57
That's it, I won: it turns out I had to restart the computer where the license manager is located, after that everything worked.
ATTENTION! Ctrl-F5 or Ctrl-R
The topic has not been updated for a long time and has been marked as archived. Adding messages is not possible.
2000
Human.
11.01.11 — 13:16
Tell me where I can download the driver for the Hasp key for 1c8.1 for Windows 7 (64x).
Aladdin's website only has:
HASP4 driver. Utility for installing the HASP4 program protection key driver under Win32/Win64 (Windows 95/98/ME/NT4/2000/XP/Vista/2003, Windows XP/2003 x64)
-HASP4 driver. Utility for installing the HASP4 program protection key driver under Win32/Win64 (Windows 98/ME/NT4/2000/XP/Vista/2003, Windows Server 2008, Windows XP/Vista/2003/2008 x64).
-HASP key driver for Linux
And Win7 complains that it is not supported by this OS. (everything is fine with the rights in Windows)
1 — 11.01.11 — 13:23
http://www.aladdin-rd.ru/support/faq/634/#faq27952
2 — 11.01.11 — 13:41
Cheers thanks!
HASP4 - cursed that it was not supported by the OS
HASP HL and HASP SRM - working
3 — 14.01.11 — 22:00
(2) 1C 8.2 Windows 7 x64 Home Basic
The 1C network key for 5 licenses did not work over the network.
Aladdin monitor shows that this computer has a HASP License Manager version 8.320
What to do next? where can I watch which versions?
Firewall turned off.
4 — 15.01.11 — 00:59
where is the key inserted? Install HASP License Manager there
5 — 15.01.11 — 01:15
Locally, the “Use hardware license (protection key)” flag works. If you remove the flag, it doesn't work.
And it shouldn't. This flag is responsible for obtaining a license through the server. The order of searching for a key is: first the local key, then the network key, then on the server. Therefore, network operation needs to be checked with another computer.
6 — 15.01.11 — 01:21
(0) why download?
7 — 15.01.11 — 10:56
Windows 7 x64 won 😉 It probably helped to read the instructions HASP_License_Manager\135-Install_LM_Under_Windows_7.pdf from the file HASP_LM_setup.zip Or in Russian there:
http://www.aladdin-rd.ru/support/faq/29188?print=Y&ID=29188
Drivers and software downloaded there:
http://www3.safenet-inc.com/support/hasp/enduser.aspx#latestDD
Sentinel_HASP_Run-time_ setup.zip
HASP_LM_setup.zip
(4) At first, I was frightened by the absence of the corresponding service at my usual place.
HASP License Manager - hardware license manager for 1C
it turned out to be under a different name “Sentinel HASP License Manager”
(5) if you connect to a computer on which the network key is installed via RDP, then 1C can access the local network via the network and this can be seen in Aladdin Monitor.
If through Remote Admin or TeamViever, then using only one computer it was not possible to check the operation of the key over the network 😉
(6) Do the key drivers included with the latest 1C 8.2 platform work everywhere? It seems that they can be installed on any Win OS. But if before this the drivers from Sentinel_HASP_Run-time_ setup.zip were installed, the system curses - “replace with an older one...?”
Get your work in order using the 1C configuration "IT Department Management 8"
ATTENTION!
If you have lost the message input window, click Ctrl-F5 or Ctrl-R or the "Refresh" button in the browser.
The thread has been archived. Adding messages is not possible.
But you can create a new thread and they will definitely answer you!
Every hour on the Magic Forum there are more 2000
Human.
1C 8.3 Linux X64 Hasp Key Emulator Average ratng: 3.9/5 3687votes
Installation 1. With Enterprise 8. Cent. OS 6. 3. How to install 1.
Aladdin
Aladdin
- Categories:Sega
- Review prepared by: Liza
- Application rating: 3.08 points
- Update date: 04/23/2016
Aladdin– this is an opportunity to replay your favorite game, which is practically no different from the original and has received a quick save function.
Its plot is the plot of a cartoon released in 1992, the story of what feats and battles Aladdin had to undertake to prevent Jafar from taking his place on the throne. And, as in the cartoon, Ginny, Gin’s faithful friend and comrade, will become his assistant in this difficult task. But he also has another goal - this is the heart of the beautiful Jasmine, and the battle for it will not be much easier.
Each level of this game is a new location and new characters, which are based on scenes from the cartoon with numerous enemies and traps.
Why doesn't Aladdin Monitor see the key?
Sometimes these are guards armed with curved sabers, which your hero can pelt with throwing apples or use the same sharp saber against them.
The game Aladdin was very popular on Sega and now all its heroes have received a second life and will be able to fight each other again. They are all very lively and cheerful, constantly taking risks and ready to do anything to cheer and please you. Everything that happens on the screen looks exactly like a cartoon, and the main character is an exact copy of his cartoon prototype. That is why there are so many children among the players.
Download the Aladdin game for Sega on Android. Perhaps, with your help, its main character will be able to quickly achieve his goal: he will fall in love with Jasmine and defeat his worst enemy Jafar.
The article is a copy of the blog! If you have any questions, see the link at the end..
I came across this problem the other day. One of the machines refused to work network version 1C Enterprise. When connecting to the database, the following error occurred:
I would like to point out that the error appeared on a computer that had 2 network cards with 2 different networks. For some reason the meanings immediately at this moment didn't give it. Apparently, because the HASP monitor detected these keys perfectly, which is why I looked for the problem in 1C. As a result, I lost half a day of working time. The problem really lay in two network cards, or to be more precise, 2 different networks, the solution was in the file
C:\Program Files\1cv81\bin\conf\nethasp.ini
Having disconnected the network in which there are no HASP keys, after rebooting the machine - 1C started up.... I went to Google to find a solution to this problem. The search did not take long, the solution was as follows:
I'll start with a small educational program:
1C:Enterprise 8 uses a protection system using HASP hardware keys; you can download the driver, monitoring program and HASP Loader service on the website http://www.aladdin-rd.ru/, and specifically in the support section http://www.aladdin -rd.ru/support/downloads/hasp/. Protection keys for 1C are divided into: Single-user key 1C1. Single-user (must be physically connected to the computer running 1C)
model HASP HL Basic (blue), this key is marked H4 M1 ORGL8, does not have built-in memory and personal ID, does not store any parameters and settings. Supplied with products licensed for one workplace. Multi-user key 1C
HASP network key
Download Center
Multi-user (the key is on the network, 1C can be launched on any computer within the local network or domain)
Network client keys include the HASP HL Net series (red). They have an internal memory that stores the number of licenses and a unique ID. There are varieties for 5, 10, 20, 50 and 100 users. It is marked NETXX ORGL8, where ХX is the number of licenses (for example NET5 ORGL8). There are also keys for 300 and 500 users that are labeled NET250+ ORG8A and NET250+ ORG8B. Supplied with products licensed for 5 workstations, as well as separately, in the form of additional client licenses. HASP server key
Key for Server 1C
3. Server (must be physically connected locally to the computer on which the 1C Enterprise agent server is installed and running)
Keys for the 1C Enterprise server are only local. The 32-bit version has a HASP HL Pro protection key ( purple), which has internal memory and a unique ID. It is marked ENSR8 and comes with a license for the 1C Enterprise server.
For a 64-bit server, a HASP HL Max key (green) is used with internal memory and a unique ID. It is marked EN8SA and also supports a 32-bit server. Those. Having a license for a 64-bit server, you can use the 32-bit version without changing the key, but not vice versa.
For the single-user and server key to work, it is enough to install the protection key driver on the local machine and insert the protection key into the local machine USB port.
For a multi-user (network) security key, you must: 1. Install the security key driver on one of the machines on the network, which will serve as the key server - HASP4_driver_setup.zip 2. Install the security key server (service) on the same machine - HASP_LM_setup.zip 3. Insert the security key into the server into USB port 4. Install 1C on client machines
In general, these actions are sufficient for 1C to work. During the launch and further operation of 1C:Enterprise 8 on local machines, the system will contact using a broadcast request on port 475 and look for the protection key. If the search is unsuccessful, the message “program protection key not found” will be displayed and 1C:Enterprise will be interrupted.
If you encounter the message “the program’s protection key was not found,” you need to check: 1. the presence of the protection key in usb port key server 2. check whether the key server is running on the server (process named “Hasp loader”) 3. check telnet command accessibility of the key server from the local machine via port 475 (for example: telnet 192.168.100.100 475)
If all checks were successful, but the error remains, move on to more detailed settings. In the 1C:Enterprise 8 installation folder (usually c:\program files\1cv81\bin\conf or c:\program files\1cv8\bin\) there is a nethasp.ini file. This is a security key configuration file, it is divided into sections, we are interested in the section. When installing 1C, by default, in this section all parameters are separated by double signs “;”, which means that these settings are ignored. In this case, the key driver behaves as follows: 1. a broadcast type packet is sent over the local network on port 475 in search of a security key server 2. if no response is received, an error occurs
Disadvantages of the default configuration: 1. broadcast takes some time 2. not all servers respond to such packets 3. broadcast is of some kind, but the load on the network
To solve this problem, you need to do the following: 1. specify the specific address where to look for the key server (for example: NH_SERVER_ADDR = 192.168.100.100) 2. disable broadcast search (NH_USE_BROADCAST = Disabled) 3. and limit the types of packets to the TCP protocol only (NH_TCPIP_METHOD = TCP )
As practice shows, the launch speed of 1C:Enterprise 8 after such a setup increases noticeably!
But there are some disadvantages of this method:
You must ensure that the address of the security key server does not change, otherwise you will have to reconfigure the nethasp.ini file on all local machines!
I would also like to clarify a few points about working with keys that I encountered while working: 1. Monitor HASP does not show the key
The monitor itself can only show the presence of a license manager at a particular address. He will be able to see the key only after the protected application has successfully opened at least one session with the key. In addition, it should be taken into account that Aladdin Monitor only works over the UDP protocol, port 475. Thus, the absence of data about the key in the monitor does not mean that the key is not available to the application. 2. Two 1C HASP protection keys on one computer
When installing two or more HASP software protection keys on one computer, please note that:
Keys with different series will work fine. (in relation to 1C: 1 server and 1 network will work normally) Keys of the same series will work if such a feature was implemented by the developer of the secure software.
If the developer this opportunity was not implemented, then keys belonging to the same series will not work together on one computer, only one of them will be visible: either the one closest to the port (in the case of LPT keys), or located on the port with a low address (in the case of with USB keys for protecting HASP programs). (in relation to 1C, - 2 local or 2 network keys on one computer most likely will not work correctly) it is not recommended to put a local and network key together, this is due to the security feature of 1C Enterprise: when finding a local key, the program will never look for a network one .
Possible solutions to this problem:
Replacing several HASP program protection keys with one, with a larger number of licenses (this is well written here: http://v8.1c.ru/predpriyatie/questions_licence.htm). Installing protection keys on different computers, followed by installing and configuring license managers for each key.
3. Two or more license managers (License Manager) on the network
If you have two or more network keys, it is not always enough to separate them different computers. License managers must be configured. Each license manager must have a unique name, which must be explicitly communicated to the protected program. It is recommended to perform a similar setup if you are using a terminal server, even with the same network key.
On the machine where the key is installed, find the nhsrv.ini file in the folder with the license manager. The NHS_SERVERNAMES parameter is responsible for the name of the license server; it can consist of Latin letters and numbers and contain no more than 7 characters.
NHS_SERVERNAMES = NAME1
After which, on client machines, it is advisable to edit the nethasp.ini file, explicitly specifying the addresses and names of license managers:
NH_TCPIP = Enabled NH_SERVER_ADDR = 192.168.0.10, 192.168.0.11 NH_SERVER_NAME = NAME1, NAME2
Well, I think I’ve described all the nuances, if I remember anything, I’ll definitely add it! Bye everyone!
1C does not see Hasp.
In the organization where I work, all software is licensed, incl. and 1C. Therefore, every time you install 1C, you need to install the protection driver in order for the program to start.
Once they asked me to install the platform on a laptop. I took the distribution kit and went to install the program. The installation went quickly as usual, after which I clicked the "Install protection driver" menu item. An installer information window with the installation progress status appeared on the screen. After waiting a couple of seconds, the installer displays a message that the driver could not be installed:
Failed start the Aladdin Device Driver.
Failed to start a service in the Service Control Manager Database 0x2008007 0x0.
I forgot to say that the laptop has Windows XP SP2. My further attempts to install the driver led to the same result. I tried rebooting the laptop, logging in as an administrator, and directly copying the driver files to the disk - all to no avail.
I decided to download the Hasp driver from its native site, that is, from www.aladdin.com (there is also a Russian site www.aladdin.ru). I downloaded it, started the installation... I'm waiting... Hurray! Installed! I'm launching 1C... waiting... We've arrived! "The security key was not found!"
What to do? After all, everything should work. Maybe the network? I check the connection with the server where the license manager is located - everything is fine. Strange... I return to the Aladdin website, download diagnostic utilities that scan the network for the presence of Hasp's, check - the key is visible on the network. I try to change the settings of the Nethasp.ini driver initialization file, where I specify the IP address, port and sending method packages didn't help either. There was only one option left - yandex, rambler, google.
After a short search, I open another link and see a description of my situation. Fortunately, in addition to describing the problem, there was also a hint on how to solve it. So, the fact is that this situation may occur on some computers with Windows XP Service Pack 2.
Let's just say that the problem is solved "in two moves." We find the boot.ini file in the boot disk (usually the C: drive), and ALWAYS make a backup copy of it. Then remove the “read-only” and “hidden” attribute, open it, add a line that looks something like this:
multi(0)disk(0)rdisk(0)partition(1)\WINXP="Windows XP RU" /fastdetect /NoExecute=OptIn
We replace the parameters /fastdetect /NoExecute=OptIn in this line with /fastdetect /Execute=OptIn /noguiboot /NOPAE, as a result of which the line will look something like this:
multi(0)disk(0)rdisk(0)partition(1)\WINXP="Windows XP RU" /fastdetect /Execute=OptIn /noguiboot /NOPAE
This means that the system will boot without the driver signature verification service.
I reboot the system with the changed parameters, install the driver again - everything is fine, it’s installed! I RESTORED the boot.ini file to its original state, rebooted the laptop, started 1C - again “The security key was not detected!”.
I return to Yandex, Rambler, Google. I find something similar again. They advise changing some parameters of the Nethasp.ini file. Namely, set NH_USE_BROADCAST to Disabled, which means disabling broadcast messages. I did as recommended, launched 1C... HERE IT IS! FINALLY! WORKS!
This is how a whole day (!) was spent on installing 1C, which usually takes a maximum of 20 minutes.
Software products“1C:Enterprise” version 8 can also be protected from copying by hardware LPT or USB keys such as HASP4 Net from Aladdin. This article provides information about the type, marking and purpose of various HASP4 Net keys from 1C:Enterprise. As well as an overview of software products from Aladdin, which are used for installing, configuring and administering these keys (for Windows operating systems).
1. Marking and assignment of keys
All HASP4 Net keys can be divided into 2 types: “Client” and “Server”:
The purpose of a specific key can be determined by its blossom And labeling. In the pictures below, the key marking is highlighted with a frame. The remaining characters on the key have no special meaning for program users. 
The type and purpose of the key by marking can be determined from the table below:
| Type/color | Marking/series | Purpose |
|---|---|---|
| SINGLE USER VERSIONS OF BASIC DELIVERY AND CLIENT KEYS | ||
| H4 M1 ORGL8 |
|
|
| NETWORK VERSIONS OF MAIN DELIVERY AND MULTI USER KEYS | ||
| H4 NET5 ORGL8 |
|
|
| H4 NET5 ORGL8 |
|
|
| H4 NET10 ORGL8 |
|
|
| H4 NET20 ORGL8 |
|
|
| H4 NET50 ORGL8 |
|
|
| H4 NET100 ORGL8 |
|
|
| NET250+ ORG8A |
|
|
| NET250+ ORG8B |
|
|
| KEYS TO SERVER 1C:ENTERPRISE 8.* | ||
| H4 M1 ENSR8 |
|
|
| Max EN8SA |
|
|
| KITS | ||
|
||
|
||
|
||
The size of USB keys may differ from the size of the keys shown in the pictures. Software products of the 1C:Enterprise system produced before 2009 were equipped with USB keys in a longer form factor - 52 mm. The color scheme and markings of the keys remain unchanged.
2. What you need to know when installing keys
There are a few things to consider before installing HASP keys, namely:
- The total number of users who can work with the 1C:Enterprise system is equal to the sum of licenses available in each of the client keys.
- Two or more keys of the same cannot work on one physical computer Series, because these keys are indistinguishable and only one of them (chosen at random) will actually be used. The key series can be determined by the last 5 characters in the marking (ORGL8, ORGL8A, ENSR8, etc.). Keys of different series can be installed on one computer without any problems.
- Client keys can be installed on any computer on the network (if the HASP License Manager is running).
- If there are several keys, licenses are issued in the following order:
- in ORGL8 series key
- in ORGL8A series key
- in ORGL8B series key
- Also valid “remembering the key”, i.e. when accessing again, an attempt will first be made to obtain a license from the key whose license was received by the user during the last connection.
- The server key must be installed directly on the same computer that is used as the cluster server "1C:Enterprise". It will not work over the network.
- Server 64-bit keys can also be used on 32-bit systems.
- There are certain problems with forwarding a server key from a physical environment to a virtual one on some hypervisors. For example, I never managed regular means forward the server key to virtual machine V .
- A COM connection also requires a license.
- Web services do not require client licenses to operate.
- Full algorithm for searching for a license when starting “1C:Enterprise” for the version 8.3 described, for version 8.2 — .
3. Features of accounting for client licenses
When launched, the 1C:Enterprise client can use to obtain licenses:
- Local key— a key installed on the physical computer from which 1C:Enterprise is launched. Gives the right to launch on a computer with a key from one Windows session an arbitrary number of system instances in 1C:Enterprise or Configurator mode. When working in terminal mode, allows only one user to work, who has connected to the terminal session with ID 0.
- Multi-user key accessible over the network via HASP License Manager— Ensures simultaneous operation of as many computers as there are users with a key. Similar to a local key, on one computer in one Windows session, it is possible to launch an arbitrary number of system instances in any mode within the framework of one license. When working in terminal mode, installation of the HASP License Manager is also required.
- 1C:Enterprise server or web server extension module— In addition to the HASP License Manager program, licenses can also be issued by the 1C:Enterprise server or a web server extension module (only when working with file database via Web client). In this case, the calculation of licenses is carried out directly by the 1C:Enterprise server or the web server extension module. In this case, unlike the two previous options, licenses are consumed on the basis of “one session - one license”. Thus, if two instances of 1C:Enterprise are running on one computer, then two licenses will be consumed.
Besides it is very important to know and take into account the following feature: if several multi-user client keys of the ORGL8 series are detected on the network, then the server will select one arbitrary key. After the licenses for this key have been exhausted, you can use one multi-user key ORG8A, and then it is possible to use one multi-user key ORG8B.
4. Programs for administering HASP keys
4.1 HASP Device Driver
At the time of writing, version 6.62.1 was current. You can download from the official website or from.
This is nothing more than a regular device driver. It is needed so that the HASP4 Net key is identified in the system. Install following the installer's instructions.
4.2 HASP HL License Manager
from the official website or from .
A license manager is a utility that serves as a link between the network key and 1C running on a remote machine. When installed, HASP License Manager automatically creates a . However, for a protected application to work on a remote workstation, it is necessary to verify that UDP and TCP packets can pass unimpeded on port 475 in both directions. It is advisable to install the manager as a service by selecting “ Service (nhsrvice.exe)" during installation.
Well, after installation the corresponding service should appear.
When installing two or more license managers on a network, they must be configured for correct operation. Otherwise, a collision between license managers by name may occur on the network - at startup they take the same name by default, and as a result, there are several resources with the same names on the network. It is worth noting that managers often work normally without settings. However, be aware that a problem may occur. In addition, configuration may be necessary, for example, to separate clients into different license managers. Read more about this.
4.3 Aladdin HASP Monitor
At the time of writing, version 8.32.5 was current. You can download from the official website or from.
This utility serves to monitor access to the key and occupied licenses. After installation and launch, the program scans the network in search of a license manager and shows active connections of client applications to these services. The monitor allows you to see the names of the hosts on which the service and HASP keys are installed, the maximum number of licenses in the key, the number of occupied licenses and the names of clients who received the license.
It should be understood that the monitor itself can only show the presence of a license manager at a particular address. He will be able to see the key only after the protected application has successfully opened at least one session with the key. In addition, it should be taken into account that Aladdin Monitor only works over the UDP protocol, port 475, so for the program to work you need. Thus, the absence of key data in the monitor does not mean that the key is not available to the application.
5. View the received license in 1C
The list of all visible keys, as well as the location where the current license was obtained, can be viewed directly from 1C:Enterprise. It is enough to launch 1C in 1C:Enterprise mode, select “ Reference» — « About the program…» or click the icon with the image exclamation point on the panel.
In the window that opens, information about licenses can be viewed in the “ License». 
Here we will see the key that issued the license to this user, as well as everything visible keys networks. Information about issued licenses is also present in the 1C:Enterprise Server Administration Console in the list of sessions information base(starting from platform version 8.2.15).
Did this article help you?
Loading...
