@HDAL I had a similar issue while upgrading to 23R2.2 with components evelog and sklmgt that were missing in the solutionset.yaml file. I have added those components as true, committed the changes in the release update branch and then I was able to order the environment. 

Thank you @Marcel.Ausan 
Just for my understanding, did you decide this “on your own” or were advised by IFS to do so ? ;-)

@HDAL  you should raise a ticket with IFS to make sure nothing is wrong with your solution set. Be persistent that they should check. In theory you should never touch the solutionset as it is “IFS” generated. So just run it with support and they will fix it for you. 

@Marcel.Ausan  is right you could do it yourself but its not advisable as you never know what history your solutionset has etc.  

So with your beloved support it should be sorted out!

Thank You @kvbe,
Don’t worry, a case as been opened in // on IFS Support Portal too ;-)

@kvbe in my case Event Log (evelog) and Skill Management (sklmgt) were new components introduced in 23R2 and my client has the Service/Asset solution set, so those components should have been set to true.

Anyways, my understanding is that even if you set something to true in solutionset.yaml, it doesn’t mean the component is activated if it’s not part of the license. In our case, both evelog and sklmgt were part of the licensed components and come in very handy since we started looking at Request Mgmt functionality.

The true/false values should match between customer-baseline and customer-solution. I had to set sklmgt to false to get my particular sanity build going.

This is described in the ALE Documentation, under Sanity Builds, “Things to avoid”:

https://docs.ifs.com/techdocs/ale/020_lifecycle/080_release_update_studio/040_after_applying_release_update_to_baseline/010_release_update_with_customization/060_sanity_build/#things_to_avoid