Post reply

getting error to connect server

  • June 9, 2008 at 12:55 am

    #122949

    Hi,

    I am getting following error to connect server

    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) (.Net SqlClient Data Provider)

    Regards,

    Sunil

  • June 9, 2008 at 1:04 am

    #825979

    Use Surface Area Configuration to enable remote connections.

  • June 9, 2008 at 1:10 am

    #825981

    1.Make sure you have enabled Remote Connections in the Surface Area Configurations.

    2.Make sure the SQL Server Browser service is started in the Sql Server Configuration Manager.

  • June 9, 2008 at 1:21 am

    #825987

    Hi,

    Everything is enable still its not connected.

    Regards,

    Sunil

  • June 9, 2008 at 2:27 am

    #825996

    To which edition of SQL Server you are connecting????

  • June 9, 2008 at 2:54 am

    #825997

    SQL EXPRESS

  • June 9, 2008 at 3:27 am

    #826001

    connect giving InstanceName\SQLEXPRESS

  • June 9, 2008 at 3:49 am

    #826007

    use

    strt->> programs ->>sql server->> configuration tools ->> sql server configuration manager

    now

    choose

    sql native client configuration->> client protocols

    sahred memory - enabled

    tcp/ip -- enabled

    named pipes -- enabled

    via --disabled

  • June 9, 2008 at 4:31 am

    #826020

    Kumar ..u got connect or still the same problem persists ???

  • June 10, 2008 at 3:36 am

    #826503

    still its not connected................

  • June 10, 2008 at 8:43 am

    #826707

    run the cliconfg program (in the windows\system32 directory)

    move tcp/ip and named pipes to the enabled list.

    you enabled the server to communicate with previous steps, my instructions should enable the client to talk to the server.

    -don

  • June 10, 2008 at 8:45 am

    #826709

    oh, and i *think* when you changed the connection options on the server (a few posts above) you need to restart the sql server service. not 100% sure, but if you can't connect after configuring the client, that's the next thing to do.

    -don

  • June 11, 2008 at 5:06 pm

    #827596

    If the SQL instance is installed on Windows Server 2003 try doing the following:

    1. Open Control Panel -> Administrative Tools -> Component Services.

    2. Expand the Component Services -> Computers menu in the left hand pane

    3. Right click on My Computer

    4. Click Properties

    5. Open the MSDTC tab and click the "Security Configuration" button

    6. Check "Network DTC Access" check box if it is not already enabled.

    7. Check "Allow Remote Clients".

    8. Click OK.

    9. Click OK again.

    If the Component Services window doesn't display the properties page, you'll need to check Add/Remove Programs -> Add/Remove Windows Components and verify that MSDTC is installed.

    Hope this helps

  • June 11, 2008 at 6:03 pm

    #827603

    Well how certain are you that you have the correct user/password ? And if not using a SQL Server login do you have mixed mode so you can use Windows Authentication and SQL Server logins.

    (And the most bizarre thing, the spell checker for this page is telling me that I have spelt "SQL" incorrectly (and "spelt"))


    The systems fine with no users loggged in. Can we keep it that way ?br>

  • June 20, 2008 at 6:27 am

    #831701

    Try giving INSTANCE_NAME\SQLEXPRESS,1433..Make sure your SQL Server service is up and running.

Viewing 15 posts - 1 through 15 (of 15 total)

You must be logged in to reply to this topic. Login to reply