Page tree
Skip to end of metadata
Go to start of metadata

Category:Deployment failed

Problem

PrerequisiteViolated - Dependencies could not be resolved or there are cyclic dependencies

Keywords

  • PrerequisiteViolated
  • Unresolved Dependency
  • Dependencies could not be resolved
  • Cyclic dependencies
  • Deploy time dependency
  • [ERROR CODE DPL.DC.3437], 3437
  • [ERROR CODE DPL.DC.3033], DC.3033, 3033, DPL.DC.3033
  • [ERROR CODE DPL.DC.3034], DC.3034, 3034,

Symptoms

During deployment, a similar error to one of the following occurs:

[ERROR CODE DPL.DC.3033] An unresolved dependencies error occurred while sorting the deployment batch items regarding the dependencies.[ERROR CODE DPL.DC.3034] A cyclic dependencies error occurred while sorting the deployment batch items regarding the dependencies.UnresolvedDependenciesException

Unresolved dependencies means that at least one component in the batch depends on components that are not present in neither AS Java nor the current deployment batch.

Cyclic dependencies means that a cyclic dependency is being introduced with the current deployment batch. A cyclic dependency is not acceptable and the batch is rejected.

Solution

The missing or cyclic dependencies are usually caused by the fact that:

  • some SDAs that are missing in the batch. For example, the DVD does not contain all required SDAs.
  • all the SDAs are present but some of them have incorrect versions and contain dependencies that have been removed in the newer versions.

The error may have occurred because there was not enough disk space on the server. Check for the following message in the log files listed bellow:

IOException: There is not enough space on the disk
    • defaultTrace
    • /usr/sap/<SID>/<INSTANCE>/work/deploy.*.trc

In this case, see: There is not enough space on the disk

  • Deployment dependencies issues may be faced also in the following scenario: You have an application A that depends on application B, but want the availability of B to be optional. 
    In this case, see follow this page .

Sample Logs

#1.5 #001279A75FEF00800000002B0000105C000411DED183C2FF#1145548602080#/Syste m/Server/Deployment##com.sap.engine.services.
tc~bl~deploy_controller#Administrator#11####23a82c70d08611dacd2f001279a7
5fef#3 Telnet unknown Thu Apr 20 18:45:26 EEST
2006##0#0#Error#1#/System/Server/Deployment#Plain###An unresolved
dependencies error occurred while sorting the deployment batch items
regarding the dependencies.; nested exception is:
java.rmi.RemoteException: class com.sap.engine.services.dc.cm.
deploy.sdu_deps_resolver.UnresolvedDependenciesException:

1. Component: name: 'tc~esi~esp~api', vendor: 'sap.com', location: 'SAP
AG', version: '7.1000.20060419175049.0000', software type:
'primary-interface', dependencies: '[name: 'tc~esi~esp~lib', vendor:
'sap.com']'
Unresolved dependency:
name: 'tc~esi~esp~lib', vendor: 'sap.com'

Reason : An unresolved dependencies error occurred while sorting the
deployment batch items regarding the dependencies.; nested exception is:

java.rmi.RemoteException: class com.sap.engine.services.dc.cm.
deploy.sdu_deps_resolver.UnresolvedDependenciesException:

1. Component: name: 'tc~esi~esp~api', vendor: 'sap.com', location: 'SAP
AG', version: '7.1000.20060419175049.0000', software type:
'primary-interface', dependencies: '[name: 'tc~esi~esp~lib', vendor:
'sap.com']'
Unresolved dependency:
name: 'tc~esi~esp~lib', vendor: 'sap.com'

Common unresolved dependency errors

  • No labels