Not able to delete or create licensekey after migrating kentico database to new server

What is the error that you are getting? Seems like something is mising here

do you have access to to the SQL Server ?

Chances are you dont have the correct permissions on your database with the user you are using in your connection string. Make that user membership of that database as "db_owner" and see if that helps.

Dave

Hello Positive Purchasing,

thanks for the response, the connection is established and the membership "db_owner" is also set.

Hello Chetan Sharma, plz have a look again.

For clearification: Our workfow was like: 1. creating a full DB backup 1. restored the database from the full backup on our new server

So far content editing is no problem (create, delete pages - update, change content eg.) so connection could not be the problem.

any futher suggestion

kind regards

stefan

Hi,

Could you try using the export/import feature to insert the new (and current ones again) perhaps something got messed up and reinserting them will fix this.

Otherwise if this is the only problem in your installation you could, although usually not advised, just delete them directly using SQL. Licenses are located in the "[dbo].[CMS_LicenseKey]" table.

David

Check your license table in your db and see if there is a primary key. Usually when you see messages like that, it is related to primary keys not being set, just from what I have seen. Otherwise, I would check and make sure that all of the files were brought over and they were copied from the correct directory.

I think you should write to support@kentico.com. This should not happen. Seems like there is some underlying problem.

A silly question. What is the error you are getting in the event log also.

Was your migration successful? Was there any accidental change made to this file?

Thank you all for your time and your help.

Finally i was able to fix this problem through the kentico support.

The problem was the DB Server Sorting!

Although the database itself had the right sorting configuration the server had not. I changed the collation of the server to case sensitive (CI) and this fixed it all.