Hello, I am trying to build my project but I keep getting an "object reference not set to an instance of an object" error. I have researched other threads addressing this error message but none of the solutions have worked for me. The build is goes well right up until it is generating the final TOC as seen in my build log below. I have tried the build in both Flare V9 and V11. Is there something wrong with my TOC? Any ideas?
Processing topic: Welcome.htm...
Generated Welcome.htm
Generating output skins...
Generating synonyms file...
Generating alias file...
Processing audio links...
Generating final TOC...
Build failed: Object reference not set to an instance of an object.
Publish skipped: Target not built.
I don't have an answer ( ), but we have the same problem. All of a sudden we can no longer successfully build our HTML5 Tripane output. This happens in one project only, but it is reproducible on different machines. The build fails with error ID 10086 (Build failed: Object reference not set to an instance of an object.). The last step before the failure is applying master page to a topic. We have tried eliminating topics from the TOC, to no avail. We have tried applying different master pages, to no avail. Only when we leave the master page as (default) does the build progress. Any ideas would be SO appreciated!
Ordinary (but as you are finding out, not necessarily always) the file listed in the build log directly before the error is the offending file.
Try the following procedure, often suggested by MadCap Tech Support as a "catch all fix" for various issues.
> Close Flare.
> Browse to the folder with your Flare project using Windows Explorer
> Delete the Analyzer and Output folder(or move the Output folder to a different location if you do not want to lose any previously built outputs)
> Browse into your Project folder and delete the "Users" folder inside
> Then, navigate to C:\Users\[Your User]\Appdata\Roaming\MadCap Software\Flare
> Select and delete the CatapultMDIEditor folder
Thanks for your response, roboHAL! We ended up rolling back the project. We couldn't get it to work any other way. We suspect that the mess happened because of changes made outside of Flare, but we can't be sure. Hopefully we won't run into any other issues going forward.