We have three textbases in the following environment:

Server operating system: Win2K SP2
Client operating systems: Win XP and Win2K SP3
Network: TCP/IP
Recently upgraded to DB/Textworks 7.01
IE on clients: IE 5.5 SP2 and IE 6 SP1

When one user opens up a record for editing, and another user attepmts to get in that textbase, they get a "lock violation" error. If both users are already in the same textbase, then it's fine.

After talking with both our VAR and InMagic directly, we got all the clients and our server upgraded to Service pack 3, which is what we all hoped would solve the problem, but unfortunately it did not.

Everything within the database files themselves is sine--I even sent the files to Inmagic and they were unable to replicate the error.

At this point no one knows what to try next. So I thought I'd throw it out there to see if anyone else has faced this. I saw a couple of similar posts but nothing really the same as our problem.

Any replies greatly appreciated.

We've started encountering this same problem over the last two weeks. I was wondering whether you'd found a solution - we have no idea what to do and our IT section can't help us.

Regards

Fiona

Hi,

I hadn't checked the forum for a long time, and now see your message.

We have not resolved the issue. And no one, apparantly, can help us. I'd love to know if you've had any luck resolving, and will be happy to provide direct contact info. so we could chat.

Hello,

We're still experiencing this problem and I know of two other libraries in my region that have been trying to live with it for longer than us. Nobody seems to have a solution and I'm reluctant to spend more money on upgrades when it's not a definite solution to our problem. (We're on Version 6.01 and we're running on a Windows NT platform. Two of our PCs still run Windows 95 but as this problem still happens when they're not in use that doesn't appear to be the source of conflict.)

This is really a big problem--I'm glad to hear that we're not the only ones having it. We, too are reluctant to pay for a new contract for maintenance, and as I may have mentioned this sort of negates our multi-user license, since multiple users cannot in fact add records at the same time.

Whew! We finally got a fix to this problem!!

Our IT department sleuthed it out. There is something called "opportunistic locking" in Windows. You have to get into the Windows registry, so only a professional IT person should attempt!

The fix works for NT-class machines only. In our case, the fix was made to the clients only, NOT the server (since we didn't know how it might affect other applications.

Paste the following link into your browser to go to the Microsoft site:

http://support.microsoft.com/default.aspx?scid=kb;en-us;296264&Product=win2000 <http://support.microsoft.com/default.aspx?scid=kb;en-us;296264%26Product=win2000>

I hope this is the end of the problem, and it proved that there was never any problem with our server, in spite of InMagic's insistence that it was....

Thank you so much for sharing your discovery with us. Most problems are self-evident once you know what the answer is, but this one certainly isn't. This answer will be of huge benefit for Inmagic to know too, because there must be other libraries out there suffering in silence.

We'll know next week (when our IT support person is back at work) whether it works for us too, and we'll be passing this info on to the other libraries we know of who have this problem. It's been hell for us because we're spread over three locations so it has affected our ability to work in DbText really badly.

Your IT section deserves a medal for making DbText useable again.

I am wondering if any one is still having this lock violation issue? We have not had it for some time and all of the sudden it is back. I suspect a server patch or update may be the issue and have forwarded the solution that Peter Schmid posted earlier. Just wondering if this solution has worked.

Jennifer

This message has been edited. Last edited by: JennM,

Is your lock violation on the .dbo file or the .dbs file? And is a Novell network involved in any way?

If it's the .dbo file, then you should see the "opportunistic locking" fix, which you apply on each workstation.

If it's the .dbs file and a Novell network is involved, you need to add NovellLock=1 to the [Advanced] section of your DBTEXT.INI file.

It was the dbo file and yes the "opportunistic locking" fix has worked. We had to add the registry key to the client workstations. We left the server registry as is.

Thanks, Jennifer

I'm having the same problem since we upgraded to version 10 - is there an easier way round this as our IT department takes, at best, around three months to deal with any problems? (don't ask! )

The opportunistic locking link from microsoft worked for us and my IT department was able to QA and pass the registry edit and push it to the workstations. The fact that the solution is from microsoft should have them breathing easy and testing more quickly. If it is only a handful of users involved then I suggest you get it passed by IT and then manually make the changes to the registry. It take a few seconds at most and will skip the step of testing a push to workstations.

Thing is we're not allowed any admin rights so IT would have to change each PC themselves. It's just taken them three weeks to acknowledge they've received an e-mail from me and then a further week to do the work (and all I wanted was a deleted file restored!!) Lord knows how long this will take!

Still if that's the only option that's what'll have to do!
Thanks for the quick response
Ax

We have also been getting this error message for the last few months.
"Error reading from file ....collections.dbo: Lock violation"

The MS Windows "Opportunistic Locking" fix did not work for us, but our IT department suggested an easier fix: if you are on a Novell server, try this on each workstation:
Go to Settings - Network Connections. Right click on Local Area Connection and select Properties. Under General--Novell Client, select Properties--Advanced Settings.
Set the following parameters:
File caching = off
File commit = on
Click OK and reboot.