We spend a lot of time in this forum trying to figure out why some people have a problem with their particular setup, but we don't spend a lot of time trying to figure out why most people DON'T have a problem with their setup. This thread is intended to fill that void. I'll kick off with some of the things I've learned.
 
1. A computer integrated for music is a great place to start. I'm sure you've all seen Jim Roseberry's helpful posts. Well, he integrates computers for music, and they rock. I don't recall seeing a weird Sonar problem with someone having one of Jim's computers in a sig. I've been using machines from PC Audio Labs for years, and they've been rock solid. Ditto my experiences with ADK machines from Scott. Sure, you pay $1,000 and more compared to getting an Office Depot Special for $399. $1,000 is not trivial, but the amount of aggravation and time you'll save is probably worth twice as much. And avoid gaming machines; they're not the droid you're looking for.
 
2. Treat your computer like a multitrack tape recorder. Use a different computer, like the aforementioned $399 box from Office Depot (or what used to be your music computer), to do your taxes, write notes, crop photos, and all that other personal stuff. Separate church and state, and both will be happier.
 
3. Back up. This seems so obvious, but whenever someone posts about losing hours of work because of a crash...the crash was the system's fault; losing hours of work was the user's fault.
 
4. Practice safe update. Yes, you will need to attach your computer to the net sometimes. If you get an alert that there's an update to Adobe Reader, don't download it! Go to the Adobe site and download it there. Ditto Java etc. I also get my Windows Updates directly from the Microsoft site.
 
5. Commit to 32-bit or 64-bit and stick with it (although I highly recommend 64). Systems with a mix 'n' match combination of 32- and 64-bit programs and plug-ins and a bunch of wrappers are trouble waiting to happen.
 
6. Don't read the documentation. That's right...I'm saying that because I know you won't read it anyway. BUT do use the documentation's Index and Search functions. I have to learn a lot of software, and I basically just plod along until I run into something I don't know or have a problem. Then I dig into the documentation, get the answer, and carry on a little smarter than when I started.
 
7. This forum ISN'T the first place to go to solve a problem. Google, Bing, etc. are great for finding common solutions. For example, searching on "Cakewalk Sonar [name of interface] problem known issue" is often all you need to find out if, for example, there are issues with a particular interface. Compared to the forum, you'll often end up in a previous thread where there has already been substantial discussion, so you don't have to wait for a thread to unfold over the next several days.
 
8. Don't let a cat walk on your keyboard when you're in the middle of a session. Just sayin.' I don't think they memorize the keyboard shortcuts, but if they do, it's so they can pick the problematic ones.
 
Anyone else want to contribute their recipes for success?

Not even on the edge of your ballpark, but:
1. Read and follow this forums subjects, solutions and directions.
Setup bookmark/s with specific subjects and mark any of the subjects "You may need in future".
 
2. Breakdown the system into workable sections you can learn and understand.  This is how the video's are
created by Craig and others.  Also some of the video's available, especially some bargains this month are great learning and reference sources.
 
3.  Craigs #7 is a big +1 or more.  Accidentally discovered this looking at another subject.  Then used
    it more.
4. Learn the fine art of inventing new Cuss words.
 
5. Enjoy this journey as much as possible.

However!
 
If you do come to this forum for help please stick around or at least check back often. Most times answerers are provided quickly. Often to serve better more information is needed. Thus if the OP will stay on line and interact with the forum a solution can come quicker.
 
If one is an old hand and is running into a problem not reading the manual wont hurt much and using the index is a great way to find solutions. BUT new users need to read the manual if for no other reason then learning the nomenclature of Sonar. This means we will know what you are talking about.
 
A report after a solution is given and works helps in letting us know if the problem is truly solved.
 
Writing very long posts only makes people not want to answer. Try to keep it short.
 
 
 
 

just a couple more... from a dinosaur's perspective:

• Just because you can does NOT mean that you should or must. I can edit the life out of any track with V-Vocal, Melodyne, and AudioSnap, not to mention plain old slip-editing. But I can also get a great take, even if it isn't the first take. I'm not suggesting that all these tools do not provide artistic, and even practical opportunities, but you'll be a lot happier if you start with great performances.
• Speaking of which - garbage in equals, at best, polished garbage out! The single most important lesson I ever learned was to match the microphone to the instrument, and the performer, and the space. That doesn't apply to folks using only virtual instruments, but the rest of us should at least think about it. While I won't share names, the gentleman that taught me to think this way has a LOT of gold and platinum hanging on his walls. If it is good enough for him<G>...
• Don't be afraid to commit (yeah, that can be difficult for some of us, I'llskip the musician jokes for now). Sometimes you really do run out of steam. If you really can't decide just how deep the flanger should be then create an audio track that is 100% wet, then you can still adjust effect depth without straining the CPU.
• That doesn't apply only to effects... the same is true for basic processing. If you really need compression or equalization use them, print them to a new track, archive or backup the original (unprocessed) track, and move on.
• Remember that no matter the style or genre, you are producing music. Composition and arrangement will have as much or more of an impact on the mix than any processor or effect.
• Don't get a new plug-in (effect, processor or instrument) or library until you have learned the ones you have, or determined that you won't use it. Then, buy these things one at a time so you don't get overwhelmed.
• Set up track templates to do some of the heavy lifting for you. These days I am trying to set up Kontakt templates, it is a lot of tedious, BORING, work. IF I complete the task it will make my life much easier. I have other track templates set up for specific synthesizers,
• If you are using key-switched virtual instruments consider using control tracks. I use two MIDI tracks per instrument, so a fully loaded instance of Kontakt will have 32 MIDI tracks and 16 audio tracks... yeah, it sounds cumbersome, but it really isn't. OR, consider mapping key switches to continuous controllers. I'm still experimenting<G>! The benefits of CCs include no clutter in the PRV or staff view, and you can chase controllers, you can not chase key switches.

Being relatively new to this, the pain of getting started is still fresh in my memory and +1 on John's comment.  If it weren't for the forum users here I would have dropped the ball on Cakewalk.
 
1. One very clever person once told me, (that is, my brother hehe) is that teaching logic is one of the most difficult tasks to do... This is why we need to practice, some a lot more than others...

- If you're going to do a lot of composing of original material in MIDI, get a decent keyboard controller and learn to play and record as much as you can in real time. Having a dedicated "button" for every note that sends start time, velocity and duration in real time is a very powerful thing. Editing in the PRV is great, but, with few exceptions, composing from scratch in the PRV is a productivity and groove killer. Remember, they don't actually build the ship inside the bottle. 
 
- Regarding Googling for answers, put site:forum.cakewalk.com after the keywords to find relevant threads on the forum. And adding "brundlefly" as a keyword will often get you the best answer. 

I am SOOO resisting the urge to flag Brundlefly's last post as Spam :)
 
Great points.
 
It sure does seem that this go round of X3e is certainly one of, if not THE, best versions of Sonar ever released.
 
Bob Bone
 
 

I practice 2 and 4 of Craig's post religiously. I only surf and do other tasks with my Compaq Win Vista machine. I have both a custom built PC (Firwewire) and a newer gaming PC (USB). Both are used for music recording only. Both are Windows 7 64 bit, are similar in specs as far as CPU, RAM, etc... and they perform equally well with the gaming PC feeling a tad better. Probably cause it's newer and is slightly more powerful. Both are offline and only get connected to the internet for important MS updates.  I'm curious though... why avoid gaming PC's?

Well, lots of gaming computers are set up to maximize for VIDEO, and that can sometimes be problematic, due to having video processing take precedence over streaming audio, and that would be bad for Sonar - that sort of thing.
 
For Sonar, memory, CPU power, and hard drive type/number of/configuration seem to be the bigger issues than video.
 
Bob Bone
 

Lot's of great tips in here that can and WILL save hours of frustration and downtime.
 
With all of them being good - Craig's #1 suggestion is the most powerful problem solver. I have had a couple of problems here and there, but in the main scheme of things, not many. Why is that? I think it's simple. Having an optimized computer along with a solid audio interface / drivers cures as many problems as a so-so b-ball team with a great shooter. While other have complained with legitimate show stoppers for them, I've had the pleasure of mostly trouble free operations with all versions including the ridiculed X1 - and at that time I was using "gasp" Vista 64 with all updates installed. Why is that - - - I'll tell you. I have a Jim Roseberry machine I purchased in 2009. It still rocks and is dependable if not more than my previous setup of a Fostex 16 track reel to reel with a JL Cooper Smpte time code generator/reader. A great computer can power through so many software and operator shortcomings. I'm living proof.