[Sybase][ODBC Driver]Internal Error

[Akash]

Hi All,

I am facing a problem with ODBC drivers while working on the migration
of one of vb application to our wintel box.

If anybody had faced the same problem earlier and can suggest me to
resolve this issue, that would be a great help.

Our one of VB application crashing randomy(sometimes) with one of
following errors.

1. Runtime error [-2147467259] At field [] [Sybase][ODBC Driver]
Internal Error

2. Runtime error [-2147217859] Type is invalid

3. Runtime error [-2147467259] At field [] Data provider or other
service returned an E_FAIL status.

The application works fine if i use Sybase ASE ODBC Driver
(syodase.dll) , but it doesn't work with new Sybase driver Adaptive
Server Enterprise (sybdrvodb.dll) and fails with the above error. I am
using sybase 12.5 odbc driver with sybase 15 server. Even tried
sybase 15 odbc driver, but faced the same problem.

Please suggets if anyone knows the problem and the solution.

Thanks
Akash

[Paul Vero [Sybase]]

Hi Akash,

Provide exact file versions of the driver and please
provide some of the details in the application leading to this
behavior. Some problems could be cleared if using current
versions. If using current versions and still getting the errors
you'll need to open a Sybase tech support case to have this
investigated.

What exactly is the vb application doing?

-Paul

"Akash" <taneja...@googlemail.com> wrote in message
news:88a33354-9b1b-4a01...@k2g2000yql.googlegroups.com...

[Akash]

Hi Paul,

Exact driver version is Adaptive Server Enterprise 12.05.01.500. The
sybase server which i am trying to connect is sybase 15.0.2.
The application is VB application which is using ADODB.Connection and
ADODB.Command to call a sybase procedure. Sometime is gives an error
while executing the sybase procedure call. It sometimes also gives the
following error.

DB Error Details:
Error No : -2147217859
SQL State :
Native Error : -2147217859
Source : Provider
Description : Type is invalid.

But suprisingly, if i use old Sybase ASE ODBC Driver 4.20.00.35,
application works fine without any problem.

Thanks
Akash

On 6 Apr, 16:58, "Paul Vero [Sybase]" <pv...@nospam.com> wrote:
> Hi Akash,
>
> Provide exact file versions of the driver and please
> provide some of the details in the application leading to this
> behavior.  Some problems could be cleared if using current
> versions.  If using current versions and still getting the errors
> you'll need to open a Sybase tech support case to have this
> investigated.
>
> What exactly is the vb application doing?
>
> -Paul
>

> "Akash" <taneja.ak...@googlemail.com> wrote in message

>
> news:88a33354-9b1b-4a01...@k2g2000yql.googlegroups.com...
>
>
>
> > Hi All,
>
> > I am facing a problem with ODBC drivers while working on the migration
> > of one of vb application to our wintel box.
>
> > If anybody had faced the same problem earlier and can suggest me to
> > resolve this issue, that would be a great help.
>
> > Our one of  VB application crashing randomy(sometimes) with one of
> > following errors.
>
> > 1. Runtime error [-2147467259] At field [] [Sybase][ODBC Driver]
> > Internal Error
>
> > 2. Runtime error [-2147217859] Type is invalid
>
> > 3. Runtime error [-2147467259] At field [] Data provider or other
> > service returned an E_FAIL status.
>
> > The application works fine if i use Sybase ASE ODBC Driver
> > (syodase.dll) , but it doesn't work with new Sybase driver Adaptive
> > Server Enterprise (sybdrvodb.dll) and fails with the above error. I am
> > using sybase 12.5 odbc driver with sybase 15 server.  Even  tried
> > sybase 15 odbc driver, but faced the same problem.
>
> > Please suggets if anyone knows the problem and the solution.
>
> > Thanks

> > Akash- Hide quoted text -
>
> - Show quoted text -

[Paul Vero [Sybase]]

HI Akash,

That's a relatively old version of the driver - EBF 16165 12.5.1 ESD#25
(12.5.1.680) might
resolve the issue. I can't say this with certainty but there are a few
conversion and datatype
related fixes in this newer build version.

You should try that - if problem still persists open a Tech Support case
with Sybase.

Thank you,

-Paul

"Akash" <taneja...@googlemail.com> wrote in message

news:9766d186-b71f-4ea9...@a7g2000yqk.googlegroups.com...

[Akash]

Hi Paul,

I installed 15.00.00.50 driver and tested my application. The problem
is still coming. Also, the code works sometimes and throws error "Type
is invalid" sometime.

The problem comes only when i use a stored proc and pass some
parameters to it.

The exact code is as below.

Set com1 = New ADODB.Command
With com1
.CommandTimeout = 55
.CommandType = adCmdStoredProc
.CommandText = "dbo.up_mdb_GetSeedMdbStatus"
.ActiveConnection = mstrConnectionString
.Parameters.Append .CreateParameter("@rstrReady", adVarChar,
adParamOutput, 1)
.Parameters.Append .CreateParameter("@vstrForceRegenerate",
adVarChar, adParamInput, 1, "Y")
.Execute
End With

It seems i should open a sybase tech support case. Can you please
suggest me how to open a sybase tech support case.

I can only see following options in case management.

Create Registration Card Case
Create Non Technical Case
Create Bug Report Case
Create Enhancement Request Case

I cann't see any option of Create Technical Case.

Thanks
Akash

On 8 Apr, 19:01, "Paul Vero [Sybase]" <pv...@nospam.com> wrote:
> HI Akash,
>
> That's a relatively old version of the driver - EBF 16165 12.5.1 ESD#25
> (12.5.1.680) might
> resolve the issue.  I can't say this with certainty but there are a few
> conversion and datatype
> related fixes in this newer build version.
>
> You should try that - if problem still persists open a Tech Support case
> with Sybase.
>
> Thank you,
>
> -Paul
>

> >> - Show quoted text -- Hide quoted text -

[Paul Vero [Sybase]]

Hi Akash,

That's an old 15.0 version - probably the original -
On the ASE ODBC Driver - the codelines are the same so if
this is fixed you need either latest 12.5.1 or 15.0 (15.0 latest is ESD#17)

You should call 1-800-879-2273 (1 -800-8SY-BASE)
to have your case management checked out.

-Paul

"Akash" <taneja...@googlemail.com> wrote in message

news:9af8b9f7-1844-4922...@k2g2000yql.googlegroups.com...