On This Page


The Utilities > Logs menu includes commands related to log files written by GedSite as it operates:

  • The Open GEDCOM Log command opens the GEDCOM log file in the default text file editor.
  • The Open Application Log command opens the Application log file in the default text file editor.
  • The Open Publish Log command opens the Publish log file in the default text file editor.


GedSite writes GEDCOM log file entries when it loads a GEDCOM file. The log file entries include INFOrmational, WARNing, and ERROR messages about the GEDCOM file.

  • Example INFO Message

    INFO - Reading GEDCOM file 'C:\GEDCOM\smith-family.ged'

  • Example WARN Message

    WARN - Line 66: Line length (293) exceeds GEDCOM maximum but will process

  • Example ERROR Message

    ERROR - Line 85: Unrecognized text 'UNKNOWN' parsing date 'UNKNOWN'

You should review the GEDCOM log to see if there are any serious errors. Most GEDCOM files will trigger some error messages, but you may choose to ignore some (or all) of them. For example, many people put text in date fields, and that leads to invalid GEDCOM DATE tags. GedSite will write an error message (see example above), but the error may be ignored because GedSite will load the text as a date phrase, and that will yield the expected output. If you use the GEDCOM file for other purposes, you may want to change the data in your genealogy program to avoid the error.

Application Log File

GedSite writes Application log file entries as it operates. The log file is recreated when the application starts. The log file entries include INFOrmational, WARNing, and ERROR messages.

Application Log entries include a time stamp and the name of the component within GedSite that generated the message. The component name will not mean much to end users, but may provide a useful clue about issues that arise when using the program, and is vital to debugging efforts by support staff.

  • Example INFO Message

    INFO GedSite.FormMain - Opening GedSite file "C:\Users\jfc\Documents\GedSite\site.gsfile"

  • Example WARN Message

    WARN GedSite.GedTagTypes - No sentence for tag 'Marriage', role 'Usher'

  • Example ERROR Message

    ERROR GedSite.MessageWindow - Making site: File not found attempting to copy 'C:\Users\jfc\Documents\GedSite\site-i\if\mary.jpg'

Publish Log File

GedSite writes the Publish log while uploading content as a result of the Family History Hosting > Publish command. The log file includes two main sections:

  1. Client Log – progress and status messages written by the GedSite Publish software and intended to capture the logical steps in the Publish process
  2. Session Log – FTP communication messages written by the FTP component.

Users unfamiliar with the technical details of the FTP protocol will find it difficult to follow the entries in the Publish log. The log is mostly intended for use by Family History Hosting support staff if customers encounter an issue.