For some reason, even though I specify the correct DB credentials/server name, SF fails to setup the DB on installation. It acts as though there's a problem connecting to the DB server, even though the DB server is accessible from the same machine via other applications (no problems whatsoever). I've attached a print screen of the error.



I'm evaluating this software and am not able to get too far because of this.

Ivan, I'm using a remote server, and I can get to that server via my other DB tools on the same PC. Also, there is no option in the installer to provide a port, although the default server name and credentials seem to pass validation in the installer, as it doesn't state an error was encountered during that phase of the installer process/workflow, only after, once it gets to the part where SF needs to install the SF database--that's where it fails.



I've attached a few print screens.

The error occurs on this step:

And I've tried 3 different SQL Server 2005 servers--all of them produce the same error.

Hi Michael,



If you are using a port other than the default for MS-SQL just add a comma and the port number next to the server name. Ex if you are using port 1234 the server name should look like this:

Edhy Rijo

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

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

Edhy Rijo

Standard host name:

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

Additionally, I have no firewall enabled.

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.

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.

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

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).

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.