> > 4. Connecting to Firebird 3.0 Alpha 2 (LtColRDSChauhan) > 5. Re: Connecting to Firebird 3.0 Alpha 2 (Mark Rotteveel) > 6. Re: Connecting to Firebird 3.0 Alpha 2 (Norbert Saint Georges) >
> > Message: 5 > Date: Mon, 07 Jul 2014 18:06:38 +0200 > From: Mark Rotteveel <m...@lawinegevaar.nl> > Subject: Re: [Firebird-net-provider] Connecting to Firebird 3.0 Alpha > 2 > To: "For users and developers of the Firebird .NET providers" > <firebird-net-provider@lists.sourceforge.net> > Message-ID: <53bac58e.70...@lawinegevaar.nl> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > On 7-7-2014 15:43, LtColRDSChauhan wrote: > > Hi, > > > > 1. I attempted to migrate from Firebird 3.0 Alpha 1 to Alpha 2. After > > a backup / restore I'm not able to connect to the database using .NET > > Provider. I've the following updated in the Firebird Config file : > > > > UserManager = Legacy_UserManager > > > > AuthClient = Srp, Win_Sspi, Legacy_Auth > > > > > > 2. FlameRobin connects fine. > > > > 3. Please help. > > When you install Firebird 3 - unless you already enabled legacy > authentication in the installer - you will only have a user account in > the new SRP authentication model. As you edited the firebird.conf later, > you currently do not have a legacy authentication user. > > To fix this, you need to > 1) Edit firebird.conf again and > 1a)set the UserManager to Legacy_UserManager: > > UserManager = Legacy_UserManager > > 1b) Set WireCrypt to Enabled (instead of Required), or even Disabled so > that the server doesn't require encryption > > WireCrypt = Enabled > > 2) Restart Firebird (not 100% sure if necessary) > > 3) Next you need to create another SYSDBA account (using gsec) so it > also exists as a legacy user. I am not 100% sure if you only need to do > "gsec -user sysdba -password masterkey", or that you explicitly need to > do "add sysdba -pw masterke" from the gsec prompt. > > No luck. Still could not connect to Firebird 3.0 Alpha 2. Could though revert back to Alpha 1 successfully. > The reason Flamerobin works is that it uses the Firebird 3 fbclient.dll, > so it automatically supports the new authentication model and encryption. > > Mark > -- > Mark Rotteveel > > > > ------------------------------ > > Message: 6 > Date: Mon, 7 Jul 2014 19:40:14 +0300 > From: "Norbert Saint Georges" <n...@tetrasys.eu> > Subject: Re: [Firebird-net-provider] Connecting to Firebird 3.0 Alpha > 2 > To: "For users and developers of the Firebird .NET providers" > <firebird-net-provider@lists.sourceforge.net> > Message-ID: <666624F4077B9243BF64C0A5B64D49DA189125@sharepoint> > Content-Type: text/plain; charset="utf-8" > > Hi, > > force good client library for Firebird? > eg "customer library = j: \ firebird-3 \ fbclient30.dll;" in the > connection string. > > Tried setting ClientLibrary in the connection string. No luck, again. > > > > > Norbert Saint Georges > > > > TetraSys Oy > > Bergantie 69, FI-02540 Kylm?l? > > Tel. : +358 (0) 400 27 25 18 > > E- mail : n...@tetrasys.eu <mailto:taru.kaukova...@tetrasys.eu> > > _____________________________
------------------------------------------------------------------------------
_______________________________________________ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
