Monitoring and reporting for Veeam Data Platform
Post Reply
teletek
Novice
Posts: 8
Liked: never
Joined: Jan 09, 2020 6:48 am
Full Name: Teletek
Contact:

Violation of PRIMARY KEY constraint Veeam One 11

Post by teletek »

Hi all,

When I take report from Protected VMs in Veeam One 11, I get the following error. How can I fix it? Can you help me ?

Violation of PRIMARY KEY constraint 'PK__#all_vms__E7B6593FAB8D70B9'. Cannot insert duplicate key in object 'dbo.#all_vms'. The duplicate key value is (sauron.********l_vm-430262).


Case #05326721 Report Problem
Mildur
Product Manager
Posts: 8549
Liked: 2223 times
Joined: May 13, 2017 4:51 pm
Full Name: Fabian K.
Location: Switzerland
Contact:

Re: Violation of PRIMARY KEY constraint Veeam One 11

Post by Mildur »

Hi Teletek

Please keep working with support, it‘s a known issue and there should be a hotfix. Support can confirm if you have the same issue.
#1: Protected VMs report fails with error after upgrade to V11a
Symptoms: When attempting to generate the Protected VMs report after upgrading to V11a report generation fails with the "Violation of PRIMARY KEY constraint 'PK__#all_vms__E7B6593F0D341491'. Cannot insert duplicate key in object 'dbo.#all_vms'." error message.
Cause: Issue with one of the stored procedures which caused the erroneous deletion of job sessions. Issue ID 348516.
Status: Please, contact our customer support to receive a hotfix
Product Management Analyst @ Veeam Software
wishr
Veteran
Posts: 3077
Liked: 453 times
Joined: Aug 07, 2018 3:11 pm
Full Name: Fedor Maslov
Contact:

Re: Violation of PRIMARY KEY constraint Veeam One 11

Post by wishr »

Hi Teletek,

It definitely looks like issue #348516.

Thanks
Post Reply

Who is online

Users browsing this forum: No registered users and 9 guests