By Michael Gonzalez - 3/8/2010
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.
|
By Trent L. Taylor - 3/8/2010
Michael,When are you getting this error? During the installation or when you go into Visual Studio?
|
By Michael Gonzalez - 3/9/2010
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.
|
By Ivan George Borges - 3/9/2010
Hi Michael.Things that I have tried before when I faced this situation were: - 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.
- 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
|
By Michael Gonzalez - 3/9/2010
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.
|
By Michael Gonzalez - 3/9/2010
The error occurs on this step:
|
By Michael Gonzalez - 3/9/2010
And I've tried 3 different SQL Server 2005 servers--all of them produce the same error.
|
By Edhy Rijo - 3/9/2010
Michael Gonzalez (03/09/2010)
...Also, there is no option in the installer to provide a port
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:
GSNSQL001,1234
|
By Michael Gonzalez - 3/9/2010
Nop--I'm using the standard SQL Server port (1433).
|
By Edhy Rijo - 3/9/2010
You mentioned before that this was a remote server if so, are you using and IP or UNC name for the server?
|
By Michael Gonzalez - 3/9/2010
Standard host name:
|
By Michael Gonzalez - 3/9/2010
As you can see in the following picture, I'm able to connect to this server via SSMS on the same workstation.
|
By Michael Gonzalez - 3/9/2010
Additionally, I have no firewall enabled.
|
By Ivan George Borges - 3/9/2010
Also, there is no option in the installer to provide a port 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.
|
By Michael Gonzalez - 3/9/2010
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.
|
By Edhy Rijo - 3/9/2010
Michael Gonzalez (03/09/2010)
... 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?
|
By Michael Gonzalez - 3/9/2010
Could it be that you don't have enough rights to create database and tables?
No. I'm a member of the SysAdmin server role on the server.
Have you tried to manually create a database or table on this server with your credentials?
Yup, do it weekly (I'm a developer and a DBA where I work).
|
By Trent L. Taylor - 3/10/2010
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.
|