If an urgent or serious system error occurs from which recovery is not possible or which might corrupt information if operations are continued, all services of the asset management system are stopped.

Urgent or serious system errors are described below.

• Invalid settings or read errors in the environment definition file
• Detection of damaged meta table
• Program exceptions, such as a general protection exception
• Internal program errors

If a system error that is not urgent or serious occurs from which recovery is possible over time and which will not corrupt information, even if operations are continued, the executing process in which the error was detected is terminated.

System errors that are not urgent or serious are described below.

• Invalid format of messages from Web browser
• Message log output errors
• Database connection broken by the DBMS
• Notification of errors in a program linked to the asset management system
• Access error notification during addition, updating, or deletion of asset information (except when there is no property data that becomes the key)
• Internal program errors

If either of the operational errors described below occurs in the asset management system, no asset management system service has stopped.

• Login error due to invalid user ID or password
• Import errors during asset management system operation and errors in inventory information

If a temporary error occurs from which recovery is possible by re-executing the command after some time, the executing process in which the error was detected is terminated, releasing the session.

Examples of temporary errors are described below.

• Memory allocation errors and database connection errors
• Database lock errors
• Import errors during asset management system operation and errors in inventory information