Subject | Re: FireBird Embedded DllNotFoundException |
---|---|
Author | omertasoft |
Post date | 2008-03-12T06:26:44Z |
--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@...>
wrote:
data access driver wants to load...some interfaces can load either
name.)
I don't think this must be done. All other clients use it as is and
it works.
Yes, it is in the same directory.
have full servers and regular clients installed and are not actually
accessing the embedded server at all.
Nope, they all have it working fine, firebird is the only database in
the application and it's the core component, if they are not
accessing it they can't use the app. And my test machines work in the
same way too, and I never installed the full server at all.
people in the net-provider list who have done this deployment before
and can help out with tricks and tips.
Thanks for the reply
wrote:
>above
> At 02:16 PM 12/03/2008, you wrote:
> >Hi,
> >
> >I read the archives and understand that most of the time, the
> >issue has to do with fbembed.dll or one of icu*.dll files notbeing
> >in the right folder. My situation is a little different. I have anfbembed.dll,
> >msi package that does the installation which copies the
> >FireBirdClient.dll and 3 icu dll's to the applications bin folder.gds32.dll (which one depends on the name of the library that your
>
> 1. The file fbembed.dll should be renamed to fbclient.dll or
data access driver wants to load...some interfaces can load either
name.)
I don't think this must be done. All other clients use it as is and
it works.
> 2. The renamed fbembed.dll should be in the same directory as theapplication executable (not in the \bin\ directory).
Yes, it is in the same directory.
> If your data access driver is the Firebird .NET driver then ask inthe firebird-net-provider list exactly which name you should use.
>and/or it was located in \bin\. Perhaps those other machines already
>
> >Our clients successfully installed our app with the msi file,
>
> They should have had problems too, if the library was not renamed
have full servers and regular clients installed and are not actually
accessing the embedded server at all.
Nope, they all have it working fine, firebird is the only database in
the application and it's the core component, if they are not
accessing it they can't use the app. And my test machines work in the
same way too, and I never installed the full server at all.
> >however2.0
> >there is one specific client who has windows 2003 server intalled
> >boxes (2 of them), and the same application failed to create the
> >database on both machines (they are both fresh installs with .NET
> >installed), the error is as followsto do it. It's better than trying to guess...and there are plenty of
> >
> >----------------------------------------------------------
> >[...snip... looks like .NET Provider tracking]
> >----------------------------------------------------------
> >
> >I checked the application folder and all 5 dll's are in the folder
> >(fbembed, FireBirdClient and 3 icu's)
>
> Try studying the Fb 1.5, 2.0 or 2.1 release notes for the right way
people in the net-provider list who have done this deployment before
and can help out with tricks and tips.
>that's right, i probably should have asked in firebird-net list
> ./heLen
>
Thanks for the reply