--- title: "The EAVR window disappeared and an error occurs when working with ESF" country: KZ lang: en author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti) date: 2026-09-23 canonical: https://buhgpt.kz/suraqtar/propalo-okno-eavr-i-oshibka-pri-rabote-s-esf-en source: BuhGPT --- # The EAVR window disappeared and an error occurs when working with ESF > **TL;DR:** Short answer: If in the fresh version of 1C the EAWR (electronic act of completed works) window disappears and errors appear when working with the ESF, the problem is almost always related to accumulated program cache or temporary malfunctions on the side of the cloud service. --- Short answer: If in the fresh version of 1C the EAWR (electronic act of completed works) window disappears and errors appear when working with the ESF, the problem is almost always related to accumulated program cache or temporary malfunctions on the side of the cloud service. Solution: clear the cache and contact 1C:Fresh support — specialists will fix the malfunction on the service side. Why this happens specifically in the fresh version Fresh versions of 1C work through a cloud service, not on the user's local computer. Because of this, part of the interface and data exchange with external systems (including the IS ESF portal, through which ESF and EAWR pass) depend on the correct operation of the cloud and on the local cache of the browser/thin client. Such failures — the disappearance of interface elements (for example, the EAWR window), errors when generating or sending ESF — are often caused precisely by accumulated cache or temporary malfunctions on the service side. These causes are eliminated by fresh technical support, so it is usually not necessary to "fix" the configuration yourself. What to do: step-by-step order - Clear the program cache. This is the first and most common solution. After clearing the cache, log back into the database and check whether the EAWR window has appeared and whether exchange with the ESF works without errors. - Contact 1C:Fresh support. If the problem persists after clearing the cache, fresh support specialists will help resolve the situation on the service side — that is where temporary cloud malfunctions are eliminated. It is important to understand the division of areas of responsibility: the disappearance of the interface and exchange errors in the fresh version are resolved on the service side, so contacting fresh technical support is not a formality, but the correct route to a solution. How to clear the cache in the fresh version The clearing method depends on how you connect to the fresh service (through the 1C thin client or through a web browser). General order: - If login is performed through a browser — clear the browser's cache and temporary files, then restart it and log into the database again. - If a 1C thin client is used — close the program and clear the client's local cache (the 1C temporary files directory), then start it again. - After clearing, be sure to perform a re-login to the database — the cache is recreated upon a new connection. If you are not sure which cache exactly and how to clear it in your connection configuration, do not delete service files blindly — it is better to clarify this step with fresh support so as not to affect working data. What to check before contacting support To speed up the solution and rule out simple causes, check: - Stability of the internet connection. Exchange with the ESF and the operation of the cloud database require stable network access. - Repeatability of the error. Does the error appear constantly or once? A one-time failure may be a temporary service malfunction and pass on its own. - Exact error text. Record (screenshot) the message that the program displays when working with the ESF — this will help support determine the cause faster. - Whether the problem affects other database users or only you — this suggests whether it is a local problem (cache) or a general one (service). - Availability of the IS ESF portal itself. Sometimes exchange errors are related to unavailability or scheduled maintenance on the side of the government system, and not to 1C. Typical mistakes - Trying to fix the configuration manually. In the fresh version, configuration modifications are limited, and the cause of the failure is usually not in it, but in the cache or service. - Ignoring cache clearing and immediately reinstalling or changing settings — most often it is precisely cache clearing that solves the problem. - Not contacting fresh support. If the cache is cleared but the error remains, further "self-treatment" can only delay the solution — a malfunction on the service side is eliminated only by its specialists. - Confusing an interface problem with a data problem. The disappearance of the EAWR window is, as a rule, a display of the interface, and not a loss of documents; the data itself in the database is preserved. - Deleting or recreating ESF/EAWR documents "just in case". Until the cause is clarified, unnecessary actions with documents can lead to desynchronization with the ESF portal. Conclusion The disappearance of the EAWR window and errors when working with the ESF in the fresh version of 1C is a typical situation related to the cloud architecture of the service. In the vast majority of cases, it is resolved in two steps: clearing the program cache and contacting 1C:Fresh support. Since fresh versions work through a cloud service, such failures (disappearance of interface elements, ESF exchange errors) are eliminated precisely on the service side by technical support, and the accountant is required to correctly describe the problem and provide data for diagnostics. --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_