Announcement

Collapse
No announcement yet.

Get error when uploading ANcestryDNA

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

  • nooni
    replied
    Originally posted by OldFinneyKid View Post
    I also independently arrived at the solution since 2 of my kits finished on Ancestry yesterday. FTDNA Customer Support correctly pointed me to the version discrepancy on line 3 between V1 and V2. I called Ancestry, and they were not aware they had changed anything, and they said if I need it to say V2, then change it to V2. Essentially, not their problem.

    I changed line 3 to reference V2 instead of V1, recompressed the file, and the transfer worked perfectly. I did not have to make the second correction some people have noted.

    Just for my own information, I had a copy of the raw data from an Ancestry kit I loaded successfully 2 weeks ago, and it had the V2 in line 3. I downloaded it today and it now has V1 in that spot, so the headers Ancestry is building currently will have the problem, no matter when the kit finished.
    Did your final file sizes match the numbers given earlier in the thread? FTDNA and WeGene are both throwing up errors to my .zip file no matter what text changes I'm making.

    Leave a comment:


  • OldFinneyKid
    replied
    Autosomal Transfer from Ancestry

    I also independently arrived at the solution since 2 of my kits finished on Ancestry yesterday. FTDNA Customer Support correctly pointed me to the version discrepancy on line 3 between V1 and V2. I called Ancestry, and they were not aware they had changed anything, and they said if I need it to say V2, then change it to V2. Essentially, not their problem.

    I changed line 3 to reference V2 instead of V1, recompressed the file, and the transfer worked perfectly. I did not have to make the second correction some people have noted.

    Just for my own information, I had a copy of the raw data from an Ancestry kit I loaded successfully 2 weeks ago, and it had the V2 in line 3. I downloaded it today and it now has V1 in that spot, so the headers Ancestry is building currently will have the problem, no matter when the kit finished.

    Leave a comment:


  • pbear
    replied
    This solution worked great.

    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:


  • joe4227
    replied
    Ancestry header is corrupt

    I independently arrived at the same solution, after comparing several Ancestry Raw Data Downloads going back to March.

    Indeed, it appears Ancestry somehow have picked up an old file header when building these text files. I have notified Ancestry as well as FTDNA support.

    On changing the header to "AncestryDNA array version: V2.0" everything works fine once again. There is NOTHING wrong with the data itself.

    Uploaded file immediately got matches to know linked individuals in our trees.

    And YES, this IS the correct solution to "Error uploading file "XXXXXXX" as starting this thread...

    It's been a short trip, but a long journey...

    Leave a comment:


  • MayaXo
    replied
    How long did it take your matches to show up?!?
    I am still waiting, since May 30... getting the 'check again in 24 hours' msg..

    Leave a comment:


  • Grant Brown
    replied
    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
    Thanks heaps!!!!

    It worked for me about a week ago, I now have my matches.

    Thanks again
    Grant.

    Leave a comment:


  • ada
    replied
    I uploaded the same file (with the correct header) the next day and it worked the first time i tried. I'm now waiting for my matches.

    Leave a comment:


  • Darren
    replied
    Hi Graham,

    I sent you a private message. Thanks.

    -Darren
    Family Tree DNA

    Leave a comment:


  • ada
    replied
    Originally posted by wilters View Post
    Ada

    Ive just read that you are getting a different rejection message. That is significant. There may be a temporary problem at FTDNA's end. I suggest you leave it for a few hours and try again.

    Graham
    Will do! Thanks

    Leave a comment:


  • wilters
    replied
    Ada

    Ive just read that you are getting a different rejection message. That is significant. There may be a temporary problem at FTDNA's end. I suggest you leave it for a few hours and try again.

    Graham

    Leave a comment:


  • wilters
    replied
    Ada

    Since the file size is now "correct" and the text seems to be that which worked for me and two others, I am at a loss as to why it will not upload.

    You imply that Ancestry have changed something compared to your earlier download. Perhaps they have changed something else, and this is causing the problem.

    If you have previously successfully uploaded a file, you might try comparing that .txt file with the one that will not upload. I did this by importing both to Excel on separate worksheets and then getting Excel to show the differences.

    Graham

    Leave a comment:


  • ada
    replied
    The only difference is that instead of 'corrupted file' error I was getting before (with the older files) the message I get today is:
    The specified file 'AncestryDNA.txt' could not be uploaded. Please try again.

    I keep trying but it just doesn't work.

    Leave a comment:


  • ada
    replied
    Originally posted by wilters View Post
    Ada

    I suggest you get a fresh download from Ancestry and then check the size and preamble text.

    Graham
    Hi graham,
    The size is actually correct when i click on file properties
    17.2 MB (18,110,076 bytes)
    I have downloaded the file twice today, tried to upload at least ten times, both zipped and unzipped. .Nothing works.
    I also downloaded the raw data from them twice before and in those older files the header is wrong. In the file i downloaded today the header is already corrected, it's just as you say it should be:

    #AncestryDNA raw data download
    #This file was generated by AncestryDNA at: 05/31/2017 21:31:21 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
    #SUBJECT TO THE AncestryDNA TERMS AND CONDITIONS, BUT PLEASE BE AWARE THAT THE
    #DOWNLOADED DATA WILL NO LONGER BE PROTECTED BY OUR SECURITY MEASURES.
    #WHEN YOU DOWNLOAD YOUR RAW DNA DATA, YOU ASSUME ALL RISK OF STORING,
    #SECURING AND PROTECTING YOUR DATA. FOR MORE INFORMATION, SEE ANCESTRYDNA FAQS.
    #
    #Genetic data is provided below as five TAB delimited columns. Each line
    #corresponds to a SNP. Column one provides the SNP identifier (rsID where
    #possible). Columns two and three contain the chromosome and basepair position
    #of the SNP using human reference build 37.1 coordinates. Columns four and five
    #contain the two alleles observed at this SNP (genotype). The genotype is reported
    #on the forward (+) strand with respect to the human reference.

    Leave a comment:


  • wilters
    replied
    Ada

    I suggest you get a fresh download from Ancestry and then check the size and preamble text.

    Graham

    Leave a comment:


  • ada
    replied
    None of this works for me. :-( My file will not upload.
    BTW, the size of the file is 17,686 KB and the ancestry results were received by me on 5/13.
    Anybody else still having the same problem?

    Leave a comment:

Working...
X