An error similar to the following might occur in the SASSearchService.log:

ERROR [e19adc36-4cff-11f1-b560-8c8474cd2ef0] com.sas.svcs.search.dao.irstudio.IRStudioQueryDao - IR Studio query Server not reachable :

com.teragram.jqclient.TgiException: null

When this error occurs, complete the following steps to troubleshoot the issue:

1. Ensure that all IRStudio servers are running by submitting the following commands:
   
   • proxy server on port 10661
   • pipeline server on port 1691
   • indexing server on port 10721
   • query server on port 10731
     
     

     cd ../Lev1/Applications/SASInformationRetrievalStudioforSAS/bin

      

     python information-retrieval-studio-client.py   --get-proxy-server-status

     python information-retrieval-studio-client.py   --start-proxy-server

      

     python information-retrieval-studio-client.py  --get-pipeline-server-status

     python information-retrieval-studio-client.py --start-pipeline-server

                                                        

     python information-retrieval-studio-client.py  --get-indexing-server-status

     python information-retrieval-studio-client.py  --start-indexing-server

      

     python information-retrieval-studio-client.py --get-query-server-status

     python information-retrieval-studio-client.py --start-query-server

2.  Do as follows if the Query server fails to start with an error in the query-server-errors.log:
   

   ERROR: Unable to load tk

   ERROR: The launch server could not be located

   ERROR: The TKELS extension could not be loaded.

   ERROR: Unable to load extension: (tkels)

   ERROR: The TKELS extension could not be loaded.

   1. Verify that the SLL is configured correctly.
   2. Edit the information-retrieval-studio.conf file and ensure that the following parameters are correct:
      
      Note: These are examples only. Use directory paths that are appropriate for your system. 
      

      tkpath=/opt/local/sas/sasca/sashome/SASFoundation/9.4/sasexe:/opt/local/sas/sasca/
      sashome/SASFoundation/9.4/utilities/bin

      auth-server-certificates-path=/opt/local/sas/sasca/sashome/SASSecurityCertificateFramework/
      1.1/cacerts/trustedcerts.pem
      
      Reference: Integrating Search Interface to SAS® Content 3.7    

3. If you need additional help, open a case with SAS Technical Support with the following information:
   • Provide the following files:
     • From the VA Server where IRStudio is deployed:

{SASConfig}/Lev1/Applications/SASInformationRetrievalStudioforSAS/logs

• • • • information-retrieval-studio-server.log
      • information-retrieval-studio-server-errors.log
      • query-server-errors.log
      • pipeline-server-errors.log
      • indexing-server-errors.log

{SASConfig}/Lev1/Applications/SASInformationRetrievalStudioforSAS/work

• • • • /information-retrieval-studio.conf
        
        
    • From the Midtier Server where Search Content is deployed:

{SASConfig}/Lev1/Applications/SASInformationRetrievalStudioforSAS/logs

• • • • information-retrieval-studio-server.log
      • information-retrieval-studio-server-errors.log
      • query-server-errors.log
      • pipeline-server-errors.log
      • indexing-server-errors.log

{SASConfig}/Lev1/Applications/SASInformationRetrievalStudioforSAS/work

• • • • /information-retrieval-studio.conf

<SASCONFIG>\Lev1\Web\Logs\SASServer12_1\SASSearchService.log 
(Note: If this log is large, SAS Tech Support needs only the last 5000 lines.)

• • • From the Midtier Server where Search Content is deployed:

<SASCONFIG>\Lev1\Web\Logs\SASServer12_1\SASSearchService.log  
(Note: If this log is large, SAS Tech Support needs only the last 5000 lines.)

• • Include a screenshot of the Search Interface to SAS Content - the Advanced tab in the SAS^® Management Console.