At 02:16 PM 12/03/2008, you wrote:

>Hi,
>
>I read the archives and understand that most of the time, the above
>issue has to do with fbembed.dll or one of icu*.dll files not being
>in the right folder. My situation is a little different. I have an
>msi package that does the installation which copies the fbembed.dll,
>FireBirdClient.dll and 3 icu dll's to the applications bin folder.

1. The file fbembed.dll should be renamed to fbclient.dll or gds32.dll (which one depends on the name of the library that your data access driver wants to load...some interfaces can load either name.)

2. The renamed fbembed.dll should be in the same directory as the application executable (not in the \bin\ directory).

If your data access driver is the Firebird .NET driver then ask in the firebird-net-provider list exactly which name you should use.

>Our clients successfully installed our app with the msi file,

They should have had problems too, if the library was not renamed and/or it was located in \bin\. Perhaps those other machines already have full servers and regular clients installed and are not actually accessing the embedded server at all.

>however
>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 2.0
>installed), the error is as follows
>
>----------------------------------------------------------
>[...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 to do it. It's better than trying to guess...and there are plenty of people in the net-provider list who have done this deployment before and can help out with tricks and tips.

./heLen