It happens one day, out of nowhere, the 1C program gives us: Error connecting to 1C:Enterprise server Not a single worker process is running. Connection to the database is impossible.
Several options for finding errors and solutions:
1. Server glitch - anything can happen
Stop the processes in the task manager: ragent rphost rmngr and Start the 1C:Enterprise Server Agent service
2. In case of a sudden power outage or similar situations, the file is damagedsrvribrg.lst
You need to delete everything from the folder srvinfo
For Windows go to the catalog c:\program files\1c\1cv82\srvinfo, If Linux usr1cv8/home/.1cv8/1C/1cv8 ...
Through Administration of 1C Enterprise servers, create a new 1C cluster and add information bases
3. Renamed the server on which the 1C agent service
After renaming a Windows Server 2008 server with 1C:Enterprise 8.2 installed, the 1C:Enterprise 8.2 Server Agent service stopped working. It starts, runs for a few seconds and stops. If you connect to the 1C:Enterprise 8.2 server via the server console, an error occurs:
Error connecting to the 1C:Enterprise 8.2 server server_addr=tcp://SERVER:1540 descr=Error in network access to the server (Windows Sockets - 10061(0x0000274D). The connection was not established because the target computer rejected the connection request.) line =590 file=.\Src\DataExchangeTcpClientItmpl.cpp
When connecting to the database on this server we have the following error:
No worker processes are running. Connection to the database is impossible.
This problem is due to the fact that the settings of the 1C:Enterprise server cluster are stored in files in the srvinfo directory (the path to it is indicated by the -d parameter in the properties of the 1C:Enterprise Server Agent service). Therefore, after changing the computer name, you must additionally perform the following steps:
For Windows go to the catalog c:\program files\1c\1cv82\srvinfo, If Linux- then the files are located in the home directory of the user on whose behalf the service is launched: usr1cv8/home/.1cv8/1C/1cv8 ...
Edit two files in any text editor: srvinfo\srvribrg.lst and srvinfo\reg_1541\1CV8Reg.lst. Replace the old server name in these files with the new one.
Start the 1C:Enterprise Server Agent service.
After completing these steps - Everything will be fine
if suddenly not, repeat step 2!
Last week they delivered a new server for 1C. HP Proliant 380 G6 2 processors of 2.58 GHz, 6 GB of RAM and three disks, each with a capacity of 72 GB and a rotation speed of 15K. Since 1C users can’t handle Windows 2008 (for now!), I installed Windows Server 2003 x64 Standard Edition.
The first rake came when we launched the server into “combat mode”, naturally, renaming it: the “1C:Enterprise 8.2 Server Agent” service began to crash (it starts, runs for 10 seconds and stops).
When connecting to the 1C:Enterprise 8.2 server via the server console, we receive the error:
"Error connecting to server 1C:Enterprise 8.2
server_addr=tcp://s02:1540 descr=Error in network access to server
(Windows Sockets - 10061(0x0000274D). The connection was not established because the destination computer rejected the connection request.) line=590 file=.\Src\DataExchangeTcpClientItmpl.cpp"
When connecting to a database on this server we receive the following error:
"No worker process is running. Connection to the database is impossible."
Firewall is disabled, DEP is also disabled (enabled only for Windows services). Rebooting the server and reinstalling the platform did not help. We looked through the registry twice, also to no avail.
It turns out that the settings for the 1C:Enterprise server cluster are stored in the srvinfo directory (the path to this directory can be found in the properties of the "1C:Enterprise 8.2 Server Agent" service - parameter -d). This directory stores the name of the cluster and its settings (including security) and lists of information security systems connected to this cluster and their settings. These are two files: srvinfo\srvribrg.lst and srvinfo\reg_1541\1CV8Reg.lst. The old server name remains in these configuration files.
Next bug: V82.ComConnector stopped calling - wrote Class not registered. After some googling I found a solution to the problem on the resource http://www.gilev.ru/1c/hasp/
15. For COM connections to a 64-bit application server, use
only possible on the computer on which the key is installed
64-bit 1C:Enterprise server (and not from a terminal session).
For
using V81.COMConnector on computers that only have access to
client keys, you can register the 32-bit V81.COMConnector in
COM+.
- start Component Services;
- create an empty COM+ application with Activation type - Server application and a name, for example, V81_COMConnector, specify the Windows user name under which the component will be launched in the address space of a separate dllhost.exe process;
- in the Components branch, add a new component comcntr.dll from the 1C:Enterprise load modules directory.
In this case, V81.COMConnector will run in a separate 32-bit process and can be used by both 32-bit and 64-bit applications.
I would like to add that the user under whom the 8.2 server is running needs to be added to the users of this new component.
Errors that appear when working with software products most often make it impossible to use them. And the lack of special knowledge to understand the operating algorithms also creates the impossibility of diagnosing and correcting failures that occur. In this article, let’s look at the problem “1C:Enterprise Server is not detected, how can I fix the launch of the agent server?”
There are several ways to fix the problem in 1C.
The errors that arise have different background details, they can be sorted by levels of occurrence:
- Incorrect coding by the developers of the one-esque itself;
- Errors made by programmers who modify (change) the product in relation to the requirements (tasks) of a specific user;
- Failures caused by cache memory errors, most often perplexing programmers;
As for the “1C:Enterprise server not detected” error, it is impossible to classify it as one of the above, since such a notification is an indication to the user of failure to perform a certain necessary action for the program to work.
Let's fix it - start the server
So, the situation that this publication is devoted to occurs when the agent-server service is either disabled or stopped. Let us note that, as a rule, the reasons for this remain unclear (who admits it).
This service runs in two ways - either as an application or as a service. Let's see how to do it in both cases:
As an application
To run it as an application, run the command:
In this case, you specify (in your settings) the port, port ranges, level and directory. If these parameters are not specified, their values will be set by the program “by default”.
As a service
When, during the first installation of 1C, the startup option was selected as a service, it is registered and subsequently should be launched automatically (every time the operating system is started).
If the agent was initially installed by the application, then you can manually register it and launch it. This will happen with the command (don't forget about the parameters):
ragent.exe -instsrvc -usr ‹specify the name› -pwd ‹specify the password›
Port ‹for port› -regport ‹for port› -range ‹port ranges›
Seclev ‹desired level› -d ‹specify directory›
The result of registration will be the creation of a new Service (in this case for 1C version 8.3 for 64-bit):
For memory
To delete (unregister) a service:
Stop:
Now you know everything about the causes of the “1C:Enterprise server not detected” problem and what needs to be done when it appears.
Leave your comments.
Loading...
