Sage 100

You could always schedule an overnight reboot of the TS... they'll quickly learn to save their work at the end of the day if they don't want to lose it.  :-)  Of course, when to do that is complicated when considering overseas workers.

For the error, what is it exactly?  -30 is a timeout, and if that's the issue, look for things that could be causing a lag.  Not enough server resources (CPU / memory...), slow network, name resolution issues (i.e. change the PDF path to an IP address instead of machine name...), anti-virus slowing down the PDF creation process, network authentication delays (domain controller unavailable...).

What version of Sage?  v2023 has a new PDF converter....

Otherwise, perhaps an onsite visit to square things up??

You could always schedule an overnight reboot of the TS... they'll quickly learn to save their work at the end of the day if they don't want to lose it.  :-)  Of course, when to do that is complicated when considering overseas workers.

For the error, what is it exactly?  -30 is a timeout, and if that's the issue, look for things that could be causing a lag.  Not enough server resources (CPU / memory...), slow network, name resolution issues (i.e. change the PDF path to an IP address instead of machine name...), anti-virus slowing down the PDF creation process, network authentication delays (domain controller unavailable...).

You could always schedule an overnight reboot of the TS... they'll quickly learn to save their work at the end of the day if they don't want to lose it.  :-)  Of course, when to do that is complicated when considering overseas workers.

For the error, what is it exactly?  -30 is a timeout, and if that's the issue, look for things that could be causing a lag.  Not enough server resources (CPU / memory...), slow network, name resolution issues (i.e. change the PDF path to an IP address instead of machine name...), anti-virus slowing down the PDF creation process, network authentication delays (domain controller unavailable...).

Original Message:
Sent: 11/10/2023 1:01:00 PM
From: Kevin Moyes
Subject: RE: PDF Converter issues for REMOTE remote users

You could always schedule an overnight reboot of the TS... they'll quickly learn to save their work at the end of the day if they don't want to lose it.  :-)  Of course, when to do that is complicated when considering overseas workers.

For the error, what is it exactly?  -30 is a timeout, and if that's the issue, look for things that could be causing a lag.  Not enough server resources (CPU / memory...), slow network, name resolution issues (i.e. change the PDF path to an IP address instead of machine name...), anti-virus slowing down the PDF creation process, network authentication delays (domain controller unavailable...).

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


Original Message:
Sent: 11-10-2023 12:46
From: Robert Osborn
Subject: PDF Converter issues for REMOTE remote users

Original Message:
Sent: 11/10/2023 11:12:00 AM
From: David Overholt
Subject: RE: PDF Converter issues for REMOTE remote users

@Kevin Moyes " -30 is a timeout" is this documented somewhere, or you just figured it out? I don't know why I haven't come across this before. 

I have one site that has suddenly been experiencing severe Paperless issues. I have done everything in the book. We finally just had to turn off Paperless for Journals. Weird thing is it isn't failing on forms (Invoices and Direct Deposit Stubs have not failed once). 

I just reviewed a playback of a lengthy session from a couple of days ago and it is the -30 error every time. 

They are experiencing severe performance issues on this system (single server with only about 5 concurrent RDP users) so it makes sense what you posted. 

Edit: Oops, should not have relied on Sage kb and Google is my friend!

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


Original Message:
Sent: 11-10-2023 14:42
From: Robert Osborn
Subject: PDF Converter issues for REMOTE remote users

Original Message:
Sent: 11/10/2023 1:01:00 PM
From: Kevin Moyes
Subject: RE: PDF Converter issues for REMOTE remote users

You could always schedule an overnight reboot of the TS... they'll quickly learn to save their work at the end of the day if they don't want to lose it.  :-)  Of course, when to do that is complicated when considering overseas workers.

For the error, what is it exactly?  -30 is a timeout, and if that's the issue, look for things that could be causing a lag.  Not enough server resources (CPU / memory...), slow network, name resolution issues (i.e. change the PDF path to an IP address instead of machine name...), anti-virus slowing down the PDF creation process, network authentication delays (domain controller unavailable...).

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


Original Message:
Sent: 11-10-2023 12:46
From: Robert Osborn
Subject: PDF Converter issues for REMOTE remote users

Original Message:
Sent: 11/10/2023 11:12:00 AM
From: David Overholt
Subject: RE: PDF Converter issues for REMOTE remote users

Hi Bob,

You might try setting the Default Windows Printer, when a problem user connects to a terminal server, to a printer on the server, or the terminal server.  If one doesn't exist, set up a null printer device on the server or terminal server.  We found that speed issues with PDFs and timeouts can occur because the PDF converter appears to be using the Default Windows Printer queue (not the printer showing in the lower left when printing forms/reports) to create the PDF.  We found this to be true in Sage 2017, and believe it continued in 2022.  Not sure about in-between versions.  The idea is that the data has to travel to that device to be created, and once created, back to the storage location for the PDF.  Often users will have their local printer as the default, so the data has to travel back and forth, causing the delay or timeout.

We have the login script for the users set the Default Windows Printer when they connect to the Terminal Server.

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

Hi Bob,

You might try setting the Default Windows Printer, when a problem user connects to a terminal server, to a printer on the server, or the terminal server.  If one doesn't exist, set up a null printer device on the server or terminal server.  We found that speed issues with PDFs and timeouts can occur because the PDF converter appears to be using the Default Windows Printer queue (not the printer showing in the lower left when printing forms/reports) to create the PDF.  We found this to be true in Sage 2017, and believe it continued in 2022.  Not sure about in-between versions.  The idea is that the data has to travel to that device to be created, and once created, back to the storage location for the PDF.  Often users will have their local printer as the default, so the data has to travel back and forth, causing the delay or timeout.

We have the login script for the users set the Default Windows Printer when they connect to the Terminal Server.

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

Just to be clear, they do not have to turn off re-direction.  The user can still print to their re-directed printer.  It's only the Default Printer on the Terminal Server session when they connect that is used to spool/convert the pdf.

Hi Bob,

You might try setting the Default Windows Printer, when a problem user connects to a terminal server, to a printer on the server, or the terminal server.  If one doesn't exist, set up a null printer device on the server or terminal server.  We found that speed issues with PDFs and timeouts can occur because the PDF converter appears to be using the Default Windows Printer queue (not the printer showing in the lower left when printing forms/reports) to create the PDF.  We found this to be true in Sage 2017, and believe it continued in 2022.  Not sure about in-between versions.  The idea is that the data has to travel to that device to be created, and once created, back to the storage location for the PDF.  Often users will have their local printer as the default, so the data has to travel back and forth, causing the delay or timeout.

We have the login script for the users set the Default Windows Printer when they connect to the Terminal Server.

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

Hi Chris

  The problem is that the PDF converter errors out in the user's session even with a default printer set. Per @Kevin Moyes the error is a time out issue.   Redirection can make it take longer for the spooler to respond.    Yesterday the IT turned off redirection for the user and she reported that she was able to generate the PDF's successfully,. 

------------------------------
Bob Osborn
Consultant
ACI Consulting
------------------------------


Original Message:
Sent: 11-14-2023 14:05
From: Chris St. Amand
Subject: PDF Converter issues for REMOTE remote users

Just to be clear, they do not have to turn off re-direction.  The user can still print to their re-directed printer.  It's only the Default Printer on the Terminal Server session when they connect that is used to spool/convert the pdf.

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


Original Message:
Sent: 11-13-2023 15:00
From: Robert Osborn
Subject: PDF Converter issues for REMOTE remote users

Original Message:
Sent: 11/13/2023 12:19:00 PM
From: Chris St. Amand
Subject: RE: PDF Converter issues for REMOTE remote users

Hi Bob,

You might try setting the Default Windows Printer, when a problem user connects to a terminal server, to a printer on the server, or the terminal server.  If one doesn't exist, set up a null printer device on the server or terminal server.  We found that speed issues with PDFs and timeouts can occur because the PDF converter appears to be using the Default Windows Printer queue (not the printer showing in the lower left when printing forms/reports) to create the PDF.  We found this to be true in Sage 2017, and believe it continued in 2022.  Not sure about in-between versions.  The idea is that the data has to travel to that device to be created, and once created, back to the storage location for the PDF.  Often users will have their local printer as the default, so the data has to travel back and forth, causing the delay or timeout.

We have the login script for the users set the Default Windows Printer when they connect to the Terminal Server.

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

Change the session's default printer to something local to the server, and the PDF converter will use the server's print spooler, not the remote print spooler.

Edit:

If that doesn't work, I hear good things about using TSPrint (to solve terminal server printing issues).

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


Original Message:
Sent: 11-15-2023 10:22
From: Robert Osborn
Subject: PDF Converter issues for REMOTE remote users

Hi Chris

  The problem is that the PDF converter errors out in the user's session even with a default printer set. Per @Kevin Moyes the error is a time out issue.   Redirection can make it take longer for the spooler to respond.    Yesterday the IT turned off redirection for the user and she reported that she was able to generate the PDF's successfully,. 

------------------------------
Bob Osborn
Consultant
ACI Consulting


Original Message:
Sent: 11-14-2023 14:05
From: Chris St. Amand
Subject: PDF Converter issues for REMOTE remote users

Just to be clear, they do not have to turn off re-direction.  The user can still print to their re-directed printer.  It's only the Default Printer on the Terminal Server session when they connect that is used to spool/convert the pdf.

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


Original Message:
Sent: 11-13-2023 15:00
From: Robert Osborn
Subject: PDF Converter issues for REMOTE remote users

Original Message:
Sent: 11/13/2023 12:19:00 PM
From: Chris St. Amand
Subject: RE: PDF Converter issues for REMOTE remote users

Hi Bob,

You might try setting the Default Windows Printer, when a problem user connects to a terminal server, to a printer on the server, or the terminal server.  If one doesn't exist, set up a null printer device on the server or terminal server.  We found that speed issues with PDFs and timeouts can occur because the PDF converter appears to be using the Default Windows Printer queue (not the printer showing in the lower left when printing forms/reports) to create the PDF.  We found this to be true in Sage 2017, and believe it continued in 2022.  Not sure about in-between versions.  The idea is that the data has to travel to that device to be created, and once created, back to the storage location for the PDF.  Often users will have their local printer as the default, so the data has to travel back and forth, causing the delay or timeout.

We have the login script for the users set the Default Windows Printer when they connect to the Terminal Server.

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