TS Synthetic - Best practices for configuring systems to run SilkTest scripts on a TEA Agent

Version 1
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    Micro Focus Silk Test for TrueSight Synthetic Monitor


    BMC Synthetic Transaction Execution Adapter


    Silk Test 10.0, 10.1, 10.5, 10.7, 11.0, 11.3.01 TEA Agent 10.0, 10.1, 10.5, 10.7, 11.0, 11.3.01


    If the system is not configured correctly, then you may see the following errors on your Synthetic Transaction in the TrueSight Presentation Server Console or in your Synthetic Truelog:

    StInitSession(GUI-Level Testing Replay: 10 - Virtual user information, Silk Test Connection timeout reached.)
    StInitSession(GUI-Level Testing Replay: 3 - Communication failed. The application has terminated, StInitSession) 
    LoadtestController: 3513 - Command <execute transaction> is currently not possible. Start load test controller first.


    In order for a Silk Test script to run correctly on a TEA Agent, the system must be properly configured.  Below are some best practices for configuring your TEA Agent/Silk Test Open Agent system:

    1.  The TEA Agent must run as a process on the same server as the Silk Test Open Agent.  If the TEA Agent does not run as a process, then the Silk Test script may not have enough permissions to run correctly.

    2.  Please follow all the directions in the following 2 links to ensure that the system is configured correctly:


    3.  Confirm that these registry settings on the TEA Agent system are blank:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon LegalNoticeCaption and LegalNoticeText keys


    4.  The server that the TEA Agent is running on must be a server edition running an OS such as Windows 2008 R2 or Windows Server 2012 R2.

    5.  Confirm the following settings are set:

    • Local Computer Policy > Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security > Set client encryption level. Enable and set to low.
    • In same folder Require user authentication for remote connections by using network level authentication > set to disable. 


    Article Number:


    Article Type:


      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles