Hello. I am new to Rootsmagic, however quite familiar with Familytree maker and numerous other PC software systems and networking architecture. Ok, to the issue at hand. I created a new blank database, then followed the treeshare process to successfully download my large ancestry content. All the names came across with no issue except one - not of the media came across. I attempted this a second time while having another web browser window open in ancestry (not sure that makes a difference..) and again, same outcome. I’ve deleted the databases and media subdirectory - uninstalled version 11, re-downloaded it, insured by license information was correct, and attempted the ancestry.com database download. Again, same result.
Next, I reached out to Rootsmagic help desk to pose the question. I added screen shots showing the treeshare results windows indicating ancestry has media attachments to each of the ancestors. The response appeared to be a canned answer:
"Hi,
Thank you for your feedback and for the screenshots. We are confirming that this issue has been reported to development and they are actively working with Ancestry on it. Once it is resolved, the fix will be released in an update. We truly appreciate your patience as we work through this.
Sincerely, Jesa RootsMagic, Inc.
Does anyone have a suggestion or recommendation to resolve this issue?
Add’t note: there are numerous files in the media subdirectory of the rootsmagic database directory - however they are not linked to anything.
It sounds like You understand that RootsMagic, at present, CANNOT download associated media. Family Tree Maker, on the other hand, reportedly works fine with the latest API changes that are hampering RM. So, there’s that. Elsewise, it’s wait and see for a fix that is anticipated here in the near future.
WELCOME, by the way !!!
TreeShare has been a part of RootsMagic since 2017. Unfortunately, your delay in adoption until now, comes just as Ancestry itself is making changes to facilitate the many RM users who have the shared exclusivity (with FTM) to synch their tree info.
~ Kevin ≡÷þ
My understanding FTM 2024 25.0.2 Update was meant to make it work with API 2.0 and if its true they do not have (most?) of the same problem that is curious.
That is one possibility / Good thought. It would likely have to do thing differently in order for full sync to work and not fail (most of the time ) and that is often with complicated changes
Well considering there have been at least 7 other different posts on this problem in just the last 17 days, no telling how many people contacted support and 8 days ago @rzamor1 posted that RM was working on the problem, I guess you could say it was a canned response…
You MIGHT check out this thread
@kbens0n and @kevync1985 As an FYI for you I ( several times now ) have treeshared a very small file with media – very small meaning abt 400 people and 10-15 media-- I also upload a gedcom abt 2000 people --no media..
The media did upload – typically I don’t have any media going either way and normally my tree will upload/ download very fast ( in a flash-- like 30 seconds???) whether by treeshare or by gedcom BUT both the gedcom and the treeshare took longer–abt 5 minutes-- it uploads the media 1st and then stall on People and Relationships
Still 5 minutes is nothing BUT as I said these were very small files as compared to what you all are trying to send-- The one thing I did notice is that Media now goes first instead of 2nd like it use to ( if I remember correctly) and I don’t remember ever seeing the Relationship BUT maybe my files just loaded too fast..
I upload a new file with abt 13,000 people–no media–no notes-- it took 42 minutes just to upload the people–33 minutes on Relationships and a couple of minutes on Changes-- perhaps on a large file there is a time out issue also???
RE: the media files not transferring correctly, I ran into a solution after tracing the ancestry API traffic to RootsMagic 11.
Originally, I was using OPENDNS IP4 and IP6 servers. From the Wireshark data, it appears OpenDNS blocks certain traffic rx (receiving traffic) , marking as suspect or questionable.
Now, if I change the DNS servers on my Synology router to Google DNS (8.8.8.8 / 8.8.4.4), the media files come in successfully.
Another issue I learned through this experience is… the Ancestry.com transfer portal is extremely slow if used during normal business hours - specifically during 1500 - 2200 EST (3pm-10pm EST). If you transfer early morning EST or late night EST, the transfer appears to not be delayed. Of note: this delay during peak times caused issues with information completing through TreeShare and possibly (still looking into this) corrupting the existing or new RootsMagic DB.
