Copy link to clipboard
Copied
Hi,
An error says that I need to fix a cyclical loop before I can save the book as a pdf. Does anyone know what this might be. I've also noticed that everytime I try to update the book the program crashes.
Thanks,
Julianna
Thanks for your replies, Barb and Bob! After getting a good night's sleep, I took another look at the file and discovered that I had accidentally created a second book file within the document. It appeared right under the actual book title. I went ahead and deleted that extra book, and everything is back to normal now. I vaguely remember noticing it before but didn’t think much of it at the time. I suspect it happened when I was renaming the book. A typical, wacky situation that I get myself int
...Copy link to clipboard
Copied
Hi Julianna:
This came up once before that I can recall—https://community.adobe.com/t5/framemaker-discussions/creating-toc-problem/m-p/9074315. Looks like I tried to help but didn't—re-reading the thread, solving other issues in the Book error log resolved this odd message.
So let's start with the book: try opening the book file, then Shift + File > Open All Files in Book, followed by Shift + File > Save all Files in Book to make sure all chapters are updated to the currrent version. Then, with all files open, update the book. Does it update now? If there is a book error log, what does it show?
~Barb
Copy link to clipboard
Copied
At what point in what operation is that being reported?
And what is the actual error message?
In general, it is theoretically impossible for a computer program of any complexity to determine if a loop will ever complete (the "halting probem" in computer science).
FM usually dodges the whole issue by doing only one, or a finite few, passes through the document on any operation, such as open, update, save.
This means that it is possible to have non-terminating loops, such as reciprocal cross-references by $paratext, or self/reciprocal Text Insets. The document can grow without bound, and FM cannot detect it. In the 32-bit days, it would eventually crash at 2 or 4GB. But a bounds crash was the definitive symptom; FM couldn't pre-detect it. In FM2022, you probably have to fill VM or the file system to get such a crash.
Copy link to clipboard
Copied
Thanks for your replies, Barb and Bob! After getting a good night's sleep, I took another look at the file and discovered that I had accidentally created a second book file within the document. It appeared right under the actual book title. I went ahead and deleted that extra book, and everything is back to normal now. I vaguely remember noticing it before but didn’t think much of it at the time. I suspect it happened when I was renaming the book. A typical, wacky situation that I get myself into. Haha!
Copy link to clipboard
Copied
Glad you got past it!
~Barb