Skip to main content
  • EN

Hi community,

 

Case number: 07501750

After upgrading to Veeam BR 12.2.0.334 (I was on v11 before) my Surebackup Job stopped working with error:

“Error: Value cannot be null. Parameter name: destination”

I’m using “Advanced single-host” with two production networks and I have “Application Group” with single VM.

I’ve tried recreating Virtual Lab, Application Group but the error still persists, it looks like it has problems with adding route?

 

Value cannot be null.

Parameter name: destination (System.ArgumentNullException)

at Veeam.Backup.Common.CRouteUtilityItem..ctor(String destination, String netmask, String gateway)

 

But routes are appearing when I put “route print” on windows cmd.

Is this a bug or am I missing something in V12?

 

 

Hi @sparx ...welcome to the Community. Yeah..it could definitely be a bug. I’ve personally not seen a problem like that posted here. It sounds like there may be something going on in the VBR DB which may need cleaned up. I’d continue working with Support to resolve.

Best.

 

Not sure if this is a bug or not.  Since you have an open case I would suggest to continue on that path.  The community can only offer suggestions as we are not support and in order to address this issue support is the better avenue to pursue for help.

 
 
 

I’m trying to but I’m on NFR license so I only have free support 😃 I’m curious if only I’m having this issues.

I’m trying to but I’m on NFR license so I only have free support 😃 I’m curious if only I’m having this issues.

I have not seen this issue myself.  Maybe also do a search in the forums - https://forums.veeam.com

Since you have a case number you can post that and you will get more response there.

Hi @sparx , are you configuring the vLab from the Veeam Backup & Replication console or you’re inside the windows VBR, try to configure connected into the VBR server, just an ideia.

I’m on windows server where VBR is installed :/

did you triy to add the route already (manually)

I’ve tried adding route manually but it looks like Veeam isn’t checking for that and is still adding the route.

Even after changing networking in virtual lab to “Basic single-host (automatic configuration” I got the same error.

Comment


Terms & Conditions