Announcement

Collapse
No announcement yet.

Get error when uploading ANcestryDNA

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

  • 462DNA
    replied
    Like others here, I've been unsuccessful in trying to upload raw data for an AncestryDNA kit which completed its processing on August 22, 2017. When I first downloaded the raw data on the same day it finished, I immediately noticed that the header had a V1.0, something which was mentioned earlier in this thread. However, I didn't try to upload it to FamilyTreeDNA until several days later. When I did so, it was not accepted. I tried the remedies in this thread (changing the header) with no success.

    I then decided to try to download a new copy and noticed that the header had changed to match the "older" style which some people had success in submitting. Unfortunately this file was also not accepted.

    I noticed that the file size (17,595,826 bytes) did not match the expected 18,110,076 bytes which was mentioned in this thread. In fact, when I first downloaded the raw data and looked at number of lines or SNPs, I noticed it did not match up with the number I expected based on the ISOGG comparison chart.

    Yesterday, I decided to download a sample AncestryDNA raw data file posted several weeks ago to the Personal Genome Project in order to compare the lines/SNPs. I found that there are 18532 fewer SNPs in my newer raw data! The older files seem to have 668,962 lines, whereas my newer raw data files only have 650,430.

    After doing a basic comparison operation on the two different files, I found that there are 1354 SNPs which are apparently unique to the 17,595,826 byte "broken" file and 19886 SNPs unique to the sample (V2.0) Ancestry file from PGP. Could this be a possible change to Ancestry's chip? If so, it's a shame they're removing more SNPs.

    I have to wonder whether these SNPs could have been removed deliberately for medical or other reasons. I have uploaded a list of the unique SNPs to each chip, and a list showing the differences in total SNPs for each chromosome.

    Also, today another family member's AncestryDNA kit finished processing and the raw data is the same 650,340 lines.

    Leave a comment:


  • Ann Turner
    replied
    Originally posted by nooni View Post
    Thank you for your offer! I've transferred two kits into FTDNA before, and this one I'm having trouble with is my third. I realized it would make the most sense to compare two .txt files from the same person, but when I re-downloaded the Ancestry .zip files for the two previous kits, they both came up as the original 18.1 MGs (exactly 18,110,076 bytes). This third one that finished Ancestry's processing on 16 Aug 2017 is the only one that is 17,595,826 bytes.

    I think whatever formatting change that FTDNA doesn't like is built into recent data. Of course, I can't check the first two kits to see if FTDNA still accepts them since I've already transferred them to FTDNA previously. I wonder if it has anything to do with AncestryDNA's administrator change for profiles from 18 July...
    I could still see if the SNP coverage is the same, if you'd like.

    Leave a comment:


  • nooni
    replied
    Originally posted by Ann Turner View Post
    If you'd like to send me copies of your old and new downloads, I could take a look at them and see what differences I spot. My regular email is [email protected]
    Thank you for your offer! I've transferred two kits into FTDNA before, and this one I'm having trouble with is my third. I realized it would make the most sense to compare two .txt files from the same person, but when I re-downloaded the Ancestry .zip files for the two previous kits, they both came up as the original 18.1 MGs (exactly 18,110,076 bytes). This third one that finished Ancestry's processing on 16 Aug 2017 is the only one that is 17,595,826 bytes.

    I think whatever formatting change that FTDNA doesn't like is built into recent data. Of course, I can't check the first two kits to see if FTDNA still accepts them since I've already transferred them to FTDNA previously. I wonder if it has anything to do with AncestryDNA's administrator change for profiles from 18 July...

    Leave a comment:


  • OldFinneyKid
    replied
    Are file sizes an issue?

    So far, from what I have seen, the file size determines whether the fix will work on files downloaded over the last week or two. It seems that the Ancestry files are now being downloaded with the proper header so the fix is no longer necessary. File size appears to remain an issue.

    All the older V1 files with an uncompressed size of 18,400 KB seem to work. All the newer V2 files with an uncompressed size of 17,686 KB seem to work.

    The files that will not work, header fix or no header fix, are the ones where the uncompressed size is something different.

    Does anyone see an exception -- a file with the correct size that cannot be fixed? -- or a file with a different size that works?

    Leave a comment:


  • Ann Turner
    replied
    Originally posted by nooni View Post
    I re-downloaded the .zip file from Ancestry about twenty minutes ago and this copy has the V2.0 and DIAGNOSTIC format, so it appears Ancestry has started reverting back to the old header. However, the unzipped file is now 17,595 KB, and of course FTDNA still won't accept the .zip or .txt file. So I don't know that the issue is entirely the header since my file's text now matches.

    I don't have the patience to make a copy of a pre-broken, 18.1 MG .txt file and manually change the ATCGs to the new file's in an effort to capture these invisible format changes, but I wonder if that's what it'll take for some of us.
    If you'd like to send me copies of your old and new downloads, I could take a look at them and see what differences I spot. My regular email is [email protected]

    Leave a comment:


  • nooni
    replied
    Ancestry header reverted

    I re-downloaded the .zip file from Ancestry about twenty minutes ago and this copy has the V2.0 and DIAGNOSTIC format, so it appears Ancestry has started reverting back to the old header. However, the unzipped file is now 17,595 KB, and of course FTDNA still won't accept the .zip or .txt file. So I don't know that the issue is entirely the header since my file's text now matches.

    I don't have the patience to make a copy of a pre-broken, 18.1 MG .txt file and manually change the ATCGs to the new file's in an effort to capture these invisible format changes, but I wonder if that's what it'll take for some of us.

    Leave a comment:


  • OldFinneyKid
    replied
    Uncompressed file sizes?

    Just curious, but if your file still does not work, do you have the older file with an uncompressed size of 18,400 KB or do you have the newer file with an uncompressed size of 17,686 KB? Does anyone have a file with either of these sizes that still will not upload after the V2 fix?

    Leave a comment:


  • rkd
    replied
    nothing works

    I have tried every combination suggested, but nothing seems to work. I've tried Notepad++, uploading the *.txt file and the *.zip file. Very frustrating.

    Leave a comment:


  • OldFinneyKid
    replied
    Sometimes it doesn't matter

    I've had the opportunity to upload 9 kits since this problem started (a family reunion generated interest, in case you're wondering), and I tried different things after I saw what was and was not working. Here are my observations:

    1. Line 3 must have a version number of 2 rather than 1.
    That's it. Everything else is just overkill and will not change the outcome if done properly.
    2. You should avoid introducing any formatting changes, seen or unseen, during unzipping, editing, saving, or rezipping.
    Invisible formatting characters are sometimes added just by opening a file with a word processor, spreadsheet, text editor, etc. Those invisible changes would include line feeds, tabs, screen formatting, watermarks, anything that was not in the file when Ancestry created it.

    Now, the interesting discovery came on my 8th file, with an Ancestry file that was generated prior to the problem and just had not been uploaded previously. I tried the upload, got the error message, and assumed the file had the wrong version.

    I opened a copy in the Notepad++ editor (always a duplicate file, I never start with the original downloaded data) and saw that it had V2 where it needed to be. Everything looked perfect.

    Then I tried the upload again. Error. So right after emailing my cousin to obtain a new copy for me, I tried again. Within that short 10 minutes the original unaltered file uploaded correctly.

    If this had been my first file upload, I might have started making more header changes and eventually after replacing the entire header it possibly could have worked. It might have randomly worked after I made only 2 changes or 5 changes. I would never have known that everything after the V1 to V2 revision was not necessary.

    Now when you consider the rejections from the Ancestry change combined with random rejections of good, workable files, I would say it's a wonder anyone can get past this issue.

    Leave a comment:


  • Runwithit
    replied
    Read my post on page 7, it will work

    Leave a comment:


  • Obriejen
    replied
    Error message

    I am receiving the same error message for several days now. I have tried upward of 30 times to upload this. I have tried all the solutions.

    Will FTDNA support be able to help via phone better?

    Leave a comment:


  • jimjwilliamson
    replied
    Yeesh! I have been racking my brain trying to make this work.. flipped those couple of bits and uploaded first try..

    Thanks Wilters!


    Originally posted by wilters View Post
    For those of you unable to upload Ancestry raw dna data to FTDNA.

    The latest I got from FTDNA Customer Support asserted that "reads for specific SNPs are in the wrong locations in the files". This turns out to be rubbish.

    I imported into Excel a file that would upload and a file that would not. I then got Excel to identify differences between the files. The differences are NOT associated with SNP locations. The differences are purely related to the pre-amble text in the Ancestry raw dna data files. By changing the preamble text, the files will upload.

    The following preamble is from a file that will not upload:

    #AncestryDNA raw data download
    #This file was generated by AncestryDNA at: 05/15/2017 03:51:26 UTC
    #Data was collected using AncestryDNA array version: V1.0
    #Data is formatted using AncestryDNA converter version: V1.0
    #Below is a text version of your DNA file from Ancestry.com DNA, LLC. THIS
    #INFORMATION IS FOR YOUR PERSONAL USE AND IS INTENDED FOR GENEALOGICAL RESEARCH
    #ONLY. IT IS NOT INTENDED FOR MEDICAL OR HEALTH PURPOSES. THE EXPORTED DATA IS


    However, this text will upload:

    #AncestryDNA raw data download
    #This file was generated by AncestryDNA at: 05/28/2017 23:32:38 UTC
    #Data was collected using AncestryDNA array version: V2.0
    #Data is formatted using AncestryDNA converter version: V1.0
    #Below is a text version of your DNA file from Ancestry.com DNA, LLC. THIS
    #INFORMATION IS FOR YOUR PERSONAL USE AND IS INTENDED FOR GENEALOGICAL RESEARCH
    #ONLY. IT IS NOT INTENDED FOR MEDICAL, DIAGNOSTIC, OR HEALTH PURPOSES. THE EXPORTED DATA IS

    Ignoring the different times in line 2, the key changes are:

    Line 3: "V2.0" instead of "V1.0"

    Line beginning "#ONLY": add ", DIAGNOSTIC,"

    When I changed the text as above, two Ancestry files that previously failed (many times) to upload, then uploaded at the first attempt.

    Heaven knows why the FTDNA upload converter concerns itself with the preamble. Clearly GEDMATCH does not because as I and others discovered our unaltered files would readily upload to GEDMATCH.

    And shame on you FTDNA to assert the problem was related to SNPs being in the wrong location. FTDNA: get your house in order!

    There is, of course, another issue related to why Ancestry changed the collection version and other text. Ancestry DNA extractions in Feb and 28 May had "V2.0" text, while extractions on 15 May had "V1.0". I am tackling Ancestry on that point.

    G

    Leave a comment:


  • denative302
    replied
    Originally posted by sunkeeper View Post
    I tired this but didn't delete ALL of the lines, only to *THE EXPORTED DATA IS* I left the other lines beginning with # and it appears to have worked this time! Thanks for this, been trying for weeks to get this file uploaded, now we wait to see if any matches actually show up, I now am in the come back in 24 hours phase.
    I did the same and it seems to have finally worked!

    Leave a comment:


  • Runwithit
    replied
    yvw

    yvw, like you said, the trick is to delete ALL of the lines starting with # at the top of the file, not just half of them and replace them with the lines Ann gave

    #teamwork

    Leave a comment:


  • sunkeeper
    replied
    Originally posted by Runwithit View Post
    Big thanks to Ann for posting the solution, for those of you where it is still not working, I did the following,

    1) Download your raw data from ancestry
    2) Extract the .txt file from the zip file
    3) Open the .txt file (it will take a while to load because there are so many lines)
    4) Select ALL of the lines that start with #
    5) Delete all of the lines that you just selected
    6) Paste the following lines into the .txt document at the top so that they 'replace' all of the lines you just deleted:

    #AncestryDNA raw data download
    #This file was generated by AncestryDNA at: 05/28/2017 23:32:38 UTC
    #Data was collected using AncestryDNA array version: V2.0
    #Data is formatted using AncestryDNA converter version: V1.0
    #Below is a text version of your DNA file from Ancestry.com DNA, LLC. THIS
    #INFORMATION IS FOR YOUR PERSONAL USE AND IS INTENDED FOR GENEALOGICAL RESEARCH
    #ONLY. IT IS NOT INTENDED FOR MEDICAL, DIAGNOSTIC, OR HEALTH PURPOSES. THE EXPORTED DATA IS

    7) Save the file (it will take a little while to save because the file is quite big)
    8) Re-upload the file to FTDNA like you did before

    The above worked for me, my end file size was 17,685kb so file size doesn't make a difference. I agree it sucks that you have to do this, but who cares if it works and it's free

    I tired this but didn't delete ALL of the lines, only to *THE EXPORTED DATA IS* I left the other lines beginning with # and it appears to have worked this time! Thanks for this, been trying for weeks to get this file uploaded, now we wait to see if any matches actually show up, I now am in the come back in 24 hours phase.

    Leave a comment:

Working...
X