Please, try increasing the time out and potentially allow SQL traffic on the firewall to flow freely. You can configure the time out period that Xtraction waits before timing out by adding the following entry to the web.config file in the Xtraction\Web\Server folder.
<httpRuntime executionTimeout="300" />
This needs to go somewhere inside the first <system.web> block. Usually it is best to add it straight after the first <system.web> tag, you just need to make sure it is not already there somewhere else. Note that 300 means 300 seconds. Then recycled IIS.
Also open ports TCP 1433 and UDP 1434 for SQL and possibly enable named pipes in SQL Configuration Manager. You can enable it under default MSSQLSERVER instance, located at "SQL Server Configuration Manager (Local) >> SQL Server Network Configuration >> Protocols for MSSQLSERVER", by changing its status from "Disabled" to "Enabled".
Other actions that could be done:
Check if there is any issue with network team as well;
Check if there is any firewall between the SQL server hosting the Xtraction and CA SDM (MDB) databases and the Xtraction application server;
Check if there is any firewall enabled at the Windows Operating System.
If after performing all these actions, if the problem persists, you might consider to upgrade to latest Xtraction 2018.3 release available at the moment at Ivanti link Xtraction Downloads & Instructions