Page 1 of 2 12 LastLast
Results 1 to 15 of 16
  1. #1
    Join Date
    Mar 2003
    Location
    Memphis, TN, USA
    Posts
    61

    Red face Unanswered: ODBC error 80004005'

    Hi there !

    I am getting an error message and i have no idea where is the fault. I am getting the below mention error on my index file when i try to extract some data from tables. The error which i am getting is....

    Microsoft OLE DB Provider for ODBC Drivers error '80004005'
    [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.

    I used correct user id and password in odbc dsn and able to connect to the server with the same user id and password thru sql tools. I am also able to ping my remote sql server.

    As per my experience, i guess that there is some settings problem. Or it might be that I just plain can't do this?

    I am using ASP and SQL Server 2000.

    Can anyone put some light on it ? Where is the fault ??

    Thanks for your anticipations.
    sql boy

  2. #2
    Join Date
    Aug 2002
    Location
    Scotland
    Posts
    1,578
    Have you tried using TCP/IP as default netlib.
    --Satya SKJ
    Microsoft SQL Server MVP
    [IMG]http://sqlserver-qa.net/google_bart.gif[/IMG]

  3. #3
    Join Date
    Mar 2003
    Location
    Memphis, TN, USA
    Posts
    61
    Hello Satya !
    Thanks for reply. But it would be great help if you eloborate your point atlength. I am not getting what you wish to convey.
    Pardon me, for not getting your words.

    Sqlboy

  4. #4
    Join Date
    Aug 2002
    Location
    Scotland
    Posts
    1,578
    Not a problem, get more of it from this http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q169/3/77.asp&NoWebContent=1
    Originally posted by sqlboy
    Hello Satya !
    Thanks for reply. But it would be great help if you eloborate your point atlength. I am not getting what you wish to convey.
    Pardon me, for not getting your words.

    Sqlboy
    --Satya SKJ
    Microsoft SQL Server MVP
    [IMG]http://sqlserver-qa.net/google_bart.gif[/IMG]

  5. #5
    Join Date
    Nov 2002
    Location
    London
    Posts
    47
    Hi

    Any reason why you're not using the OLE-DB provider for SQLServer but the SQLServer ODBC driver?

    Emmon
    OpenLink Software

  6. #6
    Join Date
    Mar 2003
    Location
    Memphis, TN, USA
    Posts
    61

    Post

    Satya,
    The link wasn't working.

    Thanks for your reply.

    sqlboy

  7. #7
    Join Date
    Aug 2002
    Location
    Scotland
    Posts
    1,578
    I replied to your message, either you paste the whole content on new window or search MS knowledge base for Q169377.

    HTH
    --Satya SKJ
    Microsoft SQL Server MVP
    [IMG]http://sqlserver-qa.net/google_bart.gif[/IMG]

  8. #8
    Join Date
    Aug 2002
    Location
    Scotland
    Posts
    1,578
    Yes it did the trick I can get the KBA by pasting the whole HTTP link on new window.
    --Satya SKJ
    Microsoft SQL Server MVP
    [IMG]http://sqlserver-qa.net/google_bart.gif[/IMG]

  9. #9
    Join Date
    Mar 2003
    Location
    Memphis, TN, USA
    Posts
    61

    Post

    Satya,
    I read that article but not find anything special which can sort out my problem. So, I attached my index file with this reply.

    Thanks for your anticipations.

    sqlboy
    Attached Files Attached Files

  10. #10
    Join Date
    Mar 2003
    Location
    Memphis, TN, USA
    Posts
    61
    Hello Emmon,
    Above all thanks for your concern. Because, I am getting error using ODBC driver so I opt OLE-DB. I guess, it's not an right decision.

    So in the same sense.. Any reason why I left SQL ODBC driver and take OLE-DB apart from that error ???

    sqlboy

  11. #11
    Join Date
    Aug 2002
    Location
    Scotland
    Posts
    1,578
    As referred in KBA:
    -The Trusted Connection box is not checked in the System DSN definition.
    -The SQL Server security mode is not Windows NT Integrated.
    -Within the connection attribute, the uid is not blank.

    As I referred in my first post, try connecting the server by making TCP/IP as default netlib on server.
    --Satya SKJ
    Microsoft SQL Server MVP
    [IMG]http://sqlserver-qa.net/google_bart.gif[/IMG]

  12. #12
    Join Date
    Nov 2002
    Location
    London
    Posts
    47
    Hi

    Well although I'm biased as I work for an ODBC vendor, the OLE-DB provider will always be a more efficient way of connecting as it provides more functionality than the ODBC drivers would.

    Emmon (www.openlinksw.com)

  13. #13
    Join Date
    Mar 2003
    Location
    Memphis, TN, USA
    Posts
    61

    Post

    Satya,
    Okay fine. I'll try to make TCP/IP as default netlib and let you know after that. Though, I'll do that thing first time in my life so i amn't sure wether i am capable to do the thing right or not. If you have any article regarding the same sense then it would be great help.

    With Thanks,
    Sqlboy

  14. #14
    Join Date
    Mar 2003
    Location
    Memphis, TN, USA
    Posts
    61

    Post

    HelloEmmon,
    Well said. I guess, a good debuger is not that person who give the suggestion to opt something else but it is those who try to nab the error by taking the same code.

    Emmon there is saying.... Some men see things as they are and ask why. Others dream things that never were and ask why not.

    Anyway!
    Thanks for your anticipations
    SQlboy.

  15. #15
    Join Date
    Nov 2002
    Location
    London
    Posts
    47
    Hi Sqlboy

    That's one saying I will be using with my support consultants. :d

    Emmon

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •