Any ideas how to fix?
Partially fixed with backing down Crystal Reports to 32-bit after an upgrade to 64-bit got through, but still having problems.
Huh? Crystal doesn't have a 64-bit version, there's nothing to "back down". But in any case, you're missing the DLL that that report wants, it needs to be copied from GL6xA to the Customization directory's GL6xA.
Hi Jay,
Earlier, we were getting error:
The database connector "crdb_p2bpipe.dll" could not be loaded.
We repaired it using the following steps:
a)Renamed the business object folder and runtime folder.
b) Ran a repair on the Sage 300 Program version 2023.
c) Reinstalled PU3. Then the error disappeared.
Now We are getting the same error on GL TB reports. Any idea will surely be appreciated.
Custom reports?
Its the standard GL trial balance report. Before we corrected the first error, none of the standards reports was printing. After correcting it, some reports like requisition can print but the GL reports are throwing the above error
I'm seeing this with several clients now with custom Crystal reports using ODBC Driver 18 for SQL. I have been unable to get any of the failing crystal reports to work and have resorted to downgrading their ODBC client to ODBC Driver 17. It works every time.
There is obviously something going on with that 18 driver and I'm wondering if there has been a recent windows update because I've had a few clients on the 18 driver for a while and this only recently started happening.
And just to confirm - your reports have the CSCOM table added to them? I just upgraded a client to 2024 with the ODBC Driver 18 version with a bunch of custom reports that all worked. But I did add CSCOM to each of them.
It's there in the subreport only. This payroll cheque report has been working fine with no changes for months. All of the sudden, this payroll run, it gives the can't find table error. No Sage updates, no changes to the report, it just stopped working and this is the third client I've had this happen to in the last 2 weeks. As soon as I downgrade the driver it works fine. Something is up.
It does need to be in the main report for Sage to do it's thing with swapping out the data source within the report.
I do hear what you're saying about downgrading the driver - not ignoring it, I just think that you should be setting up the report to let the Sage reporting interface help you as much as possible.
How many thousands of custom reports are out there that are going to have to be modified for CSCOM then that wete working fine prevously? I will test out your theory with this one and see. I am suspecting a recent windows security update is the root cause of this
FWIW, no one else is reporting this problem.
How do you get the company name at the top of your reports? ;)
I'm curious to see what you find.
I suspect they will.
This particular report is just a payroll check advice. The company name is a graphic.
Microsoft ODBC Driver 18 defaults to Encrypt=Yes and ODBC Driver 17 defaults to Encrypt=No/Optional
Changed my driver back to 18, added CSCOM to the main report, linked to the BKREG table. Same error:
Invalid argument for database. This is the same error the client has on their end. Both running a full install of Sage programs locally, both running Windows 11. There were a few windows security updates installed on my machine mid-February. I might try uninstalling them and see what happens
At this point it's just so much easier to install ODBC driver 17.
I have done many upgrades to the SQL 18 driver. I do know about this and always change it. That is not the issue.
seen all this behavior before; it was data corruption with invalid invisible characters;
you have cheques going to GL .... suspicious data flow
my 2 cents
No. That's not the issue. Look, this report has run fine for months on both the clients and my machine using ODBC driver 18 until today. No changes have been made to the report or to Sage. I have seen this pop up at three different clients in the last 2 weeks, all running the ODBC 18 client. All sorts of different custom reports. Looked at the reports frontwards, backward and sideways and tried multiple different things to get them working. All failed. You know what did work? Downgrading the ODBC client to anything less than 18. Because of the timing of this, I'm still leaning towards an windows update of some sort.
Has anyone experienced the error on sage standard reports? My error is on the normal trial balance reports.
Question for you. Is this running on a Windows 11 machine?
error is both in the application server :Windows Server 2022 Standard and all the workstations are running windows 11. All was running fine until the server was restarted.. seems there was some applications installed and From the control panel, we identified that new C++ library was installed. after repairing the first error, we got this error now
Had another one today.4th different client. Stock Orchid EFT options report. Sage 2023 with SQL driver 18. Something is going on out there.
Did you manage to fix the issue - i have the same issue - custom report works from sage 2014 all the way to 2022 version but doesnt work on 2023 version PU5.
No. I haven't had any new ones pop up since that rash of errors 3 weeks ago. The only thing that worked in those cases was to downgrade the ODBC driver to version 17. I just downloaded the driver, installed, removed the ODBC connection and recreated with the 17 driver. Worked in every case.
Hi Darren
So in your system DSN there is only one entry with 17 driver which you use for DB setup and all reporting to work ?
Or you have database setup linked using driver 18 and for reporting to work you have driver 17 as both drivers can co exist according to Microsoft website article below.
The Microsoft ODBC Driver 18 for SQL Server can be installed side by side with Microsoft ODBC Driver 17 for SQL Server.
*Community Hub is the new name for Sage City