Announcement

Collapse
No announcement yet.

Trouble uploading to YSearch

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

  • Trouble uploading to YSearch

    Sorry if there's already a thread about this. If so, feel free to lock this one and direct me to the original thread.

    Whenever I try to upload my results to YSearch, I get this message: "500 - Internal server error. There is a problem with the resource you are looking for, and it cannot be displayed." This was happening several weeks ago too. I've tried uploading the results using both Firefox and Chrome with no success. Ideas?

  • #2
    If you pushed the FTDNA button to upload to ysearch, then contact FTDNA and hopefully they get the issue resolved.

    Comment


    • #3
      I sent them a message. By the way, to clarify, this message appears after I click the save button on YSearch. I'm pretty sure I've been feeling in all the required fields--I don't get the pop-up message telling me I'm missing something.

      Comment


      • #4
        Perhaps the Ysearch entry is getting created properly, and the error message pertains only to the email notice of the password?

        Comment


        • #5
          I searched for my surname, but it doesn't turn up, so I don't think they're getting uploaded at all.

          Comment


          • #6
            This problem was recently discussed on another thread:

            http://forums.familytreedna.com/showthread.php?t=30427

            I don't know if that helps, but it's the same problem.

            Comment


            • #7
              The person in that thread realized that they had created five different accounts (like lgmayka suggested above). I still don't see anything with my surname on it there. I guess YSearch just doesn't like me.

              Comment


              • #8
                The person was I. I just thought the thread might have other info of interest. You could try searching on your markers instead of your surname. (If an identity was created, you match it.) In my case, the identity I was creating was not for myself -- in case you are searching on your name Jones, but creating an ID for your relative Smith.

                Comment


                • #9
                  Forgot Password help- has Error Message

                  "Perhaps the Ysearch entry is getting created properly, and the error message pertains only to the email notice of the password?[/QUOTE]

                  I managed to upload my McIntire Y-Gedcom today. However, when I want to edit my account the password is not working. It has been that way for some time as I have had no success finding it. So today I clicked on 'forgot password' and the error came up mentioned earlier today in this forum:
                  "500 - Internal server error. There is a problem with the resource you are looking for, and it cannot be displayed."

                  Very frustrating.

                  Cindy (McIntire) Johnson-Brother's Kit 164095
                  Last edited by cacitoo; 17 March 2012, 01:28 PM. Reason: A different question on same error message

                  Comment


                  • #10
                    I searched again using both my surname and my STR values, still to no avail. I even tried using two different operating systems (Kubuntu 11.10 and Windows 7) and it didn't make any difference. We'll have to see what FTDNA says, though I assume I won't get a reply till at least Monday.

                    Comment


                    • #11
                      For anyone else having this issue, it appears that the easiest solution is just to call FTDNA and have them create an account for you. Thank you to the nice customer service rep who helped me.

                      Comment


                      • #12
                        It did the same thing to me when I uploaded my dna but the dna DID save.

                        It did the same thing when I tried to upload my GEDCOM file again and it seems to not have saved my GEDCOM file. I hope they fix this soon.

                        Comment


                        • #13
                          I think the rep I talked to said that their IT people had been having trouble with this and weren't really sure what the problem was.

                          Comment

                          Working...
                          X