Failure of executions in SilkCentral Test Manager because the virtual execution server cannot be connected in time

0 Likes

Problem:

Failure of executions in SilkCentral Test Manager because the virtual execution server cannot be connected in time

Resolution:

Up until SilkCentral 2008 R2 configurations were captured statefull on Lab Manager side, which means that the Os is captured and restored in a running state. When such a configuration is deployed again, the memory containing the running windows is loaded and the VM runs in a short time.

To improve performance of checkout/deployment configurations are now captured stateless, which means the OS in VM is shut down and needs to be re-started each time the configuration gets deployed.

Due to this change the timing of the deployment changes. This may result in a stateless captured configuration failing to provide the execution server connection in time (because the OS has to be turned-on and started- up). Thus, execution may fail on SCTM side, if the execution server cannot be connected in time.

This can be avoided by increasing the value in the following setting in the SCCAppServerBootConf.xml file:


120

Increasing this value will support statefull as well as stateless capturing , but in error situations more time is consumed until the error is raised. A restart of the SilkCentral services is required to ensure the change to the SCCAppServerBootConf.xml file is implemented.

Old KB# 25181
Comment List
Anonymous
Related Discussions
Recommended