Beserver.exe shows a constant CPU (processor) usage (never idles) and shows signs of a memory leak regardless of the Backup Exec for Windows Servers application activity

Article:TECH55466  |  Created: 2007-01-12  |  Updated: 2011-09-18  |  Article URL http://www.symantec.com/docs/TECH55466
Article Type
Technical Solution

Product(s)

Environment

Issue



Beserver.exe shows a constant CPU (processor) usage (never idles) and shows signs of a memory leak regardless of the Backup Exec for Windows Servers application activity


Solution



To confirm symptoms and need for this solution, perform the following steps:

1.  Open the C:\Documents and Settings\All Users\Application Data\Symantec\CRF\CRF.log

 
The lines below are repeated indefinitely in the log file:
 

 
03/07/2008 10:14:40 [3]:  Initializing reporting engine.
 
03/07/2008 10:14:40 [3]:  Object reference not set to an instance of an object.
 

 
-OR-
 

 
05/18/2007 12:01:48 [3]:  Initializing reporting engine.
 
05/18/2007 12:01:48 [3]:  Could not load file or assembly 'System.EnterpriseServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
 

 
-OR-
 

 
03/19/2008 11:58:44 [3]:  Initializing reporting engine.
 
03/19/2008 11:58:44 [3]:  Could not load file or assembly 'Microsoft.ReportViewer.Common, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. (C:\Documents and Settings\avadmin\Local Settings\Temp\c9e80867dc9f48c09d67121f5f616dfa\web.config line 9)
 

 
2.  Go to the following site and download Process Monitor:

 
Process Monitor v1.26
 
When filtering for beserver.exe, the following repeat entries will occur:
 

 
QueryOpen  C:\Documents and Settings\All Users\Application Data\Symantec\CRF\xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx  NAME NOT FOUND       (where x... stands for a unique GUID)
 

 
After confirming these errors are received, remove (uninstall) and reinstall .NET Framework 2.0.


Please Note: The exact error messages in the CRF.log can range wildly.  While it has been observed that some issues can be resolved by uninstalling and reinstalling various programs that access .NET (i.e. Microsoft Report Viewer Redistributable 2005), in every instance of this error, completely uninstalling and reinstalling .NET 2.0 is the best course of action.  For more information on downloading .Net from Microsoft's Site, review the following:

 
Microsoft .NET Framework Version 2.0 Redistributable Package (x86)
 



Legacy ID



294064


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


Terms of use for this information are found in Legal Notices