iiX Online Support - ExpressNet

Support Home • ExpressNet • Express for Browsers • Express for Windows • MVR Information • A-Plus™, Credit, UDI/UDV • Criminal History

Search

A "Decompression Error" Occurs While Receiving Reports

A "Decompression Error" Occurs While Receiving Reports

Problem:

Decompression error message is displayed after reports are received.

It may be helpful to determine if the problem is an ongoing one or if this is just an isolated case. If the problem is ongoing and happens every time reports are received, Suggestions 3, 5, 6 or 7 may be particular helpful. If the problem has occurred infrequently or this is the first time, work thru the entire list.

Suggestion #7 should be used only as a last resort. It presents special problems when updates are installed.

Solution 1:

Shut down and restart Windows.

On Windows 3.1 systems, if the user rarely shuts down the workstation, or if they enter and exit a lot of applications during the day, system resources become low. Restarting Windows releases these resources and frees memory.

Solution 2:

If this is a Network install, check to make sure that the user has all rights to the \AMSEXPW (or \EXPRESSW) directory and the subdirectories that reside under it, i.e. \INBOUND, \OUTBOUND, etc.

Solution 3:

Purge reports and requests. It has been noted that once there are more than 5000 reports and/or 1500 requests stored, this problem may occur. However, these numbers can be higher or lower depending on the amount of memory available on the PC, or how many other applications are open at the same time as Express.

It may also help to run a Repair and Compact of the database.

Select File and then Repair Database.
If Repair is successful, then Select File and Compact Database.

Solution 4:

For either a Standalone or Network installation, check the \AMSEXPW\INBOUND and \AMSEXPW\INBOUND\TMP directories for any stray files. If any files exist in these directories, delete them. If you are missing reports, contact iiX Customer Support to have the reports reloaded.

Solution 5:

Changing the access phone number and slowing the baud rate are at least worth a try. Alternate access numbers available at 2400 baud are: 800-709-6802 or 800-665-4274 or 800-299-1412 or 800-777-6877.

Solution 6:

If this is a network install, or if Windows NT is involved (either as the network or NT Workstation) and the user is on Express version 2.30b or earlier:

Request the latest version of Express for Windows. Express versions 3.00 and later include the RDCWIN.DLL patch for NT.

If the problem occurs with 3.00, and Express had been upgraded from 2.2x or earlier:

Check the date/time stamp on RDCWIN.DLL and make sure it is the 2-11-98 (or later) version of the file. This file is located in the \WINDOWS\SYSTEM directory.

Solution 7:

A workaround for Network installs:

Install Express to the network and make sure user has full rights to the \AMSEXPW (or \EXPRESSW) directory structure
Make sure to do any network flag commands to make the files shareable.
Install Express a second time as a Standalone on the system which does the communications.
On the Standalone station only, edit the AMSEXPW.INI file and point the DataDir to the Network copy of the database. Leave the other paths ( such as HomeDir, CommModule ) pointed to the local drive. This places the decompression process on a local drive rather than a network drive and seems to resolve some of these issues.

This page has been viewed 13343 times | Document Rating is -- / 5.00 | Last Updated on 4/28/2004 7:08:33 AM