Answer the question
In order to leave comments, you need to log in
Crash?
Several new configurations were installed in the Configurator in succession. The latest update issued a warning that was successfully ignored.
When entering normal mode, a warning was issued that not all operations of the previous update were carried out. If you continue, the program will be unstable.
Actually, this is what happened. See screenshot. This happens 2-5 minutes after login in any screens. "Testing and fixing" was done in the configurator, it fixed something, but it didn't help much.
Backup base is only the middle of last year.
Question: how to fix the base?
Answer the question
In order to leave comments, you need to log in
In typical configurations, upon successful and especially unsuccessful update procedures in the enterprise mode (after the updates are successfully installed in the configurator mode or in batch mode), it is proposed to view the log with a filter for the current session.
In this log, you would see all the problems that occurred and would know exactly the reason why the update was not applied. But even now you can make a selection in the log filter for the time of the update and try to understand what happened. Maybe it's a data problem. Perhaps this is a combination of problems in the structure of the database and the quality of this data. Perhaps the above was superimposed on a rare bug in the platform...
If analyzing the log does not help, then you will need to set up a technological log and carefully study what happens at the moments of crashes.
Backup base is only the middle of last year.
Question: how to fix the base?
several new configurations
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question