MSQuery hangs connecting to file on Netware server

[Michael Salem]

I hope this is not considered off-topic; I believe this is the only
Netware newsgroup here.

I have a problem with a number of machines connected to a Netware 3.12
server. The network generally works fine.

There are Paradox tables on the Netware server. The local machines are
running the Novell Client32 (one has the latest v4.90 SP2) and are
running Microsoft Office, and a system ODBC connection has been made to
the directory containing the tables. Data can be imported into a Word
mailmerge document so long as Microsoft Query is not invoked. But if an
attempt is made to access data via MS Query, the table name is displayed
with a "+" to expand the display to show the field names. On clicking
the "+", Query immediately hangs (Task Manager shows "not responding"
_immediately_, and the event log reports a hung application). The
Network directory is set to the server directory with Paradox lock
files.

No other machines were accessing the Paradox files at the time of the
tests.

So far I have tested this on workstations running under Windows XP, with
or without SP2, and Office 2000 with all patches.

I did try setting the Paradox file Netware Shareable attribute,
following a suggestion found on the Web, but it made no difference.

Many years ago I had what was probably a different problem with Windows
95, Office 95 or 97): it was impossible to access Netware server data
via ODBC, though local data was fine. I don't think the symptoms were
identical. On that occasion we stopped trying to access the data; months
later we tried again and it worked, possibly after installing new 3Com
NIC drivers.

I need to do more testing, but will post this now in case anybody has
had the same problem.

Best wishes,
-
Michael Salem

 

[Keith V. Klenke]

do you setup the client with ACU & tell it not to install nmas & for 3.12,
to install IPX only?

--
Thanks,
Keith V. Klenke
--------------------------------------------------
Hey everyone,
I just wanted to let you know there is a site that may be of some use. A
lot of people who work with Novell products, and are VERY good with
implementations and troubleshooting, frequent the site. You can find it at:
http://www.abend.org

 

[Michael Salem]

do you setup the client with ACU & tell it not to install nmas & for 3.12,
to install IPX only?

I install it manually from a CD or a network drive, generally without
NMAS (would this cause trouble?), IPX only, bindery connection.

The client works fine in all other circumstances (though there have been
occasional cases of corruption of MS Excel files which seem to improve
after updating everything in sight: operating system, client, office
software; removing MS QoS; file cacheing off, commit on).

In particular, ODBC works fine if we use MS Word's mailmerge with data
accessed directly (not via MS Query); the problem arises accessing the
SAME data via MSQuery.

Best wishes,