Sybase ODBC Driver: Net-Lib protocol driver call to close endpoint failed
Abraham
table that works on a Windows XP computer running IIS 5.1.
However, if I try to run it on a Windows Server 2003 running
IIS 6, the page fails with the following error:
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[SYBASE][ODBC Sybase driver][Sybase]ct_connect(): network
packet layer: internal net library error: Net-Lib protocol
driver call to close endpoint failed
The ODBC driver is from the same install package on both
computers. I can test the driver via the ODBC settings and
it will test successfully. I've tried to find any
information on what exactly this error means, but the only
search hits I get are people requesting assistance that go
unanswered. It seems to be a problem with the ODBC
connection on this platform, but I'm unsure on what
direction to go in troubleshooting.
The ASP code fails at the last line of this segment, which
has the connection data changed to protect the innocent:
Set myConn = Server.CreateObject("ADODB.Connection")
Set myRS = Server.CreateObject("ADODB.Recordset")
myConn.ConnectionString =
"DSN=myDSN;SRVR=myServer;DB=myDB;UID=myID;PWD=myPass"
myConn.Open
Paul
You're using a very old odbc driver, which is no longer supported
by Sybase to access the IIS. However, the error implies the connection
information you're providing to the driver is no correct - it can't find the
ASE.
The SRVR property must match the ASE name found in the SQL.INI file
found in %SYBABSE%\ini. From the same machine running the IIS you
could use the ISQL utility to confirm this connectivity.
Since you're on Windows 2003 I highly suggest you upgrade the ODBC
driver to use the current ODBC driver (in the SDK 12.5.1 or 15.0 for
Windows PC). The current driver doesn't rely on Open Client for
connectivity - the ODBC API directly communicates to the TDS protocol,
the layer communicating the client to the server. In this regard you
provide the host and port in the DSN used. If the host and port setup
match that of the ASE you should connect without difficulty.
Also - in your string:
DSN=myDSN;SRVR=myServer
In your DSN you should already have the SRVR set already - I'm wondering if
this driver is somehow getting
messed up by using SRVR again. Maybe remove SRVR and try it?
-Paul
<Abraham> wrote in message news:478e2b3e.6d1...@sybase.com...
J
Paul,
I agree it would be better if he used a later supported ODBC driver. I
see this : http://support.microsoft.com/kb/238971
I find the error unusual since it says "unable to close endpoint" vs.
the more typical "unable to connect two endpoints".
Jay
Paul
You really want to upgrade to newer client product.
WIth IIS 6.0, running on Windows 2003 you'll likely start
working from ASP to ASP.NET,
In this regard, you'll have 3 options to use with ASP.NET:
ASE ODBC, OLEDB or ADO.NET Provider.
The 80004005 implies missing DSN, however, since you get the ct_connect
message,
this implies the DSN exists but for some reason the session between client
and ASE
fails for some reason. I suspect you're using some outdated driver and
maybe
running into some problem.
-Paul
"J" <jtotall...@sbcglobal.net> wrote in message
news:478ea644...@forums.sybase.com...
Abraham
differently.
I wouldn't mind upgrading the client at some point, but I'm
not in a situation to do so at the moment.
What I was able to do was completely eradicate all traces of
Sybase on the server and start over by configuring
everything manually instead of letting the install package
handle the details. That ultimately solved my problem.
Your collective help got my mind working in different
directions on what I needed to look for, so while I didn't
follow the good advice given, it still helped!