Mitsubishi Electric Melsec Q Series User Manual page 368

10
TROUBLESHOOTING
Table 10.5 Event log output error list of DB Connection Service (source name: DBConnector)
Error code
501
502
503
504
505
506
507
Table 10.6 Event log output error list of DB Connection Service Client (source name: DBCnctClient)
Error code
50
51
52
53
10
- 27 10.2 Error Code List
10.2.2 Error codes of DB Connection Service
Error description and cause
The computer ran out of memory when initializing
the SQL failure log file.
The computer ran out of resources when initializing
the SQL failure log file.
The full path name of the SQL failure log file is too
long.
The SQL failure log file could not be opened.
The log could not be written to the SQL failure log
file.
Failed to delete an old SQL failure log file.
Failed to rename the SQL failure log file.
(c) Event log output error list of DB Connection Service Client (source name:
DBCnctClient)
Error description and cause
Unable to start DB Connection Service Client.
(From the previous page)
Corrective action
• Terminate any unnecessary applications.
• Add more memory to the personal computer.
• Shorten the path to the SQL failure log file with
DB Connection Service Setting Tool.
• If no directory exists for storing the SQL failure
log file, create it.
• When the attribution of the SQL failure log file is
set to read-only, cancel the setting.
• If read/write is disabled for the SQL failure log
file, enable it in the security setting.
• When the SQL failure log file name represents a
directory, rename or delete the directory.
• When the SQL failure log file has been open in
another application, terminate the application.
• Check the disk device for any fault.
• When the disk space is full, ensure a free disk
space.
• When the SQL failure log file has been open in
another application, terminate the application.
• Check the disk device for any fault.
• When the attribution of the oldest SQL failure log
file is set to read-only, cancel the setting.
• If read/write is disabled for the oldest SQL failure
log file, enable it in the security setting.
• When the oldest SQL failure log file has been
open in another application, terminate the
application.
• Check the disk device for any fault.
• When the attribution of the new and old SQL
failure log files is set to read-only, cancel the
setting.
• If read/write is disabled for the new and old SQL
failure log files, enable it in the security setting.
• When the new and old SQL failure log files have
been open in another application, terminate the
application.
• Check the disk device for any fault.
Corrective action
• Terminate unnecessary applications.
• Add more memory to the computer.