Lately I've had issues with HTML5 target outputs that contain *.flglo glossary files. The build fails with a Compile Status of Build failed: Sequence contains no elements.
The issue first occurred a few months ago and it seemed to fix itself. Now it's back again and can be replicated. I'd appreciate anyone's thoughts as to what is causing this and how I can fix it.
Background
- Each author in our team is responsible for their own products. All of the products are related and share common terms.
- We keep our glossary of terms in a master project that is imported into all of our product projects.
- Each letter of the alphabet corresponds to a separate *.fltoc file and a separate *.flglo file. For example, Glossary_A.fltoc and Glossary_A.flglo.
- Not every term is used in every product. We use conditional tags for each product name. The glossary project terms are marked-up with the appropriate product name conditional tags in each of the *.htm, *.fltoc, and *.flglo files.
- Everything has been working well for the past couple of years.
During the compilation, the build fails with a Compile Status of Build failed: Sequence contains no elements.
Troubleshooting
- I searched the forums and knowledge base but found no similar issue.
- When this issue occurred in Project ABC, the only change the author made to the project was to select all of the *.flglo file check boxes on the Glossary tab of the target. We cleared all of the check boxes, except for the Glossary_A.flglo file, and then rebuilt the target. The build was successful.
- We then added the Glossary_B.flglo file and rebuilt the target. The build was successful.
- This process continued until the build failed, which happened when we added the Glossary_I.flglo file.
- Project DEF, which uses the same files as Project ABC, builds correctly with all *.flglo files, including Glossary_I.flglo.
- I compared the target files from both projects and didn't see any major differences apart from the names of the projects.
The author has had to build the targets without the Glossary_I.flglo file. This means the glossary terms in that HTML5 Help file do not appear in the Glossary tab of the Tripane skin we use. However, because the source *.htm files are included in the build, the terms appear in the main Search field.
I'd like to resolve this if possible but have run out of ideas. Before logging a ticket with MadCap, I thought I'd ask for your help.
Thanks in advance.