Announcement

Collapse
No announcement yet.

Get error when uploading ANcestryDNA

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • New Ancestry format?

    I've got a few users who have messaged me saying their percentages are low (78%) instead of the typical 99.84%. Can anyone confirm they have gotten recent results from Ancestry that only show that amount of overlap with the older files? Heres an example of what I'm talking about from someone willing to share their results, the original file seems to be from June 2018, note the percentage at the bottom of the page:

    http://www.mapmy23.com/tools/ancestr...QyNTg2MS43NDky

    Comparing that one to a working one from last year:

    http://www.mapmy23.com/tools/ancestr...YzNTA1Ny4wMjYz
    Last edited by chrisbonisa; 27th August 2018, 12:12 PM. Reason: Added working link

    Comment


    • Originally posted by Darren View Post
      It looks like there was an issue with certain files from Ancestry being too short in terms of not having all of the data normally included in the file. Re-downloading the data should correct this problem, but I cannot rule out that Ancestry has not changed something recently. If you still have the same problem after re-downloading please let me know.

      Has anyone received this same error with any recent 23andme transfer?

      -Darren
      Family Tree DNA
      Yes Darren! Current 23andme files cannot be uploaded. My parents did their test after the cut off date on "the new file system" I think it's May 2017, they did the kit November 2017. I tried and tried. Downloaded a 2nd time, no success. After finally finding my answer. CANNOT BE DONE!!!! I was able to upload my AncestryDNA but without my parents dna in there I cannot tell on which side these people are related to me.~Edie

      Comment


      • I have been trying for three days to upload my brother’s Ancestry raw DNA file to FTDNA, and keep getting the error that the file is unsupported or corrupted. He only tested in November, so this is a new file. I have downloaded the file several times from Ancestry, and the text file size is always the same size (17,903 KB). After I run the file through the MapMy23 tool, it comes back as 17,686 KB. I have tried uploading the zip file, and also the text file on its own. In all cases, I get the same error message from FTDNA. I have successfully uploaded the file to Gedmatch and MyHeritage, so I don’t think the file is corrupted.

        The link to the fixed file in the MapMy23 tool is: http://www.mapmy23.com/tools/ancestr...jE5MDA2OC4zMzU

        The percentage is 77.86%. So it seems to be the same situation as mentioned in chrisbonisa’s post of 27th August. Is there anything else I can do to solve the problem, please?

        Comment


        • This is obviously a problem with FTDNA misreading the Ancestry files. I have exactly the same file sizes (17903/17686) and 77.86% as above; the Ancestry files are consistent. Tried multiple downloads, uploads, file renames, and zip vs txt with no luck. The same file loaded without issue to GED Match and MyHeritage.

          Comment


          • I have the exact same issue, tried multiple downloads/uploads, fixed the file via MapMy23 still get an error.

            Comment


            • I also have encountered problems uploading the AncestryDNA file here as it just keeps stating it cannot be read or is unsupported or corrupted. The same file has been successfully uploaded to GedMatch and I have tried all the various solutions provided in this thread, including the file fix MapMy23 which has failed for me. The file percentage is around 77% I think - no idea if that makes any difference.

              Comment


              • Originally posted by vocalistuk View Post
                I also have encountered problems uploading the AncestryDNA file here as it just keeps stating it cannot be read or is unsupported or corrupted. The same file has been successfully uploaded to GedMatch and I have tried all the various solutions provided in this thread, including the file fix MapMy23 which has failed for me. The file percentage is around 77% I think - no idea if that makes any difference.
                I got my AncestryDNA result last week and I have the same problem. I have uploaded my file to GEDmatch and MyHeritage without any problem, but I'm having the same problem as the rest of you with FTDNA. MapMy23 did'nt work with my file. The problem is, obviously, with FTDNA, please fix ASAP! I want to do FTDNAs YDNA and mDNA test, but I'm hesitating now.

                Comment


                • Originally posted by Tilt View Post
                  I got my AncestryDNA result last week and I have the same problem. I have uploaded my file to GEDmatch and MyHeritage without any problem, but I'm having the same problem as the rest of you with FTDNA. MapMy23 did'nt work with my file. The problem is, obviously, with FTDNA, please fix ASAP! I want to do FTDNAs YDNA and mDNA test, but I'm hesitating now.
                  Did you hesitate buying your test from Ancestry because they don't allow us to upload FTDNA's autosomal DNA to their system?

                  I will assure you, you'll get more autosomal matches at FTDNA if you order your autosomal test from FTDNA. Too bad you missed the year end sale. I wish FTDNA would do the same thing Ancestry and 23andMe do. Not accept transfers.

                  Since you are hesitant about buying Y-DNA an mtDNA from FTDNA why don't you buy it from another source?

                  Comment


                  • For issues with uploading, have you tried contacting ftdna via their contact us link?
                    https://www.familytreedna.com/contact

                    Comment


                    • Originally posted by Jim Barrett View Post
                      Did you hesitate buying your test from Ancestry because they don't allow us to upload FTDNA's autosomal DNA to their system?
                      No, why would I hesitate to buy an autosomal test from Ancestry because they don't allow upload of autosomal tests from FTDNA?

                      I'm Swedish and I chose Ancestry because of their large databases of both DNA tests and historical records. Actually, the Sweden DNA Project at FTDNA recommends Ancestry for tracing Swedish ancestors in original records (such as church books): https://www.familytreedna.com/groups...out/background


                      Originally posted by Jim Barrett View Post
                      I will assure you, you'll get more autosomal matches at FTDNA if you order your autosomal test from FTDNA.
                      Are you sure about that? Ancestry has, by far, the largest autosomal DNA database size, it more than 10 times as big as FTDNAs. I got 1000+ matches at Ancestry.


                      Screen-Shot-2018-09-03-at-9.11.28-PM.png?w=1502&ssl=1.png


                      Originally posted by Jim Barrett View Post
                      I wish FTDNA would do the same thing Ancestry and 23andMe do. Not accept transfers.
                      The major component of an autosomal DNA test is matching other individuals. A large database benefits ALL of FTDNAs customers, so why would FTDNA not want people to upload their atDNA-data?

                      Originally posted by Jim Barrett View Post
                      Since you are hesitant about buying Y-DNA an mtDNA from FTDNA why don't you buy it from another source?
                      Ancestry does not offer Y-DNA or mtDNA tests anymore. Who knows, I might try both FTDNA and LivingDNA. The point is: I wanted to upload my atDNA to FTDNA to compare the quality of their autosomal matches to Ancestrys, but I can't since FTDNA do not seem to accept Ancestry files at the moment. And there is no problem with my DNA-file, it worked just fine at MyHeritage.
                      Last edited by Tilt; 10th January 2019, 06:56 AM.

                      Comment


                      • Just spoken to FTDNA Support who state the following:

                        Unfortunately, as soon as our IT department was able to accept files from Ancestry's version two test, they changed the format of their file again, end of September.
                        Now our system is reading it as an incomplete or corrupted format file yet again, because there are more SNPs missing in their file.

                        Oh that is a shame - any idea when or if the problem will be fixed ?

                        Unfortunately there is no timeline or prediction date I can give.

                        I can put your email address on a list that we will contact once it becomes available again though.

                        >>>>>>>>>>>>>>>>>>>>>>>>>>>

                        So if you are experiencing the same problem, suggest contacting support with a request to be put on their email list to be informed if/when the issue is resolved.

                        Comment


                        • This has been recurring on and off since at least 2017. Reading the comment above about the data being short in some downloads, I compared the file to an earlier one that uploaded successfully. The new files have MORE data lines, not less. The notes have mentioned Ancestry V3 - the headers still say it's V2.

                          The fact that these files upload successfully to MyHeritage and Gedmatch beg the question: Is FTDNA not assigning priority or resources to fix this recurring problem in order to sell more Family Finder Kits? If so, that's pretty shoddy...
                          Last edited by joe4227; 22nd January 2019, 01:50 AM.

                          Comment


                          • I'm having the same problem as everyone else, so I eventually contacted the FTDNA helpdesk, and they've given me permission to post their reply here. This is what they said:

                            Yes, unfortunately, there are some known issues with certain Ancestry transfers. We were previously able to accept both Ancestry Version 1 and Version 2 files, but recently, Ancestry began making small changes to their Version 2 files so that they are more difficult to interpret. This means that if you have a more recent Ancestry raw data file, especially anything from after September of 2018, the file has likely been changed and our system cannot accept it currently. Our IT department is aware of the issue and is working diligently to create a workaround so that we can continue to accept Ancestry transfers. While I do not have an estimated date that IT will resolve the issue, I can tell you that it is a high priority issue that they are focusing on. If you would like I can add your email to a list to be notified when a patch is developed. Please reply to this email if you would like me to add you to that list, and again, I apologize for the inconvenience.

                            Comment


                            • Makes me wonder if AncestryDNA does not want its kits on the Family Finder database for competitive reasons.

                              Comment


                              • Originally posted by joe4227 View Post
                                This has been recurring on and off since at least 2017. Reading the comment above about the data being short in some downloads, I compared the file to an earlier one that uploaded successfully. The new files have MORE data lines, not less. The notes have mentioned Ancestry V3 - the headers still say it's V2.

                                The fact that these files upload successfully to MyHeritage and Gedmatch beg the question: Is FTDNA not assigning priority or resources to fix this recurring problem in order to sell more Family Finder Kits? If so, that's pretty shoddy...
                                Maybe GEDmatch and MyHeritage are not as particular about the quality of the data they accept. Maybe people should complain because Ancestry doesn't accept transfers from FTDNA. I have never understood why it is always FTDNA that is the bad guy.

                                If you want your results on 23andMe, what do you have to do? If you want your results on Ancestry, what do you have to do? If FTDNA is the bad guy, it is because they started out trying to accept data from the other companies!

                                Comment

                                Working...
                                X