Results 1 to 5 of 5

Thread: Named Pipes Error...

  1. #1
    Gary Guest

    Named Pipes Error...


    Can anybody help?
    I have recently got any error -
    Microsoft OLE DB Provider for ODBC Drivers error '80004005'
    [Microsoft][ODBC SQL Server Driver][Named Pipes]Connection Broken
    /

    Does anybody know how to resolve or point me in the right direction.....?

    Thanks

  2. #2
    ran Guest

    Named Pipes Error... (reply)

    Make sure the connection settings are properly defined.


    ------------
    Gary at 6/28/01 11:37:11 AM


    Can anybody help?
    I have recently got any error -
    Microsoft OLE DB Provider for ODBC Drivers error '80004005'
    [Microsoft][ODBC SQL Server Driver][Named Pipes]Connection Broken
    /

    Does anybody know how to resolve or point me in the right direction.....?

    Thanks

  3. #3
    Raghu Guest

    Named Pipes Error... (reply)


    Check the client configuration on ODBC Driver and make sure that the pipe name is a valid

    ------------
    Gary at 6/28/01 11:37:11 AM


    Can anybody help?
    I have recently got any error -
    Microsoft OLE DB Provider for ODBC Drivers error '80004005'
    [Microsoft][ODBC SQL Server Driver][Named Pipes]Connection Broken
    /

    Does anybody know how to resolve or point me in the right direction.....?

    Thanks

  4. #4
    Anu Guest

    Named Pipes Error... (reply)


    check Q169377

    in microsoft knowledgebase


    -Anu

    ------------
    Raghu at 7/3/01 11:17:51 AM


    Check the client configuration on ODBC Driver and make sure that the pipe name is a valid

    ------------
    Gary at 6/28/01 11:37:11 AM


    Can anybody help?
    I have recently got any error -
    Microsoft OLE DB Provider for ODBC Drivers error '80004005'
    [Microsoft][ODBC SQL Server Driver][Named Pipes]Connection Broken
    /

    Does anybody know how to resolve or point me in the right direction.....?

    Thanks

  5. #5
    Dave Guest

    Named Pipes Error... (reply)

    Set your ODBC data source connection type to TCP/IP. TCP connections are always more reliable in my experience, especially with non-standard network layouts ( firewalls, private networks, etc. ).

    The problem remaining is that the ODBC driver has a nasty habit of switching back to named pipes when the TCP network drops out. This can be fixed by setting the default connection type to TCP on install.

    Hope this helps!

    -Dave


    ------------
    Gary at 6/28/01 11:37:11 AM


    Can anybody help?
    I have recently got any error -
    Microsoft OLE DB Provider for ODBC Drivers error '80004005'
    [Microsoft][ODBC SQL Server Driver][Named Pipes]Connection Broken
    /

    Does anybody know how to resolve or point me in the right direction.....?

    Thanks

Posting Permissions

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