GEDCOM UPLOAD ERRORS
There have been various people reporting errors on the GEDCOM upload to FS Genealogies. The load intitiates - but almost appears to time out - before the progress bar hits 100 %. (a time out issue??)
I know there are max file size limits (some places say 300 MB other places 100 MB) the people reporting the error have been uploading files UNDER these size limits.
can the rest of you see if you face the same type of problem (with files that range between 30 and 100 MB) ?
Can the developers/engineers look into this?
Comments
-
FamilySearch
.
FYI
.
A recent post, in the "Community.FamilySearch" Forum, that most likely prompted this post ...
.
(General) Question
12 January 2021
.
I have been unable to complete an upload of a gedcom file (31.6 MB) for 4 days. I get 1/2 way there and it stops. I have Family Tree Maker 2019 and exported it correctly.
.
.
As an aside ...
.
Apart from everything else (ie. all the various possibilities )...
.
As proffered in the aforementioned ...
.
The problem/issue MAY relate to "Slow" INTERNET "Speed" of Users/Patrons.
.
Despite that the GECOM Files being uploaded are less than 100 MB, the maximum size allowable to be uploaded into the "Genealogies" Part of 'FamilySearch'.
.
Just a thought, to consider.
.
Brett
.
0 -
I am pretty sure the issue is NOT related to extra slow INternet connections.
I have had the same experience - and my INternet is not slow.
0 -
Logically, it would make no sense for a system to simply hang or stop in the middle of an upload due to some king of limit without throwing up some kind of message. Furthermore, size checks can be made PIOR to starting the upload.
I also believe that I heard somewhere that in addition to the file size limit, there is also a limit to the number of person records that can exist in the GEDCOM file (100MB files can contain a LOT of person records). But here again, even if that was a factor here, a message would normally be provided.
So something is definitely breaking for you. It could be a speed issue as the assimilation rate of the FS server farm can fluctuate--especially if certain servers need to be re-booted. This would be regardless of how fast your local connection was. But it is just as likely that software in that area has been "bumped" recently and needs to be fixed.
0 -
who knows - - maybe someone bent on stopping GEDCOM processing - sabatoged it . . .
LOL
:-)
0 -
the message thaat pops up is just a very general failure message that says "try again later"
which leads me to beleive it is something like you say - either plain bug - or the rate of assimilation is so slow it does time out. but it seems to happen at 30 seconds which you would think would be under some max time limit.
0 -
Ah-hah! That "Try again later" seems to be a common error message in FS. It is likely some handshaking protocol between servers is timing out. I've seen that happen when a server has gone rogue and needs rebooting, but I've also seen it in heavy load situations which can not only happen during the day at peak usage, it can also occur when backups are running or they are pulling a snapshot of the system into the Beta test site.
Yea, just "Try again later" and see if you continue to have the issue. I run into this occasionally when trying to access certain sources. I "Try again" immediately 2 or 3 times and usually that does it for me. Otherwise, the following day has usually worked. It is something inside the FS system.
0 -
right but for the GEDCOM thing - it has been that way for many weeks if not months
0 -
Oooh! who knows -- maybe someone bent on stopping GEDCOM processing - sabotaged it…
:-)
0 -
For what it's worth, I just ran a test by uploading a GEDCOM file that was 3.5MB and contained 12,500 records. It succeeded in 2 minutes.
Note that after the file is uploaded (as part of that process) it is converted into the FSFT format so that it can be viewed with the typical pedigree chart viewer already in the system, so obviously some time is involved in that activity as well.
0 -
One person that previsouly reported this - is now reporting that the error has gone away.
0
