Projects or instruments missing or incorrect
Product: Test Services for OpenLab CDS Audience: OpenLab CDS administrators
Symptom
A verification run behaves unexpectedly because the Test Services project or the Test Services instrument is missing, renamed, or changed. You typically observe one of:
- A run stops with an error such as
Test Services cannot create Test Services Project. - The Connectivity Test reports
Failedshortly after an OpenLab CDS upgrade, while other tests pass. - The Test Services project or instrument is missing from the Control Panel, or one of them was edited by hand.
Test Services manages its own project and instrument automatically, so in normal operation you do not create or maintain them. A run that fails on the project or instrument usually means one was removed or modified, or that an upgrade has not finished renaming it.
Confirm this is the right document
This page covers problems with the Test Services project and the Test Services instrument. Confirm the symptom before you continue.
- If a run reports
FailedorNot availablefor reasons unrelated to the project or instrument, see Results reported as not passed. - If the Workflow Test hangs at the
Starting sequencestep instead of failing, see Sequence hangs during the Workflow Test. - If a specific error string appears, look it up in Error messages first.
- Otherwise, continue here.
Affected services
OpenLab CDS continues to operate while you investigate. What is affected is the verification evidence: tests that depend on the project or instrument cannot run, so you cannot rely on the Summary report until the project and instrument are restored. Test Services recreates both automatically on the next run, so most problems resolve when you run the verification again.
Background
Test Services creates its project, named Test Services Project, on the first test run. During the Workflow Test it configures that project (folder paths, audit trails, and a custom sample parameter) and creates the Test Services instrument, a virtual instrument under the Test Services Instruments location. The instrument always uses the Test Services Project as its default project. If either the project or the instrument is deleted or modified, Test Services recreates it on the next run, so a one-time problem corrects itself when you run the verification again.
After an OpenLab CDS upgrade, the renamed instrument appears only when the Workflow Test next runs, not at install time. The Workflow Test removes the old-named instrument and recreates it under the Test Services name. Until then, a test that looks for the new name may not find the instrument.
Prerequisites
- You must have an administrator role for OpenLab CDS.
- You must have a role that includes the Manage project or project group privilege in OpenLab CDS, such as the Test Services User role.
- You need access to the Control Panel for the machine that produced the result.
Diagnostic steps
Work through these steps in order. Each step ends with a result table that routes you to the resolution.
-
Note which test reported the problem and read its result. (See Review the test Summary report.)
Result Next step The Connectivity Test failed right after an upgrade See Instrument not yet renamed after an upgrade. A run failed creating or reusing the project Go to step 2. The project or instrument was deleted or edited by hand See Project or instrument deleted or modified. -
Open the Control Panel and confirm that you can create a project with your current role.
Result Next step You cannot create a project See Insufficient privileges to create the project. You can create a project Go to step 3. -
Check whether the machine was renamed or the instrument controller re-registered since the last successful run.
Result Next step The machine was renamed or the controller re-registered See Machine renamed or controller re-registered. Nothing changed Run the verification again so that Test Services recreates the project and instrument. If the problem recurs, see Error messages.
Resolution
Project or instrument deleted or modified
Test Services recreates a missing or changed project or instrument on the next run, so you do not need to restore it by hand.
- Run the verification again. Test Services finds or creates the Test Services Project, restores its folder path if it was changed, and recreates the Test Services instrument during the Workflow Test.
- Do not edit the Test Services Project, its folders, or the Test Services instrument by hand. Test Services overwrites these settings on each run, and manual changes are replaced.
Instrument not yet renamed after an upgrade
After an upgrade, the Connectivity Test can fail because it still refers to the instrument by its previous name. Test Services renames the instrument only when the Workflow Test next runs.
- Run the Workflow Test first, then run the Connectivity Test. The Workflow Test renames the instrument, and the Connectivity Test then finds it.
Insufficient privileges to create the project
Creating the Test Services Project requires a role that can create projects in OpenLab CDS. If your role cannot, the run stops with a project error.
- Request that your administrator grant you a role that includes the Manage project or project group privilege, such as the Test Services User role.
- Run the verification again once the role is in place.
Machine renamed or controller re-registered
If a machine is renamed and its instrument controller is re-registered, the existing instrument keeps the old name and is no longer bound to a controller.
- Run the verification again. Test Services creates a new instrument that uses the new machine name as its prefix.
- Leave the old instrument in place unless your administrator removes it; Test Services does not reuse it.
Related documents
- The verification run: how a run uses the project and instrument.
- The OpenLab CDS Workflow Test: the test that configures the project and creates the instrument.
- Where results are stored: the storage paths for the Test Services Project.
- Results reported as not passed: diagnose Failed or Not available results.