Server 1c enterprise 64 bit for windows. Adding a user to MS SQL Server

Beta Menu

Configuring Server 1C: Enterprise 8.3 and PostgreSQL 9.4.2-1.1C. Full instructions

In this tutorial, we will tell (and show) how to set up a bundle 1C:Enterprise 8.3 And PostgreSQL 9.4.2 from the moment of installation of both services, up to the creation of an infobase. You can read about tuning this bundle in.

Steps we have to go through:

  1. Installation Servers 1C:Enterprise(64-bit) for Windows
  2. Installation PostgreSQL 9.4.2-1.1C
  3. Creation of the Information database.

More under the cut!

Stage 0. Input data.

Server name - 1CServer
Server account name - Administrator
Account password - 123456Ab

1C account name on the server - USR1CV8
1C account password on the server - 123456cd

PostgreSQL account name on the server − postgres
PostgreSQL account password on the server - 123456Ef

PostgreSQL superuser name − postgres
PostgreSQL superuser password - 1234

Test database name − testdb

Stage 1. Installation Servers 1C:Enterprise(64-bit) for Windows


Step 2. Installing PostgreSQL and pgAdmin.


Stage 3. Creation of the 1C information base.

  1. Before performing the following operations, disable IPv6 on your network interface: Network and Sharing Center > LAN connection > Properties> uncheck Internet Protocol Version 6 (TCP/IPv6).
  2. We launch the client 1C:Enterprise and add a new database.
  3. Creating a new infobase > Creating an infobase without configuration (for example, you can have any configuration) > On the 1C:Enterprise server >
  4. We fill in all the fields in accordance with our example (Stage 0):
    Server cluster 1C:Enterprise: 1CServer
    Infobase name in the cluster: testbd
    Secure connection: Turned off
    DBMS type: PostgreSQL
    Database server: 1CServer
    Database name: testbd
    Database user: postgres
    User password: 1234
  5. Next, next. We launch the created database in enterprise mode - everything works!

Once again, we remind you that PostgreSQL can be well overclocked. Details in .
And do not forget about 1C!
If there are any problems with the database, you may be able to help.
1C databases are possible!

Do you have any questions?

Something went wrong? The specialists of our company will help you deal with the problems that have arisen! Contact us! →

Installing the 1C:Enterprise 7.7 platform on a 64-bit operating system is fraught with some difficulties. The fact is that installing 1C through a regular installer will not work, even if you run the program in mode. But nothing is impossible. Below is a step-by-step instruction for installing 1C:Enterprise in 64-bit Windows, in my case it is .

1. Installation in Windows x32

First you need to install the required platform 1C:Enterprise in any other 32-bit Windows system by changing the default installation path to " C:\Program Files (x86)\1Cv77\” (for all shortcuts to work). In detail, I wrote about installing 1C. Then you need to copy the 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
    (the paths may vary depending on the version of Windows you are using).
  3. Copy file from path
    « C:\WINDOWS\system32\» 32-bit system in
    « C:\Windows\SysWOW64\» 64-bit operating system.

Did this article help you?

  • tutorial

Good afternoon, the article is written as a kind of continuation of this opus. The 1C company is often criticized, often objectively, but I will try to show by my example that 1C provides freedom of choice, which at the present time at least deserves respect. Let's also count some money.

Prologue.

The main activity of our small company is IT outsourcing. Rather, for marketing and enthusiastic purposes, we create templates for solutions that allow us to slightly standardize the IT infrastructure of the wards, and for the client to receive and, most importantly, realize the savings (if you don’t praise yourself with a report, then no one will notice). Clients - small companies from 20 to 200 people. One of these solutions is the implementation of a 1C enterprise server on the free Linux + Postgres SQL platform. The article will not have another technical implementation, since everything has been chewed and chewed for a long time. There will be only a comparison of the standard offer from 1C franchisees and our economical option for May 2014.

Task number 1.

Transfer the database from the file mode of operation to the SQL version with the possibility of using up to 20 clients.

Calculation of two options.

We do not support 1C, therefore all recommendations: about the need to switch from a file base to SQL, purchase licenses, a hardware complex, the client receives from the franchisee accompanying him 1C. Then a consultation with us takes place, we offer an alternative solution based on 1C + Linux + Postgres SQL, and we implement it ourselves.

Offer for 20 users.

Name
1C licenses
- 86400
103700 -
Client license for 20 workplaces 1C: Enterprise 8 (USB) 97600 -
1C: Enterprise 8. Client license for 20 workplaces - 78000
SQL licenses
13381 0
Client access for 20 workstations to MS SQL Server 2012 Runtime for 1C: Enterprise 8 117748 0
Total 332429 164400
Saving 168029

Explanations and nuances:

  1. 1C implementers (of course, there are others in the universe who are trying to save money for the client, but we haven’t come across such ones) offer USB option keys by default, they are significantly more expensive than file licenses. Naturally, the choice of key type does not depend on the implementation platform in any way. It turns out that a trick is made in favor of the Linux platform in the table. Nevertheless, let me remind you that we are not talking about a scrupulous evaluation of proposals, but about a fresh example from practice. For the sake of objectivity, I must clarify that, in my opinion, the implementers are inclined in favor of USB keys not in order to increase costs, but for the sake of reliability of use and ease of further maintenance, “especially” when it comes to implementation on Linux + Postgres SQL.
  2. Often, we also purchase a 1C key for small companies: Enterprise x86, not 64. At the same time, Postgres SQL uses the 64-bit version, and 1C Enterprise Server is 32-bit. Application on the scale of organizations up to 60 people, we consider it acceptable, the thesis is subjective.
  3. Labor costs not included. In our case, it is included in the service contract, therefore it is equal to zero for the client. We will assume that the implementation and further support are approximately the same.

Task number 2 + bonus from 1C

Transfer the database from the file mode of operation to the SQL version with the ability to use up to 10 clients.

Offer for 10 users

Name Standard offer 1C franchisee Windows + MSSQL (rub.) Linux + Postgres SQL Sanity Option (RUB)
1C licenses
1C: Enterprise 8.3. Server license (x86-64) - 0
1C: Enterprise 8.3. Server license (x86-64) (USB) 103700 -
Client license for 10 workplaces 1C: Enterprise 8 (USB) 51900 -
1C: Enterprise 8. Client license for 10 workplaces - 41400
SQL licenses
MS SQL Server Standard 2012 Runtime server license for 1C:Enterprise 8 users 13381 0
Client access for 10 workstations to MS SQL Server 2012 Runtime for 1C: Enterprise 8 58874 0
Total 227855 41400
Saving 186455

Addition to the nuances from example No. 1

  • Good 1C allows you to use a 1C enterprise server on Linux for 12 clients without an enterprise server key, there is no such thing for Windows. The bonus is doubtful, because 10 users will be able to survive on the file one, but still pleasant.

Outcome.

Often, saving within the framework of our country ruins any good systemic undertakings. It seems to me that this case is still from a different category. Three years ago, when we introduced the 1C enterprise server on Linux as a standard for our companies, we really, without false concern, heard from 1C implementers that they disclaim responsibility for the performance of the supported configuration on such a non-kosher Linux + Postgres SQL bundle, with thus introducing the client into a state of panic.
It is possible that a dozen more critical arrows can be shot into the calculations I have given, it is difficult to claim objectivity, but I wanted to convey a general idea of ​​​​the financial component of the issue.

UPD. from Thug21
client software and hardware licenses are consumed differently in client-server mode.
-Software consumed per connection
-Hardware on the computer.

UPD from [email protected]
the technical ability to work without a key does not mean legal permission to do so. The law on the legal protection of information for computers prohibits the use of any software products, the copyright holder of which does not declare them free (and we have not declared this server free anywhere).
Best regards, Sales Manager Viktor Bykov
We kindly ask you to save the history of correspondence for future calls.

50400 RUBBuy
  • 60500 RUBBuy
  • RUB 86400Buy
  • 50400 RUBBuy
  • 60500 RUBBuy
  • What is the difference between versions
    "Server 1C enterprise (x32) 8.2" And " Server 1C enterprise (x86-64) 8.3" ?

  • Load requirements for working servers can be set remotely
  • Remotely set and change the load on production servers
  • Automatic "thin client" update for application users
  • Support for popular secure Internet connections
  • Working with Linux OS
  • Optimized and accelerated work with databases and files
  • Add-ons for working with mathematical functions
  • The x64 server has one fundamental difference: the amount of available address space. The x32 server has up to 2 GB of address space available per worker process. The x64 server does not have this limitation. This gives the x64 server the following benefits:

    • 1. Significantly larger scalability limit.
      The x64 server will stably withstand a greater increase in the load on the system (an increase in the number of simultaneously working users, an increase in the intensity of work, etc.).
    • 2. Longer period of work without reboot.
      At a certain intensity of work, the x32 server may require a periodic reboot to eliminate the effect of memory fragmentation. The x64 server can work without a reboot for almost unlimited time.
    • 3. Better utilization of the RAM of the computer running the 1C:Enterprise server.
      One x32 server worker process has 2 GB of address space available. If your computer has more RAM installed, you will need to create an appropriate number of worker processes to use it. An x64 server can use an almost unlimited amount of RAM with a single worker process.



    When working simultaneously on the same platform 1C: Enterprise 8 more than 15 users, it will be more efficient to use the client-server mode of operation (SQL). Why, besides the server itself, you need to purchase licenses for the server 1C Enterprise 8. In the client-server mode of operation, the price of licenses increases compared to operation in file mode, which is associated with the development of client-server solutions jointly by 2 companies: Microsoft and 1C.


    Using licenses for server 1c enterprise 8 the client-side application interacts with the 1C server cluster. The cluster, in turn, sends a request to the database server (PostgreSQL or MS SQL Server). Moreover, the 1C:Enterprise 8 server cluster and the database server can be physically located on different computers. This allows the administrator to distribute the load between servers.


    The most resource-intensive data processing tasks can be transferred to a 1C:Enterprise 8 server cluster. In this case, even when executing fairly complex queries, the client-side program will receive only the necessary selection, and all intermediate data processing processes will be performed on the server. It is usually much easier to increase the capacity of a server cluster than to upgrade the entire fleet of user computers.


    One of the main advantages of using a three-tier architecture is the ease of managing and distributing user access rights to the database. Moreover, the user does not have access to information about the physical location of the platform or database. Access is made through a cluster of 1C:Enterprise 8 servers. When requesting a database, the user only specifies the name of the cluster and infobase and enters the username and password.

    1C:Enterprise 8 uses MS SQL Server for efficient data sampling:

    • the query mechanism assumes the maximum use of MS SQL Server to perform calculations and generate reports
    • large dynamic lists are processed without performing a large number of queries to the database, and the user has the ability to efficiently search, filter and sort.

    The process of deploying the client-server version of work and its administration is quite simple. The database is created directly when the configurator is launched. The distribution package of the program contains an application for administering the client-server mode of operation, which allows the administrator to configure and manage databases and user connections.

    Server 1C:Enterprise 8 (x86-64)

    A 64-bit 1C:Enterprise 8.2 server is required for the x86-64 architecture (EM64T, AMD64) to work under Windows and Linux. The main advantage of the 64-bit 1C:Enterprise 8.2 server is the practically unlimited address space allocated to the worker process, which allows you to almost fully use the server's capabilities.

    To interact with a 64-bit 1C:Enterprise 8.2 server, a 32-bit 1C:Enterprise 8.2 application can be used on the user side. 1C:Enterprise 8.2 servers (32-bit and 64-bit) work with both 32-bit and 64-bit databases.

    The supply of a license for the server 1C:Enterprise 8 (x86-64) includes

    • Distributions of the 1C:Enterprise client application, 1C:Enterprise server for Linux and Windows (32-bit and 64-bit)
    • PostgreSQL distributions (32-bit and 64-bit)
    • usb security key
    • The book "1C: Enterprise 8.2 client-server (x86-64). Features of installation and use"
    • License agreement for the use of the server 1C:Enterprise 8 (x86-64).

    Features of using a license for a server 1C: Enterprise 8:

    • the use of a server license is allowed only within the same local network with the basic delivery
    • Physically 1C:Enterprise 8 server license is a hardware dongle (USB)
    • The protection key works with both 32-bit and 64-bit 1C:Enterprise 8.2 servers, and also supports 1C:Enterprise 8.1 and 8.0 servers.
    • Server license 1s does not increase the total number of user workstations, which is determined by the number of client licenses in the local network
    • The server license does not apply to base versions.

    Do I need to replace 1C:Enterprise 8 client licenses when moving from a 32-bit to a 64-bit server?

    If a user already has a license for a 32-bit 1C:Enterprise 8 server and needs to buy a 64-bit 1C server, then 1C:Enterprise 8 client licenses are not replaced. You can purchase a license for a 64-bit 1C: Enterprise 8 server according to the scheme by replacing an existing license with an x86-64 server license.

    Installing a 1C Enterprise server on the Windows platform is a simple and intuitive task that even an inexperienced administrator can handle. However, we decided to devote a couple of lines to it in order to bring final clarity to this issue and give our cycle completeness and completeness.

    As you know, repetition is the mother of learning, updating knowledge is always useful, especially since sometimes the installation of a 1C Enterprise server turns into a hodgepodge of all kinds of components, half of which are not needed on the server.

    Let's talk about versions first. At the moment, 1C offers a server in two editions of 32 and 64 bits, which differ primarily in cost of 42,000 and 72,000 rubles. It should be remembered that a license for a 64-bit server gives the right to use the 32-bit version, but not vice versa. For normal operation of the 1C Enterprise server, the security key must be physically connected to the server, however, to successfully launch application solutions, you will need a network key for the required number of users, both keys can be physically located on the same server, they do not interfere with each other. More about keys.

    A widespread mistake is installing the wrong version of the server when a 64-bit server is installed on a 64-bit server OS with a license for 32-bit. Therefore, before installing, carefully check which version you have purchased.

    To install the 32-bit version of the server, the same distribution kit is used as for installing the client part. Run the installer and carefully examine the window of available components:

    The first three points do not interest us - these are various options for client platforms that are not needed on the server. I think it is unnecessary to say that you should not combine the role of the 1C Enterprise server and the role of the terminal server. The only role that the 1C server can be combined with is the database server, provided there is a small load and sufficient resources that are correctly distributed between the roles. First of all, it is necessary to limit the appetites of the DBMS regarding RAM and it is highly desirable to store the database on a separate disk array.

    Main component - Server 1C:Enterprise, it seems to us redundant to clarify its purpose. If you intend to use a web server or thin client over the Internet, you should install Web Server Extensions, component 1C:Enterprise server administration is not mandatory, it can (and should) be installed on the administrator's workstation.

    With a simpler 64-bit version, this installation package contains only the 1C Enterprise server:

    As you can see, the 64-bit distribution does not contain the server administration component; if necessary, it should be installed from the 32-bit distribution.

    If the localization of your OS does not match the language of the 1C interface, then do not forget to additionally install the necessary ones and explicitly select them in the next step. For example, when installing the Ukrainian version of 1C on the Russian localization of the OS.

    To start the services of the 1C Enterprise server, you can use the Administrator account or, which will be more correct and safe, a special account USR1CV82. If this account does not exist, you will be prompted to create one during installation.

    When setting a password, remember that it must comply with the requirements of the security policy, otherwise you will receive an error 8007056B / 800708C5, in which case you will need to set a new password for this user manually. A blank password is also not allowed, even if your security policy allows it.

    Another possible error is an incorrectly specified password for an existing account, this usually happens when updating the platform, in which case you will receive an error:

    Two options are possible here. If you remember the password, abort the installation and restart it with the correct password. Otherwise, click Skip and change the user password USR1CV82 the one you specified during installation. Then start the service Server agent 1C:Enterprise 8.2 manually.

    Also, do not forget that the platform versions of the server and the client must match, and the next step should be to install (update) the client platforms. If you need to update the server version, we advise you to first uninstall the previous one via Installing and uninstalling programs and only after that install the new version, all settings will be saved.