Incorrect path to file 1cv8 cdn what to do. Starting a session with the infobase is prohibited. Backup. Limitations of the free version of the program

57
It happens, one day, out of nowhere, the 1C program gives us: Error connecting to the 1C:Enterprise server. Not a single worker process is running. Connection to the database is impossible. Several options for finding errors and solutions: ... 28
I have already written several articles: Setting up and optimizing a server, cluster 8.3 Adding, restarting, optimizing the work processes of a cluster server is now a little more detailed: Cluster 1C 8.3 First of all, after... 18
Many people have problems with rphost.exe, of various types: rphost takes up all the memory, rphost loads the processor, rphost eats up memory, and 1C is not even running, and in the manager the following: every minute the calculation is 2-3 megabytes. How to... 17
If the background COM connection process fails with an error: (Processing.XMLDataExchange.ObjectModule(15947)): Error when calling the constructor (COMObject): -2147221005(0x800401F3): Invalid class string ComConnecto library must be registered

  • Firstly, it will help you better understand what happened. And in rarer cases, it can even help solve the problem yourself.
  • Secondly, if you couldn’t cope on your own, then first and foremost you should contact a specialist for technical support with the contents of the information and diagnostic window that appears.

Let's take a closer look at the contents of the received dialog message:

Line 1.A “Starting a session with the infobase is prohibited.” is a standard entry indicating that user entry into the program has been blocked. With such blocking, a special file with the extension “.cdn” is automatically created in the infobase directory (for more details, see the following sections).

Line 1.B usually indicates the reason, duration of blocking, as well as other useful information. Depending on who or what (in the case of a system) the entry blocking was installed, as well as for what purpose, the information in this block may be different. The line “Backup” is a standard entry for manual or routine backup (in this case the line “To perform a backup.”) of the information base using 1C Enterprise tools is also typical.

An administrator, in case of creating a block in the user mode of 1C 8.3 Enterprise, or a 1C programmer, in case of setting a block programmatically in the configurator, can come up with his own messages:

Line 2 provides a hint on how you can run the program from the Windows command line if you know the so-called “permission code” (see next step).

Line 3 explains the process and what the buttons do.

Step 2. Solution on how to remove the lock and enter the 1C 8.3 database

Session locks can be roughly classified as follows:

  • Planned. When a session lock was started manually or automatically, serving a scheduled process in the 1C database (backup, routine task, update);
  • Others, erroneous. When a lock is installed as a result of erroneous user actions or errors encountered by the system itself, when it does not automatically remove the previously installed lock. For example, a backup process was started, but the user interrupted it by forcefully closing the program.

Method 1

In both cases, when setting session blocking, as mentioned above, a file with “.cdn” permission is created in the storage directory of the current infobase:

Thus, a simple solution to the program launch error due to a session lock is to delete the 1Cv8.cdn file.

However, the user should first ask the question: “After all, if sessions are blocked, does this mean that this is due to something?” Perhaps another user with administrative functions (hereinafter referred to as the administrator) launched a really important task or processing in 1C 8.3 Accounting that cannot tolerate the presence of several users in the database at the same time.

Method 2

If such a situation is possible, then you should contact the administrator and find out whether you can enter the database and whether he has a special permission code, which was mentioned just above. In this case, we will use the second method - by entering a blocked infobase by launching the program from the command line, specifying the permission code in one of the launch parameters:

  • “C:\Program Files (x86)\1cv8\common\1cestart.exe” – path to the 1C Enterprise 8.3 launcher;
  • ENTERPRISE – means that the program will start in user mode, i.e. in 1C Enterprise mode;
  • /F”F:\Bazy1C\Accounting” – denotes the file information base (parameter /F) and the path to it (the server database address is indicated in the /S parameter);
  • /C Allow Users to Work – an optional parameter: if checked, the system will not start, but the lock will be removed (the lock file will be destroyed), and subsequently users will be able to access the information base.

If the parameter is not set, then the specific user is allowed to log in, but the lock is not removed. This user can do a complete unlock in user mode by going to the Support and Maintenance panel (Section Administration - Program Settings command group - Support and Maintenance command:

And calling the form Blocking users by the command of the same name:

In the form that opens, you can unblock sessions by clicking the Unblock button, where /UC12345 – the /UC parameter specifies the permission code (12345). Parameter names are written in English.

For more information about command line parameters, see the 1C 8.3 Enterprise help.

Method 3

There is an alternative and even easier for the user method of using the above parameters for launching an information base (hereinafter referred to as IB) - it is possible to register the required ones in the properties of the database of interest.

1. In the launcher window (marked “A”), select the locked database and click the Change button, after which the window for editing information security properties (marked “B”) will open:

In property Additional launch options we write down the unlock code and, if necessary, a parameter to allow users to work (in this case, after the first launch and before the next launch, this parameter must be deleted). These parameters were described in more detail above.

Note: when an automatic backup occurs (directly or as part of another procedure, for example, during an automated update), the system blocks the 1C 8.3 information base and sets the standard unlock code “ Backup ».

Therefore, if the procedure fails and the database remains blocked, but there is no way to delete the cdn file, then you can use the parameter when starting the information security: /UCBackup.

3. Click the Finish button and return to the launcher window, where we launch IS using the 1C:Enterprise button. Thus, the error “Starting a session with the infobase is prohibited. “Backup” has been eliminated:

If 1C 8.3 Enterprise operates in a client-server version, but the user does not have access rights and the necessary knowledge to administer databases in this mode, then in this case you should contact the system administrator for help. We only note that in the client-server version, in addition to access via the command line with additional parameters, it is possible to remove the blocking using the 1C: Enterprise server cluster administration utility, namely, it is necessary to remove the flag in the properties of the desired infobase Session start blocking is enabled.

Anatomy of the 1Cv8.cdn lock file

The curious can look inside the file 1Cv8.cdn created when sessions are blocked - this is a simple text file that can be opened with the appropriate Notepad editor:

The text in the file is surrounded by curly braces that list the following locking parameters, separated by commas:

  • 1 (0) – sign of setting the blocking (1 – installed; 0 – disabled);
  • 20160706154700 – full date (date + time) of the start of session blocking, in our case it is July 6, 2016 20:00:00;
  • 20160706154700 – full date (date + time) of the end of the session blocking, in our case it is July 06, 2016 20:00:00 (if the end date is not specified, then by default the value 00010101000000 is entered into the parameter);
  • Next comes the text parameter, where the auxiliary text displayed to the user in the dialog box is placed in double quotes;
  • “123” – permission code is specified.

As you can see, the file contains all the parameters displayed in the information and diagnostic dialog box that appears.

On the website you can read other free articles and video tutorials on the 1C Accounting configuration (

Open a text editor in 1 with Enterprise. We write the following code:


“C:Program Files1cv81in1cv8.exe” ENTERPRISE /F”D:ase1cmagazin” /N”Administrator” /P”5555″/CEndUsers /Out d:ackuplog%date%.txt /DisableStartupMessages


“C:Program Files1cv81in1cv8.exe” DESIGNER /F”D:ase1cmagazin” /N”Administrator” /P”55555″ /UCBatchUpdateIB Configuration /DumpIB d:ackupinfobase%date%.dt /Out d:ackuplog1%date%.txt /DisableStartupMessages


“C:Program Files1c v81in1cv8.exe” ENTERPRISE /F”D:ase1cmagazin” /N”Administrator” /P”55555″ /UCBatchUpdateIB Configuration /CAllow Users to Work /Out d:ackuplog2%date%.txt /DisableStartupMessages


/DumpIB d:ackupinfobase%date%.dt - saving the database configuration to a file



“C:Program Files1c v81in1cv8.exe” is the path to your executable,


/F”D:ase1cmagazin”-<Путь>path to the infobase, if it is stored in a file (the file name does not need to be specified)


Accordingly, if the server then


/S<Адрес>
The address of the information base stored on the 1C:Enterprise 8.0 server is as follows:
<Имя компьютера, работающего сервером приложений> <Ссылочное имя информационной базы, известное в рамках сервера 1С:Предприятия 8.0>


/N”Administrator” /P”55555” - user name. The password of the user whose name is specified in the /N parameter must be specified in the same way as in the list of users created in the Configurator. If the user does not have a password, this parameter can be omitted.


/UCBatchUpdateIBConfiguration - allows you to establish a connection with an infobase that is blocked from establishing connections. If a non-empty access code is specified when setting the blocking, then to establish a connection you must specify this access code in the /UC parameter.


/Out d:ackuplog1%date%.txt - setting the file for outputting service messages. If the -NoTruncate switch is specified (separated by a space), the file is not cleared


/DisableStartupMessages - Suppresses startup messages: “The database configuration does not match the saved configuration. Continue?"; “Your computer's capabilities are not sufficient to edit the configuration help. To edit the help, you must install Microsoft Internet Explorer version 6.0 or higher.”; “Your computer’s capabilities are not sufficient to edit HTML documents, including help topics. To edit HTML documents, you must install Microsoft Internet Explorer version 6.0 or higher. In this launch, editing html documents will not be available."



Be very careful with spaces, slashes and quotes.


Save as a file with the bat extension and in OEM encoding. To edit, save it first under a different name in UTF-8 encoding, otherwise you will have to deal with bugs or rewrite the script again.



When you enable the end user mode mode, a key is registered in “Trade Management”


Accordingly, replace /UCBatchUpdateIBConfiguration with it. Otherwise no one will be able to work. Or, in the server console, enter the database (right-click on the properties of the corresponding database) and uncheck the “Blocking of the database” checkbox.


To find out the key in the configurator, call the global search and type “Permission Code”


About removing blocking:


Method 1: Create a copy of the “1C:Enterprise 8” shortcut and add certain parameters in the line with the name of the working folder: “C:Program Files1cv81in1cv8.exe”/UC 123,


where /UC is the parameter for entering the database, regardless of the installed lock


123 - in this case, the password for the installed lock (using a password to set the base lock is OPTIONAL).


2nd method: “Start” - “Run”, specifying “Unblock connections” as the blocking action. Click the “Run” button.


3rd method: remove the “signal” blocking file “1Cv8.cdn” from the database directory.


In client-server version


To perform installation and unlocking actions, you can use the server cluster administration utility of the 1C:Enterprise 8.1 program.


  • Service Processing Options
    In the processing form you can indicate:

    • Sign of setting/unlocking;

    • Period (time) of the start and end of the blocking;

    • The text of the message displayed to users when warning about the planned blocking of connections;

    • The permission code is an arbitrary string, using which as the startup parameter “/UC” you can later enter the infobase, despite the blocking.


Having launched the 1C program once, at startup I saw the error “Starting a session with the infobase is prohibited. Backup". I was very surprised - I didn’t set any blocking myself. After a little analysis, the reason turned out to be a “glitch” of automatic archival copying, which is built into (one of the subsystems).

The error looks like this:

The problem turned out to be that when setting up the creation of archive copies of the database, the system automatically sets a block on the entrance to the information base. It prevents users from starting the program while the process is running.

But sometimes it happens that after copying the system cannot remove it. In this case, we get the error “Starting a session with the infobase is prohibited...”

Get 267 video lessons on 1C for free:

Solution

The easiest way to fix the problem is to delete the file 1Cv8.cdn(infobase lock file) from the database folder.

For example, in my screenshot above the location of the base is as follows:

You need to go to this folder, and then find and delete 1Cv8.cdn.

Unblocking the 1C client-server database

If you have access to the server console, removing the lock is very simple. Just go to the infobase properties and remove the “Session start blocking is enabled” flag: