Video Screencast Help

Beserver.exe CPU load

Created: 14 Jan 2014 • Updated: 15 Jan 2014 | 5 comments
This issue has been solved. See solution.


just as Lorenz in tttps://

"We are using Backup Exec 2010 R2 with latest updates on a Windows Server 2008 R2 SP1 with latest Windows Updates.

beserver.exe never gets idle, it is always using 30% - 50% CPU load, even if there are no jobs are running.

In CRF.log the following error is logged multiple times per second:

03.03.2011 01:31:31  [10]:  Attempted to access an unloaded AppDomain."

I can't find any reference to this issue but in this closed thread without solution.

However we do exprerience the same issue in same context (except for our BE witch is R3)

Uninstalling/reinstalling .NET 3.5.1 did not resolve.

Can somebody helps ?

Thank You


Operating Systems:

Comments 5 CommentsJump to latest comment

CraigV's picture


R2 is 1 behind R3 which also has just had SP3 released. My advice would be to upgrade to BE 2010 R3 which fixed a number of issues with the previous 2 versions, and then load BE 2010 R3 SP3. After installing SP3, run LiveUpdate to see if there are any subsequent patches.

Once done, you can push-install these updates to your remote servers. You can use your current licenses (just grab copies of the Data/Catalogs folders before doing the upgrade) and then check again.

You can get the ISO and SP3 on the links below:

You should also make sure that any antivirus installed on the media server isn't perhaps actively scanning the BE services...put in exclusions for them if this is the case.


Alternative ways to access Backup Exec Technical Support:

Jean-Michel Berne's picture

Thank you.

I should have written "except for our BE witch is R3 with latest updates"

SP3 is installed and LiveUpdate says all protucts are up to date.

Investigating with the AV is a good idea, thank you again !

I'll do and report ...


VJware's picture

One good way to start would be to use ProcMon for monitoring beserver.exe activity when there are not jobs running. And I would recommend to log a formal support case as well.

Jean-Michel Berne's picture

Well done !

I first uninstalled AV (KAV FSEE) to check what its impact is.

Then beserver.exe was so quiet !!!

I re-install now the AV, setting the exclusions I think to be done.

Hope has returned.

I think I'll play with procmon anyway, just for fun (knowledge is fun)

Thank you all

Oh... and happy new year

CraigV's picture

Glad this has worked out for you!

Alternative ways to access Backup Exec Technical Support: