cancel
Showing results for 
Search instead for 
Did you mean: 

Enterprise License issue moving from v5.2 to v7.2

corvo
Champ in-the-making
Champ in-the-making

Hi all,

we're facing a weird issue moving from Alfresco 5.2 to Alfresco 7.2. We have an enterprise license which expires in 6 months. If we use it with a freshly installed Alfresco 7.2, that is new DB and empty contentstore (the one under /alf_data/), then it is correctly read, the expiration date is shown and the file is renamed to 'something'.installed. 

If instead we use the license once the old contentstore and DB from 5.2 have been restored, following the migration recipe found here https://docs.alfresco.com/content-services/7.2/upgrade/, then Alfresco always returns these lines:

2023-01-12 11:46:23,743 WARN [repo.transaction.TransactionServiceImpl] [main] setAllowWrite:false. Applying veto on write operations: {http://www.alfresco.org/model/application/1.0}LicenseComponent
2023-01-12 11:46:23,744 ERROR [service.descriptor.DescriptorService] [main] Alfresco license: Failed to verify license - Invalid License!
2023-01-12 11:46:23,833 ERROR [service.descriptor.DescriptorService] [main] There is no license in the content store or it can't be reached.
2023-01-12 11:46:23,833 ERROR [service.descriptor.DescriptorService] [main] There is no license certificate installed for Enterprise - v7.2.
2023-01-12 11:46:23,833 ERROR [service.descriptor.DescriptorService] [main] Alfresco license: Restricted Alfresco Repository to read-only capability

The license is copied exactly in the same path, the cofiguration is exactly the same. The "only" difference is a DB and contentstore coming from Alfresco 5.2.

Hint: when using an empty, fresh contentstore and the old DB from 5.2, the license is correctly read. Of course Alfresco doesn't start because of the incoherence between data and db, but at least the license is deemed good. On the other hand, when using an empty, fresh DB and the old contentstore, then the problem shows up. Like there's something stored/ciphered in the contentstore with the old 5.2 license that is not recognised by the new one.

Does anyone have a clue on why this is happening?

Thanks in advance!

1 REPLY 1

openpj
Elite Collaborator
Elite Collaborator

For each specific major version of Alfresco (for example 6.0, 6.1, 7.0, 7.2) you need to raise a ticket in order to request a new license for your project.

In this case you have to raise a ticket asking for a new license for ACS 7.2, typically in one or two hours you should receive your license to use in your upgraded installation.

Hope this helps.