1c accounting errors. The most common 1C errors and methods for correcting them. Errors were found in the sales document for last year, one of which led to an overpayment of income tax, and the other to an underpayment, and the amount of the overpayment was greater than the underpayment. Ka

Many different errors can occur in information databases on the 1C platform:

violation of the logical/physical integrity of the database, user errors, “crooked” developer code and much more.

There can be many reasons: the power was turned off and there was no source uninterruptible power supply, or Friday evening was a success, and the user can no longer remember on Monday what he did.

First, it’s worth asking a few clarifying questions to the user:

1) Platform/configuration releases.

2) Full text of the error message. Users have the unfortunate tendency to not read such messages in their entirety, and perhaps they contain recommendations for troubleshooting.

3) How long ago it arose and under what circumstances it appears. We are unlikely to be able to fix non-reproducible errors that we have not encountered before.

4) Does this happen if I run 1c from another computer/from another user? This will give us food for thought - whether clearing the cache, setting permissions, or clearing user settings can help.

Now a little about the errors themselves and how to solve them.

General:
Some errors occur when using unlicensed software (Windows, 1C, etc.).

A common example is a broken platform. One of the patches hacks a specific version of the platform, so after installation new version platform and try to enter the database, you can see the “No free license found” window.

If you encountered an error for the first time - perhaps someone has already encountered it -

search on google, maybe someone has already encountered this and solved the problem, and you won’t waste an extra couple of hours of your time.

The release of configurations must be up-to-date (primarily for the configurations from which regulated reporting is submitted); it is not without reason that the consultation line almost always suggests updating first, and then looking further.

Current platform release - for each configuration it is written which platform release is recommended for working with this configuration.

The technological log allows you to log all 1C:Enterprise events (or part, using a filter).
You can read about him also.

!!!IMPORTANT

Before any actions with the database, make an archive copy!

If the database does not open in the configurator, copy the folder with the database and perform all operations on the copy!

1) The database does not open at all, either in user mode or in the configurator.

The fastest thing you can do is clear temporary files (remove the database from the list of databases and connect again)
This action will not delete temporary files (cache), but will create a new folder for temporary database files. You can delete files:
On Windows 7 in C:\Users\Username\AppData\Roaming\1C\1Cv8x
In Windows XP C:\Documents and Settings\User_Name\Application Data\1C\1Cv8х

You can also try to log into the database from another user.

If the database is file-based, then it is worth running the utility for testing the physical integrity of the database chdbfl. It is located in the folder:
C:\Program Files (x86)\1cv8\8.x.x.xxx\bin\chdbfl.exe

If the database is sql, then testing using sql.

If neither one nor the other helps, then you can update the platform (see what platform the release works under)
If none of the above works, you can use the Tool_1CD program.

2) If the database is dumped upon startup.

Disable video card hardware acceleration:

Open screen properties. This can be done through the Control Panel, or simply by clicking right click mouse anywhere on the desktop, free from windows and icons, and selecting the “Properties” context menu item.
In the display settings window that opens, go to the “Settings” tab and click the “Advanced” button.
In the video card properties window that opens, go to the “Diagnostics” tab.
Move the "Acceleration" slider to the far left position ("no") and click "Apply" or "OK". Hardware acceleration is disabled. The changes will take effect after the system is rebooted.

Open Control Panel (Start - Control Panel).
Find and open the Screen element.
In the left part of the window that opens, click on the “Configure screen settings” link.
In the window that opens, click on the “Advanced settings” link.
Go to the Diagnostics tab and click the Change Settings button.
In the window that opens, move the slider to the far left position (“no”) and click “Ok.” If UAC is enabled, you will have to confirm that the changes are authorized by the user. Hardware acceleration is disabled. The changes will take effect after the system is rebooted.

In Windows 7, in some cases the "Change Settings" button will be grayed out. In this case, it is impossible to disable hardware acceleration, since the video card and its driver do not support manipulation of hardware acceleration.

If you have Kaspersky antivirus, you can try disabling self-defense and renaming the kloehk.dll and mzvkbd3.dll files in the Kaspersky folder. (The error occurred on older versions from 2011, but still occurs sometimes)
Check that the release platform/configuration matches.
Try logging into the database from another platform.

3) The database opens in the configurator, but does not want to enter user mode.

Clearing temporary files
Trying to log in as another user
chdbfl / testing using sql
Information security testing and correction:
In the configurator Administration-Testing and Correction - checkboxes depending on the situation.
Try to create another user with full rights and log in as him.
Try to transfer it to another PC and open it there, maybe something from the PC.

4) When some action occurs, it throws the code into the configurator.

To check, you should clear the cache.
If it doesn’t help, then most likely there is an error in the code - this is especially true for non-standard and self-written configurations, but sometimes occurs in standard ones too.

If the configuration is atypical, then either the update was incorrect or the developer who finalized the configuration did not provide for all the possibilities of user errors - foolproof (if possible!).

If it is typical, then there may be a bug in the release.

In any case, it's worth running through the debugger and seeing what's wrong.

5) Under one user it allows you to do something, under another it does not.

User rights settings.
User Settings.
Clearing the cache.

6) It logs in from one PC, but not from another.

Check in Explorer to see if the database is visible - maybe the folder with the database is not shared.
Clearing the cache.
Login as a different user.

7) I didn’t do/did anything, but everything broke for me

If they can tell you what exactly they “didn’t do” and when, then you can use

log with selections and perhaps find out what the problem is.
The log book can be found in the configurator:
Administration - log book.
Or in user mode - the location depends on the configuration.

8) Not enough memory.

I had a case, a client came and said that when closing the month, the error “Insufficient memory” appears. I took on this problem. I thought it was easy, first I added RAM - a mistake. It was 2 gigabytes, now it’s 4, but 1s is still not enough. I changed the size of the paging file - an error, reinstalling the system (installed Windows 7) gave only a temporary result, for about a week. I tried everything. After some time, a solution was found.

Solution

On the client computer, run the command line as administrator and enter the following:

BCDEdit /set increaseuserva xxxx- instead of xxxx, write the amount of virtual address space in megabytes, i.e. how much memory is needed for running applications. Default is 2 gig. Generally in 32-bit operating systems ah, 4 gigabytes are allocated: 2 for applications and 2 for the needs of the OS itself. I chose 3000 (ie CDEdit /set increaseuserva 3000 ). However, the system may be buggy. Especially if you have 2 gigs of RAM, like me. This is for the OS family Windows Vista, 7, Windows 2008.

For Windows XP\Windows 2003 we write
/3GB /userva=xxxx (xxxx in MB in the range 2048 - 3072) in the boot.ini file, recommended maximum values userva 2900-3030.

9) Form elements overlap each other and are incorrectly positioned.

Clearing the cache.

10) DBMS error Internal error dbeng8 components

The error is due to differences in the code between different versions of the platform when users try to use the file option. For the client-server version, control occurs at startup and working with different versions of the platform is in principle impossible.

Solution: update to the latest release on all workstations.

If it doesn’t help, then do the following:

Testing and fixing

11) Error in platform 8.3.4.428

In version 8.3.4.428 of the 1C:Enterprise platform, a critical error was discovered that occurs during data restructuring. This error has been localized and will be fixed in the next version of the platform.

12) Lock conflict during transaction execution:

Microsoft OLE DB Provider SQL Server: Could not continue scanning with NOLOCK due to data movement.
HRESULT=80040E14, SQLSrvr: SQLSTATE=42000, state=3, Severity=C, native=601, line=1

"How to check (restore) a database on MS SQL Server using server tools
Checking logical integrity must be performed using standard 1C:Enterprise tools (IS Testing and Correction). If such a check cannot be performed, you should check the physical integrity of the database using MS SQL. To check integrity using MS SQL, you need to run the following command:
Code:
DBCC CHECKDB ("",REPAIR_REBUILD)
Before executing this command, you need to switch the database to "single user" mode:
Code:
sp_dboption "","single user",true
During the operation of DBCC CHECKDB, errors may be detected and some may be corrected immediately. If errors remain, then apparently they cannot be restored without losing some data. In this case, you need to run DBCC CHECKDB with the REPAIR_ALLOW_DATA_LOSS parameter (it is advisable to make a copy of the database files before running).
Code:
DBCC CHECKDB ("",REPAIR_ALLOW_DATA_LOSS)
After executing DBCC CHECKDB, you must remember to return to normal mode (exit "single user" mode):
Code:
sp_dboption "","single user",false" (Taken from the site)

Of course, the list is far from complete, so I will be glad if it is supplemented in the comments.

Everyone knows that any software can give various glitches from time to time or, simply put, not work properly. Such failures that lead to disruption of the proper functioning of the system are called mistakes. Program 1c is a software product ( software), accordingly, in this program, various errors may also occur 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 internal mechanisms of 1C, then you will not be able to correctly understand and diagnose the error, much less correct it. Any of our 1c programmer is always ready to help you in resolving any issues related to 1s errors!

What causes errors in the 1C database?

Now let's talk a little about why various things can happen. errors in 1s database when working with the program. In fact, there can be a lot of reasons and they can all have completely different reasons. And yet, we will try to understand in general terms the reason for the emergence of various errors in 1s.

Types of errors in the 1C database

Errors in 1s There can be a great variety and they can happen for a variety of reasons. In this article we will not consider everything possible mistakes 1c, we will try to highlight the so-called main “types” of errors encountered. We conventionally call them “types” since 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 ones errors in 1s database:

Stream format error
Object field not found
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

1s stream format error

Object field not found

Object field not found

The index is outside the bounds of the array

Error 1c

Stream format error in 1s

This error very often occurs when a sequence of commands is mistakenly read from bytecode in a stream, which is why it is called 1s stream format error. Any transaction will be aborted if this error occurs as a result of its execution. Such errors require immediate correction as they can harm the operation of the 1C Enterprise system. These errors can only be corrected by qualified 1C programmers.

Object field not found

If the 1c system gives you an error message with the text " Object field not found", this means that the error occurs in a situation when the program tries to access an attribute (field) of an object that simply does not exist. This error has the nature of a “runtime error” if it occurs in 1C Enterprise. Errors of this kind can also only be corrected programmers.

The index is outside the bounds of the 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, DirectoryLink, DocumentObject, etc., as well as any primitive types such as number, string, Boolean, etc.). Error 1c associated with going beyond the bounds of an array occurs precisely when a program accesses the boundaries of the memory that is allocated for the array. Accordingly, the program in this case generates an error and notifies the user (programmer) that an access outside the array is occurring, and this in turn is a software error.

Object method not found

A similar error occurs when the system tries to access a method (function) of an object whose description does not exist in the code. Errors of this type can be corrected by programmers.

Not enough memory in 1s

This error occurs when the system runs out of all RAM allocated for the needs of executing programs in the operating system, which is why the program generates the error " Not enough memory in 1s". It can occur during various events such as configuration updates, processing large file, when generating a report, loading a large database, etc. A similar error the user can try to fix it himself.

Possible fix for 1c error “Not enough memory”

The error lies in the limited allocation of address memory by the operating system for software (software).
The default address memory limits are:

for a 32-bit system – 2GB
for 64 bit – 4 GB

In order to increase the address memory size you need to do the following:

Launch the command line: “Start – Run” - type CMD and press enter
Now in command line enter the text without quotes “bcdedit /set increaseuserva 3072″, where 3072 is the size of the desired address memory
Reboot your operating system (computer)
Try to perform that action in 1C that did not work before and led to an error.
If everything worked out and the operation is not repeated so often, it is recommended to return the address memory size 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, when the system accesses the table and cannot read the data. This error may occur due to correct settings server, and also due to damage SQL tables. In particularly difficult situations, it may not even be possible to restore the database, and then only an archived copy of the database can save you. We strongly recommend making timely backup copies of the database.

Access error in 1s

This error occurs when a user tries to perform an action that is prohibited by access rights (roles). This is why the system issues an access error of 1s. Roles are configured in the configurator by the programmer.

Couldn't fix the error in 1s?

If you were unable to fix any error in 1C, don’t despair, pick up the phone and call us! Our specialists are always ready to help you resolve any issues related to 1C, including errors that arise during the operation of the system.

This article will explain the causes, types and solutions.
“Stream format errors” 1C.

Everyone who works with 1C:Enterprise in any configuration has at least once seen a window with the error “Stream format error”.

This window is included in the TOP 3 most common 1C:Enterprise errors. It is unpleasant because it is not informative. It’s not clear: where and what is the error? The natural reaction would be to click the “Restart” button, but with a high probability it can be argued that restarting the problem will not fix the problem, and the user will see this window again.

This article will explain the causes, types and methods of eliminating the “Stream Format Error” 1C.

Why does 1C 8 write “Stream format errors”?

The 1C:Enterprise program is created in such a way that during its work it constantly strives to optimize the speed of operations. For this purpose, a “cache” is created on the user’s computer, which stores frequently used information, for example: the location and shape of windows, user service data, selection settings, fonts, etc. Caching allows you to reduce the number of calls to the server and, thereby, increase the speed of 1C:Enterprise.

But what happens if the “cache” file is written with an error/errors, as a result of an incorrect termination of a work session, or a power surge, or a network failure (for the client-server version of 1C)? The next time you try to access the “cache,” 1C will not be able to read the file and the “Stream Format Error” window will appear. “Broken cache” is the most common cause this error occurs.

In addition to an incorrectly written cache, documents (or directories, or any other object) may also be incorrectly written to the information database, and this can also cause the error discussed in this article to occur.

Types of stream format errors

Conventionally, the 1C stream format error can be divided into 2 types:

The first type is an error that occurs when starting 1C. It is the result of an incorrect termination of a work session or a power outage; or appears after . In this case, the error must be looked for in the cache.
The second type is an error that occurs while working with 1C, for example, when opening a directory, or when posting a document, or when generating a report, or when updating. In this case, you need to look for the error in the information database.

Depending on the type of error, you can choose the most appropriate option for eliminating it. But you can use all the methods in turn until one of them works. The methods will not harm your 1C 8 database. However, if you act as real professional– you should first make a backup, and only then deal with the “Stream format error”.

How to resolve “Stream format error”?

Let's consider the TOP solutions:

1. Clear 1C cache

This method was discussed in detail in our article “”. Let us briefly recall. To delete cache files manually, you need to find the folders where the cache is stored. For operating systems Win7 and higher, temporary files are stored at C:\Users\Username\AppData\Roaming\1C And C:\Users\Username\AppData\Local\1C in folders starting with "1cv8". In Windows XP, in the user's folder at Local Settings\Application Data\1C\. If the AppData folder is not visible, adjust the visibility hidden folders. The figure below shows what cache files look like - folders with long, unclear names (in our case there is only one file). To clear the cache, you need to delete these folders.

Important! You can delete folders only when the processes of working with 1C:Enterprise are completed.

2. Start testing and fixing 1C

In the configurator mode, you need to click on the “Administration” menu item and then “Testing and correction”.

The first two points “reindexing tables” should be checked information base” and “checking the logical integrity of the information base”. Click the “Run” button. The system itself will check the database, find errors, correct them and provide you with a report on the work done. If necessary, also check the third item “checking the referential integrity of the infobase”.

3. Run “chdbfl.exe”

If it is not possible to enter the configurator, then run the program “chdbfl.exe”, which is located: “C:\Program Files (x86)\1cv8\8.3……\bin”. Select the Database file, check the “Correct detected errors” checkbox and click the “Run” button. Then the system will do everything for you. The system itself will check the database, find errors and correct them. While the “chdbfl.exe” program is running, there should be no active sessions with 1C.

4. Upload and load the information base into .dt

In configurator mode, select the “Administration” menu item and click “Download infobase”. After that, select the location where you want to save the database file (.dt), give the file a name and click “Save”.

After this, create a new empty database on your computer (or server). Go to the new database configurator, click “Administration”, then “Load infobase”. Select the previously prepared file and click “Open”.

5. Upload and load XML data.

This method may result in data loss, so it is recommended to be used only by experienced users. The method is similar to the previous one and consists in the fact that first the database is unloaded (just not in.dt, as in previous method, but in a special format.XML). Then the database is loaded back. This is done using the built-in processing “Uploading and loading XML data”.

6.Update 1C

The cause of the error in question may be the presence of active user sessions working in different versions. For example, in the database there is an active user session with the 1C platform 8.3.5...., and another one is trying to connect, with version 8.3.4.... If several versions are installed on your computer, make sure that the “correct” version you need is selected in the infobase editing window.

7. Other methods.

In 99% of cases, the above methods of dealing with “Stream Format Error” will effectively do their job and the error will “go away”. In the remaining 1%, you will have to use more complex diagnostics, sometimes beyond the scope of 1C, for example: clean the computer’s temporary files, and not just the 1C cache; check HDD on bad sectors using the “chkdsk.exe” utility; check your computer with antivirus. You can even try to run the 1C database on another computer and thus localize the problem, making sure that the error lies in the information database, and not in the hardware or the Operating System.

This article was created to help those who encountered the 1C error “Stream format error”; the reasons for its occurrence, its conditional types and methods of elimination were discussed and explained here. The error looks scary and incomprehensible due to its uncertainty, but, as we see, it can be eliminated this error everyone can do it.

Description of the stream format error in 1C 8.3

The stream format error in 1C occurs most often among all users. And usually in such cases it is difficult to explain its appearance - it seems that they were working in 1C, everything is as usual. Once again launching 1C, we receive the following message:

None of the Stream Format Error buttons allow you to launch the database and continue working. Precisely because this error is the most popular and frequent, we will first explain its causes, and only then move on to considering methods for solving it.

Reasons for the stream format error in 1C 8.3

The stream format error in 1C is related to reading the database cache when accessing it. Cash, if we speak in simple words, this is auxiliary information (settings, favorites, frequent commands, etc.) 1C, stored in files separate from the database. During operation, 1C regularly accesses the cache. If a situation arises when this access was interrupted (during a power outage, network problems, emergency shutdown of 1C), the cache may be written with errors. In this case, upon subsequent startup, reading the cache will lead to this same error - a stream format error in 1C.

Ways to solve stream format errors in 1C 8.3

Before you start solving the problem using any of the methods, be sure to make a backup copy of your database! This will help you return to the original result in cases where an attempt to solve a problem fails.

For quick creation backup copy open the folder with the database (as done in method No. 1) and copy its contents to any other location. Carry out error correction work only with a backup copy!
1.
2.
3.
4.
5.
6.

Clearing the 1C database cache

The simplest and most helpful method is to clear the 1C database cache. To do this, launch 1C: Enterprise and find out the path where the database is stored:

Let's open this folder in Explorer and delete all files except the database file, as shown in the figure below. Note that the number of files may differ; all of them must be deleted, except one - 1Сv8 (file information database).

Clearing 1C cache

The next method is to clear the 1C: Enterprise cache. To do this, you need to open the folders where they are stored. On Windows 7 and higher there are two of them:

C:\Users\Username\AppData\Roaming\1C

C:\Users\Username\AppData\Local\1C

You should delete the 1cv8 folder in both of them:

After clearing the cache, try logging into the database again. Is the error still there? Try the following method.

Correcting the database using the chdbfl.exe utility

It is possible that the stream format error may be related to errors in the database itself. To do this, you should check it using special program chdbfl.exe, which comes bundled with 1C: Enterprise. To do this, go to the folder with the program (most often this is C:\Program Files\1cv8\8.3.XX.YYY\bin\) and find the chdbfl.exe file:

Once you open it, click the ellipsis in the upper right corner and find the broken database file. Based on the method above, we can say that this is the same database file that you did not delete when clearing the cache.

After that, check the Fix detected errors checkbox and click Run. Wait until the check is completed and try to start the database. Is the error still there? Try the following method.

Testing and fixing the database using the Configurator

The next way to solve a stream format error in 1C is to Test and fix the database, available from the Configurator.

Launch 1C: Enterprise through the Configurator mode:

In the Configurator that opens, select Administration – Testing and Correction:

In the window that opens, set the settings as in the figure below and click Run.

Wait until all procedures are completed. Close the Configurator and try logging into the database. Is the error still there? Try the following method.

Uploading and loading the database via dt

This method can help eliminate errors that are not eliminated by paragraphs 3 and 4 of this article. Log in to the database through the Configurator mode, as in the method above. Select Administration – Upload infobase:

In the window that opens, select the unloading location. It can be anything, the main thing is to remember this place.

By clicking Save, wait for the upload to complete. Exit Configurator mode. Open 1C: Enterprise again and select Add – Create a new infobase – Create an infobase without configuration – Next – Finish.

Open the created database through the Configurator and click Administration – Load infobase. In the window that opens, indicate the upload file that you just created. Wait for the download to finish, close the Configurator and try logging into the newly downloaded database. Is the error still there? Try the following method.

Advanced ways to solve 1C data format errors

A detailed discussion of advanced methods for solving data format errors in 1C is beyond the scope of this article, since to use them you need to have some knowledge in the field of handling a computer, so the instructions and notes for each of them would be quite voluminous.

We will limit ourselves to listing them:
1. Uploading and loading data between a non-working and empty database using the “Uploading and loading XML data” processing.
2. Various versions used 1C, working in the same database via the network (for more details, see) must be put in order.
3. Disabling the IPv6 protocol through the Windows registry.
4. Reinstallation or update of 1C: Enterprise.
5. Transfer the database to another computer and try to run it there.
6. Disabling or removing firewalls and/or antiviruses.
7. Checking the stream format using the Tool_1CD utility
8. Update the configuration using the .cf file.

Is the problem “Stream format error in 1C 8.3” not resolved? Get a free consultation from our specialists to solve this problem!

There are situations when, when working with 1C 8.3 or 8.2, you get the error “DBMS error: Internal error in dbeng8 component.” Of course, its description is not as informative as we would like it to be.

In this case, most likely, the structure of the internal storage of tables in the database of the application solution you are using is broken. Don’t despair, the error can be treated and if you use all our advice, you will most likely be able to fix it.

Please note that before proceeding with the methods below, Necessarily. You shouldn't create unnecessary problems for yourself.

In cases like this, as with fixing anything, it's always best to start from simple to complex. Therefore, the first thing you need to do is install the latest version of the 1C platform. If you are already using it, or for some reason do not want to update, you can simply replace the “dbeng8.dll” library, taking it from a different directory installed program, both on your PC and on another.

In our case, it is located in the “D:\Program Files (x86)\1cv8\8.3.9.2170\bin” directory, since this is where the platform itself is installed.

Testing and correction in 1C

Often, the method of updating the platform does not always help, since the error lies in the database itself. In this case, with a very high probability, it will help you.

Using the configurator

Solving the problem in this way is done from the configurator. Go to the "Administration" menu and select "Testing and fixing...".

In the preliminary settings form that appears, remove the flags from the items “Reindexing infobase tables” and “Recalculation of totals.” These add-ons will not play a role in correcting our error, but will only increase the data processing time.

After clicking on the “Run” button, the program will start the process of testing and correcting the information base, which can take quite a long time. Upon completion, you will be presented with a full report.

Utility "chdbfl.exe"

This utility is an analogue of testing and correction and is intended for file information databases. No need to search on the Internet where to download it. This utility is included in the delivery of the 1C platform itself and is located in the same folder as the library referenced by the error we are correcting.

In addition, you need to find out where the information base in which you received the error is located. Select it in the list of information bases, and at the very bottom of the window, this information will be available to you.

Now let’s open it itself and in the “DB file name” field, select the file “1Cv8.1CD” from the directory whose address we just found out.

We need not only to carry out diagnostics, but also to restore the functionality of the information base. In this regard, in this situation, it is necessary to set the flag on the “Correct detected errors” item.

These and some other methods are also discussed in this video: