How to set up synchronization of 1C databases?

Question

1C

Good afternoon, colleagues! There is such an urgent question:
There is a 1C server, it was updated to version 1C.Enterprise 8.3.12.1685. And there is a terminal server from which they work with databases hosted on the 1C server. Both servers are running Windows Server 2012 R2.
The 1C server hosts the Bukh 3.0 and Zup 3.1 base. Synchronization was configured between them on the previous platform, 8.3.11.2954. On 8.3.11.2954, the sync worked fine, but to update Buch to the latest configuration, they were forced to go to 8.3.12.1685 (anticipating a possible question - no, there is no test server). After the transition, it turned out that the synchronization was not working. When I try to connect (for example, in the settings check window), I get the following message:

Не удалось подключиться к другой программе: метод объекта не обнаружен (Connect)

What was tried:
1. Reinstall the platform on the server and terminal
2. Install 8.3.15.1513
3. Register regsvr32 "C:\Program Files (x86)\1cv8\8.3.12.1685\bin\comcntr.dll" (on the server and client)
4 Create a COM application V83COMConnector (on the client)
What other options are there? Perhaps someone has come across this and was able to win?
PS The option to demolish the 1C server completely and install it again is undesirable due to the presence of other client bases on it, but if there are no other options, then of course you will have to.

Answer 1

Problem solved. To solve it, it was necessary to create a new user with administrative rights, and execute the command from under it

regsvr32 "C:\Program Files (x86)\1cv8\8.3.12.1685\bin\comcntr.dll"

Answer 2

Register regsvr32

How did they do it? What is the bitness of the server?

Answer 3

8.3.11.2954, 8.3.12.1685, 8.3.15.1513 - are you confused? But your computers seem to be confused, since each of them registers its own V83COMConnector.
Since Bukh and ZUP are installed on a single server, they are most likely exchanged there. Therefore, the problem with class registration is there, and not on the terminal server. (I did not work with Russian managed configurations - check the synchronization settings, maybe there is something about the account to exchange on the server and exchange on the client).
Try the third tip from this article - manual registration of COM is described there. In order not to confuse the versions of platforms, recommending that you delete the "old" one on your server.