MadCap Software Forums

Since I've updated to Flare 2017 every time I open multiple instances of Flare, an error occurs every time when I shut them down again.
As I use a lot of project merging, I often have to work with mutliple Flare instances.
Until now I haven't seen any negative side effects (e.g. loosing unsaved data, or problems when the Flare project is re-opened).
Nevertheless this behavior is annoying and the fact that I haven't seen side effects yet does not mean that in fact there are some that I haven't detected yet.

Is there anybody out there who experiences(d) the same and has a suggestion how to fix it?

dotNET framework?

Check you are running the latest version...

Thanks Steve, I have .NET Fw 4.7, last updated 11-27-2017. I think that is the latest version ...

The latest version is 4.7.1 and it broke some stuff for me. You may want to look if 4.7.1 is installed and remove it.

Ramon, we're using on 4.6.01590 and it works alright, albeit a bit laggy at times. Do you think upgrading .NET would fix that?

Still, there seems to be something to 4.7.1 that causes previously working applications to fail.

Right, "Microsoft Inside."

Thanks - I just opened a case with support (126440) as I'm experiencing the same issue. The error message happens pretty much every time I exit Flare, and then my cursor stops responding for several seconds. When I click OK to dismiss the error, it often shows up again... ARRGGHH

EDIT: Support got back to me quickly. I was instructed to delete the madcap registry keys and the madcap folder under appdata/roaming. So far, the problem appears to be resolved. But it's annoying to lose all my "recent projects" and last-viewed files in a project and UI preferences.... AND all my ftp logins for publishing.... UPDATE: I was informed that I can try restoring the madcap registry keys from backup to get my preferences and everything back and it might work if the keys were not corrupted. I am already reinstating my preferences and all manually so I did not attempt this. UPDATE AGAIN: Unfortunately, still experiencing this issue after closing down Flare for the day.... working in 3 different projects / problem didn't occur till I shut down Flare. ARRGGHHH

We also have a writer experiencing this issue - has a permanent solution been identified yet?

Is it a combination of rolling back .NET to 4.6.X and removing the MadCap Software appdata\roaming folder, or is there something else that has worked for you?