Just starting a new remix session and have encountered this major issue. I am trying to save to a HDD with 450+ GB free. This shouldn't be happening.

These are the steps I took:

1. open up session drag in vocal track and instrumental.
2. Drag in loop from drums sample folder.
3. Cut up loop and place each hit on separate track.
4. Ctr S then the error message.

Copied all and opened in a new session with the same result.

Attempting to close the session without saving causes Sonar to freeze.

Is it possible a wave file is corrupting the session?

Retried same steps with 'import audio files to session folder' checked, resulting in even more error messages.

Narrowed it down to one specific drum loop causing the problems. Glad to find its not anything more serious.

I think crisis averted and issue solved. Anyone else had this problem>?

Having this problem right now...

Seeing threads about this issue from as long as five years back, none with any actual fix.  [sarcasm] Good thing Cakewalk hasn't tackled the issue or anything. [/sarcasm]

Well, when I was running 32 bit, I would try and RAM and much as I could into a session (large sample libraries, etc.).... this would tax my system... and I think one of the plugs had a memory leak which would lead to the SYMPTOM when saving... DISK SPACE FULL or some such non-sense.

When I went to 64 bit OS and x64 SONAR... problem GONE.

Jim

alexniedt


Having this problem right now...

Seeing threads about this issue from as long as five years back, none with any actual fix.  [sarcasm] Good thing Cakewalk hasn't tackled the issue or anything. [/sarcasm]

There will always be VSTs with memory leaks and other stuff causing problems. It not possible for Cakewalk to eliminate (all of) those, if the flaw is in the product of another company. 
 
 

The "disk full" message is bogus. It just means an (unidentified) error was raised while attempting to write to disk. It could be a failing disk drive, a loose cable, or simply a badspot on the disk. Run a disk diagnostic that can map out badspots. Go to your drive manufacturer's website; all the majors offer free diagnostic software.

Sometimes running defrag clears these things up. Working a while in some programs can cause a lot of fragmenting to the point where the program can't put all the bits together to complete a task. Whenever Sonar acts goofy like this, I close out of everything and run the defragger and alls back to normal.
 
Steve

perfectprint


Just starting a new remix session and have encountered this major issue. I am trying to save to a HDD with 450+ GB free. This shouldn't be happening.

These are the steps I took:

1. open up session drag in vocal track and instrumental.
2. Drag in loop from drums sample folder.
3. Cut up loop and place each hit on separate track.
4. Ctr S then the error message.

Copied all and opened in a new session with the same result.

Attempting to close the session without saving causes Sonar to freeze.

Is it possible a wave file is corrupting the session?

Dude, i am right there with you. memtest came up clean, disks all defraged several times. im lost on this and can find nothing to help me out either.

Instead of CTRL-S, try a File-Save-As if you haven't already. 

There are SO many threads about this.  Has there really not been a solution or workaround for this after 7-8 years?
 
In my case, when I get the error message, I can't even copy-and-paste any of my tracks to a new session because as soon as I try to close the session (without saving) SONAR crashes, and SONAR never crashes for me.  Only when I get the 'disk may be full' message, which happens only twice a year or so but is still vastly annoying.  It's been twice a year for the past 5 years.
 
I finally noticed something, maybe a clue.  I have 900+ GB of acid files on a separate drive.  I have them organized into 8 major categories, i.e. 'hip hop', 'jazzy & funky', etc.  I have one folder of 'pads & electronica' that I use the least, very rarely.  But it seems like everytime I get the error message I've been digging around in that folder, audition samples and whatnot.  That seems like it might be something specific to my situation, like corrupt files in that folder, but I don't know enough to diagnose it.
 
Even if the problem is not SONARs, I wish they could build a workaround into the program, since it seems to happen often enough.  Something like a 'duplicate this file' command where it regenerates all the audio into a new file and copies all the settings and plugins and routings over to the new file.