Post reply

SQL connectivity error very urgetn

  • August 22, 2008 at 4:02 am

    #211485

    Hi all,

    It happend like this : some devlopers requested me to change the default port of sql server to 1035. After i changed, it asked for restarting the services.

    Now thoug sql server is up and running, our developers complaints that they are getting this message while trying to connect

    :Provider named pipes , could not connect to sql server. I tried everyhing but nothing worked out.

    any suggestion will b a gr8 help

    thanks

    santosh

  • August 22, 2008 at 4:08 am

    #861745

    Is the SQL Browser service started?

    If I remember correctly you need to use the browser service when you use a none default port number.

    [font="Verdana"]Markus Bohse[/font]

  • August 22, 2008 at 4:11 am

    #861747

    hi marks,

    yes sql browser is up and running...there is no issue with that.

  • August 22, 2008 at 7:39 am

    #861887

    have the developers check SQL Server Configuration Manager on their machines, and see if they have an Alias setup under the SQL Native Client Configuration section. With an Alias, they can specify the port number.

  • August 22, 2008 at 7:53 am

    #861896

    Yes, verify that they are specifying port number but do you have named pipes enabled on the server? Configuration Tools > SQL Server Configuration Manager > SQL Server Network Configuration

    That would seem to be the issue based on the error that you provided.

    David

    @SQLTentmaker

    “He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot

  • August 28, 2008 at 7:50 am

    #864394

    WE reverted back to port 1433 and asked them to modify in their application .

    It is fine now.

    thanks for all the inputs.

Viewing 6 posts - 1 through 5 (of 5 total)

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