| Title | We don't tell people to use the Windows event log |
| Status | closed |
| Priority | essential |
| Assigned user | Richard Brooksby |
| Organization | Ravenbrook |
| Description | TeamTrack's error reporting to the API is very poor, and often we can't tell what went wrong. It tends to write some information to the Windows event log, but we don't tell people to look there. |
| Analysis | We should tell people about TeamTrack's poor error handling and suggest that they enlarge their event log (or set it to "overwrite as needed" perhaps) when they install. We should tell people to look at the event log when the replicator reports certain errors, to find out what's going wrong. We should update the code to tell them to look at the event log as well, as part of the error message written to our log, whenever the TeamShare API throws an vague error. |
| How found | manual_test |
| Evidence | <http://www.ravenbrook.com/project/p4dti/doc/2000-10-30/mahi-alpha-test/> item 16 |
| Observed in | 0.3.2 |
| Created by | Richard Brooksby |
| Created on | 2000-11-22 12:21:20 |
| Last modified by | Gareth Rees |
| Last modified on | 2001-12-10 19:02:12 |
| History | 2000-11-22 RB Created from sources. |
| Change | Effect | Date | User | Description |
|---|---|---|---|---|
| 5175 | closed | 2000-11-30 14:36:32 | Richard Brooksby | Telling the administrator to check the Windows event log when things go wrong, because the TeamShare API doesn't tell the replicator about errors. |