Interesting. The Kingston update also didn't have the "ReWire distortion on playback with Reason" that started with Lexington, although that bug has been fixed in SONAR 2016.04. Maybe it's too much to hope that fixing the ReWire bug also fixed this one...
 
Ron, I would recommend re-submitting a report, since the fact that it worked in Kingston but hasn't worked since Lexington is the kind of data that should make it a lot easier to track down the problem. I'm sure the Bakers will appreciate that level of diligence.

williamcopper
For the OP, however, try using "select all", first, to get all tracks involved, and then "select by time", and then cut special with 'delete hole' (not 'by whole measures' .. that's another bug)  -- then even the unselected clips will be moved as you want them.

But will this still work on the OP's project where a track didn't have data until after the hole to be deleted? I don't think so.

Yes, it works, at least as of Platinum Kingston.

Anderton
 
Ron, I would recommend re-submitting a report, since the fact that it worked in Kingston but hasn't worked since Lexington is the kind of data that should make it a lot easier to track down the problem. I'm sure the Bakers will appreciate that level of diligence.

 
As Craig suggested, I created and submitted the following Problem Report.

CWBRN-49873

Report Details

Product    SONAR Platinum
Version    22.3.0.71
Architecture  x64
Status      New
Summary  Delete Hole function does not work after Lexington Update
 
Repro Steps

1. Create new project
2. Insert 5 MIDI tracks
3. Record 4 bars of MIDI notes
4. Copy recorded Clip to tracks 2 -5. Move the clip on track 3 to Measure 5 and track 4 to Measure 6
5. Select all tracks
6. Drag timeline from Measure 1 to Measure 4
7. Execute Delete Special with the Events and Delete Hole check boxes checked

Expected Results
The first 3 Measures of midi data should be deleted from Tracks 1,2 and 5 with the remaining MIDI notes moving to bar 1. The clip on Track 3 should move 3 Measures to the left and start on Measure 2. The clip on Track 4 should move 3 Measures to the left and start on Measure 3. The expected results were confirmed in Sonar 8.5, Sonar X2a, Sonar X3e, and all Platinum versions up to "Kingston".
 
Actual Results
The first 3 Measures of midi data are deleted from Tracks 1,2 and 5 with the remaining MIDI notes moving to bar 1. The clip on Track 3 remains at Measure 5 and the clip on Track 4 remains at Measure 6. The Actual results were confirmed on all Platinum versions starting with Lexington through 2016.03. I am attaching a test project based on the Steps to Reproduce, an animated GIF from Platinum Kingston and an animated GIF from Platinum 2016.03.
 
OS  Windows 7 64-bit
Reproducibility   ReproducibleInAllProjects
Filed   4/24/2016
Last update  4/24/2016

Thank you!!

SquireBum
 
The second animation is Platinum 2016.03.  Notice that the clips on Tracks 3 and 4 do not move.

 
Thanks,
Ron

Just in case folks didn't catch this... note that the non-shifted tracks also deselect, which is the same bug/issue noted in this thread. If SONAR decides there is nothing to process, the user selection is altered.
 
I think the core of this bug is the deselection... and it seems to be done prior to the "delete hole" portion of the algorithm.

As written before, there must be something (both audio or midi) in every track at the beginning of what you want to delete.

lapasoa
As written before, there must be something (both audio or midi) in every track at the beginning of what you want to delete.

I think an automation node will also serve this purpose.

Got to be careful about that 'something' ... again, clips are likely to get involved here.    If the 'something' results in a clip extending from the beginning of the file into your selection region, yes, but if the 'something' results in a separate clip, not selected because the start time is beyond the end of that clip, then the OP remains. 

There is no reason why Sonar can't let you select some tracks and a region of time and then delete that region of time, moving all the tracks over.  For years their have been issues with deleting holes -- this forum is full of posts about various methods and processes to remove silences/delete holes.  It sounds like this specific problem didn't start until Lexington back in Nov 2015.  I wished we could get Cakewalk to understand how important it is to have these bread and butter project database operations work.