This can happen for multiple reasons

• The SF installer tries to download the latest version of SF but the server does not have access to microsoft.com
• system requirements are not met. SF installs will not complete if even one system requirement is not met
• computer performance. The SF install is very load intensive and if the computer does not have enough resources, it will fail
• anti-virus or network security
• outdated computer image that is most likely missing a required Microsoft update

• check that the Service fabric machine can connect to Microsoft.com
• Verify the system requirements
• turn off all non-essential services on the computer, including the Solver services. These can be turned on after SF is installed. 
• We have seen that anti-virus will sometimes block certain SF .dll files. Ensure that the antivirus allows for all SF files
• In rare cases, we have seen that older computer images are not compatible with SF, even though it has been updated to a supported version. In these cases, a new server based off a "fresh" operating system install is needed. 
  • To find out when the operating system was installed, you can type in systeminfo into command prompt. 

In this case, if you are following the progress window, you will see that the cluster has successfully been installed, but it fails during the install of the application.

The causes here are similar to the above, but are typically more related to computer performance than anything else. 

• Turn off all non-essential services on the computer, including the Solver services. These can be turned on after SF is installed. 

There are typically two causes for this error

• The SQL server where the SolverDW databases are has multiple instances
• You are using a windows name in the prepareSF step, but this name has not been properly propagated throughout the organization's internal network

• If the SQL server where the SolverDW databases are getting installed has multiple instances, make sure that SQL Server Browser Services is enabled
• In the prepareSF step, if you typed in the windows name of the SQL server, use the IP address of this SQL server instead

• On the SF server, make sure that the Service Fabric service is running from the Services menu
• Ensure that ports 19081 and 31313 are open between the Web Server and the Services Server
• Open SF explorer (localhost:19081) in your web browser and make sure that all application are health
• On the SQL server, verify the settings are correct in the Solver_Repository.MasterSettings table as shown below.

  The blurred out section should show your service fabric server name.

  
• The credentials used to create the SF connection during install may have expired. Navigate to (http://localhost:19081/SolverFabricConnection/DatabaseConnectionService/connectionStrings/jobsscheduler) on the SF server. This will give you the connection information, including the SQL account being referenced which can help identify whether the credentials have expired or not. 

• Whitelist marketplace.app.solverglobal.com