Error when compiling a personal book

Rev Mark Woodhouse

Hi All, can any one help. I have compiled 100s of personal books and all fine. However I am compiling one and I get the error below, I copied the book into a new word doc file tried again, I'm closed everything down and started it and tried again. Same error. any thoughts?

Thanks 

Mark

[Info] Starting build for PBB:912c44f07fdb4acba72e21dbce051087
[Info] Converting
[Info] Converting C:\Users\Mark\OneDrive\Library, Books & Magazines\Books Logos\The Apostles - Donald Guthrie.docx
[Info] Compiling
[Error] Article 'A_25BRIEFLETTERSFROMJOHN_B' has no content; articles cannot be empty.
[Warning] Failed to interpret width value: 0pt
[Warning] Failed to interpret width value: 0pt
[Warning] Failed to interpret width value: 0pt
[Warning] Failed to interpret width value: 0pt
[Warning] Failed to interpret width value: 0pt
/*  [Warning] appears many times */
[Warning] Failed to interpret width value: 0pt
[Error] The Compile Failed
[Error] Error while building book: Error compiling resource.
[Error] Exception: LDLS4.Panels.PersonalBookBuilderPanel.PersonalBookBuilderException: Error compiling resource.
at LDLS4.Panels.PersonalBookBuilderPanel.PersonalBookConverter.CompileResource(LicenseManager licenseManager, String manifest, ResourceDocumentData metadata, IPersonalBookBuildLog buildLog, TempFiles tempFiles, IWorkState workState)
at LDLS4.Panels.PersonalBookBuilderPanel.PersonalBookConverter.<CreatePersonalBookWork>d__2.MoveNext()
at Libronix.Utility.Threading.AsyncWorkerTask`1.EnumMoveNext()
at Libronix.Utility.Threading.AsyncWorkerTask`1.EnumMoveNextWithCatch()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Libronix.Utility.Threading.AsyncWorkItem.Verify()
at LDLS4.Panels.PersonalBookBuilderPanel.PersonalBookViewModel.<CreatePersonalBookWork>d__137.MoveNext()

Ken McGuire

The Warning statements are common when you compile PB's with MS Word Tables. I have seen it countless times - and yet it worked fine.

The Error statements are where the problem lies. The problem is the Error statements are a bit less than clear. If I were you, I would start testing the first half, and then the second half to try to narrow down where the error lies.