Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Anybody experiencing Record Locking Problems in NetWare
Message
From
04/10/1997 13:45:08
 
 
To
03/10/1997 12:02:18
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00052955
Message ID:
00053262
Views:
25
Eric,

It seems hat the problem might be with NetWare's 32 bit client. Here's what I found and the Novell site:
======
======
Q: I am having problems with database and mail programs when using
Client 32. What can I do to troubleshoot the problem?
A: There have been reported cases of problems with some applications
that do record locking. To verify whether the issue is with the Client,
Go to Control Panel | Network. Select Client 32 and choose Properties.
Now select Advanced settings and select Opportunistic Locking. Turn this
parameter OFF (the default is ON) and restart the machine to verify if
this is the issue.

======
======

Q: When the Win95 file locking patches will be released?
A: The Novell Client32 for Windows 95 v2.11 or later addresses file
locking issues.

======
======

Issue

This summary TID compiles the different problems that have been
seen between the Client 32 for
Dos/Windows and the Client 32 for Windows 95 (they will be referred
here as "the Clients 32")
and NetWare 3.11 servers. It is divided into two sections :

- Problems related to the SHORTAFX.NLM
- Other problems

Make sure that the latest version of the NetWare Client 32 for
Windows 95 has been installed on
the workstations. The latest file updates for the Client32 for
Windows 95 can be found at
http://support.novell.com/

1. Problems related to the SHORTAFX.NLM

The SHORTAFX.NLM is a patch which is shipped with the Clients 32
(it can be found in the
Admin\Patches\NW311 directory) and which should ALWAYS be applied
to the NetWare 3.11
servers in order to have them working properly with the Clients 32.

2. Other problems

- When reading and forwarding mail with Client32 for Win95, the
CCMAIL database would
become corrupt on the 3.11 server. Disabling packet burst, and
opportunistic locking didn't
solved the problem. SOLUTION : Customer applied the 3.11 patch set
from 311PTD.EXE and the
problem went away. The patch that seemed to resolve the problem was
RPLENFX.NLM in
combination with disabling Opportunistic Locking. This problem is a
known issue with other
versions of NetWare but is not as easily reproducible on 3.12 and
4.1. Opportunistic Locking
should be disabled on all clients where CCMAIL and other Database
applications are being
used.


================================================================================
>I have not narrowed my problem to this specific cause, but I am having update conflicts with certain tables even though I am using RLOCK(). We are using Netware 3.12, and the tables are on the server. Please let me know if you find out more about this problem, it could clear a lot of things up for me.
Previous
Reply
Map
View

Click here to load this message in the networking platform