Sage 100

We are troubleshooting the same issue with a client at summit hosting. I don't know if it is when two users try to print to paperless at the same time, but we have not ruled that out. We too have a case open with Summit Hosting and with Sage.

Our client gets the "error-30 printer not activated" message. They have been on Summit Hosting for over a year, and it seems to have either started or gotten significantly worse in the last 3-4 months.

At first I thought this was random; but once a user gets the error printing a document, they keep getting it repeatedly. Sometimes they wait till the next day to update a register and the user can then print it. More often they have the office manager with administrative user rights on the server update the register. I don't think that she has ever gotten the error.  I've let Sage know that.

I do have a suspicion that this MIGHT be similar to the issue with printing multiple documents but I have not confirmed that yet.

Sage did a live connect to one of the users while it was happening and ran Process Monitor. That showed SentinalOne was scanning the PDF files as they were created. They  asked to have the Paperless Office directory whitelisted. Summit seemed to have difficulty with whitelisting it. First they were "reviewing" our request and then the told us several times that it was done but process monitor still showed that not to be the case. Summit was going to whitelist it again and reboot overnight so I will test again today and see if that is going to help.

TS print might be a good workaround and if this does not work, I may approach the client with that option. 

I will post updates to this thread and let everyone know.  

------------------------------
David Overholt
DWD Technology Group
------------------------------

Fast solution is to set default printer in windows to a local printer BEFORE launching Sage 100. 

In my customer's case, they rarely print anything and usually print to CutePDF anyway. 

This resolved it for them without additional expense. 

I asked Summitt to set users default printer in GP, but they tell me they can't. Apparently, they don't have these customers in separate OUs to be able to group policy by customer. 

I should add no more Paperless issues and PDF creation is exponentially faster. 

------------------------------
Eric Lunceford
First Mate Business Solutions
Oklahoma City, OK
877-880-8960
------------------------------

For all terminal servers, make sure the "Use Lockfile" option is turned on in PL_AdvancedOptions_UI... for each company code.

Without this setting the PDF file contents (of multiple users printing to PDF at the same time) can become merged / corrupted.

Edit:

I know you said this option doesn't help with this issue... I'm just saying: don't leave it off, to prevent problems with bad PDF's.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------

A lot of great suggestions here. I'll add my $.025 based on my own experiences.

• In case Adobe Acrobat Reader (or Acrobat) is used for auto-opening PDFs, I ALWAYS add the UNC path to the Paperless PDF folder as a privileged location in the security setting so it doesn't heavily scan. This has fixed speed and hanging issues many times. It's described here and works well, the only problem being this may have to be done for every user: 
  https://helpx.adobe.com/acrobat/using/enhanced-security-setting-pdfs.html
• Sentinel One out of the box sucks is very undesirable slowing down everything. Besides sending IT the Sage KB article on antivirus exclusions, ask them to also exclude pvxcom.exe from scanning as well as MDF and LDF file extensions if you're on Premium
• Definitely check the Use Lockfile box in PL_AdvancedOptions_UI like Kevin said. It is on by default but know it company specific
• I'm adding a positive vote for TSPRINT but know there are other RDF print mgmt tools also, in case you need a choice, or need to show pricing options to the client. Here are 2 of them that @Steve Iwanowski told me about once
  • ThinPrint - this has worked out nicely like TSPRINT
  • Printix - haven't tried it yet but Steve mentioned it has worked well in Azure AVD environments.

------------------------------
Alnoor Cassim
Accounting Systems, Inc. (ASI)
------------------------------


Original Message:
Sent: 03-06-2024 11:58
From: Kevin Moyes
Subject: Summit Hosting Printing Conflicts

For all terminal servers, make sure the "Use Lockfile" option is turned on in PL_AdvancedOptions_UI... for each company code.

Without this setting the PDF file contents (of multiple users printing to PDF at the same time) can become merged / corrupted.

Edit:

I know you said this option doesn't help with this issue... I'm just saying: don't leave it off, to prevent problems with bad PDF's.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON

Thanks @David Overholt  and Here is our status of our issue from last Friday:

Sage has created a KB entry on this topic. I believe Sage could use some help in expanding on these items as many of the newer KB are nothing more than "yeah we know about that" and very little explanation about the issue or potential fixes.

Sage has created a KB entry on this topic. I believe Sage could use some help in expanding on these items as many of the newer KB are nothing more than "yeah we know about that" and very little explanation about the issue or potential fixes.

Personally, I marvel at how you find these "new articles" every day.  Thank you @Wayne Schulz!!!

Sage has created a KB entry on this topic. I believe Sage could use some help in expanding on these items as many of the newer KB are nothing more than "yeah we know about that" and very little explanation about the issue or potential fixes.

It's a four-step process to locate the latest KB articles:

1. Login to the Sage Knowledgebase - https://us-kb.sage.com/portal/ss/?tabid=3&searchaliases=custom_us_onehundred
2. Search the keyword sage (or any keyword - the word doesn't matter you just need to get to step #3)
3. From the results, wipe out whatever you were searching for and leave that area blank and search again
4. Sort by new

Your final screen should look like this.

Note that it doesn't appear you can search a blank field initially, so I have found that the four steps are needed to get to a list of the newest KB articles.

Personally, I marvel at how you find these "new articles" every day.  Thank you @Wayne Schulz!!!

Sage has created a KB entry on this topic. I believe Sage could use some help in expanding on these items as many of the newer KB are nothing more than "yeah we know about that" and very little explanation about the issue or potential fixes.

Sage has created a KB entry on this topic. I believe Sage could use some help in expanding on these items as many of the newer KB are nothing more than "yeah we know about that" and very little explanation about the issue or potential fixes.

So many other things in play, not just adding TS Print.  We changed permissions on the RDP Server for Adobe Acrobat, We set up an "administrator like account" to set the icon to "run as administrator", Sage added process monitor and confirmed Summit was scanning every PDF before it was saved (got that changed); etc. etc. etc. 

------------------------------
Madeline Stefanou
RKL eSolutions, LLC
------------------------------


Original Message:
Sent: 03-13-2024 08:50
From: Wayne Schulz
Subject: Summit Hosting Printing Conflicts

Sage has created a KB entry on this topic. I believe Sage could use some help in expanding on these items as many of the newer KB are nothing more than "yeah we know about that" and very little explanation about the issue or potential fixes.

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT

If you are still interested in finding a solution without using TS Print, I would look at the Default Windows Printer of your successful user (Admin?) and those users that are having issues.  If you are not having a rights problem, the issue may be the location of the Default Windows Printer of each user.  Regardless of the printer selected by the user when running the forms, the Default Windows Printer of the user appears to be used to spool and create the PDFs.  If the Default Windows Printer of the user running the process is their local printer (not a Sage App Server or Terminal Server Printer), the data has to be moved to that remote print queue to generate the PDF.  You can easily test this by setting the Default Windows Printer of a problem user to either a printer or a null print device at the server, or at the terminal server to see if the speed improves.

If you run into issues with the users stepping on each other's print jobs, you can set up multiple null printers, and point your users to their own device.  For example

On the server, create Null Printer 1, Null Printer 2, Null Printer 3.  These print queues go nowhere, but are used to create the PDFs.  One of our large clients that process large (5k+) payroll runs, has each of three payroll clerks assigned to one of the Null printers using their Default Windows Printer.   Server and Terminal Servers are in the cloud.  Users are working from home on laptops.  Each DD stub takes 2-3 seconds to pdf.

------------------------------
Chris St. Amand
Arizona Accounting & Information Systems
------------------------------


Original Message:
Sent: 03-13-2024 09:06
From: Madeline Stefanou
Subject: Summit Hosting Printing Conflicts

So many other things in play, not just adding TS Print.  We changed permissions on the RDP Server for Adobe Acrobat, We set up an "administrator like account" to set the icon to "run as administrator", Sage added process monitor and confirmed Summit was scanning every PDF before it was saved (got that changed); etc. etc. etc. 

------------------------------
Madeline Stefanou
RKL eSolutions, LLC


Original Message:
Sent: 03-13-2024 08:50
From: Wayne Schulz
Subject: Summit Hosting Printing Conflicts

Sage has created a KB entry on this topic. I believe Sage could use some help in expanding on these items as many of the newer KB are nothing more than "yeah we know about that" and very little explanation about the issue or potential fixes.

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT

Wanted to acknowledge @Chris St. Amand suggestion to set user default printer to one on the terminal server.  I set a PR user's default printer to MSFT PDF printer on the terminal server.  She reported back that the remittance advice PDFs generated a LOT faster.

Thanks Chris

If you are still interested in finding a solution without using TS Print, I would look at the Default Windows Printer of your successful user (Admin?) and those users that are having issues.  If you are not having a rights problem, the issue may be the location of the Default Windows Printer of each user.  Regardless of the printer selected by the user when running the forms, the Default Windows Printer of the user appears to be used to spool and create the PDFs.  If the Default Windows Printer of the user running the process is their local printer (not a Sage App Server or Terminal Server Printer), the data has to be moved to that remote print queue to generate the PDF.  You can easily test this by setting the Default Windows Printer of a problem user to either a printer or a null print device at the server, or at the terminal server to see if the speed improves.

If you run into issues with the users stepping on each other's print jobs, you can set up multiple null printers, and point your users to their own device.  For example

On the server, create Null Printer 1, Null Printer 2, Null Printer 3.  These print queues go nowhere, but are used to create the PDFs.  One of our large clients that process large (5k+) payroll runs, has each of three payroll clerks assigned to one of the Null printers using their Default Windows Printer.   Server and Terminal Servers are in the cloud.  Users are working from home on laptops.  Each DD stub takes 2-3 seconds to pdf.

------------------------------
Chris St. Amand
Arizona Accounting & Information Systems


Original Message:
Sent: 03-13-2024 09:06
From: Madeline Stefanou
Subject: Summit Hosting Printing Conflicts

So many other things in play, not just adding TS Print.  We changed permissions on the RDP Server for Adobe Acrobat, We set up an "administrator like account" to set the icon to "run as administrator", Sage added process monitor and confirmed Summit was scanning every PDF before it was saved (got that changed); etc. etc. etc. 

------------------------------
Madeline Stefanou
RKL eSolutions, LLC


Original Message:
Sent: 03-13-2024 08:50
From: Wayne Schulz
Subject: Summit Hosting Printing Conflicts

Sage has created a KB entry on this topic. I believe Sage could use some help in expanding on these items as many of the newer KB are nothing more than "yeah we know about that" and very little explanation about the issue or potential fixes.

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT

great feedback @Jeff Schwenk

Wanted to acknowledge @Chris St. Amand suggestion to set user default printer to one on the terminal server.  I set a PR user's default printer to MSFT PDF printer on the terminal server.  She reported back that the remittance advice PDFs generated a LOT faster.

Thanks Chris

If you are still interested in finding a solution without using TS Print, I would look at the Default Windows Printer of your successful user (Admin?) and those users that are having issues.  If you are not having a rights problem, the issue may be the location of the Default Windows Printer of each user.  Regardless of the printer selected by the user when running the forms, the Default Windows Printer of the user appears to be used to spool and create the PDFs.  If the Default Windows Printer of the user running the process is their local printer (not a Sage App Server or Terminal Server Printer), the data has to be moved to that remote print queue to generate the PDF.  You can easily test this by setting the Default Windows Printer of a problem user to either a printer or a null print device at the server, or at the terminal server to see if the speed improves.

If you run into issues with the users stepping on each other's print jobs, you can set up multiple null printers, and point your users to their own device.  For example

On the server, create Null Printer 1, Null Printer 2, Null Printer 3.  These print queues go nowhere, but are used to create the PDFs.  One of our large clients that process large (5k+) payroll runs, has each of three payroll clerks assigned to one of the Null printers using their Default Windows Printer.   Server and Terminal Servers are in the cloud.  Users are working from home on laptops.  Each DD stub takes 2-3 seconds to pdf.

------------------------------
Chris St. Amand
Arizona Accounting & Information Systems


Original Message:
Sent: 03-13-2024 09:06
From: Madeline Stefanou
Subject: Summit Hosting Printing Conflicts

So many other things in play, not just adding TS Print.  We changed permissions on the RDP Server for Adobe Acrobat, We set up an "administrator like account" to set the icon to "run as administrator", Sage added process monitor and confirmed Summit was scanning every PDF before it was saved (got that changed); etc. etc. etc. 

------------------------------
Madeline Stefanou
RKL eSolutions, LLC


Original Message:
Sent: 03-13-2024 08:50
From: Wayne Schulz
Subject: Summit Hosting Printing Conflicts

Sage has created a KB entry on this topic. I believe Sage could use some help in expanding on these items as many of the newer KB are nothing more than "yeah we know about that" and very little explanation about the issue or potential fixes.

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT

As an update, after 2 weeks of using TS Print users have not had any problems. Before installing TS Print, I would hear from them almost every day. They started with the 25-day free trial license and have now purchased the unlimited version for $399. 

great feedback @Jeff Schwenk

Wanted to acknowledge @Chris St. Amand suggestion to set user default printer to one on the terminal server.  I set a PR user's default printer to MSFT PDF printer on the terminal server.  She reported back that the remittance advice PDFs generated a LOT faster.

Thanks Chris

If you are still interested in finding a solution without using TS Print, I would look at the Default Windows Printer of your successful user (Admin?) and those users that are having issues.  If you are not having a rights problem, the issue may be the location of the Default Windows Printer of each user.  Regardless of the printer selected by the user when running the forms, the Default Windows Printer of the user appears to be used to spool and create the PDFs.  If the Default Windows Printer of the user running the process is their local printer (not a Sage App Server or Terminal Server Printer), the data has to be moved to that remote print queue to generate the PDF.  You can easily test this by setting the Default Windows Printer of a problem user to either a printer or a null print device at the server, or at the terminal server to see if the speed improves.

If you run into issues with the users stepping on each other's print jobs, you can set up multiple null printers, and point your users to their own device.  For example

On the server, create Null Printer 1, Null Printer 2, Null Printer 3.  These print queues go nowhere, but are used to create the PDFs.  One of our large clients that process large (5k+) payroll runs, has each of three payroll clerks assigned to one of the Null printers using their Default Windows Printer.   Server and Terminal Servers are in the cloud.  Users are working from home on laptops.  Each DD stub takes 2-3 seconds to pdf.

------------------------------
Chris St. Amand
Arizona Accounting & Information Systems


Original Message:
Sent: 03-13-2024 09:06
From: Madeline Stefanou
Subject: Summit Hosting Printing Conflicts

So many other things in play, not just adding TS Print.  We changed permissions on the RDP Server for Adobe Acrobat, We set up an "administrator like account" to set the icon to "run as administrator", Sage added process monitor and confirmed Summit was scanning every PDF before it was saved (got that changed); etc. etc. etc. 

------------------------------
Madeline Stefanou
RKL eSolutions, LLC


Original Message:
Sent: 03-13-2024 08:50
From: Wayne Schulz
Subject: Summit Hosting Printing Conflicts

Sage has created a KB entry on this topic. I believe Sage could use some help in expanding on these items as many of the newer KB are nothing more than "yeah we know about that" and very little explanation about the issue or potential fixes.

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT

Our client also went that direction and everything has been working; since. 

As an update, after 2 weeks of using TS Print users have not had any problems. Before installing TS Print, I would hear from them almost every day. They started with the 25-day free trial license and have now purchased the unlimited version for $399. 

great feedback @Jeff Schwenk

Wanted to acknowledge @Chris St. Amand suggestion to set user default printer to one on the terminal server.  I set a PR user's default printer to MSFT PDF printer on the terminal server.  She reported back that the remittance advice PDFs generated a LOT faster.

Thanks Chris

If you are still interested in finding a solution without using TS Print, I would look at the Default Windows Printer of your successful user (Admin?) and those users that are having issues.  If you are not having a rights problem, the issue may be the location of the Default Windows Printer of each user.  Regardless of the printer selected by the user when running the forms, the Default Windows Printer of the user appears to be used to spool and create the PDFs.  If the Default Windows Printer of the user running the process is their local printer (not a Sage App Server or Terminal Server Printer), the data has to be moved to that remote print queue to generate the PDF.  You can easily test this by setting the Default Windows Printer of a problem user to either a printer or a null print device at the server, or at the terminal server to see if the speed improves.

If you run into issues with the users stepping on each other's print jobs, you can set up multiple null printers, and point your users to their own device.  For example

On the server, create Null Printer 1, Null Printer 2, Null Printer 3.  These print queues go nowhere, but are used to create the PDFs.  One of our large clients that process large (5k+) payroll runs, has each of three payroll clerks assigned to one of the Null printers using their Default Windows Printer.   Server and Terminal Servers are in the cloud.  Users are working from home on laptops.  Each DD stub takes 2-3 seconds to pdf.

------------------------------
Chris St. Amand
Arizona Accounting & Information Systems


Original Message:
Sent: 03-13-2024 09:06
From: Madeline Stefanou
Subject: Summit Hosting Printing Conflicts

So many other things in play, not just adding TS Print.  We changed permissions on the RDP Server for Adobe Acrobat, We set up an "administrator like account" to set the icon to "run as administrator", Sage added process monitor and confirmed Summit was scanning every PDF before it was saved (got that changed); etc. etc. etc. 

------------------------------
Madeline Stefanou
RKL eSolutions, LLC