As I have mentioned on the other thread, this has nothing to do with the connection. It has to do with the enumeration of the SQL Servers on the network. We will be publishing a new build soon (hopefully later in the week) that will prevent this error from happening. This is being cause by the installation tool that we use in conjunction with the MSI.

No. I'm a member of the SysAdmin server role on the server.







Yup, do it weekly (I'm a developer and a DBA where I work).

Could it be that you don't have enough rights to create database and tables?



Have you tried to manually create a database or table on this server with your credentials?

Edhy Rijo

But I'm assuming specifying the host name alone should suffice, since the server uses the standard SQL Server port (1433). The installer verifies and passes the SQL Server connection validation phase, but when it reaches the part where it actually creates the SF database, it fails, so something's amiss.

Yep, there isn't... you do that when you type the SQL Server Instance. Since I create a port for IP All, I put it in the line when I type the instance name, as in: tcp:MySLQServerInstance,1500 , where 1500 is what I would have put as a port fot the IP All.

Additionally, I have no firewall enabled.

As you can see in the following picture, I'm able to connect to this server via SSMS on the same workstation.

Standard host name:

You mentioned before that this was a remote server if so, are you using and IP or UNC name for the server?

Edhy Rijo

Nop--I'm using the standard SQL Server port (1433).