If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Looking at an ancestry file that fails uploading and comparing it to an original Ancestryv2 file, as well as comparing number of SNPs used by FTDNA, I have come up with roughly the following numbers
These smaller Ancestry files have roughly 5261 less SNPs that FTDNA utilizes
I got this response today from Ancestry when I asked them for an update:
Hello April,
Thank you for contacting Ancestry in regard to your report on not being able to download your RAW DNA data.
The problem has been reported to our developers and hopefully will be corrected in the near future. We will contact you via email when this issue is resolved. Your feedback helps us correct errors and improve the website. Thank you for your patience with us in this matter.
I've noticed what might possibly be a theme with this issue. My two aunts and my sister were able to upload their data, but my father and brother in law couldn't. CFegley mentioned it was her husband and son's that wouldn't upload. Has anyone had the same error message when trying to upload a female's DNA file?
Someone on a Facebook group posted that SHE couldn't upload her own raw data. So, yes, it crosses both genders, though it does seem to be more prevalent with male files.
For autosomal transfers.
"For a limited time only, unlock your full-featured Family Finder account for only $10 with the below promo code! You’ll get enhanced results plus gain access to Family Finder’s unlimited matches and industry-leading tools.
USE CODE: ATUL0917"
I've noticed what might possibly be a theme with this issue. My two aunts and my sister were able to upload their data, but my father and brother in law couldn't. CFegley mentioned it was her husband and son's that wouldn't upload. Has anyone had the same error message when trying to upload a female's DNA file?
p.s. despite my wishful thinking, their update yesterday must not have been to fix this issue as I tried again and it's still not working. I also expect that I will get email confirmation once they've implemented the fix.
Guess what? I received an email back from Ancestry Support this afternoon. It was a SURVEY to see what I thought of how they'd done in helping resolve my issue! My thoughts, of course were, why thank you ever so much for asking and for providing the opportunity to give constructive feedback! Here ya go!
"First, you're sending this email prior to my issue being resolved. So, what could you have done better? How about actually addressing my issue! Second, TRAIN your front line employees to answer questions and when they don't know, they need to be truthful and escalate the issue, not make up an "answer" which people who have knowledge of how things are supposed to work will know is a "fake" answer. Third, have people available for all types of questions...some can tell people how to set up their account, start a tree, etc., but if you're offering DNA testing, you need people who can actually answer questions about the files and those people need to be available to talk to your customers. They shouldn't be tucked away into a room or building and not accessible to anyone, not even your presumed "managers" who, themselves are clueless and actually think saying that they don't get that many questions about "X" so they don't need to know anything about it and it is okay for them to "guess" at what the problem "might" be! REALLY???!!! I worked in a call center for Property and Casualty insurance and had to be LICENSED to talk to people. Your employees should at the very least be taught terminology for genealogy and genetics and know what they should and shouldn't try to address!"
I tried to keep my "cool" and had to end it there or that would have gone straigh out the door. LOL. Have you heard anything?
Hello,
I opened a ticket for this same problem on Saturday night after reading you guys' posts in here. I was trying to upload a new tester's results, they had just come in on the morning of the 23rd. The file size of the raw data is 5.7mb. I think something changed between Sept 20th and the 23rd because my other tester's results that hit on the 20th is the usual 5.9mb and it uploaded to FTDNA beautifully.
So, I opened a ticket, told them the different file sizes and that I could see there were rsids missing in the second one. I also had to allow them access to my account by letting them define a new password.
I'm still waiting for word of a solution as well, hoping to take advantage of the coupon!
I'd appreciate it if any of you could post updates as you hear or have any success. I'll do that same.
Teresa
Were the missing rsids across several chromosomes?
Also, were the files downloaded at approximately the same time? If you downloaded a file that currently works would you receive an identical file to the first one?
Yes, the missing rsids were actually across all the chromosomes as Ancestry lists them. The number of rsids missing from each varied from chromosome to chromosome.
Earlier this week, I finished composing an email to [email protected], after having had numerous phone conversations with CSR's up to mid-level managers, presumably. Like you, I pointed out that my husband and son's files are missing in excess of 18,000 lines of data (rsids / alleles). I explained the various excuses I'd been given and, essentially, said enough was enough.
Would you mind posting or PMing the part of your message where you describe the problem? I would love to open a ticket on my account for the issue, and this is exactly what I was assured was absolutely impossible due to privacy reasons.
Were the missing rsids across several chromosomes?
That's an interesting question. One easy way to check might be for the person with a working and non-working file to upload them to GEDmatch and compare the DNA File Diagnostic Utility stats.
Note that it is entirely possible for Illumina to modify its base-calling software and deprecate some SNPs that aren't performing well across the board; or AncestryDNA could be doing some post-processing itself. IF that's the case, FTDNA simply needs to allow some slack when importing files: just look at everything and decide at the conclusion if there are enough SNPs for comparison. That's what GEDmatch does.
Leave a comment: