Hello,

Backup Exec 2010 is not processing a job, but is listed as using 25-30% CPU and 1.2-1.5 gb of RAM on a 2008 server with 10 gb of RAM.

Event Viewer shows many of the following entries:

Log name: application
Source: ASP.NET 2.0.50727.0
EventID 1309

Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 11/26/2012 9:18:30 AM
Event time (UTC): 11/26/2012 5:18:30 PM
Event ID: 860b7c8a7c81497cabce22decc919175
Event sequence: 1
Event occurrence: 1
Event detail code: 0
 
Application information:
    Application domain: 20be86d9a8bf447590bc5cb5a43a466a-159674-129984239097465020
    Trust level:  
    Application Virtual Path: /CRF
    Application Path: C:\ProgramData\Symantec\CRF\20be86d9a8bf447590bc5cb5a43a466a\

NOTE: - I checked the drive, and this folder does not exist
    Machine name: {server name removed}
 
Process information:
    Process ID: 5572
    Process name: beserver.exe
    Account name: {domain name removed}\administrator
 
Exception information:
    Exception type: HttpException
    Exception message: Server cannot access application directory 'C:\ProgramData\Symantec\CRF\20be86d9a8bf447590bc5cb5a43a466a\'. The directory does not exist or is not accessible because of security settings.
 
Request information:
    Request URL: http://127.0.0.1/CRF/CRF.aspx?DataFile=C:\Users\Administrator\AppData\Local\Temp\20be86d9a8bf447590bc5cb5a43a466a\Data.xml&RDLFile=C:\Users\Administrator\AppData\Local\Temp\20be86d9a8bf447590bc5cb5a43a466a\RDL.rdl
    Request path: /CRF/CRF.aspx
    User host address: 127.0.0.1
    User:  
    Is authenticated: False
    Authentication Type:  
    Thread account name: {domain name removed}\administrator
 
Thread information:
    Thread ID: 12
    Thread account name: {domain name removed}\administrator
    Is impersonating: False
    Stack trace:    at System.Web.HttpRuntime.EnsureAccessToApplicationDirectory()
   at System.Web.HttpRuntime.HostingInit(HostingEnvironmentFlags hostingFlags)
 
 
I saw a similar post about a year ago, with no resolution listed. So far, if I start and restop the BE services, the errors go away for a couple of days. If anyone has any other suggestions, please let me know.

Thank you for your assistance.

Sincerely,

Andreas

Andreas@MurphyMcKay.com