Actions are similar). We will add a rule on the example of the server 1C: Enterprise 8.x (you need to open the port 1541 for cluster manager, ports 1560-1591 For workflows and port 1540 For server agent).
Some programs and services when working through network protocols use certain ports for data exchange. By default, the Windows Firewall enabled blocks such network activity. In particular, if you try to connect from the client machine to you can come across an error:
« Error when performing an operation with information Base (...). Error network access To server (...). Attempting to establish the connection was unsuccessful, since the required response is not received from another computer for the required time, or it was broken already installed connection Due to the incorrect response of the already connected computer (...) »
This error means that by specified address not found server "1C: enterprises", well, or the port is closed on the server (in this case port 1541 ).
To open the port, go to the computer where the server "1C: Enterprises" is installed (in my example, this is a computer with an address 10.192.128.15 and the operating system installed on it Windows Server 2012 R2).
Run Windows Firewall. You can make it by clicking the right mouse button on " Start» ( Start.), then " Control Panel» ( Control Panel.) — « system and safety» ( SYSTEM AND SECURITY.) — « Windows Firewall» ( Windows Firewall). Or by completing the command firewall.cpl(For this, you need to click the Win + R keys combination, in the window " Out off» ( Open.) Enter the name of the command and click " OK») .
In the window that opens, in the tree on the left, open the tab " » ( InBound Rules.), and then in the menu " Actions» ( Actions) Select item " Create Rule ...» ( New Rule ...).
Run " Creation Wizard for the new incoming connection» ( NEW INBOUND RULE WIZARD). On the first page, choose the type of rule ( Rule Type) « For the port» ( Port.) and click " Further» ( Next).
Then you must specify the protocol (in our example it is TCP) and, directly, the port number (Specific Local Ports), which is open. After which we click " Further» ( Next).
Now specify the action associated with the added rule. Choose " Allow connection» ( Allow The Connection.) and click " Further» ( Next).
On the next page You need to specify, for what firewall profiles will act rule. We celebrate the necessary profiles with ticks and click " Further» ( Next).
Well, finally, we enter a name and description for the new rule and click " Ready» ( FINISH.) To complete the work of the wizard.
We try to connect to the 1C: Enterprise server again and we see that the error has been preserved, but the message is already another, the 1560th port.
The method described above will add one more resolution, with the name " 1C: Workflows»For the entire range of ports with 1560 by 1591 (for 1c working processes), indicating them through a hyphen in step " Protocol and ports» ( Protocol and Ports.).
Now, in the snap " Windows Firewall in Increased Safety Mode» ( Windows Firewall WITH ADVANCED SECURITY) in the table " Rules for incoming connections» ( InBound Rules.) We have to see 2 just created rules.
Well, I have to connect to the server without errors. If you need to connect to this server through, you must also open the port 1540 .
Similarly, the rules for outgoing connections (OutBound Rules) prohibit rules for certain programs and protocols are added. Also, any rule can be changed by opening its properties from this snap.
Will this article help you?
Terms, concepts
Why do you need a server 1c
Under the notion of "server cluster" is understood as several computers (servers) perform the overall task.
Tasks solved by a 1C server cluster: Enterprise 8 in the figure below.
The difference between 8.1 and 8.2
Cluster 1C 8.1.
1C Server Cluster: Enterprise 8.1 is the implementation of the Ideas of the Load Distribution on the server serving client requests. Such a mechanism implements the distribution of the load on computing resources within a single server or multiple servers ("working servers"), thus providing application scaling. The server cluster duplicates the code that serves client connections. The duplicate executable cluster code is called the "workflow" (RPHOST). When you install the cluster, only one workflow is created.
Several workflows on one server make it possible to effectively use the volume. random access memory and processor resources for querying, as well as connect a client session to another workflow during the "crash" of the current.
For understanding that running on a specific server, the Server Agent program (RAgent) is responsible. Stop the server agent will make the server inaccessible to the cluster. The agent stores its information in the srvribrg.lst file.
Information about working bases involved work processes owns the Server Manager (RMNGR). It stores this information in the 1CV8Reg.lst file. Stopping the server manager can lead to a restart of client applications in cases of successful manager restart or to complete the work of the work servers of the entire cluster.
1C: Enterprise 8.1 allows you to create several independent clusters on one server. Each of them is identified in the network a unique "IP port" and a unique number in service files. The first default cluster receives port 1541.
To control the cluster, the "Enterprise Servers" is designed.
You can connect to servers by name or IP address of the server.
Agent Server
The server agent "knows" about all clusters that are running on the server. This information is stored in the srvribrg.lst file with the list of clusters and list administrators. The main port of the agent is 1540. Only one agent serving all possible clusters on this server can be launched on each operating server.
To get more detailed information, use the Process Explorer utility (SysInternals Developer). The program allows you to deeply look into any processes performed, including 1C server cluster: enterprises 8.1.
Cluster Manager
The cluster manager is responsible for the work of the cluster. Each cluster has its own manager. The manager stores the cluster information in the 1CV8Reg.LST file (cluster registry). Each cluster manager also has its own port on the working server. For the first cluster by default, the manager of the manager 1541. It is this port that this port is displayed in the "Servers 1C: Enterprise" snap-in in the cluster branch, identifying the cluster.
The manager accepts requests from the client part 1C: enterprises 8.1 and makes a solution to which workflow to give this service request.
To interact with work processes, the manager uses the utility.
The working process
For "work with clients" meets the workflow. We can say that in previous version 1C: Enterprises 8.0 "workflow" was one.
Workflows in the 1C cluster: enterprises 8.1 may be several. The server manager decides which of the workflows will serve the client connection. For client connections, the default workflows are allocated by the Range of IP ports 1560 - 1591. In addition, a service port for exchanging with the cluster manager is assigned to each workflow. Each workflow uses up to 2 Gb RAM in the 32x discharge operating system. In the 64x discharge operating system, the restriction is imposed by the physical volume of RAM
Cluster 1C 8.2.
1C Server Cluster: Enterprise 8.2 - Further Development of Server Technologies 8.2.
The server can work "as 8.1", i.e. It remained compatibility with previous technologies.
And plus a new approach to server work is implemented. Now instead of the processes an important role of sessions.
Sessions allow you to carry out loading and fault tolerance in the managed application.
Cluster Manager
The cluster manager has now become more difficult. Some functions can now be highlighted in a separate process and even place the cluster on another work server. This allows you to balance server workload.
Server failtaking 8.2 is achieved due to:
- Storing information about the user's work session.
- The user is not tied to the workflow.
- Reservation of workflows in the cluster.
- There must be several workflows, including redundant
- Reservation of clusters.
- Specifies a spare cluster when connected - listed in the connection string
This allows you to ensure continuity of work:
When the cluster's physical connection is broken with the cluster (the cleaner pulled out the cable, the power supply equipment was turned off, the provider's malfunction) does not have to reinstate the information base and start all the work first. After restoring the physical connection, the user can continue to work from the place where it was interrupted.
If you need a cluster computers maintenance, you can turn them right while working without stopping the operation of users with an information base.
When you fail, any server cluster server work will not stop it will be automatically transferred to the backup cluster and / or backup workflows. For users, such a transition will be invisible.
If one of the working processes of the cluster is completed, the alarms connected to it will be automatically translated into other or backup workflows. Such a transition will also be invisible to users.
Cluster 1C 8.3.
Server 8.3 is characterized by recycled internal code, although the "outside" may seem that this is the burdens, refined 8.2.
The server has become more "auto custom", part of the parameters of the type of workflows is no longer created manually, but is calculated based on the descriptions of the requirements for refusal tasks and reliability.
Received the development mechanism of load balancing, which can be used either to increase the performance of the system with an integer, or use the new "memory saving" mode, which allows "with limited memory" in cases where the configuration used "likes to dismiss memory".
The stability of work when using large amounts of memory is determined by the new parameters of the operating server.
The "Safe Memory Consumption per challenge" option is especially interesting. For those who are poorly present what it is - it is better not to train on a "productive" base. The parameter "Maximum amount of workflow memory" allows you when "overflow" does not dangle the entire workflow, but only one session "with a loser". "The amount of workflow memory, to which the server is considered to be productive" allows you to block new connections as soon as this memory threshold is overcome.
I recommend to isolate the working processes on the information bases, for example, specify the "Number of IB per process \u003d 1" parameter. With several high-loaded bases, this will reduce the mutual influence of both reliability and performance.
A separate contribution to the system stability makes "spending" licenses / keys. In 8.3, it became possible to use the manager program licenses"Recalling the manager" Aladina ". The goal is the ability to bring the key to a separate machine.
It is implemented in the form of another "service" in the cluster manager. You can use for example "free" laptop. Add it to 1C 8.3 cluster, create a separate manager with the licensing service on it. In a laptop, you can stick hardware HASP key, or activate software licenses.
The greatest interest for programmers must submit "Requirements for functionality".
So on a laptop with a protection key to not run users to the cluster server, you need to add "Requirements" for the object "Client Union with IB" requirement - "Not to assign", i.e. Prohibit working processes this server handle client connections.
An even greater interest is given the ability to run "Only background tasks" on the working cluster server without user sessions. Thus, you can take high-load tasks (code) to make a separate machine. What can one background setting of the "closing of the month" can be started through the "value of an additional parameter" on one computer, and the "Updating of the full-text index" background task on the other. It occurs through the "Additional parameter value" indication. For example, if you specify the backgroundjob.comMonModule as a value, you can limit the operation of the working server in the cluster only by background tasks with any content. The value backgroundjob.commonmodule.<Имя модуля>.<Имя метода> - Specifies a specific code.
Solving possible problems with installation
When installing the server part 1C: Enterprises 8.1 You can create a new user or select an existing account.
If you select an existing account, you must specify the correct password and confirmation, otherwise the launch of the server part will result in an error.
When you first start the cluster agent, a default cluster is created.
The default cluster has the following characteristics:
· Port number - 1541;
· IP range ports - 1560: 1591;
· Support for many workflows - disabled;
· One workflow, the port number is installed from the specified range.
If you have any problems when you first start the cluster agent, then the default cluster may not be created. This manifests itself that when the server agent starts, it starts, but does not start other cluster processes (RMNGR, RPHOST). List of clusters SRVRIBRG.LST looks like this:
{
{0},
In this case, you can stop the Ragent process, delete the cluster list (srvribrg.lst) and run Ragent again.
Check the port match specified in the PORT parameter command line Starting the server agent service and set in the cluster console settings specified in the dialog dialog:
- Stop 1C: ENTERPRISE 8.1 Server Agent.
If the server agent is running as an application, the stop is performed by pressing the Ctrl + C key combination.
- Make sure in the task manager (Task Manager), that all the processes are ragent, RMNGR, RPHOST ended. If necessary, complete them with Task Manager.
- Open the 1C: ENTERPRISE 8.1 Server Agent service properties.
- Pay attention to the "Path to Executable" string. It has a -D parameter, followed by a cluster data directory. All the cluster relating files are in this directory.
- Delete all the contents of this directory.
- Run the 1C: ENTERPRISE 8.1 Server Agent service.
- Make sure the task manager (Task Manager), that all the processes are RAGENT, RMNGR, RPHOST started.
- Run the cluster console and register a central server in it. The console must be connected to the central server and show one cluster created by default.
Possible trouble cluster failures for server cluster are problems with protection keys, service account rights, incorrect launch parameters.
- The server part key is installed locally to each enterprise server.
- Do not ask your service account with an empty password
- With multiple clusters, the ports used should not intersect
Please note that in the process of installing the 1C platform: Enterprise 8.1 may be issued error messages. The following are the most likely messages. The reasons that caused messages and steps to eliminate are indicated.
Error 1069: The service is not running due to the login error
The problem is related to the Run Rights Rights on behalf of the System Service. Open the utility Local Security Policy ( Local politics Security) and add a user (on behalf of which the cluster working servers started) to the Logon AS Service policies and the Logon As Batch (work as a batch task) Job.
If the data stored in the service files is violated, and the launch of the cluster working servers may be unsuccessful. Make sure that the server agent 1C: Enterprises 8.1 is running (Ragent process in Task Manager).
Do not forget that the analysis tool is also an audit of Windows events. To do this, see whether any "suspicious" messages appear in the Windows event log.
Error 8007056B / 800708C5
The New Password Does Not Meet The Password Policies. The Password May Be Too Short or You Have Already Used This Password Recently.
Cause: The specified password for the account in the "Installing Server: Enterprise" dialog box does not satisfy the security policy requirements.
Solution: Set a new password for the selected account that meets the security policy requirements or weaken the requirements of the security policy applied, i.e. Do not require a "complex" password, do not limit the number of signs in the password, do not check the attempts of repetition, etc.
Error 1923: no privileges to install the service
Cause: Error is related to account installation rights as applications. This error is characteristic of attempts to install the server on the domain controller, where elevated security measures are presented.
Solution: Do not use the domain controller to accommodate the enterprise server or weaken the security requirements and specify for the selected account of the right "Work as a service", "work as a batch task".
Error 80070056.
Your Password Could Not Be Changed. Each Password Must Be Used for At Least X Days.
Cause and solution: Another error arising from violating security policy requirements to the passwords used. The solution is similar to the error 800708C5.
Windows Sockets - 11004 (0x00002AFC)
1) Ensure that the working server of the cluster in the Task Manager (Task Manager) is launched:
Server agent (ragent.exe),
Cluster Manager (rmngr.exe),
Cluster workflow (rphost.exe).
2) To check the permission of the IP address names, run on the command prompt:
Ping name_Mashina
In the response of the system to the command, we are interested in, to determine if the IP address.
3) If the name is determined, but the working process is still not located, then make sure that the definition of the name IP address<имя машины> and<имя машины>.<имя домена> Defined not differently.
(Windows Sockets - 10054 (0x00002746).
Remote host forcibly broke the connection.
Such a message can be obtained in the case of rebooting the server or forced removal of the workflow.
This error usually does not appear when re-connected. If the error remains, it is necessary to investigate the causes of the failure of the cluster working servers.
This error can occur when the workflow is achieved by the workflow of the maximum amount of memory in 32x bit systems.
Another case is an attempt to connect from a client with an error message:
(Windows Sockets - 10060 (0x0000274c)
An attempt to establish the connection was unsuccessful, because From another computer, for the required time, the required response is not received, or the already installed connection was broken due to the incorrect response of the already connected computer.
The essence of this error is the absence of a response during a certain time (timaout).
1) Make sure the firewall does not block the application traffic. Turn off the firewall.
To do this, run the command in the command line (the command is available from Windows XP and Windows Server 2003, in more early versions There is no built-in firewall, however, it can be installed third-party software):
netsh.firewallsET.oPMode.disable
If the command is successful, you will receive a message:
OK.
Besides firewall block traffic can network filters. They are turned off by default. However, make sure it is:
- Open the Network Connections folder.
- Right-click network connectionyou want to configure and select the command Properties.
- On the tab General (for connecting to local network) or on the tab Net (For all other connections) select Internet Protocol (TCP / IP) and click Properties.
- Press the button Additionally.
- Open tab Parameters, Select a parameter TCP / IP filtering and click Properties.
- Make sure the checkbox TCP / IP filtering (all adapters) Shot.
2) Make sure the processor resources are not loaded by 100% (CPU%).
3) Measure the network activity of the client interfaces and server. Stress on network adapter should not exceed 60%.
(Windows Sockets - 10061 (0x0000274d)
Connection is not installed, because The destination computer rejected the connection request.
A characteristic reason for such an error is the lack of a running server agent. Run the server manually or restart the server to automatically start.
Answers on questions
Multiplatform 1C.
Server Installation
Q: Server installation error 1c on MS Server 2008 R2 x64 when installing 1C server via a command line, such as such, ragent.exe -instsrvc -port 2040 -Regport 2041 -Range 2060: 2091 -D "C: \\ Program Files \\ 1CV82 \\ OpenSCManager Error! " The service is not created. Checked at 8.1.15.14 and 8.2.10.77
A: To install from a command line on the OS, where the UAC is present, you need to use the Runas service, because Even if the user enters the administrators group, the UAC blocks actions that change the state of the system.
Protection keys
Q: The protection key from server 8.2 allows you to start the server 8.1?
A: Yes, allows
Q: To start the 1s server, I need Hasp keys some server? Local, or 5 users will not go?
A: Yes, for the server you need your key, local user and networks will not fit. More B. « « , Slide number 30.
Q: Suppose 1C server cluster stands out of 3 physical servers. how much need protection keys
Q: There is a terminal server and a key to 5 licenses, the 6th extra charge is purchased. license. Is it possible to install it on the server next to the key on 5? And will all 6 users work in Teminal sessions or 5 - under the theerminal, and 1 in the file version?
A: No, will not. The 6th License in the form of a local key must be stuck in the user's computer, but not in the terminal.
1C Server Updates
Q: when leaving new version 8.2.xxx Platforms What is the procedure when updating servers and customers
A: Distributions 8.2 Install their files in different folders (For each version of its folder), i.e. Theoretically, the possibility of calling parallel to several versions of the server remains.
I didn't have any special problems. However, it is necessary to carefully track the ports occupied by an instance of the 1C server. The intersections should not be.
Configuring server 1C.
Q: 1C 8.1, how to better place information bases if there are several of them, in one cluster or create a separate cluster for each base? A: With a large volume or load, as well as test bases are needed in separate clusters!
Q: Question: Works process 1C: Enterprise 8.1 is a single-threaded application or multi-threaded? Those. Can there be a lot of cores for one connected user? With several? And the working process 1C: Enterprise 8.2? Thank you.
A: 1SV8.exe and rphost.exe in version 8.1 eaten 1 core. By how much of 8.1, the client's connection is rigidly tied to the workflow, it can be conventionally assumed that the processing of 1c clients is performed within one nucleus. The exclusion is a DBMS that uses the kernels regardless of how the server 1C works.
In version 8.2, the connections are replaced by sessions. Sessions can already be performed in different workflows. Therefore, to call 8.2 single-threaded probably not correctly. Client 8.2 also visually loads several nuclei, so this is:
platform 8.2 does not implement all the designers of the multi-threaded system, but it significantly uses the possibilities of iron compared to 8.1, including in terms of parallelism.
Q: Are there several working processes 1C: Enterprise 8.1 so that the database server (MS SQL) loads several cores? (It is noted that MS SQL usually "loads" only one kernel, i.e. "parallelization" processing one request in several nuclei, as a rule, does not occur.) Thank you.
A: Specially control MS SQL does not need, it is quite a self-adjusting system using resources as needed. You can manage the execution parallelism:
Exec sys.sp_configure n'max degree of parallelism ', n'5'
Go.
Reconfigure with Override.
Go.
Create several workflows on the 1C server can be based on the fact that one working process does not provide the ability to users to re-connect in cases of falling the workflow. 2 Process (on 8.2 it is better to make it "backup") solves this problem. But 3 and more working processes make sense to add only if the first two work processes are strongly loaded (more than 90%). Without failure to produce workflows, it is not worth it, it may worsen performance.
A: At least 1 the backup workflow in 8.2 must be.
Failover cluster
Q: The question about the inclusion of 1C 8.2 cluster reservations. If we have fallen a server (the cleaner pulled out the wire), the network name, for example, "Server: 2540" will not be available. As a client, which is written in the "Server: 2540" connection string, find out what you need to connect to the backup cluster? Where does he get the name of another server? And if you write clusters through a comma in the base row?
A: Several clusters are combined into a "reservation group". To do this, there is a "reservation list" in the cluster snap-in.
When you first access the client to the cluster, the list of clusters included in the reservation group is transmitted.
If the client has not yet appealed, then in this case you need to manually specify the addresses of all clusters, such as Storm: 2541, Monster: 2541.
Between the backup clusters is exchanged synchronized data.
Q: What happens after restoring the main cluster? When users switched to the backup.
A: Return back. Possible pauses when switching for cluster data synchronization time.
Background tasks
Q: How to delete the background task running on 1C: 8.1 and 1C servers: 8.2?
A: The ability to cancel the regulatory task only works if the code is performed within the embedded language 1C: enterprises. If the code is executed in external libraries, then it is impossible to cancel such a job otherwise, as a forcibly completing the workflow. If in the process of the block to start voltail () - fix the transaction (), it is unlikely. The remaining background tasks can be removed through the task console.
Regulatory procedures
Q: Is it possible to destroy the database during TII?
A: I have such cases unknown, but IMHO is possible everything. Therefore, before Tii, it would be nice to make a backup.
Q: Vyacheslav, for what reasons you do not make a reindex by means 1C testing and correction?
A: For these purposes, the possibilities of the DBMS are better suited, since they are also doing the rebuilding of indices, but do not require the monopoly capture of the base.
Technological journal
Q: Good afternoon. Question on Technological Journal: I need to receive copies of workstation screens when 1C errors. Do I need to configure the technological log and on workstations, or is it only for the server?
A: You can only configure the screenshot when dropping the platform, and not at any error. However, not much useful in such an operation, it is quite enough to collect exclusive situations through the technological journal. At the same time, most of the errors can be seen with the help of the TJ on the 1C server side. An exception can make events like "Format Flow Errors" associated with obsolete metadata cache.
Problems and mistakes
Q: Have you come across a problem - the disappearance of user report settings when dynamically updated the configurations on the platform 8.2. There are recommendations, how to deal with it?
A: Problems associated with dynamic update Reflected in "Servers 1C: Prefirmation 8.1 and 8.2 - with what they eat"), Slide No. 60. Clean cache. Perhaps in some cases it is necessary to understand where the user settings specifically stored. If necessary, stored as binary data in the information register.
Q: A passing question, because This is relevant for the file mode: what errors corrects chdbfl.exe?
A: This is a storage storage error tool. This may be the situation when the "database file is damaged ... / 1cv8.1cd". Those. Eliminates damage to the database file. However, it does not perform the functions of Tii. I launch chdbfl.exe if "does not stop successfully" Tii.
Q: Please tell me the challenge with such a problem. When founding in the database large number Users (about 40) when carrying out large documents, for example, the reflection of the SP in the regulation. Accounting about 8000 lines. An error is issued lack of memory on the server 1C server and the user initiated this document falls off. The document then can be carried out only after restarting the 1C server agent.
A: Looks like a memory leakage:
1. Restart Server 1C, increase the number of workflows, to hold only one of this database in the cluster.
2. Beat a portion, say 1000 lines at a time. Tracking the objects occupying at the start of the operation, but not freeing up the operation upon completion.
3. Put x64 version, increase the scope of RAM, go to 8.2.
Q: Question on testing and giving. Is it possible to start the "reference integrity check" on the basis of the UrbD with the selection according to the data transmitted? (i.e., in some nodes there are physically missing objects, but there are links to them). Thank you!
A: Unfortunately, so far there is no such possibility.
Q: Why testing and fixing does not immediately solve all questions, you have to run several times?
A: Only developers can answer exactly. I launch the regulations (cyclically), so this question is not very relevant for me. It is necessary to make Tii more than once, but constantly as "then for the car."
Q: Is there any difference of 8.1 and 8.2?
A: Currently writing a response and release 8.2.10 I do not know the difference.
Q: Do I need to restructure to make reindexing?
A: No need.
Other
Q: Dear the Lord, nobody tried to mirror the database with MSSQL 2008 by means of MSSQL 2008?
Q: Question to enable Shared Memory on Server 1C 8.2
A: Do not need to enable anything, the server will understand.
Q: For 1C: Enterprise 8.1 is noticed situations when on the same hardware The file-server version with "heavy" operations and a single user works much faster than the client-server, when all "links" (DB Server, Server 1C: Enterprise and Client) are installed on one server. At the same time, when performing this "heavy" operation of explicitly expressed overloads of the hardware part (loading the processor, memory, hard disks minimum). That is, there are many hardware resources, but it works slowly. What can we "rest"? Thank you.
A: The advantage of client-server architecture from the point of view of performance is the ability to parallel to handle customer requests to the data. Those. The flow rate is not the indicator for which the general conclusions should do. Mechanisms that improve parallelism, still within the framework of a single stream may slightly reduce performance.
In order to unambiguously find a bottleneck in your case, you need to get the loading of server equipment and match the time with the longest operations in the client-server mode. Often it happens to excess data to the client part. Those. Instead of performing operations on the 1C server, data from the DBMS through the server is transmitted to the client.
Speed \u200b\u200bin one client-server version will only catch up with the file option. It is worth doing this problem if the operation time in absolute figures is measured at least in less than a minute. Optimization within 1-3 second requests is doubtful.
Q: The difference between Windows Terminal and the subtle client 1c.
A: While most solutions are not fully translated under 8.2, it is definitely difficult to talk about the practical comparison of these technologies.
It is clear that slim client 1C should exacerbate less traffic and provides the ability to work through the web. But this is what has yet to be implemented, and terminal solutions are exploited very wide now.
For conservative pragmatic project managers, converting 8.1 under 8.2-terminal solution. For small projects with low cost of errors and the configuration immediately implemented with controlled forms and SCD - a subtle client of preferred IMHO.
Q: And how to spend stress Testing Approached to real conditions? After all, you will not drive the users to "roll something."
A: 1C: Testertr with the choice of the most difficult operations, 100% reproduction is not necessary, the clicks themselves are not heavy, mainly conducting and report requests. Testing will be a separate webinar. I also cut out more.
Find in the branch
HKEY_LOCAL_MACHINE \\ SYSTEM \\ CURRENTCONTROLSET \\ SERVICES \\ 1C: ENTERPRISE 8 SERVER AGENT , Parameter Imagepath.
By default, the server 1C: Enterprises use the following ports:
- 1540 - Server Agent
- 1541 - Cluster Manager
- 1560:1691 — dynamic range Ports for workflows.
Or official definition from http://its.1c.ru:
Installation and Settings 1C: Enterprises 8.1 in the "Client Server" version
In most cases, for installation 1C: Enterprises 8.1 In the "Client-Server" version, it is enough to start the 1C installation program: enterprises 8.1. At the same time, the server 1C: the enterprises receive the standard values \u200b\u200bof the parameters necessary for its normal functioning.
Consider the installation of the server 1C: enterprises in more detail. In the process of installing the server 1C: Enterprises 8.1 Installation program 1C: Enterprises 8.1 performs the following actions:
Copies the 1C server boot modules: enterprises in the directory specified by the 1C installation program: Enterprises as a destination folder.
If you select "Create a USR1CV81" user in the installation process, then creates a USR1CV81 user. On behalf of this user, the server is working 1C: enterprises 8.1, if it starts as a service. Only those resources that are required by the 1C server are available to him. It is important that the 1C server: Enterprises require two directory: a common directory with server data (usually "C: \\ Program Files \\ 1CV81 \\ Server") and temporary file directory (usually "C: \\ Documents and Settings \\ usr1cv81 \\ local settings \\ Temp "or" C: \\ WINNT \\ TEMP "). User Usr1CV81 gets the rights to a general directory with server data. Catalog of temporary files is usually available to all users.
If during the installation process is enabled "Set the 1C server: Enterprise 8.1 as a Windows Service", it logs on Windows Server Agent 1C: Enterprises and starts it. When you first start, a 1C server cluster is created: enterprises with default settings. It has one working server and one workflow. The address of the operating server coincides with the name of the computer on which the installation is made.
User usr1cv81 and its right
Server 1C: Enterprises is the server application of which should not depend on which user entered the server computer in the interactive mode, if at all someone entered. Therefore, when installing the server 1C: enterprises It is advisable to create a special USR1CV81 user with rights minimally necessary for the 1C server: enterprises, and not intended for interactive input. Server 1C: enterprises seem windows system User usr1cv81.
Consider a Read more rights to be installed by the user usr1cv81. Server 1C: Enterprises use the following directories:
Catalog of loading modules is in the catalog, specified program Settings 1C: Enterprises as a destination folder. It has a loading modules of Server 1C: Enterprises. User UserR1CV81 requires the rights to read data and launch programs from this directory and its subdirectories. It receives these rights implicitly, thanks to the inclusion in the User group.
The server data directory typically has the name "C: \\ Program Files \\ 1CV81 \\ Server". The user of the USR1CV81 requires complete rights to this directory. The 1C installation program: Enterprises when creating a USR1CV81 user gives its rights to this directory.
Catalog of temporary files usually has the name "C: \\ Documents and Settings \\ usr1cv81 \\ Local Settings \\ temp" or "C: \\ WinNT \\ TEMP", which is determined by the value of the TEMP environment or variable Temp systemic Environment. You can see the value of this variable in the System Properties dialog (Start -\u003e Settings -\u003e Control Panel -\u003e System -\u003e Advanced -\u003e Environment Variables). Installation program 1C: Enterprises Specifies the user with USR1CV81 full rights to this directory. Usually when windows installations The directory of temporary files is available to all users by including in its access list of the Creator Owner group. However, this is not complete access. In particular, all users are not available for searching for files in this directory. Installing a USR1CV81 user full rights to the temporary file directory allows 1C server: Enterprises to carry out all the operations you need. You can see the access list in the directory properties dialog on the Security tab. The presence of the Creator Owner group allows you to access the directory to any user who creates any files in this directory or owning any files in this directory. At the same time, a user who created the file will be recorded instead of the Creator Owner group of the Creator Owner group. Among users who are allowed to access this directory must be USR1CV81, endowed with full rights to this directory.
It is important to keep in mind that the directory of temporary files of a specific user (including the USR1CV81 user) is determined by the combination of environment variables of this user and systemic environment variables. To find out this directory, the installation program is 1C: the enterprises request the USR1CV81 user context. To this in Windows 2000, the user, on behalf of which the 1C installation program is launched: Enterprises may be required: ACT AS Part of The operating System And Bypass Traverse Checking. You can check the user privileges in the Local Sequrity Settings utility in the Local Policies branch -\u003e User Rights Assignment. In the process of installing the new software, the installation program usually receives these privileges automatically.
Signup Server 1C: Enterprises as a Windows service
Server 1C: Enterprises are simple console Windows Application And it can be launched interactively. However, for permanent use, it is inconvenient, since it puts the launch of the server 1C: enterprises from the input of an identical user to a server computer. To eliminate this dependence, Server 1C: Enterprises can be launched as a Windows service. To do this, it must be registered in Windows Services Manager.
To view the list of Windows services and their parameters, the Component Services utility is designed (Start -\u003e Settings -\u003e Control Panel -\u003e Administrative Tools -\u003e Services). Server 1C: Enterprises are presented in the service list service "Server 1C: Enterprise 8.1" service. Service Settings Specify the start of the "Server 1C: Enterprise" (RAgent), the user, on behalf of which it starts, as well as a restarting method in emergency situations.
In the dialog of the 1C: Enterprise 8.1 Agent of Server 8.1, the General tab is shown the Ragent process string, which is the server agent 1C: enterprises. Usually this line has the form:
It indicates that:
the process of the server agent is the loading module "C: \\ Program Files \\ 1CV81 \\ Bin \\ ragent.exe";
the Ragent process starts as a Windows service and must be managed by the service manager (-srvc);
used as a server agent 1C: Enterprises (-Agent);
when you first start the service, the cluster must be created with default parameters and the main IP port number 1541 (-Regport 1541). In this port, client applications must connect to the information bases registered in the cluster;
The server of the server agent must have number 1540 (-Port 1540). By this port, the cluster console must be connected to the central server to perform administrative functions;
when you start the cluster processes on this server, they will dynamically assign IP ports from the range of 1560-1591 (-range 1560: 1591).
the general cluster data will be placed in the C: \\ Program Files \\ 1CV81 \\ Server directory (-d "C: \\ Program Files \\ 1CV81 \\ Server").
Service Agent Server 1C: Enterprise 8.1 »can be added or removed not only when installing or removing 1C: Enterprises of the 1C installation program: enterprises 8.1, but manually. To do this, you can execute the Ragent utility from the command line by specifying the corresponding parameters to it.
To create a service, you need to specify the -INTSRVC parameter and parameters: -USR - the username, on behalf of which the service must be running, -PWD is the password of this user. In this case, the remaining parameters will be the parameters of the string of the server of the server 1c: enterprises as a service. For example, for standard registration of the service agent service 1C: Enterprises in debug mode The set of parameters should be:
"C: \\ Program Files \\ 1CV81 \\ Bin \\ ragent.exe" -INTSRVC -USR. \\ USR1CV81 -PWD Password -Regport 1541 -Port 1540 -Range 1560: 1591 -D "C: \\ Program Files \\ 1CV81 \\ Server" - Debug.
To delete the service, you need to specify the -RMSRVC parameter. For example:
"C: \\ Program Files \\ 1CV81 \\ Bin \\ ragent.exe" -RMSRVC
Sometimes it is possible to change the server agent launch string or other parameters of the agent service, for example, enable debug mode, or create multiple services different versions. The service property dialog does not allow you to edit the startup string of the service application and some other parameters, for example, service identifier. To edit, you will need a REGEDIT utility designed to view and edit. system registry Windows.
Attention!
Editing the Windows system registry requires extreme caution, since erroneous changes in it can lead operating system In an inoperable condition.
Run the Regedit utility (Open Start -\u003e Run and type Regedit) and select a branch:
HKEY_LOCAL_MACHINE \\ SYSTEM \\ CURRENTCONTROLSET \\ SERVICES \\ 1C: ENTERPRISE 8.1 Server Agent
Among its parameters there is an imagepath parameter, the value of which is a string of the server of the server 1C: Enterprises. Here you can add new startup string parameters or change the values \u200b\u200bof existing ones. A complete list of possible parameters is given in the book "1C: Enterprise 8.1 Client-Server" documentation.
If you need to register multiple independent 1C server agent services: Enterprises need to specify different boot modules, different ports and different cluster data catalogs. It is still required to register them with different service identifiers. This can be done like this:
Create the first service:
"C: \\ Program Files \\ 1CV81 \\ Bin \\ Ragent.exe" -SRVC -Agent -Regport 1541 -Port 1540 -Range 1560: 1591 -D "C: \\ Program Files \\ 1CV81 \\ Server"
Using the Regedit utility, change the registered service identifier. To do this: Choose a branch
HKEY_LOCAL_MACHINE \\ SYSTEM \\ CURRENTCONTROLSET \\ SERVICES \\ 1C: ENTERPRISE 8.1 SERVER AGENT FIRST
Create a second service:
"C: \\ Program Files \\ 1CV81_10 \\ Bin \\ ragent.exe" -SRVC -Agent -Regport 1641 -Port 1640 -Range 1660: 1691 -D "C: \\ Program Files \\ 1CV81_10 \\ Server"
Perhaps its identifier is also changed. To do this: Choose a branch
HKEY_LOCAL_MACHINE \\ SYSTEM \\ CURRENTCONTROLSET \\ SERVICES \\ 1C: ENTERPRISE 8.1 Server Agent
And change her name, for example on:
HKEY_LOCAL_MACHINE \\ SYSTEM \\ CURRENTCONTROLSET \\ SERVICES \\ 1C: ENTERPRISE 8.1 Server Agent Second
What can not do the 1C installation program: Enterprises
As already mentioned, the 1C installation program: enterprises copies 1C loading modules: enterprises and performs the necessary registration in the COM and in Windows Services Manager. The above is the information necessary to understand the internal mechanisms of this registration. If the server computer is installed not only the server, but also the client part 1c: enterprises, then it is ready to work immediately after installation (and connecting the protection keys).
To the server 1C: Enterprises have been available from other computers on the local network, you need to check network settings On the server and client computer, as well as for the network as a whole. To transfer data between client applications and 1C server: enterprises, as well as between server cluster processes, TCP / IP is used. From the correct setting it depends on the work of 1C: enterprises in the client-server version.
1C server cluster processes: Enterprises are connected to each other by addresses defined as the values \u200b\u200bof the "Computer" properties of the properties of the working servers. For a cluster, it is necessary that the "Computer" properties value is either an IP address in point notation, or such a symbolic address by which the IP address can be defined using the GethostByname function defined in the TCP protocol program interface. The definition of the IP address is performed either based on the local table of symbolic addresses (C: \\ WINNT \\ System32 \\ Drivers \\ ETC \\ HOSTS) or by addresses in the available DNS servers. If, on the symbolic address of the working server, its IP address is not determined or determined incorrectly (for example, the IP address does not match the actual IP address this computer), then the cluster will not work. It is important that the names of the computers and their addresses defined in Windows on each of the working servers of the cluster did not contradict their names in the DNS.
On each working server, the cluster processes use the following ports: IP port of the operating server (usually 1540); IP ports from the IP ports of the workflow ports (usually 1560-1591). In addition, the cluster port is used on the central cluster server (usually 1541). If network screens are used in the system, the data transmission over these ports must be allowed. Instead of the port permission from the list of the list, you can allow the data transfer of the cluster processes (Ragent, RMNGR, RPHOST).
Connecting a client application 1C: Enterprises with a server runs in 2 stages. At first it establishes a connection to the cluster manager. This uses the address of the central server (symbolic or numeric) and cluster port (usually 1541). Next, the client application establishes a connection with one of the workflows. As its address, the value of the "Computer" properties of the corresponding working server and the port of the workflow, which is selected from the IP port of the operating server ports. Data transfer to these ports must be enabled in all network screens on the route from the client application to the computer cluster computers 1C: enterprises. The IP address of the server processes is performed using the GetHostByname function on the client's computer. It is important that the names of the central and working servers and their addresses defined in Windows on each of the cluster servers did not contradict their names in the DNS accessible to the client's computer.
And last. Obviously, for successfully access to the 1C server: enterprises from other computers, it must be on the network and the necessary settings must be performed. Connecting to the network and the configuration methodology relate to the administration of networks based on Microsoft Windows. and are described in the relevant instructions.
Features SQL Server Settings
1C: Enterprise in the "Client-Server" version uses for storage of SQL server data. In this case, only the server 1C: enterprises are referred to the SQL server. Customers 1C: enterprises of direct access to the SQL server do not have. Installing and configuring the SQL server is described in detail in the Microsoft SQL Server documentation. For successful operation of the server 1C: Enterprises with a SQL server need to pay special attention to the following settings.
Required SQL Server Components. To access the SQL server from the server side of 1C: Enterprises on a 1C server computer: Enterprises must be installed Microsoft Data Access 2.6 or later.
SQL server authentication. SQL Server Database Access Rights are determined by the user, on behalf of which access to databases. From the computer on which the SQL server is installed, launch the SQL Server Enterprise Manager utility, we will find the Local node (Console root -\u003e Microsoft SQL Servers -\u003e SQL Server Group -\u003e (Local)) and open its properties. On the Sequrity tab, you can see that the SQL server supports two methods of user authentication: SQL Server and Windows and Windows Only. Windows authentication will allow the 1C server: Enterprises to access the SQL server only on behalf of the USR1CV81 user, which does not allow to distinguish between access rights to various information bases served by one 1C server: enterprises. It is recommended to select SQL Server and Windows mode. In this case, the appeal to a specific information database will be executed on behalf of the user, which is specified as a SQL server user when creating this information base. It is important that this user must have not only full rights to the information base database, but also the right to create databases in the SQL server and read the Master database tables.
Network protocols to access the SQL server. If the server 1C: Enterprises and SQL server are posted on different computers, then you need to configure network access protocols to the SQL server. This can be done using the SQL Server Client Network Utility utility. On the General tab, you can select a list of network protocols used to access the SQL server. The fastest and most universal is to use the TCP / IP protocol. When using other protocols, it is necessary to keep in mind that some of them, such as Named Pipes, perform additional authentication. windows tools When exchanging data with a SQL server. In this case, a USR1CV81 user must be registered to successfully work with the SQL server on a computer with the SQL server. The access protocol to this SQL server can be changed on the Alias \u200b\u200btab.
26.07.2017
Adding Rules in Windows Server 2012 R2 Firewall for 1C: Enterprise
During the work of various services and software network protocolsThese working items use specific ports through which data exchange occurs.
In the Windows Server 2008/2012 R2 Branmaer Configuration, the default network activity is provided. To give your opportunity client Programs Work via the appropriate ports with server components, you must add rules to Windows Firewall to allow you to exchange data on the network using certain ports.
Often, users face situations in which the client software cannot find the server "1C: Enterprise", running in the server environment managed by Win Server 2012. This can take out the following errors:
error access to the server over the network;
error when performing operations with an information base;
unsuccessful attempt to establish a connection, the necessary response from another computer was not obtained;
a fixed connection was broken due to the incorrect response of the already connected computer.
Error data indicate that the client software failed at the specified address to find 1C server. It often happens that on the server the port required to connect is simply closed. In the case of 1C server, this is a port at number 1541.
To open this port, you need to go to the server via RDP connection and run windows management Firewall. This operation can be made in two ways. The first option is to go to the "Control Panel", then in the subsection "System and Security", the DG e must be launched, actually a firewall.
Also, for this, you can use the command line by running the firewall.cpl command in it - for this, press the hot keys of Win + R, after which go to the "Open" section, enter the command name and click confirmation.
After we got access to windows Firewall, In its active window, we need to select the section of additional parameters, which is located in the left menu. Further on the left side of the new window that opened the new window must be processed to the section of the Rules for incoming connections and select "Create a new rule" through the Actions menu.
Before, we will find a rules wizard for new incoming connections. On the title page you need to select the type of the selected rule marked with the name "for ports" and can be followed. Now specify the network data transfer protocol (in our case, specify TCP), as well as the number of the port open.
On the next tab, we will need to specify the action directly, which will be associated with the rule we create. We are interested in "Allow connections". Choose it and click "Next". Now celebrate the required Windows Firewall profiles, which we create the action should be distributed. last page The master invites us to enter a name for the new rule, as well as add a description to it if desired. We click ready and complete work with the master.
After creating the rule, you need to try to connect to the 1C server again. When you connect, we will see the same mistake, but now the message is already talking about another port at number 1560.
By analogy with the ports described above, add another rule in which you specify the range of ports 1560-1591. These ports are required to provide various program processes 1C. Ports included in this range indicate through a hyphen in the Protocol and Ports section.
After the manipulations have done, go to the Windows Firewall with Advanced Security snap. Here, in the Rules section for an incoming connection, we will be able to see our rules. At the same time, now the 1C client must be freely connected to the server surround. If you need to connect to your server through the 1C server administration console, you will need to create a separate rule that opens port 1540.
If you need to add rules to outgoing connections, you can use the same rules scheme for individual protocols and programs.
Setting up Windows Firewall for Win Server 2012 on 1C server + MS SQL
Now a few words about how to configure firewall under Windows Server 2012 in the specified configuration. Such a bunch is not uncommon for modern offices, but sometimes it takes extra time to figure out windows work Firewall with 1C server environment.
Provided that the server receives connection to the standard TCP port 1433, it is necessary to simply allow this port using the creation of the rules for the firewall, the principle of which we looked higher. To check whether the work really goes through this port, you can run the SQL Server Configuration Dispatch snap in Server 2012 and go to the Network Configuration tab. Here you need to select the tab of the protocols for MSSQlServer and find the TCP / IP protocol in the left window. Select it and click "Properties", after which we are looking for the "IP Addresses" tab and reveal the IPAII branch.
If the SQL port is dynamic, you will need to resolve the connection to the next application% ProgramFiles% \\ Microsoft SQL Server \\ MSSQL10_50.MSSQLServer \\ MSSQL \\ Binn \\ sqlservr.exe.
As already mentioned above, 1C server operates with port 1541 and ports in the range of 1560-1591. However, it often happens that for incomprehensible reasons, this list of open ports does not any equal to the server connected. So that everything worked at 100% you just need to expand this range by specifying ports from 1540 to 1591.
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 allocated 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.
Mounting program 1C: enterprises 8.2 and 8.3 sets up software To use your 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 the 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 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 window
You 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 that 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
. You just have to run it with the team ragent.exe -Start: Server Manager -\u003e Configuration -\u003e ServicesC: \\ Program Files (x86) \\ 1cv8 \\ 8.3.4.437 \\ bin\u003e ragent.exe -start
In the window
We see the service "Server 1C: Enterprise 8.3": Server Manager -\u003e Configuration -\u003e Services where the field "executable file" has a setting:
launched with parameters:
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: you will have to do
This operation
Each time the 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 version 8.2, it will automatically open in the desired version of the 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 ...
