Troubleshooting the error: "Violation of PRIMARY KEY constraint

Title

Troubleshooting the error: "Violation of PRIMARY KEY constraint - Cannot insert duplicate key in object"

Overview

A Primary Key constraint is a unique identifier of a row or record in a database table and must contain a unique value.

Sometimes it happens that there has been changes made in Snow License Manager that causes a violation of the primary key. This generates an error "Violation of PRIMARY KEY constraint" with "Cannot insert duplicate key in object" and the error will be evident in different places depending on where it happens. If it happens during the Data Update Job which fails, then it is usually found in the tblErrorLog, or if it happens when a Snow License Manager service is working with the data, it can be seen in the service' log file.

The reason behind this can be found by having a closer look at the actual error message and back-track the information in the SQL databases to find out where to look in Snow License Manager web GUI.

Examples

Error during that Data Update Job:

From SnowLicenseManager.dbo.tblErrorLog:

Error #2627 in procedure CustomFieldJobFullRebuild line 170. [Violation of PRIMARY KEY constraint 'PK__#EAV______F7EDC7F541292C9D'. Cannot insert duplicate key in object 'dbo.#EAV'. The duplicate key value is (4, 1, 1173, Accepted Budget).]

Here we can see that during the procedure CustomFieldJobFullRebuild something went wrong, and it indicates that something with a Custom Field Value is not right. If we look at the numbers and what they mean.

From SnowLicenseManager.dbo.tblcustomfieldValue:
4 is the Custom Field
1 is the CID
1173 is the unique identifier where this custom field is applied to
Then we have the text entered into this custom field

If we then look at the SnowLicenseManager.dbo.tblCustomfield and search for #4 we will get additional information and the type of custom field which is in the CategoryID column:
1: User
2: Computer/Mobile Device
3: License
4: Agreement
5: Application
6: Oracle Order Product
7: Oracle Order

When we know the category type, we can then browse it in Snow License Manager by using the unique value of 1173, in the error above, this was of the License category and then we browse:

<your slm-server>/Pages/License.aspx?id=1173&list=LL

to see if we can find something wrong with the Custom field or its data.

Error during a Snow License Manager service:

Violation of PRIMARY KEY constraint 'PK_tblComputerLicenseTransfer'. Cannot insert duplicate key in object 'dbo.tblComputerLicenseTransfer'. The duplicate key value is (1, 498, 8, 2657aae9-83f9-40ff-8728-03d5e6ecae6a, 82bc7621-5977-4dc5-b206-d2761878ba77, 37370, 363831016).

This particular error is happening during Compliance calculation and is logged in the Licensing Service log file found in
C:\Program Files\Snow Software\Logs\LicensingService. As we know the table name we can query it and match the numbers to the columns to find out where this is happening.

From SnowLicenseManager.dbo.tblComputerLicenseTransfer:
1 is the CID
498 is the LicenseID
8 is the Metric ID
The two long ID's are Application ID's in From and To columns
37370 is the ComputerID
363831016 is the OrgChecksum

As we know which license this is (498) and which computer it is (37370) we can browse these and check for any errors:

<your slm-server>/ Pages/License.aspx?id=498&list=LL
<your slm-server>/ app/#/computers/computers/37370/detail?list=CS

In this particular case, the license has been assigned to both the Datacenter but also the Computer itself which resides in the Datacenter, and after removing them and reassigning licenses the problem was gone.

Conclusion

The above steps may not automatically identify or fix all issues regarding Primary Key violations. Sometimes the problem requires in-depth troubleshooting to find out if it is programmatical and requires a fix to be resolved. If the problem can't be identified by following these steps in this article, please do contact Snow Support for assistance with the troubleshooting.

Was this helpful?

Support Hub

Product

Snow License Manager

Deployment type

On-premises;Service Provider Edition (SPE)

Visibility

Guest

URL Name

Violation-of-PRIMARY-KEY-constraint

Are you sure you want to cancel the case creation?

Case closed successfully

Action performed successfully

Upload Attachment

Maximum file size allowed is 3 MB.

File type not supported.

Supported file types:

Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files (.csv) Speadsheets (.xlsx, .xls)

Are you sure you want to close this case

Get Hotline support

Products	Region	Phone Numbers
FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield	North America *	+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America)
	Europe *	+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe)
	Japan *	+81 3-4540-5335 (select option 2)
	Australia *	+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia)
Usage Intelligence (formerly Revulytics) Compliance Intelligence	Please use the Case Portal to submit your support ticket or reach out to your Revenera contact.

Overview

Examples

Error during that Data Update Job:

Error during a Snow License Manager service:

Conclusion

Related Articles

Please wait...

Case id: 00001065