1c enterprise installation of hasp driver. Tmplts folder structure reminder

Knowing how to install the driver for 1C is necessary for every user of this program. This is especially important in new versions, starting with 1C 8, where it was first implemented software protection. Without the necessary driver, the program refuses to work because it believes that it, like user data, is in a vulnerable position. If you do not install the key, thereby assuring the program that it is secure, the work will stop. This is why installing drivers is so important. But many users and system administrators have difficulties with 1C protection, so we will analyze in detail how it works and why it is needed.

What is 1C protection?

1C is a program that automates financial flows and their accounting in an enterprise. The financial sector always needs an increased level of security, and 1C contributes to building a protective barrier. The 1C security system is called a software license and serves to restrict unauthorized access to software data and provide safe work several users at the same time.

There are several types of software licenses:

For one user - an unlimited number of applications can be launched simultaneously - blue HASP HL ​​Net key.

For several users - limits the number of simultaneously running programs to an arbitrary number - red HASP HL ​​Net key.

Combined - allows you to activate either the single-user or multi-user version. As a result, the version launched first remains forever.

For a 32-bit server - limits the number of 32-bit processes to an arbitrary number - purple HASP HL ​​Pro key.

For a 64-bit server - limits the number of 64- and 32-bit processes to an arbitrary number - green HASP HL ​​Max key.

There are several options for checking your license:

Client - the scan is launched on a computer with a client version of the program and if the response is incorrect, the program is blocked. The check is carried out when the program starts and regularly during operation. Client-side verification is implemented for multiple users working on a network and using the same license.

Server - the check is launched on a computer with a server version of the program to authorize the server to start.

Implementation of 1C software license

The software license is presented at two levels - software and hardware. Moreover, on older versions, for example, 1C 7.7, only the hardware key works, but starting from 1C 8.1 you can already choose between hardware and software keys.

Hardware protection. Initially, the security license for 1C was implemented using the HASP system in the form of an electronic key. It was a flash memory device connected to the client computer via a USB connector, or it was an LPT dongle. For such a key to work, the Alladin driver must be installed on the computer, and if one key is used for several network computers, the Alladin key manager must also be installed. The HASP key is still the main security system of the program and is supplied as a component to the 1C software product.

Software protection. Starting with version 1C 8.1, it became possible to use alternative key- software. This key is installed on the client computer, and not the fact of the presence of the key is used as a check, but its binding to a specific machine. Changing the car leads to the need to change the key. At the same time, a significant update of the operating system version, for example, from Windows 7 to Windows 8, will signal to 1C that this is a different machine and is needed new key, otherwise 1C will not start.

Proper installation of the key and driver in 1c

The 1C software license causes many problems at any level, but this is not caused by a “crooked” software, but by illiterate installation of keys and drivers. We hope that you have already understood a little about the typology of 1C security keys and we draw your attention to the following points for correct installation:

Only one key from the series can be installed on one car.

It is not recommended to install both local and network keys on the same machine. The system by default looks for the local key first and will therefore only see the local key. You can change the search order for keys, as well as other default settings, in the nethasp.ini file.

In order for the network key to be available to all network users, both the key and the license manager (supplied with the main program) must be installed on one machine. You can configure the manager’s operation and the number of connected licenses in the nhsrv.ini configuration file, usually located at C:\Program Files\Aladdin\HASP LM.

When using network keys, a license manager is required; the key must be assigned a unique name on each machine. This can be done in the nhsrv.ini file, which is located in the same directory as the license manager. Names must not exceed seven characters and must consist of numbers and Latin letters.

When using multiple license managers, you must assign a unique name to each one. This can be done in the nhsrv.ini file, which is located in the same directory as the license manager. Names must not exceed seven characters and must consist of numbers and Latin letters.

To account for licenses, use special program Aladdin Monitor, it allows you to track your remaining licenses.

To exchange data between 1C and retail equipment, you need to install an additional cash register driver from ATOL.

When it doesn't install: errors

1C has its own error reporting system, so instead of clear HASP notifications, one error is issued for all cases - “The program protection key was not found!” The program refuses to work, but does not explain why. In fact, this error means four variants of problematic situations and is eliminated accordingly:

"The number of licenses has been exceeded." The number of licenses specified in the key is less than the number of active connections (users). Or two license managers with the same names are running on the same network.

"Terminal service detected." When starting 1C from a terminal session with a local key.

"The key does not contain a license." If two keys of the same series are installed on one machine, the system may mistakenly see the first key that does not contain the required license. Or a similar message appears when two license managers with the same name and using keys of the same series are working on the same network.

"Key not found." The most common error message. Indicates the use of a key from another car, the absence of a key, when network connection- the license manager is not running, the port is closed, or the network key is not installed (but a local one is installed).

If you encounter any difficulties with the operation of the program, installing keys or drivers, or setting up any level, please contact our professionals for help.

Software protection of licensed software does not provide a 100% guarantee against copying and illegal exploitation. The optimal, although not the cheapest, way to prevent hacking is to install a hardware security key. By distributing copies of its accounting system, the 1C company took, among other things, this route of ensuring security. Next, we will discuss the nuances of working with 1C keys in practice.

1C software licensing concepts

The 1C protection key looks similar in appearance to an ordinary flash drive. However, its function is completely different - it is intended to mark the 1C software package as having passed licensing. Running 1C programs on a computer that does not have such protection or on a network where the key is not installed on any of the computers is impossible. Depending on the type of “1C Enterprise” “client”, one of the policies for using the protection key is adopted:

• Policy for file-server type configuration.
• Policy for client-server configuration.

The simplest example of a configuration of the first type is the case when 1C is used on one single computer. The key and software are not physically separated and are located on the same machine. A more complex version of the same policy is to spread it across several computers. Moreover, each of them is equipped with a key, and the user can run as many copies of 1C software as he likes. This type of license and key is called single-user.

If the file server configuration uses multi-user protection keys, then only a certain number of copies of 1C applications are allowed to run at the same time. How these applications will be distributed among users does not matter. The key will prevent any attempt to launch more copies. This type of license and key is called multi-user. The Hasp License Manager program (1C license manager) must be installed and configured on each machine.

The client-server protection policy differs from the file-server one in that a dedicated server on the network is occupied with monitoring 1C licenses. There are two versions of this license: for a 32-bit server and for a 64-bit server.

• Local single user HASP HL ​​Basic has blue markings;
• Network client HASP HL ​​Net has a red marking. Each such key has a unique identification number recorded in its internal memory. They vary in the number of users: from 5 to 100, there are options for 300 and 500 users;
• The 32-bit version of the server type is labeled purple;
• The 64-bit version of the server type has emerald markings.

Only one key of the same type can be installed on each computer.

Advice: 1C specialists do not recommend simultaneous installation of network and local keys on the same machine. The reason for this is very trivial: if the local key is recognized first, then the search for the network key will be canceled and the work of other network users in the client-server configuration will become impossible.

A little about Hasp License Manager

If you use a multi-user license, it is necessary that the security device installed on one of the machines on the network be visible to other computers. The already mentioned “Hasp License Manager” program is responsible for this. Program information:

The Hasp License Manager parameter settings are stored in a file named nhsrv.ini. Default this file is located in the folder “..\Program Files\Aladdin\HASP LM”. By manipulating some of the file parameters, you can control the behavior of the protection system. For example, the NHS_USERLIST parameter is responsible for the maximum possible number of connections to Hasp.

If everything went wrong...

When installing hardware protection, problems often arise that personnel responsible for maintaining 1C products should be aware of:

• Failure to install the security key. Evidence that the device is recognized is a burning light on his body. If this is not the case, then the key driver is probably not installed on the system. You can check whether the driver is installed correctly by entering command line hinstall –info instruction. It is necessary to check whether the user has a sufficient level of privileges to install programs in system folders. You should run the installation with local administrator rights. Sometimes the driver version does not match the operating system version. Another hindrance to driver installation may be that the installation is blocked by a protected application. In this case, perform the installation from the console immediately after booting the system. To do this, type in the command line: hinstall -i –kp;
• The program protection key was not found. The problem occurs when the key is physically missing from the system, when there is no license manager, when Hasp is used of the wrong type, or as a result of port 475 being blocked;
• Installing more than one license manager with the same name. In this case, each license manager needs to be assigned a unique name in the nhsrv.ini file (change the value of the NHS_SERVERNAMES parameter in the NHS_SERVER section);
• An error message appears when you turn off your computer. The reason is that the security driver was activated later than the security server. Change the security server to the LMSETUP security manager service.

That’s probably all a beginner should know about hardware protection in 1C.

Installing and removing the security driver

To ensure interaction of the 1C:Enterprise 8.1 system with a hardware security key, you should install the security driver included in the system delivery package. Availability installed driver protection is necessary when working under the Windows operating system.

Installing the security driver.

To install an anti-tamper driver in the operating room Microsoft system Windows select line Installing HASP Device Driver in Group 1C Enterprise (Start › Programs).

To install the protection driver from the command line, run the program hinstall.exe, placed in the catalog bin, with key -I. Thus, the command line for installing the security driver looks like this:

HINSTALL -I

Removing the protection driver.

If it is no longer needed, the protection driver can be removed from the system. To remove the security driver in the operating system Microsoft Windows select line Removing HASP Device Driver on the menu 1C Enterprise (Start - Programs).

To remove the protection driver, you can also use a command line like this:

HINSTALL -R

Startup sequence

As a result of the installation program running in the menu Start - Programs a program group will be added 1C Enterprise 8.1, shortcuts will be created to launch the 1C:Enterprise 8.1 system in various modes ( Configurator, 1C:Enterprise) And utilities protection server.

To launch the 1C:Enterprise 8.1 system, select the appropriate line in the menu 1C Enterprise 8.1 (Start › Programs).

Before starting, make sure that the client hardware security key is connected to the USB port of the computer (or computer local network in case of an additional multi-user license). The "visibility" of the security key is checked after selecting information base. If the program does not detect the hardware key, a message will be displayed - The program protection key was not found!, and the program will finish. If a protection key is available, but all its licenses have been exhausted, a message appears:

No free license was found in the program's network protection key!

If this message appears when the hardware security key is connected to the computer's USB port, check that the hardware key is securely installed and perform the installation again HASP Device Driver.

1C, like any other program, requires that the user only use licensed versions. To confirm that the program has been officially purchased, use license keys 1C.

This article will discuss the types and features of 1C protection keys, as well as provide answers to frequently asked questions about working with them.

1C supports working with both software and hardware keys. Let's take a closer look at each of these types:

1C protection software key

1C software license- this is a file that is stored on a PC and is involved in the launch of 1C. If the file is activated with a PIN code, then 1C will be launched, otherwise (if it is launched for the first time) you will need to enter the PIN, which is included in the delivery package. The software key is tied to the computer hardware, so periodically, when replacing computer components, you have to reactivate the 1C license.

Conventionally, the 1C software license can be divided into 2 types:

• single-user,
• multi-user.

Single-user license installed on one PC and allows you to use the 1C platform. It is worth noting that the number of configurations and information bases software key does not limit.

Multi-user license most often installed on a server (1C:Enterprise, terminal server, WEB server). When a 1C client accesses a 1C server, the software itself monitors the number of free licenses and allows (or does not allow, if the number of licenses is exhausted) to work with 1C. It is worth noting that a multi-user license for up to 50 users can be activated not only on the server, as a general one, it can be activated on 50 different client computers as 50 single-user licenses. But if at least one license from a multi-user set is activated as a single-user license, then further use of the licenses as a “set” is no longer possible.

Hardware protection key 1C

A more reliable, but at the same time more expensive way to protect 1C are hardware keys. Hardware security keys (HASP key) look like a flash drive and mark 1C as having passed licensing. In this case, unlike software license,The PIN is stored on HASP and not in a file on the computer/server.

There are 4 types of hardware keys, each with a distinctive color and marking:

• Key for one user (local). The key is blue and marked H4 M1 ORGL8. This key comes with products that are licensed for one personal computer.
• Network key. The key is red. The HASP key is inserted into one computer and is visible to all computers on the network. Marked as NETXX ORGL8.., where XX is the number of licenses. There are varieties for 5, 10, 20, 50, 100, 300, 500 licenses.
• Server key for 32-bit server. It is purple in color and marked ENSR8. Always comes with a server license.
• Server key for a 64-bit server. It is green in color and marked EN8SA. Can also work with 32-bit servers.

!!! It is worth emphasizing that 1C specialists do not recommend using a local key and a network key on the same machine. When 1C is launched, the local key will be identified, and the network key will not be used, while all other network users will not be able to “see” the network key and, as a result, will not be able to work in 1C.

1C license manager

When working with a multi-user license, it is necessary for 1C to know about the presence of such a license on the network. The 1C License Manager is responsible for this ( Hasp License Manager). The 1C license manager is additional software (included in the package), without which the multi-user license will not work correctly.

Answers to frequently asked questions about 1C protection keys:

No. 1. 1C does not see the license

In the case of using hardware keys, if 1C does not see licenses, first of all you need to make sure that the indicator on the HASP key is blinking. This is an indication that the device is detected and the HASP key driver is installed. If the light does not light, try connecting the flash drive key to another USB port, or contact system administrator, the user may not have enough access rights to install the driver.

Also, first of all, make sure that the key of the required series is connected to the computer. remember that keys can block each other.

No. 2. The HASP security key driver is installed with an error.

1. Possibly incompatible operating system and the key driver. Try downloading more new version drivers.
2. Driver files may be blocked due to being occupied by another process. Try restarting your computer and installing the driver immediately after loading. Or use the console version of the installation utility with command line parameters: hinstall -i -kp

No. 3. Error: HASP not Found (-3), (Error 7), (H0007)

HASP on the network runs on port 475. Make sure that on the computer with the key, on the computer with running application and port 475 is not blocked on the network. It may be blocked by a firewall or antivirus.

No. 4. HASP Device Driver not installed (-100)

Common Windows error XP. The protection driver loads slower than the protection server from startup. Instead of the protection server, use the LMSETUP License Manager, which is installed, please note, as a Windows Service!

In addition, let’s say that when working with 1C, two or more license managers can function simultaneously, but to prevent errors, each manager must be assigned its own unique name. To do this, use the nhsrv.ini file; you need to change the value of the NHS_SERVERNAMES parameter in the NHS_SERVER section. Moreover, it is necessary to communicate these names to each copy running program. To do this, use nethasp.ini: in the NH_SERVER_ADDR parameter indicate the IP addresses of the servers, in the NH_SERVER_NAME parameter indicate their names in the same order in which the addresses were specified.

If you still have questions about choosing, setting up, purchasing software or hardware, you can always contact our specialists for advice

At the request of our regular visitor to the site, we will publish a short article on how to install and configure the HASP driver emulator to run 1C 8.2 for Windows x64.
We will also analyze the installation and configuration of 1C 8.2 configuration with demo data.

Installation and configuration of 1C 8.2 HASP driver emulator for Windows x64

Operation is guaranteed with a completely clean licensed Windows system ( Windows Vista x64, Windows Server 2008 x64, Windows 7 x64, Windows Server 2008 R2 x64 including with Service Pack 1 installed)
Perform installation under local administrator!

1) Remove the old license manager and HASP driver (Control Panel -> Programs and Features). We also remove all old emulators and platform patches.
2) Disable User Account Control. Start -> Control Panel -> Change User Account Control settings. Set the value to “Never notify” (slider down).
3) Installation of 1C (platform) with the HASP driver or Installation of the HASP driver version with x64 support:

Download HASP Driver with x64 support:

4) Add dumps (the registry branch with dumps has changed) - “Dumps” folder, run and add the file to the registry "v8 50 user.reg" for a workstation, for a server you need to add all files to folder "Dumps"- archive for downloading at the bottom of the article.

5) Launch install_sertif.cmd(installation of personal certificate and enabling test Windows mode ) if you don't want to press F8 every time you start it.

In this case, your OS should boot in test mode - if this does not happen, then when rebooting, you need to press the F8 button and select Test mode with the ability to install drivers with unsigned certificates. The test version is used to install device drivers into the system that are not signed with a certificate. The certificate is issued by Microsoft after the corresponding driver is sent by the device (hardware) manufacturer for testing to a Microsoft laboratory. The absurdity is that no one will issue a certificate for the emulator driver and, accordingly, it is impossible to avoid the test version.

Check: in the lower right corner of the worker Windows desktop must be written in white letters "Test version" Windows 7 Build ???
If this message is not present, then, alternatively, you did not enable test mode, so step 6 may not pass.
You can run bcdedit.exe /set TESTSIGNING ON at the command prompt and reboot.

You also need to repeat removing all patches and HASP emulators found in the system and rerun step 5.
Test mode may not turn on if Windows already is in a different mode, such as Protected Mode.
Some Windows activators put the system into protected mode to bypass the activation mechanism.
In this case, you need to remove this activator and/or update the activator and/or purchase a licensed product.

Don't forget to disable your antivirus; its components often block driver installation.

7) Install the driver
Control Panel -> Add Hardware -> (Control Panel -> Device Manager)
Add a new hardware device -> (Place the cursor on any of the device classes -> Action ->
Install old device ->)
Install the hardware that I manually select from a list -> (installation of equipment selected from
list manually ->)
Show all Devices -> (Show all devices ->)
Have disk -> (Install from disk ->)
Browse -> (Browse ->) path to the directory with files vusbbus.inf, vusbbus.cat, vusbbus.sys

Answer “Yes” when prompted to continue installing unsigned drivers.

8) Device Manager -> System devices should appear "Virtual USB Bus Enumerator"
(Device Manager -> System Devices)

Attention. After installing the “Virtual Usb Bus Enumerator” driver, in “ USB controllers» additional equipment will appear
"Aladdin HASP key" or analogue "SafeNet key"
"Aladdin USB key"
or after a reboot or after clicking Action -> Update hardware configuration

Examination. “Virtual Usb Bus Enumerator” should not appear on the device icon Exclamation point. The device should work normally.

9) Installing HASP LM driver (ONLY for installation on the Windows Server platform). In the archive - at the bottom of the article.

9) To disable the display of messages on the desktop “Test version” you must install "RemoveWatermarkX64.exe". In the archive - at the bottom of the article.

Download the archive with the HASP driver emulator for installing 1C 8.2 on Windows x64:

It is also advisable to prohibit the 1C platform from accessing the Internet (we use a Firewall or a third-party firewall).
That's all 1C Enterprise 8.2 is installed and working.

Installation. Setting up 1C 8.2 configurations

This detailed instructions By installing 1C configuration and creating a 1C database (from the installed configuration). Don't forget that you first need to install the 1C platform. Installing 1C configuration on a computer. Creating a 1C database from the configuration. Creating a 1C database from CF. Creating a 1C database from DT.

What needs to be done to install the 1C configuration?

Configuration 1C- this is a template. Based on this template, a 1C database is created. The number of 1C databases based on one 1C configuration template is unlimited.

Thus, the essence of setting up a 1C configuration is creating a database.

You can create a database in the following ways:

— Install a configuration (template) on your computer and create one based on it

— Create an empty database and load CF into it

— Create an empty database and load DT into it

— Restore the 1C SQL database backup to another database and connect it to the 1C server.

CF and DT are downloading a configuration from an existing database. They differ from each other in that DT includes data, while CF does not (contains only configuration information).

Installing the 1C configuration from the distribution kit on the computer

The configuration distribution package is distributed on disk (select the Install menu item to install) or as a self-extracting archive via the Internet (unpack it anywhere and click setup.exe).

Installing a 1C configuration distribution kit asks only one question - the installation directory. By default, the 1C configuration is installed in the templates directory.
This is a standard directory. For 8.1 it is usually located in “C:\Program Files\1cv81\tmplts\”, for 8.2 in “C:\Users\UserName\AppData\Roaming\1C\1Cv82\tmplts\”.
Change the directory to yours:

As a result of installation, a folder with the installed configuration will appear in the tmplts directory. Inside this folder are folders installed templates configurations. They contain documentation and “additional things”. For the structure of the tmplts folder and a description of the files in the configuration distribution, see the end of the article.

Creating a 1C database from the installed configuration (file version)

The configuration is stored in a directory on disk (the file version, which is what we are considering).

It is necessary to select a location on the disk where we will create the configuration, for example “E:\My_docs\1C\baza\”. Let's go or create this folder and create a database folder in it, for example: “e:\My_docs\1C\baza\torgovlai-dla-fop”.
Let's launch 1C. In the database selection window, click the button Add.

Select “Create a new information base” and click “Next”.

If you installed a configuration (one or more) from the distribution kit, now you will see a list of installed configurations. The following options are available in each configuration:
— Configuration name/version
— Configuration name (demo)/version
The first option is a clean empty database. The second option is a database with demo data for training. We choose the second option (place the cursor on the version number).

Enter the name of the database, it can be anything you understand. This name will be displayed in the list of databases when logging into 1C. For example, “Trade for private enterprises of Ukraine (DEMO)”

You need to select a database location. We are installing the file option, so we select “On this computer...”. When you install the client-server option, select “On the 1C server.” It is necessary to select the same directory that we prepared for the database. Indicated earlier when installing 1C. In our case it is: e:\My_docs\1C\baza\torgovlai-dla-fop

After this, we leave the installation step unchanged:

Tmplts folder structure reminder

1) folder “1C” – 1C company configuration templates
2) folder “Configuration name” – the English name of the configuration (Accounting-Accounting, Trade-Trade Management, Hrm-Salaries and Personnel Management)
3) “Version” folder – configuration version
4) Configuration template folders and files.
For example, the path to the “Trade Management” configuration template version 10.3.9.4:
C:\Program Files\1cv81\tmplts\1c\trade\10_3_9_4\

1) Readme.txt – contents of the directory, what is where
2) HTML files – various descriptions and help for using configurations
3) 1cv8.cf - it is in this file that the 1C configuration is stored
4) 1Cv8.dt – this file stores a database archive based on this configuration, usually a demo database; the file contains both configuration and data
5) 1cv8.cfu – configuration update file, used to migrate from one configuration version to another
6) TTF files – font files, used for example for printing barcodes, please note that these fonts need to be added to the system if they are in the configuration distribution
7) XML files – often various classifiers are supplied with the configuration, we will consider loading them into the database in future releases, please note that these files should also be loaded into the database after it has stopped (for example, okp.xml)
8) ExtReps catalog – external reports and processing used for accounting, often this is how reports are supplied that change frequently, for example various printed forms
9) TradeWareEpf catalog - processing that is used to connect equipment, we will consider connection in future issues
10) Conv_ХХХ directories – such directories store “conversion rules”, the rules by which you can upload data from one database to another

That's all, if you want to “thank” us, you have this opportunity: on the right there are options for donations for the development of the portal. Or share the article on your social media using the services below.