Get error when uploading ANcestryDNA

[Ann Turner]

435970 SNPs used for this comparison. <- original to itself
435861 SNPs used for this comparison. <- original to fixed

This is using the one to one compare using these kits:
Original: A084257
Fixed: A179561

So those GEDmatch kits don't have the full complement of SNPs from the original AncestryDNA download (600K+). It looks like GEDmatch just uses whatever SNPs are present in its "template."

The reason I asked is that a fellow was wondering if he should upload his fixed kit to GEDmatch. I don't see any compelling reason to do that, do you?

[JeremyGlen2017]

The converter on the website worked like a charm for my two kits that weren't uploading from Ancestry.

I tried the downloadable version, but it is stating that I'm missing a dll, and I don't feel like trying to figure that one out right now.

Thanks so much for getting these created!!

[chrisbonisa]

So those GEDmatch kits don't have the full complement of SNPs from the original AncestryDNA download (600K+). It looks like GEDmatch just uses whatever SNPs are present in its "template."

The reason I asked is that a fellow was wondering if he should upload his fixed kit to GEDmatch. I don't see any compelling reason to do that, do you?

No, I don't really see a point in doing that, all you would be doing is losing a tiny percentage of snps for no reason

[backdraftuk]

If you do use the tool, please respond in here and let others know if it works or not. So far in my testing its working 100%, but the more people that try it the more we will know if this is a solution until FTDNA resolves it themselves.

Brilliant, I had been trying for two weeks to upload from Ancestry, read this and did it in minutes. That was 2 days ago but it has taken FTDNA 2 days to allow me to post here. So if joining the forum takes 2 days, how long will it take them to fix the upload?

Backdraft

[mesamike]

My V2 kit doesn't upload

I see all these posts about converting V1 data to V2 format, but I've got a V2 format data set, and it still won't upload.

Here's the header:
See anything wrong?

#AncestryDNA raw data download
#This file was generated by AncestryDNA at: 10/07/2017 06:13:38 UTC^M
#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.
rsid chromosome position allele1 allele2^M

[prairielad]

I see all these posts about converting V1 data to V2 format, but I've got a V2 format data set, and it still won't upload.

See page 18 of this post for fix

[chrisbonisa]

I see all these posts about converting V1 data to V2 format, but I've got a V2 format data set, and it still won't upload.

Here's the header:
See anything wrong?

#AncestryDNA raw data download
#This file was generated by AncestryDNA at: 10/07/2017 06:13:38 UTC^M
#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.
rsid chromosome position allele1 allele2^M

This tool is for "fixing" a v2 file, which it sounds like is the issue you are having....

http://www.mapmy23.com/tools/ancestry_ftdna_fix.php

[BigPhilly808]

THANK YOU THANK YOU!

Yeah I didn't notice the PM, but I've read and responded to it. I've built out a tool that seems to work 100%. The key to solving it is a combination of what I was doing before, filling in the blank template file of a working file with the data from the non-working one, but keeping the I's and D's from the template and not zeroing the entire thing and also filling everything in by position number instead of RSID, which is what I was doing the first go around.

I stuck it up on one of my websites where I'm doing some other DNA stuff, anyone can feel free to use it if they wish:

http://www.mapmy23.com/tools/ancestry_ftdna_fix.php

If you do use the tool, please respond in here and let others know if it works or not. So far in my testing its working 100%, but the more people that try it the more we will know if this is a solution until FTDNA resolves it themselves.

Your are amazing!!!! So happy i decided to check this forum again!! I FINALLY was able to get my grandfathers raw data uploaded!!! MAHALO NUI LOA! (Hawaiian for Thank you VERY Much!)

[RichardMW2]

This tool is for "fixing" a v2 file, which it sounds like is the issue you are having....

http://www.mapmy23.com/tools/ancestry_ftdna_fix.php

Many thanks.
I had this problem today for a cousin's DNA and the 23andMe tool fixed it.

[chrisbonisa]

Your are amazing!!!! So happy i decided to check this forum again!! I FINALLY was able to get my grandfathers raw data uploaded!!! MAHALO NUI LOA! (Hawaiian for Thank you VERY Much!)

Na'u ka hau'oli!

Many thanks.
I had this problem today for a cousin's DNA and the 23andMe tool fixed it.

So glad this is helping people!

[Obriejen]

I'm surprised that the companies still aren't fixing this and people are having to go through a third party method...

[dna]

I'm surprised that the companies still aren't fixing this and people are having to go through a third party method...

Company A will not fix it.

Company A has switched on purpose.

Was I in their boardroom? No.


Mr. W

[Jim Barrett]

When will we ever learn?

Company A has a long history of starting something, messing it up and then dropping it. Yet people keep buying products from company A.

I wasn't in their board room either, but I know history repeats itsself.

Anyone wanting good Family Finder results at FTDNA needs to buy their test from FTDNA and then transfer their results to the other companies. Then they can get mad at the other companies for not accepting transfers.

[swiftrabbit]

Me too!

I also just tried to upload my Ancestry raw data and received the message. I don't even know what that means never mind trying to solve the problem. Please help!!! I can't afford a new DNA test right now.

[prairielad]

I also just tried to upload my Ancestry raw data and received the message. I don't even know what that means never mind trying to solve the problem. Please help!!! I can't afford a new DNA test right now.

It is a long thread, but the actual fix is give on page 18 of this post...Read from page 18 on...
Link to fix is as follows

http://www.mapmy23.com/tools/ancestry_ftdna_fix.php