OK, first of all, I'm NOT accusing Sonar of ANYTHING, so no need to have anyone's guard up.  I'm just trying to figure out where my problem could possibly be coming from.  BTW, I have my system specs in my signature if you're interested.
 
My external keyboard keeps getting msgs from somewhere to boost the MIDI volume only on 2 different channels way out of range of what I specified in Sonar.  I use a Sonar template for each project so I know everything is just the way I need it for each project. I also know that there are NO Volume Controller 7 events on ANY channel/track in Sonar. The ONLY NON-Note events are Patch Changes. I've got a support msg into Alesis for whatever their responsible for, and honestly, it very well may be their problem, but I want to get ALL the data so I can make a truly intelligent diagnosis.  So, I just want everyone to offer whatever info they can on whatever parameters I should check that I haven't offered here that could be causing this issue, cuz I'm pulling my hair out.  If you need anymore info, let me know. Just in general.

I found that some synths and some instruments within multi-timbral synths (Kontakt), are natively set to react to fader changes on their Master Volume parameters, and I generally go in and alter that default to sever that connection.
 
I see it in quite a few of their synths and instruments. and it is pretty annoying.  I have had other synths inexplicably have pitch tied to mod wheel, and the Sonar default to zero all continuous controllers would jazz that up unless I altered that default behavior for that synth.
 
I offer the above to just illustrate that there may be some sneaky ways things can happen that do not involve recorded midi events.
 
Bob Bone
 

King Conga
My external keyboard keeps getting msgs from somewhere to boost the MIDI volume only on 2 different channels way out of range of what I specified in Sonar.

The volume values are way out range, or the channel numbers are not being used?
 
If the channels are being used in the project, check that the MIDI Volume controls are disabled (parens around the value). If not, right-click the widget, and and choose Disable Control". Just moving a control will enable it, and SONAR will send that value to the synth as a starting value every time you start playback.
 
 

OK! I just now Disabled the Volume in the most problematic track, and before I checked back here I had added a Controller 7 msg to 2 keyboard tracks that are supposed to be at the same volume.  One of them worked as it should, but the one that's been problematic worked a few times on playback.  However, after that it started doing the following:
I had set the Controller 7 value at 55 for both tracks.  The UNproblematic one worked fine, and still is.  The problematic one started jacking the volume on the keyboard up to 80 BEFORE it even got to the point where I had set the Controller 7 event (measure 11). Then, as soon as it would get to measure 11 it would tick down to 79 on the keyboard.  So, it's OBVIOUSLY responding to Sonar, but still has a mind of it's own.  If I could just get to the place where I could mix it down to audio I would, but I've got to get another whole section done before that.
 
I'm going to send this post to the Sr. Alesis Tech Support guy that might regret reaching out to me before it's all over with.
 
Thanks Guys,
KC
 

It's possible you have a data slider/knob on your keyboard that is jittering and sending spurious messages that are overriding what's coming from SONAR. The Mod wheel on my Alesis QS8 developed this problem, and I had to put a flatline Modulation envelope in the track to keep it steady.

You can try to get from http://www.tencrazy.com/gadgets/mfx/ 2 plug-ins: PortDiag and TrackDiag.
Insert both on MIDI track in question. One display if something going into track (from MIDI input), other display what is the output from that MIDI track. At least that should show what SONAR sends.
 
For example, controller 7 events are also sent by Track Volume Automation.
 
Excuse me if I look in wrong direction, noob here

Thanks MUCHO guys.  Will check these out.
 
So, Azlow, when you say "Insert" it into the said MIDI track, are you saying insert it as a MIDI FX insert?  Please advise.
Thanks,
KC

Yes, these plug-ins are MIDI FX.
 
Do not be confused that events are shown in a kind of "reversed" order (first events are at the end of the text). But I guess you are just interested either you see some CC at all and either they come from the input or somehow generated at track level.

OK! Azslow3, I installed those plugins and here are the results.  The Port Analyzer didn't show any data.  However, the only data the Track Analyzer showed was at Bar 1, and they were Cntrlr 64, and the Program Change that is the same ones set in Track View, and finally, the expected Note Events.  All of which were also found in the Event View. 
 
Here's the odd thang.  The Volume jump happens not only at the beginning, but also at bar 11, even after I turn it back after the initial jump.  When I substituted the Cakewalk TTS synth there was no volume jump.
 
I'm fwding these findings to Alesis, but please let me know your opinions.
 
Thanks,
KC

Hi King Conga...
 
Also check to make sure you have not accidentally/inadvertently sent a
volume controller to your keyboard via system exclusive msg 
along with your patch changes..
 
You can use Splat's midi filter prefs to check this.
 
Hope this helps,
 
Mel