The most common 1C errors and methods for correcting them. The most common 1C errors and methods for fixing them Subd error internal error of the dbeng8 component

Base won't open

Platform update.

Clearing temporary (cash) files: remove the database from the list and connect it again.

Login to the database from another account.

Nothing works for no apparent reason

Platform update.

Search for the cause of the failure in the log.

Dump bases on startup

Disable graphics card hardware acceleration Windows tools, system reboot.

The database opens in the configurator, but not in user mode

Platform update.

Clearing temporary (cash) files.

Login to the database from another account (and / or from an administrator account).

Logging into the database from another computer (to exclude a general malfunction of the current one).

Testing the physical integrity of the database using the "chdbfl" utility (folder C:\Program Files (x86)\1cv8\8.x.x.xxx\bin\chdbfl.exe) or, in the case of a SQL base, testing using SQL tools.

Testing and fixing information security using the configurator.

The program opens the configurator code without warning

Platform update.

Clearing temporary (cash) files.

Checking the code in the debugger.

As a rule, this situation occurs due to errors in the modified code, most often in the case of non-standard configurations.

The program works differently for different users

Platform update.

Clearing temporary (cash) files.

Group rights setting.

Setting user rights.

Incorrect display of form blocks

Platform update.

Clearing temporary (cash) files.

Login to the database from another account (and / or from an administrator account).

Logging into the database from another computer (to exclude a general malfunction of the current one).

The program does not work on some computer in a working network, but works on others

Checking network rights this computer(Windows tools).

Platform update. This includes checking that configuration and platform releases match within the network.

Clearing temporary (cash) files.

Login to the database from another account (and / or from an administrator account).

Not enough memory

Platform update.

Clearing temporary (cash) files.

Login to the database from another account (and / or from an administrator account).

Logging into the database from another computer (to exclude a general malfunction of the current one).

Optimization of problem queries.

Hardware expansion of memory.

Increasing the paging file size.

Dedicated memory management via command line Windows. Line: "bcdedit / set increaseuserva 3072", where 3072 is the size of the desired address memory.

DBMS error, internal component error dbeng8

Platform update on all network computers.

Testing testing the physical integrity of the database using the "chdbfl" utility.

This error is typical for networks without a 1C server and is associated with a difference in the code of different versions of the platform on different access points.

A problem such as Stream Format Error occurs quite often in 1C 8.3. Let's see how to fix this error.

What is a stream format error in 1s 8.3?

This happens in the following situations:

1. The stream format error when starting 1C Enterprise 8.2 or the configurator is usually associated with problems in the cache. It is usually caused by improper shutdown of the system due to, for example, a power outage. Therefore, it is highly recommended to put blocks uninterruptible power supply not to lose important information. Often the error appears when starting the database after updating the configuration.
2. The second situation is when generating a report, for example, opening a report, posting a document, opening a document, etc. Often this is due to the content of the information in the database. The reason for this error is most often the presence of “broken” information inside the system.

Get 267 1C video lessons for free:

Correction

1. As a rule, to solve this problem, it is enough to clean the temporary files in the system. .
2. If it didn’t help, but there is an opportunity to get into the configurator, run .
3. If there is no access to the configurator, and the database is a test one, use it, which is located in the program folder.
4. If the above methods do not help, but the 1C enterprise mode starts, upload the data to a new database using the processing "". However, data loss is possible.
5. Update. Another reason may be the presence of active user sessions with different versions of the client part of the 1C platform. That is, for example, a user with the 1C platform 8.3.5.1517 works in the database, and another one tries to connect, with version 8.3.5.1444.

If this does not help, there are more sophisticated ways to solve this problem. For example, using a HEX editor. If you need qualified assistance from 1C programmers, please contact us! Details on the page

This article will explain the causes, varieties and solutions
"Stream format errors" 1C.

Everyone who works with 1C:Enterprise in any configuration at least once saw before his eyes a window with the error "Stream format error".

This window is included in the TOP-3 of the most common 1C:Enterprise errors. It is unpleasant because of its lack of information. It is not clear: where, what is the mistake? The natural reaction would be to press 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, varieties and ways to eliminate the "Stream Format Error" 1C.

Why does 1C 8 write "Stream format errors"?

The 1C:Enterprise program was created in such a way that in the process of work it constantly strives to optimize the speed of operations. For this purpose, a "cache" is created on the user's computer, in which frequently used information is stored, for example: the location and forms of windows, user service data, selection settings, fonts, etc. Caching allows you to reduce the number of requests 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 session termination, 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 occurrence of this error.

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

Kinds of Stream Format Error

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 session termination, 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 in the process of 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, the error must be looked for in the infobase.

Depending on the type of error, you can choose the most appropriate option for its elimination. But you can use all the methods in turn, until one of them works. The methods will not harm your 1C 8 base. However, if you act like true professional- you should first make a backup, and only then deal with the “Stream Format Error”.

How to fix “Stream Format Error”?

Consider the TOP solutions:

1. Clear cache 1C

This method was discussed in detail in our article "". Let's briefly recall. To delete cache files manually, you need to find the folders where the cache is stored. For operating systems Win7 and above, temporary files are stored at C:\Users\Username\AppData\Roaming\1C and C:\Users\Username\AppData\Local\1C in folders starting with "1cv8". On Windows XP, in the user folder at Local Settings\Application Data\1C\. If the AppData folder is not visible, set the visibility hidden folders. The figure below shows what the cache files look like - folders with long incomprehensible 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 menu item “Administration” and then “Test and fix”.

The first two items “reindexing infobase tables” and “checking the logical integrity of the infobase” should be checked. 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 "chdbfl.exe" program, which is located: "C:\Program Files (x86)\1cv8\8.3……\bin". Select the Database file, check the "Fix 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 program "chdbfl.exe" is running, there should be no active sessions with 1C.

4. Unload and load the infobase in .dt

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

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

5. Upload and download XML data.

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

6.Update 1C

The reason for the error in question may be the presence of active user sessions running in different versions of . 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 the computer, make sure that the “correct” version you need is selected in the infobase editing window.

7. Other ways.

In 99% of cases, the above methods of dealing with the “Stream Format Error” will effectively do their job and the error will “go away”. In the remaining 1%, you will have to apply more complex diagnostics, sometimes beyond the scope of 1C, for example: clean up temporary computer files, and not just 1C cache; verify 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 precisely in the infobase, and not in the hardware and not in the Operating System.

This article was created to help those who encountered the 1C error “Stream Format Error”, here the reasons for its appearance, its conditional types and methods of elimination were considered and explained. The error looks scary and incomprehensible because of its uncertainty, but, as we see, everyone can eliminate this error.

AT information bases on the 1C platform, many different errors can occur:

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

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

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

1) Platform/config releases.

2) Full text of the error message. Users have the unfortunate habit of not reading the entirety of such messages, and perhaps it contains a recommendation for troubleshooting.

3) How long ago did it occur and under what circumstances does it appear. Non-reproducible bugs that we have not seen before, we are unlikely to be able to fix.

4) Does it occur if you run 1s from another computer / from another user? This will give us food for thought - whether clearing the cache, adjusting permissions, or clearing user preferences 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 installing a new version of the platform and trying to enter the database, you can see the window “No free license found”.

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

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

The release of configurations should be up-to-date (first of all, for 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 - each configuration has a description of which platform release is recommended for working with this configuration.

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

!!!IMPORTANT

Before any actions with the base - 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 (delete the database from the list of databases and reconnect)

  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
  On Windows XP C:\Documents and Settings\Username\Application Data\1C\1Cv8x

• You can also try to access the database from another user.

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

• If the base is sql-th then testing by means of sql.

• If neither helped, then you can update the platform (see under which platform the release works)
• If none of the above happened, you can use the Tool_1CD program.

2) If the base goes into a dump at startup.

• Disable graphics card hardware acceleration:

1. Open the display properties. This can be done through the Control Panel, or simply by right-clicking on any place on the desktop that is free from windows and icons, and selecting context menu"Properties".
2. In the display settings window that opens, go to the "Settings" tab and click the "Advanced" button.
3. In the graphics card properties window that opens, go to the "Diagnostics" tab.
4. Move the "Acceleration" slider to the leftmost position ("none") and click "Apply" or "OK". Hardware acceleration is disabled. Changes will take effect after a system reboot.

1. Open the Control Panel (Start - Control Panel).
2. Find and open the Screen element.
3. In the left part of the window that opens, click on the link "Adjust screen settings".
4. In the window that opens, click on the "Advanced Options" link.
5. Go to the "Diagnostics" tab and click the "Change settings" button.
6. In the window that opens, move the slider to the extreme 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. Changes will take effect after a system reboot.

In Windows 7, in some cases, the Change Settings button will be grayed out. In this case, you cannot disable hardware acceleration, because the video card and its driver do not support hardware acceleration manipulation.

• If the antivirus is Kaspersky, then you can try to disable self-defense and rename the kloehk.dll and mzvkbd3.dll files in the Kaspersky folder. (The error occurred on older versions of 2011, but still occasionally occurs)
• Verify that the platform release/configuration matches.
• Try to access the database from another platform.

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

• Cleaning up temporary files
• Attempt to log in as another user
• chdbfl / sql testing
• Testing and fixing information security:
  In the configurator Administration-Testing and correction - checkboxes depending on the situation.
• Try to create another user with full rights and log in from him.
• Try to transfer to another PC and open there, maybe something from the PC.

4) When some action throws out the code in the configurator.

• To check it is worth clearing the cache.
• If it didn’t help, then most likely an error in the code - it is especially true for non-standard and self-written configurations, but sometimes it also occurs in typical ones.

If the configuration is not typical, then either the update went wrong or the developer who finalized the configuration did not foresee all the possibilities of user errors - foolproof (if possible!).

If typical, then perhaps 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 doesn't.

• User rights settings.
• User Settings.
• Clearing the cache.

6) It comes from one PC, but not from the other.

• Check whether the explorer sees the database - maybe the folder with the database is not shared.
• Clearing the cache.
• Log in as a different user.

7) I did / did nothing, but everything broke down for me

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

• logbook with selections and maybe find out what the problem is.
• The log can be found in the configurator:
• Administration - registration log.

  Either in user mode - the location depends on the configuration.

8) Not enough memory.

I had a case, a client came, he says, when the month is closed, the error "Not enough memory" crashes. I took on this problem. I thought it was easy, at first I added RAM - a mistake. It was 2 gigabytes, it became 4, but still 1s is not enough. Changed the size of the paging file - an error, reinstalling the system (installed Windows 7) gave only a temporary result, about a week. Tried everything. After some time, a solution was found.

Decision

On the client computer, run a command prompt as an administrator, enter the following there:

BCDEdit /set increaseuserva xxxx- instead of xxxx write the amount of virtual address space in megabytes, i.e. How much memory do you need for running applications? The default is 2 gigs. Generally in 32-bit operating systems 4 gigabytes are allocated: 2 for applications and 2 for the needs of the OS itself. I chose 3000 (i.e. CDEdit /set increaseuserva 3000 ). However, the system may be buggy. Especially if you have 2 gigs of RAM, like I do. This is for 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, the recommended maximum values userva 2900-3030.

9) Form elements overlap each other and are in the wrong position.

• Clearing the cache.

10) DBMS error dbeng8 component internal error

• The error is related to the difference in the code of different versions of the platform when users try to use the file version. For the client-server version, at startup, control and work with different versions platform is basically impossible.

Solution: upgrade to the latest release on all workstations.

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

• Testing and fixing

11) Bug in platform 8.3.4.428

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

12) Lock conflict while executing a transaction:

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

"How to check (restore) the database on MS SQL Server using server tools
Checking the logical integrity must be performed by regular means of 1C: Enterprise (Testing and fixing information security). If such a check fails, you should check the physical integrity of the database using MS SQL. To check the integrity using MS SQL, you need to run the following command:
The code:
DBCC CHECKDB("",REPAIR_REBUILD)
Before executing this command, the database must be set to "single user" mode:
The code:
sp_dboption "","single user",true
In the process of running DBCC CHECKDB errors may be found 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 (before starting, it is advisable to make a copy of the database files).
The code:
DBCC CHECKDB("",REPAIR_ALLOW_DATA_LOSS)
After running DBCC CHECKDB, you need to remember to return to normal mode (exit "single user" mode):
The code:
sp_dboption "","single user",false" (Taken from )

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