Program configuration errors. Program configuration errors File read error with configuration parameters

It happens that if you need to configure 1C in the startup dialog box, an error - "Error writing configuration file" Let's deal with why such a message is displayed.

On a note: If you are tormented by this kind of problem and do not want to bother - look for files, something to modify in the operating system, boldly write professionals - Smart1c.ru. We will help solve problems and customize accounting system 1C under the class of solved tasks.

So, examples from life:

By the way, if you are interested in the topic of selecting a virtual server, I advise you to contact Rackstore. On servers included the ability to use your own software, i.e. 1C: Enterprise 8 can also be used on a virtual server.

Solving problems with saving the settings 1C 8.2-8.3

As you can see, problems with saving the 1C program settings may be the countless number. All these situations can be solved in the root. And it turns out to be very easy to correct. It is important only to be able to watch hidden files and folders on your computer. To eliminate this error, make the following actions.

Incorrect setting software (access rights, open ports, Interfesa) As a result, a computer system or data can be compromised. The most important step in writing any software is its configuration under certain platforms for correct work with them.

Some individuals or groups of attackers use such inconsistencies for their own purposes.

Regardless of character, any failure leads to weakening the built-in protective mechanisms and makes the car vulnerable to hacker attacks.

Classification of program configuration errors

The most common cause of program configuration errors is the human factor. The system administrator may not know or forget to close access to the computer system, as a result of which anyone who wants to perform any action from his behalf.

Basic errors that can be used criminals for subsequent hacking:

Logic type malfunctions arise in the process of editing configuration parameters, incorrect input of variables for calculations or incomprehension of individual results, which will most likely lead to the appearance of failures in the work or complete program hang.
System errors consist in overflowing memory, incorrect redirection, loss of data or links to non-existent objects.
Violation of the integrity of the structure.
Left by active debug switches for making changes to the ready-made product and corrected bugs detected; Part of the users when installing and reinstalling OS or software automatic inclusion Additional features.
In Windows 10, there are quite often shortcomings in text files containing data on the basic configuration parameters.
Complete absence or outdated anti-virus software signatures.

In all of the above cases, attackers will actively use the problems that have arisen for implementing a malicious code or a hidden launch of various applications.

Object impact

Configuration errors may occur in any application, however, the most vulnerable to hackers are those located in system files Windows installed on software servers, iTunes, software products 1C and other using multi-level engineering calculations and hyperlinks.

The main causes of errors are:

Outdated versions of OS components; You can establish current modifications through the center. windows updates Or download them manually from the official site.
Incompatibility of individual components with elements of the Visual C ++ package, which is included in the basic configuration of many games and other applications. It is decided by removing obsolete versions and installing relevant for this OS, calculated from the official Microsoft website.
Invalid parallel configuration Due to incorrect keys and records in the registry, in the event of the default versions of the library system specified by default recent updates. To correct, it is necessary to bring the corresponding registry entries to the default values, before editing, it is recommended to create a recovery point.
Incompatibility of the discharge of the installed software and OS.

Causes of configuration errors

Basic sources of configuration errors:

allowed by the creators of inaccuracies in the program code, design or implementation made in the process of developing and writing the program;
invalid product installation or non-compliance with developers recommendations (for example, close running applications during installation or disable Internet);
external factors: computer feeds or equipment connected to it, incorrect operation of drivers or other OS components;
overflow hard disk or memory, as a result of which the changes made are not fully saved;
negligence, inexperienced users or deliberate causing harm to the attackers accomplices;
some bugs arise as a result of a combination of previously performed actions that separately do not lead to the appearance of such a kind;
random or intentional external intervention in order to cause a failure and implement a third-party code, launch a virus or a trojan, or establish another malicious software.

Analysis of the risk of configuration errors

From the emergence of such bugs, no one is insured. They may arise due to incorrect actions of users and after failure in the hardware operation. It is worse that emerging problems can be used by attackers to infect a computer.

If the configuration error has appeared during installation or startup, you must perform the following steps:

check compatibility of installed software with operating system and its components; If this is the cause of the conflict, you can try to set another version or replace the program analog;
try to start an application with administrator rights;
to restart a computer; Perhaps a malfunction was one-time and after restarting the system will not happen again;
check the versions of Microsoft Visual C ++ components, if necessary, download them from the official website of the company and reinstall;
check the registry for compliance with the problem-related default settings;
if the above steps did not give the desired result, you can reinstall the application.

To begin with, I bring a list of reductions used by me:

Rib - distributed information base
CB - Central base, Rib root knot
UB - remote base, database of remote node Rib

According to your own experience, I can say that I came across two reasons for an error:

during the reception of the message file in UB "fell" base, in connection with which, apparently, there was a disinxcline of conf. Central Bank and UB;
under MSSQL, the client has downloaded a copy of the working base and did not turn off the regulation in the copy. Autobractions assignments, as a result, part of the messages to remote nodes were formed from the working database, and a part of the copy, which led to the connection to the configuration

There is also the opinion that this error provides the use of a dynamic update mechanism. There are doubts here, because on the one hand, the dynamic update never affects the structure of the database, and the Rib mechanisms are still working precisely with the database structure, and not with its own part, nevertheless, the RIB uses a digital signature mechanism for the configuration version (in I will be called it to reduce Hashe), and when changing the applied part, the hash is naturally obliged to recalculate. I will not deny it nor say, because If I came across this situation, I did not find this evidence.

For correction I use 2 techniques, depending on the situation.

First technique

The first (the most common) is repeatedly mentioned in the affiliate conference, and on other Internet resources associated with 1C. It is used in most cases when despite the message about the configurations, when compared manually, it is issued that they are identical.

Sequencing:

unload the CF file from the Central Bank;
we asslaunt the UB from Rib (the method of installing chain, ready-made processing can be found in the appendix or in other publications);
replace conf. UB on the CF file unloaded in the first step, to do this, use the "Download configuration from the file" menu (and not comparing-association !!!);
relative signs of Rib for UB.

In most cases, these actions are more than enough that restore the exchange, but not always ...

Second technique

It is used if the first technique did not work, and it is not possible to unload the node again.

Prehistory: The client had a cascade rib and the error occurred in the first level of the stage (the second level all this time worked flawlessly). The configuration development was carried out in conjunction with the IT client service and from the moment the error occurs, the CB configuration managed to change several times. An option with a rollback of changes was not considered even in principle, because Loss of data parts and stopping the work of several units were completely unacceptable. The first version of the correction of the error of any tangible results did not give. In this connection, what had to look for other solutions.

A thought has come to try to replace hashi configuration files directly in the XML exchange files. Description of the sharing file structure from the book "Professional development in System 1C: Enterprise 8" gave a weak understanding of the formation of digital configuration signatures and changes in them, but determined the search direction: Digest1 and Digest2 values. Everything else found out a purely empirical way (I mean by the method of samples and errors), but the regularity is to establish the same.

Test experiments were successful. On the working bases, too, everything went well.

So, the sequence of actions:

perform actions 1 - 4 of the first technique;
unload from UB file sharing, but do not load it in the Central Bank;
unload from the Central Bank the exchange file, but do not load it in the UB;
in the exchange file from the Central Bank, we replace a block containing information about configuration changes and hashi (Digest1 and Digest2), on the cache block from the UB file (see example below)
we produce the file download from the 4th point in the UB;
be sure to overwrite the exchange file from the UB (2nd item)! This file should not be downloaded when exchanging in the Central Bank!
for verification, we make several consecutive exchanges.

If the exchange is used to compress data, then either turn off the compression, or first unpack the file, change, then we are reversed back and send.

File sharing unit from the Central Bank

106.0
... Here are the blocks for describing configuration changes ...
1CF680807E97A5DC0D1ED7F901B07392.
038211651CF680807E97A5DC0D1ED7F9.

you need to replace the exchange file from the UB (note the Digest1 from the file from the UB is always equal to "0000000000000000000000000000" !!!)

106.0
00000000000000000000000000000000
11651CF680807E97A5DC0D1ED7F901B0.

The listed actions must be carried out with marginal caution, the incorrect sequence is fraught with the complete inoperability of Rib. Therefore, before these actions, the creation backups Be sure!

For the rest, I can only wish good luck!