Error when trying to create a new database project

I've installed VSTS 2005 Trial System, SQL Server 2005 Enterprise Evaluation System and Team Edition for Database Professionals CTP7. They are running on a fully patched virtual machine with 2000 Pro OS.

I'm running as an Administrator and can create databases from both SQL Management Studio and from within Visual Studio.

When I try to create a new database project I get the error:

"An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)"

Remote connections are allowed, and anyway the server is not remote as it all has to run on the same machine (as I understand it).

Any help or suggestions much appreciated.



Answer this question

Error when trying to create a new database project

  • TinSoldier

  • kageg

    Mairead,

    I was afraid you would say that. I guess my choices now are to wait until you get it fixed to use SQL Express, or upgrade my box to 2003 Server and then install SQL Enterprise Edition.


  • Dr. YSG

    Hi

    The version that was at SQLPass was indeed CTP7 which does not run with SQLExpress. The release post CTP7 will be able to run with CTP7

    mairead


  • Dave9999

    hi there. I have looked at all you suggestions above but I sill cant create a database project.

    I started using the new CTP for Microsoft Visual Studio for Database
    proffessionals and it's great. however I decided to do a walkthrough on
    a web cast and follow the steps.
    When I go and open a new instance of Visual Studio and select add new
    project > sql2005 database project I get the following error:

    ---------------------------
    Microsoft Visual Studio
    ---------------------------
    An error has occurred while establishing a connection to the server.
    When connecting to SQL Server 2005, this failure may be caused by the
    fact that under the default settings SQL Server does not allow remote
    connections. (provider: SQL Network Interfaces, error: 26 - Error
    Locating Server/Instance Specified)
    ---------------------------
    OK
    ---------------------------

    All my SQL server allow remote connections.

    I have tried every possible combination of server instande in my tools
    options > database tools > data connections AND design time
    validation database.

    I have looked at all the config TCP settings and cant figure out what
    is going on. I allow TCP and named pipes.

    I have been connecting to any number of my databases for 8 months with
    no problem and visual studio works fine in all other areas.

    Can any one help

    thanks
    RuSs

  • Krutika

    Send me a mail when you get the chance and we can walkthrough this via LiveMeeting to get you unblocked email address maireado@microsoft.com


  • vbjunkie

    I too am unable to create a database project. I had been running VS2005 Enterprise. I upgraded it to the VSTS and then installed CTP7. When trying to create a DB Project it tells me that I must either have Developer or Enterprise editions of SQL Server. Yet at Pass last week I definitely saw projects running on SQL Server Express.

    I had SQL Server Standard running on my machine as well as Express but the Express wasn't the default instance. So I uninstalled both and reinstalled Express and I still can't get it to work. I ran profiler and found the place where it fails.

    SELECT CONVERT(bit, CASE SERVERPROPERTY(N'EngineEdition') WHEN 3 THEN 1 ELSE 0 END)

    Why does it matter what version you have installed on your local machine This doesn't make sense to me. Also, Both Gert and Cameron stated we would be able to run it with Express. Obviously what I downloaded in CTP7 doesn't allow it. Does the version handed out on the CD at PASS enable the use of Express We have a site license for Enterprise (won't install on XP) but I don't have a developer edition handy.

    Right now I'm very frustrated. I'm almost 10 hours into this and still can't get it to work.


  • Evan Mulawski

    Kevin

    Was the information that Henry provided useful in resolving your issue

    mairead


  • snakeoooooo

    Short answer is no.

    I've gone through and checked each of the suggestions (where they apply to my setup) and found everything is set correctly:

    • SQL Browser is running and active
    • Remote connections using Named Pipes or TCP/IP are enabled according to the SQL Server 2005 Surface Area Configuration Manager.
    • Named Pipes and TCP/IP protocols are both enabled in both the Network Configuartion and the Client Configuration according to the SQL Server 2005 Configuration Manager.
    • Rebooted many times.

    From Henry's Lastly list:

    • Server name was typed incorrectlyServer name was typed incorrectly - I've never been asked for a server name. I click File / New / Project and then select Database Projects / Microsoft SQL Server. From the Templates I select SQL Server 2005. It goes away for short while and then comes up with the error.
    • The SQL Server service on the server is not running. -It is running, I can connect to it from Visual Studio, SQL Management Studio, SQLCMD etc.

    • The TCP/IP port for the Database Engine instance is blocked by a firewall - There is no firewall involved (its Win 2K Pro not XP) and I can explicitly connect via TCP/IP from other apps such as SQLCMD -S 192.168.1.171,1433 The connection method is reported by the SQL Profiler.

    • The SQL Server Browser service is running but UDP port 1434 is blocked by a firewall. - Again there is no firewall involved. A port scan utility shows UDP port 1434 as open. Is there any way I can independently prove that SQL Browser is responding on that port

    • The client and server are not configured to use the same network protocol. - Both client and server have Named Pipes and TCP/IP protocols enabled.

    • The network cannot resolve the server name to an IP address. This can be tested using the PING program - PING'ing the name does resolve to the correct IP address

    • The network cannot connect using the IP address. This can be tested using the PING program. - Again PING works to both IP address and name.

    Thanks again for all the suggestions, but currently I've run out ideas..........


  • GMan5309

    Thanks for the suggestions.

    The first link applies when installing SQL 2000 (or v7) after SQL 2005. This is not the case. Only SQL 2005 is installed. I have also checked the registry permissions and they are correctly set for the SqlBrowser user.

    The second link refers to how to enable remote connections. As I said, remote connections are enabled even though no remote connection is taking place as its all on the same machine!


  • woodland30033

    This problem happens on single machine with this remote connection error.

    Here is some more steps you may want to try after the steps in the links that I provided:

    • You might have named pipe or tcp enabled and connect to a named instance, but SQL Browser service was not started or enabled. To enable browser, First, Use net start or go to sql configuration manager(SSCM), check whether sqlbrowser service is running, if not, start it; Secondly,You still need to make sure SqlBrowser is active. Go to SSCM, click properties of sqlbrowser service -> Advanced-> Active “Yes” or “No”, if sqlbrowser is running but is not active, the service would not serve you correct pipe name and Tcp port info on which your connection depends
    • Cause: Server not configured for remote connections.

    The error is telling us that your server has not been configured to allow remote connections. If your SQL Server has not been configured to allow remote connections, then configure your SQL Server.

    Fix:

    SQL Server 2000: Open the SQL Server Client Network Utility. On the General tab enable the protocols you need to use. Typically this will be 'TCP/IP' and possibly 'Named Pipes'.

    SQL Server 2005 Open SQL Server Configuration Manager. Select "SQL Server 2005 Network Configuration | Protocols for MSSQLSERVER" then enable the protocols you need

    • Enabled Named Pipes and TCP/IP protocols.

    Start > All Programs > Microsoft SQL Server 2005 > SQL Computer Manager

    In the left hand pane, expand "SQL Server Configuration Manager (Local) > SQL Server 2005 Network Configuration"

    In the left hand pane, highlight "Protocols for SQLEXPRESS"

    In the right hand pane, right click "Named Pipes" and select "Enable"

    In the right hand pane, right click "TCP/IP" and select "Properties"

    On the "IP Addresses" tab ensure that "Enabled" is set to "Yes" for each network adapter listed.

    Click "OK" to close the TCP/IP Properties dialog.

    In the left hand pane select "SQL Server 2005 Services"

    Right click "SQL Server (SQL EXPRESS)" and select "Restart"

    Whilst it is not required for this process, it can make the task of configuring remote access to SQL Server Express easier if you also start the process "SQL Server Browser".

    NOTE: reboot your machine afterwards

    Lastly,

    Server name was typed incorrectly.

    Try again with the correct server name.

    The SQL Server service on the server is not running.

    Start the instance of SQL Server Database Engine.

    The TCP/IP port for the Database Engine instance is blocked by a firewall.

    Configure the firewall to permit access to the Database Engine.

    Database Engine is not listening on port 1433 because it has been changed, or because it is not the default instance, and the SQL Server Browser service is not running.

    Either start the SQL Server Browser service, or connect specifying the TCP/IP port number.

    The SQL Server Browser service is running but UDP port 1434 is blocked by a firewall.

    Either configure the firewall to permit access to the UPD port 1434 on the server, or connect specifying the TCP/IP port number.

    The client and server are not configured to use the same network protocol.

    Using SQL Server Configuration Manager, confirm that both the server and the client computers have at least one enabled protocol in common.

    The network cannot resolve the server name to an IP address. This can be tested using the PING program.

    Fix the computer name resolution problem on your network or connect using the IP address of the server. This is not a SQL Server problem. For assistance, see your Windows documentation or your network administrator.

    The network cannot connect using the IP address. This can be tested using the PING program.

    Fix the TCP/IP problem on your network. This is not a SQL Server problem. For assistance, see your Windows documentation or your network administrator.

    Good luck and let me know if they work for you.



  • pappascd

    SUCCESS!!!!!

    Tools->Options->Database Tools->Design-time Validation Database was set to some random database elsewhere on the network! No idea how it picked that up, but clearing it fixed the problem - it's usually easy when you know how. I've now created a database project and imported from an existing database. Now the real work of understanding this tool can begin.

    Many thanks to all who contributed.


  • Gafrage

    MAN!!! I have spent 2 days on this same issue now and all your suggestions dont work.
    Here is a post I posted somewhere else:

    Hello,

    I started using the new CTP for Microsoft Visual Studio for Database
    proffessionals and it's great. however I decided to do a walkthrough on
    a web cast and follow the steps.
    When I go and open a new instance of Visual Studio and select add new
    project > sql2005 database project I get the following error:

    ---------------------------
    Microsoft Visual Studio
    ---------------------------
    An error has occurred while establishing a connection to the server.
    When connecting to SQL Server 2005, this failure may be caused by the
    fact that under the default settings SQL Server does not allow remote
    connections. (provider: SQL Network Interfaces, error: 26 - Error
    Locating Server/Instance Specified)
    ---------------------------
    OK
    ---------------------------

    All my SQL server allow remote connections.

    I have tried every possible combination of server instande in my tools
    options > database tools > data connections AND design time
    validation database.

    I have looked at all the config TCP settings and cant figure out what
    is going on. I allow TCP and named pipes.

    I have been connecting to any number of my databases for 8 months with
    no problem and visual studio works fine in all other areas.

    I dont have SQL express installed just SQL 2005

    Can any one help

    thanks
    RuSs

    PS. I know these issues are already listed above but I am at my wits end.

  • Lucas Condé

    If you use sql express you will lose some product functionality, such as the ability to create full-text related objects or create partition schemes or partition functions.

  • Tsrwebman

    Hi KevMac,

    It appears you are able to connect to your local SQL server except when creating your Database Project.

    I am curious, under Tools->Options->Database Tools->Design-time Validation Database... is the "SQL Server Instance Name" a blank field or is populated with your SQL Server name. Can you try leaving it blank, close Visual Studio and trying again.

    - Manoj


  • Error when trying to create a new database project