Hi Nokuthula,
This can be many things. Here is a list from our troubleshooting guide:
Database connectivity
The Test connection to proceed button within the installer checks the following:
- If the database exists:
- That it can be connected to.
- That the account has the rights to read, write and edit the database.
- If the database does not exist:
- That the account has the right to create the database.
If these requirements cannot be met, the installation will stop.
There are a number of checks that can be performed when a connection cannot be made to a SQL Server over the LAN:
- Verify Network Connectivity – Ensure that all relevant devices are connected to the same network and are able to communicate.
- SQL Credentials – Verify the SQL credentials and that the user has appropriate permissions on the SQL Server.
- Firewall – Check that the firewalls on the servers themselves or within the network are not preventing communication.
- SQL Browser Service – Ensure the SQL Browser Service on the SQL Server is enabled to allow for a SQL Instance to be found. For SQL Server Express this service is typically disabled by default.
- Enabling TCP/IP Connectivity – Where remote connectivity is required for SQL, check that TCP/IP connectivity is enabled for the SQL Instance. Microsoft provide articles specific to each version of SQL that provide instructions to Enable the TCP/IP Network Protocol for SQL Server.
If when running the installer the installation process fails with database errors, see below, then test that the Web Server has a SQL connectivity to the database. This could be due to any of the reasons potentially listed above.
Another potential reason for failure is that the account used to create the databases within the installer has insufficient privileges to create the databases.
Finally, if the installation is a re-installation after a removal of the software. Then if the same database names have been used, the original databases should be backed up and dropped before re-installing.