Re: Internal Error: 30002

[Prakash]

I am calling a stored proc with 30 parameters and update a record in a sybase
table. The proc running file when invoked from sql editor but fails when called
from AASEClient 12.5.1. Any suggestions?

On 8 Jun 2004 03:11:21 -0700,
in sybase.public.connectivity.adonet
<Carl Worden> wrote:
>We are getting a similar problem here trying to use the ASE
>ADO.NET Data Provider. In our case invoking a sproc with 64
>parameters causes 'Internal Error: 30002'.
>
>For your info we are using Data Provider ESD1 for 12.5.1 on
>the client connecting to a "ASE/12.0.0.6/P/EBF 10628 ESD
>1/Sun_svr4" dataserver.
>
>Has the cause of this problem been identified and a fix
>scheduled for a future EBF?
>
>Thanks in advance,
>CW
>
>> I have successfully executed your stored proc with 64
>> parameters. Couple of things I did notice:
>> 1) Set the value of the money param to a decimal value
>> Dim mymoney as New Decimal(1.20)
>> param.Value = mymoney
>> 2) Increase the length of the output param msg to 100 both
>> in SP and the Param
>>
>> Try it and if it still fails, try generating the trace.
>>
>> Thanks,
>>
>> Ashish
>>
>> "Germano" <German...@Brown.edu> wrote in message
>> news:3fc3b755$1@forums-2-dub...
>> > It looks like I'm hitting some limit.
>> >
>> > Is there a limit on the number of parameters I can bind
>> > when calling a stored procedure?
>> >
>> > I put the code back to the way it was yeterday and it
>> > works fine. I now start adding one by one and it fails
>> > when I add parameter number 62, no matter which one.
>> >
>> > "Ashish Mahajan" <ashish...@nospam.com> wrote in
>> > message news:3fc3a145$1@forums-1-dub...
>> > > It is not obvious from your code and sql why you would
>> > get this error... Can
>> > > you generate trace by using the trace events as in
>> "Advanced" sample ? If
>> > > you have ever used Ribo (TDS sniffer) a TDS trace
>> > > would be great. If not just the ado.net trace would be
>> > > good. Another way to track it would be to revert your
>> > changes, make it work again
>> > > and then add columns one or two at a time. That way
>> > > you might be able to isolate the issue.
>> > >
>> > > Thanks,
>> > >
>> > > Ashish
>> > >
>> > >
>> > > "Germano" <German...@Brown.edu> wrote in message
>> > > news:3fc3922c$1@forums-1-dub...
>> > > > Ashish,
>> > > >
>> > > > This has been working fine until I had to modify the
>> > table, the SP and the
>> > > > ASP code to add a few more columns this morning.
>> That's when it stopped
>> > > > working.
>> > > >
>> > > > Here a re the columns that I added to the table:
>> > > >
>> > > > @phone_area_code char(3),
>> > > > @phone_number char(7),
>> > > > @email_address char(60),
>> > > > @major_code1 char(7),
>> > > > @major_code2 char(7),
>> > > > @major_code3 char(7),
>> > > >
>> > > > "Ashish Mahajan" <ashish...@nospam.com> wrote in
>> > > > message news:3fc3902f$1@forums-1-dub...
>> > > > > Can you send me the text of the stored proc ?
>> > > > > I assume that the line causing this exception is
>> cmd.ExecuteNonQuery()
>> > > > > Can you also send me the code that is used to bind
>> all the parameters.
>> > > > >
>> > > > > Thanks,
>> > > > >
>> > > > > Ashish
>> > > > >
>> > > > > "Germano" <German...@Brown.edu> wrote in
>> > > > > message news:3fc38ed3$1@forums-1-dub...
>> > > > > > Hi,
>> > > > > > I'm using a stored procedure to insert a record
>> > into a specific table,
>> > > > and
>> > > > > > when I call the stored procedure from SQL it
>> works fine, but when I
>> > > call
>> > > > > it
>> > > > > > from ASP.NET I'm getting this internal error.
>> > > Any ideas what this error
>> > > > > > means?
>> > > > > >
>> > > > > > The SP inserts a record and it outputs a message
>> > specifying wheter or
>> > > > not
>> > > > > > the record was successfully saved.
>> > > > > >
>> > > > > > I'm getting the error in the "Catch ex as
>> > > > > AseException" >
>> > > > > > Try
>> > > > > > cmd.ExecuteNonQuery()
>> > > > > > If cmd.Parameters("@retValue").Value = 0
>> > > > > > Then lblMsg.Text = "No record
>> > > > > > saved!" lblMsg.Visible = "True"
>> > > > > > Else
>> > > > > > lblMsg.Text = "Error: " &
>> > > > > > cmd.Parameters("@msg").Value
>> > > > > > lblMsg.Visible = "True" End If
>> > > > > > Catch ex as AseException
>> > > > > > lblMsg.Text = ex.Message
>> > > > > > lblMsg.Visible = "True"
>> > > > > > Finally
>> > > > > > cmd.Dispose()
>> > > > > > ClearSelections()
>> > > > > > End Try
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > >
>> > > > >
>> > > >
>> > > >
>> > >
>> > >
>> >
>> >
>>
>>

Prakash

[Paul Vero [Sybase]]

Is this for ADO.NET Provider?

-Paul

"Prakash" <mydear...@hotmail.com> wrote in message
news:4a13188d$1@forums-1-dub...

[KASH]

Yes, ASEClient 12.5

On Jun 18, 3:18 pm, "Paul Vero [Sybase]" <pv...@nospam.com> wrote:
> Is this for ADO.NET Provider?
>
> -Paul
>

> "Prakash" <mydearprak...@hotmail.com> wrote in message

> >>> "Germano" <Germano_Si...@Brown.edu> wrote in message

> >>>news:3fc3b755$1@forums-2-dub...
> >>> > It looks like I'm hitting some limit.
>
> >>> > Is there a limit on the number of parameters I can bind
> >>> > when calling a stored procedure?
>
> >>> > I put the code back to the way it was yeterday and it
> >>> > works fine. I now start adding one by one and it fails
> >>> > when I add parameter number 62, no matter which one.
>

> >>> > "Ashish Mahajan" <ashishmaha...@nospam.com> wrote in
> >>> > messagenews:3fc3a145$1@forums-1-dub...

> >>> > > It is not obvious from your code and sql why you would
> >>> > get this error... Can
> >>> > > you generate trace by using the trace events as in
> >>> "Advanced" sample ? If
> >>> > > you have ever used Ribo (TDS sniffer) a TDS trace
> >>> > > would be great. If not just the ado.net trace would be
> >>> > > good. Another way to track it would be to revert your
> >>> > changes, make it work again
> >>> > > and then add columns one or two at a time. That way
> >>> > > you might be able to isolate the issue.
>
> >>> > > Thanks,
>
> >>> > > Ashish
>

> >>> > > "Germano" <Germano_Si...@Brown.edu> wrote in message

> >>> > >news:3fc3922c$1@forums-1-dub...
> >>> > > > Ashish,
>
> >>> > > > This has been working fine until I had to modify the
> >>> > table, the SP and the
> >>> > > > ASP code to add a few more columns this morning.
> >>> That's when it stopped
> >>> > > > working.
>
> >>> > > > Here a re the columns that I added to the table:
>
> >>> > > >     @phone_area_code  char(3),
> >>> > > >     @phone_number     char(7),
> >>> > > >     @email_address    char(60),
> >>> > > >     @major_code1      char(7),
> >>> > > >     @major_code2      char(7),
> >>> > > >     @major_code3      char(7),
>

> >>> > > > "Ashish Mahajan" <ashishmaha...@nospam.com> wrote in
> >>> > > > messagenews:3fc3902f$1@forums-1-dub...

> >>> > > > > Can you send me the text of the stored proc ?
> >>> > > > > I assume that the line causing this exception is
> >>> cmd.ExecuteNonQuery()
> >>> > > > > Can you also send me the code that is used to bind
> >>> all the parameters.
>
> >>> > > > > Thanks,
>
> >>> > > > > Ashish
>

> >>> > > > > "Germano" <Germano_Si...@Brown.edu> wrote in
> >>> > > > > messagenews:3fc38ed3$1@forums-1-dub...

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

Yes

[Paul Vero [Sybase]]

Hi - what is the exact version - get fileversion
from Sybase.Data.AseClient.dll

There are a few known issues resolved with current release - so maybe
you're hitting one of these.

-Paul

"KASH" <prakash....@gmail.com> wrote in message
news:9807af8c-3ff2-48d3...@e18g2000vbe.googlegroups.com...