Global Search Internal connection fatal error

Hello, colleagues.

 

Im using swagger api on 

*:81/api/index.html 

to configure global search services.

 

My actions:

  • Launch all required docker containers according with documentation
  • Registered a 'my_precious' site name with the parameters 

    {"databaseType": "mssql", "databaseConnectionString": "Server=DB_SERVER_IP; Database=DATABASE; User Id=USERNAME; Password=PASSWORD; Connection Timeout=10; TrustServerCertificate=true"}
  • Created an index with the parameters 

    {"templateName": "ngram_3.json"}

     

Configured the system settings according to the academy instructions:

  • Executed an SQL query to activate the global search feature
  • Filled three system settings with url's :81, :82, and :83/indexname

     

Port 1433 (SQL) on the CRM database server is open.

 

When checking the status of the global search using 

*:81/sites/my_precious/search/state

, I receive the following error: 

Failed to check state for the 'my_precious' site: Internal connection fatal error.

I have checked the logs of all Docker containers related to the global search and haven't found anything similar to this error.

What does this error indicate, and where can I find a more detailed description of it?

 

And no, global search isn't working.

Like 0

Like

1 comments

Hello

1. I suggest performing a check using the Swagger interface:

  1. Follow this link:

    http://GS_server_address:81/api/index.html
     

Where GS_server_address is the address of the server hosting the global search services. Locate the command /sites/my_site_name/search/state

Essentially, this is the same check but through a more user-friendly interface.
 

  1. 2. Additionally, I noticed that the connection string uses PostgreSQL server flags (Server/Database). I suggest trying the following format, which is more typical for MSSQL:

 

"Data Source=server\\Instance;Initial Catalog=DB;User ID=*****;Password=*****"  

 

or

 

"Data Source=ip;Initial Catalog=DB;User ID=*****;Password=*****" 

 


  1. 3. I also recommend verifying that the database server and the database itself support external connections. You can refer to this guide:

    https://www.apesoftware.com/calibration-control/help/sql-remote-connections
Show all comments