I have just purchased and installed the upgrade to FH V5, upgrading a full version installation of V4. Upon running the program for the first time, I got the following Exception Report, which rather surprised me as I've never had this with any previous version of FH (including V4), and have not noticed it mentioned elsewhere in relation to the upgrade.
Is this something I need to be concerned about? All the exceptions seem to be 'INFO ONLY', including some 'Loaded uncategorised data' errors; presumably I need to correct them in some way?
Family Historian Exception Report - Wednesday 28 Mar 2012
=========================================================
Lines marked 'EXCLUDED:' indicate data which has not
been loaded, and explain why it wasn't loaded.
Indented lines marked 'EXCLUDED BRANCH LINE:' indicate
data lines which are not necessarily invalid in
themselves but which have had to be excluded as a
consequence of excluding other lines.
Lines marked 'INFO ONLY:' indicate data that has
been successfully loaded, but where special action
was needed to load it (e.g. GEDCOM errors detected
and automatically corrected by Family Historian).
---------------------------------------------------------
Record Type=Individual. Gedcom Id=I3. Record Number=3.
l.711 - INFO ONLY: Loaded uncategorised data (non-GEDCOM): '2 CONT McGill University, Montreal, Canada'
Record Type=Individual. Gedcom Id=I33. Record Number=15.
l.1414 - INFO ONLY: Loaded uncategorised data (GEDCOM extension): '1 _UID 87C0D09CDB7FD611A4030010B50D77816599'
Record Type=Individual. Gedcom Id=I38. Record Number=19.
l.1626 - INFO ONLY: Loaded uncategorised data (GEDCOM extension): '1 _UID 80C0D09CDB7FD611A4030010B50D77815E29'
Record Type=Individual. Gedcom Id=I39. Record Number=20.
l.1802 - INFO ONLY: Loaded uncategorised data (GEDCOM extension): '1 _UID 4331B0A76A7BD611A3F40010B50D7781F8DE'
Record Type=Individual. Gedcom Id=I40. Record Number=21.
l.1914 - INFO ONLY: Loaded uncategorised data (GEDCOM extension): '1 _UID 85C0D09CDB7FD611A4030010B50D77816379'
Record Type=Individual. Gedcom Id=I41. Record Number=22.
l.2032 - INFO ONLY: Loaded uncategorised data (GEDCOM extension): '1 _UID 89C0D09CDB7FD611A4030010B50D778167B9'
Record Type=Individual. Gedcom Id=I42. Record Number=23.
l.2117 - INFO ONLY: Detected & fixed field format error (data moved to Note Field): '2 TYPE Witness'
l.2121 - INFO ONLY: Detected & fixed field format error (data moved to Note Field): '2 TYPE Witness'
l.2125 - INFO ONLY: Detected & fixed field format error (data moved to Note Field): '2 TYPE Witness'
Record Type=Individual. Gedcom Id=I57. Record Number=25.
l.2265 - INFO ONLY: Loaded uncategorised data (GEDCOM extension): '1 _UID 3831B0A76A7BD611A3F40010B50D7781ED2E'
Record Type=Individual. Gedcom Id=I133. Record Number=35.
l.2871 - INFO ONLY: Loaded uncategorised data (GEDCOM extension): '1 _UID 83C0D09CDB7FD611A4030010B50D77816159'
Record Type=Individual. Gedcom Id=I137. Record Number=39.
l.3299 - INFO ONLY: Detected & fixed field format error (data moved to Note Field): '2 TYPE Witness'
Record Type=Individual. Gedcom Id=I146. Record Number=41.
l.3389 - INFO ONLY: Loaded uncategorised data (GEDCOM extension): '1 _UID 8BC0D09CDB7FD611A4030010B50D778169D9'
Record Type=Individual. Gedcom Id=I306. Record Number=43.
l.3483 - INFO ONLY: Loaded uncategorised data (GEDCOM extension): '1 _UID 3D31B0A76A7BD611A3F40010B50D7781F27E'
Record Type=Individual. Gedcom Id=I307. Record Number=44.
l.3581 - INFO ONLY: Loaded uncategorised data (GEDCOM extension): '1 _UID 3F31B0A76A7BD611A3F40010B50D7781F49E'
Record Type=Individual. Gedcom Id=I308. Record Number=45.
l.3622 - INFO ONLY: Loaded uncategorised data (GEDCOM extension): '1 _UID 4131B0A76A7BD611A3F40010B50D7781F6BE'
Record Type=Individual. Gedcom Id=I309. Record Number=46.
l.3688 - INFO ONLY: Loaded uncategorised data (GEDCOM extension): '1 _UID 4531B0A76A7BD611A3F40010B50D7781FAFE'
Record Type=Individual. Gedcom Id=I310. Record Number=47.
l.3810 - INFO ONLY: Detected & fixed field format error (data moved to Note Field): '2 TYPE Witness'
l.3814 - INFO ONLY: Detected & fixed field format error (data moved to Note Field): '2 TYPE Witness'
l.3818 - INFO ONLY: Detected & fixed field format error (data moved to Note Field): '2 TYPE Informant'
l.3837 - INFO ONLY: Loaded uncategorised data (GEDCOM extension): '1 _UID 4731B0A76A7BD611A3F40010B50D7781FC1E'
Record Type=Individual. Gedcom Id=I311. Record Number=48.
l.3895 - INFO ONLY: Loaded uncategorised data (GEDCOM extension): '1 _UID 4931B0A76A7BD611A3F40010B50D7781FE3E'
Record Type=Individual. Gedcom Id=I318. Record Number=53.
l.4051 - INFO ONLY: Loaded uncategorised data (GEDCOM extension): '1 _UID 3B31B0A76A7BD611A3F40010B50D7781F05E'
Record Type=Individual. Gedcom Id=I320. Record Number=54.
l.4077 - INFO ONLY: Loaded uncategorised data (GEDCOM extension): '1 _UID B91BA38EA4E50746A39D9E6CAEB3E2C83018'
Record Type=Individual. Gedcom Id=I346. Record Number=66.
l.4873 - INFO ONLY: Loaded uncategorised data (GEDCOM extension): '1 _UID 7BC0D09CDB7FD611A4030010B50D778159D9'
Record Type=Individual. Gedcom Id=I347. Record Number=67.
l.4965 - INFO ONLY: Loaded uncategorised data (GEDCOM extension): '1 _UID 7EC0D09CDB7FD611A4030010B50D77815C09'
Record Type=Individual. Gedcom Id=I348. Record Number=68.
l.5080 - INFO ONLY: Detected & fixed field format error (data moved to Note Field): '2 TYPE Will'
l.5135 - INFO ONLY: Detected & fixed field format error (data moved to Note Field): '2 TYPE Witness'
l.5139 - INFO ONLY: Detected & fixed field format error (data moved to Note Field): '2 TYPE Witness'
l.5157 - INFO ONLY: Loaded uncategorised data (GEDCOM extension): '1 _UID 8DC0D09CDB7FD611A4030010B50D77816BF9'
Record Type=Individual. Gedcom Id=I349. Record Number=69.
l.5204 - INFO ONLY: Loaded uncategorised data (GEDCOM extension): '1 _UID 90C0D09CDB7FD611A4030010B50D77816E29'
Record Type=Individual. Gedcom Id=I350. Record Number=70.
l.5259 - INFO ONLY: Detected & fixed field format error (data moved to Note Field): '2 TYPE Will'
l.5303 - INFO ONLY: Loaded uncategorised data (GEDCOM extension): '1 _UID 92C0D09CDB7FD611A4030010B50D77817049'
Record Type=Individual. Gedcom Id=I351. Record Number=71.
l.5338 - INFO ONLY: Detected & fixed field format error (data moved to Note Field): '2 TYPE Will'
l.5382 - INFO ONLY: Loaded uncategorised data (GEDCOM extension): '1 _UID 94C0D09CDB7FD611A4030010B50D77817269'
Record Type=Individual. Gedcom Id=I572. Record Number=233.
l.11893 - INFO ONLY: Detected & fixed field format error (data moved to Note Field): '2 TYPE Death'
l.11896 - INFO ONLY: Detected & fixed field format error (data moved to Note Field): '2 TYPE Death'
l.11899 - INFO ONLY: Detected & fixed field format error (data moved to Note Field): '2 TYPE Birth'
l.11903 - INFO ONLY: Detected & fixed field format error (data moved to Note Field): '2 TYPE Birth'
Record Type=Family. Gedcom Id=F21. Record Number=10.
l.15369 - INFO ONLY: Loaded uncategorised data (GEDCOM extension): '1 _UID 3931B0A76A7BD611A3F40010B50D7781EE3E'
Record Type=Family. Gedcom Id=F99. Record Number=21.
l.15534 - INFO ONLY: Loaded uncategorised data (GEDCOM extension): '1 _UID 9E64175BE47AD611A3F10010B50D778117E9'
l.15535 - INFO ONLY: Loaded uncategorised data (GEDCOM extension): '1 _UID 3F3DD9FB9C7BDB4D89E6D1B14DE40FF1B1D8'
Record Type=Family. Gedcom Id=F109. Record Number=25.
l.15580 - INFO ONLY: Loaded uncategorised data (GEDCOM extension): '1 _UID 7CC0D09CDB7FD611A4030010B50D77815AE9'
Record Type=Family. Gedcom Id=F110. Record Number=26.
l.15610 - INFO ONLY: Loaded uncategorised data (GEDCOM extension): '1 _UID 8EC0D09CDB7FD611A4030010B50D77816C09'
---------------------------------------------------------
The numeric portion of Gedcom Ids have been retained as Record Ids. Use these to match entries to records.
ID:6048
* V5 Exception Report
-
GladToBeGrey
- Famous
- Posts: 115
- Joined: 26 Oct 2004 09:16
- Family Historian: V7
- Location: Dorset, UK
-
rfj1001
- Superstar
- Posts: 291
- Joined: 14 Dec 2003 18:11
- Family Historian: V7
- Location: Dorset, England
- Contact:
V5 Exception Report
Also happened to me.
I just took a backup of my files (just in case) and then used a text editor (which showed line numbers to make things easier - such as Notepad++) to delete the problem lines in the gedcom file. Issue for me was completely resolved with no adverse effects to data.
(That being said I think you only get the messages when you run FH5 for the first time - or you rerun the reports. So I think you can actually ignore them)
HTH
I just took a backup of my files (just in case) and then used a text editor (which showed line numbers to make things easier - such as Notepad++) to delete the problem lines in the gedcom file. Issue for me was completely resolved with no adverse effects to data.
(That being said I think you only get the messages when you run FH5 for the first time - or you rerun the reports. So I think you can actually ignore them)
HTH
-
ikas
- Platinum
- Posts: 32
- Joined: 02 Sep 2011 14:37
- Family Historian: V7
- Location: West Coast of Scotland
V5 Exception Report
Hi,
I also got a similar report. Validated the GEDCOM as recommended and got a 'No Errors Found' message presumably because all the 'issues' were labelled INFO ONLY.
Problem is I get the exception report message pop-up every time I run FH. Is there any way to stop the message appearing?
I have checked all the FH program folders I know of and cannot see the log file to delete it.
Thanks
ikas
I also got a similar report. Validated the GEDCOM as recommended and got a 'No Errors Found' message presumably because all the 'issues' were labelled INFO ONLY.
Problem is I get the exception report message pop-up every time I run FH. Is there any way to stop the message appearing?
I have checked all the FH program folders I know of and cannot see the log file to delete it.
Thanks
ikas
-
Jane
- Site Admin
- Posts: 8518
- Joined: 01 Nov 2002 15:00
- Family Historian: V7
- Location: Somerset, England
- Contact:
V5 Exception Report
Ok
1. When you install a new version, it does the same checks for previous FH versions as it does for other imported gedcoms.
2. Info only means the data is retained (as UDFs), so you can fix it later.
3. If you want to fix it with V5, in the Plug store is a plug in which will find all the UDFs and report them in a result window so you can delete or move the data to new fields.
Once you save your file it will be flagged as V5 and stop popping up the messages.
1. When you install a new version, it does the same checks for previous FH versions as it does for other imported gedcoms.
2. Info only means the data is retained (as UDFs), so you can fix it later.
3. If you want to fix it with V5, in the Plug store is a plug in which will find all the UDFs and report them in a result window so you can delete or move the data to new fields.
Once you save your file it will be flagged as V5 and stop popping up the messages.
-
ikas
- Platinum
- Posts: 32
- Joined: 02 Sep 2011 14:37
- Family Historian: V7
- Location: West Coast of Scotland
V5 Exception Report
Thanks Jane. A save did it.
ikas
ikas
-
tatewise
- Megastar
- Posts: 28434
- Joined: 25 May 2010 11:00
- Family Historian: V7
- Location: Torbay, Devon, UK
- Contact:
V5 Exception Report
But remember, the Save does NOT fix the Unrecognised Data Fields (UDF), it simply suppresses the Reports.
Use the Plugin as Jane advises and review your data.
You will also find the UDF by opening the All tab in appropriate Property Boxes or expanding Records in the Record Window.
The UDF are indicated by a star-burst bullet.
Use the Plugin as Jane advises and review your data.
You will also find the UDF by opening the All tab in appropriate Property Boxes or expanding Records in the Record Window.
The UDF are indicated by a star-burst bullet.
-
GladToBeGrey
- Famous
- Posts: 115
- Joined: 26 Oct 2004 09:16
- Family Historian: V7
- Location: Dorset, UK
V5 Exception Report
Rob, Jane, Mike, thank for your help. In case it provides a modicum of help for others, the errors in my project (as reported above) were of two types:
It might help diagnosis a little more if the exception report included (say once for each exception type, as a footnote) a brief explanation of why the exception had been raised, as well as the existing info about what had been done to correct it.
- An error in the TYPE field of an ASSO record ('Associated Person' relationship). Looks like an earlier version of FH erroneously allowed the TYPE field to be set manually, which I had done, whereas V5 is now enforcing the correct values, and setting it automatically (and correctly, judging from my brief test this morning) when a new Association is made. The old, invalid value is saved in a local Note field jut in case. In my case these can be deleted manually, quite safely.
- _UID 'identifier' fields inherited, one per individual's gecom downloaded from (I think) familysearch.org (the LDS website) in the dim and distant past and merged into my main gedcom. Rightly or wrongly I have simply deleted these as the incorporated material is otherwise well sourced, and I don't see that they add much value.
It might help diagnosis a little more if the exception report included (say once for each exception type, as a footnote) a brief explanation of why the exception had been raised, as well as the existing info about what had been done to correct it.