Post reply

Dotnet data provider issue with SQL server 2000

  • May 4, 2007 at 1:42 pm

    #76700

    Hi,

    I have a connectivity problem in accessing SQL server 2000 using dotnet provider(SQL client). I tried connecting using visual web developer 2005.

    1) I can connect to SQL server using OLEDB provider but dotnet provider(SQL client) is failing with exception "Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding"

    2) I can connect to other SQL servers without any problem.

    So I guess the problem is related to this particular SQL server. I wonder any extra configuration setting should be required in SQL server to communicate with Dot net provider.

    Any help is greatly appreciated.

    Thanks,

    Rakesh

  • May 7, 2007 at 6:31 am

    #704611

    A couple of questions:

    1. Is the SQL instance you're connecting to a named or default instance?

    2. Any chance you could post the connection string you're using?

    Thanks-

    TC

  • May 7, 2007 at 8:19 am

    #704646

    Hi Rookie,

    Thanks for your reply.

    1) It is a default instance.

    2) I tried connecting using "Configure data source" wizard of Visual Web developer 2005. I also tried setting up a connection string in code lke "server=Mattisse;uid=sa;pwd=abc;database=Test". But none of it worked. If I am using OLEDB I can connect to database.

    Thanks,

    Rakesh

     

     

  • May 7, 2007 at 8:55 am

    #704667

    In Visual Studio 2005 there is an additional parameter in the connection string-providerName. Here is a sample of one I use:

    add name="cstCWR" connectionString="Data Source=server;Initial Catalog=dbname;User ID=user;Password=pwd"

    providerName="System.Data.SqlClient"

    Here is a good site for looking up connection strings:

    http://www.connectionstrings.com/

  • May 8, 2007 at 9:15 am

    #704960

    Rookie,

    That also doesn't help. I guess this is something to do with that particular SQL server setting since I can connect to any other SQL server with Dotnet data provider. Looks strange and frustrating

    Thanks,

    Rakesh

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

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