Post reply

ODBC, TCPIP and Named Pipes

  • January 29, 2004 at 8:38 am

    #83922

    Heres the problem, we have a web based reporting tool that runs via  COM + and the reports don't run since the SQL Server box was rebooted. We believe the supplier may have used ODBC to connect from COM + . ODBC on the machine has doesn't seem to be working via TCPIP only Named pipes. We were able to get other clients to run via ODBC when we changed it to Named pipes but the COM+ still fails.

     

    Any ideas?

    Nigel Moore
    ======================

  • January 29, 2004 at 11:02 am

    #492217

    Check the SQL Server log and the Application Event Log on the server wehere SQL Server resides. See if it had trouble binding to the TCP port. If it did, you'll see a bind error. If there is one, run a netstat -an and see if there is anything listening on that port. If there is, you'll have to track down what it is and stop it. If there's not, stop and restart SQL Server.

     

    K. Brian Kelley
    @kbriankelley

Viewing 2 posts - 1 through 1 (of 1 total)

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