Partially solved the problem {OLE DB error - TCP Provider: No connection could be made ...}

Partially solved the problem {OLE DB error - TCP Provider: No connection could be made ...}

• Saul775

  Thanks Ming; your response gave me enough cues to solve my problem, although partially. I am facing a new problem now as mentioned later.

  I did not have firewall enabled on the server. "netstat -ano" did not show SQL Server listening on port 1433. Eventually, it turned out to be a silly reason: the dynamic ports setting for IP_ALL was not deleted and the IP_1 and IP_2 although showed up as Active, were disabled.

  After making the corrections, I was able to see the 1433 port being listened on and telnet to the server on 1433 port did not give any connection errors.

  However, I was still not able to connect. The new error being:

  OLE DB error: OLE DB or ODBC error: Login failed for user 'NT AUTHORITY\LOCAL SERVICE'.; 28000; Cannot open database "DocumentDB" requested by the login. The login failed.; 42000.

  I checked the impersonation information for the datasource. It is set to "Use the service account". How do I assign the local service the privilege to connect to the database I am trying to access

  Any help is welcome.

  - Sanchet

  
  

• skipsizemore

  Hi Sanchet,

  I am unable to connect to the database created in SQL 2005. My username and password are correct. I am unable to start the SQL server agent.

  <<I did not have firewall enabled on the server. "netstat -ano" did not show SQL Server listening on port 1433. Eventually, it turned out to be a silly reason: the dynamic ports setting for IP_ALL was not deleted and the IP_1 and IP_2 although showed up as Active, were disabled.

  After making the corrections, I was able to see the 1433 port being listened on and telnet to the server on 1433 port did not give any connection errors.>>

  Even i am unable to see the port no. 1433 can you please explain how you resolved the issue.

  This error is bugging me a lot...........

  Thanks!!!!!!!!

  
  
  

• Reyad

  Appreciate your help, Ming. I am not clear about proceeding with your suggestion in point #2. But, I shall take it over in the security forum.

  Thanks!

  [Posted the existing problem onto the security forum @]

  http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=371493&SiteID=1&mode=1

  
  

• 12345x123456

  So, this is not connection problem anymore, and turned to be permission issue to access database.

  1) Did you install sql express or other sku

  2) Suggest open Managment studio, connect to sql instance, then find the database, and click propertied of "DocumentDB", choose permission, add the login credential. "loca service" act as a non-admin account locally, so, to access database, you need to grant login to it.

  If you further face the permission issue, please post your problem to the security forum, they are focus on the login area:

  http://forums.microsoft.com/MSDN/ShowForum.aspx ForumID=92&SiteID=1

  HTH

  Ming.

  
  

• Paul.2010

  To fix your problem, can you provide follow info

  1) Is it remote connection Do you have firewall enabled on your server

  2) On the server box, use "netstat -ano |findstr 1433", check whether it is your sql 2005 named instance by PID who is listening on the port Or double check server errorlog to make sure sql 2005 named instance is listening on 1433.

  3) From your client box, " telnet <serverip> 1433 " does it work

  4) What is your connection string, do you have multiple instances installed on your server If you connect to the sql 2005 named instance, you need specify <instancename> in your connection string:

  eg: Server= <remotemachinename>\<instancename> or

  Server=<remotemachinename>\<instancename>,1433

  5) Double check sqlbrowser service is running on your server box.

  HTH.

  Ming.

  
  
• Partially solved the problem {OLE DB error - TCP Provider: No connection could be made ...}