Tweet
Still not working for me...
-
-
I received this from FTDNA Support:
Hello,
Thanks for contacting us. FTDNA accepts both V1 and V2 of Ancestry's autosomal DNA test.
Unfortunately, the problem with the autosomal raw data file is on Ancestry's end. There is an issue with the size of some of their files (The formatting of the columns is skewed-— the data is not lining up in the proper column or category. Any time a rsid# in the first column is smaller than 5 digits then the rest of the data on that line is skewed and does not read the proper column or category. The same thing happens where the position number, in the third column, is smaller than 8 digits. That skews the rest of the columns in that line.) and that is why some of them are not uploading, like what you have experienced.
Other sites with transfers available, like Gedmatch and MyHeritage, have different transfer processes. Their upload accepts files of any size and format, which is why you would have been able to upload the file to either or both of those websites with no trouble. However, the files must be in the same size and format as all other Ancestry V1 or V2 files in order to work with FTDNA's upload so that our system can properly translate the data and give Family Finder results.
I apologize again for the trouble you are experiencing when trying to transfer. Please contact Ancestry for an accurate raw data file.
Best,
Anyone know how I ask AncestryDNA for an accurate raw data file?Comment
-
If you open the .txt file from Ancestry you can see the incorrect (i.e. "skewed") formatting exactly as reported above.
I downloaded again from Ancestry a few moments ago and the "skewed" formatting is till there.
I have reported to Ancestry via their Support/Contact Us page. I suggest others do the same to attract their attention.
GComment
-
Having said the above, Ancestry's pre-amble in their .txt download says "data is provided below as five TAB delimited columns". This is true - which is doubtless why GEDMATCH, for example, can read my "skewed" file. It is not therefore entirely clear why FTDNA does not accept the tab delimiting as well.
I can see this degenerating into a dispute between Ancestry and FTDNA.Comment
-
FTDNA Customer Support have told me also that Ancestry DNA files must be the same size and format. However, I have checked the size and format of two Ancestry DNA files I successfully transferred to FTDNA a couple of months ago with the size and format of the file that is presently not being accepted by FTDNA. The size and format are EXACTLY THE SAME! The size is 18,110,076 bytes, they are all tab delimited, and they all display exactly the same "skew" (i.e. non-alignment in columns).
I have asked FTDNA Customer Support for a further explanation. As far as I can tell at present, the problem is NOT at Ancestry's end.
GrahamComment
-
Ancestry have now confirmed to me they have changed nothing in the raw DNA data files at their end. And, as noted in a previous post, this agrees with my examination of Ancestry raw DNA data files over the last couple of months.
I have contacted FTDNA for a further explanation and resolution of this problem. I have not had a response !!!
GrahamComment
-
AFAIK, all the companies use tab-delimited files. I have not seen a raw data file from MyHeritage, though. The major difference with AncestryDNA is that they separate the two alleles into two columns. Could it be that FTDNA changed the way they handle that?Comment
-
Not working again...
For some reason, despite the problem uploading DNA from Ancestry last week, FTDNA accepted my results after several tries (over several days). I note that other people still had the problem - and still do. Now I am trying to upload results for another family member and am getting a different error message:Originally posted by Ann H View Post
"The specified file 'dna-data-2017-05-27.zip' could not be uploaded. Our records indicate the file you uploaded is already in our system. If you have not uploaded this file before and continue to receive this error, please contact support."
This makes no sense - it could not be uploaded, yet it says it is already in their system - which it is not! Customer Support please advise. Thank you.Comment
-
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.Comment
-
A woman with new Ancestry results just joined one of my projects. She had no problem and had FF matches within 24 hours. That is good.
The same woman added her Ancestry data to GEDmatch and matches my wife as shown here:
Chr Start Location End Location Centimorgans (cM) SNPs
16 --- 83,201,194 --- 88,668,856 ---- 14.4 ---- 953
She doesn't match my wife on FTDNA where my wife tested.Comment
-
Still not working...
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!Originally posted by John McCoy View PostComment
-
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.
GComment
-
Not sure this is the solution
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....Originally posted by wilters View PostComment
-
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.
GrahamComment
-
Comment