The following procedure is applied to generate error messages:
The most nested exception (i. e., the very first exception) is retrieved from a sequence of any exceptions detected.
The text describing the very first exception is used for a brief introduction of the error:
○ For module compilation errors, the brief introduction includes the text related to the location of the error (string in the module).
○ For runtime errors, the brief introduction uses the text without any details related to the location of the error (module string).
The brief error description is displayed to the user in the dialog. This dialog may also include the Details button if the following is true:
○ the debug mode is enabled;
○ a 1C:Enterprise script error appears; ○ multiple exceptions exist in the sequence.
A detailed description of an error is generated from the descriptions of all exceptions in the sequence.
If the error dialog does not contain the Details button and the error is critical (i.e., the program cannot continue), the dialog will contain the Show technical support information hyperlink.
Clicking the Details button opens an additional window with a detailed description of the error and the additional Designer button, if the dialog displays a script error.
When a thin client or a web client operates in the client/server mode, the following error situations are processed:
If an established infobase connection lock is detected when the system starts operating, an error message is displayed prompting the user to repeat the connection.
If the server and client application versions do not match, an error message is displayed prompting the user to restart the system.
If the thin client launch authorities are missing, the behavior is determined by the -AppAutoCheckMode launch key:
○ If the key was specified at startup, the system automatically tries to launch the thick client.
○ If the key was not specified at startup, an error message dialog is displayed (not prompting the user to restart the system).
When it is impossible to connect to the 1C:Enterprise server (or the web server) to send the queries with the resend option supported or the queries processed before the beginning of the session, an error message is displayed prompting the user to repeat the query or cancel it. When a query is cancelled, 1C:Enterprise is not shut down. However, if a query cannot be resent, an error message is displayed prompting the user to restart the system.
If an error occurs during query processing on the server, an error message is displayed prompting the user to restart the system.
If a session error occurs (e.g., the session is deleted by the administrator), an error message is displayed prompting the user to restart the system.
If an internal platform error occurs, the web client creates an error of the following type: Unknown error: <error description>.
If a web client or a thin client connected via a web server is used to establish a connection with the infobase, then the error codes in the case of irregular situations are as follows:
400 Bad Request – describes applied solution errors that are not critical for client application operation (including all runtime exceptions). It cannot be trapped to be displayed to the user.
500 Internal Server Error – describes the applied solution errors critical to the client application, e.g.:
○ unrecoverable database exceptions;
○ exceptions related to session deletion or lack of session data.
502 Bad Gateway – describes the server cluster or scheduled operations errors that are critical to the application, e.g. the connection with 1C:Enterprise cannot be established.
503 Service Unavailable – describes server cluster or scheduled operations errors that are critical to the client application, e.g. the connection with DBMS cannot be established.
To keep the system operable, do not trap errors with the 400 code. Errors with the 50x code may be trapped to display a more user-friendly error message.