Blueprint - Analyst installation fails to list remote SQL servers in browse window

When installing the Blueprint Analyst, after selecting 'Install on an existing database' the browse window fails to list remote SQL servers, meaning that you cannot proceed any further with the installation.

Check the following:

1. That the server can connect to the remote SQL server using SQL Enterprise from the Analyst.

2. That the default TCP/IP communication port for SQL (1433) is being used.

If the default SQL port is not being used it may be necessary to set up an alias on the Blueprint Analyst machine to map the default SQL port to the custom port on the SQL server. Clients should use the cliconfg tool to insert an alias and map it to the custom port for the remote server. After completing this step clients should re-run the Pharos Blueprint installation program.