In situations where there are issues in configuring RStudio to use the TIBCO Enterprise Runtime for R (TERR) engine on a Windows machine, analyzing the application logs from RStudio may help you identify the root cause preventing the use of the TERR engine.
     
Some of the scenarios where RStudio application logs would help are listed below:

• The configured TERR path with RStudio does not load TERR engine
• The RStudio window simply freezes while loading the TERR path
• There are general difficulties with RStudio itself

Before start capturing the logs, first ensure a supported version of RStudio is being used for given TERR version. The version compatibility information can be found on the  System Requirement Page.  For example, for TERR 4.4 RStudio IDE version 1.0.153 must be used.
 
To capture the logs, open the following from RStudio IDE:

• Help menu > Diagnostics > Show Log Files

Upon the selection of the ‘Show Log Files’ option, the logs folder location will be opened in File Explorer. This is typically located in the logged in user's local AppData path, like: C:\Users\<username>\AppData\Local\RStudio-Desktop\log

In this folder, there will be two log files generated which can be opened to investigate any issues with the use of the TERR engine:  

 rdesktop.log  rsession-<username>.log

 

This article describes steps to generate RStudio application logs which will help to troubleshoot configuration problems between RStudio and TERR.

Doc: TERR system requirements:

• https://docs.tibco.com/pub/spotfire/general/sr/GUID-8CF7DFC6-6076-4FDD-898E-DB4E94DF23B3.html

External (RStudio Article):

• https://support.rstudio.com/hc/en-us/articles/200554756-RStudio-Application-Logs