Sage 100

Printer not activated error code -30 Customer on Windows 7 64 Bit - 8 GB RAM - workstation - just upgraded to 2013. They go into print DD stubs and everything cranks for 5-10 minutes. Get messages about Crystal printing, workfile, etc. It seems to go through each employee. Then about 10 minutes or so into it I get this ""Printer not activated error code -30"" I know the traditional fixes --- set the local port to sage However I've done that. And this is puzzling because I've not seen paperless buzz along for this period of time before crashing. Anyone seen something similar?

Additional message ""Unable to print PRWFXA1.Rpt"" The device is not ready.

Trying this KB from Evernote -- https://www.evernote.com/shard/s270/sh/b99555c4-65ff-4398-aa0d-c9033c8ff9da/a73756918f84fbe3a20debf4a547958b

Have you created a new DD Stub form?

Wayne, I run into paperless issues all the time. Attached is a document that I use. Hope it helps.

@WayneSchulz not sure how to copy from Evernote the way you did. What about this document in Evernote.

This is using copy note link but to me it doesn't look right. evernote:///view/21955008/s270/2a596349-1475-4575-8acb-6eab17fbb20a/2a596349-1475-4575-8acb-6eab17fbb20a/180a33ef-1329-478b-8a50-396b69cd5c4c

We had this problem with a client who was running a remote workstation. After switching to terminal serv, the problem quit.

There's a bazillion little odds and ends once you get past the usual suspects (local port) - still looking. Find it extremely unusual that this appears to print until 5-10 minutes in then bombs.

Still looking - now at REGEDIT on this users workstation. Uninstalled, reinstalled. No fix. Unusual that the permissions for Sage PDF Converter are blank though other REGEDIT show normal. Tried uninstall this key and reinstall paperless and still blank permissions.

Customer moved to another workstation - same problem on that workstation. Continuing to diagnose.

On my workstation installs, the keys always have blank permissions - I have to import a .reg file AND set permissions on all Win 7 or 8 workstations to get paperless to work properly. I DO NOT understand why some workstations will work with the blank permissions and some will not - I think it has to do with domain administrator permission of the user but I have not researched that. In addition I have created new forms using the new version of Crystal - always for AP checks and sometimes for PR checks and dd stubs. If I have any issue with a form I will create a new one with the new version. I will attach a zipped file of the .reg file I got from Sage if it will allow. I import the file and then change the permissions on all the keys to 'users' modify. I use it for Windows 8, too.

Thanks - I'm not able to see how to set permissions. Right now I'm having the customers IT staff review.

Here is the Regedit of the Paperless PDF that looks odd to me. Oddly this seems to match what's on my desktop so I think I'm going to toss this to Sage.

I think that is normal - and it will work if you are an administrator. Problems arise when the user is NOT an administrative user. You have to set the permissions.

Thanks - I am finding that I can print from other areas of paperless - so I'm zeroing in on the DD stubs.

After a rock solid 35 to 45 minutes of watching the Sage 100 2013 DD stubs appear to print to crystal I get the Printer not activated error code -30. Calling and pulling a Sage support case.

Tip: When calling support you must use the Sage tools line or if you call on payroll you can hear the happiness in their voice as they discover they can phone transfer you to someone else...

Turning off paperless email delivery allowed us to generate paperless stubs. Looking at whether there's an issue with the email setup.

Theory: The issue was caused by email account needing to be setup again in company maintenance after upgrade to 2013 (from 4.3)

I had this happen with a client and as I recall it was because IT changed the email server and the address in Company Maintenance was wrong.

I'm going to add this into Evernote today. It's an odd one that I haven't seen before. There sure are a lot of little workarounds and fixes that apply to paperless office.

You would think that Sage could put better error messages so we would know what is wrong or help narrow down what to look for. @WayneSchulz you spent most of the day working on this paperless issue. How many hours are spent each day on paperless issues? Why can't they get this right? Just my .02

The reason is that the Sage development cycle is ""one and done"". Once the feature ships unless they can make more money off it or it's dirt simple to change it tends to go into fully complete status with no further updates. Unfortunately at some point I'm guessing Sage will be forced to update their PDF technology --- or they'll pull a fast one and require migration to one of the paperless doc third parties. If there's a migration I can already sense the nightmare that could be.

Part of the problem is that the Amiyumi PDF driver they are using give the same crappy error messages and Sage just passes them along.

This issue came back and I'm wondering if there's not some bigger problem. We at first theorized that the issue was that the email login was wrong. Fixed that. Now the customer goes in and attempts to run their next payroll. This runs for an hour before erroring as above. Wondering if this may be some type of Sage bug. All other paperless works as expected. Can also test and send email from this same PC. When I look into the paperless folder on this run I see 36 PDF files generated.

@WayneSchulz - Did you ever figure this out? Did a 4.5 to 2014 migration and am experiencing the same issue. Client has 450 employees and direct deposit stub printing churns along for 45 minutes or so, creates some of the stubs in paperless office and then stops. It does this on several workstations and a terminal server. Paperless office works fine everywhere else. This thread is so similar I'm hoping you figured out the cause so I don't have to!

Chris Powers at Sage is (was) the lead on this - christopher.powers@sage.com Last ""solution"" that I had from Sage: set the Windows default printer to 'Microsoft XPS Document Writer' and this made a significant improvement to the performance. I was told we have a case with Microsoft and we are waiting to hear about a hotfix but I am waiting for details so I can post something to the knowledgebase. Sue also contacted her most heavily affected customer and this workaround resulted in improved performance for them as well. o She told me on 8/7/2014 she would post back to the thread but I don't think she has had the opportunity to do that yet. Sage also commented (Ryan Clark): Usually this is caused by a form pre-PU5 form code. I don't trust any form codes that are prior to 2013.5. If you get any ""Printer not activated"" message with a form, my recommendation first overall is to put on PU5, create a new form code, and test.

The issue seems to have gone away. Whether it was Sage's suggested fix is still not entirely clear. With these types of issues you are often trying multiple possible solutions making it tough to determine which change could have been the lucky fix.

If the PR check or DD stub form was created with an older version of Sage, I will create a new form. This is in addition to all of the above steps after workstation setup: create a new local port for the Sage PDF Converter printer object & add the Sage PDF converter registry keys and set permissions on them.

PITA issue is back for one client. Just started a couple weeks ago, V2014 std pu 3. Replaced the prwsxa1. Nope. Reinstalled workstation. Nope. Uninstalled/Reinstalled Pl_advancedOptions_UI. Nothing works if I generate a PDF. Started before I install the 2014IRD. And as soon as I post this note, ANOTHER client calls with exact same issue........

I was able to get this fixed by installing PU4 for 2014 to get the 64 bit version of the Amiyumi driver. We had another client on 2013 that was having the same issue and the PU7 with the 64 bit driver fixed that as well.

I think you also run wksupdate unless the customer is on Advanced or Premium

Adv v2015.3 - I'm having this issue on a Win7 computer and a Win10 computer, **but _not_ on another Win7 computer**. I haven't been able to determine the difference between computers that's causing this issue. Help, please!!

I was able to _eventually_ resolve this by implementing the C/S ODBC driver, which also incredibly sped up the performance. The performance for this client's process was very slow, so I had planned on trying the C/S ODBC driver once I resolved the -30 errors, but then it occurred to me that maybe this will resolve the -30 errors also since they seemed to be caused by certain workstations timing-out / taking too long to generate periodic .pdf's. I was happy to have come across @JaneScanlan's post in this other thread (https://90minds-com.socialcast.com/messages/21349007?ref=stream).

Sage told me that any time it takes longer than 20 seconds to generate the PDF it will cause error -30.