VAO fails to deploy a VAO agent to a standalone Veeam Backup & Replication server
| KB ID: | 4097 |
| Product: | Veeam Disaster Recovery Orchestrator |
| Published: | 2021-02-09 |
| Last Modified: | 2021-02-09 |
Challenge
When VAO tries to deploy a VAO agent to a standalone Veeam Backup & Replication server, you get a generic error "Failed to communicate to agent", and all VAO attempts to communicate with the VAO agent fail. You can also see the following error in the VAO agent logs (located in the log folder under %programdata%\Veeam\Veeam Availability Orchestrator\Log) on the Veeam Backup & Replication server:
2020-08-07 16:35:52.7622 [ERROR ] 8320 [_5] Agent.AgentService: Failed to initialize Backup service: This access control list is not in canonical form and therefore cannot be modified.Cause
The permissions on the log folder are ordered incorrectly. To check if this is the issue, open the properties of the folder %programdata%\Veeam\Availability Orchestrator and switch to the Security tab. If you get the error "The permissions on <folder> are incorrectly ordered, which may cause some entries to be ineffective", you must reorder the permissions.
Solution
Open the properties of the parent folder %programdata%\Veeam on the Veeam Backup & Replication server, switch to the Security tab, click Advanced and select the Replace permissions entries on all child objects with entries shown here that apply to child objects option.
| KB ID: | 4097 |
| Product: | Veeam Disaster Recovery Orchestrator |
| Published: | 2021-02-09 |
| Last Modified: | 2021-02-09 |
Couldn't find what you were looking for?
Below you can submit an idea for a new knowledge base article.
Report a typo on this page:
Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!
Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!
