Chapter 14Troubleshooting by symptom
This chapter is one table that starts from what the technician sees, not from where the fault lies. For each symptom it gives what to check first, then the chapter with the detail. The problem tables at the end of each chapter are fuller than this one, and this table points to them.
14.1 The program and signing in
| Symptom | Check first | Detail |
|---|---|---|
| The browser does not open the program on the server | Has someone signed in to Windows on the server? Is the Server task running in Task Scheduler? | 4.3 How the program starts |
| The program opens on the server but not on another computer | Was the server opened to the network's devices? Is the network Private in Windows? | Chapter 5: Network, branches and Clarus Link |
| A message that the database is not running | The ClarusPrimePostgres service, and the free disk space | 4.6 When the database does not run |
| The program is slow | The database's size, its maintenance, and the server's memory | 4.5.2 Database maintenance |
| Sign-in refused with the right password | The account locks for 15 minutes after five tries | 11.4 A user who forgot their password |
| The administrator forgot their password | The emergency sheet and the recovery code | 11.6 An administrator who forgot their password |
| A strip at the top of every screen asks for the administrator's password | The first administrator has no password | 11.1 The first administrator |
| The program opens only to update | A required update's deadline passed | 9.1.1 A required update |
| The website's name cannot be changed, and the site tab offers to take a name again | The website service no longer has the site | 3.1.1 The laboratory's website |
| A message about the licence or the trial ending | The licence's state on its screen | Chapter 3: First run, licence, activation and moving it |
14.2 Printing and devices
| Symptom | Check first | Detail |
|---|---|---|
| The browser's print window opens instead of silent printing | Is the program running on that computer? Does this role have a printer? | 7.5 When the printer does not print |
| A blank label, or strange text instead of a barcode | The printer's command language | 7.2 Binding printers to their roles |
| A shifted label, or one of the wrong size | The resolution, the offsets and the calibration label | 7.3 Printing settings |
| An analyser's results do not arrive | The link state on the analyser's card, and the link log | 6.8 When results do not arrive |
| The analyser is connected and results are not filed | Held messages and unmapped codes | 6.4 Mapping the analyser's codes to tests |
| A network analyser stops reaching after the computer or network changed | The firewall rule, and how the network is classed | 6.3 The firewall and the network |
14.3 Data
| Symptom | Check first | Detail |
|---|---|---|
| The nightly backup was not taken | Was the program running at its time? The backup disk's space | 8.11 Problems and what to do |
| The backups card on the health screen says restore is not ready | The restore drill | 8.4.2 The restore drill |
| Lost data, or a damaged database | The last sound backup | 8.9 Restoring from a backup |
| The RealLab migration does not start, or is cut | The file and its form, and the server's memory | 10.6 When a migration stumbles |
| Moving the laboratory to a new computer | A backup, then installation, then restore | 8.10 Moving the laboratory to a new computer |
14.4 Updates and language
| Symptom | Check first | Detail |
|---|---|---|
| The program finds no update although one exists | The internet, port 443, and the update-check setting | 9.1 How an update arrives |
| An update failed | The update's log | 9.5 The log and failures |
| The program does not start after an update | Do not touch updates\rollback; contact support | 9.4 Going back to the previous version |
| A member computer stops printing reports silently after the server's update | Has the member updated? | 9.3 Member computers |
| English texts on a screen in another language | The language pack's version | 12.4 When a language stumbles |
14.5 When this is not enough
Send the status report to support from Health and diagnostics, or ask for a remote support session (see 13.3 The status report to support).