Question: Can’t see the hardware key (thick client)

Hello!

This is the problem:

The old PC had 1C 8.2 (single-user thick client - database and client on one PC).
Hardware key (purple H4 M1 ORGL8)
Windows 7, 32bit

We decided to transfer 1C to new hardware ( Windows Server 2008, 64bit).
We installed 1C 8.3 (also a single-user thick client) and the security key driver, and transferred our database there.

When starting, 1C does not find the protection key (License not found. Program protection key not found or received software license!).

The key is inserted into the USB and lights up.
The key was changed in different USB ports.
Reinstalled the key drivers.
Installed HASP Lisence Manager (although this is unlikely to be necessary, since there is no network distribution of keys)
We also installed the old 8.2 platform.

Nothing helped.
Are there any ideas on what to do so that 1C sees the key?

Thank you!

Answer:

just in case...is there a flag in the launch window - is the "Use hardware license" setting worth it?

Question: 1s 8.3 does not see the 8.2 hardware key

We worked on platform 8.2.18.61. I had to switch to platform 8.3.10.2561. The enterprise server was 64-bit (8.2). After installing 8.3 enterprise server (64 bit), when starting 1c, I cursed that the license was not found. I start 8.2 (I stop the 8.3 service and start the 1C 8.2 service), I see everything. I install the 32-bit version of 1C 8.3, the key is visible. I checked the server key, it is green MAX EN8SA (that is, 1c enterprise 64 bit should see it). I uninstalled the old Hasp driver and installed a new one along with the platform. The server was overloaded. But 1c does not see the key at point-blank range when a 64-bit enterprise server is installed! Any ideas on how to solve this issue?

Answer: Again I tore down the platform and reinstalled it and it started. Some kind of bullshit.

Question: One client hardware key for distributing licenses to two 1C servers

Hello!
There is a USB hardware key for 100 users and 2 physical 1C servers not in a cluster. One of the servers is terminal; a hardware key is installed on it. Is it possible to configure HASP License Manager in such a way that licenses are issued only to 1C servers, and client applications on the terminal server can receive licenses only from servers?

Answer:() Thank you! I'll try

Question: Local databases and hardware key.

Good afternoon Please tell me, the enterprise has a hardware key for 100 licenses. 1C client-server databases work without problems. There was a need to create local databases.
Is it possible to run local databases with a hardware key? If yes, please tell me how. Because now this option does not work, and when starting the local database it says: License not found. The program protection key was not found or the software license was obtained...etc.

Answer:

They shouldn't. The server and service operate independently of each other.

Question: 1C 8.2 Baovaya does not see the license. Doesn't ask.

Hello! I apologize in advance if I created a duplicate topic. Please help!

The situation is as follows:
Technology platform: 8.2
Configuration basic version 2_0_14_5

When I launch it for the first time, I uncheck the box in the settings so that it does not look for the hardware key, I add the database from the template, when it starts, it does not see the license, but directs it to the licensing center where it asks to enter a 16-digit pin. I don’t enter the PIN - the very fact that it asks is important.

I installed it in the office and at home - it works.

I do the same for the client, including uninstalling 1C and reinstalling it from the same distributions. But he doesn’t send it to the licensing center, he simply writes that he doesn’t see the license.

This is the picture it paints for me...

What to do? The client claims that this started after a virus cleanup. + The interesting thing is that if you simply create a database without using a template, it will also ask you to enter a PIN code. 15 characters per professional configuration. But the basics are important.

The client's OS is licensed Vista, antivirus Nod32 v5(I turned it off completely). Demolishing the system is not an option because there is a lot of paid software there.
PS I've already broken my head on this problem.

Answer:

Good afternoon

In the absence of hardware protection, it works software protection. Only 3 codes. You can install the program only 3 times. If you had to reinstall due to force majeure (virus, fire, new computer), write to 1C, they will give you new key. It looks like you have already used your 3 keys. Write to 1C.

Question: 8.3 does not see software key

All the best. Windows 10, BP 3.0. On 8.3.5 everything is ok. I'm trying to update, I need platform 8.3.6. I installed both it and 8.3.7 - both do not see the activation, a yellow window for obtaining a license appears (when launched through 8.3.5 everything is still ok)

Answer:

I’ve already given away the laptop, but thanks anyway, I’ll remember it for the future

Question: Licensing 2 keys of the same nethasp.ini type

There are a lot of topics on this issue, but apparently I'm doing something wrong.
2 servers:
A USB key for 100 licenses is inserted into the first one

a key for 5 licenses is inserted into the second one and a license manager is installed on it, which sees both keys.

but each server only uses local keys. on the second, 5 have run out and he does not take the licenses of the first, where there are 100 of them available. On the second server, I open the file C:\Program Files (x86)\1cv8\conf\nethasp.ini and write 2 addresses in the line:

NH_SERVER_ADDR = 192.168.0.1, 192.168.0.2; first ip 5, second ip 100 licenses

Doesn't work

Answer:() users open several databases and there are file

Question: v7: 1C Public catering 6.0 does not see network address protection key.

Good afternoon Here is a PC on Win 7 64. It has 1 C accounting 4.5 (network version) 7.70.505 When starting the program it gives an error:
The program protection key was not found The network address does not exist “PC user” First, I want to ask how can I specify a new key location address? Namely local, the protection keys are plugged locally directly into the PC where I run 7 .7 Keys 2 HASP and regular USB protection key.
The USB key is detected by the SLK server, although SLK does not see licenses on this key.

It is not clear what to do with the HASP key; there is a HASP LM and HASP HL ​​driver.
But if you run NHSRVW32 from the Bin folder, it writes that “the key driver is not installed”

Answer: Got it.
In my case, in the folder with the 1C database there was server.ini, where you need to manually enter the name of the server where the key is inserted. And everything worked.

Question: Analytics keys

UPP RAUZ In 2016, on December 29, HMS was moved from one warehouse 1 of organization A to another warehouse 2 of another organization B, and the inventory keys were generated; Oak JSC; KI 10.03; 10.03. Since 2017, there have been receipts of goods at warehouse 2 of organization B, but the analytics keys were generated by KI 10.03. And it turns out that there are now liters of gasoline hanging around with analytics KI 10.03; 10.03. Tell me what to do? How to write off? When I just try to move again, the move goes with analytics KI 10.03. I’ve been working for the organization for a couple of weeks, but I didn’t see that they were cheating

Answer: In any case, start all this by creating a copy of the base and do everything on it, then repeat what needs to be done in combat. Well, start with Testing keys with built-in standard processing. Maybe this alone will be enough to restore order

Question: v7: 1C 7.7 does not see HASP on Windows 10 x86

There is 1C 7.7, USB HASP local, Windows 10 x86.
Tried it different versions drivers - the old ones are no longer installed, and with the new ones the key is visible in the device manager, but 1C 7.7 displays "Protection key not detected" at startup.
I found a thread, but it’s still unclear how the problem was solved.
Please help.

Answer:() Can you write what version and build of Windows, what version of the hasp driver and release of the 1C platform? Whether HASP LM is used or not (although the key is local, but for reference). I'll try to install the same versions myself.

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 the meanings immediately at this moment didn't give it. Apparently because HASP monitor I detected these keys perfectly, which is why I looked for a 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 on which 1C is running)

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.

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 ) 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, we 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 packet is sent broadcast type over the local network on port 475 in search of the 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 one.

Possible solutions to this problem:

• Replacing several protection keys for HASP programs 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

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 don’t have a security key, it means you’re not using licensed version 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.

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, network settings 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 obtained software license was not found" on user systems 1C:

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 a window information bases click on “Settings” and check the box next to the “Use hardware license” option if such a checkbox is not 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 select the option primary or re-receipt license or its renewal. We set the visibility of the license to “All computer users”, select the method of obtaining it - manual, automatic, digital media. We fill out the registration form, after which we save the data in a file that we place in the directory:

The behavior of many system administrators, faced with difficulties when installing security keys for 1C Enterprise, are 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 key 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

Then 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 which the maximum number of connections has already been marked, which in turn will lead to receiving this error.