[Hankster71]

When trying to autologin from Legacy Family Tree to FamilySearch.org integrated program I get

Access Violation Message (see below).

None of the recommended fixes from Legacy have fixed it and Family Search Tech had me change

my user name and password to no avail.

The weird thing is that I can't use the service from any computer.
 

My O/S is Win 7 Home Premium.

 

Access violation at address 00752C45 in Module 'LegacyFS.exe'. Read of

address 0000000C.

 

 

[Advertisements]

Access violation at address 00752C45 in Module 'LegacyFS.exe'. Read of

address 0000000C.

 

Sounds like either a corrupt LegacyFS.exe program file, an incompatibility between the LegacyFS.exe program and some other program running on your computer, or it might be a bad/flaky RAM (random access memory) module.

 

Can you autologin from Legacy Family Tree to FamilySearch.org after booting the computer up in Safe Mode with Networking?

[SpywareDr]

Access violation at address 00752C45 in Module 'LegacyFS.exe'. Read of

address 0000000C.

 

Sounds like either a corrupt LegacyFS.exe program file, an incompatibility between the LegacyFS.exe program and some other program running on your computer, or it might be a bad/flaky RAM (random access memory) module.

 

Can you autologin from Legacy Family Tree to FamilySearch.org after booting the computer up in Safe Mode with Networking?

[Hankster71]

What made this problem hard to narrow down was that it was happening on both of my computers.

It turned out that I had a corrupt download of a legacy 8 update, and I used the downloaded file on

 

a flash drive on the second computer.  Dumb, I know.

To correct the situation I had to uninstall, and download updated version, re-install, and reload

 

original family files.  Voila!  I was back in business.

Thanks for your response, SpywareDr.

 

[SpywareDr]

You're welcome.

 

Good to hear you got the problem resolved. Thanks for letting us know.

[RolandJS]

For the benefit of others with a similar problem, I found out that sometimes a security program is too assertively set and "indirectly blocks" an EXE.  And, I will remember your solution also.