Cannot connect to SQL Server 2005 database with Microsoft SQL Server Management Studio Express

Discussion in 'Databases' started by CraigMur27, Aug 9, 2007.

Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.
  1. I am unable to connect to the database I have purchased. I have read through some other posts in this forum but was unable to find anything useful. I tried the connecting and got the following error message:

    Cannot connect to sql2k509.discountasp.net.

    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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)

    Next I executed the following command:telnet sql2k509.discountasp.net 1433

    The follow error message was displayed:

    Connecting To sql2k509.discountasp.net...Could not open connection to the host,
    on port 1433: Connect failed

    I'm not sure where to go from here. Please help.
     
  2. If you are using SQL Server Management Studio, try setting your connection to use port 14330. This is our alternative port. You may also want to try to perform a telnet session first with port 14330 to insure that this port is open. If neither ports are open you will need to ask your network administrator to open these ports so that you can connect to our db server.
     
  3. Hi Craig;
    </o:p>
    I have the same problem and have been unable to resolve it as if yet. I took a long hiatus and just started reworking it again today.
    </o:p>
    In my case, it is especially frustrating because I can use the database explorer tool in Visual Web Developer Express to connect to SQL 2005 without a problem. However, VWDE doesn?t allow tinkering with the database structure. So there's got to be something hinky with the SSMSE settings on my machine.
    </o:p>
    However, in looking at your error message, (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server), I noticed it said ?Named Pipes?.
    </o:p>
    If your connection properties tab has the Network protocol set to Named Pipes instead of TCP/IP, that might be your problem. Just a thought.
    </o:p>
    Also, I?ve noticed with the Network protocol set to TCP/IP, you don?t use the ?tcp:? prefix in the database name, i.e., sql2k509.discountasp.net.
    </o:p>
    But if the Network protocol set to <default>, the database name should be: tcp: sql2k509.discountasp.net.
    </o:p>
    Good luck,
    </o:p>Lar
     
  4. I am now having the same issue connecting via management studio to my new purchased database, as well as trying to connect through an asp page on my discountasp.net web site.
    Did you get this working? What was the catch?
    Thanks!
     
  5. It's working for me now, thank you!
     
  6. I am unable to connect to the database via an asp page.


    ;-2147467259
    [DBNETLIB][ConnectionOpen (Connect()).]Specified SQL server not found.


    The asp page is also on my discountasp.net site, so there should not be any connection issues from the web server. I'm unsure if there is some special connection string to connect to a discountasp.net sql server? I have used this same connection string syntax numerous times w/o issue connecting to other databases.


    The connection string I am using is
    Provider=SQLOLEDB;Data Source=tcp:sql2k511.discountastp.net; Initial Catalog=SQL2005_395411_everpalm;User ID=SQL2005_395411_everpalm_user;Password=[****];
     
  7. I'm currently making SQL Server 2005 conns to DASP servers with both ASP and ASP.NET.

    The ASP conn string I successfully use is in this format:

     
Thread Status:
Threads that have been inactive for 5 years or longer are closed to further replies. Please start a new thread.

Share This Page