Sybase ADO .NET - 30002 error

Author

30002 error

Germano

2005-12-01, 8:25 pm

Hi,

Can anyone confirm that the 30002 error goes away when upgrading to a newer
version of the driver?

In my case, I'll be going from 1.1327 to 1.1481

Thanks
Germano

Paul

2005-12-01, 8:25 pm

Hi Germano,

This will be hard to answer. Internal error 30002 occurs for various
reasons. It is an error mesg to inform that something is seriously wrong in
the Provider code and needs to be reported to Sybase Tech Support. If you
search the buglist for 30002, you will find that there were 4 bugs resolved
that involved internal error. I suggest you take a look at those
descriptions to see if they relate to your problem. I would defintely apply
the latest release.

It is always good to keep up with the releases since we are constantly
resolving customer reported problems and new features are added into the
product as well.

-Paul

"Germano" <Germano_Silva@Brown.edu> wrote in message
news:438f59b2@forums
-1-dub...
> Hi,
>
> Can anyone confirm that the 30002 error goes away when upgrading to a
newer

> version of the driver?
>
> In my case, I'll be going from 1.1327 to 1.1481
>
> Thanks
> Germano
>
>

Germano

2005-12-02, 9:24 am

I've installed EBF13008 on my local deesktop and was able to rebuild the
application just fine, but now when I deploy the application to a staging
server, I'm getting the famous "Unable to load DLL sybdrvado11.dll".

The main difference between the desktop and the server, is that I used the
setup program from the SDK1151 (EBF13008) to install the provider versus
just copying the DLL's to the staging server. The logic behind this, is that
I have other applications on that server that are still useing v1.1327 and I
don't want to rebuild them now, and I think if I use the setup to install
the new version, it will put them into GAC and it will probably affect the
others apps tha twere built with 11.327

My understanding is that if I deploy the two DLL's to the application's BIN
folder, it should work, but it does not.

"Paul" <Paul@sybase.com> wrote in message news:438fa588$1@foru
ms-1-dub...
> Hi Germano,
>
> This will be hard to answer. Internal error 30002 occurs for various
> reasons. It is an error mesg to inform that something is seriously wrong
> in
> the Provider code and needs to be reported to Sybase Tech Support. If you
> search the buglist for 30002, you will find that there were 4 bugs
> resolved
> that involved internal error. I suggest you take a look at those
> descriptions to see if they relate to your problem. I would defintely
> apply
> the latest release.
>
> It is always good to keep up with the releases since we are constantly
> resolving customer reported problems and new features are added into the
> product as well.
>
> -Paul
>
> "Germano" <Germano_Silva@Brown.edu> wrote in message
> news:438f59b2@forums
-1-dub...
> newer
>
>

Paul

2005-12-02, 1:24 pm

Hi Germano,

You installed the new stuff on the machine - and does the
Sybase.Data.AseClient.dll (1.1.481.0) and the associated
policy.1.1.Sybase.Data.AseClient.dll show up in the GAC?
I think you should be able to use this if you placed the DLLs in the bin
directory. But I think you need to gacutil the new files into the GAC in
order to use them. Was this done? Or did you just copy them over to the
staging server?

-Paul

"Germano" <Germano_Silva@Brown.edu> wrote in message
news:43906706$1@foru
ms-1-dub...
> I've installed EBF13008 on my local deesktop and was able to rebuild the
> application just fine, but now when I deploy the application to a staging
> server, I'm getting the famous "Unable to load DLL sybdrvado11.dll".
>
> The main difference between the desktop and the server, is that I used the
> setup program from the SDK1151 (EBF13008) to install the provider versus
> just copying the DLL's to the staging server. The logic behind this, is
that
> I have other applications on that server that are still useing v1.1327 and
I
> don't want to rebuild them now, and I think if I use the setup to install
> the new version, it will put them into GAC and it will probably affect the
> others apps tha twere built with 11.327
>
> My understanding is that if I deploy the two DLL's to the application's
BIN
> folder, it should work, but it does not.
>
> "Paul" <Paul@sybase.com> wrote in message news:438fa588$1@foru
ms-1-dub...
wrong[color=darkred]

you[color=darkred]
>
>

Germano

2005-12-03, 8:24 pm

I just copied the files to the staging server. I did not use the GAC
utility because I was afraid it would affect any application that is still
using an older version of the DLL's, isn't that the case or am I wrong in
assuming that?

Germano

"Paul" <Paul@sybase.com> wrote in message news:439085f9$1@foru
ms-1-dub...
> Hi Germano,
>
> You installed the new stuff on the machine - and does the
> Sybase.Data.AseClient.dll (1.1.481.0) and the associated
> policy.1.1.Sybase.Data.AseClient.dll show up in the GAC?
> I think you should be able to use this if you placed the DLLs in the bin
> directory. But I think you need to gacutil the new files into the GAC in
> order to use them. Was this done? Or did you just copy them over to the
> staging server?
>
> -Paul
>
> "Germano" <Germano_Silva@Brown.edu> wrote in message
> news:43906706$1@foru
ms-1-dub...
> that
> I
> BIN
> wrong
> you
>
>

Paul

2005-12-05, 1:25 pm

Hi Germano,

I think the gacutil will just register the assembly in the Global Cache
Assembly. So if the odler apps are using an older Provider, and it exists
somewhere on the machine then they should still use that assembly. gacutil
just adds teh new Provider and then when you reference that Provider with a
new application then it should work ok. I think maybe since it is not in
the cache, and you build with that refderence then maybe the system is
throwing the error when it checks things on the system relative to that
provider.

-Paul

"Germano" <Germano_Silva@Brown.edu> wrote in message
news:43923872$1@foru
ms-2-dub...
> I just copied the files to the staging server. I did not use the GAC
> utility because I was afraid it would affect any application that is still
> using an older version of the DLL's, isn't that the case or am I wrong in
> assuming that?
>
> Germano
>
> "Paul" <Paul@sybase.com> wrote in message news:439085f9$1@foru
ms-1-dub...
in[color=darkred]
the[color=darkred]
the[color=darkred]
staging[color=darkre
d]
versus[color=darkred
]
install[color=darkre
d]
news:438fa588$1@foru
ms-1-dub...[color=darkred]
If[color=darkred]
defintely[color=dark
red]
constantly[color=dar
kred]
a[color=darkred]
>
>

Sponsored Links