Configuration changes are blocked by distributed security tools. "Data is received from the node for which configuration changes have been registered"

Hello, dear readers of our blog site! Today we'll talk about
fixing two errors that may arise during exchange in a distributed information base (RIB). Such errors can occur if you have changed the configuration of your database and are trying to transfer these changes from the central database to the peripheral one. For example, in the way that was described. Let's get started!

These are the messages that may appear when you try to make an exchange using RIB:

"Data is received from the node for which
configuration changes have been logged.
Changes need to be transferred
configurations to the node."


“Distributed information security node configuration
not as expected!”

Let's look at the steps to help correct the situation. Before we start, let's create our information database!!!

1. Let's take the configuration file with the update and open it central base in the Configurator and load it (Configuration-Load configuration from file...). Let's save the information security (F7).
2. Let's go to and upload to a file for the peripheral database:
   
   
   • Select the exchange plan in the list, then Right click call context menu and select the item “Save changes...”.
3. Now let's deal with peripheral information security. Let's open it in exclusive mode so that there are no users, and also close the Configurator. Now you need to remember the node that is the main one for the current database. Open Operations-Exchange Plans-Select your exchange plan (for example, “By warehouse”). In the list of exchange plans, the main node is the item with the yellow icon. This information will be useful to us in the seventh point. Let’s open processing and click the “Cancel assignment of master node” button.
4. Now let's open the peripheral information security in the Configurator and load the same configuration file that we loaded in the first step in the central database (Configuration-Load configuration from file...). Let's save the information security (F7).
5. Let's change the support settings (Configuration-Support-Support Settings...). In the dialog, select the cell in the table at the intersection of the first row and second column. Then double-click to open the “Support Rules Settings” dialog. In it, check the “Install for subordinate objects” flag and click the “OK” button. Close the support settings dialog by clicking the “Close” button. Save IB (F7). Let's close the Configurator.
6. Now let’s open the peripheral information security again in 1C:Enterprise exclusive mode so that there are no users, and also close the Configurator. Let's open the processing Installation of the MainNodeDB.epf and select the exchange plan that we want to install as the main node (in the fourth point we remembered this node). Then click the “Install Master Node” button. After this, the current information security will again become peripheral.
7. Now in the current information security (peripheral) we will open the exchange plans and download the file with the exchange from the Central database, which we received in the third step:
   
   
   • Operations-Exchange Plans-Select our exchange plan (for example, “By warehouse”).
8. If everything went well, then we will upload the exchange for the Central database in the current information security (peripheral):
   
   
   • Operations-Exchange Plans-Select our exchange plan (for example, “By warehouse”).
   • Select the exchange plan in the list, then Right-click to open the context menu and select “Save changes...”.
   • In the dialog, indicate the path and name of the exchange file. Click the “OK” button.
9. Now let’s try to load this file into the Central Database and open it in 1C:Enterprise mode:
   
   
   • Operations-Exchange Plans-Select our exchange plan (for example, “By warehouse”).
   • Select the exchange plan in the list - Right-click to call up the context menu and select “Read changes...”
   • In the dialog, select the exchange file. Click the “OK” button.

To avoid problems with working copies, do first

• The message file has already been loaded into the receiving database. You need to download it from the source database again.

Error "Error when copying a file from an FTP resource... Error working with the Internet: Timeout was reached"

• It is not possible to copy from the site through which the exchange takes place required file. This could be due to your internet being slow or problems with the site itself.
• You need to try to repeat the exchange after 15-30 minutes.

Error: Editing data for this period is prohibited. Changes cannot be recorded..."

• The downloaded data contains documents from the closed period.
• It is necessary to carry out the exchange under users who have the right to change documents during this period.

Error: Database configuration updates need to be performed. The update can be performed in configurator mode"

Reason: The programmers changed the configuration in the center. Solution: Update the changed configuration in the peripheral database. For this:

• Go to the configurator.
• Execute the menu item “Configurator / Update database configuration”.
• If a question is displayed with the answers only “Repeat”, “Cancel”, “Update dynamically”, click the “Update dynamically” button.
• If a question is given with only “Retry” and “Cancel” answers.
  • all users log out of 1C.
  • press the “Repeat” button.
• Answer the remaining questions in the affirmative: “Yes”, “Accept”, “OK”.
• Close the configurator.
• Repeat loading from the center.

Error: “The configuration does not match the expected one”, “Attempting to accept changes from an unknown configuration”

• Database error.
• It is necessary to contact specialists.

The exchange takes a very long time and freezes

Possible reasons:

• There's a lot of data coming in.
  • Find out from the sender whether he performed a group change of documents (posting, changing details, etc.).
  • If so, leave the computer with the exchange overnight.
• A large file cannot be downloaded from the Internet.
  • If the file is large (80-100 MB or more), then perhaps 1C simply cannot download it.
  • You need to download the file and upload it to 1C manually (possibly with the help of specialists).
    • menu item “Operations” / Exchange plans / Full / Button on the “Read message” panel.
• The database is damaged:
  • Try it
• If these steps do not help, you will have to contact specialists.

• If the error cannot be corrected, call the emergency support number +7 (8512) 64-55-05.
• Our specialist will help you, no matter what city you are in.

A distributed information base (DIB) is often used to organize the work of branches and divisions, allowing for the rapid exchange of information while maintaining the required degree of autonomy. Although this technology It's quite reliable, and it breaks down from time to time. Today we will look at one of the fairly common errors: We will tell you about the reasons for its occurrence and methods of dealing with it.

Let's start, as always, from the beginning. After you have created the RIB all changes to the configuration information base can only be entered in the main node. Subsequently, during the next exchange, all changes will be transferred to the slave nodes and automatically applied there. But it was smooth on paper...

In practice, it sometimes happens that between exchange sessions, especially if the channel on the periphery is bad, the configuration of the main node manages to change twice. For example, they made changes, uploaded them, the peripheral database received the changes, but has not yet applied them, which may take some time, and has not yet sent confirmation. If you make changes again during this period and upload the exchange again, it turns out that the center expects to see configuration No. 1 in the peripheral node and will try to update it to configuration No. 3, but in fact will encounter configuration No. 2 there. Sometimes a similar situation occurs during dynamic updating of the central database. As a result, the exchange will become impossible and you will receive a message stating that The configuration of the distributed information security node does not match the expected one!

In general, the moral of this story is simple - do not actively refine the working database, and if you do, then complete all exchange sessions before making the next changes. But what if such a nuisance does happen?

The direct solution is to create new image slave node, but in practice it is usually not applicable. As a rule, the occurrence of a serious error during the exchange is not detected immediately, but some time after operational data from peripheral databases has ceased to arrive. Depending on the communication schedule, a full business day or more may pass between the time the problem occurs and its discovery.

Here it is worth throwing a stone at the developers, who report it as an error and highlight the situation in red in the same way Message number is less than or equal to the number of a previously received message, which is generally quite normal. As a result, users' perception of errors is dulled, and they simply stop reading the displayed messages, believing that everything is fine and that the other party has not yet made the exchange.

But let's return to our mistake. The solution is quite simple and lies on the surface: bring the configuration of the peripheral base to the expected one, i.e. bring it into line with the configuration of the central node. But in practice this is not so easy. If we open the peripheral database in the configurator, we will see that changes are blocked by the RIB management tools.

To change the configuration of a slave node, you will need to temporarily disconnect it from the central database. For these purposes, you can use one of the processing options, which are abundantly available on the network, or disconnect the information security from the central node using the Configurator launch parameter/ResetMasterNode.

Open a command prompt and enter (taking into account the platform version and actual installation path):

"C:\Program Files (x86)\1cv8\8.3.6.2100\bin\1cv8.exe" config /ResetMasterNode

After executing this command, the normal starter window will appear, select there the necessary base and press the button Conifgurator.

Launching information security at the same time will not happen, i.e. it may seem that nothing happened, but by opening the database again in the Configurator, you can make sure that it is disconnected from the main node and is available for making changes.

Attention! On platforms 8.3.7 - 8.3.9, executing this command results in a crash. The bug was fixed in platform 8.3.10.

If you don’t want to mess around with the command line, then you can use one of the treatments; below is the one we use; it was found on the Internet, and we only made cosmetic changes to it. Please note that processing is only suitable for a regular application; for configurations on a managed application, use the Configurator launch key.

Working with it is extremely simple, we launch it in 1C:Enterprise mode, via File - Open, then just press the desired button, in our case Disable master node.

Now we need the latest configuration from the central node. For this we will open central information security in the Configurator and execute Configuration - Save configuration to file. The resulting file with the extension cf will need to be sent to a peripheral node.

Then, in the peripheral node, we launch the information security (having previously disconnected it from the main node) in the Configurator and remove it from support. To do this, choose: Configuration - Support - Support Setup.

In the window that opens, first enable the editing options.

And then we remove the configuration from support.

Now you can load the configuration from a file, to do this, select Configuration - Load configuration from file and indicate not transmitted from the central node cf-file. After which you will receive a warning that the current configuration is not empty. Please note that the manipulations we perform are potentially dangerous and can lead to irreversible damage to the information security, so before continuing, make sure that you have an up-to-date backup copy.

Dynamic update errors (or other platform glitches) can be the cause of distributed infobase exchange errors:

• "Data is received from the node for which configuration changes have been registered"
  

• "The configuration of the distributed information security node does not correspond to the expected"
  

How to restore the exchange?

But let’s start not with restoration, but with the opportunity to carry outexchange “manually”, which is important during the day, because, as always, everything should work “yesterday” :) This can be done with the help of wonderful treatments that I did not remembernude where I downloaded it (authors, please respond - I’ll leave links to your resource, and if necessary, I’ll delete it from mine). Processing makes it possible to download only registered data changes in the database (according to the specified exchange plan for a specific node!) in XML without downloading configuration changes and, if the configuration objects have not changed much, then there is a very high chance of loading this data. These can be downloaded from the link at the end of the article.

As for recovery. There are simpler methods that do not include all the items in the list below, but they do not always help, as was the case in one of my cases. Therefore, I present the method that helped me; it bypasses possible problems in a more comprehensive way. Next step by step.

It is advisable to take these steps when there are no working users in the database. If this is not possible, then you will have to “finish” the method for yourself, and therefore you must first understand its logic.

1. Make backups everywhere.

2. For client-servers: disable the databases via “server administration” and immediately connect them with blocking of scheduled tasks (this will reset the server cache). After this, do not forget to transfer the registration log to the new directory.

3. On all computers used for recovery, delete the database in the list of 1C starter databases and create a new one (the user cache will be cleared)

4. In the configurator (in the central database), add a new constant and save the conf changes.

5. Clear all exchange directories.

6. Make unloads to all branches (only unloads for now).

7. Try to download (only download) the received data to all branches. It is natural to accept the conf changes.

If everything is good everywhere, we move on; if everything is bad, we think that unloading .cf from the central database and LOADING it to the branch (not comparing-merging) might help. In the slave node, you should unlink the database from the RIB (processing will help with this - download from the link below). There is an article on this topic on infostart.ru.

8. We cancel the registration of changes for branches in the Central Bank (after all, we have already received all the changes everywhere). It is important to do at this stage so that the accumulated changes from different branches get to other branches. (download processing for unbinding-binding from the link below).

9. We load into the Central Bank and if all is well, then we load and unload with each branch several times to consolidate the result.

10. That's it.

You can enable the execution of routine tasks for client-server databases.

To prevent problems that cause this error, it is recommended not to do dynamic updates (at least several times in a row - until changes are uploaded to branches), and it is also advisable to check the box “upload data only upon successful upload” in the exchange settings.

Question: Error updating the RIB node

Good afternoon.

I updated the main Rarus-Retail node to 2.2.5.27, made an exchange with a couple of RIB nodes - everything is fine.

I started a massive update of the remaining nodes (similar to the “top couple” (other RIB stores)) - an error pops up in the client part:

Distribution of Reports. Register Data for Updating the List of Routine Tasks"
deferred update handler
"Distribution of Reports. Update the List of Routine Tasks"
An error has occurred:
"(GeneralModule.GeneralPurpose.Module(3502)): Error when calling context method (Contains)
Return Metadata.InformationRegisters.Contains(MetadataObject);
because of:
Type mismatch (parameter number "1")".

Has anyone encountered this? I already tried to update the platform (to the maximum 8.3.10, and tested it on 32-64 computers)... it didn’t help. But the test 2 stores were updated without problems, I can’t understand how.

Answer:() This is how I install the main node. I wrote a little about something else: after you unbind a node by processing, the next time you start it, the update of the conf does not immediately begin, but first 1C opens a window in which it asks you to confirm that the node is being unlinked. After this it is updated - after the update the node is no longer in the list.
In fact, on 2.1, I remember that I updated it using this method, but on 2.2 something didn’t work. Maybe in the park I already poked the wrong sequence in the actions)

ACCORDING TO THE SUBJECT:
I figured out what I have. It turned out that I had overlooked:
"In one of the 2.2 releases, a directory appeared for Distribution of reports with predefined element"Personal data" - a directory with this element was also on 2.1.

The nuance is this: jambs with updating nodes are observed on those databases that were created from the central one precisely on release 2.1.9.18. Everything that was created in earlier releases was updated normally. This probably explains why a couple of TS databases were also updated successfully, and then there were problems.

I didn’t try to invent anything with creating a new element in the directory and setting it as predefined. I transferred this element from a copy of the center to 2.1 via unloading/loading XML and repeated the update on the problematic “base” - everything worked.

() So use the method if you haven’t found the answer yet.

Question: Configuration update error

I am updating the Accounting 2.0.64.14 configuration to 2.0.64.24. platform 8.2.19
An error immediately appears:
Error accessing file... path... temporary file.tmp.
Where to look?

Answer: I solved the problem that time by waiting for a new “stable” release

Question: Error in user rights to BSP

Greetings!!! I am writing a conf based on BSP 2.2, it seems that I already have experience, and have studied the docks far and wide, but when I launch the information security for the first time, an error appears:

(GeneralModule.UsersService.Module(345)): Authorization failed. The system will be shut down.
User: The administrator was not found in the Users directory.

An error occurred when trying to add a user to the directory:
"Error updating the infobase.
The access restriction parameter is not filled in:
"Possible rights for setting object rights."

For the developer: the supporting data may need to be updated,
that affect the operation of the program. To perform the update you can:
- use external processing
"Developer Tools: Updating Support Data",
- or run the program with the parameter command line 1C:Enterprises 8
"/C LaunchInformationBaseUpdate",
- or increase the configuration version number so that the next time you start
The procedures for updating the infobase data have been completed."

Click to expand...

I would like to hear the answers of the “experienced”, for subsequent active dialogue, perhaps even cooperation

Answer:

Vdeg said:

Problem solved?

I have a different problem: I add a user to BSP 2.2.5.29, and he either has full rights (if I manually add them) or none at all (he sees an empty interface without a single reference book or document). Because in typical BSP roles there are no checkboxes at all for accessing specific (my) directories and documents. How then will record level access for a new user be tracked???

Click to expand...

How should the BSP know what kind of directories you have and how you want to configure access to them?
We probably need to do it ourselves

Question: SendingDeliverableNotified Remote node failed verification

Until last Friday the following code worked fine..

XdtoSubscriber = FactoryXDTO.Create(FactoryXDTO.Type(";));
xdtoSubscriber.DeviceID = DeviceID;
xdtoSubscriber.SubscriberType = FactoryXDTO.Create(FactoryXDTO.Type(";), "GCM");
New XDTO Serializer = New XDTO Serializer(XDTO Factory);
Subscriber = NewSerializerXDTO.ReadXDTO(xdtoSubscriber);
Notification=New DeliverableNotification;
Notification.Recipients.Add(Subscriber);
Notification.Text=Text;
Notification.SoundNotification=SoundNotification.Default;
Notice.Sticker=1;
DATAAuz=TOKEN;
SendingDeliverableNotifications.Send(Notification, DataAuz, True);

Now the error: The remote node failed verification. Broke my whole head. I caught requests from the server - it was empty, it felt like it wasn’t contacting anywhere... I tried it on three different machines with different axes. dried up.. help...

Answer: Up

Answer: So, I decided to make a new image of the node. When starting the node, it says that you need to start with \c start updating the information base
and remake the image.

It turns out that this is something due to an update curve.

I tried to launch with this key and make an exchange with an existing node. No updates started on the node, I didn’t ask to restart anything.

And as a result, the message was again not accepted in the main node with the same error.

What can be done?
Can I fictitiously change something in the main node in the conf and make an exchange? Or will it not update the entire configuration, but only what I change? I'll try to make a knot for now. But I'll wait for your ideas

Question: Distributed base- error during exchange is not resolved

Good day everyone!

The situation is as follows.

When loading an exchange from a peripheral node, I receive the message “The configuration of the distributed information security node does not match the expected one.”

Then I follow the instructions.
I unload the configuration from the central database into CF, untie the peripheral database from the central node by processing, remove the configuration in the peripheral database from support, load the configuration from a file.
I bind the central processing node in the peripheral database.
Save, apply.

I download the exchange from the central database again.
I load it into the peripheral. I am unloading the exchange from the peripheral database.
I load it into the central one. Again I receive the message “The configuration of the distributed information security node does not match the expected one.”
But this is some real nonsense - I load the configuration into the central database and no one has changed the configuration in the peripheral database.

How to overcome such an error?

Answer: It never occurred to anyone to advise such obvious things after many years of abuse about the demonic update :)

Question: RIB and updates

Hi all. It is planned to use distributed information security.

configuration changed. The central database configuration is updated by the programmer. These changes will then be transmitted to peripheral databases using exchange files.

The question is: what about launching handlers after updating the database configuration and logging in for the first time in user mode?

updating the main configuration - updating the database configuration - executing update handlers in user mode

For example, many releases were missed, you need to sequentially update to 3 releases. There are no problems with updating the central database, but what about the peripheral ones? It is also necessary to update them in 3 stages (update the central database with the first release, update the RIB, update the central database with the second release, update the RIB, etc.?)

Thanks everyone for your help!

Answer:() point your nose, I can’t find the code that is executed when registering changes to an object.
It seems that if you use the WhenSendingData method, then changed objects will still be accumulated in the main node for sending to the slave node. And these are extra computer resources
Therefore, I want the objects in the main node not to be registered for sending immediately at the moment of their change (On Write, for example). In what place, for example, in the standard Accounting Rev. 3 are these objects registered for filing?

Question: [SOLVED] Error contacting online support

Dear experts, please tell me!
1C:Enterprise 8.3 (8.3.11.2899)
On the 1C server there are several databases of different configurations running, in all of them Internet support is connected and working normally. Incl. loading currency rates, banks, checking counterparties, SPARK, etc.
Proxy settings in all databases are spelled out identically.
But in the BP-3 KORP databases an error always appears:

In the log book:

Failed to obtain an authentication ticket from the service.
Failed to load content(). (GeneralModule.InternetUser SupportClientServer.Module(362)): Error when calling the context method (SubmitForProcessing)
Response = Connection.SendForProcessing(HTTPRequest, ReceivingParameters.ResponseFileName);
because of:
Internet Error: Remote host failed verification

Click to expand...

I tried it on different versions platforms (8.3.10..., 8.3.11...), and on different configuration versions (3.0.54.15, 3.0.57.10).
Testing and fixing doesn't help either.
What can be wrong?
Does BP-CORP really access the Internet in a special way?
Thank you.

Answer:

Answer from 1C (what was highlighted in red helped me):

During the transition, the BSP as part of the power supply unit was updated from 2.4.3 to 2.4.4
In the list of changes BSP 2.4.4
Increased security when establishing a secure connection with HTTPS Internet services. If various problems are detected with the certificate of the Internet service with which a secure connection is being attempted (the certificate is not valid, out of date or not trusted), the connection will not be established.
In 8.3.10, certificates are checked in Windows using operating system." -
Install the latest updates for your OS. They contain important updates to system components that are responsible for working with certificates.
Please also install latest update root certificates distributed by Microsoft in installed packages.
Requires version no lower than IE8.0. It contains important updates to system components that are responsible for working with certificates.
As a rule, after installing all the updates, the problem is solved.
Check that if you enter it in the search bar in Internet Explorer, the link opens.
The user on whose behalf you are working has Internet access.
In case this file database on the client's machine - you should check it on it.
If this client-server base, then on the server from the user under which the 1C server is running.
Check only with IE browser.
Check that ports 443 and 80 are open
If a Proxy server is used, check whether the data is configured in the Personal Settings menu.
If the client-server version is used, then you should configure the server in such a way that the connection to the Internet with the IE browser works correctly under the user on whose behalf the 1C server is running.​

I registered the proxy in the IE settings of the user under which the 1C server was running - everything worked.

Question: Bukh 3 update

Good day
Accounting 3
I updated from 3.0.43.208 to 3.0.43.235
errors
first
(GeneralModule.MessagingInternal.Module(381)): Error when calling context method (ThisNode)

because of:
More than one entry found
second
When calling the update handler:
"MessagingInternal.SetCodeThisEndPoint()"
An error has occurred:
"(GeneralModule.MessagingInternal.Module(381)): Error when calling context method (ThisNode)
ReturnExchangePlans.MessageExchange.ThisNode();
because of:
More than one entry found."

I read that there is a problem with the platform, I tried it on different versions of the platforms
I tried to take a clean conf latest version and just stupidly download a complete replacement
In general, it didn’t help, it was always the same thing. Tell me, has anyone encountered this?

Answer:

I changed the node from true to false above, I thought it didn’t work, and then I went to see it worked