Search

Express for Browsers - Communication Errors
 

Error 01 -  "File I/O error during inbound cleanup" - failure trying to delete files in \Inbound.

This could be caused by a corrupted file, a read-only file, or a problem with the user's rights to delete files.  Try deleting the file manually through DOS or Explorer.  If that is successful, try the communications again.  If the problem persists, and the software is installed on a network, load it as Standalone and see if that solve the problem.

Error 6 -  "Decompression Error" 

This could be caused by a corrupted report file that was received.  Try deleting the file from the \INBOUND folder through DOS or Explorer. Once the file has been deleted, try the communications again.   Note: If you get a decompression error there is SOMETHING in the \INBOUND or \INBOUND\TMPT folder. If you cannot see it through Explorer, you will have to access it in a DOS window to delete it.  Additional note: If the software is loaded on C: drive, to access the Program Files folder, you must type CD PROGRA~1 - unless they are using Windows 2000 - in which case CD PROGRAM FILES will work just fine.

Error 11 -  "Database error creating config.ams" - failure reading comm or modem settings from Access database.

This could be a problem with the EfB database (PLUS32.MDB).  Try modifying the modem settings slightly and save the changes.   This will force the program to update the database.  If there is a problem with the database, it should result in an error trying to save the changes.

Error 12 -  "File I/O error creating config.ams" - disk error while creating the new config.ams.

The problem is in creating a new CONFIG.AMS file.  (CONFIG.AMS contains the modem settings such as Com Port, baud rate, initialization strings, etc.)  The cause of the problem could be a corrupted CONFIG.AMS file, insufficient user rights to modify the CONFIG.AMS file, a CONFIG.AMS file that is locked by another user or is set to read-only status.  Try renaming the old CONFIG.AMS file to CONFIG.OLD.  Then start Express for Browsers and attempt to communicate.  The program will try to recreate the file. 

Error 13 -  "Unexpected exception" - some other error occurred while creating new config.ams, like out of memory.

This means something really unusual happened.   Think weird - like out of memory, out of disk space, virus checking conflict, water in the disk drive.  Try renaming or deleting the existing CONFIG.AMS file. Try closing all other applications,  rebooting, or - as a last resort - running in Safe Mode.

Error 21 -  "Database error writing <service name> requests" - error reading or flagging Access database.

This would seem to indicate a problem reading requests from the database ( PLUS32.MDB ).  Delete any files in the \INBOUND and \TMP and \OUTBOUND folders, and then have the user try to send the requests again.  If unsuccessful, have the user delete files in \OUTBOUND, and delete any requests that are being sent,  then re-enter the requests and try sending them again.  If still unsuccessful, try running the Repair and Compact function in the Control Panel | ODBC 32-bit . Additional info: Make sure that the user has rights (if this is a network installation). Make sure the database is not marked as Read-Only.  Make sure that another user does not have something locked - by having everyone who has accessed EfB log out and reboot.

Error 22 -  "File I/O error writing <service name> requests" - disk error writing request file.

The outgoing file request file may be corrupt, or EfB cannot create the outgoing request text file.  Make sure that all of the communications directories exist - \INBOUND, \INBOUND\TMP, and \OUTBOUND.  If they do, then delete any files in the \OUTBOUND folder and have the user try to communicate again.  If unsuccessful, have the user delete files in \OUTBOUND, and delete any requests that are being sent,  then re-enter the requests and try sending them again.    Note: It is possible this could also be due to insufficient network rights or out of disk space.  Basically, the program is experiencing difficulty in writing the outgoing requests to a temporary file in the \OUTBOUND directory - for what ever reason. 

Error 23 -  "Unexpected exception writing <service name> requests" - some other error occurred, like out of memory.

This means something really unusual happened.   Think weird - like out of memory, out of disk space, virus checking conflict, water in the disk drive.  Try renaming or deleting anything in the \OUTBOUND folder. Try closing all other applications,  rebooting, or - as a last resort - running in Safe Mode.

Error 31 -  "Unable to run mtw.exe" - error launching mtw.exe.

Sounds like MTW.EXE is either missing or corrupt.   Verify that it exists (in the \EfB directory) and, if so, rename it.   Reinstall the Express for Browsers CD.  (Note: Re-running just the workstation setup will not replace the file)

Error 32 -  "Communications unable to connect" - this will cause a retry, it results from mtstatus.002.

This probably indicates that EfB exhausted all it's retries and did not establish a connection.  You want to verify that the modem is actually dialing, that you can hear the phone ring, and that you can hear their modem and ours connecting (whistle, crash sound).  Troubleshoot accordingly.

Error 33 -  "Communications unable to maintain connection" - this will cause a retry, mtstatus.003.

This indicates that EfB was able to establish a connection, but was unable to hold it.  It may have failed while logging in or while uploading and downloading request/reports.  Make sure your using the right modem profile, baud rate, phone numbers, etc.

Error 34 -  "Fatal Communications Error, check communications log.

If the error occurs immediately, it usually means that either the modem driver is in use, or that there is a problem with the comport, irq, or protocol setting.  If it occurs after the modem has dialed and tries to connect, it could be a wrong password, an account on hold, or it could be a modem configuration issue.  After checking the password and the account status, troubleshoot the modem profile, baud rate, phone number, etc.   Special Note:  Express for Browsers versions 4.00 - 4.03 had Errors 34 and 35 reversed.  Make sure which version you are dealing with!

Error 35 -  "User interrupted communications." - mtstatus.005.

The user cancelled the communications session. Special Note:  Express for Browsers versions 4.00 - 4.03 had Errors 34 and 35 reversed.  Make sure which version you are dealing with!

Error 36 -  "Communications ended without creating status file." - no mtstatus file.

This error would most likely result when something blocks the creation of the MTSTATUS.* file. (The * represents the file's extension - for example MTSTATUS.001, MTSTATUS.004, etc.)  Delete any files in the \EfB directory that are named MTSTATUS (any extension).  Check user rights.  If the software is loaded on a network, try loading it standalone and see if that cures the problem.  If so, something on the network is keeping MTW.EXE from creating the MTSTATUS.* file.  Note: We have encountered one instance where EfB was unable to create the MTSTATUS.* file on a network drive, necessitating that communications be moved to a local drive.

Error 37 -  "File I/O error during communications process" - failed deleting logfile.ams or mtstatus.*.

Express for Browsers creates both MTSTATUS.*** and LOGFILE.AMS during every communications session.  While doing so, it also deletes the old copy of the file.  If EfB is unable to delete either (or both) files, this error will occur.  Try renaming or deleting the files:  LOGFILE.AMS or MTSTATUS.*     (where the * represents the file's extension - for example MTSTATUS.001, MTSTATUS.004) and then communicate again..  If unsuccessful, make sure network users have sufficient network rights.  Then, make sure the file is not locked by another user. (You may have to reboot anyone who has been in EfB.)   Note: We have encountered one instance where EfB was unable to create the MTSTATUS.*** file on a network drive, necessitating that communications be moved to a local drive.

Error 38 -  "Unexpected exception during communications" - other errors, like out of memory.

This means something really unusual happened.   Think weird - like out of memory, out of disk space, virus checking conflict, water in the disk drive.  Try renaming or deleting the existing LOGFILE.AMS file and MTSTATUS.* file.. Try closing all other applications,  rebooting, or - as a last resort - running in Safe Mode.

Error 39 -   This is the "retry" code, it should not appear as an error.
 

Error 41 -   "Database error loading <service name> reports" - Access error. 

This would seem to indicate a problem writing reports to the database ( PLUS32.MDB ).  Delete any incoming files in \INBOUND and \TMP and have the user try to receive the files again. (Reset the files or reports using Growth Plan or FRPT.) If unsuccessful again in receiving the reports, try running the Repair and Compact function in the Control Panel | ODBC 32-bit . Make sure that the user has rights (if this is a network installation). Make sure the database is not marked as Read-Only.  Make sure that another user does not have something locked - by having everyone who has accessed EfB log out and reboot.

Error 42 -   "File I/O error loading <service name> reports" - disk error reading report or deleting file.

The incoming file may be corrupt.  Delete any files in \INBOUND, reset the reports, and have the user attempt to download them again.   It is possible this could also be due to insufficient rights or out of disk space.

Error 43 -   "Unexpected exception loading reports" - other error, like out of memory.

This means something really unusual happened while EfB was loading reports that had been received.   Think weird - like out of memory, out of disk space, virus checking conflict, water in the disk drive.  Try renaming or deleting files from the \INBOUND and \TMP folders and resetting (FRPT or whatever) the reports. Try closing all other applications,  rebooting, or - as a last resort - running in Safe Mode.

Error 44 -   "Database error loading state edits" - Access error loading state edit file.

An error occurred when EfB attempted to install a new STATEDIT.TXT file.  Start by deleting all incoming files from the \INBOUND and \TMP folders and then communicate again. Try repairing and compacting the database (PLUS32.MDB) using the tools in Control Panel | ODBC32-bit. Additional info:  Make sure that the user has rights (if this is a network installation).   Make sure the database is not marked as Read-Only.  Make sure that another user does not have something locked - have everyone who has accessed EfB log out and reboot.

Error 45 -   "File I/O error loading state edits" - disk error on statedit.txt.

EfB is having trouble accessing or reading a STATEDIT.TXT file that was received.  The file could be corrupt. Delete any files from \INBOUND and \TMP and try communicating again.

Error 46 -   "Unexpected exception loading state edits" - other error, like out of memory.

This means something really unusual happened.   Think weird - like out of memory, out of disk space, virus checking conflict, water in the disk drive.  Try renaming or deleting any files in the \INBOUND and \TMP folders and then communicate again. Try closing all other applications,  rebooting, or - as a last resort - running in Safe Mode.

Error 47 -   "Database error loading misc edits" - Access error.

An error occurred when EfB attempted to install a new MISCEDIT.TXT file.  Start by deleting all incoming files from the \INBOUND and \TMP folders and then communicate again. Try repairing and compacting the database (PLUS32.MDB) using the tools in Control Panel | ODBC32-bit. Additional info:  Make sure that the user has rights (if this is a network installation).   Make sure the database is not marked as Read-Only.  Make sure that another user does not have something locked - have everyone who has accessed EfB log out and reboot. One last possibility - this one we have actually seen.......  It is possible that iiX has made a change to the account's  Billing Code file and that that is causing the error.  This can be tested by downloading the MISCEDIT.TXT file for the agency from one of our lab systems.

Error 48 -   "File I/O error loading misc edits" disk error on miscedit.txt.

EfB has received a new MISCEDIT file during communications and is unable to read it or process it.  This may be due to corruption of the file.  Try deleting the file from \INBOUND or \TMP.

Error 49 -   "Unexpected exception loading misc edits" - other error, like out of memory.

This means something really unusual happened.   Think weird - like out of memory, out of disk space, virus checking conflict, water in the disk drive.  Try renaming or deleting any files in the \INBOUND and \TMP folders and then communicate again. Try closing all other applications,  rebooting, or - as a last resort - running in Safe Mode.

This page has been viewed 13725 times | Document Rating is  3.50 / 5.00 | Last Updated on 4/28/2004 7:08:23 AM