SONARPDR.exe Still Running in Background

So, periodically, Sonar stops responding (usually as the result of a plugin not playing well with others) and I have to exit and relaunch the program. Usually, this does the trick and I'm up and running again in less than a minute. However, occasionally, SONARPDR.exe continues running in the background and, unless I reboot, I can't reopen Sonar for 5 to 10 minutes; i.e., until the executable stops.
 
Anyone know how to force the shutdown of the .exe? I've tried the following command line from the install directory (which has worked on other .exes), but to no avail:
 
taskkill /f /im "sonarpdr.exe"
 
Any suggestions would be greatly appreciated. Thanks.
 
 
 
 

Unfortunately, no. I should have mentioned that. It no longer shows up on the Applications tab of Task Manager and when I highlight it and click End Process on the Processes tab nothing happens.

Hi Benjaminfrog,
This is frequently the result of a MIDI device (keyboard, interface or whatnot) keeping the Sonar process open. 

M-Audio devices are frequent culprits for this...I had a USB Midisport interface for years that would do the same thing. Sadly, even unplugging the interface didn't work...the only solution for me was to reboot.

Dean

@razorwit... Oh man. That would drive me crazy. I'm thinking of getting an Axiom 25 too. Hope it doesn't pull that crap on me.

Hi
If Sonar is not showing up in the Processes tab on Windows Task Manager I would agree there is something wrong here - possibly with the installation - have you tried a fresh install? - with crashes things can get corrupted sometimes
Nigel

Has this problem been persistent since you've been using your current set up or is it a new issue?

Bajan Blue


Hi
If Sonar is not showing up in the Processes tab on Windows Task Manager I would agree there is something wrong here - possibly with the installation - have you tried a fresh install? - with crashes things can get corrupted sometimes
Nigel

It is showing up on the Processes tab. I just haven't been able to end the process.
 
Thanks for the tip, though. If it winds up not being the M-Audio issue Dean mentioned, I may try a fresh install.

Beepster


Aw crap... I really wanted the Axiom but not if it's gonna cause problems. I was gonna get a second gen though (or whatever the current model is... I know they've just updated it). Anyway, maybe check to see if there are any updated drivers for your Axiom. That might fix it. Just guessing though. Cheers.

Good thought. I'll check for newer drivers.

Thanks for that, Razorwit. Seriously. I was completely unaware of the M-Audio conflict. It will be factored into my controller purchase research. I love this place. :-)

Hiya, FBB. Hope you are well. That looks like a confirmation on this. What a drag. That Axiom looks like a nice little dealymadoodle... but not ten minutes of load time and BSOD nice. Ugh. More research must be done. Cheers.

I get this one happening to me about once a week (on a busy week - maybe 15ish hours of work). I'm using the Edirol UA25EX. X1d, i72600, 8gig Ripjaws X, decent Asus MoBo etc. So I don't know... I'm using Asio as WDM is not a happy camper. Doesn't appear to be any plugs or specific behaviour that causes it. I should make a detailed log each time it happens.

Got some supposed super task-kill program to try. I'm waiting for another crash now though so I can try it. I've always just restarted except once I kept trying things for 10-15 mins and it cleaned up without a restart. So maybe that would happen every time, but it's faster to just restart.

Boo :(

I occasionally have the same issue running a Delta 1010 along with an Axiom 61...just to be clear here...are we saying the sonarpdr.exe process is hard to kill in task manager due to M-audio drivers or are we saying an M-audio product/drivers are causing the issue in the 1st place? 
Thanks very much,
Randy

I had this a lot with my older Asus MB and M-Audio Axiom 49. Now that I have upgraded Motherboards, I think it went away.

hmm... sounds like it's mostly interfaces causing issues. Maybe the Axiom is safe? And I'm curious about the comment regarding just powering down the device. Essentially if I were to encounter this problem just disconnecting the Axiom might allow the process to close normally? I really want that keyboard. I'd hate to have to start my search all over again. :-/

@randy... Yeah, I've been hesitant to buy M-Audio stuff in the past and I never really knew why (I think it was the affiliation with Avid that irked me) but now that I'm here and reading up on stuff it seems that gut instinct may have been at least somewhat correct. Seems like there are a lot of strange issues like this surrounding their stuff at least in regards to Sonar. I just can't afford the fancy Roland stuff at the moment or I'd go that route. IDK... maybe it'll work out but 10 minute long screw ups is pretty bad. At least I'm aware of it now so if something does go wonky I won't be completely stumped. Ugh... it's always something, eh?