Error messages and what they mean

Some of these error messages will never cross your screen.  But for those that do, here’s what they mean and maybe a hint as to where to start looking for a correction.

  • Abbreviation cannot be null – Abbreviation must be either the 5 character quad abbreviation or the 5 digit county FIPS/block ID combination.
  • Agency cannot be null – You must use the same agency abbreviation as used in sites generation.
  • Cannot have omit reason with Delta or MC – Either the trap type or the omit reason must be changed.  Use trap type “O” for Omit.
  • Cannot inspect an omitted site – An inspection record was submitted for a trap reported as omitted at placement.  If this trap is actually in the field, please contact your database manager.
  • Catch inappropriate for condition – If trap condition is “Missing” or “Inaccessible”, you cannot report a catch.  If it was “Good” or “Damaged”, you must report catch.
  • Condition cannot be null – Enter missing, inaccessible, good or damaged based on the trappers’ notes.
  • Contractor cannot be null – Enter the initials of the trapper responsible for this bid unit.
  • Duplicate Inspection – Same state, abbreviation, site, day combination has already been entered.
  • Duplicate Omit – An omit record has already been submitted for this state, abbreviation, site combination.
  • Duplicate Placement Omit – A placement record has already been submitted for this state, abbreviation, site combination.
  • Duplicate Random Placement Omit – A random placement record has already been submitted for this state, abbreviation, site combination.
  • Duplicate UTMs – A site with this easting, northing and zone already exists.
  • Duplicate bid unit – Information for this bid unit has already been entered.
  • Duplicate inspection – An inspection record has already been submitted for this state, abbreviation, site, day combination.
  • Duplicate record ID – This should not happen during normal data flow.  If it does, contact your database manager.
  • Duplicate trapper – These initials are already in the database for this state.
  • Duplicate trapper ID – This should not happen during normal data flow.  If it does, contact your database manager.
  • Easting cannot be null
  • Elevation cannot be null – If you don’t know the exact measure, enter something close.  For gadget users, don’t worry about reproducing a signal strength code.  Contact your database manager with questions.
  • Entry Type cannot be null – Entry type must be GPS, Gadget or Manual.
  • Date cannot be null
  • Field date is later than load date – Check the field date.  No time traveling allowed.
  • First Name cannot be null – This should not happen during normal data flow.  If it does, contact your database manager.
  • ID cannot be null – This should not happen during normal data flow.  If it does, contact your database manager.
  • Inspection at omitted site – Inspection record submitted for a site that was reported as omitted at placement.
  • Invalid Entry Type - Entry type must be GPS, Gadget or Manual.
  • Invalid QC failure reason – Failure reasons must be typed in full text when using the web based error correction interface
  • Invalid Visit type – Visit must be Midseason or Final.
  • Last Name cannot be null – This should not happen during normal data flow.  If it does, contact your database manager.
  • Load Date cannot be null - This should not happen during normal data flow.  If it does, contact your database manager.
  • No Placement match found – A placement record with this state, abbreviation, site combination cannot be found.  Either check the information in the inspection record, or send in the appropriate placement record.
  • No site node found – A predetermined site node with this state, abbreviation, site combination cannot be located in the database.
  • Northing cannot be null
  • Omit Reason Invalid – Omit reasons must be typed in full text when using the web based error correction interface and must be one of the reasons known to the database
  • Omit Reason cannot be null
  • QC catch must be zero – Usually catch reports are done by the trapper.  If catch MUST be reported by a QC inspector, please create an additional regular inspection with this information.
  • Site cannot be null
  • State cannot be null
  • Supervisor ID cannot be null – This should not happen during normal data flow.  If it does, contact your database manager.
  • Trap Type cannot be null – Must be Delta, Milk Carton or Omit.
  • Trapper cannot be null – Enter the trapper’s initials
  • Trapper does not exist – Trapper initials must be entered into the database before field data are submitted.
  • UTM Zone cannot be null
  • Validation Date cannot be null – This should not happen during normal data flow.  If it does, contact your database manager.
  • Visit cannot be null – Must be either MIDSEASON or FINAL.

   
  © 2012 Slow the Spread Foundation, Inc.  

Page developed and maintained by Virginia Tech

  Contact Us