Family Historian User Group

Hi,

I just ran into a problem when trying to import a FH 6.2.7 GEDCOM to TNG 12.3.
TNG throws a dialogue with the message "Import could not be resumed. It may have already finished". The developer of TNG (Darrin) gets the same result, and he believe something is wrong with the GEDCOM.

I also tried exporting using the "Export Gedcom File" 3.9 plugin, selecting TNG as Export Mode, but that did not help.

Anyone seen this before, or any ideas?

Jan

Hi Jan.
A bit more background history would help, like have you successfully migrated a GEDCOM from FH to TNG before, or is this your first attempt? I suspect the latter, as you did not realise you needed to use the Plugin.

It is not surprising that an unconverted standard FH Project GEDCOM file would cause TNG problems.
Most products, including FH, have custom extensions and dialects of GEDCOM not understood by other products.
So, it is absolutely essential that you use the Export Gedcom File Plugin in TNG mode to produce the GEDCOM.
Hopefully, you used the GEDCOM file in your Project's ...\Public\Export folder and followed the instructions in the plugins:help:export_gedcom_file:tng_the_next_generation#import_details|> Export Gedcom File ~ (TNG) The Next Generation > Import Details.

Also, ensure you have followed the advice in the plugins:help:export_gedcom_file:export_gedcom_file|> Export Gedcom File Plugin help page where it says:
"To avoid potential problems, it is advisable, before running the Plugin, to use the following:" and lists a number of commands and Plugins to run.

Thanks for the information Mike,

I have not been very active (yet) since switching from TMG to Family Historian, so you are right that I do not have much experience with FH. My last transfer to TNG may well have been from TMG.
I am used to challenges transferring information via GEDCOM between different software, but I guess I was expecting a more graceful behaviour from TNG than immediate abortion with a cryptic error message.

Anyway, I will look at your information and try again

Jan

The non-graceful behaviour was due to limitations in php.ini, so not really a TNG or FH issue.

Anyway, your information will be very useful, so thanks again for that,

Jan

Sorry Jan, I do not understand. How does php.ini get involved, yet not a TNG or FH issue?
Could you please explain in more detail why the symptoms arise only with your GEDCOM and not others.
What is special about these circumstances that cause the TNG import to fail?
Has the problem been fixed or not?
If it has been fixed what was the cure?
These details are important so that we can warn other users on how to avoid the same problem.

I am running TNG on my own server, so I'm depending on my own setup of apache, mysql and php. At some point, maybe connected to an upgrade, I have lost my php-configuration. Specifically, upload_max_filesize and post_max_size have been set too low for php to accept bigger gedcom files.

Smaller gedcom files could be imported. My problem has been solved by increasing the mentioned settings in php.ini.

Jan

Excellent Jan. Thank you. That makes perfect sense.