| Subject | Re: [firebird-support] Firebird and Windows 7 |
|---|---|
| Author | Helen Borrie |
| Post date | 2009-09-18T22:42:56Z |
At 07:31 AM 19/09/2009, you wrote:
Does your own application code define some custom errors relating to your own private licensing scheme, that sucks up certain attach errors and spits out an "invalid license" message?
If not, then the next best bet is that the app is trying to connect using an InterBase client library. IBO creates EIB_ISCError exceptions when an API request returns an exception. It gets the message text for the exception from the client library and delivers it along with the ISC code. I don't know what text the InterBase client dll delivers these days...but this is most likely to be a Firebird exception whose ISC code is being interpreted out of context by the IB client library.
If you are seeing an ISC code, check it against the list of Firebird error codes in the document http://www.firebirdsql.org/doc/contrib/fb_2_0_errorcodes.pdf to find out the message text is that is associated with the real problem that is causing the Firebird attach request to fail. Of course, fix up the client environment so that the app loads the correct client DLL.
./heLen
>I am trying to connect from my Delphi app using IBOjects to a Firebird 2.0.5 database running on a linux server. My app is running on 64-bit Windows 7. I am getting "Could not connect to database. Invalid license information" errors. What might be causing this?That error message text doesn't exist in either Firebird or IBO. Firebird doesn't have any licence-checking and IBO has an entirely different response to running application code compiled from an IBO evaluation version.
Does your own application code define some custom errors relating to your own private licensing scheme, that sucks up certain attach errors and spits out an "invalid license" message?
If not, then the next best bet is that the app is trying to connect using an InterBase client library. IBO creates EIB_ISCError exceptions when an API request returns an exception. It gets the message text for the exception from the client library and delivers it along with the ISC code. I don't know what text the InterBase client dll delivers these days...but this is most likely to be a Firebird exception whose ISC code is being interpreted out of context by the IB client library.
If you are seeing an ISC code, check it against the list of Firebird error codes in the document http://www.firebirdsql.org/doc/contrib/fb_2_0_errorcodes.pdf to find out the message text is that is associated with the real problem that is causing the Firebird attach request to fail. Of course, fix up the client environment so that the app loads the correct client DLL.
./heLen