No license found to use the program! No license found. The program protection key or the received software license was not detected - Solution The program protection key was not found, what to do

The 1C program is used where accounting needs to be optimized. This software is licensed, therefore, to work in it, you must enter a special key. Without it, starting the program is not possible. If 1C does not see the key, then the program displays information about it. For example, " 1C 7.7 protection key not detected" Or so " 1C program protection key not found» – the second option is more common.

How to solve the problem of an undetected program protection key?

Try setting the checkbox to " Use hardware license" To do this, click on “ Settings».

If that doesn't work, proceed as follows:

• Find Nethasp.ini – the key protection configuration file.
• Do not turn off the computer into which the key is inserted. When 1C starts and it works, an automatic check for the presence of a key occurs. Do not turn off the PC; it must be connected to the power supply at this time.
• Checking in Nethasp.ini is done via "broadcast".
• Specify in the settings a specific path to the PC where the key is located and reject “wideform. newsletter."
• Open the file. You can select the editing application of your choice (in “C:\Program files\1Cv81\bin\conf” (for 8.1) or “C:\Program files\1cv82\conf”). We recommend selecting “Notepad” and looking for the line “”.
• Specify the IP address of the PC containing the 1C security key.
• Use the line “NH_USE_BROADCAST = Disabled” to disable wide-format network distribution.

That's it, you've completed the task! You can buy from us

The behavior of many system administrators who are faced with difficulties when installing security keys for 1C Enterprise is most reminiscent of shamanic throwing with a tambourine. In “admin circles” and on the Internet, there are myths and legends about the “capriciousness” of security keys, about its “crooked” implementation, etc. At the same time, most of the non-standard situations are the result of an extremely low level of knowledge about security keys and the features of their use.
What types of keys are there?

Local single-user keys are represented by the HASP HL ​​Basic model (blue), this key is marked H4 M1 ORGL8, does not have built-in memory and personal ID, and does not store any parameters and settings. Supplied with products licensed for one workplace.

Network client keys include the HASP HL ​​Net series (red). They have an internal memory that stores the number of licenses and an exclusive ID. There are varieties for 5, 10, 20, 50 and 100 users. It is marked NETXX ORGL8, where ХX is the number of licenses (such as NET5 ORGL8). There are, in turn, keys for 300 and 500 users that are marked NET250+ ORG8A and NET250+ ORG8B. Supplied with products licensed for 5 workstations, and also separately, in the form of additional client licenses.

Keys for the 1C Enterprise server are only local. The 32-bit modification 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) with internal memory and a unique ID is used. It is marked EN8SA and in turn 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 in the reverse order.

How to install keys without errors

One important point should be noted: it is prohibited to install more than one key of the same series on one computer. In addition, it is not recommended to place the local and network keys together; this is due to the security feature of 1C Enterprise: when finding a local key, the program will in no case search for the network one. Local keys of the 1C Enterprise server do not interfere with the operation of other keys.

The second important point: the key should not be located on a machine with active terminal software. In turn, there is no need to place the license manager in the terminal. 1C on a terminal server can only work with a network key located on another PC.

If you have two or more network keys, it is not enough to distribute them across different computers. It is necessary to configure license managers. Each license manager must have a unique name, which must be explicitly communicated to the protected program. It is recommended to carry out a similar setup in the case of using a terminal server, with at least one 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 that, on client machines you must 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

What are the errors?

Unfortunately, instead of the standard HASP error messages, 1C Enterprise displays its own “Program protection key not found!” There may be four types of errors hidden under this message; let’s look at them in more detail.

Key not found. Obviously the most common mistake. Occurs when there is no key or an attempt is made to use a key from another product. For network keys, this error can be detected when there is no network, when the license manager is not running on the machine with the key, port 457 is closed, or the non-network key is installed incorrectly.
.The key does not contain a license. Occurs when two keys of the same series are installed on one PC, and the one that does not have the required license is visible. When working on a network of two license managers with the same names and serving keys of the same series, the application may be the first to find a key that does not include the required license, which in turn will lead to receiving this error.
.Terminal service detected. Occurs when you try to enable an application from a terminal session with a local key. It may, in turn, appear in the case when the address of the license manager is not explicitly specified in nethasp.ini.

The number of licenses has been exceeded. Occurs if the number of users (active sessions) exceeds the number of licenses specified in the key. When two license managers with the same names and servicing keys of the same series are working on a network, the application may first find the key with the maximum number of connections already marked, which in turn will lead to receiving this error.

I came across this problem the other day. One of the machines refused to work network version of 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 I didn’t immediately attach any importance to this moment. Apparently because HASP monitor I 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 more precisely, 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 a protection system using hardware keys is used HASP, 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:

1. Single-user (must be physically connected to the computer running 1C)

model HASP HL ​​Basic (of blue color ), 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.

HASP network key

2. Multi-user (the key is on the network, 1C can be launched on any computer in within the local network or domain)

Network client keys include a series of ( 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. Has markings NETXX ORGL8 , Where XX- number of licenses (for example NET5 ORGL8 ). There are also keys for 300 and 500 users that are marked NET250+ ORG8A And NET250+ ORG8B . Supplied with products licensed for 5 workstations, as well as separately, in the form of additional client licenses.

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 1C Enterprise server are only local. 32-bit version has a protection key HASP HL ​​Pro (purple ), which has internal memory and a unique ID. Has markings ENSR8 , comes with a license for the 1C Enterprise server.

For 64-bit server key is used HASP HL ​​Max (Green colour ) with internal memory and unique ID. Has markings EN8SA and also supports 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.

A single-user and server key is sufficient to operate install the security key driver on the local machine and insert the security key into the local USB port.

For a multi-user (network) security key you need:
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’s 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, a message will be displayed “Program protection key not found” and the work of 1C:Enterprise will be interrupted.

If you encounter the message " application protection key not found“need to check:
1. presence of a protection key in the USB port of the key server
2. check whether the key server is running on the server (process named “Hasp loader”)
3. use the telnet command to check the availability of the key server from the local machine on 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 file nethasp.ini . This is the 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 - error

Disadvantages of the default configuration:
1. broadcast takes some time
2. not all servers respond to such packets
3. broadcast is not good, but it’s a load on the network

To solve this problem you need to do the following:
1. indicate 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 packet types 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 also 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 had to deal with during my work:

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 fine)
• Keys of the same series will work if this feature was implemented by the developer of the protected software. If the developer has not implemented this feature, 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 junior address (in the case of USB keys for protecting HASP programs). (in relation to 1C, - 2 local or 2 network keys on one computer will most likely 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 distribute them across 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 we find the file nhsrv.ini 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!

Best regards, McSim!

When launching the 1C Accounting program, the operator may encounter the message “License not found. The program protection key or the obtained software license was not found." The occurrence of this problem may be associated with a change in the system configuration, as a result of which 1C recognized the system as qualitatively new, or with incorrect settings of 1C itself (in particular, the network settings of the nethasp.ini configuration file). In this material, I will analyze in detail the reasons for this error, and also explain how to fix it.

Causes of dysfunction

The “License not found” error usually occurs in a situation where the 1C program did not detect a license file (usually with the .lic extension) on the local PC (or server), which makes it possible to fully launch the specified system.

This situation may arise due to the following factors:

How to fix “License not found” in 1C

Let's look at ways to get rid of the error “License not found. The program protection key or the received software license was not detected" on 1C user systems:

1. Before starting the program, disable your firewall;
2. Install “Alladin monitor” into the system. This product shows the use of licenses in the network version of the program. Use it to verify that your system has an installed license;
3. When using a hardware license, in the infobase window, click on “Settings” and check the box next to the “Use hardware license” option if there is no such checkbox there;
4. Edit the Nethasp.ini file, which is located at the following path:

Open this file and write down the IP addresses of client PCs and the names of license managers. To do this, in the specialized section, indicate:

Then in the section, specify the IP address of the license manager server (should look like NH_SERVER_ADDR = required IP), and the name of the license managers (NH_SERVER_NAME = manager name).

The name of the manager is preliminarily indicated in the section in the form NHS_SERVERNAMES = name 1, name 2, and so on.

• Activate your existing license. If you receive a message about the absence of a detected license, click on “Yes” and indicate the path to install the license (local PC or server).
• Then we select the option of obtaining a license initially, re-obtaining it, or updating it. We set the visibility of the license to “All computer users”, select the method of obtaining it - manual, automatic, on a digital medium. We fill out the registration form, after which we save the data in a file that we place in the directory:

The actions of many system administrators who are faced with difficulties when installing security keys for 1C Enterprise are most reminiscent of shamanic rituals with a tambourine. In “admin circles” and on the Internet, there are myths and legends about the “capriciousness” of security keys, about its “crooked” implementation, etc. At the same time, most non-standard situations are the result of an extremely low level of knowledge about security keys and the features of their use.

What types of keys are there?

Local single-user keys are represented by the 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.

Network client keys include a series HASP HL ​​Net(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. Has markings NETXX ORGL8, where ХX is the number of licenses (for example NET5 ORGL8). There are also keys for 300 and 500 users that are marked NET250+ ORG8A And NET250+ ORG8B. Supplied with products licensed for 5 workstations, as well as separately, in the form of additional client licenses.

Keys for the 1C Enterprise server are only local. The 32-bit version has a protection key HASP HL ​​Pro(purple), which has internal memory and a unique ID. Has markings ENSR8, comes with a license for the 1C Enterprise server.

For a 64-bit server the key is used HASP HL ​​Max(green) with internal memory and unique ID. Has markings EN8SA and also supports 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.

How to install keys correctly

You should remember one important rule: you cannot install more than one key of the same series on one computer. It is also 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. Local keys of the 1C Enterprise server do not interfere with the operation of other keys.

Second important rule: the key should not be located on a machine with active terminal software. Also, you should not install a license manager in the terminal. 1C on a terminal server can only work with a network key located on another PC.

If you have two or more network keys, it is not enough to distribute them across 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 we find the file nhsrv.ini in the folder with the license manager. The parameter determines the name of the license server NHS_SERVERNAMES, it can consist of Latin letters and numbers and contain no more than 7 characters.

NHS_SERVERNAMES = NAME1

Then on client machines you should edit the file nethasp.ini, 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

What are the errors?

Unfortunately, 1C Enterprise displays its own error messages instead of standard HASP error messages “Program protection key not found!”. There may be four types of errors hidden under this message; let’s look at them in more detail.

• Key not found. Perhaps the most common mistake. Occurs when there is no key or an attempt is made to use a key from another product. For network keys, this error can occur when there is no network, if the license manager is not running on the machine with the key, port 457 is closed, or a non-network key is installed incorrectly.
• The key does not contain a license. Occurs when two keys of the same series are installed on one PC, and the one that does not have the required license is visible. When two license managers with the same names and servicing keys of the same series are working on a network, the application may first find a key that does not contain the required license, which will also lead to this error.
• Terminal Service Detected. Occurs when trying to launch an application from a terminal session with a local key. It may also occur if nethasp.ini The address of the license manager is clearly not specified.
• Number of licenses exceeded. Occurs when the number of users (active sessions) exceeds the number of licenses specified in the license key. When two license managers with the same names and servicing keys of the same series are working on a network, the application may first find the key with which the maximum number of connections has already been established, which will also lead to receiving this error.