Re: Number of locks on Win2000 Server/Database Crash
From: Dave Patrick (mail_at_Nospam.DSPatrick.com)
Date: 12/03/04
- Previous message: WRH: "Re: WM_ENDSESSION: See if its a restart or shutdown"
- In reply to: Bart Steur: "Number of locks on Win2000 Server/Database Crash"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 3 Dec 2004 08:17:58 -0700
For Windows NT/2000
Server side, you add a Reg_Dword value named;
"EnableOplocks"
and set it's value to 0
HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
Been there did this some years back. Best solution is to migrate the Access
backends to SQL server and be done with it.
-- Regards, Dave Patrick ....Please no email replies - reply in newsgroup. Microsoft Certified Professional Microsoft MVP [Windows] http://www.microsoft.com/protect "Bart Steur" wrote: | Hello, | | We are running WIN2000 Server and we have an Access 97 on the server. | Multiple users use this database very frequently. (for Select/Insert/Update | and Delete) | | The database was first situated on a Novell/Netware Server where things ran | fine. Now we have transferred the database to the W2K server and the | database keeps crashing and we have to repair it al the time. | On the Novell/Netware server we were able to set the maximum number of locks | per connection and the total number of locks. Since we did this more users | could use the database together. | | Question1: Is this possible for W2K server | Question2: Could there be another reason for this database crash. | | Please help, | | Thanks, | | Bart | |
- Previous message: WRH: "Re: WM_ENDSESSION: See if its a restart or shutdown"
- In reply to: Bart Steur: "Number of locks on Win2000 Server/Database Crash"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
Loading