I have seen this error message during heavy server traffic or problematic connection issues. I waited a day and things worked fine. In my case, I think it was Ancestry server issues.
↧