QRS Database times out after 90 seconds

Services are all started, but QMC and HUB is not accessible, run Windows Commands To Retrieve Environment Information 

The log result is not showing port 80,443 in the list even the firewall has been turned off, 4242 is in TIME_WAIT status. 

In the log (reference: C:\ProgramData\Qlik\Sense\Log\Repository\Trace\<hostname>_System_Repository.txt). shows QRS Database timeout with the following error:
 

Fatal exception	A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond↵↓Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.↵↓Server did not respond within the specified timeout interval.

Environments:

Qlik Sense 3.x or higher

Since version 2.2, we made architectural changes to how the Qlik Sense Repository works and fixed a bug which exacerbates this change. In prior builds, the Repository Database was read from disk. Additionally, the cleanup / maintenance mechanism which was intended to work was non functional. In 2.2, the Repository Database is loaded into memory upon initialization to gain a performance edge.

As a consequence of these two changes, sometimes environment experience issues wherein the Repository Service times out upon initialization due a build up of stale data in the database. The clean-up script mentioned earlier will remedy this issue.

There are still a small subset of customers who simply have large amounts of information in their databases where 90 seconds is not sufficient and the above resolution should resolve their issues.

Follow below steps to troubleshoot:

*** check if anti-virus scanning exclusions Qlik sense file and folders per article:
            https://support.qlik.com/articles/000031189

• For synchronized Persistence these folders should be excluded from Anti-Virus scanning:
• C:\ProgramData\Qlik\
• C:\Program Files\Qlik\
  • Or alternative installation path of Qlik Sense
• C:\Program Files\Common Files\Qlik
• The application directory
• For Shared Persistence these folders should be excluded from Anti-Virus scanning:
• C:\ProgramData\Qlik\
• C:\Program Files\Qlik\
  • Or alternative installation path of Qlik Sense
• C:\Program Files\Common Files\Qlik
• The shared folder used by Qlik Sense to store applications, application contents, extensions,...
• If the PostgreSQL database is installed on another machine please refer to the PostgreSQL manual for more details https://wiki.postgresql.org/wiki/Running_%26_Installing_PostgreSQL_On_Native_Windows
• Ports to be excluded from Anti-Virus Monitoring / Blocking

*** Run the Cleanup Database script first by following  Database Cleanup Script For Qlik Sense Enterprise 2.x And 3.x
*** Run Recursive Cleanup Script for June 2017 and above Article: https://support.qlik.com/articles/000042390
If the issue persists after running the Cleanup Database script, do the following on every node:

1. Stop all Qlik Sense services
2. Open Notepad and Run as Administrator (Start > notepad > Right Click > Run as Administrator)
3. In Notepad, go to File > open > go to C:\Program Files\Qlik\Sense\Repository ( this is the default location, this might be different if Qlik Sense was installed to a customized path)
   1. Within the open window make sure to have "all files" selected so that you can see non .TXT files
4. Open Repository.exe.config
5. Find the row with this value:  <add key="PostgresCommandTimeout" value="90" />
6. Change the value from "90" to to a higher number that works for the specific environment. For example double the value until the issue is resolved.
   NOTE:The value 0 means unlimited and effectively disabled the timeout function. This should never be applied in a production environment.
7. Save the file
8. Start all Qlik Sense Services.