next up previous contents index
Next: 8.2.2 Errors at the Up: 8.2 Error Checking Previous: 8.2 Error Checking   Contents   Index

8.2.1 Errors at the 'Put' Step

There are two types of errors: those generic ones from the web server and those from BLAST server.

The generic web server error has no QBlastInfo section and generally contained numeric error code.

The error from BLAST server are contained in a BLAST formatting page. The latest update to BLAST URLAPI places the error message in a special section:

<div class="msg error">string</div>

Here the 'string' represents the actual error mesage. In addition, the formatting page with error will have an empty RID field under its QBlastInfo section. Some representation errors from 'Put' step are given below.

Table 8.2.1 Selective Error/Warning Messages for Put Step
Error/Warning Messages Meaning
Error: 500, Error: 502, Error: 803 Generic error from web server
Error: 414 Request-URI Too Large The length of the posted URL exceeds the web server limit. Use POST method instead.
Nucleotide FASTA provided for protein sequence Nucleotide-like residues (AGCTN) exceeds the threshold
Protein FASTA provided for nucleotide sequence Degenerate bases (WSKYR) in the query exceed the threshold
BLASTOptionValidateEx: Valid wordsize range is 2 to 3 Protein Word_SIZE specified incorrectly
BLASTOptionValidateEx: Wordsize must be 7 or greater WORD_SIZE for nucleotide search set too low
INFO: No database names were passed to CSeqDB::CSeqDB(). Database not specified Database was not specified [checking]
ERROR: Query sequence ID not found: F12345 accession/gi mismatch. Requested protein, found nucleotide. Wrong SeqID was provided
ERROR: BlastKarlinBlkGappedCalc: Gap existence and extension values of 13 and 5 not supported for BLOSUM62 An unsupported GAPCOSTS value was used
ERROR: Query sequence not provided in any form QUERY parameter contains no value
ERROR: An error has occurred on the server. An unspecified occurred during the search.
ERROR: Cannot accept request, error code: -1 Search cannot be put in the queue due to error in the tracking database


next up previous contents index
Next: 8.2.2 Errors at the Up: 8.2 Error Checking Previous: 8.2 Error Checking   Contents   Index
Tao Tao 2007-08-03