“Failed To Index Guest File System” Error in Veeam Backup and Replication 

When working with Veeam Backup & Replication, ensuring seamless backups is a critical part of IT infrastructure management. However, you might occasionally encounter errors that disrupt the process, such as: 

Failed to index guest file system. Veeam Guest Agent is not started. Failed to prepare guest for hot backup. Details: Failed to connect to guest agent. Errors: ‘Cannot connect to the admin share. Host: [Target Machine]. Account: [Account Name]. Win32 error:The network path was not found. Code: 53 

Or you may encounter errors such as: 

Failed to inventory guest system: Veeam Guest Agent is not started. Failed to index guest file system. Failed to prepare guest for hot backup. Details: Failed to connect to guest agent. Errors: ‘Cannot connect to the admin share. Host: [Target Machine]. Account: [Account Name]. Win32 error:Access is denied. Code: 5 

These errors can be daunting, especially if you’re unsure where to begin troubleshooting. It usually indicates issues related to network connectivity and/or permissions. By understanding the underlying causes and following structured troubleshooting steps, you can quickly identify and resolve the problem. 

Error Codes Breakdown 

Win32 Error Code 53: “The network path was not found.” 

This error indicates that the Veeam server is unable to reach the specified host over the network. Common causes include: 

• The target machine is offline or unreachable. 
• Firewall rules are blocking communication. 
• The admin share (e.g., C$) is disabled or inaccessible. 

Win32 Error Code 5: “Access is denied.” 

This error occurs when the account used for authentication lacks the necessary permissions to access the admin share or perform guest processing tasks. 

Troubleshooting Steps 

1. Verify Network Connectivity

Confirm that the host is reachable:

• Use the ping command or other network tools to test connectivity:
  • ping [Target Machine]
• If the host does not respond, check:
  • Whether the machine is powered on.
  • Network configurations (e.g., IP address, subnet, gateway).

2. Verify Admin Share Accessibility

Confirm that the admin share is enabled and accessible using Command Prompt:

• On the guest machine, run the following command:
  • net shareEnsure C$ or other default shares are listed.
• Test access to the admin share from the Veeam server:
  • net use \\\[Target Machine]\C$ /user:[Account Name]
    • If this fails, check the share permissions and the local security policy (see Step 4).

3. Check Credentials and Permissions

Verify that the account used for the job has the necessary permissions:

• The account should have local administrator rights on the guest machine.
• Ensure the account is not restricted by Group Policy or denied logon rights.

4. DNS and Hosts File

Confirm that the Veeam server can resolve the hostname to the correct IP address:

• Use the nslookup command:
  • nslookup [Target Machine]
• If DNS resolution fails, add an entry to the hosts file.

5. Test Backup Job with Another Account

If all else fails, test the backup job using a different account:

• Create a new domain administrator account.
• Update the guest processing credentials in Veeam and rerun the job.

By following these steps, you should be able to identify and resolve the “Failed to index guest file system” error.

If you encounter persistent issues or need additional assistance, don’t hesitate to contact our support team at support@managecast.com. We are ready to help ensure your backup operations run smoothly and effectively!