Configuration does not support the results
Hello, fellow readers of our blog site! Today we'll talk about
corrected two pardons, which may be lost when exchanging with the distribution of information base (RIB). Such cancellations may fail if you have changed the configuration of your base and want to transfer those changes from the central base to the peripheral base. For example, in the same way as the descriptions. Let's get started!
The following information may appear when you try to exchange for an additional RIB:
“The data are accepted as a unit for which
A configuration change has been registered.
It is necessary to reschedule changes
Change it with the vuzol."
"Configuration of the node of the distributed IB
does not indicate any recovery!”
Let’s take a look at the shortcuts that will help correct the situation. Before that, let’s build our information databases!!!
- Let's take the updated configuration file, open the central database in the Configurator and save it (Configuration-Update configuration from file...). Protected by IB (F7).
- Let's go to and create a file for the peripheral database:
- You can see the exchange plan in the list, then right-click the context menu and select the “Record changes...” item.
- Now let's move on to peripheral IX. We open them in exclusive mode, so that there is no user, and we also close the Configurator. Now it is necessary to remember the code, which is the main one for the flow base. Open Operations - Exchange plans - Select your exchange plan (for example, "Behind the warehouse"). The list of exchange plans of the head node has an element with the same icon. This information will be available to us at this point. We open the process and press the button “Select the assignment of the head node.”
- Now we open the peripheral IB in the configurator and save the same configuration file that we added in the first step in the central database (Configuration-Save configuration from file...). Protected by IB (F7).
- The support settings can be changed (Configuration-Support-Support settings...). In the dialogue, you can see in the table a mark on the crossbar of the first row and the other column. Then, under pressure, the dialogue “Adjusting the rules of support” is called. In this case, put the checkbox “Install for light objects” and press the “OK” button. Close the support settings dialog by clicking the “Close” button. Save IB (F7). Close the configurator.
- Now I will open the peripheral IB again in the exclusive mode of 1C:Enterprise, so that there are no other users, and I will also close the Configurator. Let's open the process of Installing the Head Node.epf and select the exchange plan that we want to install as the head node (at the fourth point we have forgotten this node). Then press the “Install head vuzol” button. After this, the flow of IB will again become peripheral.
- Now the current IB (peripheral) has an open exchange plan and an important file with the exchange from the Central Base, which we took on the third step:
- Operations - Exchange plans - Select our exchange plan (for example, "Behind the warehouse").
- If everything went well, then we will significantly improve the exchange for the Central database at the current IB (peripheral):
- Operations - Exchange plans - Select our exchange plan (for example, "Behind the warehouse").
- You can see the exchange plan in the list, then use the Right button to click on the context menu and select the item “Record changes...”.
- In the dialogue, you can send the same name to the exchange file. Click the "OK" button.
- Now let’s try to import this file from the Central Database, which can be opened in 1C:Enterprise mode:
- Operations - Exchange plans - Select our exchange plan (for example, "Behind the warehouse").
- Apparently the exchange plan is in the list - Right-click the context menu and select the item “Read changes...”
- In the dialog, select the exchange file. Click the "OK" button.
To avoid problems with working copies, get started
For starters, the list is very quick, so it’s worth a wiki:
- RIB – distributed information base
- Central Bank - central base, root university RIB
- UB - remote base, DB of a remote RIB node
I can say with full confidence that there are two reasons for the guilt of the amends:
- By the time the notification file was received, the database “lost” in the UB, with a connection with which, perhaps, there was a desynchronization between the conf. CPU and UB;
- Under MSSQL, the client imported a copy of the working database and did not remove the registry from the copy. Auto-exchange was specified, as a result, part of the information about the remote node was formed from the working database, and part of it was formed from a copy, which led to desynchronization of the configuration
There is also an idea that before this end the mechanism of dynamic updating of the database should be put in place. There are doubts here, because on the one hand, dynamic updating does not affect the database structure at all, and the RIB mechanisms still work with the database structure itself, and not with the applied part; instead, the mechanism for forming a digital signature is used in RIB. in the version of the configuration (in Nadalia it is called for short hash), and when the application part is changed, the hash is naturally liable to change. I don’t feel anything about it, nor do I harden it, because... As a result of this situation, there is no clear evidence of this.
There are 2 methods for correcting vicorism, depending on the situation.
PERCHA METHOD
The first one (the broadest one) can be seen more than once both in the partner conference and on other Internet resources associated with 1C. It’s a big deal if, when informed about the different changes, when manually adjusted, it becomes clear that they are identical.
Sequence of actions:
- vivantage from the CPU cf-file;
- This is due to UB from RIB (Install HeadVuzol method, the finished processing can be found in the appendix and other publications);
- replacing conf. UB for visualization in the first place a cf-file, for which the correct menu is “Add configuration to file” (and not update-ob'ednannya!!!);
- We update the RIB sign for UX.
In most episodes of these activities there is less enough to renew the exchange, otherwise not forever...
ANOTHER METHODOLOGY
One is confused because the first method did not work, and it is impossible to revive the university again.
Background: the client was adjusting the cascade RIB and the winkle was turned off at the first level of the cascade (the other level was working without a clue for the entire hour). The configuration development was carried out simultaneously with the client’s IT service and since the release, the configuration of the central bank has changed several times. The option with the final change was considered in principle, because the loss of some of the data and the lack of work for so many children was absolutely unpleasant. The first option for correcting the grinding did not produce any significant results. In connection with this, we had a chance to joke about other routes.
I came up with the idea of trying to replace the hash of configuration files directly in the XML exchange files. The description of the structure of the exchange file from the book “Professional development in the 1C:Enterprise 8 system” gave a weak statement about the formation of digital signatures, configurations and changes in them, but it directly meant a search: the values of Digest1 and Digest2. Reshta followed a purely empirical path (by trial and error), but a pattern emerged.
The test experiments were carried out in the distance. At the work bases everything went well.
So, the sequence of actions:
- Concludes 1 – 4 first methods;
- We obtain the file exchange from the UB, and we also obtain them from the Central Bank;
- We import the file exchange from the CPU, and also from the UB;
- in the CB exchange file, we replace the block that contains information about configuration changes and hash (Digest1 and Digest2) with the hash block in the UB file (example div. below)
- We are very interested in the file from the 4th paragraph in the UB;
- Obviously rewrite the file exchange with UB (2nd point)! This file is not guilty of any interference during the exchange in the CPU!
- To check the number of recent exchanges, we need to check.
As soon as the data is exchanged, the data is compressed, or the compression is turned on, or the file is first unpacked, modified, then packed back and sent.
Block file exchange from the Central Bank
...here are blocks describing configuration changes...
you need to replace the exchange file from UB with a block (return to Digest1 from the file from UB the old "0000000000000000000000000000000000"!!!)
The listing of actions must be done with extreme caution; incorrect consistency threatens the further failure of the RIB. Therefore, before these actions, the creation of backup copies OBOV'YAZKOVO!
- The file from the notifications has already been downloaded to the receiving base. It is necessary to revive him from the base-dzherel again.
Repair “Performance when copying a file from an FTP resource... Repair for robots using the Internet: Timeout was reached”
- The site through which the exchange is carried out does not allow you to copy the required file. This may be due to the excessive work of your Internet or problems with the site itself.
- It is necessary to repeat the exchange after 15-30 minutes.
Pomilka “Redaguvannya data from this period is blocked. Changes cannot be recorded..."
- Entries are required to remove documents from a closed period.
- It is necessary to carry out an exchange with correspondents who have the right to change documents during this period.
Pomilka “It is necessary to update the database configuration. Updates can be made in the configurator mode"
Reason: The programs changed the configuration at the center. Resolution: Update the changed configuration on the peripheral base. For whom:- Go to the configurator.
- Vikonati menu item "Configurator / Update database configuration".
- Once you have asked for inputs such as “Repeat”, “Save”, “Update dynamically”, click the “Update dynamically” button.
- There seems to be a supply with inputs such as “Repeat” and “Skashuvati”.
- All clients must log out of 1C.
- Click the "Repeat" button.
- When asked, the response is firm: “Yes,” “Accept,” “OK.”
- Close the configurator.
- Repeat the attraction from the center.
Message “Configuration does not support recovery”, “Trying to change against unknown configuration”
- Pardon at the database.
- It is necessary to turn to specialists.
For starters, I’ll make a quick list that you can use for my help:
- RIB – distributed information base
- Central Bank - central base, root university RIB
- UB - remote base, DB of a remote RIB node
I can say with full confidence that there are two reasons for the guilt of the amends:
- By the time the notification file was received, the database “lost” in the UB, with a connection with which, perhaps, there was a desynchronization between the conf. CPU and UB;
- Under MSSQL, the client imported a copy of the working database and did not remove the registry from the copy. Auto-exchange was specified, as a result, part of the information about the remote node was formed from the working database, and part of it was formed from a copy, which led to desynchronization of the configuration
There is also an idea that before this end the mechanism of dynamic updating of the database should be put in place. There are doubts here, because on the one hand, dynamic updating does not affect the database structure at all, and the RIB mechanisms still work with the database structure itself, and not with the applied part; instead, the mechanism for forming a digital signature is used in RIB. in the version of the configuration (in Nadalia it is called for short hash), and when the application part is changed, the hash is naturally liable to change. I don’t feel anything about it, nor do I harden it, because... As a result of this situation, there is no clear evidence of this.
There are 2 methods for correcting vicorism, depending on the situation.
PERCHA METHOD
The first one (the broadest one) can be seen more than once both in the partner conference and on other Internet resources associated with 1C. It’s a big deal if, when informed about the different changes, when manually adjusted, it becomes clear that they are identical.
Sequence of actions:
- vivantage from the CPU cf-file;
- This is due to UB from RIB (Install HeadVuzol method, the finished processing can be found in the appendix and other publications);
- replacing conf. UB for visualization in the first place a cf-file, for which the correct menu is “Add configuration to file” (and not update-ob'ednannya!!!);
- We update the RIB sign for UX.
In most episodes of these activities there is less enough to renew the exchange, otherwise not forever...
ANOTHER METHODOLOGY
One is confused because the first method did not work, and it is impossible to revive the university again.
Background: the client was adjusting the cascade RIB and the winkle was turned off at the first level of the cascade (the other level was working without a clue for the entire hour). The configuration development was carried out simultaneously with the client’s IT service and since the release, the configuration of the central bank has changed several times. The option with the final change was considered in principle, because the loss of some of the data and the lack of work for so many children was absolutely unpleasant. The first option for correcting the grinding did not produce any significant results. In connection with this, we had a chance to joke about other routes.
I came up with the idea of trying to replace the hash of configuration files directly in the XML exchange files. The description of the structure of the exchange file from the book “Professional development in the 1C:Enterprise 8 system” gave a weak statement about the formation of digital signatures, configurations and changes in them, but it directly meant a search: the values of Digest1 and Digest2. Reshta followed a purely empirical path (by trial and error), but a pattern emerged.
The test experiments were carried out in the distance. At the work bases everything went well.
So, the sequence of actions:
- Concludes 1 – 4 first methods;
- We obtain the file exchange from the UB, and we also obtain them from the Central Bank;
- We import the file exchange from the CPU, and also from the UB;
- in the CB exchange file, we replace the block that contains information about configuration changes and hash (Digest1 and Digest2) with the hash block in the UB file (example div. below)
- We are very interested in the file from the 4th paragraph in the UB;
- Obviously rewrite the file exchange with UB (2nd point)! This file is not guilty of any interference during the exchange in the CPU!
- To check the number of recent exchanges, we need to check.
As soon as the data is exchanged, the data is compressed, or the compression is turned on, or the file is first unpacked, modified, then packed back and sent.
Block file exchange from the Central Bank
...here are blocks describing configuration changes...
you need to replace the exchange file from UB with a block (return to Digest1 from the file from UB the old "0000000000000000000000000000000000"!!!)
The listing of actions must be done with extreme caution; incorrect consistency threatens the further failure of the RIB. Therefore, before these actions, the creation of backup copies OBOV'YAZKOVO!
Otherwise, I might have more luck!
A shared information base (RIB) is often used to organize the work of branches and subdivisions, allowing for the rapid exchange of information, preserving the necessary level of autonomy. Regardless of the fact that this technology is reliable, sometimes it breaks down. Today we will take a look at one of the reasons for broader pardons: Let’s talk about the causes of this guilt and methods of combating it.
Let’s start, right now. After you have created the RIB, all changes to the configuration of the information base can be made only in the head node. Then, upon the start of an exchange, all changes will be transferred to the ordered nodes and automatically stored there. The ale fell smoothly on the paper.
In practice, each node is routed in such a way that between exchange sessions, if the channel is bad on the periphery, the configuration of the head node is forced to change twice. For example, they made changes, vivanted them, the peripheral base rejected the changes, but have not yet settled them, which can take many hours, and has not yet sent confirmation. If you make changes in this period once again and re-visit the exchange, then you will see that the center will update the peripheral node with configuration No. 1 and try to update it to configuration No. 3, and after that go there with configuration No. 2. Sometimes this situation is blamed for the dynamic renewal of the central base. As a result, exchanges will become impossible, and you will be denied information about those who The configuration of the node of the distributed IB appears to be correct!
The moral of this story is simple - do not actively update the work base, but if you do, end all exchange sessions before making any changes. Ale yak buti, why did such a problem arise after all?
The solution is “head-on” - to create a new image of a light knot, but in practice it will not stagnate. As a rule, the occurrence of a serious error during an exchange is not detected immediately, but within an hour after operational data from peripheral databases ceases to be received. It is important to keep an eye on the problem between the moment the problem arises and it may take a whole business day, or even longer, for it to be identified.
Here they will throw a stone at the city of rozrobniki, which seems to be a mercy and thus highlights the situation. The notification number is lower or older than the number previously received., as a matter of fact, is completely normal. As a result, the recipients’ taste for mercy becomes dulled, and they simply stop reading the notices that appear, respectfully, that everything is good and it’s just that the other side has not yet completed the exchange with itself.
Let's turn back to our mercy. The solution is simple and lies on the surface: bring the configuration of the peripheral base to the correct level. Bring them in line with the configuration of the central node. But in practice, earning money is not so easy. If we open the peripheral database of the configurator, then it is important that the changes are blocked by the RIB management methods.
To change the configuration of a subnode, you need to immediately connect it to the central base. For this purpose, you can quickly access one of the processes that are sufficiently presented in the network, or connect IB to the central node for additional parameters to launch the Configurator/ResetMasterNode.
Open the command line and enter (depending on the version of the platform and the actual installation):
"C:\Program Files (x86)\1cv8\8.3.6.2100\bin\1cv8.exe" config /ResetMasterNodeAfter completing this command, the initial starter window will appear, select the required database and press the button Configurator.
Launching IB at any time it won't happen, then. You can leave that nothing has happened, but by opening the database in the configurator again, you can re-convert to see that it is connected to the head node and is available for making changes.
Respect! On platforms 8.3.7 – 8.3.9, these commands will cause the robot to crash. The issue was corrected on platform 8.3.10.
If you don’t want to bother with the command row, then you can quickly use one of the samples, below is the one that we vikorista, it was found in the open spaces of the border, and we made only cosmetic corrections to it. Please note that the procedure is only suitable for standard programs; for configuration on hard-wired programs, use the key to start the Configurator.
Working with it is extremely simple, we launch it in 1C:Enterprise mode, via File - Open then we simply press the required button in our selection Vimknuti golovniy vuzol.
Now we will need an up-to-date configuration from the central node. For whom is it open? central IB in the Configurator and select it Configuration - Save configuration to file. Removing a file from extensions cf need to be transferred to a peripheral university.
Then IB is launched at the peripheral node (having previously been connected to the head node) in the configurator and is removed from support. For whom choose: Configuration - Support - Adjusting support.
At the very beginning, the possibility of change is included.
And then we remove the configuration from support.
Now you can import the configuration from the file for which you select Configuration - Enter configuration from file and indicate no transmissions from the central node cf-File. After which you take away the advances about those that the flow configuration is not empty. We appreciate that the manipulations we are doing are potentially unsafe and can lead to irrevocable damage to the IB, so before proceeding, make sure you have an up-to-date backup copy.