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.

Michael,

When are you getting this error?  During the installation or when you go into Visual Studio?

Both when I first install the S/W and after, via VS.NET. It's very strange. I've verified the correct server name and credentials were provided--no luck. It timeouts during the install, and via VS.NET, it gives a login failure, or some other error (most likely due to the fact that the installer never had the chance of creating the SF database). I use SSMS and Aqua Data studio on the same PC on which I installed SF, and those DB connections work fine.

Hi Michael.

Things that I have tried before when I faced this situation were:

1. supply a TCP port on the SQL connection. I usually go to the SQL Connection Configuration Manager, on the SQL Server Network Configuration, I get the properties of the TCP/IP protocol (which should be "Enabled", of course). On the Properties, I go to IP Addresses and for the "IP All" I enter a TCP Port, like 1500. Then, on connection I type "tcp:MyServer\SQLExpress,1500". On this example, I am connecting to an Express version.
2. Other thing it has worked for me, was to add the SQL.EXE application as an exception into the server Firewall.

So, just some ideas to try.

Cheers.

sql.exe

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