I'm a Sonar newbie and have run into an issue. I'm trying to exchange projects with a friend, we both run Sonar X3 and he is sending me .CWB files of his projects. The files open fine on my install, however when I try to play the audio I get the message:
 
Unable to open audio playback device. Device may not support the current projects audio format or may be in use.
 
My playback device is a focusrite Scarlett 2i2 and functions perfectly when the .CWB file is not being opened. The device used to record the project in question is a Focusrite Saphire Pro 40 I believe. I know it's a Focusrite, but do not remember the specific model offhand. I've tried changing the audio bit depth and that has not allowed the audio to play. I'm a bit at a loss here. Any help or advice will be greatly appreciated.
 
Ron

That message comes up when you try and open a file that has a different setting than yours. 
Ask your friend what sample rate they are using. 
When sharing it's best to use 44.1 or 48 to keep the files smaller. 
 
Also instead of bundle files , which seem to occationaly have issues, why not use CWP files and share the whole folder. When CWB files go bad you loose everything at once. With CWP files you still have your audio and if you also back up as a MID file you loose very little if something goes bad. . 
I save my projects as a midi back ups because that is where a lot of work might have taken place. 

Sounds like a sample rate issue, what sample rate is your friend using for his sound card, and what sample rate do you have set for your sound card. 

As it turns out this wasn't the problem. The issue was that Sonar had previously been installed on the C: drive of this workstation and I had moved it to an application drive to allow for more space. The remove / reinstall process left a pointer in the registry to a couple of the .DLL files associated with  ProChannel. For some reason this didn't cause an issue with creating new projects, recording etc... however when I opened the .CWB files the error described above would occur. I traced down all instances of the bad path in the registry and changed them and the problem went away. Chalk it up to installer woes, they do occur.
 
Ron