Parallel launch of several servers "1C: Enterprises" of different versions on one computer. Parallel launch of several servers "1C: Enterprises" of different versions on one computer 1c enterprise 8.3 Application server

The "1C: Enterprise" system in addition to the file option can work with information bases and in the client-server version. In the latter case, an architecture consisting of several program levels, schematically shown in the figure below.

Client Applications, Thin Clients and Web Customers - This is "1C: Enterprise" in various launch modes with which the end user works. For client applications and subtle customers, users are required (or on), a web browser is enough for a web client.
Cluster of servers "1C: Enterprise" It is a combination of workflows operating on one or more computers and the list of information bases that are placed in this cluster. The server cluster performs all the work of the application objects, prepare for the display of forms (reading objects information base, filling out these forms, location of elements, etc.) and command interfaceThe reports are formed, background tasks are performed. On clients only the display of information prepared in the server cluster. In addition, service files are stored on the 1C: Enterprise cluster server, as well as the information base registration log.
Database server - On the database server, there is direct storage and work with data provided by one of the following supported by the "1C: Enterprise" system, database management systems (DBMS):
- Microsoft. SQL Server beginning with microsoft version SQL Server 2000 and above;
- PostGragesQL starting with version 8.1;
- IBM DB2 starting with version 9.1;
- Oracle Database starting with version 10G Release 2.
Web server. It is necessary only for the work of web clients and one of the work options for a thin client. Provides the interaction of these types of connection with a cluster of "1C: Enterprises" servers.

It is also worth noting that it is not necessary to each programmatic level should be located on a separate physical computer. The server cluster can be located on one computer with a database server, a web server, etc. For example, in small organizations, the following work structure is found in small organizations:

In this article, I will describe the installation of the server "1C: Enterprises" version 8.3.4.389 (for other versions of the 1C: Enterprise platform 8.1, 8.2 and 8.3 actions are similar) to one computer under windows control Server 2008 (R2) or Windows Server 2012 (R2). Microsoft SQL Server 2008 (R2) or Microsoft SQL Server 2012 will be considered as a DBMS. For this we need:

A computer that meets the system requirements for installing the Server "1C: Enterprise" and with the OS or installed on this computer.
Computer for database server, also running OS or (can be a computer from claim 1).
Local administrator rights on both computers.
Distribution for installing the server "1C: Enterprises" 8.
Software license or HASP4 NET protection key for 1C: Enterprise Server.
Distribution for installing Microsoft SQL Server 2008 (R2) or Microsoft SQL Server 2012.

2. Installing MS SQL Server DBMS

Install MS SQL Server DBMS on a computer that serves as a database server. For the operation of the system "1C: Enterprise" is enough installation components:

Database Engine Component Services (Database Engine Services)
Management Tools - Basic (Management Tools - Basic)
- Controls - full set (Management Tools - Complete).

Sort parameters choose " Cyrillic_General_ci_as." Details about the installation of systems

3. Configuring Windows Firewall for DBMS

If the database server and the "1C: Enterprise" cluster server are located on different physical computers, you need to configure Windows Firewall on the database server so that the server "1C: Enterprises" can work with DBMS, namely, open incoming port connections 1433 (For instance of SQL Server by default).

In detail about configuring Windows Firewall for Microsoft SQL Server 2008 (R2) / 2012, I wrote.

4. Adding a user to MS SQL Server

Next, add a separate user to MS SQL Server, under which the server database "1C: Enterprises" will be connected. This user will also be the owner of these databases. The added user must be logged on on the server using a password and have role set: dbcreator, processadmin, public. Details about adding a user to

Microsoft SQL Server 2008 (R2) I wrote.
Microsoft SQL Server 2012 I wrote.

5. Installing Server "1C: Enterprises"

Now go to the installation of server files "1C: Enterprises" and the launch of the relevant service. For installation requires the distribution of the technological platform "1C: Enterprise". From the list of supplied distributions are as follows:

Technological platform 1C: Enterprises for Windows - Allows the installation of a 32-bit server "1C: Enterprises"
Server 1C: Enterprises (64-bit) for Windows - allows the installation of both 32-bit and 64-bit servers "1C: Enterprises"

(There is also an extended version of Server Corp 1C: Enterprises 8.3, details can be found on the 1C site)

Open the directory with the server installation files "1C: Enterprises" and run the file setup.exe..

Start the installation assistant "1C: Enterprise" system. On the first page we click Further».

On the next page, you must select those components that will be installed, we need components:

Server 1C: Enterprises - Server components "1C: Enterprises"
Administer Server 1C: Enterprises 8 - Additional components to administer the "1C: Enterprises" cluster

The remaining components (the list of components may depend on a specific distribution), depending on the need, can also be installed on this computer. Making a choice of clamp " Further».

Select the language of the interface that will be used by default, and click " Further».

If the server "1C: enterprises" is set as a Windows service (as well as in most cases, it should be installed) I recommend immediately create a separate user, from which the service being created will be launched. For this

Leave the flag on Install server 1C: Enterprise as windows service (recommended)»;
Transfer the corresponding switch to " Create a user usr1cv8.».
We enter 2 times the password for the user being created. By default, the password must respond to politicians. windows passwords. You can read more about this:
- For Microsoft Windows. Server 2008 (R2) -;
- For Microsoft Windows Server 2012 -.

You can also select an existing user to start the 1C: Enterprise Server. In this case, the selected user must have rights:

Login as a service (log on as a service)
Log in as a batch job (log on as a batch job)
Performance log users (Performance Log Users).

Also, the user must provide the necessary rights to the server service file directory (default C: \\ Program Files \\ 1CV8 \\ Srvinfo for 64-bit and C: \\ Program Files (x86) \\ 1cv8 \\ srvinfo For a 32-bit server).

Created automatically user Usr1cv8. will have all the rights listed.

By filling out the corresponding parameters, click " Further».

Well, finally click " Set»In order to start the installation. This will copy files selected components, creating configuration files, registration of the components of the program, creating shortcuts, as well as the launch of the Server Service "1C: Enterprise".

Upon completion of the installation, the assistant will propose to install the Protection Driver - HASP Device Driver. If a software license is used to the server "1C: Enterprise", it is not necessary to install the driver. We leave or remove the flag " Install Protection Driver"And click" Further».

Installing the technological platform and applied solution on a local computer or laptop is simple and understandable. This requires to purchase a licensed version of one of the configurations, which comes installation disk With step-by-step masters of installing the platform and directly the user's program.

Installing the technological platform and configuration on the local disk

Since no 1C applied solution can work without its engine - platform - installation on a local computer is divided into two principal steps:

Step-by-step guide, how to set 1C, is described in detail in the documentation attached to each licensed version of the typical or sectoral configuration. The exact following of its instructions will allow you to install yourself and without difficulty.

Installing Server 1C: Enterprise on MSSQL

To understand the following above, it is necessary to clarify two concepts:

client - personal Computer or software, a network unit that generates requests to the server in order to obtain or process any data;
server - powerful computer With significant production capabilities or software that makes answers to customer requests.

Client-server architecture involves the interaction of the client application with the information database server by means special applications - Servers 1C: Enterprises.

Installing MSSQL on the server machine is described in many manuals with possible variability depending on the SQL version and version of the server operating system. In the general case, set 1C to the server, following step-by-step actions:

In the existing distribution, you need to start the setup.exe installation file (for continuation, Microsoft.Net Framework and Operational windows Installer Installer):
Several options for the further development of events are offered: primary installation, modification installed components, update or their search. At this stage, the program checks compliance minimum requirements MSSQL to the operating system:

You must enter the product key received when purchasing a licensed program. After attentive and thoughtful reading the license agreement on english language It is necessary to establish its consent in the form of a check mark:

The transition to the next step is carried out when the Next button is pressed ("Next").

When you click on the Install button, a variety of settings are offered, checkboxes in which are installed as needed: You can select all (Select All) or only the most necessary (DatabasengineServices, ClientToolSConnectivity, ManagementToolBasic with the inclusion of subordinate components):
Settings on subsequent steps It is recommended to leave the default, the transition is carried out by the Next button:
Select user data storage directories (SQL 1C base), logs, temporary files and files reserve copy Information bases (backups).
The next step adds the current user who will have the system administrator rights (Add Current User button):
Settings on subsequent pages remain default if the situation does not require otherwise. When you press the Install button, the direct installation process starts: the color ruler shows the dynamics of the procedure performed. After the installation is successfully completed, the appropriate message will be issued and only to close the installer by pressing the Close button (close).

If the installation of the server part with such a multitude of settings seems sufficiently difficult, then it should contact it to execute it system administrator local network.

Installation of the 1C technological platform: Enterprise to the server

Installing the required platform configuration, in fact, much different from the usual, then only the exception that at a certain step it is necessary to select the setting of the component: "Server 1C: Enterprise" and "Server Administration 1C: Enterprise":

On the following page of the installer, you must select the default interface language, select the existing or create a new user to identify when the service is started. Connection security is guaranteed by entering a password with its confirmation.

When you click on the "Set" button, the installation process "1C: Enterprise" to the server will be launched:

In the future, the need to install the protection driver in the case of purchasing delivery with hardware key or activation of a software license will be requested. When successful installation Technological platform 1C: Enterprise 8 will be issued a system message.

Creating an information database on the SQL server

Creating a new information base in the launch window is no different from creating a base on local computer Up to the time of choosing its location. For server you need to choose:

Next, you should fill out all the necessary fields of the settings of the information database: Database name and its name in the server cluster, IP cluster of 1C servers: enterprises and database servers, database management system (DBMS), etc.:

Following the following steps with default settings, the final action will be created on the SQL information database server.

Installing the client program

To be able to work with an information SQL-base, it is necessary to correctly connect it on client stations. Sequence of this connection:

If the settings for creating an information base on the 1C server were correctly indicated: the enterprises are correctly configured to configure 1C client when you start the program from the client workstation A connecting to the server machine will be connected.

Consider the option of installing a server that uses software license. This method is equally suitable for ubuntu servers 16.04 and for Ubuntu 18.04 (which only happens x64)

Inputs

Used OS: Ubuntu 18.04 x64
Used version 1C: 8.3.12.1412 (you will most likely be different)
Server Characteristics 1C: 8 VCPU + 32GB random access memory + 50 GB disk space
Characteristics of test benches:
1. ESXI1.
  - CPU: 2x Intel (R) Xeon (R) CPU E5-2680 V2 @ 2.80GHZ
  - vCPU: 40.
  - RAM: 256GB.
  - RAID 0 of 10K SAS
  - Ethernet 1Gbit.
2. ESXI2.
  - CPU: Intel (R) Xeon (R) CPU E5-2660 @ 2.20GHZ
  - vCPU: 32.
  - RAM: 96GB.
  - 10K SAS without RAID
  - Ethernet 1Gbit.
The database serves Postgres 9.6.6-1.1s from 1s.

For tests, 2 blades of one model specially selected. Since blades without additional extensions have a physical limitation of 2 disks on the blade, we cannot test various configurations. disk storage Without constantly not to reconfigure it. Therefore, we will have 2 bees, the 1st blade will have a Raid 0 of two 10K SAS drives, the second will be not combined into a 10K SAS and 7200 SAS raid. The only differences in addition to the already described already described, are models of processors and memory. Also, 2 blades will allow in the future to organize more believable scenarios for testing all sorts of clusters and migration.

Install Server 1C 8.3 on Ubuntu

It is understood that Ubuntu Server 18.04 x64 you have already installed. If not, you need to install Ubuntu Server 18.04 x64. You can also desktop ubuntu, the instruction is suitable for the server and for the desktop version, but the meaning of the installation of the desktop version for the server functional is categorically absent.

Connect to our server via SSH
We update Ubuntu Team

Sudo Apt-Get Update && Sudo Apt-Get Dist-Upgrade -Y
We set the libraries necessary for the server 1C

Here the question is quite thin, each library is needed to implement a specific functionality and if you do not use this functionality, you can not install this library.
Documentation on the ITS portal K 1C: Enterprise 8.3.12 -\u003e Client-server option. Administrator's Guide -\u003e Chapter 1 -\u003e Item 1.3. General requirements for client-server versionhe tells us that for a different functionality, the 1C server requires the following libraries.
Pour the archive with the server 1C

Archive downloaded from the site 1C will be called deb64.tar.gz. . Pour the archive with the server packages on Ubuntu in the folder / TMP.
1. Alternatively, you can connect from Wend to our SFTP server through WinSCP
2. You can raise any server inside the network and download the archive with the WGET
Remove the archive
Install 1C Server Packages

Now, in order to install the 1C server, it will be enough while in the / TMP folder, provided that there are files with the 1C server, execute the following command:

sudo dpkg -i ./1c-e*.deb

Those who are interested in a little matching, read this item further. The rest must be followed by the next item.
Actually, why did it work out without any problems install all 6 packages with one command?
- DPKG command processes all packages in the same order in which they displays the LS command or LS -L
- This happened according to a pure chance or by the will of the great admin gods, but the packages retrieved from the archive located in alphabetically arranged in such a manner that when installing each package, all previous packages from which it could depend already installed.
- If suddenly the order of packages will once change, then put them in the following order:
  1. cOMMON - independent of anything
  2. cOMMON-NLS - Depends on Common
  3. server depends on COMMON
  4. server-NLS - Depends on Server
  5. wS - Depends on Server
  6. wS-NLS - Depends on WS
- So you will not be able to install the WS package until you install Server, which in turn requires COMMON
- * -Nls bags - language packages. If you do not need the functionality that they provide them can not be installed. Someone may argue, I have all the servers work without NLS packages. The choice is yours. For the cleanliness of subsequent experiments, I will put all packages.
Run the server 1C.

Server 1C 8.3.12 For Linux it does not start automatically after installation, you can make sure that you can perform any of two commands:

systemCTL Status SRV1CV83.
Service SRV1CV83 Status.

The result will be the following message:
To start the server, you need to execute one of two commands.

Prehistory ... In our company, 1C is successfully operating: Enterprise version 8.2, in which there are about 100 intensively used accounting bases. Under this case, a separate server with rather impressive characteristics, because During operation, it turned out that the bunch of 1C: an enterprise 8.2 + MS SQL 2005 is very demanding to such iron resources, like hard drives, processor, and most importantly - the number of RAM. The cost of such a server for us exceeded 250 thousand rubles (not counting licenses both on the OS and on 1C itself).

To allocate separately "iron" under 1C: Enterprise version 8.3 considered it unreasonable, to the same way to pay more than 100 thousand rubles for the second set of keys for the 1C server, well, very considerable! An attempt to establish "in the forehead" 1C: Enterprise version 8.3 led to the fact that a cluster was lost with existing bases. This is where the features of the installation and launch of two server versions of 1C are revealed: enterprises on one computer.

Installation program 1C: Enterprises 8.2 and 8.3 Adjusts software to use its standard ports: 1540 (used by the server agent), 1541 (used by the Cluster Manager), 1560-1591 (port range used for workflows). Therefore, if the server 1c: Enterprise 8.3 should work simultaneously with the server 1c: enterprises 8.2, then the first must specify ports other than those that already use the working instance of the previous version server.

On a computer with an already installed server 1C: enterprises version 8.2 registered and running the service "Server 1C: Enterprise 8.2" service, which already uses the above standard ports. If you installed "next" server 1C: Enterprise 8.3, then the start of its service "Server 1C: Enterprise 8.3" will end emergency, because He will try to use already "busy" ports. To avoid this, you must do the following.

(All described below is fair for Windows Server 2008 R2 Enterprise (and Standart) 64 Bit + SP1 and 32-bit server versions 1C: Enterprise 8.2 and 8.3).

1C: Enterprise 8.2 (version 8.2.19.90) I was installed as a Windows service with rights to run on behalf of an existing local user "Administrator".

At the end of the installation in the window Server Manager -\u003e Configuration -\u003e Services We see the running service "Server 1C: Enterprise 8.2":

launched with parameters:

C: \\ Program Files (x86) \\ 1cv82 \\ 8.2.19.90 \\ bin \\ ragent.exe "-SRVC -Agent -Regport 1541 -Port 1540 -Range 1560: 1591 -D" C: \\ Program Files (x86) \\ 1cv82 \\ Server 1C: Enterprises 8.3 (version 8.3.4.437) I was installed in the same way:

However, as we see in the window

, Service "Server Agent 1C: Enterprise 8.3" did not start: Server Manager -\u003e Configuration -\u003e ServicesNow we need to open a command line window.

cmd. and go to the bin directory of the installed server version 1C: enterprises 8.3 and try to delete the service of the service "Agent of Server 1C: Enterprise 8.3" team RAGENT.EXE -RMSRVC: C: \\ Users \\ Administrator\u003e CD C: \\ Program Files (x86) \\ 1cv8 \\ 8.3.4.437 \\ Bin C: \\ Program Files (x86) \\ 1CV8 \\ 8.3.4.437 \\ Bin\u003e Ragent.exe -RMSRVC Error! ControlService Error!

I jumped out

Error error ! ControlService Error! that in principle is expected, because The service was properly registered in the system. But in fact, he must be removed. In the windowYou will no longer see it. Server Manager -\u003e Configuration -\u003e Services Now you need to re-register

This server but at the same time, specify ports other than those who already use Agent 1C: Enterprises 8.2. In my case, the team will look:C: \\ Program Files (x86) \\ 1cv8 \\ 8.3.4.437 \\ bin\u003e

-Port 2540.

- the port on which the 1C server agent will work: Enterprise version 8.3; -Regport 2541.
- The port through which the 1C server cluster is administered: Enterprise version 8.3;
-Range 2560: 2591 - range of ports for workflows;
-B "C: \\ Program Files (x86) \\ 1cv8 \\ srvinfo" - Catalog for storing information about the new Created Cluster of Server 1C: Enterprise version 8.3;
-USR. \\ Administrator - The user, on behalf of which will be launched by the server of Server 1C: Enterprise version 8.3;
-PWD ******** - Password for the specified user (enter your).

After that, you will again see the service "Server 1C: Enterprise 8.3" in the window Server Manager -\u003e Configuration -\u003e Services. You just have to run it with the team ragent.exe -Start:

C: \\ Program Files (x86) \\ 1cv8 \\ 8.3.4.437 \\ bin\u003e ragent.exe -start

In the window Server Manager -\u003e Configuration -\u003e Services We see the service "Server 1C: Enterprise 8.3":

launched with parameters:

where the field "executable file" has a setting:

C: \\ Program Files (x86) \\ 1cv8 \\ 8.3.4.437 \\ bin \\ ragent.exe "-SRVC -Agent -Regport 2541 -Port 2540 -Range 2560: 2591 -D" C: \\ Program Files (x86) \\ 1cv8 \\ And now the most interesting thing is: you have to do this operation every time you need to update the version of the server 1C: enterprises 8.3! "Bravo", developers ...

Now a little about how to live with the specified bundle. Need to run the 1C program itself: the enterprises of the old version (from the folder C: \\ Program Files (x86) \\ 1CV82 \\ COMMON) is no longer. When installing 1C: Enterprise version 8.3 The label on the desktop will automatically be restarted on the start of the program from the C: \\ Program Files folder (x86) \\ 1CV8 \\ COMMON. If you open an accounting database running on Server 8.2, it will automatically open in

The desired version thin client. Templates for creating databases (accounting or zick) are placed by default in the user directory, on behalf of which you launched them. If you do this on behalf of the administrator, you will find them along the path C: \\ Users \\ Administrator \\ APPDATA \\ Roaming \\ 1C \\ 1CV8 \\ TMPLTS. If you want to add a new database based on the installed template, the thin client version 8.3 will see them all:

Now, if you need to register a database version 8.3, then you will need to specify in the "Cluster of Servers 1C: Enterprise" computer, with the 1c version 8.3 server and via a colon of the cluster manager that you specified when registering the 1C version 8.3 server. In my case - it is 2541:

When you add a new accounting list of the new ones on the enterprise server running 1C: Enterprise version 8.3 You also need to specify the server name, and through a colon - the port used by the cluster manager:

The need to register the utility to administer the cluster of both 1C server (both version 8.2 and 8.3) after each installation / update is saved.

We now move on to the administration of clusters running various versions of 1C servers: Enterprise on one computer. Open the folder on the path C: \\ Program Files (x86) \\ 1CV8 \\ COMMON, and create a cluster administration on the console on the desktop for the console. Provide 8.3 (label is better immediately renamed correctly, for example 1CV8.3.):

In the same way, open the C: \\ Program Files (x86) \\ 1CV82 \\ Common in the Explorer, and create a cluster administration on the console on the desktop for the console (the label is better immediately renamed, for example, 1CV8.2.):

On the desktop you will receive the following:

Let's start the Utility Administration of the 1C server cluster: Enterprise version 8.2 "1CV8.2" label (since the server uses the default ports, the cluster will appear without problems):

When you try to open this cluster from the console, designed to administer the 1C server cluster: Enterprise version 8.3 (on the label from the desktop with the name "1cv8.3") you will see an error:

Connection error 1C: Enterprises 8.3: Versions of the client and server (8.3.4.437 - 8.2.19.90), client application: cluster console

To display the 1C server cluster you need: Enterprise version 8.3 It is necessary in this snap to create a new central server 1C: enterprises 8.3:

in field Name You must specify the computer name with the 1C server installed: Enterprise 8.3;
in field IP port You must specify the port on which the server Agent 1C: Enterprises 8.3, which you denote when setting up the agent starter;
in field Description Description.

After pressing the "OK" button you can see your new cluster, which turned out after installing the server 1C: Enterprise version 8.3.

Those. Administration of clusters of various versions of Server 1C: Enterprises installed on one computer are carried out by appropriate snaps.

That's basically it. Good luck!

_________
UPD. As practice has shown, the method described in this article is not suitable for simultaneous startup on one server of several instances of the server 1C: enterprises version 8.3. When trying to create a new service agent 1c from another version 1C: Enterprises operating on other ports, operation:

C: \\ Program Files (x86) \\ 1cv8 \\ 8.3.4.437 \\ bin\u003e ragent.exe -insrvc -port 2540 -Repport 2541 -range 2560: 2591 -d "C: \\ Program Files (x86) \\ 1cv8 \\ srvinfo" usr. \\ Administrator -PWD ********

ends with the fact that the already working service is removed old version 1C 8.3, and the new is not created.

I described how to install, create appropriate and run on one server multiple versions of Server 1C: Enterprises 8.3 ...

In the current article, consider the process of starting and setting up the parallel operation of several servers "1C: enterprises" of various versions (relevant for versions 8.1 , 8.2 and 8.3 ) On one computer. IN this example The server "1C: Enterprises" 8.3 will be launched with the server version 8.2, but the article will be relevant for other similar situations, for example, when starting the server "1C: Enterprise" version 8.1, when the server is running version 8.3 or launch two servers of various digits.

1. Statement of the task

Suppose there is a working server "1C: Enterprises" version 8.2 . Moreover, the server agent is running as a service and the standard server startup parameters are selected, i.e.

1540
1541
1560:1591
These clusters are located in the directory: " C: \\ Program Files \\ 1CV82 \\ SRVInfo »
The service starts from the local user Usr1cv8.

Start and configure to work on the same physical computer Server "1C: Enterprises" version 8.3 .

2. Installing the server part "1C: Enterprises" version 8.3

We launch the installation of the server "1C: Enterprise" (in detail about the installation of the server "1C: Enterprise" I wrote), select the component to install:

Access components 1C: Enterprises 8
Server 1C: enterprises 8

And at the same time we remember the directory of installation of files "1C: Enterprises" (in this case - " C: \\ Program Files \\ 1CV8 \\ 8.3.4.389»).

The server "1C: Enterprises" is not established as a service, but as an application, i.e. we remove the flag Install the 1C server: enterprises 8 as a Windows service»During installation.

3. Registration of Server "1C: Enterprises" version 8.3

Now manually register a new server "1C: Enterprises" as a Windows service, with modified parameters. To do this, we use command line or program Windows PowerShell . You can run PowerShell by completing the command powerShell (To do this, press the Win + R key combination, in the appeared window " Perform"(RUN) Enter the name of the command in the" Open"(Open) and click" OK") Or clicking on the appropriate label in the taskbar.

In opening windows consoles PowerShell, for the convenience of entering further commands, we turn to the catalog bin. Catalog S. installed files "1C: Enterprises" (directory from paragraph 1) by completing the command

CD "C: \\ Program Files \\ 1CV8 \\ 8.3.4.389 \\ Bin"

If the server "1C: Enterprises" version 8.3 was still installed earlier as a service, it is necessary to delete the existing server registration. To do this, you must execute the command

. \\ ragent.exe -rmsrvc

And it is also necessary to delete all the cluster registry directory files, last installation of the server "1C: Enterprise". The default is the directory C: \\ Program Files \\ 1CV8 \\ Srvinfo.

Now you can go to registration new service Server Agent "1C: Enterprises". T. to. Ports used by default ( 1540 , 1541 , 1560-1690 ) already occupied by the Server Service "1C: Enterprises" version 8.2, you must use alternative ports, for example 2540 , 2541 and range 2560-2591 . To register a server with these parameters to execute the command

. \\ RAGENT.EXE -INSTSRVC -PORT 2540 -Repport 2541 -range 2560: 2591 -USR. \\ usr1cv8 -pwd usrpass8 -d "C: \\ Program Files \\ 1CV8 \\ SRVInfo"

(Details about the parameters for starting the server of the server "1C: Enterprises" can be read in the article)

This example serves server registration with the following parameter values:

room network Port. Server agent - 2540
Number of the network port of the cluster manager - 2541
Port range for dynamic selection - 2560:2591
The service starts on behalf of the local user - Usr1cv8.
The user password on behalf of the service is launched - Usrpass8.
Cluster registry data are located in the catalog "C: \\ Program Files \\ 1CV8 \\ Srvinfo"
If you want to enable debugging on the server, you must add a parameter to the start row - debug.

Well, immediately make a start of service by completing the command

. \\ ragent.exe -start

Let's go to windows services And we will see that the list of the required service appeared in the list. 1C: ENTERPRISE 8.3 Server Agent (x86-64). The service is running, and when the service is started, the entered only parameters are used.

And if you go to the catalog with the cluster registry files, we will see that the corresponding files appeared there.

5. Adding Server "1C: Enterprises" version 8.3 in server administration console

To administer the server "1C: Enterprise", an "1C: Enterprise" servers administration console. Open the Administration Console required version from the subdirectory cOMMON. directory with installed files of the program "1C: Enterprises" (not necessarily this computer - Console can be installed separately on any computer on the network), running the snap 1CV8 Server (x86-64) .msc.

In the 1C: Enterprise Server Administration Console by clicking on the right mouse button in the settings tree on the " CENTRAL 1C: ENTERPRISE 8.3 Servers", Choose in the context menu item" Create» — « Central Server 1C: Enterprises 8.3».