Thanks again man. I will give them a call tomorrow and see what the deal is. Im pretty sure my set is still under warranty if anything is wrong with it. 

Well often if there is not a proper driver supplied there will be issues like this. It's important when using a DAW to use good drivers. 
So myself before I buy anything I go to the web page and see what's available under downloads for the product. 
Any product that claims " no driver is needed" is off my list.  I will assume problems. 
 
But maybe your set will work, you say you had it working with LE. 
 
So things to check. 
 
Insert a new midi track. 
Select your E drums Omni as the input device
Select record for the track and make sure the input echo is highlighted. It should always be highlighted when the midi track is selected. 
play your drums and the track meter should be showing action. 
if not you have no or have lost your connection to the drums and that's your drivers, a bad usb cable or?   
if the track meter is showing then move to the next step. 
Insert SI drums And not point the output of the midi track to them. 
They should play regardless of the GUI being open or not.
Just make sure you still have "focus" of the midi track and input echo highlighted.
Now what the track meter and it should still show action and you should still hear the SI drums playing as your strike your drums.  
 
 

Thanks cactus. Tomorrow I am going to try a different computer. That was what i originally used when i had sonar X1.
If i have the same problem then im going to assume its my edrums. When i bought the set i didnt know there was no drivers included. I bought it so that i could practice without causing a ruckus for everyone else but now i planned on using it for recording. Hopefully its still under warranty. 

Just to be clear, There probably nothing broken about your kit. 
And also to be clear the driver I'm talking about is a MIDI driver which is not the same as an audio driver like WASAPI. But the audio drive does come into play when you trigger a drum VST. 
Yes you will have audio latency most systems , even with ASIO drivers which come with proper audio interfaces. 
It makes it hard with drums. I have enough latency with my set up that is bugs me when I play my drums using a VST drum source so what I do is direct monitor the Digital drum set brain which has no latency. I record the midi that way and then use a VST drum for playback in Sonar. 
 
But that's a different driver, the midi driver is what I'm talking about and that is needed for Sonar to receive the output from the drums via USB and translate into midi data. Without a driver supplied by the manufacturer, Windows will toss in some sort of generic driver,and when you say it worked on the other computer that may just tell us something. Possibly that computer used a better generic driver than your other one did,, just a long shot. 
If it is a problem another solution is I see your drum kit has real MIDI ports which you can also use into Sonar.What you would need is an audio interface with midi ports like the Tascam us 2x2. https://www.sweetwater.com/store/detail/US2X2
 You will want a proper audio interface anyhow, it makes working with Sonar much  much better. 

the delay is not your computer or the EDrum kit. its most likely your soundcard.
I hade the same problem using an E Kit with a MIDI/USB cable.
I was trying to help my buddy set up his kit without a soundcard. I thought I could at least get it close (his was a Roland TD 1). but the latency was still there no matter what I did with the buffer size.
 
You might have better results using ASIO4ALL but I never recommend that. more often than not it creates more problems than it solves. so use it at your own risk.

His issue is Sonar is disconnecting from his drums. He gets it to work when the focus is on SI drums only. 
There is no reason to asio4all anymore, we now have WASAPI. 
And most certainly as I said above, in the end you should rely have a proper audio interface if you want things to go smoothly. And for E drums if your going to monitor a VST drum you will need an interface that is capable of under 7ms of RTL... so an RME, Motu etc. The easy solution is don't monitor the VST, monitor the E drums when tracking. 

Thanks guys i appreciate the help. I will mess around some more tonight and see what happens. the price isnt too bad on that tascam either. I went to guitar center and was looking for a audio interface and the guy working there said they only had one available and it was almost $350 so thats why i skipped out on that. chuckebaby thanks for the videos. I was looking for something like that one youtube and couldnt find much so thank you. 
 
EDIT: Chuckebaby I have double checked my preferences and noticed in the playback and recording section it does not show my 
edrums in the "currently assigned port" box all i have is "Microsoft GS Wavetable Synth"
 
Sonar was automatically on WDM/KS so i will try the WASAPI and see if that helps. Im still new to this so thanks once again for the help guys.

Well I was able to change the "Currently Assigned Port" to my edrum. still the same result. As soon as i click out of the SI-Drums window and go to record it just cuts out. My edrums are still getting a signal on the module but nothing in Sonar. If i restart Sonar i get it back, Until i click out of that box again. Being i bought SHS am i able to un-install the program and re-install it? or do i only get 1 download? I would like to download it on my other computer but before i hook everything up i would like to know if i can install it again. Maybe something got corrupt when downloading Sonar. I do remember that my computer did a mandatory restart because it needed a update while i was downloading Sonar.

I've seen very little information about Home Studio, but you should be able to download it from your account.
 
https://www.cakewalk.com/My-Account/Products

+1 to not using asio4all under any circumstances.

Is it only me who misreads this thread title as "Getting Sonar to recognise my eardrums" every time I see it?

I use a Yamaha kit and do as Cactus Music suggested - I monitor via the kit's brain and playback via vsti, even though I get around 4ms latency from my interface.

Hope you get it sorted.