Comprehensive data protection for all workloads
Post Reply
whippersnapper
Novice
Posts: 5
Liked: 1 time
Joined: Mar 02, 2015 3:15 pm
Full Name: Tone Loke
Contact:

Error: value cannot be null. Parameter name: key

Post by whippersnapper »

Case # - 00820342

I have opened a case but I thought I would pose this question to the forum as well. Curious if anyone knows the cause or remedy for the following error.

Error: value cannot be null. Parameter name: key

We are running the latest version of Veeam. The error occurred on a VM that has previously backed up successfully until just now.

Thanks.
Vitaliy S.
VP, Product Management
Posts: 27055
Liked: 2710 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: Error: value cannot be null. Parameter name: key

Post by Vitaliy S. »

Based on the search query against existing topics, there have not been any similar issues reported so far. Please update your topic with a resolution for future readers after investigation with our support team. Thanks!
whippersnapper
Novice
Posts: 5
Liked: 1 time
Joined: Mar 02, 2015 3:15 pm
Full Name: Tone Loke
Contact:

Re: Error: value cannot be null. Parameter name: key

Post by whippersnapper » 1 person likes this post

Thanks for the reply, Vataliy. I will be sure to update this post once I work with support.
whippersnapper
Novice
Posts: 5
Liked: 1 time
Joined: Mar 02, 2015 3:15 pm
Full Name: Tone Loke
Contact:

Re: Error: value cannot be null. Parameter name: key

Post by whippersnapper »

Response from support: "Usually this is a one-time issue with the database when an attempt is made to pull data that isn't fulfilled. Have you seen the error since it appeared this time?"

Since this was the first time it occurred I will monitor and update if reoccurs. Otherwise, looks like it might just be a one time deal.
whippersnapper
Novice
Posts: 5
Liked: 1 time
Joined: Mar 02, 2015 3:15 pm
Full Name: Tone Loke
Contact:

Re: Error: value cannot be null. Parameter name: key

Post by whippersnapper »

This server backed up successfully last night. So support's reply that the error may have been a one time occurrence seems to hold true at this point.
Post Reply

Who is online

Users browsing this forum: No registered users and 169 guests