It could also indicate there is an issue with the Ancestry tree itself.
Rooty, I tend to agree that it is a RootsMagic timeout issue. I can download small trees without issue, but I have several larger trees and they all fail on RM. I suspect it is related to either having an Apple Silicon Mac (requiring Rosetta) and/or a medium speed (300 Mb) internet connection. Unfortunately, I have the fastest connection available in my area.
Renee, I don’t believe it is an Ancestry tree issue. I have several large trees and all fail using RootsMagic while all successfully download using FamilyTreeMaker. I have given access to one of the trees to one of your support people and they were able to download it with a fiber (1Gb) connection. Unfortunately, fiber is not available in my area.
A 300 MBs down connection should work unless they throttle your upload speed which cable firms tend to do. I was using a 15 MBs down/5 up service in Tucson which really was more like 7/1. In my case if I excluded media things worked.
Many people have reported this issue over time so it is not related to one person’s specific tree.
That more and more points to the fact that it is a problem on your side, not a RM problem. I know for certain on a Windows machine, a 300Mb connection works just fine, at least through the beginning of this month when I finally went Gb.
If this were truly a problem with RM, there would be far more people with this issue. Even Rooty eventually figure out that it wasn’t working on his side, not on RM’s.
The “RM won’t treeshare but FTM does it just fine” really holds no water. FTM can very well be using a different version of the API since their ability to do an actual sync instead of the one by one updating may require something that RM doesn’t use or have access to. Keep in mind that Ancestry use to own FTM and you can bet they negotiated the terms that they needed when they sold it off.
I am going to assume along the way that you have made sure you weren’t using a VPN, turned off virus scanning and all the other standard troubleshooting bits.
Kenneth, A windows machine is running native code. The Mac translator used by RM creates inefficient Intel code that then needs to run through Rosetta on an M series Mac. Make all the excuses you want, the bottom line is RM times out on large files and once it does, the only way out is a force quit. When a program fails, it should fail gracefully.
Agreed, however it isn’t always possible to anticipate every failure in order to gracefully catch it. However RM’s blame for your issue ends there. Don’t expect that they are going to fix an issue that you, and very maybe a few others have, based on something specific to the respective systems. Maybe you should be complaining to Apple that they need to sort out Rosetta. I am sure you are aware that Rosetta has some limitations as to what it can do, right? As in not everything can be translated?
You have just lost a customer.
This is a RootsMagic problem, not Apple. If you want to sell an Apple version, it needs to run natively on Apple, not require Rosetta, Crossover or anything else.
rzamor1 is the ONLY representative of RootsMagic in this community. All the others are merely Apple or Windows users of the program, just like You. Your exclamation is NOT going to bother them one iota. Additionally, RootsMagic (the little company) knows its capabilities, its timeline and its competitors and has been serving up a genealogy product for a very long time. Customers come and go… and they know that.
3 Likes
Off base as usual. Problem is in Rootsmagic and not my equipment nor that of others reporting this RM timeout issue.
Ancestry has changed their API several times requiring both Mackiev and RM to recode.
Very unlikely that FTM uses a different API than RM. One works and one does not.
Off base as usual, and it did indeed turn out to be your equipment. New router/modem and presto, you were back in business. But your should expect problems when using Macs. They are highly unreliable, or maybe it is just their userbase.
Long and short is there’s an issue with the creation of the file AT_63317064.DT8, which on the Mac is in /users//RootsMagic/AMT/ directory. It’s a SQLite database which you can easily open and look at. It has almost nothing to do with Apple Silicon vs Intel, internet speed, etc.
I can reproduce this issue with an existing linked file by taking a RM file that is working fine with TreeShare and copying it to another computer. On the new computer, even one with a fresh OS image and no software other than RM, and It will fail with a large tree. Then you take the AT_63317064.DT8 file and copy it to the new computer and it works fine. I’ve reproduced this on Apple Silicon and Apple Intel, on Monterey and newer OS versions. Clearly an RM problem and not an Apple, Internet, etc, problem.
On a new large download the issue is there’s no AT_63317064.DT8 file to copy from elsewhere. It contains data on all the Ancestry → RM links. My assumption is the SQLite configuration is suboptimal on Mac. I would assume you could do the initial download on a Windows machine as a workaround and copy the AT_63317064.DT8 file to the needed position on the Mac.
The alternative would be RM fixing this, I can’t imagine it would be that hard to fix. I’ve already sent them files and all the information to reproduce it.
This is comical–you know more about my internet service and equipment than I do. Macs unreliable–substitute Windows and you are more on target. The mac operating system and hardware are renowned for reliabliiity and ease of use and has become the dominant consumer choice especially after dumping Intel chips.
May 15% of the hardware market is NOT dominant, and you are aware that Microsoft is heavily moving towards ARM chips also…right? The Mac hardware and OS is the result of not trusting a user to use and maintain their system and it locks them into a limited ecosystem. Maybe that isn’t such a bad thing if the average Mac user has no more skills than many Windows users seem to exhibit these days. I blame mobile devices for stupidifying the market.
Just installed the 10.0.0 update and tried to download a tree from Ancestry. It still fails and cancel on the countdown window still does not work requiring a force quit to exit RM.
It has been 9 months since this issue was reported and still no resolution. We now have a new version and it is still Intel code, requiring Rosetta to run. It seems Mac issues are not a priority.
From what I can see it has nothing to do with running Intel code. I can reproduce the problem on an Intel Mac. As I’ve noted elsewhere I’m pretty sure there’s an issue with the SQLite database they use to track Ancestry changes, and most likely the SQLite provider for Mac. Why RM won’t look into that specific issue leaves me at a loss.
Keith, I’m at a loss as well. RM runs very slow on an M series Mac. I don’t know if Ancestry is timing out because of that or if it is a SQLite for Mac issue. Regardless of why, it’s been an issue for 9 months and RM seems to have no interest in addressing it.