Sorry, I know these steps aren't very clear. I'll try to make it a bit less confusing:
 

1. Start with a blank Sonar project.
2. In Sonar, go to Edit > Preferences > MIDI > Devices. Ensure only one MIDI input device is checked, the one that will be used to record MIDI from an external MIDI keyboard.
3. Drag n Drop an instance of Kontakt using the following options ([ ]=unchecked, [x]=checked):
   • [ ] Simple MIDI track
   • [x] MIDI Source
   • [x] First Synth Audio Output
   • [x] Enable MIDI Output
   • Leave other options at their defaults
4. In Kontakt, load any instrument.
5. In Kontakt, go to Options > Engine. Under the "Send MIDI to outside world" dropdown, make sure that "GUI keyboard" is checked.
6. Go back to Sonar and Drag n Drop any synth, like SI-String Section or similar using the following options:
   • [ ] Simple MIDI track
     
   • [x] MIDI Source
     
   • [x] First Synth Audio Output
   • [ ] Enable MIDI Output
   • Leave other options at their defaults
7. On the SI-String MIDI track, change the input to [your MIDI keyboard] Omni.
8. Put the SI-String MIDI track in record mode, start recording.
9. Play some notes on the onscreen Kontakt keyboard.
10. Play some notes from the external MIDI keyboard.
11. Stop recording.
12. Notice that the SI-String MIDI track has recorded events from both the onscreen Kontakt keyboard as well as from the external MIDI keyboard. This is unexpected behavior since we should only see events from the external keyboard.
13. On the SI-String MIDI track, change the input to None, and then back again to [your MIDI keyboard] Omni.
14. Delete the previously recorded clip on the SI-String MIDI track.
15. Repeat steps 8 to 11 (record again from both the onscreen Kontakt keyboard and the external keyboard).
16. Notice this time that there are no longer Kontakt MIDI events recorded on the SI-String MIDI track, but only those from the external MIDI keyboard. This is the expected behavior.

Perfect. I can 100% reproduce this thanks :)
 
Would it be copy and paste these latest steps into the reporter (also give them a link to this thread):
http://www.cakewalk.com/support/contact/problemreport.aspx
 
And give us the number?
 
Much appreciated...
 

Steven,
 
Thanks for the additional report and steps.  We'll look into it.

Can someboduly give me the issue number?Thats all I ask for. I want to keep a record as well. Thanks

CakeAlexS
Can someboduly give me the issue number?Thats all I ask for. I want to keep a record as well. Thanks

Alex, I want to write up the problem report but unfortunately I would only be able to get to that by tomorrow morning. At that point I can give you the number.

Thanks appreciate it.
Sorry it's happened before where we do all the work, Cake comes in, follows it up (which is nice) but doesn't give us a reference, which also means we also can't track its status (no dinner for you!! ). I really wish the whole tracking thing was a lot more transparent.
 
It's the same with duplicate issues, they merely close the issue as duplicate  but never tell us the issue number of the duplicate, and again we lose the ability to track. Dead end.
 
Anyway that's my moaning out the way for 2014...
 
Cheers...

Hi guys, here's my report on the issue so far...
 

1. as mentioned, if i use Kontakt as the primary instrument, i will not have any issues with sending Midi out to another independent Midi track. This is regardless of where the track is set to Midi OMNI or Midi Track No. if its at None, it will not work - this is good!!!
2. now i tried following the steps @SilkTone laid out. As i do not have SI Strings, i did what i could with the Default Kontakt Instrument. I am not able to produce a similar result.
   • I can record to the new midi track via external keyboard only. The on screen Kontakt Keyboard events are not recorded.
   • There something curious however, if memory serves, there is a setting within Kontakt about sending Midi information out. This is under the Options page. i can vaguely remember there are 4 settings to be had. (Apologies as i cannot be specific now as i'm not at my desk)
3. Finally @SkilTone, the suggestion to cycle through the Midi Channels of the Midi Track Input Channel has not worked for me. 

 
many thanks all... cheers!!!
 

keyzs
 

• There something curious however, if memory serves, there is a setting within Kontakt about sending Midi information out. This is under the Options page. i can vaguely remember there are 4 settings to be had. (Apologies as i cannot be specific now as i'm not at my desk)

 

Yes this is critical to reproducing the issue. See step #5 in comment #11. The bug is related to the events being sent out from the VSTi back into Sonar, and how they are then routed to other MIDI tracks.
 
I will write up the problem report within the next hour or so and post the CWBRN #.

OK, written up the problem report as CWBRN-23123.

Awesome... Thanks..