BLR 623 invalid request - LRTRIM is not defined - module name or entrypoint could not be found [CORE4960] #5251
Comments
Modified by: Sen (sen)description: I am completely new to Firebird Database; I am working on a Firebird 2.5 database 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: Invalid token. (I get this both in IB Expert and SSRS) This said I am able to access other database objects that do not use LRTRIM 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? This database is given by my client, and am not supposed to modify anything (such as changing LTRIM to something else). I can just use the existing objects to develop reports. Can you provide me a step-by-step solution to resolve this issue? I am not able to move on without solving this issue permanently. => I am completely new to Firebird Database; I am working on a Firebird 2.5 database 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: Invalid token. (I get this both in IB Expert and SSRS) This said I am able to access other database objects that do not use LRTRIM 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? This database is given by my client, and am not supposed to modify anything (such as changing LRTRIM to something else). I can just use the existing objects to develop reports. Can you provide me a step-by-step solution to resolve this issue? I am not able to move on without solving this issue permanently. |
|
Commented by: Omacht András (aomacht) Hi Sen, you wrote about using LTRIM function, BUT the error message mentioned LRTRIM. Maybe you have a typo. |
Modified by: Sen (sen)description: I am completely new to Firebird Database; I am working on a Firebird 2.5 database 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: Invalid token. (I get this both in IB Expert and SSRS) This said I am able to access other database objects that do not use LRTRIM 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? This database is given by my client, and am not supposed to modify anything (such as changing LRTRIM to something else). I can just use the existing objects to develop reports. Can you provide me a step-by-step solution to resolve this issue? I am not able to move on without solving this issue permanently. => I am completely new to Firebird Database; I am working on a Firebird 2.5 database 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 LRTRIM function: Invalid token. (I get this both in IB Expert and SSRS) This said I am able to access other database objects that do not use LRTRIM 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? This database is given by my client, and am not supposed to modify anything (such as changing LRTRIM to something else). I can just use the existing objects to develop reports. Can you provide me a step-by-step solution to resolve this issue? I am not able to move on without solving this issue permanently. |
|
Commented by: Sen (sen) Hello Omacht, Yeah, I just corrected the typo. I actually got this error for LTRIM as well in the past; but now I am getting for LRTRIM |
|
Commented by: @mrotteveel This sounds more like a support question and therefor should be posted on the firebird-support maillinglist, and not as a bug report in the tracker. Also considering the question you asked earlier on stackoverflow (http://stackoverflow.com/questions/32840414/firebird-2-5-invalid-request-blr-623-ltrim-not-defined-entrypoint-not-found) are you sure you aren't still connecting to the wrong server? |
|
Commented by: Sen (sen) Hello Mark, I have a Local server (I checked this in the IB Expert Database Registration) ; the Client Library File I use is: gds32.dll Is this the server, you mean. As I had posted in StackOverflow, I have 2 Firebird clients - 32-bit client and a 64-bit client. The 32-bit is needed for the SSDT in SSRS, and the 64-bit client is needed for the Report Manager in SSRS. Can you please help me with this? Thanks. |
|
Commented by: Sen (sen) Hello Mark, 'Server' , you mean an instance of server - as we say in Microsoft SQL Server ? |
|
Commented by: @mrotteveel Please post your question to the firebird-support mailinglist, this is not the right place for this question. |
|
Commented by: Sen (sen) Hello Mark, I have already posted. I got some suggestion from Helen. But the conversation discontinued afterwards. I will forward that email to you. If you could suggest something it will be really helpful. |
|
Commented by: Sean Leyne (seanleyne) Edited/removed extra blank lines for readability. |
Modified by: Sean Leyne (seanleyne)description: I am completely new to Firebird Database; I am working on a Firebird 2.5 database 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 LRTRIM function: Invalid token. (I get this both in IB Expert and SSRS) This said I am able to access other database objects that do not use LRTRIM 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? This database is given by my client, and am not supposed to modify anything (such as changing LRTRIM to something else). I can just use the existing objects to develop reports. Can you provide me a step-by-step solution to resolve this issue? I am not able to move on without solving this issue permanently. => I am completely new to Firebird Database; I am working on a Firebird 2.5 database 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 LRTRIM function: Invalid token. (I get this both in IB Expert and SSRS) This said I am able to access other database objects that do not use LRTRIM 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? This database is given by my client, and am not supposed to modify anything (such as changing LRTRIM to something else). I can just use the existing objects to develop reports. Can you provide me a step-by-step solution to resolve this issue? I am not able to move on without solving this issue permanently. |
|
Commented by: Sen (sen) The issue has been resolved by Mark; you can see the solution posted here: |
Modified by: Sean Leyne (seanleyne)status: Open [ 1 ] => Resolved [ 5 ] resolution: Won't Fix [ 2 ] |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: Sen (sen)
I am completely new to Firebird Database; I am working on a Firebird 2.5 database 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 LRTRIM function:
Invalid token.
invalid request BLR at offset 623
function LRTRIM is not defined
module name or entrypoint could not be found
Error while parsing procedure XXXXXXX (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 LRTRIM 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?
This database is given by my client, and am not supposed to modify anything (such as changing LRTRIM to something else). I can just use the existing objects to develop reports.
Can you provide me a step-by-step solution to resolve this issue? I am not able to move on without solving this issue permanently.
The text was updated successfully, but these errors were encountered: