Jim Dettman
jimdettman at earthlink.net
Thu Aug 19 10:11:10 CDT 2004
John, Definitely want to turn off OPLOCKS and see if it clears up the problem. See: Configuring Opportunistic Locking in Windows http://support.microsoft.com/default.aspx?kbid=296264 Jim (315) 699-3443 jimdettman at earthlink.net -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of John Bartow Sent: Thursday, August 19, 2004 10:50 AM To: Access Developers discussion and problem solving Subject: RE: [AccessD] Clear Locks Via OS (was: A table that can'tbeduplicated) Jim, (Sorry, I had that info in my original post on DBA-Tech) W98 Clients W2k3 Server TCP/IP VB Apps (multiple) utilizing A97 mdb BE (also multiple) When looking at Computer Management-Shared Folders you have three items by default (same with XP/W2K): Shares - obvious Sessions - indicates any user/machine utilizing a share Open Files - indicates the files being used via the share So by session I mean the user/machine with an open Shared File Session. Presently I have them right click on the Improperly open mdb BE file and choose Close File. As you mentioned previously "this needs to be fixed"! (I get a chuckle out of that every time I read it :o) For many years now the developers didn't know this was happening and neither did any previous support persons, I guess up until you all agreed, I was the only one that cared ;o) but it is causing problems with the apps backup function and at times it affects printing - which I have no idea why it would affect printing but I still think it needs to be fixed) The entire staff just says - that's just how XXX program works. (I won't do the company the dishonor of mentioning their name as it may be a locking issue). The issue that has not been resolved yet is the mdb BE is showing as an Open File after the user(s) have closed the application on the W98 client. When checking the client machine it shows that no process is hanging on the client machine. If I log out the client on the client machine the (improperly) open mdb BE file closes on the server. By deduction as a work around I could close the share on the client machine and it would close the session on the server and the file would close. I could then re-establish the share. Although I don't know if this is causing the file to close properly or not it would on the surface seem to be no worse than forcing it to close via the Computer Management interface on the server or by logging the client out. My immediate need is to address the issue in manner the users can deal with the problem without forcing them to login to the server. My goal is to eventually remove the problem - any ideas? I am pursuing Gustav and Stuart's suggestions on file locking problems. BTW: This problem also occurred on the WNT4 Server. Thanks for all your help, John B -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Jim Dettman Sent: Thursday, August 19, 2004 6:45 AM To: Access Developers discussion and problem solving Subject: RE: [AccessD] Clear Locks Via OS (was: A table that can'tbeduplicated) John, Not sure I understand this last bit: <<Logged out of workstation with session files open, checked server open files -files closed>> Is this terminal services or Citrix? Not exactly sure what you mean by "session". And at the end, your saying after doing this the server now sees the MDB file as closed for each of the work stations? Also, more specifics on the setup: 1. Client OS 2. Server OS 3. Network protocol(s) in use Jim (315) 699-3443 jimdettman at earthlink.net -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of John Bartow Sent: Wednesday, August 18, 2004 6:57 PM To: Access Developers discussion and problem solving Subject: RE: [AccessD] Clear Locks Via OS (was: A table that can'tbeduplicated) I just had a chance to try out some of the previous suggestions. (I haven't had a chance to check out OPLOCKS yet and I haven't downloaded PsTools yet.) I checked the file/folder permissions -check I checked the AV scanner exception list -ldb was in the exception list mdb wasn't I added that I ran the multiple applications on three workstations simultaneously and then closed them out properly, I checked the task list on each workstation -nothing listed Checked the open files on the server -ldbs were not open, mdbs were left open Returned to each workstation check processes with third party tool -nothing there Logged out of workstation with session files open, checked server open files -files closed Any other ideas? John B -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com