KoriBlast warning and error messages usually come from problems occuring while the software attempt to connect and to get some data from remote servers (NCBI and EBI). When the remote servers do not respond and/or do not send back to KoriBlast correct data, the software will complain. For instance, you are certainly aware that using the NCBI servers during the afternoon (Western Europe time) is really not easy due to the high number of users connecting to the US Institute. In that case, KoriBlast may fail when connecting to NCBI due to the heavy load on the NCBI servers.

From your side, the details of the warning/error messages are usually not very useful... because quite technical! When getting such messages during remote server connections, the best thing to do is to retry later on. However, if you want to understand what happens, you can have a look at the KoriBlast log file. This file stores almost the entire behaviour of the software during a working session. To view this file, double click on the Console panel: it is located at the bottom of the KoriBlast frame (it is the component displaying single line message). Then, select the 'Log file' tab. Since the log file is not automatically reloaded by KoriBlast, you can click on the refresh button to view the most recent content of the log file. Messages are sorted by time, most recent messages being at the end of the log file.

When contacting the Korilog support to report an error, you can provide us with a copy of this file. This could help us in locating the origin of the problem.

Go back to Using FAQ