Open Forum

We are on V2018 CU5 and are having a problem with any templates for screen 01.010 that reference one particular report format.    The problem happens on a heavily customized Detailed General Ledger report (01.620) that was customized to add Customer, Vendor, PJProj and GLTran (long story).    The report has been running fine for two years, but recently has begun to cause problems.

Several users, but not all users, are reporting that using templates for this particular report format causes the dreaded "ROI.EXE not working" error, and leaves a RptRuntime record stuck in the table.   The ROI.EXE error persists when running that same report manually - i.e. without a template but using the same selections as the template - if the RptRuntime record from the previous crash isn't cleared out of the RptRuntime table when you try to run the report.

The weirdness is that the report format runs fine when run without the template and using the same report/selection/options/sort settings as the template.   I and numerous other users can run the report with those same offending report templates without error even though those particular templates cause a problem for several specific users.  

I've deleted the report templates several times, and resaved them.   Same effect - I can run the report with these templates just fine, but the problem users still get the ROI.EXE error after installing the updated reports..  Note that when I save report templates, I do NOT include current printer settings.

I've reviewed the Crystal report format, and reset the Database Location, and then verified the database.     When retesting on re-established templates, there is no change in behavior - i.e. the error on "ROI.EXE not working" persists.

I've combed through the Crystal report format to try to find a setting within the report format itself that might be saving printer settings, and can't find anything.

I'm out of ideas on how to troubleshoot this problem.    It would be a very long process to recreate the report, so I really don't want to do that if I can figure out what's triggering the error.

Can anyone offer some suggestions on other things I can try to resolve the issue?

Best regards,

------------------------------
Gail Jones-Nemeth
Financial Systems Analyst
Creative Associates Int'l
Chevy Chase MD
------------------------------

Did you try opening the report and File-->Save As to the latest version?  Perhaps it's in an old version of Crystal's file format and just needs an update.

Joe

------------------------------
Joe Miller
Director of Systems Architecture
Harrison, Walker & Harper
Paris TX
------------------------------

Original Message:
Sent: Jan 21, 2022 02:00 PM
From: Gail Jones-Nemeth
Subject: Crystal report/Template weirdness

We are on V2018 CU5 and are having a problem with any templates for screen 01.010 that reference one particular report format.    The problem happens on a heavily customized Detailed General Ledger report (01.620) that was customized to add Customer, Vendor, PJProj and GLTran (long story).    The report has been running fine for two years, but recently has begun to cause problems.

Several users, but not all users, are reporting that using templates for this particular report format causes the dreaded "ROI.EXE not working" error, and leaves a RptRuntime record stuck in the table.   The ROI.EXE error persists when running that same report manually - i.e. without a template but using the same selections as the template - if the RptRuntime record from the previous crash isn't cleared out of the RptRuntime table when you try to run the report.

The weirdness is that the report format runs fine when run without the template and using the same report/selection/options/sort settings as the template.   I and numerous other users can run the report with those same offending report templates without error even though those particular templates cause a problem for several specific users.

I've deleted the report templates several times, and resaved them.   Same effect - I can run the report with these templates just fine, but the problem users still get the ROI.EXE error after installing the updated reports..  Note that when I save report templates, I do NOT include current printer settings.

I've reviewed the Crystal report format, and reset the Database Location, and then verified the database.     When retesting on re-established templates, there is no change in behavior - i.e. the error on "ROI.EXE not working" persists.

I've combed through the Crystal report format to try to find a setting within the report format itself that might be saving printer settings, and can't find anything.

I'm out of ideas on how to troubleshoot this problem.    It would be a very long process to recreate the report, so I really don't want to do that if I can figure out what's triggering the error.

Can anyone offer some suggestions on other things I can try to resolve the issue?

Best regards,

------------------------------
Gail Jones-Nemeth
Financial Systems Analyst
Creative Associates Int'l
Chevy Chase MD
------------------------------

Gail, if you're still having this issue, have one of the users re-do their default printer and try the report again. We upgraded and had lots of these issues. If it's working for some users and not others, this may help.

Steve

------------------------------
Steve Smith
ERP Application Manager
Grain Millers
Eden Prairie MN
------------------------------

Original Message:
Sent: Jan 21, 2022 02:00 PM
From: Gail Jones-Nemeth
Subject: Crystal report/Template weirdness

We are on V2018 CU5 and are having a problem with any templates for screen 01.010 that reference one particular report format.    The problem happens on a heavily customized Detailed General Ledger report (01.620) that was customized to add Customer, Vendor, PJProj and GLTran (long story).    The report has been running fine for two years, but recently has begun to cause problems.

Several users, but not all users, are reporting that using templates for this particular report format causes the dreaded "ROI.EXE not working" error, and leaves a RptRuntime record stuck in the table.   The ROI.EXE error persists when running that same report manually - i.e. without a template but using the same selections as the template - if the RptRuntime record from the previous crash isn't cleared out of the RptRuntime table when you try to run the report.

The weirdness is that the report format runs fine when run without the template and using the same report/selection/options/sort settings as the template.   I and numerous other users can run the report with those same offending report templates without error even though those particular templates cause a problem for several specific users.

I've deleted the report templates several times, and resaved them.   Same effect - I can run the report with these templates just fine, but the problem users still get the ROI.EXE error after installing the updated reports..  Note that when I save report templates, I do NOT include current printer settings.

I've reviewed the Crystal report format, and reset the Database Location, and then verified the database.     When retesting on re-established templates, there is no change in behavior - i.e. the error on "ROI.EXE not working" persists.

I've combed through the Crystal report format to try to find a setting within the report format itself that might be saving printer settings, and can't find anything.

I'm out of ideas on how to troubleshoot this problem.    It would be a very long process to recreate the report, so I really don't want to do that if I can figure out what's triggering the error.

Can anyone offer some suggestions on other things I can try to resolve the issue?

Best regards,

------------------------------
Gail Jones-Nemeth
Financial Systems Analyst
Creative Associates Int'l
Chevy Chase MD
------------------------------