The need for a forced shutdown of the user's work mainly arises in the following cases:
- Update information base;
- Adding a new metadata object to the configuration;
- Carrying out preventive and repair work on the server;
- A hung user session that prevents the application from restarting.
In this article, we will try to tell you how to end a user session, what tools an administrator has in his arsenal to complete this task, what termination options are provided by the file, and which client-server version of 1C.
It is important to remember that when you force a session to end, you may lose data. So in order to avoid unpleasant situations, it is advisable to warn users in advance about the disconnection.
Closing sessions from the configurator
When changes are made to the database structure, dynamic configuration updates become unavailable. And an information window appears on the screen (Fig. 1).
The sequence of actions in this case is obvious:
- You must click the "End sessions and repeat" button;
- Wait for the database restructuring window;
- Press OK.
It should be noted that changes made to the program code do not require users to shut down, but without restarting the application on each specific computer, they will not work on this device.
Ending sessions directly from the program
Most of the standard products of the 1C company of the eighth version have in their set a mechanism that allows you to easily terminate the user's work remotely and provide the administrator with exclusive access to the database. This is the "Blocking connections to the infobase" processing.
You can find it at one of two addresses:
- In one of the submenus of the "Service" section;
- By going to the Operations->Processing section.
Fig.2
Appearance processing is shown in Fig.2.
Features of this processing:
- Checking and unchecking the box, and clicking the "Record" button, turns on and off blocking users, deleting sessions and preventing new connections from being created;
- The lock end time cannot be empty or less than its start time;
- In the case when the “Permission code” parameter is set, it can be written in the launch line to ignore the blocking by specifying “/UC” before the code;
- If the "Permission code" is not specified, then it will be problematic to get into the database before the expiration of the blocking period (in the file version of work, you can try to delete the 1CVcdn file from the database folder);
- If instead of the “/UС” parameter and the password separated by a space, specify “/CAllow Users”, where C is Latin, you can completely disable the lock for all users;
- Pressing the Active Users button brings up a window with complete list users (Fig. 3), from where you can open the "Registration Log" or end the session of each specific user.
Fig.3
The above two options work fine in both file and client-server mode. Further we will consider cases specific only for server work.
Removing users from rdp
It is important to remember that disconnecting user sessions from servers is possible only if you have certain rights to do so.
When working from a remote desktop, you can end user sessions using the standard task manager. Simply terminating sessions - a bit wrong, but enough effective way.
The second option is to use Task Manager − remote connection with the ability to manage each specific session and exit the program according to all the rules. This method is long, and no one guarantees that while one user is logged out, the program will not be launched by any other worker.
Removing users through the server console
Having Administrator rights for a 1C server cluster, you must:
Very often, when working in server mode, hung user sessions are not visible by means of the platform; they can only be deleted through the console.
The most radical way to terminate sessions
The situation when the above methods did not work is extremely rare. But if it occurs, there is another radical way to interrupt connections with the database: a physical reboot of the server.
Of course, users who do not have time to finish the work and save the data will be extremely outraged by such a shameless attitude, but it is fast and it is extremely effective.
Administration and control of 1C 8.3 users is an integral part of the implementation and support of any software product firm 1C. In fact, this is a simple task, and, I am sure, any person can easily cope with it. Consider the process of administering 1C users in more detail.
User management in 1C is a fairly simple and intuitive process, but it still needs a description.
Conditionally administration and control includes:
- user creation;
- setting user rights;
- view active users;
- analysis of user actions.
Let's consider each of these points in more detail:
Creation and installation of user rights 1C 8.2
Depending on the configuration, users are entered either in the configurator or in user mode. Almost all modern configurations support user input in 1C: Enterprise 8 mode. Also in 1C: Enterprise mode, as a rule, they enter Extra options users.
However, regardless of the configuration, the first user with administrative rights is always entered in configurator mode. Therefore, we will consider both modes of user input.
Entering users in the Configurator
To enter the 1C Configurator mode, select the Configurator option in the database selection list:
After logging in, select Administration - Users from the menu. A list of users will open, if you start the first user, it will be empty. Let's add a new user "Administrator":
On this page you must specify the user settings:
- Name and Full name— username.
- If the flag is set Authentication 1C: Enterprises, then the items will become available Password(password that is used to enter 1C), The user is not allowed to change the password(makes available the ability to change the password by the user in user mode), Show in selection list(makes available the selection of a user in the list, otherwise the username must be entered manually).
- Authentication operating system — flag responsible for the possibility of authorization using the username of the operating system. User- Username information system(for example, \\dom\kirill, where dom is the network domain and kirill is the OS username). 1C at startup first checks authorization through the OS, and then authorization 1C 8.2.
- Open ID authentication- enabling authorization using OpenID technology . Open ID is an open decentralized system that allows the user to use a single account to authenticate on a variety of unrelated sites, portals, blogs and forums.
Get 267 1C video lessons for free:
On the tab Other you need to specify the appropriate roles for the user (). In our case, we will specify for the administrator Full rights. For other users, the required roles can be flagged here. User rights are summarized from the available objects of different roles. Those. if the user has two roles selected, one has access to the "Nomenclature" directory, and the second role does not, access will be. For any user without "Full rights" the user role must be set(if present).
Also on this tab you can specify Main interface(only works for regular forms). Default language— if the configuration is developed in several languages. Start mode- managed or regular application.
Creating a user in 1C Accounting 2.0
After a user with full rights is registered in the system, users can be entered in 1C: Enterprise mode. For example, let's create a user in the most common configuration - Enterprise Accounting 8.2.
To do this, select the menu item Service - User and Access Management. The "Users" directory will open. Create a new user:
Enter information about the user and its main ones, click the "OK" button: the system will offer to automatically create a database user:
You must agree, the form of the new database user will be displayed:
That's all! The creation of the user and the assignment of rights to him is completed.
Viewing active users in the 1C database
To view users working in the database in 1C: Enterprise mode, select the item Service - Active Users. A list of users working in the database will open:
How to disable users in 1C 8.3 and 8.2
There are two ways to disable an active user in the 1C database:
- in the program interface (for configurations 1C Accounting 3.0, Trade Management 11, etc.);
- via the server cluster console (only available in client-server mode).
From the interface
In user mode, you can kick out a hung user by going to the "Administration" - "Support and maintenance" menu, then selecting the "Active users" item:
Select the desired user from the list and click the "Finish" button.
From the cluster console
If you have access to the administrative panel of the 1C server, you can end the session using it. We go to the console, find the hung user in the "Sessions" menu, call context menu and click "Delete":
User control 1C 8.3
To view the user's work history, go to the menu item Service - :
Hello Dmitry! Please teach me how to expel users forcibly from the database in order to update the configuration. Thanks in advance.
From user: Svetlana Nikolaevna
Hello, Svetlana Nikolaevna!
In order to expel users from the database, you need to have administrator rights.
We go to the section Administration, Support and maintenance:
Choose Blocking user work:
You can view the list of active users from the form by clicking the button.
We fill in the message that users will see on their screens, set the blocking interval (if you do not know the end time, leave the field blank). Install also unlock code, because blocking will also affect your active session, for example, set 1234 .
Click Set lock. A warning message will appear:
We agree. Now the form says in red that the blocking will begin soon.
For active users at this time, the following window appears:
Closer to the beginning of the blocking, it starts to appear every minute:
The user needs to complete his work in the program and exit. If it does not exit on its own, the program will close automatically. When trying to login to the database, the user will receive the following warning:
The user who set the block also receives a message:
Let's get out of the base.
Because the lock applies to all sessions of all users, we will need to set the launch parameter (this is where we need Unlock code):
On the second tab, we write the database launch parameter (where 1234 is our code):
We click ready. Now we can enter both the configurator and the user mode.
To unlock the base, you need to return to the lock form and click Remove lock.
If a blocking end date has been set, then the blocking will end automatically when it occurs.
To carry out routine maintenance in the 1C:Enterprise 8 information base, it is often necessary to obtain exclusive access to the database. For example, to perform a database backup or perform routine maintenance on the DBMS server (reindexing, etc.), you must disable all active sessions.
Let's consider a simple way to disconnect users from an infobase using the standard functionality of the 1C:Enterprise server.
Standard functionality
I’ll make a reservation right away that we will be talking about the client-server version of 1C: Enterprise 8. To disable sessions, go to the server administration console. There we will find the necessary infobase in the list:
Going into the IB properties, set the option "Locking the start of sessions is enabled." In this case, it may be necessary to enter the username/password account infobase administrator.
Don't forget to set the session blocking period. You should also ensure that all background jobs must be stopped while sessions are blocked. This is done with the option "Lock routine tasks enabled".
If necessary, you can set the message text for users who will be notified 5 minutes before the sessions are blocked, as well as the permission code for entering the infobase during the session blocking period.
The permission code can be used to enter the infobase to perform routine maintenance while other sessions are not active. You need to enter the permission code when connecting to the database using the parameters. For example, this is what the parameter passed to the server would look like if the permission code is "123456".
By entering the database in this way, we will get exclusive access to the infobase. Other sessions will not be able to join us.
The notification to the user that sessions are locked looks like this (depending on the message entered by the administrator). It appears every minute 5 minutes before the blocking period.
At the beginning of the session blocking period, a notification first appears:
After the session ends.
Active sessions can also be disabled by removing them from the list of active sessions. Such an action is sometimes necessary to end hung sessions.
In practice, disconnecting users is best communicated in advance to reduce the risk of losing data entered by users but not yet saved.