Errors related to SQL Server instance during AI Center standalone installation.
Issue Description:
While installing AI Center Standalone one or more issues related to SQL Server instance may be encountered:
- "ERROR [HYT00] [Microsoft][ODBC Driver 17 for SQL Server] Login timeout expired
- Document Understanding FullTextSearch Failed Exception calling "Open" with "0" argument(s): "ERROR [HYT00] [Microsoft][ODBC Driver 17 for SQL Server] Login timeout expired
- aicenter Database Creation : Failed :- Exception calling "Open" with "0" argument(s): "A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 35 - An internal exception was caught)"
Document Understanding requires the SQL Server to have the Full-Text Search component of the SQL Server Database Engine, which is not always installed by default. Please check this guide on how to add/install features on SQL server. Also check Editions And Supported Features Of SQL Server 2017 for all the components that can be added to the SQL Server, which also includes also Full-Text Search.
In the document AI Center Installation Guide before performing the last step ( step 4.4) ensure to connect to Identity Server and retrieve an installation token. Then copy this token and paste it in a placeholder in step 3.2. (in the cluster_config.json file).
Resolution:
- Check connectivity to SQL server using Telnet.
- Check resolve.conf to see if there is a DNS server. In case yes, then try to resolve Orchestrator and database hostname with DNS server.
- If the above fails then it is suggested that the user checks with the IT team and add hostname and Orchestrator entries in the database.
- Add Orchestrator server and Database server entries in the DNS server.
After performing the above checks, the installation should no longer fail with SQL Server instance errors.
In case further errors related to the application being out of sync or in a degraded state are thrown, then check the outcome of the below command and see if a response is obtained:
- dig +noedns @dnsIP domainname
There is no need to set a different DNS for Orchestrator. It is required to set up DNS for Hostname of the servers, so if for example https://rpa is used as URL for Orchestrator then it should be possible to resolve this URL from AI Center server as shown below :
In case the Orchestrator is on another domain and there is no trust relationship, either install Orchestrator and AI Center on the same machine or install Automation Suite.
To be sure of the Resources needed for AI Center, Action Center, DU and Orchestrator:
Use the following calculator to get the resources: Capacity Planning.
Note: The below specs are prescribed if all the products in Automation Suite are used and desired to be used all at a time:
- CPU: 32
- RAM: 64GB
- Storage: Total 1.516TB
- Etcd: 16GB
- Cluster: 256GB
- Datadisk: 2TB
If the environment has insufficient data disk space then un-deploy other products (like Automation Hub, Ops, Test Manager, Insights) to avoid load on the server.
Installation should proceed successfully after the above points are taken care of. If post-installation issues are thrown while importing code developed from their local to the virtual machine and the error states ‘Object reference not set to an instance of the object’ it could be due to forward compatibility issue. Refer to the below link and ensure the correct versions are installed and it should function smoothly: