# Other System Errors

Cannot Open File

Example:

C:\fp50\filepro\test: No such file or directory

Error occurs when the parent \filePro directory is missing or a filePro sub-directory is missing or invalid. Check your path environment settings and make sure that the \filePro directory exists for the path specified by PFDSK and PFDIR or the values in fppath.

Memory could not be read from

This error occurs in Windows and indicates that a file is invalid. These errors are sometimes difficult to isolate but if approached logically can be resolved. Make a note of the error and what menu option this error occurs on e.g. Define Files, IUA, Request Output, etc.

Examples:

When using Define Files you receive the following error.

The Instruction at 00401128 referred memory at ffffffff the memory could not be read from. This program has performed an illegal operation and will be shutdown.

The above error is probably due to an invalid MAP file. Somebody may have inadvertently revised the MAP using a non-filePro editor or you may have had a disk error that corrupted the map. Restore the MAP and MAP.TMP from a backup and try again. If you don't have a backup, try copying MAP.TMP to MAP after renaming MAP to something else like MAP.OLD.

Note: An invalid local edits file can also cause this type of error in Define Files since the local edits table is accessed when defining a file. Try renaming the EDITS file to EDITS.OLD to isolate as to whether the map or edits file is the problem. If renaming the EDITS file solves the problem, print the EDITS file using a text editor and reenter your local edits for this file.

If you get the "Instruction error" when defining local edits, the problem can be due to an invalid MAP file or invalid EDITS file. Try renaming the EDITS file to EDITS.OLD and go to the Define Files option. If you still get the error, you have an invalid map file. Go to above section and resolve the map problem.

If you get the "Instruction error" when using Inquire/Update/Add or "Request Output", these are the most difficult to resolve and can be due to any of following. Use the following chart to isolate your problem.

Problem | Process
Environment not properly set. | Isolate by determining if the error occurs on more than one file or all files. If the error occurs for all files, check your environment settings and try again. Refer to setting path environment variables.
Corrupted Index | Try removing all indexes and rebuilding one at a time until the error re-occurs. Make sure that you are using the same versions of the index maintenance program, *clerk and *report. Contact filePro sales if the version numbers are different.
Corrupted key or Data file | Use the fpCopy utility to create a duplicate file using "Copy formats only". Try entering data into the new file. If you are able to enter data into the new file, you more than likely have a corrupted key or data files.
Corrupted edits file | Rename the edits file to edits.old or edits.sav and try to define files. If you cannot view the map with the Define Files option, the problem has been isolated to the map file. If renaming the edits solves your problem, print the edits.old or edits.sav file using a text editor and re-enter the local edits for the filePro file.
Corrupted map file | Use fpCopy to copy the file without data e.g. "Copy formats only". If you cannot copy the map file, it is corrupted. If you are able to copy the map file, try entering data. If you cannot enter data into the new file, you probably have a corrupted local edits file. Follow the procedure for correcting a corrupted edits file.
Divide by 0 | Divide by zero "/D0" is caused by invalid math expressions that include a zero as a divisor. This can also be caused by attempting to use a string as a divisor. Make sure that fields used in math formulas use numbers and not strings and divisors are not equal to zero.
Overflow | "/OV" is an overflow when attempting to use an invalid date or date math expression. If PFCMARK has not been properly set, some 2 digit years will not be considered as valid and will create this error.
Error Expanding File | This error may appear if the data segment has been corrupted. You may also see "Error Reading Free Chain Pointer" meaning that filePro is having trouble finding the next free record due to the corrupted file. Restore a recent backup of your data prior to system failure.