|
Communications Status 006 - "Communications Not Available"
|
|
Problem: |
|
The following error message is displayed
while attempting to communicate through the modem:
Fatal Communications Error - Status
006.
Note: This might possibly be
accompanied by an Error 3261.
|
|
Solution 1: |
|
The most likely cause is that the Communications
Table in the Express database is locked. There are two likely possible
reasons for this.
-
This could be the result of a situation where
a user has inadvertently locked the communications status table due to a
system crash or GPF.
-
Another user on the network is using Express
and is in the process of communicating from their own workstation.
-
For network installations, check to make sure
that no user is in the process of communicating. Make sure also that no
users have Express minimized on their task bar with communications open or
with any unanswered system prompts (such as: Yes or No, or OK, or
Continue))
-
If no one is currently in communications, this
may be a situation where a user has inadvertently locked the table due to
a system crash or GPF.
-
Make sure all users are out of Express.
-
Log any users who have recently used Express
out of the network, and have them reboot.
-
Attempt to communicate again. If
unsuccessful, proceed to the next step.
-
Reboot the current user's workstation.
Then, attempt to delete the file: x:\EXPRESSW\DATA\EXPRESS.LDB
. If successful in deleting the file, attempt to communicate
again.
-
If everything else is unsuccessful up to
this point,
-
have the network administrator check for
user connections to the files: EXPRESS.LDB and EXPRESS.MDB.
-
Cancel any of those connections that are
active. (One customer we recently worked with found 16 connections to
the file EXPRESS.LDB, even though no users - according to them - were
currently in Express.) Canceling or ending these
connections is a function that your network administrator will have to
perform; as iiX Customer Support will not assist you with network
administration functions.
-
When the preceding steps have been
performed, try to communicate again.
|
|
Solution 2: |
|
Check to see if there are files in the \INBOUND
or \INBOUND\TMP directory located inside the Express for Windows home
directory (EXPRESSW or AMSEXPW) . If so, delete the files and try again to
run Express communications. Contact iiX Customer Support if you are missing
reports.
|
|
Solution 3: |
|
Check the CommModule= line in the
C:\WINDOWS\AMSEXPW.INI file to make sure it shows the correct path
to the communications driver file. For Example:
The MTW.EXE is the Windows based communications
driver and MT.EXE is the DOS based communications driver.
Make sure that the MTW.EXE and MT.EXE files do
exist in the Express for Windows home directory - \AMEXPW or \EXPRESSW.
|
|
This page has been viewed 13389 times | Document Rating is
-- /
5.00 | Last Updated on 4/28/2004 7:08:32 AM
|
|
|
