Known issues in TeamForge connector 2.2

The following is a known issue in TeamForge connector 2.2. It has a workaround.

Artifact ID	Description
artf7861	When the TeamForge connector (CCF Master) server is installed as a Windows service, stopping and restarting the service causes this error: "Windows could not stop the TeamForge Connector Server on Local Computer" Error 1053: The service did not respond to the start ot control request in a timely fashion. You will see this error if you don't have at least one RMD per direction that is "resumed" when the cores are in "started" status. Workaround: Before stopping the service, make sure that at least one RMD per direction is in "resumed" status. OR After the above error — at which time the service is disabled — reopen the service window and kill the disabled service. Then install the service again and start it.

Artifact ID

Description

artf7861

When the TeamForge connector (CCF Master) server is installed as a Windows service, stopping and restarting the service causes this error:

"Windows could not stop the TeamForge Connector Server on Local Computer"
 Error 1053: The service did not respond to the start ot control request in a timely fashion.

You will see this error if you don't have at least one RMD per direction that is "resumed" when the cores are in "started" status.

Workaround: Before stopping the service, make sure that at least one RMD per direction is in "resumed" status.

After the above error — at which time the service is disabled — reopen the service window and kill the disabled service. Then install the service again and start it.