MassHunter 4.6 for 7900 (G8403A) ICP-MS The batch stopped after 9 of 23 samples with the following error message. “Cannot access online Data Analysis application.”

“Cannot access online Data Analysis application.” 

Does this indicate a communication failure between the instrument and/or autosampler and the software?

Checked for any loose connections between the instruments, the ethernet lights are on the computer are active (flashing green for ethernet (yellow cable) [backup and login] and solid orange for the black ethernet communication cable to the instrument. Serial cable to the autosampler is tight. USB cable to the directly connected printer is also snug. 

So far the error appears idiopathic. Batch was repeated successfully. Any ideas what caused what appears to be a communication failure?

  • The error message “Cannot access online Data Analysis application” in MassHunter 4.6 for the 7900 ICP-MS could indeed indicate a communication issue between the instrument, autosampler, and the software. You’ve already done a thorough check of the connections, which is great. Here are a few additional steps you might consider:

    1. Software Settings: Verify that the software settings are correctly configured. In MassHunter, you can check the communication settings by clicking the Hardware icon, then selecting the Mainframe image. From the context menu, click Communication. Capture the instrument IP address and Host Name. If any discrepancies are found, correct them1.

    2. Firewall or Security Software: Ensure that there are no firewall or security software settings blocking communication between the instrument and the computer. Sometimes security settings can interfere with data transfer.

    3. Instrument Status: Check the instrument status. Are there any other error messages or warnings? It’s possible that an unrelated issue caused the communication failure.

    4. Software Reboot: Try restarting the MassHunter software. Sometimes a simple reboot can resolve communication glitches.

    5. Instrument Log Files: Review the instrument log files for any additional clues. These logs might provide more specific information about the communication issue.

    Since the batch was successfully repeated, it’s encouraging that the problem didn’t persist. However, if the issue recurs, consider contacting Agilent support for further assistance. They can provide specialized guidance based on your specific instrument setup and configuration2.

Was this helpful?