Hi guys,
I am getting the following error when testing a guest interaction proxy: "Building VMs list error: Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index"
The guest interaction proxy I am trying to test is my proxy server on the target host where the replication will be sitting on but I am also getting the same message when I am testing the local Veeam server.
It all started because I see "failed to inject guest runtime using guest interaction proxy, failing over to backup server" message.
Any idea what's going on?
I am using B&R 9.5 update 2 enterprise plus edition
-
- Enthusiast
- Posts: 37
- Liked: 2 times
- Joined: Jun 16, 2017 1:18 pm
- Full Name: Rotem Ben
- Contact:
-
- Enthusiast
- Posts: 37
- Liked: 2 times
- Joined: Jun 16, 2017 1:18 pm
- Full Name: Rotem Ben
- Contact:
Re: Building VMs list error when trying to test guest intera
Update: The reason I received the error message was because for some reason the VM was missing from the job and the VM list was empty.
However, I am still trying to figure out how come I am still getting the "failed to inject guest runtime using guest interaction proxy, failing over to backup server" message.
I am still able to run the job but it's awfully slow and I suspect this message has something to do with it.
Thoughts?
However, I am still trying to figure out how come I am still getting the "failed to inject guest runtime using guest interaction proxy, failing over to backup server" message.
I am still able to run the job but it's awfully slow and I suspect this message has something to do with it.
Thoughts?
-
- Novice
- Posts: 3
- Liked: never
- Joined: Nov 16, 2016 7:21 pm
- Full Name: Kent
- Contact:
Re: Building VMs list error when trying to test guest intera
Did you ever figure this out?
-
- Product Manager
- Posts: 20413
- Liked: 2302 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Building VMs list error when trying to test guest intera
Kent, for further investigation it might be worth reaching our support team, as the OP didn't provide solution or support ticket number. Thanks.
Who is online
Users browsing this forum: Bing [Bot] and 58 guests