Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Database & SysAdmin
  3. Database
  4. SQL Server connections to backend server failing

SQL Server connections to backend server failing

Scheduled Pinned Locked Moved Database
cssdatabasesql-serversysadminwindows-admin
2 Posts 2 Posters 9 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • C Offline
    C Offline
    Chris Maunder
    wrote on last edited by
    #1

    Given 2 machines, one running IIS, the other SQLServer, with connections to SQLServer via named pipes (as opposed to TCP/IP) on a LAN, is there any way to determine why a connection to the SQLServer from the Web server would be failing at random times? The error messages reported by SQLServer and IIS are less than inspiring. Just wondering if anyone else has come across this random fail situation before. cheers, Chris Maunder

    A 1 Reply Last reply
    0
    • C Chris Maunder

      Given 2 machines, one running IIS, the other SQLServer, with connections to SQLServer via named pipes (as opposed to TCP/IP) on a LAN, is there any way to determine why a connection to the SQLServer from the Web server would be failing at random times? The error messages reported by SQLServer and IIS are less than inspiring. Just wondering if anyone else has come across this random fail situation before. cheers, Chris Maunder

      A Offline
      A Offline
      Anders Molin
      wrote on last edited by
      #2

      Just chage the client on both machines to use TCP instead of Named Pipes and the problem is gone :) (I hope) Well, at least, if the errormessages is something about a "Overlapped Result" it works... - Anders

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups