Reasons for Abort event

The following table describes typical reasons for "abort" events.

Error message	Description
Failed to abort run!	An instrument communication error happened during the start-up of an online ChemStation instance. This could be caused by an instrument or a single LC module hosting the LAN connection being powered off, a network cable being unplugged, or a wrong IP address being configured.
Initiated Abort Run, Option Selected: Abort All Run Queue Items	The user selected Abort in the Run Queue to abort all run queue items.
Initiated Abort Run, Option Selected: Abort All items submitted by current user	The user selected Abort in the Run Queue to abort all the user's items.
Initiated Abort Run, Option Selected: Complete current run and abort sequence	The user selected Abort in the Run Queue item to complete the current run and abort the sequence.
Initiated Abort Run, Option Selected: Abort current run	The user selected Abort in the Run Queue to abort the current run.
Instrument Run aborted	A user selected Abort in the Run Queue for the current run.
Method aborted	One of the following has occurred: Instrument power failure Persistent network outage A user selected Abort in the Run Queue A vial is missing Remote shutdown (via RS232 connector) Leak detected (or any other "instrument not ready" condition)
<Module type><Serial number> - Analysis aborted by another module	A module has aborted due to a different module in the modular LC system that aborted.
<Module type>:<Serial number> - Starting Analysis aborted via CAN	An LC run has been aborted. Applies only to older Agilent LC instrument firmware versions.
Privilege "Abort any running sample" was added/removed to/from role "<Role name>"	The privilege has been added or removed from a user role.
Queued item < Sample name> changed state to Aborted	A user selected Abort in the Run Queue for the current run.
Queued item <sequence name> changed state to Aborted	A user selected Abort in the Run Queue for the sequence. This message is generated by ChemStation's Run Queue.
Run Queue - Aborted sequence - <Result file name> - Abort reason < The reason for the abort>	One of the following has occurred: A sequence or a single run was stopped by clicking Stop Run in the Run Queue. An instrument hardware error occurred. For example, pressure beyond the pressure limit. A MS detector is missing a tune report. A vial is missing.
Run Queue - Aborted single sample analysis - <Result file name > - Abort reason < The reason for the abort>	One of the following has occurred: A sequence or a single run was stopped by clicking Stop Run in the Run Queue. An instrument hardware error occurred. For example, pressure beyond the pressure limit. A MS detector is missing a tune report. A vial is missing.
<sequence name> aborted by user	A user selected Abort in the Run Queue for the sequence.
Sequence: <Sequence name> - Aborted injection < Injection number> - <Data file name>.dx - Abort reason: <The reason for the abort>	One of the following has occurred: A sequence or a single run was stopped by clicking Stop Run in the Run Queue. An instrument hardware error occurred. For example, pressure beyond the pressure limit. A MS detector is missing a tune report. A vial is missing.
Single sample analysis: <Result file name> - Aborted injection < Injection number> - <Data file name>.dx - Abort reason < The reason for the abort>	One of the following has occurred: A sequence or a single run was stopped by clicking Stop Run in the Run Queue. An instrument hardware error occurred. For example, pressure beyond the pressure limit. A MS detector is missing a tune report. A vial is missing.
Tune operation is aborted	There is a communication error with a mass spec detector. This can be due to a power failure or network disconnection.