printing | Schulz Consulting

30 Ways to Fix Sage 100 “Data is not selected for report printing”

October 8, 2019 by Wayne Schulz

If you are working in Sage 100 or Sage 100cloud and encounter the message “Data is not selected for report printing” while trying to print a form or a report then you should look at this Sage knowledgebase article.

This comprehensive article lists 30 different reasons for the “Data is not selected” message as well as links to specific knowledge articles which can help you resolve any problems.

In some cases you may be recieving the message because there truly is no dataa to print ( if , say, your Sales Order has the “print picking sheet” box UN-checked ).

However, there are some other reasons that Sage outlines where you can also run into this issue unexpectedly and the steps to take to resolve the problem and get your Sage 100 form or report printing as expected.

Some issues that this article covers include:

Report settings have been filtered such that there are no eligible records
Corrupted, damaged, or missing SY_ReportEngine.pvc file
Report Settings for one Sage 100 user have changed
Previously known issue that has been patched in latest updates
Return of Goods Entry print box not checked
Data Corruption
Blank Records in the Masterfile that need to be deleted
E-mail PDF Delivery Option is not selected for vendor
Print Invoices checkbox not checked in AR or SO Invoice Defaults
Damaged User profile
“Default Special Items to Drop Ship” selected in SO Options
Using MultiBin and there are items not distributed to bins
Line items on Sales Order are Backordered or Quantity Ordered is zero (0)
SO_SalesOrderPrint.m4t data file may be corrupted
SY_ReportOption.m4t file contains corrupted values after upgrading to version 2015
Bank Reconciliation and Accounts Payable module not Integrated
E-mail was not selected for customer in Paperless setup
History files have been removed due to Years to Retain options
Need to Rebuild Sort Files for Work Order module
Module code was incorrectly entered
Prospect does not have a Customer ID
Reported issue which Sage Engineering is Currently Reviewing

For a full list of the issues related to this printing message please visit the Sage knowledgebase here – Error: “Data is not selected for Report Printing”

No Prompt To Update Payroll Checks After Printing – Sage 100 ERP 2013

March 27, 2014 by Wayne Schulz

Issue:

Sage 100 ERP 2013 – no prompt to update payroll checks after printing. This is happening on a Windows XP workstation though it’s not known if the issue is more widespread.

Can print AP checks from same workstation.
Resolution:

This may have several potential resolutions.

1. Run the WKSUPDATE from the WKSETUP folder. Starting with PU3(?) this program performs the below KB actions of moving the DLLs files for you.

Note: Resolved with program fix LM5002-T, which can be downloaded from the Sage Support Portal and then installed onto each workstation having this issue. This patch should have been included in Sage 100 ERP 2013 PU2+ though it’s likely you need to re-run workstation setup.

Sage 100 ERP 2013 Slow Printing Fix

June 17, 2013 by Wayne Schulz

Sage have just issued a patch for Sage 100 ERP 2013 which they say resolves various printing issues including reports that printing under Sage 100 ERP 2013 was noticeably slower than prior versions. This issue appears to have occurred within accounts payable check printing but some users have reported slow printing in other areas as well.

UPDATE JUNE 17, 2013: This patch was pulled for a minor correction. When installed some users were noticing that their version of Sage 100 ERP was showing an incorrect product update level. If , for example, you had installed Sage 100 ERP 2013 product update 2 – after you applied this hotfix your system would be showing you’d only applied through product update 1. This is purely cosmetic. Expect the hotfix to be reissued shortly.

For the patch login to Sage and search for program fix LM5004-T

Error 200 in SY_ReportCommon.pvc line 611 in 4.5 and line 596 in 4.4

April 9, 2012 by Wayne Schulz

Here’s a nice solution to a somewhat rare printing problem one of my 90 Minds group members ran into.
The problem appeared in Sage 100 ERP (Formerly Sage ERP MAS 90 and 200) Versions 4.40 and 4.50 versions. These systems both stopped printing ANYTHING from a Business Framework module (forms, reports) and started giving an error 200 in SY_ReportCommon.pvc line 611 in 4.5 and line 596 in 4.4.

Sage says to uninstall and reinstall WKSETUP. Did that. Reinstalled EVERYTHING in 4.4. Including up to PU8.
Here’s what worked:

Via – Alnoor Caassim – Call for Help

It’s trying to create the Crystal runtime object and for BF the main file behind that is CRAXDRT.DLL (the CRPE32.DLL is for legacy). Try to manually register that DLL which is typically in C:\Program Files (x86)\Business Objects\Common\3.5\Bin and the version for it laid down by MAS (as see in properties) is 11.5.something. If you get errors registering the DLL, look for multiple versions of it.

Contact Us