The error information for Microsoft Active Directory can be viewed on the Druva Console or from the logs folder on the client machine.
To view the errors and logs on the client machine, follow these steps:
Navigate to the following directory:
C:\ProgramData\Druva\ActiveDirectory\logs\ActiveDirectoryPluginOpen the
ActiveDirectoryPlugin.logfile. This file contains all the errors and logs.
Microsoft Active Directory error references accessible from Druva Console
The following error references can be accessed and viewed on Druva Console:
Active Directory plugin encountered error when trying to connect Druva service
Error Message: Active Directory plugin encountered error when trying to connect Druva service
Error Description: This issue was encountered because communication with the Druva Cloud service failed.
Error Resolution: To resolve this issue, do the following:
Give it a moment, ensure your internet is connected, and retry the domain registration.
If retrying does not work,verify:
Network and Firewalls: Ensure that no local network, proxy, or firewall is blocking or modifying traffic to the Druva cloud endpoints (this often causes the HTML/decode errors).
Active Directory Agent Status: Verify that the Druva agent is properly activated and connected to the cloud.
Configuration update failed
Error Message: Configuration update failed
Error Description: The system successfully checked the backup folder you selected, but it ran into a roadblock when trying to permanently save that setting. The agent running in the background is being blocked from saving to its own internal settings file.
Error Resolution: You need to clear the path so the program is allowed to save its files. Please check the following four things:
Storage Space: Make sure the computer's hard drive is not completely full. The program needs free space to write its configuration files.
Folder Permissions: Verify that the computer's security settings give the software "write" permissions, which allows it to create and edit files.
Antivirus Blocks: Check your antivirus or security software. It might be mistakenly blocking the program from saving changes. You may need to add the backup program to the antivirus "allow list" (exclusions).
Shared Folder Setup: Double-check that the backup shared folder itself is set up correctly and allows the program to write data to it.
Once you have verified these settings, try saving the configuration again.
Your user name or password cannot be validated. Please check the details and try again
Error Message: Your user name or password cannot be validated. Please check the details and try again
Error Description: The system tried to connect to the network's directory (LDAP) to verify your account or collect domain information, but your login was rejected. The server reported "invalid credentials." This almost always means one of three things:
The password entered is incorrect.
The username is formatted incorrectly.
Your account has been temporarily locked due to too many failed login attempts.
Error Resolution: Try the following steps to resolve the issue:
Check your username format: Make sure you are typing your username exactly as required. It typically needs to be in one of these formats:
name@domain.com(UPN) orDOMAIN\username.Verify your password: Carefully re-enter your password, ensuring Caps Lock is off.
Check for a locked account: If you recently tried to log in multiple times with the wrong password, your account may be locked. You will need to wait a few minutes or contact IT to unlock it.
LDAP Server error
Error Message: LDAP Server error
Error Description: This usually happens because the system's connection account does not have the proper security permissions to read the required information.
Error Resolution: The specific account the system uses to log in (the "bind account") needs to be granted permission to read your network's setup details. If you have an IT team, you will likely need them to adjust these permissions or check the server for underlying errors.
Error decrypting plugin config
Error Message: Error decrypting plugin config
Error Description: The system is unable to unlock and read certain secure data (technically known as a decrypt failure). Because this happens in the background, you might actually see this issue show up as a completely different, seemingly unrelated error message on your screen.
Error Resolution: Restart the software: First, try using the Repair or Re-activate option on your agent. If config is corrupt, work with Support to reset plugin config safely.
Error encrypting plugin config
Error Message: Error encrypting plugin config
Error Description: This issue occurred because encrypted domain credentials storing failed during Manage Domain operation.
Error Resolution: Run the agent with appropriate permissions, ensure config directory has write permissions, and retry saving credentials. Re-activate agent if encryption keys are inconsistent.
Invalid shared folder path. Check the format and try again.
Error Message: Invalid shared folder path. Check the format and try again.
Error Description: The backup (or restore) shared folder path failed UNC/format validation. For example, invalid Windows UNC format.
Error Resolution: Use a valid UNC path (\\server\share\folder). Avoid local-only paths if the product expects a network share for staging.
Cannot access shared folder path. Check your user name and password and ensure the account has write permissions to the provided path
Error Message: Cannot access shared folder path. Check your user name and password and ensure the account has write permissions to the provided path
Error Description: The path to the backup/restore shared folder is correct, but the agent failed to access it. This typically indicates that the share is unreachable, permissions are denied, or a generic access error occurred.
Error Resolution: Verify share availability, SMB firewall rules, and read/write/modify permissions. To isolate the issue, test folder access directly from the DC using the affected account.
Failed to collect domain information from LDAP
Error Message: Failed to collect domain information from LDAP
Error Description: After authentication, collecting domain metadata from LDAP failed for reasons other than simple invalid credentials.
Error Resolution: Resolve DC replication/health and LDAP permissions so the bind account can query domain naming contexts, then retry manage domain.
Cannot connect to Druva service. Check your configuration and try again
Error Message: Cannot connect to Druva service. Check your configuration and try again.
Error Description: Your attempt to register the domain with the Druva service failed due to an internal communication issue.
Error Resolution: Check your cloud connection, proxy settings, and account activation, then retry adding the domain. If it still fails, collect system logs for support.
Unable to establish a secure LDAPS connection on port 636. Verify LDAPS is enabled on this domain controller and its certificate is valid, or uncheck 'Use SSL' to connect over LDAP
Error Message: Unable to establish a secure LDAPS connection on port 636. Verify LDAPS is enabled on this domain controller and its certificate is valid, or uncheck 'Use SSL' to connect over LDAP
Error Description: This error occurs because your application is attempting to connect to the Domain Controller (DC) securely over port 636, but the connection is failing—usually because the DC lacks the necessary certificate to support LDAPS, or a firewall is blocking the traffic.
Error Resolution: Enable LDAPS on the DC, install a valid server certificate, open port 636, or disable “Use SSL” to use LDAP on port 389 if policy allows.
Unable to connect to the domain controller on port 389 (LDAP). Verify the LDAP service is running.
Error Message: Unable to connect to the domain controller on port 389 (LDAP). Verify the LDAP service is running.
Error Description: This issue occurred because plain LDAP connection to the Domain Controller (DC) on port 389 failed.
Error Resolution: To resolve the issue do the following:
Verify your system's directory (DNS) can successfully find the main server's address.
Ensure the port 389 is open,
The AD DS is turned on and running normally.
There are no security systems or firewalls stopping your machine from reaching the server.
Windows Server Backup is not installed on this server. Install the feature before configuring this domain.
Error Message: Windows Server Backup is not installed on this server. Install the feature before configuring this domain.
Error Description: System state backup readiness check found that the Windows Server Backup feature is not installed (wbadmin feature not installed).
Error Resolution: On the Domain Controller (DC), install Windows Server Backup (Server Manager → Add Roles and Features), then run manage domain again.
Unable to verify Windows Server Backup status. Ensure the agent is running with administrator privileges.
Error Message: Unable to verify Windows Server Backup status. Ensure the agent is running with administrator privileges.
Error Description: The wbadmin readiness check failed or timed out.
Error Resolution: Run the Druva agent service as Local System or an account with administrative rights on the Domain Controller (DC). Ask your IT support team to check the server's security rules and ensure they aren't blocking the backup software from running its necessary background tasks.
The Active Directory Recycle Bin is not enabled on this domain. Please enable it before configuring this domain.
Error Message: The Active Directory Recycle Bin is not enabled on this domain. Please enable it before configuring this domain.
Error Description: This issue occurred because the plugin confirmed that the Active Directory Recycle Bin feature is disabled on the domain.
Error Resolution: Enable the Active Directory Recycle Bin for the forest, then configure the domain again.
Granular Backup/Restore Error Codes
exit status 1
Error Message: exit status 1
Error Description: This error is a general message meaning your backup or restore job failed. To fix it, you need to check the log file for that specific job to see exactly which part broke.
Error Resolution: To resolve the most common causes:
Find the exact error in the logs: Open the log file for the failed job and search for words like
ERROR,FATAL,missing, orauth failure. This will tell you which of the following issues to fix.Check your connection and passwords (LDAP issues): If you are restoring data, make sure your backup server can still connect and log in to your user directory (LDAP). Expired credentials or network blocks are common causes.
Look for locked or broken files (Object errors): If the job started but did not finish, a specific file, email, or folder might be locked or lacking the right permissions. The log file will name the exact item causing the failure so you can skip or fix it.
Verify your backup setup (Startup issues): If the job failed immediately, the backup software may have sent incomplete instructions. Double-check your backup configuration to ensure all required fields (like the log folder path and job data) are filled out correctly.
exit status 2
Error Message: exit status 2
Error Description: The Delete job completed with mixed results: some objects were deleted or skipped, while some failed.
Error Resolution: Check the deletion reports and error logs to see exactly which items (objects) failed to delete. Correct the issue blocking the deletion and run the delete process again for those remaining items.
System State Backup/Restore Error Codes
exit status 1
Error Message: exit status 1
Error Description: The system state process could not decode the instructions it needed to run your task. This happened because the instructions were either missing required information, or the data format they were written in (Base64 or JSON code) was broken and could not be translated.
Error Resolution: Restart the job from the console. If it fails again, upgrade or repair the agent software and ensure the plugin is sending valid instructions. Contact Support if the system repeatedly fails to read the instructions.
exit status 2
Error Message: exit status 2
Error Description: The process could not create the log directory or initialize logging.
Error Resolution: Ensure the configured log path exists, has free disk space, and has write permissions by the agent account.
exit status 3
Error Message: exit status 3
Error Description: This issue occurs due to the following:
Server Identity: The server is not recognized as a Domain Controller.
Storage: Not enough disk space or the system cannot create backup folders.
Software Conflicts: Windows Backup (
wbadmin) is busy with another job, timed out, or crashed.Upload Failure: The backup saved locally but failed to transfer to the cloud.
Error Resolution: To resolve this issue, do the following:
Verify Setup: Ensure you are on a healthy Domain Controller with plenty of free disk space. Run the backup agent as Administrator.
Stop Conflicts: Cancel any other active Windows Backup jobs.
Check Logs: Review the ADSS and
wbadminlogs to pinpoint the exact failure (Example, detection, space, or network upload).Fix and Retry: Resolve the specific error found in the logs, then run the backup again.
exit status 4
Error Message: exit status 4
Error Description: The system failed to perform a System State Restore (restoring essential Windows operating system files and settings). The failure happened due to one of three main issues along the recovery path:
Missing Backup Image: The download failed mid-way, or the system could not rename the downloaded staging folder to
WindowsImageBackup.Download Tool Failure: The secondary download utility (datamover) was missing or configured incorrectly.
Windows Backup (
wbadmin) Tool Errors: The built-in Windows backup utility timed out, got stuck while busy, or failed while checking status (status poll).
Error Resolution: To resolve this issue, do the following:
Check Download and Connection: Ensure a valid cloud path, verify the datamover service is configured, and confirm the backup package finishes downloading completely.
Elevate Privileges and Clear Errors: Run the restore using Administrator privileges and clear any active
wbadminhanging processes or errors.Review Partner Logs: Check diagnostic logs for specific failures like
download failed,downloader is required, orwbadmin stderr.
exit status 5
Error Message: exit status 5
Error Description: The process received an operation other than backup or restore.
Error Resolution: Retry the task from your console. If the error happens again, reach out to Support with the task details and logs.
exit status 6
Error Message: exit status 6
Error Description: The backup or restore task failed to run due to a setup or launch issue:
Missing/Invalid Settings: No backup/restore request was found, or required settings are invalid.
Forest Recovery: The forest recovery process is missing its designated backup target.
Process Launch Failure: The system failed to spawn (start) the process required to run the forest recovery.
Error Resolution: To resolve this issue, do the following:
Check Settings: Open the console and verify backup/restore configurations, file paths, targets, and forest recovery options.
Set Recovery Parameters: Ensure both the backup target and continuation settings are specified for forest recovery.
Update Agent: If process launch failures persist after verifying settings, update the system agent to the latest version and retry.
exit status 7
Error Message: exit status 7
Error Description: Automated Forest Recovery was trying to automatically fix and restore your network's domain server setup, but the recovery process failed partway through and stopped.
Error Resolution: To resolve this issue, do the following:
Check Logs: Open
forest-recovery.logand the script errors to find the specific point of failure.Fix Prerequisites: Resolve any pending server reboots, ensure DNS and domain roles (FSMO) are functioning, and confirm the DSRM admin password.
Retry: Re-run the forest recovery process once all setup checks pass.
wbadmin exit non-zero
Error Message: wbadmin … exit code=N (with stderr/stdout in logs)
Error Description: A wbadmin command (specifically start backup, restore, or get versions) failed to execute.
Error Resolution: To resolve the issue, do the following:
Review the
wbadminexecution output recorded in the ADSS or partner log files.Resolve the specific Windows error code identified in those logs.
Verify that the Windows Server Backup feature is fully installed on the machine.
Ensure the executing agent process runs with elevated administrative privileges.
wbadmin 0xFFFFFFFE / -2
Error Message: Administrator privileges required (hint in logs)
Error Description: This error occurred because Windows Backup reported an access/admin/service issue.
Error Resolution: Run the agent service as Administrator on the Domain Controller, then verify that the Windows Backup service is active.
wbadmin execute failure
Error Message: Command failed to execute (not a normal exit code)
Error Description: Unable to launch wbadmin. The executable is either missing from the system or its execution has been blocked.
Error Resolution: Install the Windows Server Backup feature and ensure wbadmin.exe is included in the service account's PATH environment variable.
Microsoft Active Directory error references on client machine
The following error references can be viewed from the logs folder on the client machine. For more information on how to access errors from logs folder, see Error references accessible from the Active Directory Plugin logs folder on client machine
1005
Error Message: You are not authorized to access this page.
Error Description: This issue was observed because the system could not verify your account access.
Error Resolution: Before continuing, please check the following:
Active Directory agent is activated and the activation tokens are valid
Your account has the required permissions to perform the change
Re-activate the Active Directory agent and retry. For more information, see Activate the agent using Registration Key.
1006
Error Message: Service is not available
Error Description: The system could not complete your request because a critical background program, the AD (Active Directory) Agent plugin was temporarily unavailable or turned off.
Error Resolution: To resolve this issue, do the following:
Check your system to ensure both the Druva Active Directory Agent and the AD Agent plugin are currently running.
Restart both of these services.
Wait a few minutes for them to fully reconnect, then try your action again.
3005
Error Message: Account does not exist
Error Description: The system encountered an unexpected problem locating this account. This is a rare error that usually indicates a mismatch in your account configuration or setup.
Error Resolution: To resolve this issue, do the following:
Check Active Directory (AD): Confirm that the account currently exists and is active in AD.
Check the Druva Console: Verify that the account is properly set up and visible within your Druva dashboard.
Retry your action: Once you have confirmed the account exists in both systems, try your task again.
If both systems show the account but you still see this error, contact Support for further assistance.