To resolve the issue, increase the socket timeout value:

1. Go to the IDF server host and open the CMD window.
2. Switch the path to the IDF server installation folder.
3. Run the following commands:

   idf_c.exe -action changesetting -name configuration.defaultSocketChannelTimeout -value 600000
   idf_c.exe -action changesetting -name configuration.agentSocketTimeoutOverride -value 600

The commands will request to restart the IDF server. After restarting IDF, the timeout value will be extended to 600 seconds for both client and server. For the configuration.defaultSocketChannelTimeout parameter, the value will be 600000 milliseconds.

If the issue is still present after following the steps above, try the following:

• Set the CPU usage level to High.

  This gives the scan more CPU power to finish. This is essential if a lot of the machines do the Recommendation Scan. Medium CPU usage level would not be enough for this kind of situation. Set it to high (which will use 100%) if there is no concern about it.

• Set the configuration.defaultSocketChannelTimeout parameter to a bigger value.

  Usually, the value should not be larger than 30 minutes (1,800 seconds or 1,800,000 mini-seconds) to prevent some unknown side effect. If it cannot finish in 30 minutes, the machine CPU power is insufficient to do the job.

• Separate the machines to be scanned into several groups in different time periods for scanning.

  If 100% CPU usage and max timeout are not enough, this is another way to reduce the failure rate. Separate them into groups for different times, so that the IDF server can finish each group in the given time. This is the last resort to solve the issue without upgrading the hardware (i.e. CPU power). Don't put the failure machines in one group since those machines would require more time to finish the scan.

• If all the aforementioned are not working or not good enough, then the best way to resolve the issue is to increase the IDF server's CPU power. If it's a VM, this should be easily done.