I have one end device that name was changed and had issues with the names not matching on veeam console. Tried to delete everything and start fresh and deleted the jobs on device and console and removed the existing software. Now I am receiving an error when the client tries to backup error invoker method 920. I have an open case and just need to move on and correct the issue, I assume it has to do with the bios UUID that is being used from the original backup under the old device name but it really shouldnt be this difficult to be able to start fresh and remove the old instance. Using latest veeam agent for windows along with software appliance 13.0, anyone have any suggestions on how I can get this working would be appreciated.
Veeam Support - Case # 08178527
-
bishoptf
- Enthusiast
- Posts: 38
- Liked: 1 time
- Joined: Oct 06, 2011 2:27 am
- Full Name: Tom Bishop
- Contact:
-
bishoptf
- Enthusiast
- Posts: 38
- Liked: 1 time
- Joined: Oct 06, 2011 2:27 am
- Full Name: Tom Bishop
- Contact:
Re: Veeam UUID issues Invoker error
Was really hoping to get this resolved over the weekend, anyone have any suggestions, nothing form support.....
-
bishoptf
- Enthusiast
- Posts: 38
- Liked: 1 time
- Joined: Oct 06, 2011 2:27 am
- Full Name: Tom Bishop
- Contact:
Re: Veeam UUID issues Invoker error
Can anyone help move my case along, they ask for logs which I provided and now they are asking for another set of logs....what are a second set of logs going to help resolve. I have a windows agent being backed up to software appliance and tried to delete and start over and now I am throwing an error when it starts to back up. Just need it resolved...
Veeam Support - Case # 08178527
Veeam Support - Case # 08178527
-
david.matthewson
- Influencer
- Posts: 15
- Liked: 4 times
- Joined: Oct 08, 2018 3:37 pm
- Full Name: D K Matthewson
- Contact:
Re: Veeam UUID issues Invoker error
I too have just started getting this error, [14/08/2026 15:30:58 :: Error: Unknown invoker method: 920]
- which persists across reboots.
W10 x64 to Veeam 13
- which persists across reboots.
W10 x64 to Veeam 13
-
david.matthewson
- Influencer
- Posts: 15
- Liked: 4 times
- Joined: Oct 08, 2018 3:37 pm
- Full Name: D K Matthewson
- Contact:
Re: Veeam UUID issues Invoker error
OK, resolved in my case.
The PC agent had quietly updated it self to the latest version which then no longer matched the version of B&R 13.x
This happened because the default 'auto update' flag had been left = ON for the Protection Group the Workstation was in.
The fix was to turn auto updates for the PG to OFF, extract the correct Windows agent from the B&R instance, remove the 'updated' one from the PC, (reboot PC), install new (old!) agent, reboot PC and it is all happy.
Check PC logs here - C:\ProgramData\Veeam\Endpoint - for more info.
Case # 08178527
The PC agent had quietly updated it self to the latest version which then no longer matched the version of B&R 13.x
This happened because the default 'auto update' flag had been left = ON for the Protection Group the Workstation was in.
The fix was to turn auto updates for the PG to OFF, extract the correct Windows agent from the B&R instance, remove the 'updated' one from the PC, (reboot PC), install new (old!) agent, reboot PC and it is all happy.
Check PC logs here - C:\ProgramData\Veeam\Endpoint - for more info.
Case # 08178527
Who is online
Users browsing this forum: No registered users and 5 guests