The most common errors "1C" and methods for their correction. The most frequent errors "1C" and methods of their correction. Malfunction of 1C
Everyone knows that any software can give from time to time various failures or, simply put, not work properly. Such failures that lead to disruption of the correct functioning of the system are called in mistakes... 1c program is software product(software), respectively, this program may also contain various errors that lead to incorrect operation of the system. can be very diverse, and if you do not have a number of special knowledge in the field of programming and the specifics of the operation of the internal mechanisms of 1c, then you will not be able to correctly understand and diagnose the error, and even more so fix it. Any our 1c programmer is always ready to help you in solving any issues related to errors 1c!
What causes errors in the 1c database?
Now let's talk a little about why, after all, various errors in the 1c database when working with the program. In fact, there can be a lot of reasons, and all of them can have completely different grounds. And yet, we will try to understand in general terms the reason for the occurrence of various errors in 1s.
Types of errors in the 1c database
Errors in 1s there can be a great many and they can occur for a variety of reasons. In this article, we will not consider all possible 1c errors, we will try to highlight the so-called main "types" of errors encountered. We conventionally call them "types" because the content of the error that the program shows you is usually always different, but the essence is often the same. So let's highlight the most common errors in the 1c database:
- Stream format error
- Object field not detected
- Object method not found
- Not enough memory
- Errors related to SQL tables (relevant for 1c servers that run on relational databases, such as MySQL)
- Access error 1s
Stream format error in 1s
stream format error 1c
Object field not detected
Object field not detected
Index is out of bounds of array
Error 1s
Stream format error in 1s
This error is very often manifested when the erroneous reading of a sequence of commands from the bytecode in the stream, which is why it is called stream format error 1c... Any transaction will be aborted if this error occurs as a result of its execution. Such errors require immediate correction, since they can harm the operation of the 1C Enterprise system. These errors can only be corrected by qualified 1c programmers.
Object field not detected
If the 1c system gives you an error message with the text " Object field not detected", it means that the error occurs in a situation when the program tries to access an attribute (field) of an object of which simply does not exist. This error is in the nature of a" runtime error "if it occurs in 1C Enterprise. Errors of this kind can also be corrected only programmers.
Index is out of bounds of array
An array in programming is a certain memory area in which many objects of the same type are stored (in 1c such types can be, for example, ReferenceLink, DocumentObject, etc., as well as any primitive types such as number, string, boolean, etc.). Error 1s associated with going out of bounds of an array just happens when the program accesses the bounds of memory that is allocated for the array. Accordingly, in this case, the program generates an error, notifies the user (programmer) that the array is being accessed, and this, in turn, is a program error.
Object method not found
A similar error occurs when the system tries to access a method (function) of an object whose description (which) does not exist in the code. Errors of this type can be corrected by programmers.
Not enough memory in 1s
This error occurs if the system runs out of all RAM allocated for the needs of executing programs in the operating system, so the program generates an error. " Not enough memory in 1s". It can occur during various events such as updating a configuration, processing a large file, when generating a report, loading a large database, etc. The user can try to fix such an error himself.
Possible correction of error 1s "Not enough memory"
The error lies in the limited allocation of address memory by the operating system for software (software).
The default limits for addressable memory are:
- for a 32 bit system - 2GB
- for 64 bit - 4 GB
In order to increase the size of the address memory, you need to do the following:
- Run the command line: "Start - Run" - type CMD and press enter
- Now on the command line, enter the text without quotation marks “bcdedit / set increaseuserva 3072 ″, where 3072 is the size of the desired address memory
- Reboot your operating system (computer)
- Try to perform the action in 1C that did not work before and led to an error.
- If everything worked out and the operation is repeated not so often, it is recommended to return the size of the address memory to the default value using the command “bcdedit / deletevalue increaseuserva”
Errors related to SQL tables
Errors of this kind usually occur on the server side, at the moment when the system accesses the table and cannot read the data. This error can occur due to incorrect server configuration, as well as due to damaged SQL tables. In special difficult situations, it may not even be possible to restore the database, and then you can only be saved by an archive copy of the database. We strongly recommend making timely backup copies of the database.
Access error in 1s
This error occurs when the user tries to perform any action that is prohibited by access rights (roles). That is why the system issues an access error in 1s. Roles are configured in the configurator by the programmer.
Couldn't fix the error in 1c?
If you failed to fix any error in 1c, do not despair, pick up the phone and call us! Our experts are always ready to help you in solving any issues related to 1c, including errors that occur during the operation of the system.
Sandbox
authority September 18, 2013 at 03:24 PM1C, restoring the infobase configuration using MS SQL
At one time I ran into a problem: when updating the configuration from the repository, a failure occurred and 1C was closed.
As it turned out later, the configuration repository was destroyed, and when the configuration was updated, the database configuration also flew from the repository. A similar error occurred before with a dynamic information security update.
Because This problem has arisen more than once. I decided to share a treatment option.
At the next launch of the configurator, an error occurred: “Attention !!! An error occurred while refreshing the data since the last restructuring. Do you want to retry the update? " if the answer is yes, we get the message: “An incomplete configuration save operation was detected. To continue working, you must complete the operation "after which the application is closed.
When analyzing this problem, several options were found to solve the problem, each solution works in different cases.
Option 1 (if you have a SQL backup with a copy with an identical configuration):
A copy of the information security is deployed, and the following query is executed:
USE GO DELETE FROM .. GO INSERT INTO .. SELECT * FROM .. GO
In this case, the table in which the IB configuration is stored is refilled. It is advisable to test and correct the information security after this operation.
Option 2 (in the absence of backup):
This option was treated like the last straw. Because the configuration was under development and the backup was forgotten a bit, relying on the repository.
In the database, two records are deleted from the "Config" table by the value in the "FileName" column - dbStruFinal and commit
The following query is executed:
USE GO DELETE FROM. WHERE FileName = "dbStruFinal" GO DELETE FROM. WHERE FileName = "commit" GO
Oddly enough, the base comes to life.
Tags: 1c enterprise 8.2, SQL, configuration restore
This article is not subject to comment, since its author is not yet a full member of the community. You will be able to contact the author only after he receives
The article shows ways to restore the 1C database using the tools built into the program or third-party applications... How to create and restore a database backup. For most users of 1C products, damage or loss of the 1C: Enterprise database is something they are even afraid to talk about. For them, the task of restoring the database seems simply unrealistic, and its loss is a terrible tragedy.
In fact, the products of the 1C company are the same software as any other. The information that users enter into their databases is saved in files that can be backed up or restored in case of damage or deletion. Often, the built-in "1C: Enterprise" tools, but also about third-party software also do not forget.
By default, the directory of the infobase, in which, in addition to the file of the 1C database itself, all files related to it are saved, is the folder in User Documents:
C: \ Users \ Username \ Documents \ InfoBase
![](https://i0.wp.com/hetmanrecovery.com/ru/pic/blog/a64/infobase.png)
This folder contains all files related to this database.
![](https://i1.wp.com/hetmanrecovery.com/ru/pic/blog/a64/infobase-2.png)
These files include:
- * .1CD- the file of the database itself, which by default has the name 1Cv8.1CD. This file includes all data entered into the database, as well as their configuration;
- * .cf, * .cfu (* .cfl), * .dt, * .epf (* .erf)- configuration files of the database;
- * .log, * .lgf, * .lgp, * .elf- log files;
- * .cdn- 1C database lock file;
- * .efd- archive file 1C;
- * .mft- auxiliary template configuration file;
- * .st- text templates file
- * .mxl- file of printed forms of the 1C database;
- * .grs- a file of graphic schemes of the 1C database;
- * .geo- file of geographic schemes of the 1C database.
Signs and causes of damage to the 1C base
Signs of damage to the 1C database can be very diverse, these are failures when working with the database or its sudden closure, freezing, various messages about the presence of errors while working with it or at startup. Often "1C: Enterprise" reporting an error while performing an operation with an infobase and describes it "... The database file is damaged".
The reasons for damage to the 1C database can be physical or logical.
The consequences of physical causes of damage to databases are the most severe, since they are associated with damage to the storage medium on which the data is stored. This can be damage to an external or built-in hard drive, optical storage medium, flash drive or memory card. In this case, in order to be able to restore the 1C base, it is necessary to return the media to work.
Logical damage to databases occurs as a result of software malfunctions, incorrect or sudden shutdown of a computer or storage medium, malfunctioning of network equipment, as well as viruses and malware.
![](https://i0.wp.com/hetmanrecovery.com/ru/pic/blog/a64/file-is-damaged.png)
Creating and restoring from a backup copy of the 1C database
We have already mentioned this many times in our articles - the best way to save your data is to create a backup copy of it. For 1C base this way also relevant.
To create a backup copy of the 1C database:
To restore a 1C database from a backup:
![](https://i2.wp.com/hetmanrecovery.com/ru/pic/blog/a64/download-data-base.png)
Recovery of a damaged 1C infobase
In the event of a malfunction in the operation of the infobase and the occurrence of the errors described above or other symptoms, you should not panic, since in most cases the 1C database is recoverable. This can be done using the tools built into the platform.
Recovery using the Configurator
To eliminate errors in the 1C base, its configurator provides the function "Testing and fixing ..."... To use it:
![](https://i2.wp.com/hetmanrecovery.com/ru/pic/blog/a64/testing-and-correction.png)
Recovering with chdbfl.exe
In each version of the platform "1C: Enterprise" there is a utility for debugging damaged infobases. There is no access to this utility from the platform's internal menu. But it is installed along with the installation of the platform. To run it, go to the folder where the 1C platform is installed on your computer:
C: \ Program Files (x86) \ 1cv8 \ 8.3.8.1652 \ bin
(where, 8.3.8.1652 is the platform release number (different for different releases))
![](https://i1.wp.com/hetmanrecovery.com/ru/pic/blog/a64/8.3.8.1652.png)
Find and run the chdbfl.exe file in this folder - this is the 1C infobase debugging utility. After starting the utility, use it to specify the database file by clicking the ellipsis to the right of the field "Database file name", and check the box next to the function "Fix found errors"... By asking required parameters- press the button "Run".
![](https://i0.wp.com/hetmanrecovery.com/ru/pic/blog/a64/run.png)
All detected errors and other actions of the utility will be displayed in the chdbfl.exe window.
Recovery using the HEX editor
In especially difficult cases, or if the previous two methods of debugging the infobase did not bring the desired result, theoretically it is possible to restore it using a HEX editor. To do this, open the main database file * .1CD in the HEX editor.
The disadvantage of this method is that this method of fixing a damaged 1C database can only be carried out by experienced and knowledgeable HEX specialists.
It should be noted that it has a built-in HEX editor that can be used to fix damaged files.
![](https://i0.wp.com/hetmanrecovery.com/ru/pic/blog/a64/hex-editor.png)
How to restore a deleted 1C information base
If, as a result of accidental deletion, reinstallation of the operating system, formatting of the hard disk or other media on which the 1C database was stored, it was lost, then you can restore it with the help of. For this:
![](https://i0.wp.com/hetmanrecovery.com/ru/pic/blog/a64/hetman-partition-recovery.png)
Note... Similarly, you can restore a lost 1C infobase backup file - 1Cv8.dt.
- Load the recovered * .dt file into the infobase as described above.
- If the infobase has been restored file by file, then open its main file 1Cv8.1CL using the 1C menu File / Open.
All the methods for recovering the 1C database described in this article are shown on the example of the platform "1C: Enterprise 8.3"... But this information is also relevant for other programs and platform configurations:
- 1c accounting
- 1C: Entrepreneur
- 1C: Salary and personnel management
- 1C: Trade Management
- 1C: Retail
- 1C: Holding Management
- 1C: Enterprise Management
- 1C: Enterprise. Control manufacturing enterprise
- 1C: Complex automation
- 1C: Document flow
- 1C: Consolidation
- 1C: Management small firm
- 1C: Taxpayer
- 1C: Entrepreneur reporting
- 1C: Payment documents
- 1c accounting state institution
- 1C: Salary and personnel budgetary institution
- 1C: Summary of reports
- 1C: Budget reporting
- 1C: Document flow of a state institution
- 1C: State and municipal purchases
- 1C: Settlement budget
- 1C: Budget municipality
- 1C: Money
- 1C: E-learning, etc.
1C software products are designed to optimize the activities of an enterprise, and failures in their work impede the normal flow of business processes in the organization. In the worst case, malfunctions in the program can cause a complete shutdown of the activities of individual structures of the company: accounting, finance, HR, production, and many others. Even if the failure is short-lived, it can temporarily restrict access to important documents. In this regard, the efficiency of resolving the problem comes to the fore. An employee trained to work with 1C products can deal with some problems on his own. Others require qualified assistance from a specialist from a service center. Let's analyze the main reasons for failures in 1C and how to restore it.
The flow chart for detecting problems should look like this:
- Determination of the error and its cause. Efficiency of actions at this stage will help to avoid wasting time in the future. Sometimes the haphazard actions of employees, whose program has ceased to function, only aggravate the problem, but do not solve it.
- Crash replay. Modeling the error is necessary to draw up a competent strategy to correct it.
- Bug fix. When testing has shown that the interpretation of the error was carried out correctly, a 1C specialist who is responsible for solving problems with 1C can start work. For example, if you use the 1C: Enterprise program, support for this solution will be provided by the employees of the service center with which you entered into an agreement.
Errors in 1C operation can be classified as follows:
1. User errors. These errors are caused by incorrect actions of the employee and are often the result of insufficient knowledge of the specifics of the 1C program. The most common errors of this type are incorrect creation of a document, incorrect use of program functionality, accidental blocking of 1C, etc. To prevent the occurrence of such a problem in the future, it is recommended to conduct training for all employees who have access to 1C. This can be either corporate training with specialists from licensed support centers, or self-training using thematic literature.
2. Software errors. The most common crashes in this category are:
- Errors when starting the program can be caused by the absence of a protection key, failures in the local network, or a violation of the configuration structure.
- Installation errors are most often the result of an incorrectly entered key.
- Update errors are the most common software errors caused by late update of program components.
To solve software errors, you need to use the services of a specialist in working with 1C products.
3. Technical errors. These errors are usually associated with faulty or problematic hardware. For example, the slow operation of a program may be caused by insufficient server capacity. To fix this problem, you need to consult with IT professionals and follow their recommendations.
The organization has the right to decide on its own whether or not to report the loss of credentials to the Federal Tax Service Inspectorate. This situation is not regulated in any way current legislation, therefore, the consequences and steps of the organization in the situation under consideration can be as follows.
So, there is a technical error as a result of a software failure (1C), as a result of which the taxpayer may have an inaccurate reflection business transactions, since the organization, being a VAT payer (on OSNO), applies VAT rates of 0, 10 and 18 percent in the sale of prosthetic and orthopedic products.
The organization in this case will not be able to appeal to the norms of paragraph 3 of Art. 401 of the Civil Code of the Russian Federation, since the failure in the software is not of an emergency and unavoidable nature (that is, due measures were not taken in a timely manner to ensure the safety of information, its timely archiving, etc.).
Taxpayers are obliged to ensure the safety of data for 4 years accounting and documents required for the calculation and payment of taxes (subparagraph 8 of paragraph 1 of article 23 of the Tax Code of the Russian Federation). In addition, accounting and storage of accounting documents are organized by the head of the economic entity (clause 1 of Art. 7 Federal law dated 06.12.2011 No. 402-FZ "On accounting", hereinafter - Law No. 402-FZ). Primary accounting documents, accounting registers, accounting (financial) statements are subject to storage for the period established in accordance with the rules for organizing state archiving, but not less than 5 years after the reporting year (part 1 of article 29 of Law No. 402-FZ). By virtue of Part 3 of Art. 29 of the Tax Code of the Russian Federation, an economic entity must ensure safe storage conditions for accounting documents and their protection from changes.
The tax authorities have the right to demand, in accordance with the legislation on taxes and fees, from the taxpayer documents that serve as the basis for calculating and paying (withholding and transferring) taxes, as well as documents confirming the correctness of calculation and timeliness of payment (withholding and transferring) taxes (clauses 1 p. . 1 article 31 of the Tax Code of the Russian Federation). In the letters of the Ministry of Finance of the Russian Federation dated July 22, 2013 No. 03-02-07 / 2/28610, dated June 07, 2013 No. 03-02-07 / 1/21191, it is explained that documents can be requested by tax authorities, including in cases of taxpayer re-visiting tax audit(Article 89 of the Tax Code of the Russian Federation) and other events tax control, including if it is necessary to obtain documents (information) related to the activities of the audited taxpayer, and information on a specific transaction (Article 93.1 of the Tax Code of the Russian Federation).
In order to ensure the execution of paragraphs. 8 p. 1 of Art. 23 of the Tax Code of the Russian Federation and submissions in accordance with the established procedure in tax authority documents specified in paragraphs. 8 p. 1 of Art. 23 of the Tax Code of the Russian Federation, the relevant documents lost by the taxpayer must be restored. Failure to submit to set time by a taxpayer to the tax authority of documents and (or) other information necessary for the implementation of tax control, entails liability established by Art. 126 of the Tax Code of the Russian Federation.
The absence of a person's fault in committing a tax offense is one of the circumstances that exclude the person being held accountable for committing a tax offense (clause 2, article 109 of the Tax Code of the Russian Federation). Circumstances precluding the taxpayer's guilt in committing a tax offense are given in Art. 111 of the Tax Code of the Russian Federation. One of these circumstances is the commission of an act containing signs of a tax offense due to a natural disaster or other extraordinary and insurmountable circumstances (these circumstances are established by the presence of well-known facts, publications in the media and by other means that do not need special means of proof).
For gross violation of accounting rules, which includes the absence primary documents, which did not entail underestimation tax base, sanctions are envisaged for both the Tax Code of the Russian Federation (paragraphs 1-3 of Article 120 of the Tax Code of the Russian Federation) and the Code of Administrative Offenses of the Russian Federation (Article 15.11 of the Code of Administrative Offenses of the Russian Federation).
Based on the prevailing judicial practice(see Resolution of the FAS PO dated 24.03.2011 No. A06-3321 / 2010, Resolution of the FAS VVO dated 05.04.2011 No. A43-10932 / 2010, Resolution of the FAS MO dated 23.09.2008 No. KA-A40 / 8513-08-2; Appeal determination of the Krasnodar Regional Court dated 16.08.2012 No. 33-15393 / 2012), it can be concluded that the organization in the situation under consideration can secure itself as follows:
- inform the Inspectorate of the Federal Tax Service about the event (loss of documents) (optional, since a strictly regulated obligation is not legally enshrined);
- if the organization decides to notify the Federal Tax Service Inspectorate of this fact, then to the letter (in any form) it must attach copies of documents (act, agreement) of a specialized organization with a conclusion that it is impossible to restore the server (computer) on which the accounting program was installed;
- since the organization is a VAT payer and applies rates of 0, 10 and 18 percent when selling goods, and due to the impossibility of confirming rates of 0 and 10 percent, it will need to calculate VAT at a maximum rate of 18 percent. In the future, you can submit an updated VAT return when the data confirming tax rates... The organization will avoid recalculating taxes if it can recover lost accounting and tax documents;
- conduct an IT audit in order to identify weaknesses in order to minimize the risks of losing information; the accounting department and the IT department jointly develop and establish strict regulations for the preservation of credentials;
- in the event of such situations, as soon as possible, by order of the manager, carry out an unscheduled urgent inventory of the remains of goods in stores, which will help to quickly restore credentials if they are lost; and the head needs to form by his order in such cases a commission in order to find out the reasons for what happened and identify the perpetrators (the results of the commission's work are formalized in an act or protocol);
- in case of presentation of claims by the regulatory authorities, the organization can apply to defend its interests in court.
Note that the presence of intent or negligence in the actions of the organization in the situation under consideration must be proved by the tax authorities.