08-17-2014 04:05 PM
Backups failed to run on Sat and Sun. The backup exec service was stopped. I have since started the service. In the logs I have the following from Sun night, not sure if it's related or not:
Failed to configure ApplicationHA Console with the Backup Exec media server for Auto Recovery as a Backup Exec certificate could not be issued to the ApplicationHA Console.Check Backup Exec Root Certificates. ApplicationHA Console may not be properly configured or may be giving an improper CSR.
Solved! Go to Solution.
08-17-2014 07:18 PM
If ApplicationHA is enabled, then you would see a Backup Exec tab in your vSphere client.
See if this KB helps - http://www.symantec.com/business/support/index?page=content&id=TECH223209
08-17-2014 06:30 PM
Is Backup Exec installed on a VM and is ApplicationHA being used in your environment ?
If not, then the above event most likely is not related to the beserver.exe being stopped.
Would recommend to check the event logs (and not just errors and warnings) for the time period prior to the service being stopped. Most likely to find a relevant event. If there isn't such an event, check if this issue reoccurs or if this was a one-time occurence.
08-17-2014 06:44 PM
BE is installed on a physical server and not on a VM. The server does have a VM server running on it though.
I'm not sure what ApplicationHA is.
Here is the BE agent error:
Log Name: Application
Source: BEDBG
Date: 16/08/2014 4:36:37 PM
Event ID: 259
Task Category: (1)
Level: Error
Keywords: Classic
User: N/A
Computer: <SERVER>
Description:
A process crash has been detected.
Faulting application: beserver.exe 14.1.1786.0
Faulting module: KERNELBASE.dll 6.2.9200.16864
Fault offset 0x47b8c
Exception code 0xe0434352.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="BEDBG" />
<EventID Qualifiers="24578">259</EventID>
<Level>2</Level>
<Task>1</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-08-16T07:06:37.000000000Z" />
<EventRecordID>179691</EventRecordID>
<Channel>Application</Channel>
<Computer>SERVER</Computer>
<Security />
</System>
<EventData>
<Data>beserver.exe</Data>
<Data>14.1.1786.0</Data>
<Data>KERNELBASE.dll</Data>
<Data>6.2.9200.16864</Data>
<Data> 0x47b8c</Data>
<Data> 0xe0434352</Data>
<Data>/entt?product=BEversion=14.1.1786&module=eng-crash-v0&error=v-79-57344-32772&ping&language=en&build=retail&OS=Windows_6_2_9200+0+0&Comment=exeName=beserver.exe|exeVer=14.1.1786.0|modName=KERNELBASE.dll|modVer=6.2.9200.16864|code=0xe0434352|offset=0x47b8c|pid=4900|tid=760b4831-19fc-488e-8d6c-b30d5c8b8bae|patches=(1)HF-218257|origin=3|arch=x64|info=NONE|stack=C:\Windows\SYSTEM32\ntdll.dll (6.2.9200.16912-7C1AE34008F746339F5DE231594F36402) 0x2B5A C:\Windows\system32\KERNELBASE.dll (6.2.9200.16864-F7C494CCF5CC467F86B40D98D9F3EF3E2) 0x10EA D:\Program Files\Symantec\Backup Exec\beserver.exe (14.1.1786.0-92302C1249FA4857954A49F22B3B3F411) 0x4E15A6 0x4E16F6 C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscoreei.dll (4.0.30319.18010-49CE7C803EF34DF29DF2007ED83CD6402) 0x44494 C:\Windows\system32\KERNELBASE.dll (6.2.9200.16864-F7C494CCF5CC467F86B40D98D9F3EF3E2) 0x68F24 C:\Windows\SYSTEM32\ntdll.dll (6.2.9200.16912-7C1AE34008F746339F5DE231594F36402) 0x8B8A3 0x16D7A 0x1612D 0x17420 0x17879 C:\Windows\system32\KERNELBASE.dll (6.2.9200.16864-F7C494CCF5CC467F86B40D98D9F3EF3E2) 0x47B8C C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll (4.0.30319.18449-FE4D3910A57F4EC5905C9E88FC357C4B2) 0x1EE6AF 0x3AA7AA 0x2444D1 0x1AFA ??? (???-000000000000000000000000000000000) 0xE754CD0F 0xD9BB3868 0xD9C5B840 0xD9C193A8 </Data>
</EventData>
</Event>
Log Name: Application
Source: Application Error
Date: 16/08/2014 4:52:58 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: <SERVER>
Description:
Faulting application name: beserver.exe, version: 14.1.1786.0, time stamp: 0x5371d6c1
Faulting module name: KERNELBASE.dll, version: 6.2.9200.16864, time stamp: 0x531d34d8
Exception code: 0xe0434352
Fault offset: 0x0000000000047b8c
Faulting process id: 0x1324
Faulting application start time: 0x01cfb0b5b7f6821e
Faulting application path: D:\Program Files\Symantec\Backup Exec\beserver.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 2550f786-2516-11e4-9403-42f2e90dd3ab
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-08-16T07:22:58.000000000Z" />
<EventRecordID>179692</EventRecordID>
<Channel>Application</Channel>
<Computer>SERVER</Computer>
<Security />
</System>
<EventData>
<Data>beserver.exe</Data>
<Data>14.1.1786.0</Data>
<Data>5371d6c1</Data>
<Data>KERNELBASE.dll</Data>
<Data>6.2.9200.16864</Data>
<Data>531d34d8</Data>
<Data>e0434352</Data>
<Data>0000000000047b8c</Data>
<Data>1324</Data>
<Data>01cfb0b5b7f6821e</Data>
<Data>D:\Program Files\Symantec\Backup Exec\beserver.exe</Data>
<Data>C:\Windows\system32\KERNELBASE.dll</Data>
<Data>2550f786-2516-11e4-9403-42f2e90dd3ab</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>
---
We do have a fair few ASP.net errors and vss errors before the crash.
08-17-2014 07:18 PM
If ApplicationHA is enabled, then you would see a Backup Exec tab in your vSphere client.
See if this KB helps - http://www.symantec.com/business/support/index?page=content&id=TECH223209
08-17-2014 07:58 PM
Thank you, I will make the exclusion and see how it goes.
08-18-2014 04:03 PM
We are still getting asp.net warning errors related to BE during the backup window, I have excluded the CRF path in VSE via ePO and restarted the BE services:
Log Name: Application
Source: ASP.NET 4.0.30319.0
Date: 18/08/2014 12:38:04 PM
Event ID: 1309
Task Category: Web Event
Level: Warning
Keywords: Classic
User: N/A
Computer: BESERVER.DOMAIN
Description:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 18/08/2014 12:38:04 PM
Event time (UTC): 18/08/2014 3:08:04 AM
Event ID: 1f44b59937d14d6e88912f2c8e96df04
Event sequence: 4
Event occurrence: 1
Event detail code: 0
Application information:
Application domain: d27b3ca294cf4a009266be63158b448a-2-130528048805738052
Trust level: Full
Application Virtual Path: /CRF
Application Path: C:\ProgramData\Symantec\CRF\d27b3ca294cf4a009266be63158b448a\
Machine name: VSDC01
Process information:
Process ID: 12096
Process name: beserver.exe
Account name: DOMAIN\backup_admin
Exception information:
Exception type: HttpException
Exception message: The file '/CRF/CRF.aspx' has not been pre-compiled, and cannot be requested.
at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate)
at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate)
at System.Web.Compilation.BuildManager.GetVirtualPathObjectFactory(VirtualPath virtualPath, HttpContext context, Boolean allowCrossApp, Boolean throwIfNotFound)
at System.Web.Compilation.BuildManager.CreateInstanceFromVirtualPath(VirtualPath virtualPath, Type requiredBaseType, HttpContext context, Boolean allowCrossApp)
at System.Web.UI.PageHandlerFactory.GetHandlerHelper(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath)
at System.Web.HttpApplication.MapHttpHandler(HttpContext context, String requestType, VirtualPath path, String pathTranslated, Boolean useAppConfig)
at System.Web.HttpApplication.MapHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
Request information:
Request URL: http://127.0.0.1/CRF/CRF.aspx?DataFile=C:\Users\backup_admin\AppData\Local\Temp\d27b3ca294cf4a009266be63158b448a\Data.xml&RDLFile=C:\Users\backup_admin\AppData\Local\Temp\d27b3ca294cf4a009266be63158b448a\RDL.rdl
Request path: /CRF/CRF.aspx
User host address: 127.0.0.1
User:
Is authenticated: False
Authentication Type:
Thread account name: DOMAIN\backup_admin
Thread information:
Thread ID: 1
Thread account name: DOMAIN\backup_admin
Is impersonating: False
Stack trace: at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate)
at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate)
at System.Web.Compilation.BuildManager.GetVirtualPathObjectFactory(VirtualPath virtualPath, HttpContext context, Boolean allowCrossApp, Boolean throwIfNotFound)
at System.Web.Compilation.BuildManager.CreateInstanceFromVirtualPath(VirtualPath virtualPath, Type requiredBaseType, HttpContext context, Boolean allowCrossApp)
at System.Web.UI.PageHandlerFactory.GetHandlerHelper(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath)
at System.Web.HttpApplication.MapHttpHandler(HttpContext context, String requestType, VirtualPath path, String pathTranslated, Boolean useAppConfig)
at System.Web.HttpApplication.MapHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
Custom event details:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="ASP.NET 4.0.30319.0" />
<EventID Qualifiers="32768">1309</EventID>
<Level>3</Level>
<Task>3</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-08-18T03:08:04.000000000Z" />
<EventRecordID>181480</EventRecordID>
<Channel>Application</Channel>
<Computer>BESERVER.DOMAIN</Computer>
<Security />
</System>
<EventData>
<Data>3005</Data>
<Data>An unhandled exception has occurred.</Data>
<Data>18/08/2014 12:38:04 PM</Data>
<Data>18/08/2014 3:08:04 AM</Data>
<Data>1f44b59937d14d6e88912f2c8e96df04</Data>
<Data>4</Data>
<Data>1</Data>
<Data>0</Data>
<Data>d27b3ca294cf4a009266be63158b448a-2-130528048805738052</Data>
<Data>Full</Data>
<Data>/CRF</Data>
<Data>C:\ProgramData\Symantec\CRF\d27b3ca294cf4a009266be63158b448a\</Data>
<Data>VSDC01</Data>
<Data>
</Data>
<Data>12096</Data>
<Data>beserver.exe</Data>
<Data>DOMAIN\backup_admin</Data>
<Data>HttpException</Data>
<Data>The file '/CRF/CRF.aspx' has not been pre-compiled, and cannot be requested.
at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate)
at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate)
at System.Web.Compilation.BuildManager.GetVirtualPathObjectFactory(VirtualPath virtualPath, HttpContext context, Boolean allowCrossApp, Boolean throwIfNotFound)
at System.Web.Compilation.BuildManager.CreateInstanceFromVirtualPath(VirtualPath virtualPath, Type requiredBaseType, HttpContext context, Boolean allowCrossApp)
at System.Web.UI.PageHandlerFactory.GetHandlerHelper(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath)
at System.Web.HttpApplication.MapHttpHandler(HttpContext context, String requestType, VirtualPath path, String pathTranslated, Boolean useAppConfig)
at System.Web.HttpApplication.MapHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
</Data>
<Data>http://127.0.0.1/CRF/CRF.aspx?DataFile=C:\Users\backup_admin\AppData\Local\Temp\d27b3ca294cf4a009266be63158b448a\Data.xml&RDLFile=C:\Users\backup_admin\AppData\Local\Temp\d27b3ca294cf4a009266be63158b448a\RDL.rdl</Data>
<Data>/CRF/CRF.aspx</Data>
<Data>127.0.0.1</Data>
<Data>
</Data>
<Data>False</Data>
<Data>
</Data>
<Data>DOMAIN\backup_admin</Data>
<Data>1</Data>
<Data>DOMAIN\backup_admin</Data>
<Data>False</Data>
<Data> at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate)
at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate)
at System.Web.Compilation.BuildManager.GetVirtualPathObjectFactory(VirtualPath virtualPath, HttpContext context, Boolean allowCrossApp, Boolean throwIfNotFound)
at System.Web.Compilation.BuildManager.CreateInstanceFromVirtualPath(VirtualPath virtualPath, Type requiredBaseType, HttpContext context, Boolean allowCrossApp)
at System.Web.UI.PageHandlerFactory.GetHandlerHelper(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath)
at System.Web.HttpApplication.MapHttpHandler(HttpContext context, String requestType, VirtualPath path, String pathTranslated, Boolean useAppConfig)
at System.Web.HttpApplication.MapHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
</Data>
</EventData>
</Event>
08-18-2014 06:54 PM
Apart from the CRF path, have you added exclusions for the rest of the BE directory ?
Add C:\Program Files\Symantec & C:\ProgramData\Symantec as well.
08-18-2014 07:10 PM
I've just added c:\program files\symantec and c:\programdata\symantec.
Screen cap below for our list of exclusions:
08-18-2014 07:23 PM
If you've just added the exclusions, check if the errors/warning still reoccur or not. (Unsure as to if McAfee's VSE takes immediate effect or not). If possible, a reboot may help as well.
However, if you already added the exclusions without any change in BE, would recommend you to log a formal support case.
08-18-2014 07:30 PM
I left of the trailing backslash on the paths which means it probably isn't excluding the paths .. If I understand McAfee's exclusion policy that is.
https://kc.mcafee.com/corporate/index?page=content&id=KB50998&pmv=print
08-18-2014 07:36 PM
Thanks,
I've fixed up the exlusions since I think they need the trailing \ otherwise it thinks its a file.
Once the backup's finish I will restart the BE service and if it still fails reboot the server.
08-19-2014 03:46 PM
Looks good overnight after I added the trailing \ onto the path.