XP clients cause Access ldb file to bloat

[rjmccorkle]

We have a Netware 5.1 sp6 file server with an Access 97 database on it. New XP machines with the NW Client 4.90 are causing the .ldb file associated with the db to "bloat" showing multiple instances of the user. I found references to the problem from a year ago (Novell TID 10016657

http://support.novell.com/cgi-bin/search/searchtid.cgi?/10016657.htm

and Microsoft KB 236101

http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q236101

). They say the problem was with the client software and it had been fixed. Anybody know if it has become "un-fixed" and if there is a re-fix?
Thanks for any help.
Bob

 

[marvhuffaker]

You should probably make sure "SET Client File Caching Enabled = OFF" is set from the server, and you can turn it off from the client as well.

From the client, it's under the client properties ==> advanced settings ==> file caching. turn it off.

While you're at it, turn off level 2 oplocks on the server, it's available with SP6:

set level 2 oplocks enabled=off

I'm guessing between those settings, your problems will go away.




Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting

http://www.redjuju.com

 

[TheLad]

That's my chestnut! I never quite got the concept of file caching, it always seems to cause more bad than good! I remember reading that Lotus said you needed it switched on if you were accessing Notes configurations off the NetWare server, works ok with it off though??!??

-----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[marvhuffaker]

Thelad, Sorry, I jumped in there with your line before you had a chance.

I don't get file caching/oplocks either. Netware has always done an incredible job with file services before file caching/oplocks were introduced. So what gives? Why such a push to get oplocks to work? I've never talked to anybody that has actually used the settings in a production environment and not had problems.



Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting

http://www.redjuju.com

 

[rjmccorkle]

We have the
"SET Client File Caching Enabled = OFF" on the server (I learned that one 3 years ago from ThLad probably the first time I set up our server).
We tried the "set level 2 oplocks enabled=off" and it seemed to have no effect on the problem.
We just uninstalled the NW 4.9 client & installed the NW 4.83 sp2 client and the problem disappeared. Worst case, we can run around the building doing uninstalls & reinstalls. Do you know if there is any BIG reason to use 4.9 rather than 4.83 sp2?
And thanks for the quick replies.
Bob

 

[marvhuffaker]

So far I have been very unimpressed with the 4.9 client.

I don't know what it might be that would cause your problems. But they've added so much new stuff to the 4.9 client that it's pretty much a whole new program. v4.83 was much cleaner.


Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting

http://www.redjuju.com

 

[terry712]

agree with 4.9 client - it sucks - not tried it with the patch
i still use 4.83 sp2 - it's solid

oplocks - honestly work no probs - as long as you nss3c is on
file caching still leave off but ops locks on

defuinately not on 3b - probs galore

only advantage i see with 4.9 is it works better with console1.3.6 but .5 is fine

 

[TheLad]

If memory serves, Novell have not messed up a client since 4.80 (or was it 4.81?) when everyone had big problems. Sounds like 4.9 is going the same way!!

-----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[LawnBoy]

I've got 4.9 on NT, W2K, and XP; no problems in the 2 months I've been using it (probably shoulda kept my mouth shut...).