Skip to main content

Sequence hangs during the Workflow Test

Product: Test Services for OpenLab CDS Audience: OpenLab CDS administrators

Symptom​

The Workflow Test stops making progress and never completes. On a domain-joined machine, the run stalls at a specific step and the progress indicator does not advance. You typically see:

  • The progress step Starting sequence <sequence> displayed for an extended time with no further updates.
  • No error message and no result, so the run neither passes nor fails.

A healthy Workflow Test moves through sequence creation, acquisition, and report steps within a few minutes, so a run that sits at one step is stuck rather than slow.

Confirm this is the right document​

This page covers a Workflow Test that hangs at the Starting sequence step on a domain-joined machine. Confirm the symptom before you continue.

  • If the machine is not joined to a domain and the test still hangs, the most likely cause is a faulty instrument controller. The Workflow Test now fails gracefully after about 3 minutes in that case rather than hanging, so update Test Services to the current version and run the test again.
  • If the test produces a result of Failed or Not available instead of hanging, see Results reported as not passed.
  • If a specific error string appears, look it up in Error messages first.
  • Otherwise, continue here.

Affected services​

OpenLab CDS itself keeps running while the Workflow Test is stuck. The Test Services Workflow Test cannot complete, so you cannot produce a Summary report that confirms the OpenLab CDS acquisition workflow operates correctly. Other tests in the run that do not drive an acquisition are not affected.

Background​

The Workflow Test drives a test acquisition on the OpenLab CDS instrument. To start and control a sequence, the Agilent Test Services service must act on behalf of the same Windows account that the Instrument service uses. When the two services run under different accounts, Test Services cannot start the sequence, and the run waits at the Starting sequence step.

Prerequisites​

  • You must have local administrative privileges on the machine where the test hangs.
  • You need the Windows account under which the Instrument service runs.

Diagnostic steps​

Work through these steps in order. Each step ends with a result table that routes you to the resolution.

  1. Confirm that the machine is joined to a domain and that the run stalled at the Starting sequence step.

    ResultNext step
    The machine is domain-joined and the run hangs at Starting sequenceGo to step 2.
    The machine is not domain-joinedSee the Confirm this is the right document section earlier on this page.

  2. Identify the Windows account that the Instrument service runs under. Open Services (services.msc), then open the Properties of the Instrument service and read the Log On tab.

    ResultNext step
    You have the Instrument service accountGo to step 3.
    You cannot determine the accountRequest that your IT team confirm the Instrument service account, then go to step 3.

  3. Compare that account with the account that the Agilent Test Services Service runs under. Open the Log On tab of the Agilent Test Services Service Properties.

    ResultNext step
    The two accounts differSee Service accounts do not match.
    The two accounts already matchThe hang has another cause. See the Confirm this is the right document section earlier on this page.

Resolution​

Service accounts do not match​

When the Agilent Test Services Service and the Instrument service run under different Windows accounts, reconfigure Test Services to use the same account, then restart it.

Important

The account may be a domain account or, on a workstation that is not joined to a domain, a local Windows account. Use the same account that the Instrument service uses.

  1. Log in as a Windows domain user who has local administrative privileges.
  2. Navigate to Control Panel > All Control Panel Items > Administrative Tools and select Services.
  3. Right-click Agilent Test Services Service and select Properties.
  4. Select the Log On tab, select This account, and enter the credentials of the account used by the Instrument service. Windows confirms that the account has been granted the Log On As A Service right.
  5. Click OK to acknowledge the message that the new logon name takes effect only after you stop and restart the service.
  6. Restart the Agilent Test Services Service.
  7. Run the Workflow Test again. The run now advances past the Starting sequence step.