Error message number 1064 appears when your data bank is either of size 0 or corrupt. Verify the size of your data bank or use the E2XFBANK utility to verify its integrity (for example, e2xfbank -e intel intel emme2ban). Please note that an EMME/2 data bank of size 0 may exist if the creation process aborted.

Error message number 1066 usually appears when you try to access a data bank created on a different platform. Use the E2XFBANK utility to verify the data bank format, and to convert it if needed.

Error message number 4001 appears when the data bank you are accessing exceeds the limitation of your licence by having too many links, segments or centroids.

Error message number 4009 appears when the data bank you are accessing exceeds the limitation of your licence by having too many turns, nodes or transit lines.

This error happens when, during a calculation, a very small value that cannot be represented within the limitations of the computer representation, is used (the smallest value that can be represented is approximately 1e-38). It is not necessarily an indication of a serious problem but you should look carefully at your functions.

You may be using a data bank created with a larger licence or your data bank may be corrupt. This message only appears when using EMME/2 releases prior to 7.0.

The data bank cannot be opened for reading and writing as required for a normal EMME/2 session because it has already been opened by Module 1.31 from another EMME/2 session. When Module 1.31 opens an external data bank for an import operation, it is for reading only. In this case, the external data bank must be protected from modifications. However, several users can access the same external data dank for reading only.

Error message number 1065 appears when EMME/2 is not able to access the data bank in READ-WRITE mode. If you are accessing the data bank via a network, verify that this file has the correct permissions. A data bank copied from a CD-ROM, may be READ only. To check that the data bank has READ-WRITE permissions, use the command attrib emme2ban in the directory where the data bank is located. If the result is:

the data bank is READ-ONLY. Use the following command to enable READ-WRITE access:

EMME/2 generates the ERR* IO - 30... message when at least one of the files (errors, reports, plots, etc., or any file name defined in the flexible file naming system) used by EMME/2 has READ-ONLY permission. EMME/2 requires these files to have READ/WRITE access. It is possible to correct the situation by using the DOS command attrib -r in the data bank directory. This will change all file permissions.

Only one user at a time can access an EMME/2 data bank and a lock file (locki) in the application environment is used to ensure this. At the beginning of an EMME/2 session, EMME/2 tests for the existence of a lock file in the application environment. If one is found, the procedure exits with the message: Data bank already in use! If no lock file is found, one is created at the beginning of the session and is deleted when EMME/2 terminates (if variables %HOST% and/or %USER% exist, their values are recorded in the lock file). If an EMME/2 session terminates abnormally (power off, reset or control-alt-del), the lock file may not always be deleted. In this case, delete the lock file before calling emme2. Check that no EMME/2 session is in progress before deleting a lock file.

Error message number 1065 appears when EMME/2 is not able to access the data bank in READ-WRITE mode. This may happen when the data bank is accessed by different users who do not belong to the same group and have a file-creation mode mask which does not give access to everyone. Verify that you have access to the emme2bank file by using the following command in the directory where your data bank is located:

If the file is accessible (READ/WRITE) for everyone, the result should be:

If the file is not writable for everyone, the permissions must be changed using the following command:

This command can only be used by the owner of the file or by the system administrator.

Note that files errors, plots, reports and batchout should also have READ-WRITE access.

This message appears on SUN computers if file is not writable (where file can be usemacro, errors, reports, plots, batchout or a file name specified via the flexible file naming feature).

This message appears on HP-UX computers if file is not writable (where file can be usemacro, errors, reports, plots, batchout or a file name specified via the flexible file naming feature).

This message appears under AIX if file is not writable (where file can be usemacro, reports, plots, batchout or a file name specified via the flexible file naming feature).

This message appears under AIX if the file errors is not writable. This file is created by EMME/2 and the protection is set according to the user's umask.

This message appears if the file nextmod is not writable. This file is created by EMME/2 and the protection is set according to the user's umask.

Only one user at a time can access an EMME/2 data bank and a lock file in the application environment is used to ensure this. At the beginning of an EMME/2 session, EMME/2 tests for the existence of a lock file (locki, bank being used interactively; lockb, bank being used in batch mode) in the application environment. If one is found, the procedure exits with the message: Data bank already in use! If no lock file is found, one is created at the beginning of the session and is deleted when EMME/2 terminates (user name, terminal ID, and session start time are recorded in the lock file). If an EMME/2 session terminates abnormally, the lock file may not always be deleted. In this case, delete the lock file before calling emme2. Check that no EMME/2 session is in progress before deleting a lock file.