Backup job fails with error 0xe000942a - Backup Exec did not find any virtual machines to dynamically include in the backup. V-79-57344-37930

Problem

Backup job fails with error 0xe000942a - Backup Exec did not find any virtual machines to dynamically include in the backup.

Error Message

Final error: 0xe000942a - Backup Exec did not find any virtual machines to dynamically include in the backup.
Final error category: System Errors
For additional information regarding this error refer to link V-79-57344-37930

Cause

A backup job may fail with this error in one of the following conditions :

1. While backing up virtual machines using Agent for Hyper-V

2. While backing up virtual machines using Agent for VMWare/ESX

3. While backing up SharePoint 2007 SP2 database using Agent for SharePoint.

4. After changing Backup Exec System Account (BESA) password in Active Directory.

Solution

1. While backing up virtual machines using Agent for Hyper-V

The host and guest machines can be seen in the backup selections, but all guest machines may be missing from the backup.

To resolve the issue :
Confirm all netowrk connections are functioning and nothing is blocking connections between the Hyper-V host and Backup Exec media server

• NICs
• cables
• Switches
• Firewalls

2. While backing up virtual machines using Agent for VMWare

Following is observed in the Beremote log :

BEREMOTE: [3704] ADC_ResolveDeviceName: pid = 2252, checking VMVCB::\\ServerName\Virtual Center 
BEREMOTE: [3704] ApplyRegExp(): Invalid input (VMVCB::\\ServerName\Virtual Center). Parsing Failed. 
BEREMOTE: [3704] GoodEvName(): Invalid EV device (VMVCB::\\ServerName\Virtual Center). 
BEREMOTE: [3704] RPCDsSession::GetLoginCredentials: Connecting to BEM API as user: DOMAIN.LOCAL\Administrator 
BEREMOTE: [4236] FS_CreateTempDLE 
BEREMOTE: [4236] VM_VCBPROXY_FS::DisconnectFromVCServer: status = 0X0 
BEREMOTE: [4236] SymVmTools: Login: SYM_VMC_ERROR: SOAP_ERROR 
BEREMOTE: [4236] SymVmTools: SOAP 1.1 fault: "":ServerFaultCode [no subcode]

This may occur due to an incorrect user name or password

To resolve this issue:
a. Use the Root account if the backup selections are done by accessing the ESX server
b. Make sure the account has BESA rights on the VCenter Server if the backup selections are done by accessing VCenter.
c. Make sure the virtual machine is selected from within the VMware vCenter and ESX Servers node available in the Backup selection list.
d. Re-create the selection list and run the backup job again.

3. While backing up SharePoint 2007 SP2 database using Agent for SharePoint.

This may occur due to incorrect permissions on SharePoint or SQL Server.

To resolve this issue:
a. Make sure the BESA account is a part of Sharpoint Administrators group.
b. Make sure the BESA account has sysadmin rights on SQL Server.
c. Add the BESA account as DBOwner on all database.
d. Make sure the SharePoint databases are selected from within the Microsoft SharePoint Server Farms node in the Backup selection list.

4. After changing Backup Exec System Account (BESA) password in Active Directory.

This occurs if the BESA password has been changed in Active Directory and not updated in Backup Exec

To resolve this issue:
a. Update the BESA password in Backup Exec console by going to Network - Logon Accounts - select the BESA account - Edit - Change Password.
b. Update the new password for Backup Exec services by going to Tools - Backup Exec Services - Services Credentials - Change Service account information.
c. Restart all Backup Exec services after completing the above-mentioned steps.