1c does not see the network key. Application protection key not found

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 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:

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.

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

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 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.

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 a 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 security keys software HASP 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 key.

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 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

Yesterday we encountered such a problem. On our terminal server, after updating the platform, 2 out of 3 keys refused to work (in the end, instead of 30 users, only 10 were able to log in to 1c). When connecting to the database, the following error occurred:

As a result, a day and a half of working time was lost.

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.

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 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 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.

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 key.

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!

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 license usage 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 there 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. Fill in registration form, after which we save the data in a file that we place in the directory:

The message “Program protection key not found” itself means that the 1C program could not find a hardware device that serves as protection for the 1C program from unlicensed use. In theory, if you do not have a security key, it means you are using an unlicensed version of 1C.

The most common model of a security key is a small device that is connected in series to the printer port. For the past few years, the security key has been supplied in the form of a device that connects to the computer via a USB port.

When working with the network version of the 1C program, you can use one security key. In this case, the key must be installed on one of the computers on the network.

Thus, if, when entering 1C, the program displays the message “Program protection key not found,” then there are several possible reasons:

• 1. You physically do not have a protection key, because you have an unlicensed 1C program.
• 2. You have a licensed version of the 1C program, but the protection key is not connected to the computer (for example, the administrator took it home for the weekend and forgot to return it).
• 3. You have a licensed version of the 1C program, and the key is installed on one of the computers on the network, but is missing network connection to the computer on which the key is installed, or to the computer from which you are logging into the 1C program.
• 4. You have a licensed version of the 1C program, and all devices are turned on and turned on correctly, but the speed of the hardware devices is low enough for the program to poll all computers on the network for the presence of a security key. If the protection key is not found on the network within the specified time, the program will display a corresponding message.

In the vast majority of cases, the message “Program protection key not found” appears when an unlicensed version of the program is used on the computer. To use the 1C program, purchase a licensed version. If everything is in order with your license, then contact the company from which you purchased the 1C program for help.

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 key.

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!