PB – Warnings & Errors

Wiki: TOC, VTOC, Home
Forum: Home, Gen, L4, Mac4

See also
 Personal Books

With Logos4 version 4.5 and higher, Logos4 reports warnings and errors when building your PB. This wiki page contains some documented warning/errors that you might encounter and in some cases ways to fix or avoid these when you are building a PB (Personal Book).

Page Contents

Where do I find the Warning/Error log?

When you build your PB and immediately after it is finished you will see the results as shown below:

  1. You will see the Finished button. Don’t click on it yet!
  2. Above the Finished button you will see how many Warnings or Errors that Logos4 found when building your PB.
    [In many cases your PB will show correctly. And if it does and you don’t want to investigate these warning/errors, then you may ignore these warnings/errors.]
  3. To view the Warnings / Errors, you can click on this link View log file.... The list should appear in a window (depending on which Operating System that you are using).

Note: If you’ve already clicked Finished but you remember there were some warnings and want to see the log file, you can either rebuild the book, or you can find the PBB log files in your ...\Logos Log Files\PBB Logs folder. The filenames correspond to the resource ID assigned by the PB builder, which you can find in the info panel of your Personal Book, next to “Support Info”.


Warning caused by Tables

  • You may see the warning below in your warning log:
    [Warning] Failed to interpret width value: 0pt

    This is caused when you haven’t set the Table’s Properties to a fixed size.

This can happen often when using Word’s default method(s) for building your table. I’ve discovered L4 wants the Preferred width set for your tables. When it is not set, L4 issues the above warning for each row in your table. Below are ways to check & correct your tables in Word.

  1. Hover your mouse over your table in Word until you see this symbol, then right-click on this symbol. Word will show you a drop-down menu as shown in the above image.
  2. In the drop-down menu click on Table Properties...
  3. Word will then open the Table Properties window as shown below.

    1. If this box is not checked, then this caused your warning. To avoid the warning check this box, then ...
    2. Enter a width value (you can enter the width between your margins [e.g. 7”]).
    3. Clicking the OK, will close and apply your changes.
    4. Now save your Word document.
    5. Then rebuild your PB in Logos4. The warning should be gone.

Picture ratio is rejected by L4 with a warning

  • When you have adjusted a picture’s size in your Word doc and the ratio of Height to Width exceeds 100%, you will get the warning below:
    [Warning] Bad aspect ratio for specified height/width on image tmp5AB2.tmp
    Note: you may see the Size percentage equal to 100%, but in reality Word has it set to 100.0001%. Its best to change the image’s percentage to slightly below 100%.

Locate your picture in your Word doc and follow the directions below;

  1. In Word locate your image, then right-click on it, in the drop-down menu click on Size and Position.
  2. Word opens the Size & Position window. Click on the Size tab if it is not the tab showing.
  3. Check the Scale percentages, one of them should be above 100%.
    1. Change either the height or the width until both percentages are below 100%.
    2. Click the OK to save your changes.
  • If the warning persists, then the method below almost always works:
  1. Rigth-click on the picture in Word and click on Copy.
  2. Open Paint or your favorite image editor.
  3. Paste your image from the clipboard as a new image into your image editor.
    (if the image needs to be smaller to fit into Word, then resize it here in the image editor)
  4. Copy the whole image in the image editor to the clipboard.
  5. Now go back to Word and delete the image, then paste the image from the clipboard into the same location in Word.
    (this basically forces a new copy of the image to be pasted into Word with the size of 100%. Don’t try resizing again in Word!)

Unknown Datatype

  • You will get this warning when a reference in your PB is linked to a book which you do not own in your Library. So this is not a warning that should concern you. It is usually found within a hyperlink in your PB, and if you click on that link you will just get a warning window that you do not own the resource.
    [Warning] Unknown data type in use: topic+topics

Invalid font name

  • The warning looks like this:
    [Warning] Font ‘TimesNewRoman’ is specified but not installed or embedded. Is this a valid font name?

    It might be followed by a warning looking somewhat like this:
    [Warning] Setting font for ‘TimesNewRoman’ to ‘Times New Roman’

    This can happen if a font used in the Word document is one that you don’t actually have installed on your system.

You can fix this in Word using the Find and Replace dialog to replace the incorrect font with one that you do have installed. Chances are it was only a typo, but you might need to find a font that looks similar to the one that was intended, if you can’t find the actual font somewhere to download.

  1. Click the More>> button to expand the dialog
  2. Click in the “Find what” box to bring the focus there, and delete whatever text might be there.
  3. Choose Format > Font...
  4. Enter the name of the font to be replaced. It will not match any in the list, and that is fine. Click OK.
  5. Repeat steps 3 and 4 for the “Replace with” box. When you’re done it will look like this, and you can click Replace All.

Note: If, after replacing any errant font names and rebuilding the book you still get an error, don’t worry about it. It might be just a leftover instruction about font mapping which will be ignored by Logos. For example, I had this remaining error: [Warning] Font ‘*TimesNewRoman’ is specified but not installed or embedded. Is this a valid font name? I couldn’t find any text with font name *TimesNewRoman in my document. I was able to eradicate the warning by saving the file as RTF, manually editing the RTF text to remove the lines mentioning *TimesNewRoman (being careful that what I deleted was within matched brackets), then save it back as .docx. But this is dangerous and not necessary, so don’t worry about it.

Font size too small or large

  • You will get this warning if a font size is extremely small or large, and Logos will assign a normal font size to that text. You might want to go back through the document searching for that font size and change it to something of your choice that is within a valid range of sizes (6 points to 149 points). To change font size, see the instructions above about changing fonts.

TOC entry too long

  • This warning happens when one of the Heading level paragraphs in the document is longer than 256 characters. Find the culprit and shorten it if you can, or if that’s just the way it has to be, live with the warning. It’s pretty harmless. The heading in question will still have the full text, but the TOC pane will only show the first 256 characters of it.

Duplicate page milestone

  • The warning looks like this:
    [Warning] Consecutive duplicate Milestone Start for data-type page: page.9

    The solution is to find the page milestone in question (in Word, for this example, I’d search for page:9) and fix it. It might require renumbering all your pages if you accidentally duplicated one. Or maybe it was simply a typo.

Unrecognized character

  • The warning looks somewhat like this:
    [Warning] Bad character in string: 0xFFFD

    It is caused by some unprintable character in the document which will probably show up like something bogus, for example:

It is hard to track down where the offending character is, because Word cannot search for unprintable characters. You can scroll through the document looking for anything unusual. But if you can’t find it, then narrow down your search by doing what is known as a “binary search”: Put in some intentional known problem causing a warning (such as an empty Heading paragraph), about halfway through the document. Rebuild the book and look at the log file to see whether the “bad character in string” error is before or after where you put in the known problem. Keep moving your known problem to the halfway mark of the section of the document you’ve narrowed down the character error to, and you’ll eventually find the problem, in the fewest possible steps.

The fix is to delete or replace the bad character with what was intended.

Temp Picture file is duplicated

  • The warning looks somewhat like this:
    [Warning] Media Metadata already exists for image tmp6c72.tmp

This is caused sometimes when you paste a picture into Word repeatedly.

The fix is to save the picture as a file and then in Word use the Insert to add your picture. Once you’ve added your picture, you can copy it in Word and paste it multiple times in other places.

Blank heading converted to Normal style

  • The warning looks somewhat like this:
    [Warning] Article ‘A_UNKNOWN’ has only 1 characters.

This is caused when we have our cursor on a Heading styled line in Word and we press Enter on the keyboard to insert a line above our Heading. We probably found that we have a blank heading and converted it’s style to Normal. But something in the XML Logos4 compiler doesn’t like.

Here are the steps which can cause this error:

  1. We place the cursor on a Heading line and press the Enter key to insert a blank line above,
  2. We notice that we have a blank Heading now.

  3. So we place our cursor on the blank heading line and change its style to Normal
    So we think we have fixed the problem.
    Then we build our PB.

  4. After building the PB, we see we have a Warning.
    Logos4 compiler has some problem with the XML and doesn’t properly recognize that we converted this line style to Normal.

How to resolve the problem
There are two ways

  1. Delete the blank line
  2. Place the cursor on the blank line and press Enter one more time. This inserts another Normal line above our forced blank line.
    1. Don’t worry about the new blank line (as long as it has no characters in it). Logos4 compiler remove extra blank line most of the time.

closing field heading that is already closed

  • The warning looks like this:
    [Warning] closing field heading that is already closed.

This is caused when adding Field tagging around text which you have already marked as a Heading in Word.

To fix this
Just don’t add these field taggings around text in Word in which you have marked with a Heading style.


Blank Heading

  • When adding Headings in your Word doc to create a Table of Contents (TOC) entry in your PB, it is easy to try and add a blank line under or above a heading by placing your cursor on the heading and pressing Enter. The problem is that Word sets your blank line to Style Heading. When you compile your PB in Logos it will not complete the build and the log will show you errors like this:
    [Error] Unable to apply topics to article ‘A_UNKNOWN_3’. Article Length is zero.
    [Error] Article ‘A_UNKNOWN_3’ has only 0 characters.

The handling of this has been changed by Faithlife over the years: What used to be a warning and could nearly always be ignored without any consequences has changed to an error that breaks the build of the PB. This has hit many users when rebuilding a PB that worked in the past.

You can find this pretty easily in Word by opening the Navigation side panel as shown below. The Navigation side panel shows you all your lines marked with Heading Styles. It is very similar to what you see in your PB when you open the PB’s Table of Contents.

  1. This is what the Navigation side panel looks like in Word 2010 and hasn’t changed much in later editions. To open the Navigation panel on Windows, press CTRL+F and click Navigation on the side panel. On Mac, open the View menu, point to the Sidebar, then click Navigation.
  2. If you expand all your headings in the Navigation panel, you can visually scan down them looking for and empty heading (as you see in this image). If you click on this heading, Word will move you to where it exist in your doc.
    1. Notice this blank line. I accidentally created it when the cursor was on the heading under it and I pressed Enter to add the blank line.
    2. To remove the blank heading you can either delete the blank line (it should also disappear in the Nav panel). Or you can click on the blank line and change it’s Style to Normal.
  3. For additional help or if these instructions seem a bit complicated, this video guide created by one of our users may be more helpful: https://youtu.be/mORoCiGam6g
  • Especially in long PBs with many of those errors, a quick fix may be to add a space character into every paragraph. You replace all “^p” (i.e. paragraph marks) with ” ^p” (space paragraph mark).
  • This error may also occur when the empty article is not a paragraph, but a section in Word

Logos Bible Software Wiki

Welcome, Guest! (sign in)