Job Completed with Exceptions

See this document

http://www.symantec.com/docs/TECH184002

The tech184002 sure explains the issue, but does not explain how to fix the problem. In my case, this error did not start happening till I installed latest patch 213186.

My 2003 servers that get backed up are ok but all my 2008 servers display this exception now.

I don't want to convert to virtual but I get pop ups displaying this error when the job first starts and at the end of the job now.

I do not see a setting to turn this off.

I wonder if Symantec is aware of this happening after installing the latest patch.

Any ideas would be helpful.

Same here. Since 26. Februar 2014 we have the same warnings at different customers. The solution/issue mentioned in TECH184002 seems to be disjointed.

We do not use physical to virtual conversion and the backups worked fine till 26. Februar.

What happened?
A sollution / advices from Symantec would be very nice.

...have you guys checked the Known Issues section to see if this is listed there? Alternatively log a call with Symantec so that they can investigate the issue, and post back here with an update.

Thanks!

@daniel,

still we have same issue.

and case is open in Symantec they are wokring on same.

@Nightbird_143:
OK, so i'll wait till news come

@CraigV:
What exactly do you mean with "Known Issues section"?
Do you have a hint, where to exatly find that information?

http://www-secure.symantec.com/connect/backup-and-recovery/issues

Thank you! I'll have a look.

Had a look at the known issues section, but no luck.
Please let me know, if a solution is found. I'll do the same.

Same problem here too... The Error "0xe000a419 Configuration XML not found" appears since 11.02.2014. I installed latest Hotfix 213186 on 15.02.2014 and the Exception still pops up every day. The problem only occurs on my 2 Domain Controllers (Win2k8 R2) with SDR enabled. The problem description in TECH184002 points to SDR and if I turn SDR "off", the backup works without Exceptions. But this shouldn't be the solution... I didn't change anything to both Servers and didn't install any updates to the Servers/Windows or the VMware running the Servers. I checked already for driver-updates at VMware without luck, but as I stated before "I didn't changed anything".

I started a trace with SGMon and this could be the point related to the exception-message:

BENGINE:  [02.25.14 15:41:34] [3012]     2014-02-25T15:41:33.678 [loops]              - NDMPBaseHostEngine::checkForFailOver Error: Cannot load the current P2V xml file 'd:\Symantec\Backup Exec\Catalogs\BESERVER01\CatalogProcessTemporaryFolder\{GUID}\p2v.xml' Error: 0
BENGINE:  [02.25.14 15:41:34] [3012]     2014-02-25T15:41:33.678 [loops]              - NDMPBaseHostEngine::UpdateBEC Information: Disabling p2v for all resources
BENGINE:  [02.25.14 15:41:34] [3012]     2014-02-25T15:41:33.678 [loops]              - NDMPBaseHostEngine::GetP2VMetaData Error: One or all of the files could not be copied over. Cleaning up the p2v stuff in the catalog folder d:\Symantec\Backup Exec\Catalogs\BESERVER01\CatalogProcessTemporaryFolder\{GUID}
BENGINE:  [02.25.14 15:41:34] [3012]     2014-02-25T15:41:33.679 [loops]              + ndmphostbackupengine.cpp (487):
BENGINE:  [02.25.14 15:41:34] [3012]     2014-02-25T15:41:33.679 [loops]              | ERROR: SSP job failed to get P2V XML!
BENGINE:  [02.25.14 15:41:34] [3012]     2014-02-25T15:41:33.680 [loops]              + ndmphostbackupengine.cpp (603):
BENGINE:  [02.25.14 15:41:34] [3012]     2014-02-25T15:41:33.680 [loops]              | Virtual target will not be created because virtual conversion not requested.
B

I hope Symantec will be investigating this issue...