1s enterprise error server addr. FATAL: database "NAME" does not exist

• Dr. Cuddy: Need a diagnosis. Woman, 26, gas explosion under building, she was pulled out of the rubble after 6 hours. Two surgeries due to multiple fractures and burns…
  Dr. House: I think the broken bones are the result of the building falling on her head.
• Dr. House: Imagine that the roof of the pantry collapsed on your favorite scrubber. And it starts to overheat.
  Cleaner: Why should I love the floor scrubber? Okay... Maybe something in the electrical wiring was damaged from the impact. Or something got inside and ruined it...
  Dr. House: HM interesting. Penetration of infection through lacerations. The bacteria would react to the antibiotics. Too much heat for a virus. Possibly parasites or fungi.
  Cleaner: Or lupus.
  House turns around in surprise.
  Cleaner A: My grandmother has lupus.
  Dr. House:(puzzled) Okay, auto-immune. I'll check for lupus. Although an infection is more suitable. It would be nice to have her map. Let's get to the worst part of the job. To communicate with the family of the scrubber.

• Dr. House: The card says she was sick before the building collapsed.
  Patient's husband A: I think it's a common cold. What do you think is related?
  Dr. House: Her illness with her illness? Sometimes it happens.
• Patient's mother: Does the diary say that my daughter takes these pills?
  Dr. House: No, but from a medical point of view ...
  Dr. Cuddy: Did you find the pills in her house?
  Dr. House: Obviously, she hid them in her purse. I thought it would be indecent to search under 1000 tons of debris.
• Surgeon: She bleeds all over, except that the abortion was done with a shotgun.

This article shows an example of the general principles for analyzing technological issues that may appear when working with 1C:Enterprise 8.1.

Everyone loves to give advice, but when it comes down to it, everyone has more important things to do :))). It will probably be fair to immediately warn that this material was written by me rather as information for reflection, and not as a theory for solving personal problems and unpleasant situations at work. Nevertheless, I think that the examples from my practice given here may be useful in analyzing similar problems.

The following will be considered as examples:

Example 1. The user complained about the impossibility of starting 1C: Accounting.

Message text:

"Error connecting to server 1c: Enterprise 8.1:
server_addr=App1С:1540=Error network access to the server
(Windows sockets - 10061(0x0000274D)
No connection could be made because the target machine actively refused it) line =567

Example 2. "Lost" access to the infobase.

Message text:

Error while performing an operation with an infobase

Microsoft OLE DB provider for SQL Server: Login failed for user 'user1c'

H RESULT=80040E4D, SQLSrvr: Error state=1, Severity=E, native=18456, line=1

Example 3. Strange "unknown" error.

Message text: "Happened Unknown error on the server 1C enterprise (80010108) "

1. Definition of the text (manifestation) of the error and localization of the source of occurrence

• Fix the error (text and/or other information that may be useful for problem analysis). It is better to fix the problem with the help of a technological log. Conclusion: if you do not use the technological log for other tasks, configure it to permanently collect "exception" events (EXCP) and generate dumps in case of a platform crash.
• Record the time the error occurred. This will later help to localize the place of study of various logs.
• READ the text of the message, try to immediately understand the source of the problem from the content of this text.
• Search for a solution in the text of the message on the Internet or in other sources of solution known to you.
• Those who have not previously dealt with solving problems with platform errors will not solve them, look for those who have done or are doing this.

Note. Example 1. Searching below in the section "Where can I find a ready-made solution" for the text "10061" given on this page will immediately show an explanation of the reason and solution: service stopped on application server " Server agent 1s:Enterprise 8.1". Accordingly, it must be launched, for example, from the command line:

net start Server Agent 1c:Enterprise 8.1

If the application server does not start, in some cases make a copy of the C:\Program Files\1cv81\server folder and delete the contents before trying to start.

The 1C:Enterprise and PostgreSQL server bundle is the second most popular among 1C installations and the most used solution on the Linux platform. Unlike implementations in Windows base and MSSQL, where it's hard to make it not work, Linux-based implementations are fraught with pitfalls for the inexperienced administrator. It often happens that everything seems to be done correctly, but error follows error. Today we will consider the most typical of them.

general information

Before you start looking for installation errors and, in general, start implementing the server version of 1C:Enterprise, it would be nice to refresh your understanding of how it works:

In small implementations, the 1C server and the DBMS server are usually combined on the same physical server, which narrows the circle a little possible errors. In our case, we will consider the situation when the servers are separated by different machines. In our test lab, we deployed the following schema:

We have two servers running Ubuntu 12.04 x64, one of them has a 1C: Enterprise version 8.3 server installed, the other has PostgreSQL 9.04 from Ethersoft, as well as a client under Windows control. We remind you that the client is working only with the 1C server, which, in turn, generates the necessary queries to the DBMS server. No requests from the client to the database management server not happening.

IMPORTANT: user "postgres" is not authenticated (Ident)

This error occurs when servers are spread across different PCs due to incorrectly configured authentication in local network. To fix, open /var/lib/pgsql/data/pg_hba.conf, find the line:

Host all all 192.168.31.0/24 ident

and make it look like this:

Host all all 192.168.31.0/24 md5

where 192.168.31.0/24 - the range of your local network. If there is no such line, it should be created in the section IPv4 local connections.

Database server not found
could not translate host name "NAME" to address: Temporary failure in name resolution

At first glance, the error is clear: the client cannot resolve the name of the DBMS server, typical mistake for small networks where there is no local DNS server. As a solution, add an entry to the file hosts on the client, which does not give any result...

And now we recall what was said a little earlier. The client of the DBMS server is the 1C server, but not the client PC, therefore, the entry must be added on the 1C: Enterprise server to the file /etc/hosts on the Linux platform or on Windows platform.

A similar error will occur if you forgot to add record type A for the DBMS server on the local DNS server.

Error while performing an operation with an infobase
server_addr=NAME descr=11001(0x00002AF9): This host is unknown.

Like the previous one, this error is related to wrong resolution server name client. This time it was a client PC. As a solution, add to the file /etc/hosts on the Linux platform or C:\Windows\System32\drivers\etc\hosts on the platform Windows entry type:

192.168.31.83SRV-1C-1204

where you specify the address and name of your 1C:Enterprise server. If using local DNS, add A-record for server 1C.

DBMS Error: DATABASE is not usable

A much more serious error, which indicates that you have installed a version of PostgreSQL that is incompatible with 1C:Enterprise or made gross errors during installation, for example, you did not install all the necessary dependencies, in particular the library libICU.

If you have sufficient experience Linux administration systems, you can try to install the necessary libraries and re-initialize the DBMS cluster. V otherwise PostgreSQL is better to reinstall, not forgetting to delete the contents of the folder /var/lib/pgsql.

Also given error may occur when using assemblies 9.1.x and 9.2.x [email protected] , see below for details.

DBMS error:
ERROR: could not load library "/usr/lib/x86_64-linux-gnu/postgresql/fasttrun.so"

Pretty specific error specific to assemblies 9.1.x and 9.2.x [email protected] , may also result in the previous error. The reason lies in an unfixed bug in the fasttrun.so library. The solution is to roll back to the assembly 9.0.x [email protected] .

DBMS error
ERROR: type "mvarchar" does not exist at character 31

Occurs if the database was created without the help of the 1C:Enterprise system. Remember, to work with 1C, databases should be created only using the tools of the 1C platform: through the console

or through the 1C launcher.

Database server not found
IMPORTANT: user "postgres" is not authenticated (by password)

A very simple mistake. The postgres superuser password is incorrect. There are two possible solutions: remember the password or change it. In the second case, you will need to change the password in the properties of all existing infobases via the snap-in Administration of 1C Enterprise servers.

Database server not found
FATAL: database "NAME" does not exist

Another very simple mistake. Its meaning is reduced to the fact that the specified database does not exist. Most often it occurs due to an error in specifying the database name. It should be remembered that the 1C infobase in the cluster and the DBMS database are two different entities and may have different names. It should also be remembered that Linux systems case sensitive and for them unf83 and UNF83 two different names.

• Tags:

When connecting to the 1C server from the console, we get:

Error on the server or the connection was terminated by the administrator
Stream format error

At startup SQL databases we get an error:

An error occurred on the server or the connection was terminated by the administrator.
Stream format error

And so, the initial data:

Freshly installed Windows 7 Professional x64, all updates, etc. (problem occurs on both Server 2008 and 2008R2)

Installed server 1C x64 (32bit also tried)

Everything works until reboot. After rebooting, when trying to connect to the database in SQL or opening a cluster in the 1C console, we get a whack with the following pictures:

When connecting to the 1C server from the console, we get:

Error connecting to the server 1C: Enterprise 8.2:
Error on the server or the connection was terminated by the administrator
Stream format error

When starting the SQL database, we get an error:

An error occurred while performing an operation with an infobase.
An error occurred on the server or the connection was terminated by the administrator.
Stream format error

To be able to start the database and connect to the cluster from the console, only the following helped:

1. Stop the server service 1C:Enterprise 8.2

2. Deleting processes rmngr.exe rphost.exe (it crashes when rmngr.exe ends).

3. Cleaning the directory C:\Program Files\1cv82\srvinfo\reg_1541\snccntx (for a 32-bit server C:\Program Files (x86)\1cv82\srvinfo\reg_1541\snccntx)

4. Starting the server service 1C:Enterprise 8.2

However, in the process of working with the SQL conf, it was possible to unexpectedly catch the emergency closure of 1Ski with the subsequent receipt of the same errors.

Have been tested:

1. different releases, different servers,

2. various users: System, Administrator, USR1CV82.

3. forced setting of full rights to these users on directories C:\Program Files\1cv82\ (on a 32-bit server C:\Program Files (x86)\1cv82\) with inheritance to child objects.

4. Dozens of reloads and more.

However, the reason turned out to be much more unexpected!

Dereferencing in Windows 7 (Server 2008, 2008R2, probably 2012 as well)

Try to ping your computer by name. What you see will determine the applicability of my solution.

It's easy to do this:

1. Launch command prompt (Win+R, type cmd and press OK)

2. In command line type "Ping" followed by a space and your computer's name. It is the name, not its IP address. Press Enter.

3. If the system began to ping itself through an address of the form fabc:de12:3456:7890:ABCD:EF98:7654:3210, or another IP address different from yours

Welcome to the private club of bugs dereferencing by Windows versions 7.

The basis of the problem lies in the fact that the 1C server cannot identify itself by name.

But, displaying your IP as IPv6 is one of the most common causes occurrence of this error.

Another reason may be a periodic connection to another network (let's say VPN) when it is created new interface and Winda again starts dereferencing itself "incorrectly".

Below I will describe two solutions to bypass this "feature".

I want to warn you first:

You perform all actions with your computer at your own peril and risk.

Option number 1 Add your PC and its IP to Hosts

1. You need to find the hosts file in the C:\Windows\System32\drivers\etc folder. If you do not see the Hosts file in this folder, then it is simply hidden. Then you can press the ALT key and, in the menu that appears, select "Tools" - "Folder Options" - "View" and take off check the box "Hide protected system files". You can also set the radio button "Show hidden files, folders, drives", then everything will be visible.(After manipulations with Hosts, I recommend returning the checkmark to its original place, so as not to accidentally hook something in the future)

2. Open this file in Notepad (notepad) and add a line like 192.168.0.1 Server (IP address PC Name) to the end. Save and close the file.

3. Try to ping your PC again through the name. If you do not see the IP you need again - something went wrong ... Perhaps the antivirus returned old version file (Casper loves this) or something else.

In general, you need to achieve the correct address when pinging through the name.

Trying to be ahead of the rest, Windows 7 not only puts IPv6 on all interfaces at once, it also sets it as the default when dereferencing. However, few people use this protocol today, and therefore it can / should be disabled. Remember that unchecking the IPv6 protocol in the interface network card won't do anything!

1. Click Win+R, type regedit and press Enter. The Registry Editor will open.
2. If you are prompted to allow actions, click in the dialog box User Account Control button Continue.
3. Locate and select the following registry subkey:

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\

4. Double click the item DisabledComponents to change a parameter DisabledComponents.
   If the parameter DisabledComponents missing, it needs to be created. For this:
   1. Being on a branch parameters, on the menu Edit select item Create, and then - DWORD value (32 bits).
   2. Type DisabledComponents and press ENTER.

      I want to remind you that both solutions are not a panacea, and do not really allow you to bypass the error, and not eliminate its cause.

Question: Com Error in ProcessingFill

I try the same thing in the 8.1 database itself, but there is no error, and I don’t enter the Fill Processing either.
What can be the jamb?

Answer: turboq, a crookedly written document module!

Added after 5 minutes
She is not called! She's trying to compile! But since when connecting via ComConnectorDialogModeQuestion DOES NOT EXIST, the document module cannot be compiled.
For such cases when it is necessary to implement work with a dialog in the object module, use instructions to the preprocessor

This is not your mistake, but the error of the document module in the database to which you are connecting.

In the database, the code is executed on the client and the Dialog Mode has a question, so everything happens without errors

Use not ComConnector, V8.Application to connect, then interface things will be available to you

Added after 5 minutes
=======================================================================================================================
from outer join description (JD) I highlighted in bold what you should read about ComConnections

Description:

In general, working with 1C:Enterprise 8 via an external connection is similar to working with 1C:Enterprise in the Automation server mode. The main differences are as follows:

• In the case of an Automation server, a full-fledged 1C:Enterprise 8 application is launched, and in the case of an external connection, a relatively small in-process COM server is launched.

• When working through an external connection, they are not available. functionality in one way or another connected with the organization user interface 1C:Enterprise 8;

• External connection does not use module managed application(module regular application) 1C:Enterprise 8 configuration. Its role when working with an external connection is played by the external connection module.

• More quick installation connections, as no separate process is required operating system, and all actions are performed within the calling process;

• Faster access to the properties and methods of 1C:Enterprise objects, since the organization of the appeal does not require the organization of interprocess communication;

• Less consumption of operating system resources.

• a COM connection manager is created, with the help of which a connection is established;
• a call is made to the Connect method of the COM connection manager. The Connect method returns an external connection to the 1C:Enterprise 8 infobase;

• valid methods, properties, and objects are accessed through an outer join information base with which the connection is established.

Availability: