[SOLVED] All my LP EQ automation suddenly gone

When I open a project where an LP EQ envelope was shown in prior session, the envelope says "orphaned", but the LP EQ plugin is still there

I sympathize with you. I've had automation envelopes go missing in Sonar as well. I remember spending a recent evening trying to automate multiple controls of a synth by using automation recording. After recording, some of the controls I had moved didn't have automation envelopes recorded (even though I had seen the automation being recorded on screen as I was moving the controls), and controls that I hadn't touched *did* have envelopes appear (flat, of course). Then, after reloading the project, some of the envelopes that had recorded successfully had disappeared, whilst more evelopes for controls that I hadn't recorded had randomly appeared. And when I tried to delete one of those, another envelope that had recorded successfully disappeared with it. Automation in Sonar desperately needed an overhaul from the ground up, I find it to be extremely buggy.

Thanks to all the kind replies.
 
SOLVED IT (myself). Life is good again
To anyone who experience this:

1. uninstall LP EQ/LP MB, the standalone ones in Command Center (not Engineering FX Suite)
2. uninstall Engineering FX Suite
3. Reinstall Engineering FX Suite version 2016.07 (newer ones somehow won't install LP EQ / LP MB
4. Update Engineering FX Suite to newest

I guess it got messed up when I installed the standalone LP EQ / LP MB in november...
All my envelopes are now back. Woohooo!!!

Resonant Serpent
This is a known bug that was acknowledged by the Bakers, and I was hoping to see fixed. Obviously, that won't happen now. It's why I quit using Sonar as my main program a while back. I use a ton of automation in my work, and I simply couldn't use it with confidence. Between this bug, the broken areas of the piano roll, and the bugs in the Pro Channel, the program became unusable for me. 
 
In a way, watching this program die reminded me of all the people I grew up with who died early from various self-inflicted conditions. I always hoped they'd pull out of the dive in time, but they didn't, and there's nothing I can do about that.
 
The words from Pet Sematary come to mind : "Sometimes dead is better."
 
This isn't a comment on anyone still using the program. I'm just glad I don't have to worry about it anymore. Sonar was my fave for a couple of decades. 
 
http://forum.cakewalk.com...-project-m3524728.aspx

I was in exactly the same boat. Just way too many evenings spent pulling my hair out and too many musical performances (like recording synth parameter moves) disappearing into the ether after Sonar either didn't record them properly or decided to ditch them after I'd done them (perhaps it was trying to tell me something )
 
Because of work and other commitments I don't have a great deal of time to work on music, so the hours that I have free are precious to me. Which made it sting all the more when an evening I'd earmarked for musical fun turned into a problem shooting nightmare. Automation, controller data and MIDI were all a problem in Sonar. I also had huge problems with MIDI crosstalk, i.e. ending up in places it's not supposed to, and I suspect this was at the root of many weird problems. For instance, loading up a project and finding all of the Quadcurves with random cuts and boosts in the same places. Or having plugin settings hosed. When you do something like hit solo on a track and it triggers a kick drum in Battery, you know there's some serious leakage going on in the program. Sometimes I would load a project with Jamstix outputting MIDI to a drum synth, hit play, and a random synth elsewhere would start playing Jamstix's MIDI (despite being on a totally different channel and not having Jamstix as as MIDI input). 
 
Part of the problem is that many of these problems only begin to surface when you have big projects with a lot of MIDI and automation flying everywhere and one plugin being routed to another etc. People who use Sonar as a glorified tape machine (seemingly quite a large % of users) might not ever come across these problems, and so there was never any concerted pressure on the forums to get these issues fixed. It was usually one or two lone voices, and a lot of people saying "can't say I've ever come across this."