Joseph, I had the same problem yesterday On 19 July 2017 at 14:21, JV Leavitt <jleavi...@att.net> wrote:
> Thank you Cathy. It was only a temporary problem with FamilySearch > yesterday. > > Joseph Leavitt > > > > On 7/18/2017 9:30 PM, Cathy Pinner wrote: > >> Joseph, >> I'm not LDS so I don't know whether there are more problems with that >> part of the Legacy FS program but it's working fine for me. >> >> See: http://support.legacyfamilytree.com/article/AA-00530 >> Access violation errors have a number of different causes. >> >> It can't be a general problem or there'd be posts in the Facebook group. >> There's only one and he found he had a heap of Check/Repair errors in his >> file. >> >> Cathy >> >> JV Leavitt wrote: >> >>> >>> A new problem has shown up when using LegacyFS. I think the error >>> started showing up several hours ago. >>> >>> The API from LegacyFS to FamilySearch must be broken again. The error >>> message says: >>> Access violation at address 0075E311 in module 'LegacyFS.exe'. Read of >>> address 0000000C. >>> >>> Any word yet? or am I the first one to notice? The LFS program will >>> no t work at all now. I'm able to see that the problem is not at this >>> end. >>> >>> Joseph Leavitt >>> >>> >>> > > -- > > LegacyUserGroup mailing list > LegacyUserGroup@legacyusers.com > To manage your subscription and unsubscribe http://legacyusers.com/mailman > /listinfo/legacyusergroup_legacyusers.com > Archives at: > http://www.mail-archive.com/legacyusergroup@legacyusers.com/ >
-- LegacyUserGroup mailing list LegacyUserGroup@legacyusers.com To manage your subscription and unsubscribe http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com Archives at: http://www.mail-archive.com/legacyusergroup@legacyusers.com/
