| |
Results |
|
Dim CM: DMSCHEDULE and DMDEPLOYSRV not connecting because of LDAP errors
|
Having set up SDP trace it was obvious from the logs why the deployment wasn't working. The SDP trace for the dmdeploysrv.exe process contained messages such as:
|
|
|
|
DimCM: Unable to log into DMCLI
|
Note: Similar errors will also be seen when the dmdeploysrv.exe process, etc., are attempting to start when the Listener is started.
|
|
|
|
Dim CM 14.1.0.3: DMDEPLOYSRV: 'Unable to connect to database' with 'Failed to get a new connection from pool'
|
Following a restart of the Dimensions listener deployment jobs started to stall with just the status "Submitted" when viewed in the Deployment tab of Web Client. When the SDP trace file for the dmdeploysrv.exe process was checked there was a message indicating that the process had failed to connect to the database to scan for jobs because it failed to get a new connection from the pool.
|
|
|
Deployment Guide
|
In Dimensions CM 12.1 you can perform deployment operations asynchronously in the background. The asynchronous processing is executed by a Dimensions CM server component called the deployment server ( dmdeploysrv.exe ). The following diagram shows the deployment server in the business logic tier in the Dimensions CM architecture:
|
|
|
|
Deployment Guide
|
In Dimensions CM 12.x and later you can perform deployment operations asynchronously in the background. The asynchronous processing is executed by a Dimensions CM server component called the deployment server ( dmdeploysrv.exe ). The following diagram shows the deployment server in the business logic tier in the Dimensions CM architecture:
|
|
|
|
Deployment Guide
|
The asynchronous processing is executed by a Dimensions CM server component called the deployment server ( dmdeploysrv.exe ). The following diagram shows the deployment server in the business logic tier in the Dimensions CM architecture:
|
|
|
