Skip to content

March 9, 2018


SCVMM 1801 Upgrade Fails

When going through the upgrade process, I got a failure when install the upgraded Management Server.

After digging through the setup logs (C:\ProgramData\VMMLogs), I found this in the SetupWizard log file: Violation of PRIMARY KEY constraint ‘PK_tbl_NetMan_PortClassification’. Cannot insert duplicate key in object ‘dbo.tbl_NetMan_PortClassification’. The duplicate key value is (<ID>).

After some investigation, I found a brief mention of this in the 1801 release notes. It states if any of the default port classifications have been renamed, the upgrade will fail. The release notes just mention that it is required to rename these back to their default values, but doesn’t tell you what these values are . In my case it was the “Live migration  workload” port classification. The default for some reason has two spaces between “migration” and port”. Sometime in the past, we had removed this extra space. Adding the space back in resolved the issue.

You can determine which port classification is the culprit by comparing the ID in the logs to the ID in the tbl_NetMan_PortClassification table in the VMM database. If the old VMM Management server is no longer online, you will have to manually update the Name in the tbl_NetMan_PortClassification table in the VMM database to fix this.

In case your failure is for a different classification, here are all the default port classifications:

  • SR-IOV
  • Host management
  • Network load balancing
  • Guest Dynamic IP
  • Live migration  workload
  • Medium bandwidth
  • Host Cluster Workload
  • Low bandwidth
  • High bandwidth
  • iSCSI workload
1 Comment Post a comment
  1. geyer
    Mar 19 2018



Share your thoughts, post a comment.


Note: HTML is allowed. Your email address will never be published.

Subscribe to comments