https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IzMDI5IiwiaGFzaCI6IjYwYjg2MDYwLWQ5MGEtNGI1MS04M2QyLWM0NmFhZjUxMGVjYyJ9
1-800-691-1991 | 9am - 8pm ET
EN

Managed Veeam Agent backup job fails with "Unknown invoker method: 2757" error

Challenge

A Veeam Agent backup job managed by the backup server fails with the following error:

User-added image

Failed to start backup job Error: Unknown invoker method: 2757

Cause

The issue occurs if you have the following software configuration:
  • Veeam Agent for Microsoft Windows 3.0.2 is installed on the backed-up computer.
  • Veeam Backup & Replication 9.5 U4a or earlier is running on the backup server.

Solution

To resolve the issue, you must upgrade Veeam Backup & Replication to version 9.5 Update 4b. For details about the Veeam Backup & Replication upgrade process, see Release Notes in this Veeam KB article and the Upgrading to Veeam Backup & Replication 9.5 Update 4 section in the Veeam Backup & Replication User Guide.

 
KB ID:
3029
Product:
Veeam Agent for Microsoft Windows, Veeam Backup & Replication
Version:
VBR 9.5.4.2753 or older w/ VAW 3.0.2
Published:
2019-10-28
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

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!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later