User guide
Appendix 2: DEALING WITH PROBLEMS
Introduction
This Appendix is intended to help you to sort out the problems that you are
most likely to have with FileStore. In the initial stages at least, you will
probably deal with a number of problems that arise through the users' (or
your) unfamiliarity with FileStore and its commands.
Error messages
FileStore will usually try to help you understand what is going wrong, by
displaying a short message (called an 'error message') that describes the
source of the problem, such as
Di sc full
or No
c lock.
These error messages are listed in alphabetical order later, together with a list
of suggestions of what to do.
Sometimes, FileStore will not be able to produce this help — for example, if
somebody turns it off by mistake. Also included here is useful advice on
diagnosing and fixing problems when there is no error message to help.
Minimising
There are two fairly simple steps you can take to minimise the number of
problems
problems you have and their impact on you:
—
Take backups of all files on a regular basis.
—
Read this guide and try to make sure that the users read the relevant parts
of their user guides. The better you (and they) understand how to use
FileStore, the fewer problems you should have.
If you cannot resolve a major operational problem by using the information
here, or if particular problems recur frequently, contact your supplier for
help.
Problems without
Symptom: FileStore won't startup
error
messages
Check that FileStore is plugged in properly. Check the mains socket by
plugging something else into the socket and trying that. If the socket is ok;
the fuse in the mains plug may be blown or there may be a more serious
electrical fault. Contact your supplier for help.
Symptom: can't access FileStore
Check that your Communicator has been configured to use the right
FileStore number, by using the Configure task. If there is only a single
FileStore on the network, the FileStore station number should be configured
Appendix 2: DEALING WITH PROBELMS
59