Unable to create Meeting Notes in Confluence 7.12.3

[Glenn Edwards]

When attempting to create meeting notes in a space (Confluence 7.12.3) the creation the application just spins, after selecting to close the window the meeting notes button disappears until the page is refreshed. There isn't an error generated on the front end, but in the atlassian-confluence.log there is an error stating (the id does vary from error entry to entry):

WARN [https-jsse-nio2-8443-exec9][plugins.createcontent.impl.DefaultPromotedBlueprintService] matchIdWithBlueprint blueprint not found with id : 17b4226f-a636-469e-8a8b-cc83bed17a14

I've checked the system plugin for the Business Blueprints and everything is enabled including the sharing, I have even reinstalled Confluence but the problem persists. Any idea about may be going on here would be greatly appreciated. Thanks.

[Brant Schroeder]

@Glenn Edwards 

I believe this will help you https://confluence.atlassian.com/confkb/unable-to-create-a-page-using-confluence-s-blueprint-due-to-no-pagetemplate-found-for-contenttemplateref-963654886.html

[Glenn Edwards]

@Brant Schroeder Thank you, unfortunately after working through the steps present in the link that you provided it seems that this not quite the issue. After reviewing the applicable tables in the database, the Meeting notes template appears to be correct (at least in those parts of the database).

[Brant Schroeder]

Are you seeing any errors or information in your logs that correlates to the time you try creating the new meeting notes?

Also, is this happening in all spaces?

[Glenn Edwards]

@Brant Schroeder Thanks for the idea to check on the other spaces, I was able to successfully create meeting notes on another page. I double checked with the page that was having the issue and although the Create meeting note (blue) button appears to be the source of the issues/errors. When using the menu or grey Create meeting note button to create a meeting note the issue is not experienced.

[Brant Schroeder]

@Glenn Edwards 

Sounds like the macro button that provides that functionality on the page might be the issue.  Have you tried adding it again to the page to see if this fixes the issue?