any event log clues?

robert_e_bone
Could that be an access violation - a problem with permissions for something?
 
I know some of that used to occur from being behind on Windows maintenance, but that was principally folks trying to run one of the X2 or X3 maintenance versions where they did not have current C++ runtime routines that were required by coding changes in Sonar.
 
Just wondering if that sort of thing might be at play - OR maybe something needed/wanted to be installed or launched with Run As Administrator explicitly selected as an option. (maybe?)
 
Bob Bone

Everything *should* be up to date. I keep all the Windows updates going and Sonar itself gets updated each release so I shouldn't have any issues there. I'm always logged in as administrator so in theory, it should be running in admin mode already though I did try opening it manually as administrator last night with the same results.
 
I'm trying to remember what plugins I had running. AD2, EW Pianos, Kontakt, Omnisphere/Trilian, Spaces and Amplitube I think was all.

pwalpwal
any event log clues?

Trying to figure out how to open the Sonar dump files right now.

TerraSin

pwalpwal
any event log clues?

Trying to figure out how to open the Sonar dump files right now.

i meant in the windows event log - access violations etc will be recorded there

Just to clarify - having a Windows user account that is an Administrator is not the same thing as explicitly selecting Run As Administrator.  Run As Administrator gives a higher set of execution privileges than you get when using a user account that is an Administrator.
 
I see that this didn't seem to help in any case, if I understood your above comments, but I just wanted to make sure you understood Administrator account and Run As Administrator are 2 different things. :)
 
Bob Bone

What happens if you actually disconnect the audio interface and open that particular project, just to see if it will open this way?
 
If it DOES open without the audio interface connected, it will yell at you for no audio device but should still open.  That would at least allow you to examine the project more closely, or even try doing a Save As to save it off under a different name, in case there is some sort of project corruption - no guarantees, but at least you would have something to try, and should be able to get into the project if there are any issues between that project and the audio interface.  IF you try a Save As, plug the interface back in and try opening up the newly-saved version of the project, and see what happens.
 
Bob Bone
 
 

robert_e_boneI see that this didn't seem to help in any case, if I understood your above comments, but I just wanted to make sure you understood Administrator account and Run As Administrator are 2 different things. :)

Correct, though by default being on the administrator account should give me full basic privileges to run everything in a standard mode.
 

What happens if you actually disconnect the audio interface and open that particular project, just to see if it will open this way?

The second picture I posted is from when I shut the interface down. Sonar itself crashes out rather than the Roland dll. That's what confused me even more and leads me to believe there is something else going on.

Uninstalled the drivers for the 700. Still crashing. Going to try reinstalling Sonar completely. I hate to do that because I lose all my settings but not sure what else I can do here.

Some of those settings could be part of the problem. It still might be better to send the dumps to CW and call them before doing much of anything though.

scook
Some of those settings could be part of the problem. It still might be better to send the dumps to CW and call them before doing much of anything though.

That's the next step if reinstalling doesn't do the trick. I'm not sure how long it will take for support to get back to me and I need to try getting this up and running today.