Using Software Delivery › Use of SD Agent Bridge › Known Issues with SD Agent Bridge

Known Issues with SD Agent Bridge

Currently, the following issues have been identified for SD Agent Bridge.

Active Job Check

The Active Job Check on the Unicenter Software Delivery legacy agent might fail in the following situation:

1. During package deployment the option, Jobs will be triggered by scalability server, is not selected.
2. And once the job container is created and is in the Active state, you select either the Active Job Check option from the DSM Explorer or run sdacmd jobcheck on the agent machine.

The result is that the status of the job remains in the Active state.

The workaround for this problem is to run sdjexec.exe on a Unicenter Software Delivery 4.0 agent machine, or asminst on a Unicenter Software Delivery 3.x or 2.0 agent machine. The status of the job will then be displayed as successful in the DSM Explorer.

Windows Mobile 5.0 Devices

When a Unicenter Asset Management 4.0 SP1 C2 agent is installed first, followed by a Unicenter Software Delivery 4.0 SP1 C3 agent, on a Windows Mobile 5.0 device pointing to Agent Bridge, the version number of the Unicenter Asset Management agent shown in the DSM Explorer might be incorrect.

Also, when a Unicenter Software Delivery 4.0 SP1 C3 agent is installed first, followed by a Unicenter Asset Management 4.0 SP1 C2 agent, on a Windows Mobile 5.0 device pointing to Agent Bridge, the Unicenter Asset Management 4.0 SP1 C2 agent might not get reported.