High CPU and Memory Utilization by Backup Exec processes like beserver.exe, dlocommandu.exe etc. in Backup Exec version 11d

Article:TECH50824  |  Created: 2008-01-19  |  Updated: 2014-01-19  |  Article URL http://www.symantec.com/docs/TECH50824
Article Type
Technical Solution

Product(s)

Issue



High CPU and Memory Utilization by Backup Exec processes like beserver.exe, dlocommandu.exe etc. in Backup Exec version 11d

 


Cause



This may happen if the directory "Temporary ASP.NET Files" does not exist in the .NET Framework install directory.
Creating this directory allows CSC.exe to function properly on which .NET Framework relies which in turn is used by Beserver.exe

 


Solution



To resolve the problem on servers running 32bit Windows Operating System:
  1. Check for a folder named "Temporary ASP.NET Files" in %windir%\Microsoft.NET\Framework\v2.0.50727 directory.
  2. If the folder is not present then create a new folder under %windir%\Microsoft.NET\Framework\v2.0.50727 and name it "Temporary ASP.NET Files".
  3. If the folder already exists then delete the folder and re-create it.
  4. Restart Backup Exec server service.

To resolve the problem on servers running 64bit Windows Operating System:
  1. Check for a folder named "Temporary ASP.NET Files" in %windir%\Microsoft .NET\Framework\v2.0.50727 folder.
  2. If the folder is not present then create a folder under %windir%\Microsoft.NET\Framework\v2.0.50727 and name it "Temporary ASP.NET Files".
  3. If the folder already exists then check for the same folder under %windir%\Microsoft.NET\Framework64\v2.0.50727 directory. If the folder is not present then copy the "Temporary ASP.NET Files" folder from %windir%\Microsoft.NET\Framework\v2.0.50727 directory and paste it into %windir%\Microsoft.NET\Framework64\v2.0.50727 directory.
  4. Restart Backup Exec server service.


 



Legacy ID



287469


Article URL http://www.symantec.com/docs/TECH50824


Terms of use for this information are found in Legal Notices