If you are installing and deploying patches for LiveCycle ES2 using the command line version of LiveCycle Configuration Manager (LCM) you may encounter an error similar to the following while deploying components:
com.adobe.livecycle.lcm.core.LCMException[ALC-LCM-030-200]: Failed to deploy component /opt/adobe/adobe_livecycle_es2/deploy/adobe-usermanager-dsc.jar. at com.adobe.livecycle.lcm.feature.deployment.DeployDSCs.deployDSCFiles(DeployDSCs.java:419) at com.adobe.livecycle.lcm.feature.deployment.DeployDSCs.deployDSCs(DeployDSCs.java:151) at com.adobe.livecycle.lcm.headless.HeadlessLCMImpl.deployDSCFilesLFS(HeadlessLCMImpl.java:285) at com.adobe.livecycle.lcm.cli.DeployLCComponentsCLI.executeCommandLineImpl(DeployLCComponentsCLI.java:96) at com.adobe.livecycle.lcm.cli.LCMCLI.execute(LCMCLI.java:298) at com.adobe.livecycle.lcm.cli.LCMCLI.main(LCMCLI.java:344)
and the LC logs may contain the following exception messages:
Component: com.adobe.PDFServices version: 126.96.36.199.20120202.1.312922 introduced a new service, it should not be patched
This problem occurs if the order of operations in LCM is incorrect. For example, if you run the deploy components step (DSCs), before configuring and deploying the new EARs. This can occur when using the command line LCM as you call each operation separately. It can also occur using the UI LCM if you run the tool twice in succession and select to deploy components in the 1st run before deploying the EARs in the 2nd run.
You should re-run the LCM steps ensuring to configure and deploy the EARs first, before deploying the components.