I’ve done some more testing and submitting my DB to RM support.
I’ve found some interesting stuff. First off the issue is unrelated to internet speed. Wired, Wireless, etc, timing is roughly the same. I’ve also found it’s unrelated to Ventura. I imaged up a MacBook Air M1 with a clean copy of Monterey and only Rootsmagic installed, hooked it to the same iCloud account and forced a download of the DB folder. Wireless, stalled at 36%, wired, stalled at 36%. Same place and same timing as on the MacBook pro(s).
Clearly there IS something on my Mac Pro that ISN’T on my laptops that has nothing to do with files in the DB folder, so it’s buried in one of the library folders.
As an FYI the MacPro from start of publish to displaying the list of changes takes 12 seconds. On the other machines it stalls and asks to retry the Ancestry connection after 2:30-3:00 minutes.
This may not be relevant but in the past Rootsmagic would stall out on my small 400 person file if media were included while FTM would sync the same file with ease. Also RM9 is still intel only code and your old and new macs probably mix intel and M chips.
Tech support usually suggests looking at giving RM full disk access and turning off any anti-malware program neither are really issues on a mac.
What’s weird is my 2019 MacBook Pro was Intel, and my 2023 is M2. Same problem on both. The MacBook Air I have for a spare at work is an M1 and nothing besides the OS and Rootsmagic was installed, so it’s not anti-virus or other things.
Very strange. I have another Mac Pro 2013 I use just for my scanner and OCR that I’ll try installing Rootsmagic on and see if it works.I have a feeling there’s a “magical” file that preloaded in a user directory that’s the issue. All my RM 9 work has been on my main Mac Pro, so I don’t think it’s coincidence that since I’ve upgraded to RM 9 only the machine I used it on primarily works. I’ve been in the business too long to believe in coincidences.
Hi. First time poster here. I’m new to RootsMagic and have jumped straight in with RM9. I too am having problems with TreeShare for Ancestry on Mac. I have 12 Thew family trees on Ancestry and, while TreeShare works well with the smaller trees, it doesn’t (yet) with the largest two. The largest is still under 5,000 people. Firstly, I had to get RM support to go into that tree on Ancestry and send me a back up. I’ve loaded that to RM9 OK but no success with TreeShare. On Ventura it would get “Collecting changes from Ancestry” to 73% then a pop up with “Ancestry is not responding”. That’s happened with consistent % over a dozen times. I’ve learnt to wait two minutes before clicking “Retry” which then proceeds to 99% before freezing there / crashing the program. I’ve upgraded to Sonoma and now it’s 58% for the pop up before proceeding to 99% and crashing. I’ve tried Settings>WebHint Settings>Reset TreeShare to no avail. RM Support’s other suggestion is it’s my Internet connection. But why would that cause the consistent %s. Is there anything that will enable TreeShare on Mac (Sonoma) with larger Ancestry trees or have I chosen the wrong program?
I just opened my 15,000+ database in TreeShare running Sonoma without an issue. If the support agent downloaded using Sonoma and tested it opening in TreeShare afterwards then its not RM with the issue. Have you made any changes to the database after the agent gave you the backup? Go to Settings, WebHints and click on “Reset TreeShare” and see if that helps. Otherwise you will need to look at your security software, or internet connection. How fast of a connection do you have.
As I wrote, I tried Reset TreeShare. Also, I asked Jackson for a second backup to rule out any database changes causing it. I have Virgin Media’s Gig1 so bandwidth shouldn’t be an issue and as it’s Mac I’m not running any additional security software. Plus I have several smaller trees that can use TreeShare OK, so I’d be surprised if the issue is just Internet connection. How many other people have experienced the stall/crash at 99% and what have the causes/resolutions been?
I’ve seen the stall with a download but not with opening TreeShare on an existing database, unless there were to many unmatched people in the database. In those cases they would need to download the Ancestry tree again.
I’ve since tried TreeShare from a relative’s house with the same error pop up at 58% followed by stall/crash at 99%. So that rules out it being my WiFi specifically. Also, Jackson sent me the second backup of my Alnwick tree, which I installed without making any changes to the tree on Ancestry. As I have 12 trees on Ancestry (for my Thew One-Name Study) I will start again with creating a New RootsMagic file for each of them, try to set up TreeShare for each and report back when done. Shall I keep it on this thread? Or start a new one for “TreeShare for Ancestry on RM9 and Mac”? I suggest the latter because I’ve read several threads where Mac users have been experiencing the same/similar issues without resolve.