Results reported as not passed
Product: Test Services for OpenLab CDS Audience: OpenLab CDS administrators
Symptom
A verification run reports an overall result other than Passed. On the home page or in the Summary report, you see one of:
- Failed: one or more tests did not pass.
- Not available: the verification report could not be produced or stored (often a report-storage problem).
- Aborted: the run was stopped before it finished. Run the verification again.
The purpose of Test Services is to confirm that OpenLab software operates as expected, so a healthy deployment produces Passed. A different result means an administrator action may be needed.
Confirm this is the right document
Before you continue, check whether the symptom actually points to a different page.
- If the run finished but the report did not upload, and Last result shows Not available with an upload error, this is a report-storage problem. See Error messages.
- If a specific test shows an error string, look it up in Error messages first.
- Otherwise, continue here.
Affected services
The deployment itself usually keeps running while you investigate. What is affected is the verification evidence: until the run passes, you cannot rely on the Summary report as confirmation that the system is operating correctly.
Prerequisites
- You must have administrator access to the machine that produced the result.
- You need the Summary report from the run that did not pass.
Diagnostic steps
-
Open the Summary report and note which tests did not pass and their result values. (See Review the test Summary report.)
Result Next step A test other than the Connectivity Test shows Failed Go to step 2. The Connectivity Test shows Failed See Connectivity Test failed. A test shows Not available See A test is not available. -
Verify that the installed software was not modified. Run the Software Verification Tool that is installed with OpenLab CDS.
Result Next step The tool reports modified files See Corrupted files or an incompatible update. The tool reports no problems Go to step 3. -
Confirm that OpenLab CDS itself works: open the Control Panel, launch an instrument, and perform a run.
Result Next step OpenLab CDS fails to run See Corrupted files or an incompatible update. OpenLab CDS runs normally The test failure may be transient. Run the verification again.
Resolution
Corrupted files or an incompatible update
A Failed result often traces to modified OpenLab CDS files or to a Windows update that is incompatible with OpenLab CDS.
- Repair OpenLab CDS using the Software Verification Tool's findings as a guide.
- If a recent Windows update broke .NET Framework compatibility, identify the update and consider rolling it back.
Uninstalling a Windows update may have security or other implications. Before you uninstall, create a system restore point and confirm that you can restore the system to its prior state.
Connectivity Test failed
The Connectivity Test reports Failed when at least one component is not connected:
- When run against an AIC, Workstation, or Workstation Plus, at least one instrument is not connected. Reconnect the instrument and run the test again.
- When run against a Client, at least one AIC is not reachable from the client. Restore network access to the AIC and run the test again.
A test is not available
Not available is more common than Failed and does not by itself indicate a problem with OpenLab CDS. It appears when a test did not run to completion (for example, because a service restarted) or because the run was aborted. Run the verification again. If Not available recurs, confirm that OpenLab CDS operations are not impaired.
A project or instrument was changed
Test Services creates its project on the first test run and creates its instrument during the Workflow Test. If either is deleted or modified, Test Services recreates it automatically on the next run. A one-time failure caused by a missing project or instrument resolves itself when you run the verification again.