Sage 100

V2014 STD PU3 - Paperless Printing for PR DD advices just will not work. Printer not activated, error code -30. It worked for a long time, then about when I installed PU 3, it began to flake out with this error message. then pops to Crystal Print error. - Unable to print PRWFXA1.rpt. Uninstalled/reinstalled via PL_advancedoptions_ui. PDF tests fine. Reinstalled WKsetup and WKworkstation (did not uninstall, hmmm). Tweaked the registry. Used a unadulterated Crystal form, Nothing works. Only this legacy form. Finally printed PDF'd/electronically delivered the forms from my remote session. Client was able to update the register and deliver them from her workstation. Hoping to install PU 5 in near term.

Just ran into this yesterday with a client. She had a redirected printer that we deleted and then it was fine.

I think the Anyumi driver gets updated in PU4 or 5. Installs when you run the wksudate file.

No redirected printer - Workstation connected to the network. New Amyuni comes into play with PU4.

@JeffSchwenk Did you ever figure out the cause? we are experiencing the same thing out of the blue. we can PDF anywhere except for Payroll DD forms. we get the error code -30 V2014 STD PU3 also. we are going to call Sage in the morning but I'm searching here first because this sounds familiar with legacy modules somehow.

No, never resolved. Since the original post, client moved up to v2015 and still has issue on occasion. It runs fine for me if I RDP into the server but not for another workstation. I thought it might be local admin rights but it works for three or four weeks then stops for a week then starts working again.

This just came back this week. Had been working with out issue for all of January. v2015 std, latest PU. Haven't touched anything since late December.

We have a client that had been getting this message sporadically. It magically went away for a couple of months and then returned. Even had Sage involved with client's IT department. Never resolved. Work around for them is to use legacy forms.

We have this Error 30 issue popping up at a customer site. We are thinking that it could be a timeout error when the printer is in heavy usage. As times it works fine and other times it is popping all the time. If we change the default printer the message goes away too. Anyone else seen this?

We never found any reason as to when it would or would not work. Our client was on a terminal Server, we tried other servers, direct RDP to the server, local workstation. It would work for a while, then stop. Since they have large payrolls (approx. 200 employees) they opted to stop trying and just print legacy forms. It was very frustrating for everyone, and we never had a conclusion.

Lately on issues like this (especially on some older versions, 2013/2014) I have found if the paperless folder is outside of Mas90 folder it quits working. redirect to a folder under Mas90 and it works again.

Thanks Kelly, I will try that next time - as a rule we always keep the PDF document folder just outside the MAS90 folder for obvious upgrade reasons so I'm sure that the couple of times I've run into this issue, it is possible that would have helped.

Just had a customer move off Sage payroll likely in part due to the slow time it took to mail out DD stubs via Paperless. They were sending out 200-225 stubs every week and I believe that it was taking a little over an hour to generate and email. Wrestled with a similar issue as well where the PDF would churn for about 30 minutes then throw out and error. I don't blame the customer for making a switch.

The last time we ran into that it was due to a bad printer. They got a new printer and everything was fine. Make sure all printers installed on the system are ""good""and online.

Just ran into this same issue (Error -30 printing paperless) in a hosted environment. If he logs into Citrix from another workstation, he gets the error. If someone logs into their account from his computer, they don't have the error. This is odd. Has anyone tried with success deleting the user profile on Citrix and then recreating it?

Update - Issue resolved by using local printer on Critix host rather than shared printer on remote server.