Greetings, I have been working on some recent issues we have had with our backup solution and sometimes I really need to restart the Backup Exec Services. For as long as I can remember, there are times when the beremote.exe service simply will not stop at all and we have profusely tried any and all command line stuff to try to terminate the process. Are there any tricks to killing that process outside of a total reboot of the server? Again, we've tried pskill, taskkill, task manager (obviously), services (obviously) and nothing will completely stop the beremote.exe process.

Hi Brandon, That seems to have carried through in a number of versions of BE. A service hangs when you're trying to restart/stop it, and it can't get stopped. Normally this was put down to the service executable trying to finish something. I'd stop your AV scans and try a test run of the service restarts. See what that does, and consider patching the media server with any available updates. Thanks!

Thank you. I will certainly give this solution a try the next time the service get's hung.

taskkill /F /IM beremote.exe /T does NOT work? This is strange.. I've seen this happening before but not for BE..

No sir. We've tried pretty much every process kill command that has ever been invented and nothing works except a reboot of the machine. This problem is beyond irritating because of the importance of this particular server in our environment.

This problem is beyond irritating because of the importance of this particular server in our environment. While I realize that every shop may not be able to afford it, this is one of the reasons I have always recommended a dedicated media server. The media server doesn't have to be all that powerful a machine, just be a server OS with plenty of RAM.

Unfortunately the installation is something I inherited. I'm not sure what the mindset might have been when the media server was chosen, but it would have definitely been better to find a less important server in the environment.

Cannot terminate beremote.exe service

14 Replies

CraigV
Moderator
13 years ago
Hi Brandon,

That seems to have carried through in a number of versions of BE. A service hangs when you're trying to restart/stop it, and it can't get stopped. Normally this was put down to the service executable trying to finish something.

I'd stop your AV scans and try a test run of the service restarts. See what that does, and consider patching the media server with any available updates.

Thanks!
Brandon_1998
Level 3
13 years ago
Thank you. I will certainly give this solution a try the next time the service get's hung.
Simon_B_
Level 6
13 years ago
taskkill /F /IM beremote.exe /T does NOT work? This is strange.. I've seen this happening before but not for BE..
Brandon_1998
Level 3
13 years ago
No sir. We've tried pretty much every process kill command that has ever been invented and nothing works except a reboot of the machine. This problem is beyond irritating because of the importance of this particular server in our environment.
Ken_Putnam
Level 6
13 years ago
This problem is beyond irritating because of the importance of this particular server in our environment.

While I realize that every shop may not be able to afford it, this is one of the reasons I have always recommended a dedicated media server. The media server doesn't have to be all that powerful a machine, just be a server OS with plenty of RAM.
Brandon_1998
Level 3
13 years ago
Unfortunately the installation is something I inherited. I'm not sure what the mindset might have been when the media server was chosen, but it would have definitely been better to find a less important server in the environment.
CraigV
Moderator
13 years ago
...might be worth your while upgrading to BE 2010 R3 if you aren't running it already!
jst3751
Level 3
13 years ago
I am running BE 2010 R3 fully patched and still have this problem.
Brandon_1998
Level 3
13 years ago
Sounds to me like Symantec has some homework to do.
Jacquesy
Level 2
13 years ago
I opened a ticket a year ago re this - and it never got sorted (luckily this was using a dedicated backup server so rebooting it isn't a massive pain...)

however, I now have the same on a SBS 2008, 2010 r3 install... so I've opened a new ticket and so far I've just been told something else is listening on the port (it isn't)

So a year on and they've still not fixed what seems to be causing a fair few people issues!

It's not quite as "practical" to reboot an SBS server when the backup services hang... !