Mega Search
23.2 Million


Sign Up

Make a donation  
Interbase XE3 - DriverAssemblyLoader property not set [Edit]  
News Group: embarcadero.public.interbase.general

Good day everyone,

I am trying to connect to Interbase XE3 with ADO.NET provider version 11.0.5000.0 using the following connection string:

{code}DriverName=Interbase;Database=192.168.126.131:c:\\employee.gdb;RoleName=RoleName;User_Name=SYSDBA;Password=masterkey;SQLDialect=3;DriverAssemblyLoader=Borland.Data.TDBXClientDriverLoader,Borland.Data.DbxCommonDriver,Version=11.0.5000.0,Culture=neutral,PublicKeyToken=91d62ebb5b0d1b1b;MetaDataAssemblyLoader=Borland.Data.TDBXInterbaseMetaDataCommandFactory,Borland.Data.DbxReadOnlyMetaData,Version=11.0.5000.0,Culture=neutral,PublicKeyToken=91d62ebb5b0d1b1b;GetDriverFunc=getSQLDriverINTERBASE;LibraryName
=dbxint30.dll;VendorLib=GDS32.DLL{code}

but I get exception that says:

*DriverAssemblyLoader property not set*

despite the fact that, as you can see it is already written in the connection string.

I have tried the same with 64 bit Interbase instance in Windows Server 2008 R2 (x64) and 32 bit Interbase instance in Windows XP (x86), and also with Interbase 2007 on Windows XP (x86) but got same exception.

And if I try new ADO.NET provider (version 16.0.0.0 instead of 11.0.5000.0) I get this error:

http://i.imgur.com/138ci5s.jpg

But with the command *sn -T Borland.Data.DbxCommonDriver.dll* you get this result:

Public key token is 91d62ebb5b0d1b1b

In addition, I have tried both Borland.Data.TAdoDbxProviderFactory.Instance.CreateConnection() and new Borland.Data.TAdoDbxConnection()

Could anyone help me to successfully connect to Interbase X3 (or 2007) through ADO.NET provider?

Edited by: Anatoly Sova on Oct 15, 2014 1:52 PM

Vote for best question.
Score: 0  # Vote:  0
Date Posted: 15-Oct-2014, at 1:52 PM EST
From: Anatoly Sova
 
Re: Interbase XE3 - DriverAssemblyLoader property not set [E  
News Group: embarcadero.public.interbase.general
> {quote:title=quinn wildman wrote:}{quote}
> Is the InterBase client installed?

Thank you for reply. Yes, it is installed.

> 
> In the directory where the ADO.NET driver gets installed there is a 
> readme type document. Have you looked at it?

Yes, I did. Of course, I have put this string:



into machine.config file under , and, as you can see, connection string is in the format this readme suggests (I have tried both with DriverAssemblyLoader part in connection string and without it).

Moreover, I have tried to put same string in 4 machine.config files: two for v2.0 and v4.0 in FRAMEWORK folder and for v2.0 and v4.0 in FRAMEWORK64 folder inside Windows\Microsoft.NET and got the same result. Googling also did not help me.

Vote for best answer.
Score: 0  # Vote:  0
Date Posted: 16-Oct-2014, at 7:13 PM EST
From: Anatoly Sova
 
Re: Interbase XE3 - DriverAssemblyLoader property not set [E  
News Group: embarcadero.public.interbase.general
Is the InterBase client installed?

In the directory where the ADO.NET driver gets installed there is a 
readme type document. Have you looked at it?

Anatoly Sova wrote:
> Good day everyone,
>
> I am trying to connect to Interbase XE3 with ADO.NET provider version 11.0.5000.0 using the following connection string:
>
> {code}DriverName=Interbase;Database=192.168.126.131:c:\\employee.gdb;RoleName=RoleName;User_Name=SYSDBA;Password=masterkey;SQLDialect=3;DriverAssemblyLoader=Borland.Data.TDBXClientDriverLoader,Borland.Data.DbxCommonDriver,Version=11.0.5000.0,Culture=neutral,PublicKeyToken=91d62ebb5b0d1b1b;MetaDataAssemblyLoader=Borland.Data.TDBXInterbaseMetaDataCommandFactory,Borland.Data.DbxReadOnlyMetaData,Version=11.0.5000.0,Culture=neutral,PublicKeyToken=91d62ebb5b0d1b1b;GetDriverFunc=getSQLDriverINTERBASE;LibraryNa
me
> =dbxint30.dll;VendorLib=GDS32.DLL{code}
>
> but I get exception that says:
>
> *DriverAssemblyLoader property not set*
>
> despite the fact that, as you can see it is already written in the connection string.
>
> I have tried the same with 64 bit Interbase instance in Windows Server 2008 R2 (x64) and 32 bit Interbase instance in Windows XP (x86), and also with Interbase 2007 on Windows XP (x86) but got same exception.
>
> And if I try new ADO.NET provider (version 16.0.0.0 instead of 11.0.5000.0) I get this error:
>
> http://i.imgur.com/138ci5s.jpg
>
> But with the command *sn -T Borland.Data.DbxCommonDriver.dll* you get this result:
>
> Public key token is 91d62ebb5b0d1b1b
>
> In addition, I have tried both Borland.Data.TAdoDbxProviderFactory.Instance.CreateConnection() and new Borland.Data.TAdoDbxConnection()
>
> Could anyone help me to successfully connect to Interbase X3 (or 2007) through ADO.NET provider?
>
> Edited by: Anatoly Sova on Oct 15, 2014 1:52 PM
>

Vote for best answer.
Score: 0  # Vote:  0
Date Posted: 16-Oct-2014, at 10:57 AM EST
From: quinn wildman