Announcement

Collapse
No announcement yet.

Get error when uploading ANcestryDNA

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

  • wilters
    replied
    To MayaXo

    Well done!

    For others: my successfully uploaded file was also set to "no access", indicating that is probably not critical. The two "lost" bytes could be made up by inserting two spaces in the preamble. Note that the original preamble text has two spaces after the full stop at the end of sentences.

    G

    Leave a comment:


  • MayaXo
    replied
    Nevermind! it just worked!

    i did change something in the file info.... in "sharing & permission"
    "everyone" was set to "no access" i changed it to "read only"
    not sure if thats what helped, but either way, Thank you!! for your patience

    Leave a comment:


  • MayaXo
    replied
    Originally posted by wilters View Post
    I too am on Macs: is there any other way to go?

    For file size: in Finder, right click on the file and select Get Info

    G
    lol

    it's 18,110,074 bytes (18.1 MB on disk) !! is there a way to change it?!

    Leave a comment:


  • wilters
    replied
    I too am on Macs: is there any other way to go?

    For file size: in Finder, right click on the file and select Get Info

    G

    Leave a comment:


  • MayaXo
    replied
    Originally posted by wilters View Post
    To MayoXo

    Two of us have succeeded by changing the preamble text, so I am reasonably confident it works.

    1. Make sure the text is EXACTLY the same as in the example I posted earlier.

    2. The resultant file size should be 18,110,076 bytes.

    In an earlier reply to me FTDNA said that, unlike e.g. GedMatch, file sizes had to be of a particular size for transfers to work. It would be extraordinarily stupid if FTDNA really required every character of the preamble to be the same. It would be slightly less stupid (only slightly) if they required a particular file size!

    G

    Thank you

    This is what I have:

    #AncestryDNA raw data download
    #This file was generated by AncestryDNA at: 05/14/2017 11:43:20 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

    I am on a mac comp and not sure how to make sure the file size is 18,110,076 bytes :/

    Leave a comment:


  • wilters
    replied
    To MayoXo

    Two of us have succeeded by changing the preamble text, so I am reasonably confident it works.

    1. Make sure the text is EXACTLY the same as in the example I posted earlier.

    2. The resultant file size should be 18,110,076 bytes.

    In an earlier reply to me FTDNA said that, unlike e.g. GedMatch, file sizes had to be of a particular size for transfers to work. It would be extraordinarily stupid if FTDNA really required every character of the preamble to be the same. It would be slightly less stupid (only slightly) if they required a particular file size!

    G

    Leave a comment:


  • MayaXo
    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
    oh man, did not work for me (((
    i'm losing hope...

    Leave a comment:


  • wilters
    replied
    Ancestry have now replied to my asking why they had changed the version of the array for dna testing:

    "Unfortunately, we do not have information as to why one test was done with a different version of the array than the other two. The results for all are accurate, as our algorithm takes the information from both versions of the test. We are not responsible if a third party is unable to accept one version or the other of our AncestryDNA test."

    I have told them that "not having information" is not good enough and have asked them to find out.

    On the second point (i.e. its FTDNA's fault not ours) I have told them that Ancestry and FTDNA's customers have an expectation to be able to transfer autosomal dna data and that both companies therefore have an obligation to their customers to continue to liaise such that transfers happen without the difficulties we have been experiencing.

    Nothing from FTDNA yet. I shall keep you posted.

    G

    Leave a comment:


  • michaelgo
    replied
    Originally posted by Darren View Post
    Thank you for your replies. I will provide this information to the management team. I don't know if this is an IT bug or if Ancestry changed the files recently so it is not compatible with the current system. I will let you know what I find.

    I was wondering if this is only a problem with Ancestry or if 23andme transfers are having the same issue. If anyone has been receiving the error with 23andme please let me know.

    -Darren
    Family Tree DNA
    Hi Darren, same problem with MyHeritage. Worked before, now it doesn't anymore.

    Leave a comment:


  • michaelgo
    replied
    Same problem, only with MYHERITAGE.
    Files are exactly the same as before, and now it doesnt work anymore.

    Leave a comment:


  • migoblu
    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, wilters. It worked!!!!!

    Leave a comment:


  • wilters
    replied
    Ann

    With respect, I believe your error message was different from the one that started off this thread which was something along the lines of:

    "The specified file 'xxxxxxx' 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."

    My comments on "how to fix" by changing the preamble only apply to those who have received the above error message and who have the preamble text as I specified. Also the text changes have to be exact.

    Graham

    Leave a comment:


  • Ann H
    replied
    Not sure this is the solution

    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
    Thank you for all of that information - I tried it as I also have 2 copies of DNA, one of which uploaded and the other which will not. I changed the files as you suggested - although the reverse seemed to be true as regards V1 and V2. Anyway, it did not work and now I have a made a complete mess as I had the wrong account open and uploaded the second persons account (which previously would not upload) to my account - where it was accepted.....!!!!! I have sent a message to customer support asking them to reverse the transaction, but it begs the question - why would one existing account accept the results, but not a new account....

    Leave a comment:


  • wilters
    replied
    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:


  • Ann H
    replied
    Still not working...

    Originally posted by John McCoy View Post
    The error message appears to be saying that the file you tried to upload had the same NAME on YOUR computer as a file that you uploaded previously. Is it possible you selected the wrong file from your computer when you attempted the upload to FTDNA? At least that's something you can check, and you could try downloading the file from Ancestry again, being sure it ends up with a unique name on your computer.
    Thanks John. I just did as you suggested - fresh download from ancestry and tried uploading to FTDNA. Unfortunately I got the same message again. Frustrating!

    Leave a comment:

Working...
X