This is a follow-up to the below-captioned posting.

- - - - - - - -

From: Michael Pohl ([EMAIL PROTECTED])
Subject: DBD::Sybase: TDS protocol error
Newsgroup: perl.dbi.users
Date: 2002-12-06 12:46:07 PST 

I have been using DBD::Sybase with mod_cgi scripts for a couple of
years without issue.  I am working on migrating to mod_perl, but under
Apache::DBI I am encountering errors such as the following:

DBD::Sybase::st execute failed: OpenClient message: LAYER = (4) ORIGIN
= (1) SEVERITY = (5) NUMBER = (28)
Message String: ct_results(): protocol specific layer: external error:
There is a tds protocol error. An illegal token was received.
DBD::Sybase::st execute failed: OpenClient message: LAYER = (5) ORIGIN
= (1) SEVERITY = (5) NUMBER = (18)
Message String: ct_results(): network packet layer: external error:
There is a protocol packet error. An illegal length was received
[Fri Dec  6 15:28:43 2002] [error] Failed:
web_orders..sspVerifyAcctNumAndTimeStamp 52237,
'103910801765HRiSqhtv2WUsAfx'
OpenClient message: LAYER = (5) ORIGIN = (1) SEVERITY = (5) NUMBER =
(18)
Message String: ct_results(): network packet layer: external error:
There is a protocol packet error. An illegal length was received
[Fri Dec  6 15:28:43 2002] [error] Failed:
web_ec_customer..sspGetEcDealerParams '00000DLI00'
OpenClient message: LAYER = (4) ORIGIN = (1) SEVERITY = (5) NUMBER =
(28)
Message String: ct_results(): protocol specific layer: external error:
There is a tds protocol error. An illegal token was received.

I have not been able to track down the source of this error.  Our db
admins have been unsuccessfully researching this as well, and have
opened a couple support tickets with Sybase.  No response yet from
Sybase beyond a recommendation to update OpenClient, which we have
completed with no effect.

Any insight appreciated.

- - - - - - - -

Some additional info:

I can only duplicate these errors via mod_perl-enabled scripts, with or
without Apache::DBI.  (My posting incorrectly implies it is specific to
Apache::DBI.)  I can duplicate the error simply by reloading a
DBI-connecting, mod_perl-enabled script a few times in rapid succession.  
I cannot duplicate the error either via isql or via mod_cgi scripts using
DBI + DBD::Sybase.  Once one of these TDS protocol errors is thrown, the
db connection is declared dead, and I have to stop and restart Apache.  
I'm using DBD::Sybase 0.95.  Our db admins say Sybase support is being
less than helpful since we can only duplicate the error via the Perl
interface, which they do not support.

Again, any insight appreciated.

thanks,

michael


Reply via email to