Kentico12: Workflow objects cannot be imported due to license limitations. License for feature 'Work

Tomasz Maruszak asked on April 16, 2020 12:40

Hi,

I am getting an error when trying to import my Workflow into another Kentico 12 (latest SP) environment.

My local dev license is Ultimate, and I want to export a workflow and then import into the staging environment which has Enterprise marketing solution license.

During importing it I get the following error:

Workflow objects cannot be imported due to license limitations. License for feature 'WorkflowVersioning' not found.

I tried clearing the workflow version history (Workflows > workflow name > Versions > Clear) and retrying the same export/import procedure again, but without luck.

How can I export a Workflow into my staging environment that has a lower version?

Correct Answer

Tomasz Maruszak answered on April 16, 2020 13:35

Juraj, investigating your first hint with the domain name, I ended up adjusting on the target site the Sites > (site name) > Edit > Site domain name:* to teacherportal-stg.rXXXc.com:443, initially there was only rXXXc.com. That solved the workflow import problem.

However, another issue is that the imported workflow is missing the whole Scopes section (Workflows > (workflow name) > Edit). I did check the Import all workflow scopes on All Objects > Global objects > Configuration > Workflows. Any ideas what am I missing?

When I did the same import procedure to our QA server, the Scopes are visible fine.

0 votesVote for this answer Unmark Correct answer

Recent Answers

Juraj Ondrus answered on April 16, 2020 12:53

The export package - is it a full site export or just a single object export package?

What is the domain name set when importing the site? Do you have a valid license available for that domain on the target instance? IT is strange since you said your local instance has Ultimate edition and the staging has EMS - this one is higher than Ultimate.
What is the domain name in the browser when importing? What license keys are listed in the Licenses app?

0 votesVote for this answer Mark as a Correct answer

Tomasz Maruszak answered on April 16, 2020 13:06 (last edited on April 16, 2020 13:06)

The export from local has been done using Sites > (site name) > Export Site > Selecting all the objects I need. I tried with pre-select all, but it didn't make any difference.

Target site has the following license (domain names + browser URL match): Image Text

Sorry, I had to put blanks for some parts for minimum privacy.

Any ideas? Do you need anything else?

0 votesVote for this answer Mark as a Correct answer

Juraj Ondrus answered on April 16, 2020 13:26

I am unable to reproduce the issue. Please, describe all the steps and export/import configuration in details.
I have a source instance with Ultimate (lower) edition. I have selected the Export site option and selected just the workflow I want to export. Then, I have imported the package into another instance with EMS (higher) edition and it is working fine.
I did the same with single object export. There must be something small I missing - please describe all the steps and setup you have.

I would also try setting up the same hash salt string and re-signing macros, just in case.

0 votesVote for this answer Mark as a Correct answer

Juraj Ondrus answered on April 16, 2020 13:42

I am glad you were able to import the workflow. Now, it looks like you did not had the same hash salt string set on the source and target instances which means there are some macro related errors in the Event log. If something is not working I would recommend checking the logs. This means, that you need to re-sign the macros.

0 votesVote for this answer Mark as a Correct answer

Tomasz Maruszak answered on April 16, 2020 14:00 (last edited on April 16, 2020 15:12)

Thanks Juraj, the re-sign helped restore the Scopes in the workflows. Indeed there were macro sign related errors in the event logs.

That said, with first site/DB installation the CMSHashStringSalt was set on the web.config and was set to same value across all environments. Anyways, that is all good now.

Thanks for your help here!

0 votesVote for this answer Mark as a Correct answer