Maintains a list of Manager errors that occured over the course of its run-time.
Since all errors should be handled "elegantly", the Manager should never "crash". In the worst case, a single Client/Server connection is terminated.
Should you find this statement to be incorrect, please send us a bug report under Tracker/Bugs.
Icon | Description | |||
---|---|---|---|---|
Removes the selected error entry from the list | ||||
Empties the entire error list | ||||
Opens this page |
Title | Description | |||
---|---|---|---|---|
Icon (currently only for looks) | ||||
Error Message | Text describing the error that occured | |||
Time Stamp | Shows when the error happened |
Icon | Description | |||
---|---|---|---|---|
Write failed with error code 10045 | ||||
A Client/Server disconnected while data was pending | ||||
As far as the Manager is concerned this error doesn't matter. But it may mean that the Client/Server crashed unexpectedly as it disconnected even though it was supposed to receive more data. | ||||
Bind failed with error code 10048 | ||||
Cannot run Manager since port is in use | ||||
Make sure no other instance of LabRAD is running and that no other program is using the port given in the Server Configuration. | ||||
DoRead exception: Access Violation ... | ||||
Known rare bug in LabRAD Manager | ||||
Happens in rare cases instead of Write failed with error code 10045. Leads to disconnection of Client/Server who sent the data as well. See bug report #1 under Tracker/Bugs. |
Please report other errors to our bug tracker under Tracker/Bugs for assessment and inclusion in this list.
Icons: Silk Icons by Mark James (creative commons 2.5 attribution)
~ Markus Ansmann, Dec 12th, 2007