Announcement

Collapse
No announcement yet.

Get error when uploading ANcestryDNA

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

  • migoblu
    started a topic Get error when uploading ANcestryDNA

    Get error when uploading ANcestryDNA

    I get this error when trying to upload raw DNA file from AncstryDNA:

    The specified file 'dna-data-2017-05-13.zip' could not be uploaded. The file is an unsupported version or in a corrupt/malformed format. Please place an order for Family Finder or download the file and try again.

    Any idea of what to do? Thanks for any help.

  • edie731
    replied
    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

    Leave a comment:


  • chrisbonisa
    replied
    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, 01:12 PM. Reason: Added working link

    Leave a comment:


  • Jim Barrett
    replied
    Originally posted by betadams View Post
    FTDNA's cautious approach does not extend to them "blocking" the transfers from mapmy23, or accepting the $ fee for access to the chrome browser
    Very true, but they are allowing transfers, unlike most companies.

    Leave a comment:


  • betadams
    replied
    FTDNA's cautious approach does not extend to them "blocking" the transfers from mapmy23, or accepting the $ fee for access to the chrome browser

    Leave a comment:


  • chrisbonisa
    replied
    Originally posted by RossWakelin View Post
    Thanks for a useful thread. Before I discovered the forum I had sent a help request to FTDNA asking what format they required the data to be in (having exhausted all variations I could think of).
    While waiting for their reply I found this thread and used the tool to convert the AncestryDNA v2 file and submitted it. Then I got the reply (given below) stating that they no longer were accepting AncestryDNA kits due to an incompatibility. However a few days later the upload of the tool-corrected file went through (with, as noted elsewhere, no distant/speculative matches included).
    Hence I assume that FTDNA either cannot tell if an AncestryDNA file has been modified by the tool, or they don't care. They could have pointed to the discussion forum and this thread, but they seem to prefer to not accept the file and hope you will buy a FTDNA kit. Given that choice I think I'd stay with AncestryDNA and import to GEDmatch.

    The reply from FTDNA "information specialist" was:
    ------
    Thank you for contacting FTDNA. Normally you should upload the .zip file that Ancestry provides without modifying the file. Unfortunately, Ancestry DNA recently made some changes to their raw data files that make them incompatible with our transfer system. We are not currently able to accept transfers from Ancestry DNA, but we're working to update our transfer system so that we can accept them again in the future.
    We do not recommend altering your raw data file in any way prior to uploading it to us. We cannot say how changes to your raw data file will affect your transfer.
    -------
    I'm fairly certain they are saying that for liability reasons, however the way the tool works is by inserting "no calls" into snps missing from the incompatible ancestry file and deleting snps that are "extra". So its not "modifying your dna" as they say, its more like aligning 99% of it properly with the file format they are expecting, its still 100% your dna thats left in the file and thats why it works as we want it to. Its actually very surprising to me that they still have not adjusted their importer to detect and accept these files as its not that complicated.

    Leave a comment:


  • RossWakelin
    replied
    Thanks for a useful thread. Before I discovered the forum I had sent a help request to FTDNA asking what format they required the data to be in (having exhausted all variations I could think of).
    While waiting for their reply I found this thread and used the tool to convert the AncestryDNA v2 file and submitted it. Then I got the reply (given below) stating that they no longer were accepting AncestryDNA kits due to an incompatibility. However a few days later the upload of the tool-corrected file went through (with, as noted elsewhere, no distant/speculative matches included).
    Hence I assume that FTDNA either cannot tell if an AncestryDNA file has been modified by the tool, or they don't care. They could have pointed to the discussion forum and this thread, but they seem to prefer to not accept the file and hope you will buy a FTDNA kit. Given that choice I think I'd stay with AncestryDNA and import to GEDmatch.

    The reply from FTDNA "information specialist" was:
    ------
    Thank you for contacting FTDNA. Normally you should upload the .zip file that Ancestry provides without modifying the file. Unfortunately, Ancestry DNA recently made some changes to their raw data files that make them incompatible with our transfer system. We are not currently able to accept transfers from Ancestry DNA, but we're working to update our transfer system so that we can accept them again in the future.
    We do not recommend altering your raw data file in any way prior to uploading it to us. We cannot say how changes to your raw data file will affect your transfer.
    -------

    Leave a comment:


  • Tim Campbell
    replied
    I had some trouble uploading my wife's results. The mapmy23 tool worked. I was concerned I would get a limited number of results or somehow get false positives. So far this doesn't appear to be the case. Thank you for providing the free tool. That's truly above and beyond.

    Leave a comment:


  • prairielad
    replied
    Originally posted by mrsprobsma View Post
    Add me to the list, zipped or txt, new or old download, will not load here and same error message and advice to buy kit. Please help.
    Have you used the mapmy23 tool to convert ancestry raw data to format ftdna will accept?

    Leave a comment:


  • mrsprobsma
    replied
    Ancestry uploads elsewhere but not here

    Add me to the list, zipped or txt, new or old download, will not load here and same error message and advice to buy kit. Please help.

    Leave a comment:


  • prairielad
    replied
    Originally posted by JohnTF View Post
    This is on files that failed first...As to whether the files were for any reason a different size and why, is beyond my understanding.
    At age 77 I try the simple route or ask someone

    Leave a comment:


  • JohnTF
    replied
    Originally posted by prairielad View Post
    Is this on files that failed to upload on initial attempt (using ancestry original unaltered file)?

    Not all ancestry files fail to upload, it is just a subset that for some reason or other have less SNP within file, making it slightly smaller then the normal ancestry Raw Data file....these are the ones that FTDNA was rejecting
    This is on files that failed first...As to whether the files were for any reason a different size and why, is beyond my understanding.
    At age 77 I try the simple route or ask someone

    Leave a comment:


  • prairielad
    replied
    Originally posted by JohnTF View Post
    Since suggesting this on Facebook 18 people have had success (that I know of) The ( - ) before the date should also be removed.. Leaving dna-data On transfer it will read dna-data.zip
    Would be interested to hear if this "does/does not" work for anyone
    Is this on files that failed to upload on initial attempt (using ancestry original unaltered file)?

    Not all ancestry files fail to upload, it is just a subset that for some reason or other have less SNP within file, making it slightly smaller then the normal ancestry Raw Data file....these are the ones that FTDNA was rejecting

    Leave a comment:


  • JohnTF
    replied
    Since suggesting this on Facebook 18 people have had success (that I know of) The ( - ) before the date should also be removed.. Leaving dna-data On transfer it will read dna-data.zip
    Would be interested to hear if this "does/does not" work for anyone

    Leave a comment:


  • chrisbonisa
    replied
    Originally posted by JohnTF View Post
    Hello, I'm a new member to the forum.

    My answer to the problem people have transferring Ancestry raw data to FTDNA ….

    When you download raw data from Ancestry it adds the date of transfer to the zip file Title.. ie: dna-data-2018-03-03 You Need to REMOVE the Date -2018-03-03 then transfer zipped file dna-data to FTDNA

    Kiss..(Keep it simple stupid)
    John we actually tried that when the original problems started happening and it didn't seem to matter. It would be wonderful if it were this simple though, thats for sure!

    Leave a comment:

Working...
X