Monitoring of 1c software licenses. Problems and solutions

• Tutorial

Many companies use 1C as the main automation platform. This is how it happened with us too. However, the process of establishing the platform was carried out without the proper approach, and therefore at first we had 5 protection keys for 95 licenses, then 3 more physical keys appeared to provide another 50 client licenses for 3 legal entities. The situation is stupid, since each key normally requires separate hosts, and there were fewer and fewer servers suitable for this, and the looming increase in the number of users and, consequently, the purchase of new keys, made me think about an alternative solution to avoid unnecessary information load on our servers and in general make the key system more flexible and, preferably, more stable.

System selection

Virtualization system

esxi 5.1 was chosen as the visualization system. Chosen for good support for USB device transfer and because, apart from ESX, I only understand Hyper-V, which does not support device transfer.

To transfer USB devices to ESX, the guest system hardware must be at least version 7. Then it will be possible to add a USB controller and map USB device to the guest system. There is also a point about support. Officially, VMware only supports a specific list of devices. And it's not very big. However, regular Aladdin security keys appear to be supported. The list of supported devices is on the official website. A description of the requirements and provisions for transferring USB to a guest system is also on the official website, in the knowledge base.

There are also alternative ways transferring USB keys into a virtual environment, and into a physical one too. These are so-called USB over IP devices and software. Software products in this case it’s not very interesting to consider, but iron ones in this case show themselves well. The most prominent representative is the well-known AnywhereUSB with 14 ports. It is installed in a rack, has two interfaces and two power inputs (whether it really has two power supplies, I don’t know :)). The device is good for everyone, but it costs an average of 60 thousand rubles, which did not fit well into our budget.

So, after tests and trials, we chose a virtualization platform and refused to use other products.

Operating system and HASP drivers

I chose Debian as the OS. Why? Just because. In fact, in this configuration you can take any favorite distribution. But I always like Debian for its stability and good repository.

The drivers used are a fairly popular package from Etersoft. You can get the compiled package for your distribution at FTP server company: ftp.etersoft.ru/pub/Etersoft/HASP/stable.
After installing the package, the haspd service appears, which manages the operation of the key.

Setup and testing

Some kind of additional settings All this is not required. The key starts working almost out of the box.
Let's check. To check functionality, the package includes the haspdemo program. Upon successful identification of the key and start of work, the program will display something like this in the console:

LOCALHASP_ISHASP: Result: 1

Using Passwords 15213 - 28875
LOCALHASP_HASPSTATUS: API version number is 8.0
port number 201
Key type: HASP4 M4
LOCALHASP_HASPGENERATION: OK, HASP4 is connected.
LOCALHASP_HASPNETSTATUS: connected key is HASP4 Net 20
MEMOHASP_HASPID: 436444258 (decimal), 0x1a039c62 (hex)

LOCALHASP_ENCODEDATA: OK.
53 C1 F1 AF | EC 16 C3 15 | 35 31 E4 7F | 9B D0 90 9F
AA BA 8C 80 | 1E 22 29 E2 | 92 7E 04 56 | DA 70 7B 63 [.....")..~.V.p(c]
23 B4 9B E6 | 2F 17 | | [#.../.]

NETHASP_READBLOCK: Failed: Return status: 10

Main field: LOCALHASP_ISHASP: Result: 1 . Letting you know that everything is okay. Further it is written about which key is inserted.

However, if there is some problem, the message is shorter:

This is a simple demo program for the HASP4 key
Copyright Aladdin Knowledge Systems Ltd.

LOCALHASP_ISHASP: Failed: status = -100

In fact, it doesn’t matter what happens to the key; it may not be inserted, the service may not be running, or something else. I've only seen two LOCALHASP_ISHASP values ​​so far. It is either: Result: 1 or: Failed: status = -100. And the latter always corresponded to inoperability, and the first always meant that everything was OK. I couldn’t find any documentation for this package, so I couldn’t find out what other statuses there are.

We've sorted out the key. We must not forget that your newly created key will appear in the key monitor only when at least one license has been taken from it. Then aladdin monitor will show the information that it usually shows: this is the type of key, the number of licenses taken, total licenses, who exactly took the license and timeout.
It’s quite easy to force this, just specify a new license manager in the client nethasp.ini manually. But we’ll talk about setting up the client a little later.

From this moment on, the initial task can be considered completed. Now we can create several virtual machines in parallel, in an amount corresponding to the number of available physical keys. The resources such virtual machines consume, naturally, are meager.

Problems and solutions

Single point of failure

The first problem that is created and in plain sight is the creation of a point of failure. If before this the keys were distributed among various servers and the failure of more than one key is practically excluded, then in this case the failure of the physical server may entail the failure of the entire 1C system, because clients will fall off within, in my opinion, 600 seconds and after a short time they will all fall off and will not be able to return to the system. What follows after such an incident need not be told. There are two possible solutions and are aimed at different directions. The first solution is to use a fault tolerant ESX configuration. However, this is advisable if your company has already deployed this system and has already met a number of requirements to maintain operability in the event of failure of any component. Another solution is more trivial:
We create a group of A records in our company's DNS. For example, key1, key2, key3 and so on. We enter DNS names into nethasp.ini of clients, distribute the file using group policy. This way we get a fairly flexible access structure. In this case, after discovering a significant problem with the esx virtual server, you can quickly move the keys to any other servers, incl. to the workstations of any employees. At the same time, we replace the A records with new ones. Within some time, the cache on clients will end and they will again be able to take a new license and continue working.
I recommend setting up the reverse DNS records for keys, otherwise aladdin monitor will not show the host name, but will only show the license manager ID, which is not very convenient.
If your company and everything uses the broadcast method of delivering keys, then everything is simplified and moving the key to another host within the broadcast domain will not affect work in any way.

The keys are falling off

There is such a fairly common problem. The keys fall off. However, no special connection was noticed. This happens on different controllers, even on different host systems. When I moved the keys and temporarily placed them in another location under control VMware Player, keys falling off occurred frequently. This is expressed quite trivially. When requesting haspdemo, the line LOCALHASP_ISHASP: Failed: status = -100 appears. Although the key is inserted and detected. dmseg shows lines that are not fully understandable: usb 2-2.1: usbfs: USBDEVFS_CONTROL failed cmd aksusbd rqt 192 rq 139 len 8 ret -110
The problem is solved as trivially as it looks - by restarting the service. But a residue remains and until this is done, the server will not distribute keys. Since I want the system to work flawlessly, it was decided to write a script that would automatically restore the operation of the license manager. So, with the help of a friend, a script was written that runs haspdemo and tries to understand whether the normal status is returned or not:
[ "`haspdemo | sed -n "s/^LOCALHASP_ISHASP.* \(\-\?*\)$/\1/p"`" == "-100" ] && service haspd restart
Next, this script is inserted into the CRON launch every minute and that’s it. Even if your system does not have the problem of falling ports, I think this script will not hurt.

Client key detection problem

And this is the problem. It lies in the fact that after losing the key, the client may not want to take a new key. This problem can also manifest itself in other ways. For example, if you have replaced the paths to the keys in the nethasp.ini file, then the client application can quite cheerfully continue to report that there are no keys and have never seen them. If you are not prepared for such a reaction, then the problem becomes very unpleasant and you begin to frantically check the operation of the entire system and curse at 1C employees, because everything works, but the Chief Accountant or, as luck would have it, the General, cannot log into 1Sku now for some unknown reason and you feel like an idiot instead of quickly solving the problem. However, a fairly simple solution helped so far. It is necessary to clear the 1C cache from the user profile. At one time I found separate file who is responsible for this information, I forgot which one :(

The keys may simply stop working

No one is insured against equipment failure. And these pathetic keys may also stop working. And the most important thing in this case is to find out about this as early as possible. For this we will use the Zabbix monitoring system. Of course, it makes no sense to deploy it only to monitor the keys, but if Zabbix is ​​already installed, then why not attach monitoring of the status of the keys to it.
To do this, we need to write our own script in the agent settings file. We are looking for the configuration file of the installed zabbix_agent, it is called zabbix_agentd.conf. Open it and add the line

UserParameter=hasp.status,haspdemo | grep "^LOCALHASP_ISHASP" | sed "s/^.* \(\-\?*\)$/\1/g"

This will allow the command to collect a digital value in the LOCALHASP_ISHASP field. In Zabbix itself, everything is added primitively, we create Item for the desired host or template, as Type indicate Zabbix agent, specify as the key parameter hasp.status. Value type - float. If desired, we can create a trigger that will send you a letter or SMS stating that the key does not work. It is better to configure this trigger in such a way that it requires at least 2 activations and covers the time required by the auto-recovery script, which was described above, otherwise false messages about problems with the key will appear.
If configured correctly, only if the key is completely inoperable will you receive a notification about problems.

Bonus

It came as a surprise to me, but many people really don’t know that you can force the 1C client parts to look for keys at the specified IP addresses using a TCP or UDP connection. Indeed, many set up the infrastructure so that each broadcast domain has a sufficient number of keys. This is wildness. For those who are not yet in the know, here is a brief instruction:
To control access to hasp key, the client has a nethasp.ini file. It is located in the \conf folder of the 1C directory. We are interested in the section. In this section we need to uncomment or create the following parameters:

• NH_SERVER_ADDR. Here we indicate a list of DNS or IP addresses of servers with a license manager, separated by commas.
• NH_USE_BROADCAST. Set the value to Disabled.
• NH_TCPIP_METHOD. The default method is UDP. You can change it to TCP, but in general there is no serious need for this.

Another point about displaying keys in aladdin monitor. Contrary to popular belief, free licenses are not only those licenses that are not listed as occupied in the aladdin monitor, but also those that have 0 in the Timeout field. The values ​​usually disappear within 36 hours, but licenses are still considered free.

In conclusion

I thought for a long time whether there was any point in such an article, after all, all this can be found on the Internet, but after calculating the time that I myself spent collecting all the information, I thought that it would be very good if at least someone The article will be useful and save time.

• Tutorial

Many companies use 1C as the main automation platform. This is how it happened with us too. However, the process of establishing the platform was carried out without the proper approach, and therefore at first we had 5 protection keys for 95 licenses, then 3 more physical keys appeared to provide another 50 client licenses for 3 legal entities. The situation is stupid, since each key normally requires separate hosts, and there were fewer and fewer servers suitable for this, and the looming increase in the number of users and, consequently, the purchase of new keys, made me think about an alternative solution to avoid unnecessary information load on our servers and in general make the key system more flexible and, preferably, more stable.

System selection

Virtualization system

esxi 5.1 was chosen as the visualization system. Chosen for good support for USB device transfer and because, apart from ESX, I only understand Hyper-V, which does not support device transfer.

To transfer USB devices to ESX, the guest system hardware must be at least version 7. Then it will be possible to add a USB controller and map a USB device to the guest system. There is also a point about support. Officially, VMware only supports a specific list of devices. And it's not very big. However, regular Aladdin security keys appear to be supported. The list of supported devices is on the official website. A description of the requirements and provisions for transferring USB to a guest system is also on the official website, in the knowledge base.

There are alternative ways to transfer USB keys into a virtual environment, and into a physical one too. These are so-called USB over IP devices and software. Software products in this case are not very interesting to consider, but hardware products perform well in this case. The most prominent representative is the well-known AnywhereUSB with 14 ports. It is installed in a rack, has two interfaces and two power inputs (whether it really has two power supplies, I don’t know :)). The device is good for everyone, but it costs an average of 60 thousand rubles, which did not fit well into our budget.

So, after tests and trials, we chose a virtualization platform and refused to use other products.

Operating system and HASP drivers

I chose Debian as the OS. Why? Just because. In fact, in this configuration you can take any favorite distribution. But I always like Debian for its stability and good repository.

The drivers used are a fairly popular package from Etersoft. You can get the compiled package for your distribution on the company's FTP server: ftp.etersoft.ru/pub/Etersoft/HASP/stable.
After installing the package, the haspd service appears, which manages the operation of the key.

Setup and testing

This does not require any additional configuration. The key starts working almost out of the box.
Let's check. To check functionality, the package includes the haspdemo program. Upon successful identification of the key and start of work, the program will display something like this in the console:

LOCALHASP_ISHASP: Result: 1

Using Passwords 15213 - 28875
LOCALHASP_HASPSTATUS: API version number is 8.0
port number 201
Key type: HASP4 M4
LOCALHASP_HASPGENERATION: OK, HASP4 is connected.
LOCALHASP_HASPNETSTATUS: connected key is HASP4 Net 20
MEMOHASP_HASPID: 436444258 (decimal), 0x1a039c62 (hex)

LOCALHASP_ENCODEDATA: OK.
53 C1 F1 AF | EC 16 C3 15 | 35 31 E4 7F | 9B D0 90 9F
AA BA 8C 80 | 1E 22 29 E2 | 92 7E 04 56 | DA 70 7B 63 [.....")..~.V.p(c]
23 B4 9B E6 | 2F 17 | | [#.../.]

NETHASP_READBLOCK: Failed: Return status: 10

Main field: LOCALHASP_ISHASP: Result: 1 . Letting you know that everything is okay. Further it is written about which key is inserted.

However, if there is some problem, the message is shorter:

This is a simple demo program for the HASP4 key
Copyright Aladdin Knowledge Systems Ltd.

LOCALHASP_ISHASP: Failed: status = -100

In fact, it doesn’t matter what happens to the key; it may not be inserted, the service may not be running, or something else. I've only seen two LOCALHASP_ISHASP values ​​so far. It is either: Result: 1 or: Failed: status = -100. And the latter always corresponded to inoperability, and the first always meant that everything was OK. I couldn’t find any documentation for this package, so I couldn’t find out what other statuses there are.

We've sorted out the key. We must not forget that your newly created key will appear in the key monitor only when at least one license has been taken from it. Then aladdin monitor will show the information that it usually shows: this is the type of key, the number of licenses taken, total licenses, who exactly took the license and the timeout.
It’s quite easy to force this, just specify a new license manager in the client nethasp.ini manually. But we’ll talk about setting up the client a little later.

From this moment on, the initial task can be considered completed. Now we can create several virtual machines in parallel, in an amount corresponding to the number of available physical keys. The resources such virtual machines consume, naturally, are meager.

Problems and solutions

Single point of failure

The first problem that is created and in plain sight is the creation of a point of failure. If before this the keys were distributed among various servers and the failure of more than one key is practically excluded, then in this case the failure of the physical server may entail the failure of the entire 1C system, because clients will fall off within, in my opinion, 600 seconds and after a short time they will all fall off and will not be able to return to the system. What follows after such an incident need not be told. There are two possible solutions and they are directed in different directions. The first solution is to use a fault tolerant ESX configuration. However, this is advisable if your company has already deployed this system and has already met a number of requirements to maintain operability in the event of failure of any component. Another solution is more trivial:
We create a group of A records in our company's DNS. For example, key1, key2, key3 and so on. We enter DNS names into nethasp.ini of clients and distribute the file using group policy. This way we get a fairly flexible access structure. In this case, after discovering a significant problem with the esx virtual server, you can quickly move the keys to any other servers, incl. to the workstations of any employees. At the same time, we replace the A records with new ones. Within some time, the cache on clients will end and they will again be able to take a new license and continue working.
I recommend setting up reverse DNS records for the keys, otherwise aladdin monitor will not show the host name, but will only show the license manager ID, which is not very convenient.
If your company and everything uses the broadcast method of delivering keys, then everything is simplified and moving the key to another host within the broadcast domain will not affect work in any way.

The keys are falling off

There is such a fairly common problem. The keys fall off. However, no special connection was noticed. This happens on different controllers, even on different host systems. When I moved the keys and temporarily placed them in another location running VMware Player, the keys would fall off frequently. This is expressed quite trivially. When requesting haspdemo, the line LOCALHASP_ISHASP: Failed: status = -100 appears. Although the key is inserted and detected. dmseg shows lines that are not fully understandable: usb 2-2.1: usbfs: USBDEVFS_CONTROL failed cmd aksusbd rqt 192 rq 139 len 8 ret -110
The problem is solved as trivially as it looks - by restarting the service. But a residue remains and until this is done, the server will not distribute keys. Since I want the system to work flawlessly, it was decided to write a script that would automatically restore the operation of the license manager. So, with the help of a friend, a script was written that runs haspdemo and tries to understand whether the normal status is returned or not:
[ "`haspdemo | sed -n "s/^LOCALHASP_ISHASP.* \(\-\?*\)$/\1/p"`" == "-100" ] && service haspd restart
Next, this script is inserted into the CRON launch every minute and that’s it. Even if your system does not have the problem of falling ports, I think this script will not hurt.

Client key detection problem

And this is the problem. It lies in the fact that after losing the key, the client may not want to take a new key. This problem can also manifest itself in other ways. For example, if you have replaced the paths to the keys in the nethasp.ini file, then the client application can quite cheerfully continue to report that there are no keys and have never seen them. If you are not prepared for such a reaction, then the problem becomes very unpleasant and you begin to frantically check the operation of the entire system and curse at 1C employees, because everything works, but the Chief Accountant or, as luck would have it, the General, cannot log into 1Sku now for some unknown reason and you feel like an idiot instead of quickly solving the problem. However, a fairly simple solution helped so far. It is necessary to clear the 1C cache from the user profile. At one time I found a separate file that is responsible for this information, but I forgot which one :(

The keys may simply stop working

No one is insured against equipment failure. And these pathetic keys may also stop working. And the most important thing in this case is to find out about this as early as possible. For this we will use the Zabbix monitoring system. Of course, it makes no sense to deploy it only to monitor the keys, but if Zabbix is ​​already installed, then why not attach monitoring of the status of the keys to it.
To do this, we need to write our own script in the agent settings file. We are looking for the configuration file of the installed zabbix_agent, it is called zabbix_agentd.conf. Open it and add the line

UserParameter=hasp.status,haspdemo | grep "^LOCALHASP_ISHASP" | sed "s/^.* \(\-\?*\)$/\1/g"

This will allow the command to collect a digital value in the LOCALHASP_ISHASP field. In Zabbix itself, everything is added primitively, we create Item for the desired host or template, as Type indicate Zabbix agent, specify as the key parameter hasp.status. Value type - float. If desired, we can create a trigger that will send you a letter or SMS stating that the key does not work. It is better to configure this trigger in such a way that it requires at least 2 activations and covers the time required by the auto-recovery script, which was described above, otherwise false messages about problems with the key will appear.
If configured correctly, only if the key is completely inoperable will you receive a notification about problems.

Bonus

It came as a surprise to me, but many people really don’t know that you can force the 1C client parts to look for keys at the specified IP addresses using a TCP or UDP connection. Indeed, many set up the infrastructure so that each broadcast domain has a sufficient number of keys. This is wildness. For those who are not yet in the know, here is a brief instruction:
To control access to the hasp key, the client has a nethasp.ini file. It is located in the \conf folder of the 1C directory. We are interested in the section. In this section we need to uncomment or create the following parameters:

• NH_SERVER_ADDR. Here we indicate a list of DNS or IP addresses of servers with a license manager, separated by commas.
• NH_USE_BROADCAST. Set the value to Disabled.
• NH_TCPIP_METHOD. The default method is UDP. You can change it to TCP, but in general there is no serious need for this.

Another point about displaying keys in aladdin monitor. Contrary to popular belief, free licenses are not only those licenses that are not listed as occupied in the aladdin monitor, but also those that have 0 in the Timeout field. The values ​​usually disappear within 36 hours, but licenses are still considered free.

In conclusion

I thought for a long time whether there was any point in such an article, after all, all this can be found on the Internet, but after calculating the time that I myself spent collecting all the information, I thought that it would be very good if at least someone The article will be useful and save time.

Question: Monitoring software licenses

Good afternoon.
Windows server 2008+ SQL server+ Server 1C 8.2.
The server has installed software licenses of 10 pcs + 5 pcs = 15 pcs.
The maximum number of simultaneously working users is 13 pcs.
There is one base. Accordingly, users run only one instance of the program.
Sometimes some users cannot log into 1c (the program’s security key is not detected). It turned out by chance that users can log in again if 1c is restarted by one specific user. Accordingly, as I understand it, this user consumes more than one license in the course of his work.
Question: how to track which licenses went where and how to deal with such frozen licenses?

Answer:

Good processing, necessary! But it doesn't work)
(ExternalProcessing.LicenseMonitoring.ObjectModule(53)): (ExternalProcessing.LicenseMonitoring.ObjectModule(23)): Error when calling the constructor (COMObject): -2147221005(0x800401F3): Invalid class string
RaiseExceptionDescriptionError();

Maybe someone could cure it?

Question: Problem with software licenses on the 1c server

Hello dear forum users! Please tell me if anyone has encountered what to do in such a situation.
Initially: there was a database 1s KA 1.1, 1s 8.2, platform 8.2.19.130, file on the terminal server. On the server itself, a key was installed for 10 user licenses and 5 software licenses (the license file was located in C:\ProgramData\1C\1Cv82\conf). Users worked through terminal sessions.
What happened: switched to a client-server version (1C server x64, platform 8.3.8.2054), Postgres database, users work directly from their workstations. Computers receive a license over the network from the server.
The problem is that 1C server does not see software licenses. The license file was copied to the server conf folder (C:\Program Files\1cv8\conf), to the licenses folder (C:\Program Files\1cv8\8.3.8.2054\licenses - although I understand that the license should not be stored here), and also to the platform folder along the same paths (C:\Program Files (x86)\1cv8\conf, C:\Program Files (x86)\1cv8\8.3.8.2054\licenses).
As far as I read on the Internet, software keys are searched and picked up first, so it should work...
But sad thoughts come to me that when installing a software license for 5 users, something was “stitched” into the register that connects it with the original scheme, on 1c 8.2, and that the 8.3 server does not see. Since you will have to activate a new PIN code for the software license, I ask for help, tell me, is this really the case??

Answer:

When activating software licenses, more than one file is created. It is best to write to the address, they answered me within half an hour regarding the issue of deactivating the license. They suggested finding and deleting all 2*.lic files and all conn8211.pfl files (or 1Сv8conn.pfl, if version 8.3). Accordingly, you at least need to move all these files, but no one will say whether it will help, so I would write them a letter. Due to incorrect actions, the license package may be blacklisted.

Question: Software license and COM connection

The software license is installed.
When I try to start 1C over a Com connection it writes:
-----------
No free license found!
Search for licenses on the client:
Software Licensing Error
The maximum number of users allowed by the software license file has been exceeded.
Source: V82.COMConnector.1
-----------
What is the problem?

Answer: The maximum number of users allowed by the software license file has been exceeded.

Question: How can I find out which file (.lic) corresponds to which software license?

Hello. There are two software licenses installed on the server (must be installed). But I see that only one is heard. In C:\Users\1C_admin.1C8\AppData\Local\1C\1cv82\conf there are 3 files: 2014*****.lic in one of them if you open it through a text viewer it is written at the top (the software licenses themselves are number 8100** ***):

Computer server1 uses two copies of the same software license file: file://C:/ProgramData/1C/1Cv82/conf/2014*****.lic and file://C:/Users/1C_admin.1C8 /AppData/Local/1C/1Cv82/conf/2014*****.lic

Although this folder is empty.
The folder C:\Users\All Users\1C\1Cv82\conf is also empty.
Can I delete this inscription and then everything will start to sound?

And most importantly, I look through the administration console for the key server 8100 - this is software key. What kind of key is ORGL8 Set 20 - what is this key? Software or hardware? I think it’s software, but why then the Server and not the client?

Answer:

Doesn’t anyone know how to find out from the .lic file which license it is (the .lic license corresponds to the number from the registration card)?

Question: Tricks for issuing software licenses by 1C server

Hi all!
Friends, please tell me about licenses, there are some things that are not clear to me.
A software license for 10 users is activated on the server. The server has a 1C server, a SQL database and a terminal server.
Licenses are issued as follows (maybe this is not accurate, correct me if I’m wrong).
1. If the user has on his local computer there is a platform and it connects via the network to the 1c database on the server, then for each running instance of the program, the server gives it one license. That is, if a user launches 10 databases, there will be no licenses left on the server.
2. If the user connects via RDP, the server gives him one client license and the user will be able to run an unlimited number of program instances (databases).
The main question is, will the second point work if the user connects to the terminal server via RDP, software licenses will be activated there, but there will be no 1c server? In the terminal he will have a platform but without a 1c server. Is it necessary for point two to work, there must be a 1c server on the terminal server?

Answer:

This issuance of licenses works for any local launch of 1C (RDP is a local launch) if the licenses are not distributed by the 1C server

Question: Client software licenses are not distributed

Good afternoon.

Created a 1C cluster (8.3.7.1759) and a licensing server. I acted according to these instructions. (). I activated a multi-user software license on the licensing server. If I launch the 1C client directly on the licensing server, then it normally receives a software license. From any other places, if we connect to the database on this cluster, a hardware license is issued. The license file is here C:\ProgramData\1C\licenses

Answer:

There is read access. The functionality assignment has been added to the licensing server. There is no need to check the box to use a hardware key.. And still gets a hardware license...

--- An association messages, 28 Dec 2015 ---

OKarlov said:

Check the other reported error

If a limit on the number of information bases per worker process, then functionality may begin to be distributed to that server that is prohibited by the functionality assignment requirements.

Click to expand...

The cluster is new - there is only 1 base on it so far. Nobody is working. The setup is now 8 databases, 128 connections per process.

Question: Problem with transferring the 1C 8.3 software license to new server

Good afternoon.

The company had one physical 1C 8.3 server with accounting file databases. It had software licenses.

We purchased licenses for 1c ERP:

1.per platform for 20 people
2. for configuration 3. for server 1 s We also bought a new rack server, installed the 1C 8.3 platform on it, deployed an ERP test database, installed software licenses - everything is ok.

There was a problem with the transfer file databases, or rather, I copied the databases themselves, but when starting 1C does not offer to enter a license, but says that the license was not found and suggests using a hardware protection key.

Tell me how to make 1C offer to introduce a software license for accounting file databases on a new server?

Answer: Thank you very much!

Question: v7: 1C 7.7 TiS - could there be a software license?

I encountered TiS 7.7 local without a hardware protection key. As far as I remember, TiS 7.7 did not come with a software license? I remember on 7 there were some products with activation according to words from a book - you had to find a word on such and such a page and then activation occurred, that is, without a security key. But it seems like these were some kind of industry decisions, as far as I remember. There is a box with a questionnaire, floppy disks and books, but the key is nowhere to be found. True, there is no LPT port on the PC, perhaps that’s why it wasn’t installed at the time and was lost somewhere. But still, I would like to make sure that the TiS did not have software activation, only hardware activation? Suddenly I’ve just always encountered hardware problems before.

Answer:

Good afternoon
The server has 2 software licenses for 20 connections each. The licenses ran out for no reason, although I look through the monitor of connected users - there are only 19 connections.
How can you find out how many licenses are in use? The program from Aladdin is good but only works with USB keys.
Thank you.

Answer:

“I look through the monitor of connected users - 19 connections in total” - through which monitor do you see the issued software licenses?