Netware 4.11 - FILE LOCKS not releasing

Here's the situation:

Netware 4.11 server.  Client 32 (v2.1.1) on workstations.

In some instances, after a user has closed a file, the file is remaining locked under that user's login ID.  I can see that the file is open on the console.  If the user logs out, the lock is released and all is well.  

Anyone encountered this?  Anyone know of a fix for this?


Paul
psiessAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Chris RipollMaster of NoneCommented:
Could you elaborate on some specifics. ie. What application(s) cause the file locking? What OS is running on the desktop?

I have experienced file locking problems but only with one application.

Cheers - CR
0
psiessAuthor Commented:
There have been two cases in the last couple of days.  One is with mail on an MSMAIL post office.  The other application is EXCEL.

Desktops are running WIN95B.  

In excel, a user opened a file but it came up readonly.  When I checked the console, the file was open under that user's ID.  I had him log out and this cause the lock to be released.

In MSMAIL, the problem is a similar one.  EXCHANGE checks the post office for mail but there is a lock left on the mail file.  In some cases, users cannot send/receive email until they log out and log in again.  When this happens, other users cannot send mail to the user in question.

Paul

0
paulnicCommented:
Does the problem happen for same user on different PC?

Do the problem PC's use the current 32-bit NDIS (not ODI) NIC driver?

The following Novell tech document describes a case where a buggy ODI NIC driver caused a similar problem:
------------------------------------------------------
Files held open with DWClient32 2.2 & Xircom  (Last modified: 09JAN1998)

     This document (2933478) is provided subject to the disclaimer at the end of this document.
       
     Symptom

     PSC file is held open AND system login script NET$LOG.DAT is held open
     With PSC and the NetWare 3.12 LOGIN.EXE files that are normally closed (with earlier versions of the Client32) are not being closed and are keeping users from getting into Platinum Software and the administrator from modifying the login script from SYSCON. To get back into Platinum the users log out (which forces the file closed) and then they login again and at that point they can get back in. The modifying the login script is more troublesome, as the file is never closed when they login to the network until they log out unless I setup the client using a previous version of CLIENT32 or the VLM client.

     Troubleshooting

     Customer Configuration
     intraNetWare DOS Windows Client 32 (Client.nlm v2.2 970630).

     NET.CFG

     NetWare DOS Requester
        first network drive=f
        show dots=on
        name context="o=mc"
        network printers=9
        signature level=0
        checksum=3
        netware protocol=nds bind
        preferred server=mchoice

     link driver pmxmlid
        port 300
        int 10
        mem c8000
        frame ethernet_802.2

     Of course the site running 3.12 does not have NDS in the protocol section and a preferred tree or context.

     Cause

     I thought the problem was with all my Client32 workstations, but I've found out that only the notebooks using Xircom's 16-bit DOS ODI driver for PCMCIA NICs have the problem. There may be a problem with how Xircom designed their ODI driver, and after talking with Xircom they have said they are spending no further resources on fixing any of their "legacy" cards. I haven't yet tried to duplicate with other 16-bit ODI drivers to see if the problem continues with them.

     Solution

     Don't use the Xircom 16 bit Dos ODI Driver for PCMCIA Nic's with client32 2.20

                    Please select if this document solved your problem.

      Document Title:
                          Files held open with DWClient32 2.2 & Xircom
      Document ID:
                          2933478
      Creation Date:
                          06JAN98
      Modified Date:
                          09JAN98
      Document Revision:
                          1
      Novell Product Class:
                          NetWare OS
                          Novell BorderManager
      Novell Product and Version:
                          intraNetWare
                          NetWare 4.11 Kayak
                          NetWare 3.12
                          NetWare 3.2
                          intraNetWare Client CD (August 97)


0
CompTIA Security+

Learn the essential functions of CompTIA Security+, which establishes the core knowledge required of any cybersecurity role and leads professionals into intermediate-level cybersecurity jobs.

psiessAuthor Commented:
The problem we experience is not as specific as you have outlined.  I've seen more than one case where when  a user saves and closes and Excel file, the file remains open & locked under that user's ID.


0
saar2Commented:
I have to say that I saw this several times while access the Intranet webserver.

Saar Carmi.
0
paulnicCommented:
The problem may be less specific than the technote, but if you're using an ODI driver instead of NDIS on the PC, why not see if the change helps?
0
psiessAuthor Commented:
The clients are all using NDIS.

P

0
paulnicCommented:
Which NIC(s) are the clients using?
0
JBirkmannCommented:
Try the simplest things first:

flag all the files (XLS...) shareable, does the symptom still remain?
0
jwillekeCommented:
not sure when the change was made but there used to be a problem with the Client 32 and  not releaseing files. The Fix was to add the following to NET.CFG requester section.

TRUE COMMIT  ON
AUTO RECONNECT LEVEL 2 (or Less)






0
psiessAuthor Commented:
I can't really use that answer jwilleke!  :-)

Paul

0
paulnicCommented:
For what it's worth...can you try the settings that jwilleke mentioned, but in (right click) Net Neigborhood/Properties/Novell Client/Properties/Advanced, instead of NET.CFG?

Or have you tried 'em already?....

And by the way, what NIC(s) are the clients using?

Paul
0
psiessAuthor Commented:
My apologies to jwilleke...when I looked yesterday, the answer had no text in it.  I have made the change to my workstation and will monitor the problem.

Paul

0
brosenb0Commented:
You should be aware that the delayed closing of files is a design feature of client32.  The idea behind it is to speed up access to files that are repeatedly opened & closed by a given application by removing the NCP requests & subsequent latency associated with re-opening a file once it has been opened. The Net.Cfg NetWare DOS Requester parameter that controls this is: -
Close Behind Ticks nn
Where nn specifies the number of 'ticks' to delay closing the file after the close request has been received.
Default:  0 (no delay)
Range:  0 to 65535
Example:

NETWARE DOS REQUESTER

CLOSE BEHIND TICKS 36

There are approximately 18.21 ticks / second or 1090 / minute.

Other Net.Cfg NetWare DOS Requester parameters associated with this parameter are: -
Delay Writes
Cache Writes
True Commit

For more information consult ngwcfgdw.hlp that came with the Client32 requester.

Bruce.
0
psiessAuthor Commented:
The CLOSE BEHIND TICKS setting is set to 0 on my system, and yet files are still being held open.

Paul

0
jchapmanCommented:
Initially, My advice here would be to update your client installations to Version 2.2 available from Novell's Support Site - www.novell.com/download - this is after all what Novell would suggest. Hope this solves your problem
0
psiessAuthor Commented:
Even after upgrading the client on my workstation to Intranetware Client 32 v2.2, a file was still left hanging open.  This is not a consistent occurance.  It is random and intermittent.

Paul

0
Chris RipollMaster of NoneCommented:
I know this may seem silly but have you ruled out viruses. A friend of mine spent a week re-installing a NOS only to find a virus was causing his intermittent problems.

Long shot but who knows ?
0
jstegallCommented:
If none of the previous answers worked try replacing NOVELLNP.DLL
with the latest version found at:
http://support.novell.com/cgi-bin/search/patlstfind.cgi?2936259
if the version you are using is older than 9/25/97.
Explode the EXE file in you Client32 install directory and the
WIndows\system directory of the workstations that already have Client32 installed.
 

0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Novell Netware

From novice to tech pro — start learning today.