Re: [firebird-support] invalid request BLR 623; LTRIM not defined; entrypoint not found.

[Helen Borrie hele...@iinet.net.au [firebird-support]]

At 05:44 p.m. 29/09/2015, s hj senthile...@gmail.com [firebird-support] wrote:

>Occasionally (not always) I get the following error when I run some stored 
>procedures or views (database objects) that use the LTRIM function:
>
>
>
>can't format message 13:896 - message file C:Windows\firebird.msg not found; 
>invalid request BLR at offset 623; function LTRIM is not defined; module name 
>or entrypoint could not be found; Error while parsing procedure XXX 
>(stored_procedure name) ;
>-
>
>(I get this both in IB Expert and SSRS)Â 
>
>This said I am able to access other database objects that do not use LTRIM 
>function!!
>
>My temporary workaround:
>
>Sometimes I restart the machine, and am able to run these same stored 
>procedures and views that threw this error sometime back.
>At other times, I restart the machine a couple of times, and am able to access 
>these views and stored procedures.
>
>At some other times, I restart the machine many times, still not able to run 
>the database objects. I get frustrated and quit for the day.
>When I open the machine fresh the next morning, I am able to run these objects 
>again !!
>
>
>
>What could be the reason for this ? 

You have a messed-up installation.  It looks as though you have both a full 
server and an embedded setup.  In the embedded setup, you are missing the UDF 
libraries, which is where the server needs to find the entry point for the 
external function LTRIM, and firebird.msg, which contains the text of some 
external exceptions.

At the times when LTRIM works, I would say you are on the full server and the 
UDF libs are where they should be - in the UDF folder beneath the server's root 
directory.  If you want to use embedded instead of the full server, you'll need 
more than just the fbembed.dll sitting in the same directory as the 
application's exe file.  You'll need firebird.msg there too, and to create a 
copy of the ...\UDF folder directly beneath it.  You'll need to make sure 
everything belongs to Fb 2.5.  A message file from an older Fb version won't 
work properly with an Fb 2.5 client and/or server.

>And what will be the permanent solution ?

Well, first decide whether you're going to run the full server or embedded.  
You can keep the embedded installation if you want it for something;  but don't 
use a serverless protocol from the client for connecting to the database via 
the full server: use tcp/ip or wnet.  Then fbembed will behave like a remote 
client and won't try to attach to its embedded server.

>As I said earlier, this database is given by my client, and am not supposed to 
>modify anything (such as changing LTRIM to something else)

LTRIM is a bit of a pre-Fb 2.1 artifact, along with a multitude of other 
external scalar functions.  If it's the only external function being used, it 
might be worth considering altering the SP to use the internal function TRIM 
(with appropriate parameters) ( see 
http://www.firebirdsql.org/file/documentation/reference_manuals/reference_material/html/langrefupd25-intfunc-trim.html
 ).  It's just an idea.


Helen Borrie, Support Consultant, IBPhoenix (Pacific)
Author of "The Firebird Book" and "The Firebird Book Second Edition"
http://www.firebird-books.net
__ 

Re: [firebird-support] invalid request BLR 623; LTRIM not defined; entrypoint not found.

[s hj senthile...@gmail.com [firebird-support]]

Thanks very much Helen. I appreciate it.



To give a background, I use a 32-bit as well as a 64-bit client of Firebird
Database.

The reason is that I can work with a 32-bit client for the SSDT part of
Microsoft SSRS, and the 64-bit client for the Microsoft Report Manager.

This whole Firebird installation was done by an external application
installation that uses Delphi.  The Delphi application connects to the
Firebird Database using the 32-bit client. I later installed 64-bit client
to connect to Microsoft SSRS Report Manager.
-

So am not very familiar with the full-server or embedded set up at all; is
there any link that I can follow to remove the embedded set up?
Or any step by step instruction you can provide me to have just the
Full-Server set up ? Please let me know.

As I have already mentioned, I am not a Firebird Database developer (as far
as our company's client is concerned), so I cannot meddle with the LTRIM
part at all.

I have to be very careful while altering anything with the installation.  I
want to completely eliminate this LTRIM error ASAP.

On Tue, Sep 29, 2015 at 12:08 PM, Helen Borrie hele...@iinet.net.au
[firebird-support]  wrote:

>
>
> At 05:44 p.m. 29/09/2015, s hj senthile...@gmail.com [firebird-support]
> wrote:
>
> >Occasionally (not always) I get the following error when I run some
> stored procedures or views (database objects) that use the LTRIM function:
> >
> >--
> >
> >can't format message 13:896 - message file C:Windows\firebird.msg not
> found; invalid request BLR at offset 623; function LTRIM is not defined;
> module name or entrypoint could not be found; Error while parsing procedure
> XXX (stored_procedure name) ;
> >--
> >
> >(I get this both in IB Expert and SSRS)Â
> >
> >This said I am able to access other database objects that do not use
> LTRIM function!!
> >
> >My temporary workaround:
> >
> >Sometimes I restart the machine, and am able to run these same stored
> procedures and views that threw this error sometime back.
> >At other times, I restart the machine a couple of times, and am able to
> access these views and stored procedures.
> >
> >At some other times, I restart the machine many times, still not able to
> run the database objects. I get frustrated and quit for the day.
> >When I open the machine fresh the next morning, I am able to run these
> objects again !!
> >
> >
> >
> >What could be the reason for this ?
>
> You have a messed-up installation. It looks as though you have both a full
> server and an embedded setup. In the embedded setup, you are missing the
> UDF libraries, which is where the server needs to find the entry point for
> the external function LTRIM, and firebird.msg, which contains the text of
> some external exceptions.
>
> At the times when LTRIM works, I would say you are on the full server and
> the UDF libs are where they should be - in the UDF folder beneath the
> server's root directory. If you want to use embedded instead of the full
> server, you'll need more than just the fbembed.dll sitting in the same
> directory as the application's exe file. You'll need firebird.msg there
> too, and to create a copy of the ...\UDF folder directly beneath it. You'll
> need to make sure everything belongs to Fb 2.5. A message file from an
> older Fb version won't work properly with an Fb 2.5 client and/or server.
>
> >And what will be the permanent solution ?
>
> Well, first decide whether you're going to run the full server or
> embedded. You can keep the embedded installation if you want it for
> something; but don't use a serverless protocol from the client for
> connecting to the database via the full server: use tcp/ip or wnet. Then
> fbembed will behave like a remote client and won't try to attach to its
> embedded server.
>
> >As I said earlier, this database is given by my client, and am not
> supposed to modify anything (such as changing LTRIM to something else)
>
> LTRIM is a bit of a pre-Fb 2.1 artifact, along with a multitude of other
> external scalar functions. If it's the only external function being used,
> it might be worth considering altering the SP to use the internal function
> TRIM (with appropriate parameters) ( see
> http://www.firebirdsql.org/file/documentation/reference_manuals/reference_material/html/langrefupd25-intfunc-trim.html
> ). It's just an idea.
>
> Helen Borrie, Support Consultant, IBPhoenix (Pacific)
> Author of "The Firebird Book" and "The Firebird Book Second Edition"
> http://www.firebird-books.net
> __
>
> 
>

[firebird-support] invalid request BLR 623; LTRIM not defined; entrypoint not found.

[s hj senthile...@gmail.com [firebird-support]]

I am completely new to Firebird Database; I am working on a database *Firebird
2.5* that already exists; I retrieve the stored procedures and views
(database objects)
from this database to develop reports in Microsoft SSRS. I use Windows 7
Operating System.






Occasionally (not always) I get the following error when I run some stored
procedures or views (database objects) that use the LTRIM function:





can't format message 13:896 - message file C:Windows\firebird.msg not
found; invalid request BLR at offset 623; function LTRIM is not defined;
module name or entrypoint could not be found; Error while parsing procedure
XXX (stored_procedure name) ;
-


(I get this both in IB Expert and SSRS)


This said I am able to access other database objects that do *not* use
LTRIM function!!


*My temporary workaround:*


Sometimes I restart the machine, and am able to run these same stored
procedures and views that threw this error sometime back.
At other times, I restart the machine a couple of times, and am able to
access these views and stored procedures.


At some other times, I restart the machine many times, still not able to
run the database objects. I get frustrated and quit for the day.
When I open the machine fresh the next morning, I am able to run these
objects again !!






*What could be the reason for this ? And what will be the permanent
solution ?*


As I said earlier, this database is given by my client, and am *not*
supposed to modify anything (such as changing LTRIM to something else)



Any suggestion will be greatly appreciated.