"Connection String cannot be parsed" if password contains semicolon

If the password in the connection string contains a semicolon the dashboard writes always a "Connection String cannot be parsed" message.

After I changed the password (removing the semicolon) the message got replaced by the SQL Server name.

Start by reproducing the dashboard failure with a SQL Server connection string whose password contains a semicolon, then trace the connection-string parsing path. The fix is complete when the dashboard accepts the password and displays the SQL Server name instead of "Connection String cannot be parsed".

Written by the indexing model from the issue text.