Error establishing socket to SQL Server 2003

Ask a Question related to Coldfusion Database Access, Design and Development.

  1. #1

    Default Error establishing socket to SQL Server 2003

    I loaded 11 MS cirtical updates last night on my CF server and SQL server and now I can not get any of the ODBC connections to work. Hellp!
    xwawx Guest

  2. Similar Questions and Discussions

    1. Error establishing socket. No buffer space available
      I have a server problem that I cannot figure out. I found an old thread but no one ever posted a solution, so thought I would see if anyone has any...
    2. Error establishing socket. Connection refused:connect
      ODBC Connection saved the day. Thanks for the post.. i still have my hair intact. SP2 on Win XP Pro is a deadly combo it seems.
    3. Error establishing socket. Address already in use
      Running CFMX 6.1 on Win2k3, I just recently started getting these errors from connections to one of our SQLServer database servers (2000,...
    4. Error establishing socket
      Need some help here! I am using Cold Fusion 7 MX standard and SQL server 2000 sp4 on Win XP sp1. All of the installation and setup looked good....
    5. Error ASP 0178 on Windows 2003 Server (IIS6) by Server.CreateObject on DCOM registred Component
      Heres is a workaround, 1. go to Administrative Tools> Component Services 2. expand COM Services and right click on My computer. 3. click...
  3. #2

    Default Re: Error establishing socket to SQL Server 2003

    I have SP# loaded and I am loading SP 4 as I type. Anyone else have this problem?
    xwawx Guest

  4. #3

    Default Re: Error establishing socket to SQL Server 2003

    I have SP3 loaded and I am loading SP 4 as I type. Anyone else have this problem?
    forumnotifier Guest

  5. #4

    Default Re: Error establishing socket to SQL Server 2003

    In the ColdFusion MX 7 Administrator, when I try to create a new datasource of
    type ?ODBC Socket?, the drop down labled ?ODBC DSN? that is supposed to show
    you the list of DSN?s defined in the Windows ?System DSN? list comes up empty.
    How do I get the list of my system DSN?s to appear on the ODBC Socket
    configuration page??

    I?m running Windows 2003 Server running CFMX 7. I have the ?MX7 ODBC Agent?
    and ?MX7 ODBC Server? services running.

    Jon Block Guest

Posting Permissions

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

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139