Not to say an expert, even though I had been working with SCOM for quite some time, error below was the first time I encountered during a recent engagement. Error below occurred when I tried to install a third SCOM management server which was totally unexpected, since the installation for the first and the second MS was done successfully without much hiccup.
Tried to repeat the installation again but the failure rate was 100%. Check out the internet and it seems that this might have something to do with the SQL connection time out, while the installation was trying to connect to the SCOM DB server to register the new Management Server.
One of the way you could possibly try is to extend the duration before the connection is timed out, and this requires updating the registry key of the server before the installation is re-started. Following will be the key that needs to be created.
Once created, reboot the server and try to reinstall the SCOM Management Server again. It should work this time (well at least it worked for me 
note: one thing to take note about before you reinstall the MS is that, you must remove that particular server from the management server list via the Operations Console. If not, you will not able to select the OpsMgr database during the MS installation.
