Sage 100

Perplexing paperless printing issue. Sage 100 2015.3 We have a client who is continually running into form corruption using emailing via paperless. See the attached error message. The error occurs when trying to print a form that is set to be emailed using paperless. It will work for a while and then the next time they go to print the error 20 pops up. It appears to be random. We had the user try their TS instead of the workstation to see if the problem was tied to the workstation but it happened on the TS, too. Their are no errors in emailing the documents. The fix is to create a new form code using a copy of the original crystal form report. It works for a while than bam.

I would try this even though it is not the same line number, it's close and it wouldn't hurt to do this if you haven't tried it yet. I would also delete all of the user-specific records for that form code and company in SY_ReportSetting. The Form/Report code referenced in SY_LastFormUsed.m4t is invalid. Delete the record in SY_LastFormUsed.m4t for the affected report, company and user. Determine the company key in SY_Company.m4t. Note: This step is not necessary if only one company code exists. Expand Modules, Library Master, and Utilities. Double-click Data File Display and Maintenance (DFDM). Select ..\Mas90\Mas_System\Sy_Company.m4t. Click the Key lookup button, and select the affected company code. Note the company key (for example: 0000000003) Determine the company key in SY_Company.m4t. Expand Modules, Library Master, and Utilities. Double-click Data File Display and Maintenance (DFDM). Select ..\Mas90\Mas_System\Sy_User.m4t. Click the Key lookup button, and select the affected user code. Note the user key (for example: 0000000008) Delete the record in SY_LastFormUsed.m4t for the affected report, company and user. Expand Modules, Library Master, and Utilities. Double-click Data File Display and Maintenance (DFDM). In DFDM, select ..\Mas90\Mas_System\SY_LastFormUsed.m4t. Click the Key lookup button and select a record that matches the module, company key, and report name. Click the Delete button. Test the report. If nothing happens, repeat step 3 again for each report setting until the report opens. Close DFDM. Run the report again

The above process fixes the issue until it breaks again. We are trying to determine the cause of it ""breaking"". The usual Sage scapegoats - redirected printers, multiple PDF converter printers have all been eliminated.

Hi - has anyone asked you to debug when you get this error, to try to understand what (exactly) the error 20 is ? (debug and print tmp$ ) Jeff

Actually no - we haven't used the print tmp$ command. We'll give it a look.

This is happening about once per week. Sometimes more frequently. Other times it may go a couple of weeks.

2 common problems I have run into: 1. Sage PDF Printer port is not set to local port Sage; 2. Multiple Sage PDF Printers installed (from upgrades or redirects). Sage Port-hell does have a document with more solutions. I will see if I kept a copy...I doubt I will find it on their system.