As shown by the reader's response to ours, dedicated to the peculiarities of working 1C Enterprise 7.7 in the Windows 7 (Vista) environment, we have raised a pressing problem. At the same time, the difficulties that our readers have to face begin at the installation stage. Therefore, we decided to fill this gap.

A small lyrical digression or “do you need it?”

Before we begin to consider technical problems, we would like to try to understand the question: “is the game worth the candle?” The question is far from idle. The latest release of 1C Enterprise 7.7 (7.70.027) was released at the end of 2006; in fact, the development of the platform ended two years earlier with the release of the 25th release.

Therefore, we must clearly understand that today we are trying to launch in a modern OS environment an application that was five years old, moreover, it is at the end of its life cycle; the same 25th release, even at the time of its release, was already in many ways obsolete. Therefore you do everything at one's own risk, all possible problems, including plant downtime, data loss, etc. will be exclusively yours, neither 1C nor Microsoft are responsible here and cannot be held responsible.

If your company is seriously planning to migrate to a new platform, especially if you plan to use 64-bit systems, then we advise you to consider the option of migrating to 1C Enterprise 8.1, especially since 1C offers good discounts for upgrades. We tend to consider the use of 1C Enterprise 7.7 in a Windows 7 environment solely as temporary a solution used within the transition period (implementation of 1C 8.1, personnel training, etc.) and is categorically not recommended as a standard solution.

Platform 32 bit

We did not encounter any particular problems with installing release 7.70.027 on 32-bit versions of Windows 7, regardless of the distribution version and component composition. We fundamentally did not consider possible problems with installing previous releases; if you have to use outdated software, then you need to use the most recent version. If you do not have the 27th release, then you can get it from any 1C partner.

The first problem awaits us upon startup; the program reports a missing security key. This is normal, the HASP driver included with 1C is incompatible with new OSs. You need to download the latest version of HASP from the manufacturer's website; for the network version you will also need the latest version of NetHASP License Manager.

Configurations are installed in the same way; we have not had any problems with the latest releases. If you cannot install a release or configuration for some reason, but there is such a need, you can use another method; for 64-bit systems this is the only way to “install” 1C Enterprise. More on this below.

Platform 64 bit

It is impossible to directly install 1C 7.7 on a 64-bit system, this is due to the 16-bit installer that is still used, but the application itself is 32-bit, which allows it to work successfully in 64-bit versions of Windows. 1C Enterprise 7.7 does not store any global settings in the registry, all entries are in the branch HKEY_CURRENT_USER\Software\1C related to the current user (as well as in branches HKEY_USERS for multi-user systems) and contain a list of databases, paths to them and other user settings. If missing, these keys are created automatically the first time you start the program. This allows you to simply transfer the folder with the installed program from one machine to another while fully maintaining the functionality of the application.

To “install” 1C 7.7 on a 64-bit OS, we need a machine with a 32-bit system (Windows XP is best) on which to install the application and the necessary configurations for it. After which the folder with the program (by default C:\Program Files\1Cv77) is copied to the appropriate location in the 64-bit system (by default C:\Program Files (x86)\1Cv77). Then the HASP drivers for 64-bit systems and, if necessary, the NetHASP License Manager are installed. All that remains is to display the shortcuts and work.

But not everything is so rosy. Due to the above features of the installer, you you can't To fully support 1C, update releases and regulated reports, you will have to first install it in a 32-bit environment. In the network version, you should avoid using 64-bit workstations for employees involved in maintenance or programming for 1C.

SQL version

1C Enterprise 7.7 for SQL, of course, can be installed in a Windows 7 (Vista) environment, but the meaning of such an action tends to zero. Windows 7 does not support working with SQL Server 2000, 1C Enterprise 7.7 does not support later releases of SQL Server.

There are two unofficial ways to “cross a snake with a hedgehog”: patch 1C to work with SQL Server 2005 or replace libraries in Windows 7 ODBC drivers responsible for working with SQL, to their counterparts from Windows XP. We We absolutely do not recommend try none of them. The first method is questionable from the point of view of licensing purity, the second threatens the stability of the system as a whole, primarily other applications that use ODBC. In addition, there is a possibility of destruction or distortion of information in the database due to an incorrect request or other non-standard situation, or downtime (which is no better) due to a failure in a “cunning” connection.

Anticipating objections that someone patched it and has been working for a month (quarter, year), we would like to remind you once again that by such actions you are taking to myself all possible liability for any failures, downtime, data loss and other possible emergency situations. No one will figure out what exactly caused the failure. Any qualified specialist will certainly point out the use of incompatible products and wash his hands of it or will work, but at a completely different price (while giving absolutely no guarantees). Are you ready to take on such responsibility? If yes, then don’t say later that you weren’t warned.

It is known that the 1C:Enterprise 7.7 platform has compatibility problems with 64-bit systems of the Windows family (XP, Vista, 7, Server 2003, Server 2008). What should you do if you still need to run this software product on a 64-bit operating system? Next we will look at the solution to this issue.

The essence of the problem lies in the very outdated architecture of the 1C:Enterprise 7.7 platform (it’s time to bury it!). You should immediately give up the idea of ​​installing on a 64-bit operating system using setup.exe. It won't work.
You should do this:

Step 1. Install the 1C:Enterprise 7.7 platform correctly (i.e. in accordance with all books and instructions) on a 32-bit operating system. It is better if it is not a server operating system (so as not to fight with possible problems ahead of time).

Step 2. Copy folder C:\Program Files\1cv77\BIN from a 32-bit system to a folder C:\Program Files (x86)\1Cv77\BIN 64-bit system. Make appropriate shortcuts to the 1cv7.exe (or 1cv7s.exe) file on the user’s desktop.

Step 3. (Step for Windows server operating systems) Add exception to DEP. For this we will open Control Panel –> System–> Tab Additionally

Click on the button Options. A window opens Performance Options. Open tab Data Execution Prevention.

When you first open it, the list will be empty. You should press the button Add and select files 1cv7.exe(or 1cv7s.exe). After this you can accept the changes.
Disable DEP (select option Enable DEP for essential Windows programs and services) not worth it. The purpose of DEP can be found in the footnote below.

Data Execution Prevention (DEP) (English) Data Execution Prevention) is a security feature built into the operating system familyWindows, which does not allow the applicationexecute code from a memory area marked "data only". It will prevent some attacks that, for example, store code in such an area using a buffer overflow. DEP operates in two modes: hardware, for processors, which can mark pages as “not for code execution”, and software, for other processors. This feature first appeared in Windows XP Service Pack 2.

Step 4. Install drivers for the HASP key. You can find drivers for the HASP key for the 64-bit version of Windows on the Aladdin website.
The following drivers should be used:

• Drivers for the key HASP Device Driver 5.22;
• License Manager (for the key to work on the network) HASP License Manager 8.32;

Step 5. Overcome remaining problems when using Windows Vista/7 and Windows Server 2008/2008 R2. You can read about what needs to be done in my post.

ATTENTION! SEVERAL FEATURES!

After publishing this post, I encountered an unpleasant feature. I got my hands (almost simultaneously) on two laptops with the Windows 7 x64 operating system installed. It turned out that single-user version 1C:Enterprise 7.7(in my case the configuration was Accounting) DOES NOT WORK on a 64-bit operating system. No matter what I did, the protection key did not give up and tried not to be detected. Alas, the 1C:Enterprise 7.7 software platform is old and problems like this will never be fixed.

However, during the experiment, it was possible to establish that if a multi-user license is used, working on a computer with Windows 7 x64 installed in 1C: Enterprise 7.7 is possible and everything written above is absolutely true. It is advisable to choose a computer with a 32-bit operating system as a place to place the security key.

The described case can become a serious problem for system administrators when migrating to new equipment. I am inclined to believe that in each individual case it is necessary just test one way or another.

Installing the 1C:Enterprise 7.7 platform on a 64-bit operating system is fraught with some difficulties. The fact is that you won’t be able to install 1C through a regular installer, even if you run the program in . But nothing is impossible. Below are step-by-step instructions for installing 1C:Enterprise on 64-bit Windows, in my case it is .

1. Installation on Windows x32

First you need to install the required 1C:Enterprise platform on any other 32-bit Windows system by changing the default installation path to " C:\Program Files (x86)\1Cv77\"(so that all shortcuts work). I wrote in detail about installing 1C. Then you need to copy the following files to the 64-bit system:

1. Directory " 1Cv77» out of the way
   « C:\Program Files (x86)\» 32-bit system in
   « C:\Program Files (x86)\» 64-bit system.
2. Directory " 1C Enterprise 7.7» out of the way
   « C:\Documents and Settings\All Users\Main Menu\Programs»
   on a 32-bit system
   « C:\ProgramData\Microsoft\Windows\Start Menu\Programs»
   64-bit system
   (Paths may vary depending on the versions of Windows used).
3. Copy file from path
   « C:\WINDOWS\system32\» 32-bit system in
   « C:\Windows\SysWOW64\» 64-bit operating system.

Did this article help you?

Probably many have encountered the problem of installing 1C:Enterprise 7.7 on 64-bit systems. However, this problem can be solved. To solve this, you will need a computer with a 32-bit OS installed.

So, we install 1C on a computer with a 32-bit OS (if you plan to use 1C on a server, select: “Installation on a server - Administrative”). Then we go to C:/Program Files and copy the folder with the 1Cv77 program (say, to a flash drive), after which we insert the flash into a computer running the Vista x64, Windows 7 x64 or Server 2008 x64 system of interest to us and copy the folder with the 1Cv77 program to directory C:/Program Files (x86). Open the 1Cv77/BIN folder, look for the 1cv7.exe file and create a shortcut for it on the desktop.

It is advisable to install the license manager as a service; if you install it as a program, then sometimes crashes may occur during autostart, and the license manager will have to be started manually.

Now we go to the properties of the shortcut for 1C created earlier on the desktop and set it to run as administrator.

Very often, upon startup, an error occurs: “1C multi-user has detected an error, the application will be closed.” And DEP is to blame for this.
Open "System Properties - Advanced System Settings", in the "Performance" section, click the "Options" button - go to the "Data Execution Prevention" tab. Either check the box “Enable DEP only for Windows programs and services,” or add the 1C program (file 1cv7.exe) to the exceptions.
After this, 1C enterprise works great. When installing on a server, you will have to repeat the settings for each user to run as administrator and as for the DEP settings.

If an error appears: “The database sorting differs from the system one” You need to open the database in the configurator. Next "Administration - Code page of information security tables" and change to + current system setting. When asked to re-sort the database, answer “Yes”.

There is one nuance in the problem with the code page - simultaneous work with one database from computers running Windows XP and Windows Vista (Windows 7) is impossible! When connecting to a database either on Vista or XP, an error message will be displayed - the database sorting is different from the system one. Despite the fact that this can be circumvented by simply prohibiting database sorting altogether, I do not recommend doing this; in the event of an emergency shutdown of 1C, this method can lead to unpredictable results, including complete loss of data contained in the database.