Browse
 

Html CSS Menu Css3Menu.com

Tools
Categories

Access Violation in Legacy FamilySearch

Author: Reference Number: AA-00530 Views: 25784 Created: 2013-11-18 01:34 PM Last Updated: 2019-01-21 09:58 AM 80 Rating/ 5 Voters

Note for anybody using Legacy 8 or earlier: When we release a new version of Legacy we no longer update the older version.  As time goes on and Family Search makes changes to their API (how we connect Legacy to their servers) and changes are not being made to the old version of Legacy the Family Search interface will no longer work with the older version.  You are free to stay with the older version of Legacy if you wish and the program will continue to function as it always has but the Family Search interface will only work with the latest version of Legacy.  If you wish to check out Legacy 9 we offer discounted pricing for returning customers.  Click here to learn more.

We are aware of the Access Violation problem in Legacy FamilySearch that some users experience. There is no one cause. Sometimes it happens when a button is clicked while another action is still being processed. Often it will not repeat. 

The most common cause of this error is that the Family Search programmers are tweaking the servers and so the Legacy Family Search servers are down for maintenance (this does not always mean the FamilySearch.org site is down, just the Legacy Family Search servers).  Please try the Legacy Family Search interface again at a later time.  If the problem is still occurring after 24 hours please feel free to try the steps below.  

Browse on your computer to C-Drive>Program Files(X86)>Legacy9>FamilySearch and in the FamilySearch folder you should see the Legacy FS application.  Right click this and choose troubleshoot compatibility and go through the compatibility tool.  Next browse to C-Drive>Program Files(X86)>Legacy9 and in the Legacy9 folder you should see the Legacy application.  Right click this and choose troubleshoot compatibility and go through the compatibility tool for this application.

If the problem persists, please apply these steps in the order given.

 1. Click OK and hopefully everything should behave as expected. Try what you were doing in Legacy FamilySearch again. If the problem persists, go to step 2.
 2. 
Click the Refresh button on the right side above the FamilySearch person and then click the Reload button to reload your Legacy person. Sometimes Legacy FamilySearch is holding on to old data and this will clear it out.
 3. Close Legacy FamilySearch and open Legacy Family Tree.
 4. Run File Maintenance - Check/Repair.  Click on File> File Maintenance > Check/Repair and follow the prompts. If the error messages occur during the Check/Repair process, click No to continue with the repair. Do step 1 twice if errors are found.
 5. Open Legacy FamilySearch and if you are able, click on File > File Maintenance > Check and Repair.
 6. Try what you were doing in Legacy FamilySearch again. If the problem persists, go to the next step.
 7. Close Legacy FamilySearch and Legacy Family Tree. Next browse into the Legacy folder on your hard drive and right-click on the FamilySearch folder, then select Rename from the popup menu and rename the folder zFamilySearch.


    For 32-bit Windows OS   C:\Program Files\Legacy9\zFamilySearch
   
For 64-bit Windows OS   C:\Program Files (x86)\Legacy9\zFamilySearch

 8. Next update your Legacy program by visiting the following site, which will create a new FamilySearch folder.

LEGACY: http://www.legacyfamilytree.com/DownloadUpdate.asp

 9. If none of these steps work, the Access Violation error might be fixed with clean re-installation of Legacy.

If none of the above steps fix the problem Copy DAO360.DLL from the C:\Program Files (x86)\Common Files\microsoft shared\DAO folder into the C:\Windows\SysWOW64 folder and the C:\Windows\System32 folder. This should fix the problem. Make sure Legacy is closed when you do this and your computer will probably ask for Administrative approval, so give it.