System Error Messages |
Top Previous Next |
The Error Display When working with The Auto Shop Writer, there will be occasions when the computer will display an error box, alerting the user to call MasterLink. It is vital that the exact error message be copied down, and then any key may be pressed to return the operator to the Windows Desktop.
Errors do occur. However, it must be realized that errors need to be addressed as soon as they occur, not several hours later. A small problem, if caught immediately, can be prevented from becoming a major problem.
Prolonged usage of the system after an error has occurred may lead to a total system failure, damage to the data files, and perhaps the necessity of completely restoring the system from a backup.
Error Messages The error system in The Auto Shop Writer will provide you with the nature of the problem and most probable cause. Solutions may be suggested. If you have an option to continue, and the failure re-occurs, exit the system, and then re-enter, trying the procedure again. The error system will print messages in a special pop-up box. There are some very common errors which you can resolve.
The Error Log Whenever your system has an error, it writes a lot of information to a file called error.log. It would certainly help if you send an email to support@mstrlink.com explaining what you were doing when the error occured, and then select error.log as an attachment to your message. This way our engineering staff can know exactly what took place in your computer when the error occured and provide you with a very accurate solution to the problem you have encountered.
General Windows Errors Operating system errors may be recognized because they usually have a message displayed at the top of the screen which always ends (A)bort, R)etry, Ignore). These are generated by the operating system, and have nothing to do with The Auto Shop Writer. Usually they indicate a problem with hardware.
Divide overflow Your processor has suffered a failure, either in its operation, or with a memory chip. Sometimes this is transitory, and rebooting (turning the power off, then on again) the system will clear the problem. However, this may also lead to a total failure of the computer. See your hardware technician for assistance.
Unable to access drive C Drive C (or any other drive) cannot be read by the system. This may be caused by a bad hard disk, or controller. If you are on a network, it may also indicate a network card, cable, or software failure. Before you panic, your drive may be salvageable. Hopefully, you have a great, recent backup.
There are several excellent utilities available that can recover a drive, or reformat it without even losing the data. Check with a systems expert before trying anything. Before your drive is replaced, an attempt to reformat the system should be made by a qualified technician.
Sector not found The computer expected to find a disk address that wasn't there. Its like the problem a postman faces when he needs to deliver mail to a house destroyed by a tornado. Again, several utilities can mark this spot, and clean up the problem. Consult your systems expert for a resource. This does not mean a major hardware problem in all cases - just a need to do some cleaning.
There are several utilities available to "optimize" a disk drive. These re-arrange all of the files so that all of their data is written sequentially, not fractured all over the drive (which is the result of normal operation). Optimizing your drive once a week, after that day's backup, is highly recommended.
Unable to write device prn Your printer is hiding. Usually this means that the printer is "off line" (check the light in front), or your cable has come loose. If this is not the problem, check to be sure someone didn't redirect the printer to another port. If all else fails, try the printer on another machine to see if it works. If so, you may have a defective printer port card - an inexpensive item to replace.
Otherwise, you may have a bad printer. Send it to the printer hospital for a quick repair.
CDX Errors The Auto Shop Writer utilizes index files to keep track of the location of certain records. These permit quick look-up of information. The .CDX error messages indicate an index has been damaged. The most likely cause of a "blown index" is someone turning off the power without exiting the program. However, power glitches, and computer "hiccups" can also create a problem. Also, if you receive an error message indicating "File Corruption", it may also be a blown index.
Your system will create a new set of indexes when you select the INDEX option from the Tools menu. You will not need to clear the old indexes, or perform any "recovery" process. The new indexes will contain all of the data necessary, and will be written over the old copies.
Record/file lock failure on xxxxxx -or- xxx.DBF(5) Your system tried to lock a record, or file, and found that it could not complete the task. This is usually because someone else has the file already locked. The system will try to lock the file, or record, 10 times. Then it will display this message. On a multi-user system, check to see who is using the file. Once they are finished, press RETRY, and you should gain access.
If this message occurs and you are sure no one is using the same file, then you may have a network locking difficulty. Some networks do not release the locks immediately when a file is released. Some also do not have 100% accuracy when releasing locks. In such a case you may have to quit, exit the program at all stations, and then power down the system, and bring it up again. The lock table is usually stored in memory in the server, and only is released when the power is turned off. |