After a fresh remote-deployment install, all components show as installed and active in the environment, but the solutionset.yaml being used still lists many components as inactive/false — and subsequent Service Update installations then throw errors that may be related. Is this expected?

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

No — check whether the very first distribution/base build was actually installed as the first step after standing up the environment, before anything else. Skipping or missing that initial base distribution step (an easy gap since it isn't always called out prominently in the installation documentation) is a known cause of the installed-components-vs-solutionset.yaml mismatch you're seeing, and can cascade into errors on later SU installations that assume that base state is consistent. Installing the correct starting distribution first, in the right order, resolves both symptoms together.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Developer Studio, deployment, and upgrades questions