Backups of Exchange 2010 server fail with: Final error: 0xe0000391 - Backup Exec attempted to back up an Exchange database

Article:TECH169389  |  Created: 2011-09-12  |  Updated: 2013-11-20  |  Article URL http://www.symantec.com/docs/TECH169389
NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.
Article Type
Technical Solution


Issue



During a Backup of Exchange 2010, the Backup fails with the below error without writing a byte count.

 


Error



Final error: 0xe0000391 - Backup Exec attempted to back up an Exchange database according to the job settings. The database was not found, however. Update the selection list and run the job again.
 

SGMon debug logging with third party debug output enabled reveals:

MONAD:   [0000]     BECRYPTO Base Address is BE00000
MONAD:   [0000]     BECRYPTO is not loaded at proper base address, halting FIPS initialization!
MONAD:   [0000]     BECryptoInit: Initialized locks for SSL callbacks
MONAD:   [0000]     BECryptoInit: BECrypto non-FIPS mode successfully enabled.
MONAD:   [0000]     [1] []  BEExch2007Component::ValidCredentials
MONAD:   [0000]     [1] []  BEExch2007Component::CreateRunspace local PowerShell
MONAD:   [0000]     [1] []  BEExch2007Component::CreateRunspace configure Local PowerShell - Exception:  The Windows PowerShell snap-in 'Microsoft.Exchange.Management.PowerShell.E2010'
is not installed on this machine.
MONAD:   [0000]     [1] []  BEExch2007Component::CreateRunspace local PowerShell
MONAD:   [0000]     [1] []  BEExch2007Component::CreateRunspace configure Local PowerShell - Exception:  The Windows PowerShell snap-in 'Microsoft.Exchange.Management.PowerShell.E2010'
is not installed on this machine.
MONAD:   [0000]     [1] []  BEExch2007Component::IsDagVirtualNode:  [MAILBXSRVR]
MONAD:   [0000]     [1] []  BEExch2007Component::GetTargetDatabaseCopyStatus - Error:  Object reference not set to an instance of an object.
MONAD:   [0000]     E2010 GetTargetDatabaseCopyStatus failed with hr = 0x80004003
MONAD:   [0000]         Source:          BEExch2007Component
MONAD:   [0000]         Description:     Object reference not set to an instance of an object.
MONAD:   [0000]         HelpFile:
MONAD:   [0000]         HelpContext:
MONAD:   [0000]         Source:          BEExch2007Component

 


Solution



Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec Corporation is committed to product quality and satisfied customers.

This issue is currently under investigation by Symantec Corporation. Pending the outcome of the investigation, this issue may be resolved by way of a patch or hot fix in current or future revisions of the software. However, this particular issue is not currently scheduled for any release.  If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Symantec Sales representative or the Symantec Sales group to discuss these concerns.  For information on how to contact Symantec Sales, please see  http://www.symantec.com Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.


NOTE:
Customers experiencing this issue are encouraged to contact Symantec Technical Support as data is still being collected to assist in resolving this issue.

 


Supplemental Materials

SourceETrack
Value2535224
Description

EXCH: MONAD: During backup of Exchange 2010 standalone server, receive "Object Reference not set to instance of object" when attempting to create powershell runspace.



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


Terms of use for this information are found in Legal Notices