This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.
TrueSight Synthetic Transaction Monitor with Micro Focus Silk Performer
BMC Synthetic Transaction Execution Adapter
TEA Agent 10.0, 10.1, 10.5, 10.7, 11.0, 11.3.01 Borland Silk Performer 16.0, 16.5, 16.6, 17.5, 18.0, 18.5
Getting the following error message in TrueSight Presentation Server Console and/or Truelog from the TEA Agent:
Execution Errors ( 1 ) LoadtestController: 3309 - The temp directory could not be cleared. ERRID -1 reached timeout.
This error typically indicates that the script you are running is not completing and this may be causing the browser to hang or a process to lock up that will not allow the perfBrowserHost_x86.exe to exit properly.
This error typically indicates that the script running is not completing and this may be causing the browser to hang or a process to lock up that will not allow the perfBrowserHost_x86.exe to exit properly.
Possible solutions for this issue include the following:
1. Running the script on anther TEA Agent on a different system may resolve the issue. This may be because there is anther script that is already running on the agent that is using a file that is needed by the new script and causing a conflict.
2. Add BrowserStop to the end of the script. This function will close all instances of the browser that were opened by the script while the script was running. If there are any instances of the browser still running on the next run of the script, then this issue could potentially happen.
3. Look at the Truelog of the transaction that ran right before receiving the LoadTestController error. To do this, locate the transaction in the Truesight Presentation Server Console and select the 3 dots next to the transaction and choose the option to download the log.
Review the Truelog to see if there are any issues. It may help to compare this log to another Truelog that was successful to see if there are any differences in the playbacks. Some things to look for may be if the failed Truelog timed out or if the failed Truelog ran slower than the successful Truelog. It may be necessary to modify the script via Silk Performer to prevent these delays from happening which could require custom coding.