Message Help 1500-2299

1500 ERROR: NMFS Person Name is invalid

1501 ERROR: NMFS Person Name is too long

1502 ERROR: IFQ Permit Holder Name is required

1503 ERROR: IFQ Permit Holder Name is invalid

1504 ERROR: IFQ Permit Holder Name is too long

1505 ERROR: IFQ Permit Class is required

1506 ERROR: IFQ Permit Class  CLASS  is invalid where:  CLASS  is The one character IFQ permit class code.

1507 ERROR: IFQ Permit Class is too long

1508 ERROR: Agency Stat Area is required

1509 ERROR: Agency Stat Area  STAT_AREA  is invalid where:  STAT_AREA  is The ADF&G Statistical Area identifier.

1510 ERROR:  UNIT_OF_EFFORT  must be greater than zero where:  UNIT_OF_EFFORT  is The unit of measurement for effort for the gear type, such as number of pot lifts for pot gear.

1511 ERROR:  UNIT_OF_EFFORT  cannot be greater than  MAX  where:  UNIT_OF_EFFORT  is The unit of measurement for effort for the gear type, such as number of pot lifts for pot gear. MAX  is The maximum number.

1512 ERROR:  UNIT_OF_EFFORT  is required where:  UNIT_OF_EFFORT  is The unit of measurement for effort for the gear type, such as number of pot lifts for pot gear.

1513 ERROR:  UNIT_OF_EFFORT  must be numeric where:  UNIT_OF_EFFORT  is The unit of measurement for effort for the gear type, such as number of pot lifts for pot gear.

1514 ERROR: All Agency Stat Area Worksheet Lines but one need percent entered

1515 ERROR: Species  CODE  is not a valid crab IFQ species where:  CODE  is The numeric disposition code, indicating what is being done with the catch.

For crab IFQ reporting five species are valid: Red King crab, Blue King crab, Golden King crab, Opilio snow crab, and Bairdi tanner crab. No other crab species can be entered for IFQ reports.

The species entered is not a crab species, or it is not a species that is managed under an IFQ program.

Enter the correct species code.

1516 ERROR: NMFS RAM IFQ System communications error:  MSG  where:  MSG  is The Java Exception message.

When IFQ reports are submitted on the eLandings system the reports are sent to the NMFS RAM IFQ system and the transaction results are returned so that IFQ receipts can be printed. This message results if the NMFS RAM IFQ system experiences problems or the communications link between the eLanding System and the NMFS RAM IFQ system is unable to handle the transactions properly.

Technical communication problems between component parts of the eLandings system.  More specifically, network problems between the eLandings system and the NMFS IFQ system, or issues with firewalls, proxies, web services configurations, or Oracle packages called by web services.

Contact eLandings support to resolve the problem and/or NMFS Enforcement to complete a manual IFQ landing report. In some cases the system problem can be resolved and the IFQ report can be submitted like normal. In other cases manual IFQ landing reports must be made by phone to the NMFS Enforcement Data Technicians.

1517 ERROR: Estimated weights are not allowed on final reports

Itemized catch line weights may be entered as estimated weights in certain cases when vessels are unloaded by the catch is not weight until processing. Initial landing reports may have estimated weights, but they must be reentered as scale weights before the landing report can be submitted as a final landing report.

At least one itemized catch line has its weight modifier field set to indicate that the weight for the item is estimated rather than a scale weight. Alternately, you entered scale weights for the itemized catch lines, but forgot to reset the weight modifier.

Enter scale weights for all itemized catch line items, and reset the weight modifier to blank.

1518 ERROR: Unsubmitted IFQ reports are not allowed on final Landing Reports

You were trying to submit a final report for a landing and it had unsubmitted IFQ reports.

The landing report had issues with IFQ reporting and the IFQ reports were submitted as manual landings over the phone with the NMFS Data Technicians. Alternately, the landing report has been submitted, the IFQ reports are ready to submit, and you were trying to submit the report as a final landing report before you submitted the IFQ reports.

Submit the IFQ reports if IFQ reporting has not been done via a manual landing. If a manual landing has been done with NMFS Enforcement then remove all unsubmitted IFQ reports.  Use the 'Edit IFQ Reports' page to access the IFQ Reports entry page and then 'Remove Unsubmitted Reports'.

1519 ERROR: Batch Year is required

The batch year is required data and must be entered.

Batch data was being added to a landing report and no batch year was provided.

Enter a valid batch year. Alternately, set default batch information before saving landing report information.

1520 ERROR: Batch Year  YEAR  is invalid where:  YEAR  is The earliest year allowed to be entered.

The batch year entered is not valid. 

The batch year is not numeric, is a year in the future, or is too long ago in the past.

Enter a valid batch year. Alternately, set default batch information before saving landing report information.

1521 ERROR: Batch Office Code is required

The batch office code is required data, and must be entered. Office codes are ADF&G office codes.

Batch data was being added to a landing report and no office code was provided.

Enter a valid office code. Alternately, set default batch information before saving landing report information.

1522 ERROR: Batch Office Code  CODE  is invalid where:  CODE  is The numeric disposition code, indicating what is being done with the catch.

The office code entered is not valid. 

The office code entered is not numeric, is zero or less, or is greater than 99.

Enter a valid office code. Alternately, set default batch information before saving landing report information.

1523 ERROR: Amount is required

The paper fish ticket line item amount was required, and was not provided.

Amount was not entered.

Enter an amount.

1524 ERROR: Amount must be numeric

The paper fish ticket line item amount was not numeric.

Amount was entered with non-digit data. Amount must be a number. It can include decimal points.

Enter a numeric amount.

1525 ERROR: Amount cannot be negative

1526 ERROR: Amount is too large

1527 ERROR: Agency Stat Area  AREA  not in effect for date  DATE  where:  AREA  is The IPHC Regulatory Area. DATE  is The date entered for the announcement.

The statistical area was not valid at the time the report was made. The date of the report is the date of landing for landing reports. For production reports it is the report date.

1528 ERROR: Vehicle License Number should not be entered for  OP_TYPE  operations where:  OP_TYPE  is The name of the operation type.

A vehicle license number are only used for Buying Station operations. 

A vehicle license number was entered for an operation that is not a buying station.

Remove the vehicle license number from the operation data. If the operation is a new operation and it is a buying station change its type to Buying Station.

1529 ERROR:  UNIT_OF_EFFORT  cannot be entered if no stat area is entered where:  UNIT_OF_EFFORT  is The unit of measurement for effort for the gear type, such as number of pot lifts for pot gear.

Effort information must be reported by statistical area. Effort, such as pot lifts for crab, has no meaning with out the provided statistical area.

Effort was entered for the report line, but no statistical area was entered.

Remove the effort entered or enter a statistical area.

1530 ERROR:  UNIT_OF_EFFORT  cannot be entered,  STAT_AREA  is entered in Stat Area Worksheet where:  UNIT_OF_EFFORT  is The unit of measurement for effort for the gear type, such as number of pot lifts for pot gear. STAT_AREA  is The ADF&G Statistical Area identifier.

1531 ERROR: Agency  UNIT_OF_EFFORT  cannot be entered if no stat area is entered where:  UNIT_OF_EFFORT  is The unit of measurement for effort for the gear type, such as number of pot lifts for pot gear.

1532 ERROR: Agency  UNIT_OF_EFFORT  cannot be entered,  STAT_AREA  is entered in agency Stat Area Worksheet where:  UNIT_OF_EFFORT  is The unit of measurement for effort for the gear type, such as number of pot lifts for pot gear. STAT_AREA  is The ADF&G Statistical Area identifier.

1533 ERROR: Lookup ID is required

1534 ERROR: Lookup ID  LOOKUP_ID  is invalid where:  LOOKUP_ID  is The message lookup ID number

1535 ERROR: Species Code  SPECIES_CODE  cannot be used in Production Reports where:  SPECIES_CODE  is The numeric species code.

The species code entered is not setup to be used on production reports.

You entered a line on a production report with for a species that is a valid species, but that is not eligible for production reports. The species code may have been mistyped.

Enter the correct species code or remove the line for the species code from the report.

1536 ERROR: Product Code  PRODUCT_CODE  cannot be used in Production Reports where:  PRODUCT_CODE  is The product code.

The product code entered is not setup to be used on production reports.

You entered a line on a production report with for a product code that is a valid code but that is not eligible for production reports. The product code may have been mistyped.

Enter the correct product code or remove the line for the product code from the report.

1537 ERROR: Comment Code  COMMENT_CODE  is not valid with Condition Code  CONDITION_CODE  where:  COMMENT_CODE  is The comment type identifier. CONDITION_CODE  is The numeric condition code.

1538 ERROR: Comment Code  COMMENT_CODE  is not valid with Disposition Code  DISPOSITION_CODE  where:  COMMENT_CODE  is The comment type identifier. DISPOSITION_CODE  is The numeric disposition code, indicating what is being done with the catch.

1539 ERROR: Comment Code  COMMENT_CODE  is not valid with Species Code  SPECIES_CODE  where:  COMMENT_CODE  is The comment type identifier. SPECIES_CODE  is The numeric species code.

1540 ERROR: Comment Text is required

1541 ERROR: User  USER_ID  is not authorized to view Production Report  REPORT_ID  where:  USER_ID  is The eLandings system user ID. REPORT_ID  is The eLandings landing report ID

1542 ERROR: Statistical Area  STAT_AREA  is entered with  UNITS  on multiple lines for the same species and Fish Ticket where:  STAT_AREA  is The ADF&G Statistical Area identifier. UNITS  is The unit for counting the number of animals in the catch, such as fish or crab.

On the itemized catch lines, effort is not always a required field.  If there is effort information, please report it as the system allows.  For some disposition codes, you will not enter effort, if there are multiple line items with the same species code, stat area, and fish ticket.

Effort was entered for multiple line items with the same species code, stat area, and fish ticket.  The convention is enter the effort for the sold items (i.e. disposition of 60) and do not enter effort for the personal use items (i.e. disposition 95).

Review effort information for all line items, make corrections as necessary.  Leave all dispositions blank for a line items with the same species code, stat area, and fish ticket except for one, usually the sold item.

1543 ERROR: IFQ Reports not allowed on reports with confiscated catch

1544 WARNING:  SPECIES  overages should not be retained for bait where:  SPECIES  is The species code.

1545 WARNING: Some of the search criteria specified cannot be used to search for unsubmitted reports, so unsubmitted reports will not be filtered by this criteria.

The system does not allow unsubmitted reports to be filtered by fish ticket number or port code, so unsubmitted reports will be displayed with this criteria; however, other criteria can be entered to filter these unsubmitted reports.  Reports with a status other than unsubmitted will be filtered by this criteria.

This warning is generated when a fish ticket number or a port code is entered.

No action is necessary for this warning.  If you can not find the report you are searching for, enter more criteria to narrow your results.

1546 ERROR: Product Type  PROD_TYPE  is not allowed for Product Code  PROD_CODE  where:  PROD_TYPE  is The product type, either P for primary or A for ancillary. PROD_CODE  is The product code.

The Product Types:  primary designated product (P) or ancillary secondary product (A) must be compatible with the Product Code.   For example:  Product Type  'P' is valid with Product Code '23 - filets, skinless/bone' because filets are a primary product. Product Type 'A' is valid with Product Code '16 - heads only' because heads are an ancillary product.  Some products like '14 - roe only' can have a Product Type of 'P' or 'A'.

An invalid combination of Product Type and Product Code was input.

Review the Product Type and Product Code and correct one or the other so they are compatible.

1547 ERROR:  UNITS  are required for statistical area  STAT_AREA  where:  UNITS  is The unit for counting the number of animals in the catch, such as fish or crab. STAT_AREA  is The ADF&G Statistical Area identifier.

1548 ERROR:  UNITS  are required for agency statistical area  STAT_AREA  where:  UNITS  is The unit for counting the number of animals in the catch, such as fish or crab. STAT_AREA  is The ADF&G Statistical Area identifier.

1549 ERROR: Agency override statistical area  STAT_AREA  is entered with  UNITS  on multiple lines for the same species where:  STAT_AREA  is The ADF&G Statistical Area identifier. UNITS  is The unit for counting the number of animals in the catch, such as fish or crab.

1550 ERROR: Percent add up to more than 100 percent

1551 ERROR: Percent do not add up to 100 percent

1552 ERROR: All lines must have percent entered

1553 ERROR: Weights add up to more than itemized catch line weight

1554 ERROR: Weights do not add up to itemized catch line weight

1555 ERROR: All lines must have weight entered

1556 ERROR: Pre-printed ticket  TICKET_NUMBER  is invalid where:  TICKET_NUMBER  is The pre-printed ticket number.

The system expects a pre-printed fish ticket number in the form of a leading letter with two digits, a space, and six more following digits. Examples of this are G03 394820, A99 999999, and Z00 000000.  The letter is associated with the type of report, the following two digits are the year of the landing report, and the last two digits is a sequential number.

The pre-printed fish ticket number entered is not in the correct format.

Verify the fish ticket number, and enter the value in the correct format.

1557 ERROR: No CFEC Permits found that match search criteria

1558 ERROR: No Vessels found that match search criteria

1559 ERROR: CFEC permit holder name is required

1560 ERROR: CFEC permit holder name cannot be longer than  MAX_SIZE  characters where:  MAX_SIZE  is The maximum number of characters that can be stored in the database for the field.

1561 ERROR: CFEC serial number is required

1562 ERROR: CFEC serial number  SERIAL_NUMBER  is invalid where:  SERIAL_NUMBER  is The serial number on the CFEC permit

1563 ERROR: Vessel name is required

1564 ERROR: Vessel name cannot be longer than  MAX_SIZE  characters where:  MAX_SIZE  is The maximum number of characters that can be stored in the database for the field.

1565 ERROR: Search criteria must be entered

Search criteria is required to perform a search on this panel.

The search criteria was omitted.

Enter search criteria and try again.

1566 ERROR: Search returned too many records to display. Refine search criteria to limit results

1567 ERROR: No data found that match search criteria

No information was found.

The search criteria does not match any information in the database.

Verify the search criteria used and try again or try different criteria.

1568 ERROR: Message ID  MSG_ID  is invalid where:  MSG_ID  is The unique message identifier.

1569 ERROR: Message ID is required

1570 ERROR: Message severity is required

1571 ERROR: Message severity  SEVERITY  is invalid where:  SEVERITY  is The message severity, S for System Error, E for error, W for warning, or I for information

1572 ERROR: Message text is required

1573 ERROR: Message description is too long

1574 ERROR: Message probable causes is too long

1575 ERROR: Message corrective action is too long

1576 ERROR: Message substitution tag is required

1577 ERROR: Message substitution tag is too long

1578 ERROR: Message substitution tag  TAG  is invalid where:  TAG  is The substitution tag that will be replace in the message data with the actual value

1579 ERROR: Message substitution tag description is require

1580 ERROR: Message substitution tag description is too long

1581 ERROR: Message text is too long

1582 ERROR: Message probable causes is required

1583 ERROR: Message corrective action is required

1584 ERROR: Message description is required

1585 ERROR: Message constant is required

1586 ERROR: Message constant  NAME  is invalid where:  NAME  is The constant name.

1587 ERROR: Message constant is too long

1588 ERROR: Announcement date is required

1589 ERROR: Announcement date  DATE  is invalid where:  DATE  is The date entered for the announcement.

1590 ERROR: Announcement expiration date is required

1591 ERROR: Announcement expiration date  DATE  is invalid where:  DATE  is The date entered for the announcement.

1592 ERROR: Announcement expiration date requires a four digit year

1593 ERROR: Announcement date requires a four digit year

1594 ERROR: The text of the announcement is required

1595 ERROR: The text of the announcement is too long

1596 ERROR: Announcement title is required

1597 ERROR: Announcement title is too long

1598 ERROR: Announcement ID  ID  is invalid where:  ID  is The unique numeric identifier for the operation.

1599 ERROR: Announcement ID is required

1600 ERROR: At least one announcement method is required

1601 ERROR: Announcement date cannot be after expiration date

1602 ERROR: Announcement expiration date cannot be in the past

1603 ERROR: Interim value for ADF&G Vessel Number must be replaced before Final Report can be submitted

1604 ERROR: Interim value for CFEC Permit Number must be replaced before Final Report can be submitted

1605 ERROR: Interim value for Species Code must be replaced before Final Report can be submitted

1606 INFO:  NUMBER  Landing Reports found that match search criteria where:  NUMBER  is The number of reports found.

The shown number of landing reports were found that match the supplied search criteria.

1607 INFO: One Landing Report found that matches search criteria

One landing report was found that matches the supplied search criteria.

1608 INFO:  NUMBER  Production Reports found that match search criteria where:  NUMBER  is The number of reports found.

The shown number of production reports found match the supplied search criteria.

1609 INFO: One Production Report found that matches search criteria

One production report was found that matches the supplied search criteria.

1610 WARNING: Date range  FROM  -  TO  is invalid, from date is after to date where:  FROM  is The start of the date range. TO  is The end of the date range.

1611 ERROR: Password is invalid

1612 ERROR: Processor Code does not match Processor Code on report

1613 ERROR: Vessel ADF&G Number does not match ADF&G Number on report

1614 ERROR: Port Code does not match Port Code on report

1615 ERROR: Date of Landing does not match Date of Landing on report

1616 ERROR: Federal Permit Number does not match Federal Permit Number on report

1617 ERROR: Date of Report does not match Date of Report on report

1618 INFO: Unsubmitted Landing Report  REPORT_ID  deleted where:  REPORT_ID  is The eLandings landing report ID

The displayed unsubmitted landing report was deleted.

1619 INFO: Unsubmitted Production Report  REPORT_ID  deleted where:  REPORT_ID  is The eLandings landing report ID

The displayed unsubmitted production report was deleted.

1620 ERROR: Query ID is required

1621 ERROR: Query Name is required

1622 ERROR: Query Output Format is required

1623 ERROR: Query Output Format  FORMAT  is invalid where:  FORMAT  is The output file format.

1624 ERROR: Query XML Template is required

1625 ERROR: Query Parameter  PARM  is required where:  PARM  is The query parameter name.

1626 ERROR: Query Parameter  PARM  is invalid,  VALUE  could not be converted to  TYPE  where:  PARM  is The query parameter name. VALUE  is The query parameter value input. TYPE  is The operation type code.

1627 ERROR: Query  ID  not found where:  ID  is The unique numeric identifier for the operation.

1628 ERROR: Query ID  ID  is invalid where:  ID  is The unique numeric identifier for the operation.

1629 ERROR: Query  ID  is not a processor query where:  ID  is The unique numeric identifier for the operation.

1630 ERROR: Query Name is too short

1631 ERROR: Query Name is too long

1632 ERROR: Query Name  NAME  is invalid where:  NAME  is The constant name.

1633 ERROR: Query Jasper Reports XML Template is too long

1634 ERROR: Jasper Reports Error:  MSG  where:  MSG  is The Java Exception message.

1635 ERROR:  NAME  User Security Role required for this function where:  NAME  is The constant name.

1636 ERROR: Comment Text is not allowed for comment code  CODE  where:  CODE  is The numeric disposition code, indicating what is being done with the catch.

1637 ERROR: Species  SPECIES  cannot be sold on a Crab Landing Report where:  SPECIES  is The species code.

Only crab can be sold on a crab landing report. Non-crab species may be entered in the itemized catch as discards or other non-sold dispositions, but sold catch should always be reported on a landing report or fish ticket of the appropriate type. The exception is cod, or other fish sold as bait.

A species that is not a crab species was entered on the crab landing report as sold.

Verify that the species was landed.  Contact the local office of ADF&G or NMFS enforcement regarding allowable purchase of this species.

1638 ERROR: Species  SPECIES  cannot be sold on a Groundfish Landing Report where:  SPECIES  is The species code.

Only groundfish can be sold on a groundfish landing report. Non-groundfish species may be entered in the itemized catch as discards or other non-sold dispositions, but sold catch should always be reported on a landing report or fish ticket of the appropriate type.

A species that is not a groundfish species was entered on the groundfish landing report as sold

Verify this species was landed.  Contact the local office of ADF&G or NMFS enforcement regarding allowable purchase of this species.

1639 ERROR: Quantity is required

1640 ERROR: Quantity must be numeric, without a decimal point

1641 ERROR: Quantity is too small

1642 ERROR: Quantity cannot be more than  MAX_QTY  where:  MAX_QTY  is The maximum value.

1645 ERROR: Fish Ticket Number  FT_NUM  is issued to an operation for which user  USERID  is not authorized where:  FT_NUM  is The ADF&G fish ticket id number. USERID  is The eLandings system user ID.

1646 ERROR: Fish Ticket Number  FT_NUM  is not available for import. It is not issued or is already used where:  FT_NUM  is The ADF&G fish ticket id number.

1648 ERROR: Cannot have both pre-issued importable Fish Ticket numbers and regular Fish Ticket numbers in the same landing report

1649 ERROR: A grading/pricing template already exists for species  SPECIES , condition  CONDITION  where:  SPECIES  is The species code. CONDITION  is The numeric condition code.

1650 ERROR: Either Size/Grade or Price is required 

1651 ERROR: At least one grading and pricing item is required 

1652 INFO: Please Enter Grading and Pricing Template Items

Please enter grading and pricing template items.

1653 INFO: Edit Grading and Pricing Template

Please edit the grading and pricing template.

1654 ERROR:  UNIT_OF_EFFORT  must be numeric, without a decimal point where:  UNIT_OF_EFFORT  is The unit of measurement for effort for the gear type, such as number of pot lifts for pot gear.

1655 ERROR: Number of  UNITS  must be numeric, without a decimal point where:  UNITS  is The unit for counting the number of animals in the catch, such as fish or crab.

1656 WARNING: A landing report already exists with the same vessel number, processor code, and date of landing

An identical landing has already been entered.  Only one unique landing is allowed based on the vessel, processor and landing date.

There has been a data entry error which happens to match a previous landing.  Or, this landing was previously input and could be submitted or saved as an un-submitted report.

Review the landing information for accuracy, particularly the date of landing. If data is accurate, then:  a) cancel this report, return to the Reports Menu, find the original report and complete it.  Or b) Save the Report, Ignoring Warnings

1657 INFO: Please review the messages in the Status column of the IFQ Reports section below for NMFS ID  NMFS_ID  and IFQ Permit Number  IFQ_NUMBER  where:  NMFS_ID  is The NMFS ID number for persons involved in IFQ fisheries. IFQ_NUMBER  is The IFQ report sequence number.

Please review the messages in the status column of the IFQ reports section below for the shown NMFS ID and the shown IFQ permit number.

1658 ERROR: A landing report already exists for Seq. Ticket Number  SEQ_NUMBER  and Batch  BATCH_INFO  where:  SEQ_NUMBER  is The sequence number stamped on the fish ticket when received by ADF&G. BATCH_INFO  is The batch year, office code, and batch number. FT_NUM  is The ADF&G fish ticket id number.

1659 ERROR: Special Area  SPECIAL_AREA  is not valid with Federal Reporting Area  FED_AREA . where:  SPECIAL_AREA  is The 5 character trawl gear Special Area. FED_AREA  is The 3 digit Federal Reporting Area.

1660 ERROR: Special Area  SPECIAL_AREA  is not valid with Gear Code  GEAR_CODE . where:  SPECIAL_AREA  is The 5 character trawl gear Special Area. GEAR_CODE  is The numeric gear code.

1661 INFO: No IFQ Reports were generated. Please review IFQ permit and species information.

No IFQ reports were generated.  Please review the IFQ permit and species information.

1664 ERROR: Species Code  SPECIES_CODE  cannot be used on a production line. where:  SPECIES_CODE  is The numeric species code.

The species code entered is invalid on a detail line of a production report.

An invalid species code was input.

Review the species code and correct.

1665 ERROR: Disposition code  CODE  cannot be used on a discard line. where:  CODE  is The numeric disposition code, indicating what is being done with the catch.

1666 ERROR: Product Code  PRODUCT_CODE  is not valid for species  SPECIES_CODE  where:  PRODUCT_CODE  is The product code. SPECIES_CODE  is The numeric species code.

1667 ERROR: Multiple discard lines for species  SPECIES_CODE  and disposition  DISPOSITION_CODE  where:  SPECIES_CODE  is The numeric species code. DISPOSITION_CODE  is The numeric disposition code, indicating what is being done with the catch.

1669 ERROR: Sold Condition Code must be the same as the Itemized Catch Condition Code for non-sold lines

1670 ERROR: Grading/Pricing weight must be the same as the Itemized Catch weight for non-sold lines

1671 ERROR: Price is not allowed on grading/pricing lines for non-sold itemized catch lines

1672 ERROR: Size/Grade is not allowed on grading/pricing lines for non-sold itemized catch lines

1673 WARNING: IFQ permits should be entered when management program is IFQ

1674 ERROR: Only IFQ permits for halibut are allowed when management program is CDQ

1676 ERROR: Sequential ticket number  SEQ_NUM  entered multiple times where:  SEQ_NUM  is The stamped sequential ticket number

1677 ERROR: At least one grading/pricing product type must be primary

1678 ERROR: No grading/pricing product types may be primary

1680 ERROR: Return Receipt already processed

1681 ERROR: Report file  FILE  on workstation, could not be read where:  FILE  is The user file name on the workstation

1683 INFO: Report file  FILE  found in return receipt but not found on workstation, and will be added where:  FILE  is The user file name on the workstation

1684 INFO: Processing return receipt file  FILE  where:  FILE  is The user file name on the workstation

1685 WARNING: Report file  FILE  was updated and resent. Expect another return receipt for the update where:  FILE  is The user file name on the workstation

1686 INFO: Report file  FILE  was resent. Expect another return receipt where:  FILE  is The user file name on the workstation

1687 ERROR: Report file  FILE  was updated more recently than the version in the return receipt. Please retransmit where:  FILE  is The user file name on the workstation

1688 INFO: Report file  FILE  on workstation was not marked as sent, return receipt version will be saved where:  FILE  is The user file name on the workstation

1691 INFO: User file  FILE  found in return receipt but not found on workstation, and will be added where:  FILE  is The user file name on the workstation

1692 ERROR: Return receipt user file  FILE  contained only messages where:  FILE  is The user file name on the workstation

1694 INFO:  NUMBER  report numbers received where:  NUMBER  is The number of reports found.

1695 INFO:  NUMBER  fish ticket numbers received where:  NUMBER  is The number of reports found.

1696 ERROR: A report that has been sent by email cannot be updated until the return receipt has been processed

1698 ERROR: User cannot be both an Admin and a Read-Only user

1699 ERROR: IFQ Area/Fishery is required.

1700 ERROR: IFQ Area/Fishery  AREA  is not valid. where:  AREA  is The IPHC Regulatory Area.

1701 ERROR: IFQ Area/Fishery  AREA  is not valid for Species  SPECIES . where:  AREA  is The IPHC Regulatory Area. SPECIES  is The species code.

1702 ERROR: Pounds to max-out permit can only be entered here if Area/Fishery has been entered

1703 ERROR: NMFS ID  NMFS_ID , IFQ Permit  IFQ_PERMIT_NUMBER , Species  SPECIES  combination is entered both with and without Area/Fishery where:  NMFS_ID  is The NMFS ID number for persons involved in IFQ fisheries. IFQ_PERMIT_NUMBER  is The NMFS Restricted Access Management Division IFQ permit number. SPECIES  is The species code.

The IFQ permit and species code, on the IFQ Permit Worksheet, can match more than once for each NMFS ID only if each has a different Area/Fishery.

1704 ERROR: NMFS ID  NMFS_ID , IFQ Permit  IFQ_PERMIT_NUMBER , Species  SPECIES , IPQ Permit  IPQ_PERMIT_NUMBER  combination is entered both with and without Area/Fishery where:  NMFS_ID  is The NMFS ID number for persons involved in IFQ fisheries. IFQ_PERMIT_NUMBER  is The NMFS Restricted Access Management Division IFQ permit number. SPECIES  is The species code. IPQ_PERMIT_NUMBER  is The NMFS Restricted Access Management Division Processor quota share permit number.

The IFQ permit, species code, and the IPQ permit, on the IFQ Permit Worksheet, can match more than once for each NMFS ID only if each has a different Area/Fishery.

1705 ERROR: Area/Fishery  AREA  in IFQ permits for species  SPECIES  has no itemized catch where:  AREA  is The IPHC Regulatory Area. SPECIES  is The species code.

1706 ERROR: Area/Fishery  AREA  for species  SPECIES  has itemized catch, but no IFQ permit(s) where:  AREA  is The IPHC Regulatory Area. SPECIES  is The species code.

1707 ERROR: Part or all of line item  ITEM_NUM  cannot be allocated to a CFEC permit where:  ITEM_NUM  is The itemized catch line item number.

The automatic allocation of itemized catch to CFEC permits has many complicated business rule to insure that the right weights and area/fisheries are assigned to the right permits, to allow IFQ reports to be generated according to the area/fisheries and max out pounds specified on the IFQ permit worksheet. The automated allocation logic was not able to completely allocate the indicated itemized catch line.

This error can be caused by itemized catch and statistical area data that cannot be divided up without violating the area/fishery and max out pounds requests entered on the IFQ permit worksheet. This might be because all of the IFQ permits for one or more of the CFEC permits have a particular area/fishery entered and one or more of the statistical areas on the statistical area worksheet do not have that area/fishery. It can also be causes by situations where the program cannot figure out the right way to divide up the itemized catch line, particularly if the statistical areas involved have ambiguous IPHC areas.

1708 ERROR: A line item assigned to Fish Ticket  FT_NUM  does not fit the area/fishery and max out pounds constraints entered on the IFQ Permit Worksheet for the CFEC permit where:  FT_NUM  is The ADF&G fish ticket id number.

An itemized catch line has been assigned to the specified fish ticket, either by the user or by the automated allocation program. However, the weights and area/fisheries for the line cannot be reconciled with the area/fisheries and max out pounds entered on the IFQ Permit Worksheet.

This error can be caused by itemized catch and statistical area data that cannot be divided up without violating the area/fishery and max out pounds requests entered on the IFQ permit worksheet. It can also be causes by situations where the program cannot figure out the right way to divide up the itemized catch line, particularly if the statistical areas involved have ambiguous IPHC areas.

1709 ERROR: Max out pounds for Area/Fishery  AREA  for Fish Ticket  FT_NUM  cannot be satisfied where:  AREA  is The IPHC Regulatory Area. FT_NUM  is The ADF&G fish ticket id number.

The automatic allocation of itemized catch to CFEC permits has many complicated business rule to insure that the right weights and area/fisheries are assigned to the right permits, to allow IFQ reports to be generated according to the area/fisheries and max out pounds specified on the IFQ permit worksheet. The automated allocation logic was not able to itemized catch line weight to satisfy the max out pounds specified.

This error can be caused by specifying more max out pounds than there are pounds on itemized catch lines that can be assigned to the fish ticket and area/fishery. It can also be causes by situations where the program cannot figure out the right way to divide up the itemized catch line, particularly if the statistical areas involved have ambiguous IPHC areas.

1710 SYSTEM ERROR: Total line item landed weight was  BEFORE_WT  before allocating to permits and  AFTER_WT  afterwards where:  BEFORE_WT  is The weight before allocations. AFTER_WT  is The weight after allocations.

The sum of the landed weights of all the itemized catch lines was one amount before splitting lines to assign fish ticket, and a different amount after the splits.

This error can only be caused by an internal system error.

1711 ERROR: XML Schema Version number is required

The XML Schema Version number identifies the version of the XML file format for import and export XML files for landing and production reports, and other eLandings data excehanged as XML files. It is required input.

1712 ERROR: XML Schema Version number must be numeric

The XML Schema Version number identifies the version of the XML file format for import and export XML files for landing and production reports, and other eLandings data excehanged as XML files. It must be numeric. A non-numeric value does not identify any file format.

1713 ERROR: XML Schema Version  NUM  is invalid where:  NUM  is The number of fish ticket numbers that have been issued but not imported yet.

The XML Schema Version number identifies the version of the XML file format for import and export XML files for landing and production reports, and other eLandings data excehanged as XML files. It must a version number that identifies a valid file format. eLandings production support personnel can provide information on valid schema version numbers and the file formats they represent.

1714 WARNING: Max out pounds  REQ_LBS  requested for NMFS ID/IFQ Permit  NMFS_ID_PERMIT  Area/Fishery  AREA  not honored, actual pounds is  LBS  where:  NMFS_ID_PERMIT  is The NMFS ID and IFQ Permit number. AREA  is The IPHC Regulatory Area. REQ_LBS  is The max out pounds requested for the permit. LBS  is The actual number of pounds on the IFQ reports.

The max out pounds requested for the IFQ permit and Area/Fishery does not match the actual pounds on the IFQ report(s). Pounds for max out are in IFQ quota management units, which is pounds in condition 05 for halibut and round pounds for other species.

This situation can be caused by problems in the automatic permit allocation and IFQ report generation process. Permit allocation is quite complicated, and some combinations of permits, area/fisheries, max out pounds, and itemized catch can prevent the automatic generation from completing successfully. This situation can also be caused by user input for IFQ reports.

1715 WARNING: Max out pounds  REQ_LBS  requested for NMFS ID/IFQ Permit/IPQ Permit  NMFS_ID_PERMIT  Area/Fishery  AREA  not honored, actual pounds is  LBS  where:  NMFS_ID_PERMIT  is The NMFS ID and IFQ Permit number. AREA  is The IPHC Regulatory Area. REQ_LBS  is The max out pounds requested for the permit. LBS  is The actual number of pounds on the IFQ reports.

The max out pounds requested for the IFQ permit and Area/Fishery does not match the actual pounds on the IFQ report(s). Pounds for max out are in IFQ quota management units, which is pounds in condition 05 for halibut and round pounds for other species.

This situation can be caused by problems in the automatic permit allocation and IFQ report generation process. Permit allocation is quite complicated, and some combinations of permits, area/fisheries, max out pounds, and itemized catch can prevent the automatic generation from completing successfully. This situation can also be caused by user input for IFQ reports.

1716 ERROR: The Statistical Area Worksheet cannot be used for this Landing Report. Please enter statistical areas on Itemized Catch lines

Fishery managers have determined that in some fisheries the statistical area worksheet does not provide adequate data. In these cases the statistical area and effort data must be input on the itemized catch lines. 

Statistical area data was entered in the statistical area worksheet on a landing report were the statistical area worksheet is not allowed.

1717 ERROR: Total sold weight for species  SPECIES  on Fish Ticket  FT_NUM  does not match sold weight on IFQ Report for stat area  STAT_AREA  where:  FT_NUM  is The ADF&G fish ticket id number. SPECIES  is The species code. STAT_AREA  is The ADF&G Statistical Area identifier.

1718 ERROR: Total retained weight for species  SPECIES  on Fish Ticket  FT_NUM  does not match retained weight on IFQ Report for stat area  STAT_AREA  where:  FT_NUM  is The ADF&G fish ticket id number. SPECIES  is The species code. STAT_AREA  is The ADF&G Statistical Area identifier.

1719 ERROR: Total deadloss weight for species  SPECIES  on Fish Ticket  FT_NUM  does not match deadloss weight on IFQ Report for stat area  STAT_AREA  where:  FT_NUM  is The ADF&G fish ticket id number. SPECIES  is The species code. STAT_AREA  is The ADF&G Statistical Area identifier.

1720 ERROR: Due to IFQ Permit allocation requirements, stat area is required on Itemized Catch lines for species  SPECIES  where:  SPECIES  is The species code.

1721 ERROR: Species  SPECIES  is not in effect for date  DATE  where:  SPECIES  is The species code. DATE  is The date entered for the announcement.

The species code was not valid at the time the report was made. The date of the report is the date of landing for landing reports. For production reports it is the report date.

1722 ERROR: Management Program  MGMTPGM  is not in effect for date  DATE  where:  MGMTPGM  is The Management Program. DATE  is The date entered for the announcement.

The management program was not valid at the time the report was made. The date of the report is the date of landing for landing reports. For production reports it is the report date.

1723 ERROR: Management Program ID  MANAGEMENT_PROGRAM_ID  is not in effect for date  DATE  where:  MANAGEMENT_PROGRAM_ID  is The fisher's identification number for the management program under which the fishing was conducted. DATE  is The date entered for the announcement.

The management program ID was not valid at the time the report was made. The date of the report is the date of landing for landing reports. For production reports it is the report date.

1724 ERROR: CFEC Fishery  FISHERY  is not in effect for date  DATE  where:  FISHERY  is The CFEC fishery code that is on the CFEC permit card. DATE  is The date entered for the announcement.

The CFEC fishery code was not valid at the time the report was made. The date of the report is the date of landing for landing reports. For production reports it is the report date.

1725 ERROR: Condition Code  CODE  is not in effect for date  DATE  where:  CODE  is The numeric disposition code, indicating what is being done with the catch. DATE  is The date entered for the announcement.

The condition code was not valid at the time the report was made. The date of the report is the date of landing for landing reports. For production reports it is the report date.

1726 ERROR: Disposition Code  CODE  is not in effect for date  DATE  where:  CODE  is The numeric disposition code, indicating what is being done with the catch. DATE  is The date entered for the announcement.

The disposition code was not valid at the time the report was made. The date of the report is the date of landing for landing reports. For production reports it is the report date.

1727 ERROR: FMP Area  AREA  is not in effect for date  DATE  where:  AREA  is The IPHC Regulatory Area. DATE  is The date entered for the announcement.

The FMP area was not valid at the time the report was made. The date of the report is the date of landing for landing reports. For production reports it is the report date.

1728 ERROR: Gear Code  CODE  is not in effect for date  DATE  where:  CODE  is The numeric disposition code, indicating what is being done with the catch. DATE  is The date entered for the announcement.

The gear code was not valid at the time the report was made. The date of the report is the date of landing for landing reports. For production reports it is the report date.

1729 ERROR: Harvest Code  CODE  is not in effect for date  DATE  where:  CODE  is The numeric disposition code, indicating what is being done with the catch. DATE  is The date entered for the announcement.

The harvest was not valid at the time the report was made. The date of the report is the date of landing for landing reports. For production reports it is the report date.

1731 ERROR: Operation Type  TYPE  is not in effect for date  DATE  where:  TYPE  is The operation type code. DATE  is The date entered for the announcement.

The operation type was not valid at the time the report was made. The date of the report is the date of landing for landing reports. For production reports it is the report date.

1732 ERROR: Port Code  CODE  is not in effect for date  DATE  where:  CODE  is The numeric disposition code, indicating what is being done with the catch. DATE  is The date entered for the announcement.

The port code was not valid at the time the report was made. The date of the report is the date of landing for landing reports. For production reports it is the report date.

1733 ERROR: Area/Fishery  AREA  is not in effect for date  DATE  where:  AREA  is The IPHC Regulatory Area. DATE  is The date entered for the announcement.

The IFQ area/fishery was not valid at the time the report was made. The date of the report is the date of landing for landing reports. For production reports it is the report date.

1734 ERROR: Statistical Area  AREA  is not in effect for date  DATE  where:  AREA  is The IPHC Regulatory Area. DATE  is The date entered for the announcement.

The statistical area was not valid at the time the report was made. The date of the report is the date of landing for landing reports. For production reports it is the report date.

1735 ERROR: Salmon/Shellfish Statistical Area  AREA  not valid for groundfish where:  AREA  is The IPHC Regulatory Area.

5 digit Salmon/Shellfish statistical areas cannot be used on groundfish landing reports or groundfish lines on salmon troll reports. 6 digit groundfish statistical areas should be used.

1736 ERROR: Salmon/Shellfish Statistical Area  AREA  not valid on crab reports west of Cape Suckling where:  AREA  is The IPHC Regulatory Area.

5 digit Salmon/Shellfish statistical areas cannot be used to report crab fishing west of Cape Suckling. 6 digit groundfish statistical areas should be used.

1737 ERROR: Groundfish Statistical Area  AREA  not valid on crab reports east of Cape Suckling where:  AREA  is The IPHC Regulatory Area.

6 digit groundfish statistical areas cannot be used to report crab fishing east of Cape Suckling. 5 digit Salmon/Shellfish statistical areas should be used.

1738 ERROR: Salmon/Shellfish Statistical Area  AREA  not valid for production reports where:  AREA  is The IPHC Regulatory Area.

5 digit Salmon/Shellfish statistical areas cannot be used on groundfish landing reports or production reports. 6 digit groundfish statistical areas should be used.

1739 WARNING: Out of State flag is set, but port code is in Alaska

The out of state flag indicates a landing outside of Alaska, but the port of landing is in Alaska.

The out of state flag does not make sense for the port of landing.

Reset the flag.

1741 ERROR: Tender Vessel ADF&G Number is required

The ADF&G number of the tender is required information and must be entered. ADF&G vessel numbers are five digit numbers issued by the Commercial Fisheries Entry Commission (CFEC).

Vessel ADF&G numbers are required for at-sea and tender operation setups, landing reports, and at-sea production reports.

Enter a valid ADF&G vessel number. Leading zeroes are not required, but may be entered.

1742 ERROR: Tender Vessel ADF&G Number  VESSEL_NUM  is not valid where:  VESSEL_NUM  is The ADF&G Vessel number, issued by CFEC.

The tender ADF&G vessel number entered was not found in the database.

The vessel ADF&G numbers are stored in the database. They are issued by CFEC, and are updated daily. The vessel ADF&G number can be at most 5 characters.

Enter a valid ADF&G vessel number. Leading zeroes are not required, but may be entered. If you are sure the vessel number is the correct one for the tender, contact eLandings system support.

1743 ERROR: Tender Vessel ADF&G Number cannot be the same as the delivering vessel ADF&G Number

The tender vessel ADF&G number entered was the same as the ADF&G Vessel number.

The Vessel ADF&G Number should be the vessel number of the catcher vessel. The Tender Vessel ADF&G Number should be the vessel number of the tender that took delivery from the catcher vessel. A vessel cannot deliver to itself, if it delivering its own catch it is not involved in tendering, even though it may act as a tender at other times.

If the tender took delivery from a catcher vessel enter that vessel's ADF&G vessel number as the ADF&G Vessel Number and the tender's ADF&G vessel number as the Tender ADF&G Vessel Number. If the vessel was doing its own fishing (i.e. not acting as a tender) don't enter anything in the Tender ADF&G Vessel Number, even if the vessel acts as a tender at other times.

1744 ERROR: Pre-printed ticket cannot start with 'I'

The system expects a pre-printed fish ticket number in the form of a leading letter with two digits, a space, and six more following digits. Examples of this are G03 394820, A99 999999, and Z00 000000.  The letter is associated with the type of report, the following two digits are the year of the landing report, and the last two digits is a sequential number.  A leader letter of 'I' stands for interim/import, and is reserved for landing reports imported through the eLandings website.

The pre-printed fish ticket entered starts with the letter 'I'.

Verify the fish ticket number, and enter the correct value.  The leading letter of the type of landing report will be the correct letter to enter.  For example, G is for groundfish and C is for crab. If the pre-printed fish ticket number starts with GI or CI the letter Z should be used.

1745 ERROR: Management Program must be  MGMT_PGMS  where:  MGMT_PGMS  is The allowable Management Program(s).

The management program must be one of the management programs specified.

This message is given when the business rules determine that only certain management programs are allowed for the reported data.

Change the Management Program to one of the allowable values. If you do not want to change the Management Program review all data especially gear code and CFEC permit fisheries, and change as needed.

1746 ERROR: Install Directory is required

1747 ERROR: Install directory name is too long

The directory provided is too long. Excessively long directory path names are commonly used in cracking attempts, extra long directories paths should not be required for eLandings.

1757 ERROR: Installation type is required

1758 ERROR: Installation type is too long

1768 ERROR: Transmit type is required

1769 ERROR: Transmit type is too long

1776 ERROR: Cannot write to directory  DIR  where:  DIR  is The directory path name.

1777 ERROR:  DIR  is not a directory where:  DIR  is The directory path name.

1780 WARNING: Production Report  REPORT  already exists for the same header information where:  REPORT  is The production report ID.

Another report was found with the same Federal Permit Number, Vessel ADF&G Number, Processor Code, Management Program, Port Code, Gear Code, Federal Reporting Area, Special Area, and Report Date.

1781 WARNING: The Federal Permit Number  FED_PERMIT  and ADF&G Number  ADFG_NUM  combination does not match any registered operation where:  FED_PERMIT  is The Federal Permit Number. ADFG_NUM  is The ADF&G Vessel number, issued by CFEC.

The Federal Permit Number and Vessel ADF&G Number combination on the report does not match any of the operations where the user is authorized

1782 ERROR: Trip event is required

1783 ERROR: Trip event  CODE  is invalid where:  CODE  is The numeric disposition code, indicating what is being done with the catch.

1784 ERROR: Trip event  CODE  not in effect for date  DATE  where:  CODE  is The numeric disposition code, indicating what is being done with the catch. DATE  is The date entered for the announcement.

1785 ERROR: Temperature is required

1786 ERROR: Temperature must be numeric

1787 ERROR: Temperature  TEMPERATURE  is too low where:  TEMPERATURE  is A fish temperature

1788 ERROR: Temperature  TEMPERATURE  is too high where:  TEMPERATURE  is A fish temperature

1789 ERROR: Groundfish Statistical Area  AREA  not valid for salmon where:  AREA  is The IPHC Regulatory Area.

6 digit Groundfish statistical areas cannot be used on salmon landing reports or salmon lines on salmon troll reports. 5 digit Salmon/Shellfish statistical areas should be used.

1790 WARNING: Directory  DIR  does not exist, and will be created where:  DIR  is The directory path name.

The directory specified does not exist. If the warning is ignored it will be created as a new directory.

1791 ERROR: Chill Water Temperature is required

1792 ERROR: Chill Water Temperature must be numeric

1793 ERROR: Chill Water Temperature  TEMPERATURE  is too low where:  TEMPERATURE  is A fish temperature

1794 ERROR: Chill Water Temperature  TEMPERATURE  is too high where:  TEMPERATURE  is A fish temperature

1795 WARNING: Chill Water Temperature  TEMPERATURE  is low where:  TEMPERATURE  is A fish temperature

1796 WARNING: Chill Water Temperature  TEMPERATURE  is high where:  TEMPERATURE  is A fish temperature

1797 ERROR: Report Date range is required

1798 ERROR: Report Date range is invalid

1799 ERROR: Update Date range is required

1800 ERROR: Update Date range is invalid

1801 ERROR: Logging Level is required

Logging level must be provided, and must be a valid value

1802 ERROR: Logging Level must be numeric

1803 ERROR: Logging Level cannot be negative

The logging level must be within the range used in the system. Values outside the valid range have no meaning to the system.

1804 ERROR: Logging Level cannot be greater than  LEVEL  where:  LEVEL  is The maximum Logging Level.

The logging level must be within the range used in the system. Values outside the valid range have no meaning to the system.

1805 INFO:  MSG  where:  MSG  is The Java Exception message.

This message is used to provide general information about activities on the system.

1817 ERROR: Period is required

Period is a fishing time indicator defined and determined by fishery managers. The period is a two digit numeric code, with leading zeros.

1818 ERROR: Period must be numeric

Period is a fishing time indicator defined and determined by fishery managers. The period is a two digit numeric code, with leading zeros.

1819 ERROR: Chill type is required

Chill (Refrigeration) Type specify the cooling technique used on a fishing / tender vessel to keep fish cool. Types include: ICE = ice, SLH = Slush ice, RSW = Refrigerated Seawater system, CSW = Circulating Seawater system, FAZ = Frozen at sea, and LIV = Fish delivered live. The chill (refrigeration) type is related to the fish temperature.

1820 ERROR: Chill type is invalid

Chill (Refrigeration) Type specify the cooling technique used on a fishing / tender vessel to keep fish cool. Types include: ICE = ice, SLH = Slush ice, RSW = Refrigerated Seawater system, CSW = Circulating Seawater system, FAZ = Frozen at sea, and LIV = Fish delivered live. The chill (refrigeration) type is related to the fish temperature.

1821 ERROR: Location code is required

The location code is used by agency staff to designate a region within a statistical area. These designations; their creation, definition, maintenance and use, are field office specific. Location codes are numeric and range from 00-99 in value. The definitions, interpretations and uses of these location codes are not currently available in the eLandings system at this time.

1822 ERROR: Location code must be numeric

The location code is used by agency staff to designate a region within a statistical area. These designations; their creation, definition, maintenance and use, are field office specific. Location codes are numeric and range from 00-99 in value. The definitions, interpretations and uses of these location codes are not currently available in the eLandings system at this time.

1823 INFO: Return receipt sent to  EMAIL  where:  EMAIL  is The entered email address.

A return receipt file was emailed to the specified email address.

1824 ERROR: Magnetic Stripe data not in valid format

The magnetic stripe data was read in, but it was not in the proper format.

1825 ERROR: Total sold weight on fish ticket  FISH_TICKET_NUMBER  does not match total sold weight on IFQ reports for species  SPECIES_CODE  where:  FISH_TICKET_NUMBER  is The ADF&G fish ticket id number. SPECIES_CODE  is The numeric species code.

1826 ERROR: Total retained weight on fish ticket  FISH_TICKET_NUMBER  does not match total retained weight on IFQ reports for species  SPECIES_CODE  where:  FISH_TICKET_NUMBER  is The ADF&G fish ticket id number. SPECIES_CODE  is The numeric species code.

1827 ERROR: Total deadloss weight on fish ticket  FISH_TICKET_NUMBER  does not match total deadloss weight on IFQ reports for species  SPECIES_CODE  where:  FISH_TICKET_NUMBER  is The ADF&G fish ticket id number. SPECIES_CODE  is The numeric species code.

1828 ERROR: Statistical area  STAT_AREA  does not map to Federal Reporting Area  FED_AREA  for report, maps to  FED_AREAS  where:  STAT_AREA  is The ADF&G Statistical Area identifier. FED_AREA  is The 3 digit Federal Reporting Area. FED_AREAS  is The federal reporting areas for the stat area.

1829 ERROR: Only at-sea operations can be used when creating consolidated landing reports

1830 ERROR: Only Catcher/Processor operations can create consolidated landing reports

1831 ERROR: CFEC Permit is required for management program  MGMT_PGM  where:  MGMT_PGM  is The management program.

1832 ERROR: No production reports with production or discards found for date range

1833 ERROR: At least one statistical area must be entered

1834 ERROR: Manual IFQ Report flag cannot be set if the landing report has IFQ reports

1837 ERROR: User  USER_ID  is not authorized to access reports for the Registered Buyer Number  REG_BUYER_NUM  where:  USER_ID  is The eLandings system user ID. REG_BUYER_NUM  is The NMFS Restricted Access Management Division registered buyer number for halibut and sablefish IFQ.

1838 ERROR: User  USER_ID  is not authorized to access reports for the RCR Number  RCR_NUM  where:  USER_ID  is The eLandings system user ID. RCR_NUM  is The NMFS Restricted Access Management Division registered crab receiver number for crab IFQ.

1839 ERROR: Weight must be less than 1,000 metric tons.

The system does not allow the weight entered to be greater than 1,000 metric tons.

The weight entered, in the weight field, is greater than 1,000 metric tons.

Verify the weight, and enter the correct value.

1840 WARNING: Weight is greater than  MAX_EXPECTED_WEIGHT  metric tons. Is this correct? where:  MAX_EXPECTED_WEIGHT  is The maximum allowable weight.

This warning is generated when the weight entered is between the maximum expected metric tons (varies by species) and the maximum of 1000 metric tons.  The system will let you continue when you select Save Ignoring Warnings.  This button only appears when no errors are generated with the warnings.

The weight entered, is between the maximum expected (varies by species) and the maximum of 1,000 metric tons.

Verify that the weight entered is correct, and if it is, select Save Ignoring Warnings at the bottom of the website.  If the weight is not correct, enter the correct weight and select Save.

1844 ERROR: Sample weight is required 

The sample weight must be entered.

1845 ERROR: Sample weight  WEIGHT  is invalid  where:  WEIGHT  is The weight in pounds.

The sample weight entered is not valid.

1846 ERROR: Sample count is required 

The sample count must be entered.

1847 ERROR: Sample count  COUNT  is invalid  where:  COUNT  is The sample count

The sample count entered is not valid.

1848 ERROR: Average weight is required 

The average weight must be entered.

1849 ERROR: Average weight  WEIGHT  is invalid  where:  WEIGHT  is The weight in pounds.

The average weight entered is not valid.

1850 ERROR: Average weight  WEIGHT  is too small for species  SPECIES  where:  WEIGHT  is The weight in pounds. SPECIES  is The species code.

The average weight entered is too small for the species.

1851 ERROR: Average weight  WEIGHT  is too large for species  SPECIES  where:  WEIGHT  is The weight in pounds. SPECIES  is The species code.

The average weight entered is too large for the species.

1852 ERROR: At least one user is required 

At least one User ID must be entered or selected.

1853 WARNING: Condition Code of  CODE  is an unexpected delivery condition for a Chill Type of FAS and CFEC Fisheries of S05B and S15B, on a line with Chinook or Coho. where:  CODE  is The numeric disposition code, indicating what is being done with the catch.

This warning is generated when line items are entered with a Condition Code other than 07 for Chill Type of FAS and CFEC Fishery is S05B or S15B.  This is an unexpected Condition Code for Frozen At Sea processing for the troll fisheries in this area.

A line item was entered with a Condition Code of 07 when the Chill Type was determined to be FAS and the CFEC Fishery is S05B or S15B, on a line item with Chinook or Coho.

Verify the CFEC Fishery, Chill Type, Condition Codes, and Species and correct as needed.  If there is no correction needed, you can accurately report by save or submit ignoring warnings.

1854 ERROR: Time of landing is required 

The time of landing records is required. 

The time of landing was not entered on the form. 

Enter the time of landing on the form. 

1855 ERROR: Time of landing is invalid

The time of landing records is invalid. 

The time of landing was not entered incorrectly on the form. 

Enter the time of landing on the form in the formate HH:MM or HH.MM or HHMM For example, 01:30 or 01.30 or 0130 

1856 WARNING: Condition Code of  CODE  is an unexpected delivery condition for a Dock Delivered Chinook or Coho in a CFEC Fishery of S05B or S15B. where:  CODE  is The numeric disposition code, indicating what is being done with the catch.

This warning is generated when line items are entered with a Condition Code other than 04 for Dock Deliveries, and CFEC Fishery is S05B or S15B, on line items with Chinook or Coho.

A line item was entered with a Condition Code other than 04 for a Dock Delivery and the CFEC Fishery is S05B or S15B, on a line item with Chinook or Coho

Verify the CFEC Fishery, Dock Delivery flag, Condition Codes, and Species and correct as needed.  If there is no correction needed, you can accurately report by save or submit ignoring warnings.

1857 ERROR: From Time is required

A search From Date is required when searching for reports.

The From Time was left blank.

Enter a valid From Time.

1858 ERROR: From Time is invalid

The system will accept the time in several commonly used formats, and will convert to the standard format.  The from time field was not entered with one of the following formats:  HH:MM, HH:MM:SS, HHMM, HHMMSS.

The from time field was entered in a format that was not recognized. This message can also be seen if the from time field is entered with letters in place of digits.

Verify the from time field, and enter the correct value.

1859 ERROR: To Time is required

A search To Date is required when searching for reports.

The To Time was left blank.

Enter a valid To Time.

1860 ERROR: To Time is invalid

The system will accept the time in several commonly used formats, and will convert to the standard format.  The to time field was not entered with one of the following formats:  HH:MM, HH:MM:SS, HHMM, HHMMSS.

The to time field was entered in a format that was not recognized. This message can also be seen if the to time field is entered with letters in place of digits.

Verify the to time field, and enter the correct value.

1861 ERROR: No reports selected

The application allows the user to select reports for processing, but none was selected.

Select a report and try again.

1864 ERROR: Chum Percentage is required

A percentage must be entered in order to apply it to landing reports.

1865 ERROR: Chum Percentage must be numeric

The chum percentage entered is invalid, it must be a number between 0 and 100.

1866 ERROR: Chum Percentage cannot be less than zero

The chum percentage entered was less than zero, which is not possible.

1867 ERROR: Chum Percentage cannot be greater than 100

The chum percentage entered was more than 100 percent , which is not possible.

1868 WARNING: Chum Percentage is greater than  PERCENT , is that correct? where:  PERCENT  is The chum percentage.

The chum percentage entered was uncommonly large. The system gives this message so the user can confirm that the chum percentage was entered correctly.

1870 ERROR: From/To Date Range is too large

The date range specified by the From Date and To Date is too big.

The date range for chum percentage mass updates can be a maximum of 3 days.

1871 ERROR: Landing report  REPORT_ID  is not a Bristol Bay salmon landing report, Chum Percentage adjustment is not allowed where:  REPORT_ID  is The eLandings landing report ID

The chum percentage mass change capability is only for use with landing reports in the Bristol Bay salmon fisheries.

1873 ERROR: Landing report  REPORT_ID  does not have mixed salmon itemized catch, it is required for Chum Percentage mass change where:  REPORT_ID  is The eLandings landing report ID

In order to apply a chum percentage to a landing report the report must have mixed salmon itemized catch to take the percentage from.

1875 ERROR: Create Date  FROM  for data file cannot be after usage date  TO  where:  FROM  is The start of the date range. TO  is The end of the date range.

The create date of the data is after the date the data is being used. This is illogical.

1876 ERROR: The Create Date of the data file is too old. The data is stale

The data file must be used in a timely manner. Old data files contain stale data that can cause system problems.

1877 WARNING: Nearest Bay and Headland should not contain stat areas or district and sub district codes

It appears that the Nearest Bay and Headland contains the numeric pattern of a statistical area or district and sub district pattern.  The intention of this field is to record the common names of the nearest bays or headlands.

1878 ERROR: Chill Type  CHILL_TYPE  not effective for date  DATE  where:  CHILL_TYPE  is The selected Chill Type. DATE  is The date entered for the announcement.

The Chill Type has been retired or is not in effect yet.

A Chill Type was used that is no longer valid.

Verify your Chill Type and use the most accurate code.

1879 ERROR: Delivery Port or Region is invalid

Delivery Port or Region is required for IFQ crab deliveries to stationary floating processors. It should not contain special characters.

1880 ERROR: Encrypted Number is invalid

Encrypted number is invalid.

The Encrypted number was entered incorrectly or is invalid.

Review your encrypted number and try again, or verify the number with the processing plant.  You may request a new encrypted number.

1881 ERROR: Encrypted Number is stale

Encrypted number is stale.

The Encrypted number was reserved on a previous date.

Review your encrypted number and try again, or verify the number with the processing plant.  You may request a new encrypted number.

1882 ERROR: Encrypted Number is reserved for another vessel

Encrypted number is reserved for another vessel.

An encrypted number was used, which was intended for another vessel.

Review your encrypted number and try again, or verify the number with the processing plant.  You may request a new encrypted number.

1883 ERROR: Halibut may not be reported on a Salmon Landing.

Halibut are not permitted on Salmon landings

A halibut line item was included on a salmon landing

Remove the halibut line item from the salmon landing. Create a groundfish landing for the halibut items.

1884 WARNING: Nearest headland value is missing. This information may be required by the Area Management Biologists.

No value was entered in the Nearest Bay or Headland field

No value was entered in the Nearest Bay or Headland field

Enter a text description in the nearest bay or headland field

1885 ERROR: Date Fishing Ended is required

The date fishing ended is required information and must be entered.

The date fishing ended was not entered.

Verify the date fishing ended, and enter the correct value.

1886 ERROR: Date Fishing Ended is invalid

The system will accept the date in several commonly used formats, and will convert to the standard format.  The date fishing ended field was not entered with one of the following formats:  mm/dd/yyyy, m/d/y, mmddyyyy, mm-dd-yyyy, m-d-y.

The date fishing ended was entered in a format that was not recognized. This message can also be seen if the date fishing ended is entered with letters in place of digits.

Verify the date fishing ended, and enter the correct value.

1887 ERROR: Date Fishing Ended requires four digit year

1888 ERROR: Date Fishing Ended cannot be before this date in  YEAR  where:  YEAR  is The earliest year allowed to be entered.

The system restricts the date fishing ended field from being dated more than six years in the past.

A date earlier than six years in the past has been entered in the date fishing ended field.

Verify the date fishing ended, and enter the correct value.

1889 ERROR: Date Fishing Ended cannot be in the future

The system restricts the date fishing ended entered from being dated in the future.

A date that is in the future has been entered in the date fishing ended field.

Verify the date fishing ended, and enter the correct value.

1890 WARNING: CFEC Permit  PERMIT  year does not match Date of Landing year where:  PERMIT  is The CFEC Permit.

The year sequence date of the CFEC permit does not match the year of the date of landing.

This can be caused by using an old CFEC permit, or by using a new one that was received before the beginning of the year for which it is valid.

1891 ERROR: Delivery Port or Region is required

Delivery Port or Region is required for IFQ crab deliveries to stationary floating processors.

1892 ERROR: Date Fishing Ended cannot be before Date Fishing Began

The date fishing ended cannot be before the date fishing began, that is illogical.

A date fishing began or date fishing ended was mis-entered.

Verify the date fishing ended, and enter the correct value.

1893 ERROR: Date Fishing Ended cannot be after Date of Landing

The date fishing ended cannot be after the date of landing, that is illogical.

A date fishing ended or date of landing was mis-entered.

Verify the date fishing ended, and enter the correct value.

1894 ERROR: Average weight for  SPECIES  is required where:  SPECIES  is The species code.

The average weight for the species is required.

Average weight was not entered.

Enter an average weight for the species.

1895 ERROR: Average weight for  SPECIES  must be numeric where:  SPECIES  is The species code.

The average weight for the species must be a number.

The average weight for the species was mis-entered.

Verify the average weight, and enter the correct value.

1896 ERROR: Average wight for  SPECIES  cannot be negative where:  SPECIES  is The species code.

The average weight for the species cannot be negative, that is illogical.

The average weight was mis-entered.

Verify the average weight for the species, and enter the correct value.

1897 ERROR: The user defined alias assigned to the size/grade template is too large.

The user defined alias assigned to the size/grade template is too large.

You have entered too many characters.

Provide a shorter alias name

1898 ERROR: QA probe score is required

1899 ERROR: QA probe score  SCORE  is invalid where:  SCORE  is The QA Probe Score.

1900 WARNING: Halibut must be landed and weighed (04) head-on

The IPHC has determined that head on weight is more accurate for determining impact on the halibut resource. Beginning in 2017, all IFQ halibut should be weighed head on when landing, except for halibut frozen at sea.

You have entered head off itemized catch for halibut being sold or retained.

If the halibut was frozen at sea this warning can be ignored. Otherwise, check with NMFS Enforcement.

1901 WARNING: Itemized catch line has grading/pricing that could not be automatically edited. Please check grading/pricing for consistency after saving

1902 WARNING: Vessel  ADFG  is on report with name  RPT_NAME . but name on server is  SVR_NAME  where:  ADFG  is The vessel ADF&G number. RPT_NAME  is The name of the vessel entered on the tLandings report. SVR_NAME  is The name of the vessel on the server.

The tLandings CFEC permit dialog allows users to enter both the vessel ADF&G number and the vessel name. If they make a mistake the landing report can have a different vessel name than the name associated with the ADF&G number on the server

The user corrected the vessel name, but did not change the vessel number, or they input either the vessel name or number incorrectly.

Review the report and make sure that the Vessel ADF&G Number is correct for the landing. If only the vessel name is incorrect it will fix itself on report import.

1903 ERROR: Vessel length  VESSEL_LENGTH  is invalid. where:  VESSEL_LENGTH  is Vessel length

1904 ERROR: License year  LICENSE_YEAR  is invalid. where:  LICENSE_YEAR  is Vessel license year

1905 ERROR: Effectivity date  EFFECTIVITY_DATE  is invalid. where:  EFFECTIVITY_DATE  is Vessel license effectivity date

1906 ERROR: Effectivity end date  EFFECTIVITY_END_DATE  is invalid. where:  EFFECTIVITY_END_DATE  is Vessel license effectivity date

1907 ERROR: Coast guard number  COAST_GUARD_NUMBER  is invalid. where:  COAST_GUARD_NUMBER  is Vessel coast guard number

1908 ERROR: Homeport city name  HOMEPORT_CITY_NAME  is invalid. where:  HOMEPORT_CITY_NAME  is Vessel homeport city

1909 ERROR: Homeport state code  HOMEPORT_STATE_CODE  is invalid. where:  HOMEPORT_STATE_CODE  is Vessel homeport state

1910 ERROR: Net tonnage  NET_TONNAGE  is invalid. where:  NET_TONNAGE  is Vessel net tonnage

1911 ERROR: Gross tonnage  GROSS_TONNAGE  is invalid. where:  GROSS_TONNAGE  is Vessel gross tonnage

1912 ERROR: Shaft horsepower  SHAFT_HORSEPOWER  is invalid. where:  SHAFT_HORSEPOWER  is Vessel shaft horsepower

1913 ERROR: Year built  YEAR_BUILT  is invalid. where:  YEAR_BUILT  is Vessel year built

1914 ERROR: Engine type  ENGINE_TYPE  is invalid. where:  ENGINE_TYPE  is Vessel engine type

1915 ERROR: Hull type  HULL_TYPE  is invalid. where:  HULL_TYPE  is Vessel hull type

1916 ERROR: Hold tank  HOLD_TANK  is invalid. where:  HOLD_TANK  is Vessel hold tank size

1917 ERROR: Live tank  LIVE_TANK  is invalid. where:  LIVE_TANK  is Vessel live tank size

1919 ERROR: Salmon area  SALMON_AREA  is invalid. where:  SALMON_AREA  is CFEC salmon area

1920 ERROR: Fuel  FUEL  is invalid. where:  FUEL  is Vessel fuel

1925 ERROR: Cfec ID  CFEC_ID  is invalid. where:  CFEC_ID  is Vessel CFEC ID

1926 ERROR: Owner last name  OWNER_LAST_NAME  is invalid. where:  OWNER_LAST_NAME  is Vessel owner last name

1927 ERROR: Owner first name  OWNER_FIRST_NAME  is invalid. where:  OWNER_FIRST_NAME  is Vessel owner last name

1928 ERROR: Owner middle initial  OWNER_MI  is invalid. where:  OWNER_MI  is Vessel owner middle initial

1929 ERROR: Owner suffix  OWNER_SUFFIX  is invalid. where:  OWNER_SUFFIX  is Vessel owner suffix

1930 ERROR: Owner type  OWNER_TYPE  is invalid. where:  OWNER_TYPE  is Vessel owner type

1931 ERROR: Owner address  OWNER_ADDRESS_TYPE  is invalid. where:  OWNER_ADDRESS_TYPE  is Vessel owner address type

1932 ERROR: Owner address  OWNER_ADDRESS  is invalid. where:  OWNER_ADDRESS  is Vessel owner address

1933 ERROR: Owner city  OWNER_CITY  is invalid. where:  OWNER_CITY  is Vessel owner city

1934 ERROR: Owner state  OWNER_STATE  is invalid. where:  OWNER_STATE  is Vessel owner state

1935 ERROR: Owner zip code  OWNER_ZIP  is invalid. where:  OWNER_ZIP  is Vessel owner zip code

1936 ERROR: Owner country  OWNER_COUNTRY  is invalid. where:  OWNER_COUNTRY  is Vessel owner country

1937 ERROR: Export Format is required

The format of the export file must be specified, otherwise  the system does not know what format to use.

Specify an export format

1938 ERROR: Export Format  FORMAT  is not valid where:  FORMAT  is The output file format.

The valid export formats are CSV for comma separated values and XLS for 

1939 ERROR: Template File is required

A template file is needed

1940 ERROR: Template File is not valid

The template files is invalid.

The tempalte files was not a Microsoft Excel 97-2003 file.

1941 ERROR: Template File name is too long

The lenght of the directory path and file name cannot be more than 256 characters

1942 ERROR: Partial Delivery or Last Delivery for Trip is required

For crab landing reports, the user must indicate if the report is for a partial delivery or is the last delivery for the trip.

Both the Partial Delivery checkbox and the Last Delivery for Trip checkboxes are unchecked.

Check the appropriate checkbox.

1946 ERROR: Mixed Salmon species code is not allowed on final reports

The species code for mixed sockeye and chum salmon was entered on the itemized catch line, and the report was submitted or saved as a final report.

The mixed salmon species code is used in fast paced tendering operations where the fish are not sorted until after the tender unloads at the plant. The mixed salmon species code is used on the fish tickets that are cut on the tender. These landing reports can be entered into eLandings, but the chum percentage must be applied and the species codes changed to the actual codes for sockeye and chum before the landing report can be finalized.

Run the chum percentage mass change on the landing report, or edit the report by hand.

1947 ERROR: Userid  USER_ID  is invalid where:  USER_ID  is The eLandings system user ID.

The userid entered is not a valid userid.

The userid contained the colon character. This is not allowed.

1948 ERROR: Species  SPECIES  should ony be used on salmon landing reports where:  SPECIES  is The species code.

Some species codes are used for special cases only. Among these are codes for some salmon.

The species code for general salmon, mixed salmon, or undersized chinook salmon was used on a non-salmon landing report

Use one of the standard salmon species codes.

1949 ERROR: Landing Report numbers are not in numerical sequence

The landing report numbers are not in sequential order

Internal system error

Notify eLandings production support

1950 ERROR: Fish Ticket numbers are not in numerical sequence

The landing report numbers are not in sequential order

Internal system error

Notify eLandings production support

1951 ERROR: The number of landing report numbers is not the same as the number of fish ticket numbers

The sets of landing report numbers and fish ticket numbers are of unequal length

Internal system error

Notify eLandings production support

1952 ERROR: Check digit error, the encoded character string was not entered exactly

The encoded character string includes check digits to make sure the characters are entered exactly as they were generated.

The check digits calculated from the character string did not match the check digits that were included in the string.

Re-enter the encoded character string, being careful to enter it exactly. Alternately, request that the processor read off the character string again, being sure to give it exactly.

1953 ERROR: Manual landing via the Data Techs is required due to non-04 or 05 halibut

The user has tried to create an IFQ report for an itemized catch line that has halibut in a condition other than 04 or 05.

This is caused by using a condition code for halibut other than 04 Gutted or 05 Headed and Gutted.

Contact the NMFS Data Techs to do a manual IFQ landing.

1954 ERROR: IFQ reports cannot be created for itemized catch with estimated weight

The user has tried to create an IFQ report for an itemized catch line that has estimated weight. IFQ regulations require all IFQ reporint to use scale weights.

This is caused by using the estimated weight value in the wegiht modifier for an IFQ species.

Enter the actual scale weight with no weight modifier or the ice and slime weight modifier, as appropriate.

1955 ERROR: No Report Numbers available, request more with an email transmission

The user has run out of new report numbers, which are needed to create landing and production reports.

This can be caused by doing a large number of reports without processing a return receipt. It can also occur if you have started to create reports and shutdown the application, causing report numbers to be lost.

On seaLandings, send a report transmission message, with or without reports. The return receipt will contain more numbers.

1956 ERROR: No Fish Ticket Numbers available, request more with an email transmission

The user has run out of new fish ticket numbers, which are needed to create landing reports.

This can be caused by doing a large number of reports without processing a return receipt. It can also occur if you have started to create reports and shutdown the application, causing report numbers to be lost.

On seaLandings, send a report transmission message, with or without reports. The return receipt will contain more numbers.

1958 ERROR: Counts add up to more than tally line count

1959 ERROR: Counts don't add up to tally line count

1960 ERROR: Statistical area  STAT_AREA  does not map to Special Area  SPECIAL_AREA  for report where:  STAT_AREA  is The ADF&G Statistical Area identifier. SPECIAL_AREA  is The 5 character trawl gear Special Area.

1961 ERROR: Duplicate species default for species  SPECIES  and condition  CONDITION  where:  SPECIES  is The species code. CONDITION  is The numeric condition code.

Either you are requesting to add a new species defaults record when one already exists in the list or you have created a list of species default records that contain two or more species default records for the same species and condtion code.

Two species default records have the same species code and codition code

Edit the existing species default record or remove duplicate records from the list.

1962 ERROR: Duplicate grading and pricing default for species  SPECIES , condition  CONDITION , size grade  SIZEGRADE , and product type  PRODUCTTYPE  where:  SPECIES  is The species code. CONDITION  is The numeric condition code. SIZEGRADE  is The size/grade description. PRODUCTTYPE  is The product type.

Either you are requesting to add a new grading and pricing record when one already exists in the list or you have created a list of grading and pricing records that contain two or more grading and pricing records for the same species, condtion code, size grade and product type.

Two grading and pricing records have the same species code, codition code, grading and pricing description and product type.

Edit the existing grading and pricing record or remove duplicate records from the list.

1963 ERROR: ROW_NUMBER_REQUIRED

When a request is made to the database, each record is assigned a row number. In some cases, the system cannot return every result because the result set is so large. To avoid this problem the system asks to know row numbers that the user would like to receive.

Either the starting or ending row number was not entered

Enter the starting and ending row number range.

1964 ERROR: ROW_NUMBER_MUST_BE_NUMERIC

Row numbers must be positive integers.

The value entered is not a positive integer.

Review the entered value and ensure that it is a positive integer.

1966 ERROR: Coho Percentage is required

A percentage must be entered in order to apply it to landing reports.

1967 ERROR: Coho Percentage must be numeric

The coho percentage entered is invalid, it must be a number between 0 and 100.

1968 ERROR: Coho Percentage cannot be less than zero

The coho percentage entered was less than zero, which is not possilble.

1969 ERROR: Coho Percentage cannot be greater than 100

The coho percentage entered was more than 100 percent , which is not possilble.

1970 WARNING: Coho Percentage is greater than  PERCENT , is that correct? where:  PERCENT  is The chum percentage.

The coho percentage entered was uncommonly large. The system gives this message so the user can confirm that the coho percentage was entered correctly.

1972 ERROR: Processor Edit Stop Date is required

The processor edit stop date is required information and must be entered.

The processor edit stop date was not entered.

Verify the processor edit stop date, and enter the correct value.

1973 ERROR: Processor Edit Stop Date is invalid

The system will accept the date in several commonly used formats, and will convert to the standard format.  The processor edit stop date field was not entered with one of the following formats:  mm/dd/yyyy, m/d/y, mmddyyyy, mm-dd-yyyy, m-d-y.

The processor edit stop date was entered in a format that was not recognized. This message can also be seen if the processor edit stop date is entered with letters in place of digits.

Verify the processor edit stop date, and enter the correct value.

1974 ERROR: Processor Edit Stop Date cannot be more than one day in the past

When resetting the processor edit stop date the new value cannot be more than one day in the past. A date one day in the past will prevent users from being able to edit the report, but will preserve information about the time period when the date was changed.

1975 ERROR: Processor Edit Stop Date requires four digit year

The system requires the year portion of the processor edit stop date to be specified as a 4 digit year.

1976 ERROR: Processor Edit Stop Date cannot be more than  DAYS  days in the future where:  DAYS  is The number of days in the future the date may be set, according to the business rules.

The system restricts the processor edit stop date field from being too far in the future. If the processor will need to continue to edit the report far into the future then an agency user should be aware of this activity, and authorize it by resetting the edit stop date

A date earlier further in the future than the business rule limit has been entered in the processor edit stop date field.

Enter a processor edit stop date within the allowed range. If the processor user needs more time then reset the processor edit stop date again later.

1979 ERROR: Report  REPORT_ID  is locked, email eLandings support at elandings@alaska.gov to unlock where:  REPORT_ID  is The eLandings landing report ID

Individual landing and production reports cannot be updated or modified after 90 days from the date of landing or the date of the production report. After that time the report is locked against updates. Agency support personnel can unlock reports if updates are needed.

Send an email to eLandings support at elandings@alaska.gov, with the subject 'Modify Report'. Include the Report ID in the email and the reason for modifications. 

1980 ERROR: The schema version passed in the web service call and the schema version of the document are not consistent

When calling a web service method, the schema version passed in the version argument must be the same as the schema version of the report document passed to the web service.

The software calling the eLandings web service is not handling schema versioning properly.

Contact technical support for the software that is trying to call the eLandings web service. The problem is in the interfacing software, not eLandings, so eLandings system support will not be able to resolve the problem.

1981 WARNING: Temperature  TEMPERATURE  is low where:  TEMPERATURE  is A fish temperature

1982 WARNING: Temperature  TEMPERATURE  is high where:  TEMPERATURE  is A fish temperature

1983 ERROR: Species  SPECIES  is not allowed where:  SPECIES  is The species code.

Some species codes are used for special situations, and are not allowed to be used on reports except for those situations.

A limited use species code was used as a general purpose species code.

Select another species code. For example, if species code 411 (undersized Chinook salmon) caused this error select species code 410 (Chinook salmon).

1984 ERROR: Total sold weight on fish ticket  FISH_TICKET_NUMBER  does not match total sold weight on IFQ reports for species  SPECIES_CODE  and  AREA  where:  FISH_TICKET_NUMBER  is The ADF&G fish ticket id number. SPECIES_CODE  is The numeric species code. AREA  is The IPHC Regulatory Area.

1985 ERROR: Total retained weight on fish ticket  FISH_TICKET_NUMBER  does not match total retained weight on IFQ reports for species  SPECIES_CODE  and  AREA  where:  FISH_TICKET_NUMBER  is The ADF&G fish ticket id number. SPECIES_CODE  is The numeric species code. AREA  is The IPHC Regulatory Area.

1986 ERROR: Total deadloss weight on fish ticket  FISH_TICKET_NUMBER  does not match total deadloss weight on IFQ reports for species  SPECIES_CODE  and  AREA  where:  FISH_TICKET_NUMBER  is The ADF&G fish ticket id number. SPECIES_CODE  is The numeric species code. AREA  is The IPHC Regulatory Area.

1987 ERROR: Tare weight is required

1988 ERROR: Tare weight must be numeric

1989 WARNING: Tare weight  TARE_WEIGHT  is too small where:  TARE_WEIGHT  is Weight of the container used to weight fish

1990 WARNING: Tare weight  TARE_WEIGHT  is too large where:  TARE_WEIGHT  is Weight of the container used to weight fish

1991 ERROR: Total Tare weight  TARE_WEIGHT  may not be greater than or equal to scale weight  SCALE_WEIGHT  of all mixed salmon where:  TARE_WEIGHT  is Weight of the container used to weight fish SCALE_WEIGHT  is Weight of fish and container if not zeroed out

1992 ERROR: Tender Trip Number is required

The tender trip number must be input.

1993 ERROR: Tender Trip Number  TRIP_NUMBER  is invalid where:  TRIP_NUMBER  is The trip identifing number for the vessel.

The tender trip number must be a number between 1 and 999. No decimal points are allowed.

1994 ERROR: Tender Trip Number is not allowed without Tender Vessel ADF&G Number

The tender trip number should only be input if the report has a tender vessel number. Otherwise, no tender is identified for the tender trip.

1998 ERROR: Input File name is required

An input file is needed

2000 ERROR: Input File name is too long

The length of the directory path and file name cannot be more than 256 characters

2001 ERROR: Pink Percentage is required

A percentage must be entered in order to apply it to landing reports.

2002 ERROR: Pink Percentage must be numeric

The pink percentage entered is invalid, it must be a number between 0 and 100.

2003 ERROR: Pink Percentage cannot be less than zero

The pink percentage entered was less than zero, which is not possilble.

2004 ERROR: Pink Percentage cannot be greater than 100

The pink percentage entered was more than 100 percent , which is not possible.

2005 WARNING: Pink Percentage is greater than  PERCENT , is that correct? where:  PERCENT  is The chum percentage.

The pink percentage entered was uncommonly large. The system gives this message so the user can confirm that the pink percentage was entered correctly.

2007 ERROR: Total tare weight and mixed salmon line item tare weights cannot coexist

Total tare weight has been defined for the landing report and a tare weight has been defined on an individual mixed salmon line item.

Remove the tare weight from the total tare weight field or remove the tare weight(s) from the individual mixed salmon line items.

2009 ERROR: Disposition code  DISPOSITION  is only allowed on crab reports where:  DISPOSITION  is The disposition code.

This disposition is only allowed on crab reports

Choose another disposition.

2010 ERROR: Statistical area is required on the line item

Statistical area is required on all line items that use the No Harvest disposition.

Add a statistical area..

2011 ERROR: This line item must have a condition code of Whole

Some dispositions, such as No Harvest, require that the condition code Whole.

Change condition to Whole.

2012 ERROR: The species on this line item must be a shell fish species or octopus

This species code must be greater than 800. this includes all shelfish species and octopus

Change species code to one greater than 800.

2013 ERROR: A count is not allowed on this line item

Some dispositions, such as No Harvest, require that no count be shown on the line item.

Remove the count.

2014 ERROR: A weight is not allowed on this line item

Some dispositions, such as No Harvest, require that no weight be shown on the line item.

Remove the weight.

2015 WARNING: At least one grading and pricing item should be entered for a line item with a condition that can be either Primary or Ancillary

Some condition codes can be used for either Primary or Ancillary product. For itemized catch lines that use these condition codes a grading and pricing item is needed to indicate whether the line is for Primary or Ancillary product.

Add a grading and pricing item for the line. No size/grade or price is needed, just the product type (P/A). The sold weight should be the same as the line item weight.

2016 ERROR: All grading and pricing items for the line must have the same product type, either Primary or Ancillary

Some condition codes can be used for either Primary or Ancillary product. For itemized catch lines that use these condition codes the grading and pricing items indicate whether the line is for Primary or Ancillary product. All of the grading and pricing items need to use the same product type.

Divide the weight for the itemized catch line into two itemized catch lines, one for the Primary product and another for the Ancillary product. Each itemized catch line will require at least one grading and pricing item, specifying the product type.

2017 ERROR: Period is not valid

Period is a fishing time indicator defined and determined by fishery managers. The period is a two digit numeric code, with leading zeros.

2019 ERROR: Average Weight may not be calculated for species  SPECIES  where:  SPECIES  is The species code.

The average weight function may not be used for this species. 

Provide the actual fish count number on the line item.

2020 WARNING:  MSG  where:  MSG  is The Java Exception message.

This is a warning message from a subsystem of eLandings.

Some subsystem issued a warning message, which eLandings passed on.

Depends on the specific message

2021 ERROR: Color is required

The color field is required.

2022 ERROR: Color  NAME  is not valid where:  NAME  is The constant name.

The color input is not valid.

2023 ERROR: Label is required

The label field is required.

2024 ERROR: Label  NAME  is not valid where:  NAME  is The constant name.

The label input is not valid.

2025 ERROR: Cache Name is required

The cache name field is required.

2026 ERROR: Cache Name is not valid

The cache name is not valid.

2027 ERROR: Cache Key is required

The key field is required.

2037 ERROR:  MSG  where:  MSG  is The Java Exception message.

This is an error message from a subsystem of eLandings.

Some subsystem issued an error message, which eLandings passed on.

Depends on the specific message

2038 ERROR: Logbook ID is required

The logbook ID number is required to find the logbook record in the database.

A Logbook Report was submitted without a logbook ID.

Provide the Logbook ID. If the logbook has not been registered, register it before trying to submit entries.

2039 ERROR: Logbook ID  ID  is invalid where:  ID  is The unique numeric identifier for the operation.

Logbook IDs are generated by the system. Valid ones are always numbers greater than zero and less than a maximum value.

The logbook ID provided was not numeric, was less than one, or was too big.

Check that the logbook ID used is correct, and was received from the system.

2040 ERROR: Gear ID is required

Gear ID identifies the gear used. For trawl it is the same as the gear code. For longline in includes skate configuration information by referring to a fsihing entry.

Gear ID was missing.

Provide the appropriate gear id.

2041 ERROR: Gear ID  ID  is invalid where:  ID  is The unique numeric identifier for the operation.

The gear ID provided was not previously defined on a fishing entry, and is not a recognized gear code.

The gear ID was not found in the current definitions.

Provide a fishing entry with the Gear ID, or use a Gear ID that is already defined.

2042 ERROR: Haul Number is required

Haul entries must include the sequence number of the haul for the year. In cases of vessels that fish both trawl and longline or pot gear, the number required is actually the sequential number of the haul or set in the year.

The haul number was not provided for the haul entry

Provide the correct haul number

2043 ERROR: Haul Number  NUMBER  is invalid where:  NUMBER  is The number of reports found.

The haul number is the numeric sequence of the haul during the year. Since the number is the count of hauls during the year, and a boat can only make so many hauls, the number must be reasonable.

The Haul Number provided was not numeric, was less than one, or was too big.

Provide the appropriate haul number.

2044 ERROR: Latitude is required

Latitude must be input as a decimal number, giving degrees and fractions of a degree.

The latitude was missing.

Enter the latitude as a decimal number.

2046 ERROR: Latitude  LATITUDE  is invalid where:  LATITUDE  is The latitude.

Latitude must be input as a decimal number, giving degrees and fractions of a degree.

The latitude was not a decimal number. This can occur if it is input as degrees and minutes instead of decimal degrees.

Enter the latitude as a decimal number. Convert minutes and seconds to fractions of a degree.

2047 ERROR: Latitude is outside of North Pacific waters

Latitude input on eLandings should be in the North Pacific ocean.

The latitude input was a for valid location, but it is far from Alaska.

Check the latitude and enter the correct value.

2048 ERROR: Longitude is required

2050 ERROR: Longitude  LONG  is invalid where:  LONG  is The longitude.

2051 ERROR: Longitude is outside of North Pacific waters

2052 ERROR: Begin Latitude is required

2054 ERROR: Begin Latitude  LAT  is invalid where:  LAT  is The latitude.

2055 ERROR: Begin Latitude is outside of North Pacific waters

2056 ERROR: Begin Longitude is required

2058 ERROR: Begin Longitude  LONG  is invalid where:  LONG  is The longitude.

2059 ERROR: Begin Longitude is outside of North Pacific waters

2060 ERROR: End Latitude is required

2061 ERROR: End Latitude must be numeric

2062 ERROR: End Latitude  LAT  is invalid where:  LAT  is The latitude.

2063 ERROR: End Latitude is outside of North Pacific waters

2064 ERROR: End Longitude is required

2065 ERROR: End Longitude must be numeric

2066 ERROR: End Longitude  LONG  is invalid where:  LONG  is The longitude.

2067 ERROR: End Longitude is outside of North Pacific waters

2068 ERROR: Average Sea Depth is required

2069 ERROR: Average Sea Depth must be numeric

2070 ERROR: Average Sea Depth cannot be negative

2071 ERROR: Average Sea Depth is too large

2072 ERROR: Average Gear Depth is required

2073 ERROR: Average Gear Depth must be numeric

2074 ERROR: Average Gear Depth cannot be negative

2075 ERROR: Average Gear Depth is too large

2076 ERROR: Target Species is required

2077 ERROR: Target Species  SPECIES  is invalid where:  SPECIES  is The species code.

2078 ERROR: Target Species  SPECIES  not in effect for date  DATE  where:  SPECIES  is The species code. DATE  is The date entered for the announcement.

2079 ERROR: Hail Weight is required

2080 ERROR: Hail Weight cannot be negative

2081 ERROR: Hail Weight must be a whole number

2082 ERROR: Hail Weight must be numeric

2083 ERROR: Hail Weight is too large

2084 ERROR: Year is required

2085 ERROR: Year  YEAR  is invalid where:  YEAR  is The earliest year allowed to be entered.

2086 ERROR: Weight Unit of Measure is required

2087 ERROR: Weight Unit of Measure  UNIT  is invalid where:  UNIT  is The unit of measure.

2088 ERROR: Depth Unit of Measure is required

2089 ERROR: Depth Unit of Measure  UNIT  is invalid where:  UNIT  is The unit of measure.

2090 ERROR: Go Active Date is required

2091 ERROR: Go Active Date is invalid

2092 ERROR: Go Active Date cannot be in the future

2093 ERROR: Go Active Date year must be four digits

2094 ERROR: Go Active Date is too far in the past

2095 ERROR: Go Inactive Date is required

2096 ERROR: Go Inactive Date is invalid

2097 ERROR: Go Inactive Date cannot be in the future

2098 ERROR: Go Inactive Date year must be four digits

2099 ERROR: Go Inactive Date is too far in the past

2100 ERROR: Start Date is required

2101 ERROR: Start Date is invalid

2102 ERROR: Start Date cannot be in the future

2103 ERROR: Start Date year must be four digits

2104 ERROR: Start Date is too far in the past

2105 ERROR: Operator Name is required

2106 ERROR: Operator Name cannot be longer than 32 characters

2107 ERROR: Observer Name is required

2108 ERROR: Observer Name cannot be longer than 32 characters

2109 ERROR: Cruise Number is required

2110 ERROR: Cruise Number  NUM  is invalid where:  NUM  is The number of fish ticket numbers that have been issued but not imported yet.

2111 ERROR: Entry Time is required

2112 ERROR: Entry Time is invalid

2113 ERROR: Entry Sequence is required

2114 ERROR: Entry Sequence is invalid

2115 ERROR: Overlimit threshold is required

Overlimit threshold is required.

2116 ERROR: Overlimit threshold must be a numeric value

Overlimit threshold must be a numeric value

2117 ERROR: Overlimit threshold cannot be less than zero

Overlimit threshold cannot be less than zero.

2118 ERROR: Overlimit threshold cannot be greater than  MAX_THRESHOLD  where:  MAX_THRESHOLD  is The maximum overlimit amount.

Overlimit threshold is too large.

2120 ERROR: Set Number is required

2121 ERROR: Set Number  NUMBER  is invalid where:  NUMBER  is The number of reports found.

2122 ERROR: Condition is not allowed on Catch Entry

2123 ERROR: Haul Entry not found for Haul Entry Sequence Number  NUMBER  where:  NUMBER  is The number of reports found.

2125 ERROR: Gear Deployment Time is required

2126 ERROR: Gear Deployment Time is invalid

2127 ERROR: Gear Retrieval Time is required

2128 ERROR: Gear Retrieval Time is invalid

2129 ERROR: Gear Retrieval Time is too long after Gear Deployment Time

2130 ERROR: Gear Retrieval Time cannot be before Gear Deployment Time

2131 ERROR: Begin and End Latitude are too far apart

2132 ERROR: Begin and End Longitude are too far apart

2133 WARNING: Begin Lat/Long is not in Federal Reporting Area  AREA  where:  AREA  is The IPHC Regulatory Area.

2134 WARNING: End Lat/Long is not in Federal Reporting Area  AREA  where:  AREA  is The IPHC Regulatory Area.

2135 WARNING: Begin Lat/Long is not in Special Area  AREA  where:  AREA  is The IPHC Regulatory Area.

2136 WARNING: End Lat/Long is not in Special Area  AREA  where:  AREA  is The IPHC Regulatory Area.

2137 ERROR: Gear ID  GEAR  must appear on prior Fishing Entry where:  GEAR  is The gear ID.

2138 WARNING: Gear Retrieval Time is more than 48 hours after Gear Deployment Time

2139 ERROR: Gear Retrieval Time cannot be in the future

2140 ERROR: Haul or Set Entry required for Catch Entry

2141 ERROR: Duplicate Entry Sequence Number  SEQ  where:  SEQ  is The entry sequence number.

2142 ERROR: Entry Sequence Number  SEQ  out of sequence where:  SEQ  is The entry sequence number.

2143 ERROR: Entry Sequence Number not the next number in sequence

2144 ERROR: Entry Time out of sequence

The entry time is before the last entry time that was created for the current logbook

The time on your computer was changed so that the current date and/or time is before the last entry time.

Reset your computer clock to the correct date and time then close and re-open the application.

2148 ERROR: Logbook Entries are requried in Logbook Reports

2149 WARNING: Begin Lat/Long is in Special Area  AREA  where:  AREA  is The IPHC Regulatory Area.

2150 WARNING: End Lat/Long is in Special Area  AREA  where:  AREA  is The IPHC Regulatory Area.

2151 WARNING:  FISHERY  Permit should not be used for Management Program  PGM  where:  FISHERY  is The CFEC fishery code that is on the CFEC permit card. PGM  is The management program.

2152 WARNING: Management Program SMS in Southeast requires C61A, C61C, or C91C CFEC Permit

2153 ERROR: User  USER_ID  is not authorized to view Logbook  REPORT_ID  where:  USER_ID  is The eLandings system user ID. REPORT_ID  is The eLandings landing report ID

The federal permit number for the logbook does not match one of your userID's authorized operations.

You tried to access a logbook by report id that does not match one of your authorized operations. This can happen if you put in the wrong logbook report id. You can also get this message if you tried to submit a logbook report from the processor workstation and the logbook has a federal permit number that does not match one of your authorized operations. You can also get this message if you try to import a logbook report with a Federal Permit Number that does not match one of your authorized operations.

If you are importing an XML file, check the Federal Permit Number in the file to make sure it is correct. If you are sure you should be able to view the logbook whose ID you entered, have your eLandings administrative user check to make sure you are authorized for the operation that applies to the logbook. They can authorize your user id for that operation. Otherwise, contact eLandings technical support to have them determine what you need to access the operation.

2154 ERROR: Logbook  REPORT_ID  not found where:  REPORT_ID  is The eLandings landing report ID

All logbooks are required to have a unique ID number. The ID number is used to locate the report in the database.

The ID entered was not found in the logbooks in the database.

Verify the ID, and enter the correct value.  If the logbook has never been registered, register it in order to receive the unique ID number.

2155 ERROR: Logbook identifying data in the logbook_header section is required

Logbook header information is required to identify the logbook.

The header information was not found in the logbook.

Verify that the logbook header element is created and added to the logbook XML data.

2156 ERROR: Search Date Type is required

The search date range type must be specified, to identify either the date of landing or the date of last update as the search criteria.

The search date type was not provided.

Retry after making sure the search date type is specified correctly.

2157 ERROR: Search Date Type  TYPE  is invalid where:  TYPE  is The operation type code.

The search date range type must be specified, to identify either the date of landing or the date of last update as the search criteria.

The search date type specified was not a valid value. Valid values are 'report' and 'lastupdate'.

Retry after making sure the search date type is specified correctly.

2158 ERROR: Extract Detail Type is required

The detail type must be specified for report Excel extracts. The extract detail type specifies whether grading and pricing detail is given for itemized catch lines, or itemized catch lines are split according to the statistical area worksheet.

The extract detail type was not provided.

Retry after making sure the extract detail type is specified correctly.

2159 ERROR: Extract Detail Type  TYPE  is invalid where:  TYPE  is The operation type code.

The detail type must be specified for report Excel extracts. The extract detail type specifies whether grading and pricing detail is given for itemized catch lines, or itemized catch lines are split according to the statistical area worksheet.

The search date type specified was not a valid value. Valid values are 'gradingpricing' and 'statarea'.

Retry after making sure the extract detail type is specified correctly.

2160 ERROR: The IFQ Reported Manually checkbox for this report is checked, indicating the IFQ reports have been made.

The IFQ Reported Manually checkbox indicates that IFQ reports were made by contacting the NMFS Data Technicians.

The IFQ Reported Manually checkbox for this landing report was checked, and you tried to generate or submit IFQ reports.

If you believe that the IFQ report for this landing has not been made, and thta the IFQ Reported Manually checkbox is checked in error, go to the Landing Report, Vessel, Permit, and Location Information page and uncheck the box. You can then generate and submit IFQ reports. However, if a manual landing was done with the NMFS Data Technicians then do not submit IFQ reports again. If the IFQ reports were already generated on this landing report go to the Edit IFQ Reports page and remove them.

2161 ERROR: A Logbook is already registered for vessel  ADFGNUM , Permit  FEDPERMIT  for the year  YEAR  where:  ADFGNUM  is The vessel ADFG number. FEDPERMIT  is The federal permit for the vessel. YEAR  is The earliest year allowed to be entered.

A logbook already exists in the database for the vessel and permit.

A duplicate logbook registration was received on the server.

Determine who registered the logbook and what machine it is stored on. Use that logbook to record log entries. If the logbook needs to be on a different machine, move the logbook XML file to the new machine to use with the logbook software there.

2162 ERROR: Logbook ID  ID  not registered where:  ID  is The unique numeric identifier for the operation.

Before a logbook can be used to record and submit data it must be registered with the eLandings system. 

A logbook report was submitted for a logbook that was not previously registered on the system.

Register the logbook and use the logbook ID assigned by the registration when submitting logbook reports.

2163 ERROR: Logbook Entry is already in the database

A logbook entry can only be submitted once. If changes need to be made to the logbook entry they must be submitted as amendments to that entry.

A logbook entry was received with an entry sequence number that was submitted for a logbook, and the data in the entry is differnent than the data previously submitted.

Resubmit the logbook data with the changes recorded as amendments. If you are using eLandings logbook software, contact eLandings support. If you are using other software, contact your technical support.

2165 SYSTEM ERROR: Logbook Entry Seq  SEQ  is missing from the database where:  SEQ  is The entry sequence number.

Logbook entries have a sequential number. They should never be entered in the database out of sequence or with a skipped number. 

A logbook entry sequence number that was less than the most recently entered sequence number was missing from the database.

Contact eLandings support.

2166 ERROR: Logbook Entry Seq  SEQ  is in the database as type  ACTUAL , not type  NEW  where:  SEQ  is The entry sequence number. ACTUAL  is The entry type for the entry already in the database. NEW  is The entry type for the entry received.

Once logbook entry is submitted it cannot be removed, only amended.

A logbook entry was received with an entry sequence number that is already in the database for a different entry type.

Resubmit the logbook data with the new entry with the correct sequence number. If you are using eLandings logbook software, contact eLandings support. If you are using other software, contact your technical support.

2167 ERROR: Logbook Entry Seq  SEQ  is in the database has type  DB  amendments, submitted data has  SUB  amendments where:  SEQ  is The entry sequence number. DB  is The number of amendments in the database. SUB  is The number of amendments submitted with the report.

A particular amendment to a logbook entry can only be submitted once. If another change need to be made to the logbook entry then another amendment is needed. Multiple fields can be changed in a single amendment, but once submitted, further changes must be recorded on a new amendment.

The number of amendments in the submitted does not match the number in the database. This could be caused by having previously submitted amendments, but not having processed the return data correctly.

If you are using eLandings logbook software, contact eLandings support. If you are using other software, contact your technical support.

2168 ERROR: Logbook Entry Seq  SEQ  is a new entry, but the data included amendments where:  SEQ  is The entry sequence number.

Elogbook entries can be amended after they are submitted, but should not have amendments when submitted for the first time.

A new logbook included amendments.

Submit the logbook entry, then amend it.

2169 ERROR: Page Number is required

The page number must be input.

A page number was not input where it was required.

Input the page number.

2170 ERROR: Page Number  PAGE  is invalid where:  PAGE  is The page number.

Page number must be between 1 and 999.

A non-numeric or out of range page number was input.

Check the page number and input the correct value.

2171 ERROR: No logbook entries found

Logbook pages require haul, set, or delivery entries, or both start and end of inactivity entries.

The logbook does not have entries yet.

Input entries.

2173 ERROR: No logbook entries found for dates  FROM  to  TO  where:  FROM  is The start of the date range. TO  is The end of the date range.

Haul entries, set entries, and a number of other entry types have dates. These are not the date of data entry, but indicate the date of the logged activity. Searches by date look for the date of logged activity.

The No entries were found with logged activity in the given date range.

Check the date range, and expand it.

2178 ERROR: Font Size is required

2179 ERROR: Font Size must be numeric

2180 ERROR: Font Size cannot be less than one

2181 ERROR: Font Size cannot be greater than  SIZE  where:  SIZE  is The file size in K bytes.

2182 ERROR: Tender Batch identifier is required

2183 ERROR: Tender Batch identifier is invalid

2184 ERROR: Tender Batch identifier is too long

2185 ERROR: Trip entry is required before other entries

2186 ERROR: Go Active date cannot be prior to the Voyage start date  DATE  where:  DATE  is The date entered for the announcement.

2187 ERROR: Gear deployment time not allowed before first trip entry start date

2188 ERROR: Comment Date is required

2189 ERROR: Comment Date is invalid

2190 ERROR: Comment Date cannot be in the future

2191 ERROR: Comment Date year must be four digits

2192 ERROR: Comment Date is too far in the past

2193 ERROR: No entry found for  DATE  where:  DATE  is The date entered for the announcement.

The logbook requires at least one entry for each date that the logbook is active. No entry was found for the specified date. A comment entry can be entered if there was no activity to log.

2194 ERROR: No entries found from  STARTDATE  to  ENDDATE  where:  STARTDATE  is The start date of the period with no entries. ENDDATE  is The end date of the period with no entries.

The logbook requires at least one entry for each date that the logbook is active. No entries were found for the specified date range. A comment entry can be entered for each date if there was no activity to log, or an inactive entry can be made for the start of the period, with an active entry added at the end of the period.

2195 ERROR: Tally Invoice is required

Tally invoice is required information and must be entered.  The system expects a whole numeric value between zero and 999999.

The tally invoice was not entered.

Verify the tally invoice, and enter the correct value.

2196 ERROR: Tally Invoice must be a whole number

The system expects a whole numeric value between zero and 999999.

Data other than numbers have been entered in the tally invoice field.

Verify the tally invoice, and enter the correct value.

2198 ERROR: Tally Invoice cannot be greater than  MAX_SIZE  characters where:  MAX_SIZE  is The maximum number of characters that can be stored in the database for the field.

The system does not allow tally invoice to be greater than 999999.  The system expects a whole numeric value between zero and 999999.

The tally invoice entered is greater than 999999.

Verify the tally invoice, and enter a valid numeric value, between zero and 999999.

2199 ERROR: A trip entry already exists with a start date of  STARTDATE  where:  STARTDATE  is The start date of the period with no entries.

The logbook trip entry provides a date for the start of the trip.

More than one trip entry was found with the same start date.

If the start date is incorrect, the entry should be edited or amended.

2200 ERROR: A go inactive entry already exists with an inactive date of  STARTDATE  where:  STARTDATE  is The start date of the period with no entries.

The logbook go inactive entry provides a date that is the start of a period with no entries. More than one go inactive entry on the same date has no meaning, the first such entry establishs the date as the start of the inactive period.

More than one go inactive entry was found with the same go inactive date.

No entry is needed, the inactive period already starts on the given date.

2201 ERROR: A go active entry already exists with an active date of  STARTDATE  where:  STARTDATE  is The start date of the period with no entries.

The logbook go active entry provides a date that is the end of a period with no entries. More than one go active entry on the same date has no meaning, the first such entry establishs the date as the end of the inactive period.

More than one go active entry was found with the same go active date.

No entry is needed, the inactive period already ends on the given date.