Sage 100

Unable to print SO_Invoice2.rpt. The data area passed to a system call is too small. Getting that trying to Print/PDF or Electronically Deliver somewhere over 100 invoices. First error is the ""Printer not activated, error code -30"". What's fun about this is that this only happens after about half an hour of steady printing/pdf'ing/emailing of invoices. I tried the usual paperless tricks anyway but this seems to be either an O/S issue or maybe a printer issue. But after half an hour??? System is 2013 Premium connecting through a 2008 R2 Terminal Server. Any thoughts will be most welcome.

I had the 30 minutes of printing then kapow -- this happened while emailing stubs from payroll DD. Chris Powers is apparently assigned to look at the overall issue of slow printing in paperless. I'm unsure what ultimately resolved the issue other than a combination of ""usual suspect fixes"". It apparently resolved itself through one of the following though the end users claims speed is still slow (1 hour to send vs prior 30 minutes). Case Notes: System appears to process a number of DD stubs. Get -30 error Get ""Unable to print PRWFXA1.RPT the device is not ready"" Tried: Change printer port to local - sage or c:\users\sage --- no luck Reviewed REGEDIT for Software key - did not appear to be the issue SAGE SUPPORT LOGGED IN AND: CDINTF.DLL searched and renamed to *.old by Sage Should only be in one directory -- sage common component Imported in a Sage PDF Registry by running PDFINSTALL. Fix for payroll checks (probably not specific to your case) https://www.evernote.com/shard/s270/sh/f7299ff1-1c9f-4931-b5ae-2268f907984d/2dbc822dc27804f87b8f8e162df5b19d

We are having this problem with a client with emailing the direct deposit stubs on over 200 employees as well. Sage's answer for now - print in groups of less than 100 at a time.

Thanks @WayneSchulz, I'll go through the checklist. Hopefully something will shake out. Maybe that patch will even help. @ChristineReeders - you may want to mention to whomever you spoke with that Chris Powers is aware of this issue. Perhaps they will reopen the case and escalate it over to Chris. Not sure but it may be worth a try. I may contact my old buddy as well, just to let him know how widespread the issue is.

Thanks. I will, it is an active case. I'm on the phone with them every other week when payroll is in process trying to get this figured out.

chris.powers@sage.com with cc: himanshu.palsule@sage.com -- they are looking into this and it would be helpful for them to get reinforcement that this is indeed a problem.

@CullenLowe After someone with more esteem (in Sage's view) mentioned this problem in Sage 100 LinkedIn and Himanshu picked up on it. Chris is tagged as the point person to research further as I understand. I think it's important that we continue to drive home these product design defects.

I just got a call from Nathan at Sage on this. I told him it seems to be with TS users. They have not tested in that environment so he's going back to Chris to see if they can give that a try.

My workaround for paperless is for large batches, start the process at the server (TS is ok as long as it is on the MAS server). That usually eliminates the errors.

I am on my way to creating a case so I can follow Wayne's advice. Just heard from them that 60 invoices went out just fine this morning, so somewhere between 60 and 166 may be the tipping point.

I gave Chris my customer's name so I think he is calling them direct. It's a frustrating problem initially because it takes 30-45 minutes until it errors out. Not fun when the customer is trying to get their payroll direct deposit done on a deadline.