• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1078
  • Last Modified:

Backup Exec 2010 R3 errors

Hi,

For some reason, I seem to be getting loads of errors in my Application event log. It seems to be logging more than a few per minute, and wondered if anyone could advise on a solution.

I can see that the issue is being logged under a certain user, which I am sure is a local administrator, and I have rebooted the server, and still no difference.

I can also see the error lies with Symantec. The only symantec software this server has is backup exec 2010 R3, with all updates installed.

Can someone help?

thanks


Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 11/18/2013 1:38:59 PM
Event time (UTC): 11/18/2013 1:38:59 PM
Event ID: 508cf92008cf4a23a8243f7425483e82
Event sequence: 1
Event occurrence: 1
Event detail code: 0
 
Application information:
   Application domain: 66b387f57ead4c3982219d40dc5340c5-1258247-130292555380313143
   Trust level:  
   Application Virtual Path: /CRF
   Application Path: C:\ProgramData\Symantec\CRF\66b387f57ead4c3982219d40dc5340c5\
   Machine name: LDR-BACK-01
 
Process information:
   Process ID: 3224
   Process name: beserver.exe
   Account name: LDC\supbackup
 
Exception information:
   Exception type: HttpException
   Exception message: Server cannot access application directory 'C:\ProgramData\Symantec\CRF\66b387f57ead4c3982219d40dc5340c5\'. 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\supbackup\AppData\Local\Temp\66b387f57ead4c3982219d40dc5340c5\Data.xml&RDLFile=C:\Users\supbackup\AppData\Local\Temp\66b387f57ead4c3982219d40dc5340c5\RDL.rdl 
   Request path: /CRF/CRF.aspx
   User host address: 127.0.0.1
   User:  
   Is authenticated: False
   Authentication Type:  
   Thread account name: domain\user
0
ccfcfc
Asked:
ccfcfc
1 Solution
 
Gareth GudgerCommented:
0
 
ccfcfcAuthor Commented:
Turns out that .Net 4.0 was corrupt.

Thank you for your help. Running a repair on .Net 4.0 resolved the issue.

Kind regards
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now