Access/FoxPro Database Corruption

Toutes les réponses

• vendredi 5 décembre 2008 15:58

   

   
  

  0
  Hi
  
  I have nothing to add unfortunately other than to say that I have raised an issue regarding a significant increase in file based disk corruption since I moved to a Windows 2008 64 bit server.  Like you I find have no AV installed on the servers. Unfortunately no-one has commented back which either means no-one else has a problem or there's an issue that has no fix!
  
  What server type / motherboard do you have, and assuming you are using a RAID configuration in hardware what make/type is that?  Just seeing if there is any correlation with my previous setups, which used Silicon Image Sil3112 controllers (yuck!) in one server and an LSI controller in the ASUS DSBV-DX server board in another.
  
  Kind regards
  D
  
  
  
  • Réponse
  • Citation

   
• lundi 8 décembre 2008 11:44

   

   
  

  0
  Hi,

   

  According to my research, if we are perform a large SQL append query, it is likely the database will be corrupted. Although, Opportunistic locking improves file I/O performance on file server, it increases the risk of database corruption in a multi-user environment.  If the file is stored on a Windows NT kernel based file server, please consider disabling "opportunistic locking" (oplocks) on the file server.

   

  Please refer to the following Microsoft KB article to disable opportunistic locking on the problematic server and then monitor if the database corrupted issue will still re-occur.

   

  Configuring opportunistic locking in Windows

  http://support.microsoft.com/kb/296264

   

  For your reference, I have list some links to troubleshoot the database corruption.

   

  How to troubleshoot and to repair a damaged Access 2002 or later database

  http://support.microsoft.com/kb/283849

   

  ACC2000: How to Recover Data from a Corrupted Table by Using the DAO Method

  http://support.microsoft.com/kb/815280

   

  How to keep a Jet 4.0 database in top working condition

  http://support.microsoft.com/kb/303528

   

  How to troubleshoot corruption in a Microsoft Access database

  http://support.microsoft.com/kb/306204/

   

  Hope it helps.

  ---

  David Shen - MSFT

  • Proposé comme réponse David Shen vendredi 16 janvier 2009 03:19
  •  
  • Réponse
  • Citation

   
• mardi 9 décembre 2008 12:20

   

   
  

  0
   Hi David
  
  According to the linked article the opportunist locking configuration only relates to SMB1 - the behaviour cannot be modified for SMB2.  So depending on the client end both the server and the client need to be "downgraded" to use legacy SMB to avoid potential corruption?  This really doesn't sound right to me  - although this isn't really my problem so I guess the poster will be able to comment more :)
  
  Kind regards
  D
  
  
  • Réponse
  • Citation

   
• jeudi 11 décembre 2008 08:25

   

   
  

  0
  Thanks for your comments.
  @Haileris: Our configuration is entirely different: We have a HP Storageworks MSA2000 attached via iSCSI to a HP ProLiant DL380 G5 Server.
  
  We will try switching off opportunistic locking, as all clients which uses the Access program are still on Windows XP (and so don't use SMB2). Do I understand it right that I can set the OplocksDisabled to 1 on the Client computers that use the Access program and then I don't need to set EnableOplocks to 0 on the server?
  
  I will let you know, if it works.
  
  thanks
    Michael
  
  • Réponse
  • Citation

   
• mercredi 6 mai 2009 15:36

   

   
  

  0
  Hi Michael Gross,
  
  I have the samme issue, we have a ms access database application and the users enter via RDP (remote desktop) and Database Corruption still frequent.
  
  i need to know if i set EnableOplocks to 0 in client computers solve Database Corruption.
  
  Thanks,
   Ricardo Silva

  • Proposé comme réponse David Shen dimanche 10 mai 2009 14:32
  •  
  • Réponse
  • Citation

   
• vendredi 25 mai 2012 07:21

   

   
  

  0

  One of our customers has a application which uses an Microsoft Access database and one application which uses a FoxPro database. The applications run on the client computers, the databases are accessed via the Windows File Server. Since we installed a new server (Windows 2008, 64 Bit) we have frequently problems with corrupt databases. We have to repair these databases on average about once or twice a week. There is no anti virus installed on the server (Trend Micro antivirus on client side).
  
  The support of the Microsoft Access based application told us, that they have a few customers with the problem of frequent database corruption but they couldn't come up with a solution. Because of the similar problem with the FoxPro database I think it might be a server related problem.
  
  Frankly I have no idea how to trace this problem. Had somebody a similar problem or can give me advice where I can start to look for the problem?
  
  thanks a lot
    Michael Gross
  

  Actually this problem is occurring due to .dbf files' corruption. And you know what? This is quite common issue of .dbf files' corruption.  So all those who use .dbf files must have faced this situation. I myself have suffered from this situation. I use Visual FoxPro for database files. My files were also corrupted. Everytime when I tried to open them I just got errors, nothing else. But now files are good as I repaired them. So if you really want an advice they I can just say that take help of a software program. Your problem must be solved as I think. 

  Help

  • Réponse
  • Citation

   
• samedi 16 juin 2012 21:51

   

   
  

  0

  In such case I would suggest programmed method

  You may try next one http://www.dbf.repairtoolbox.com software repairs database files starting with Windows 98

   
  • Réponse
  • Citation