Sage 100

First thing I'd do is try to rule out a form issue and try printing to STANDARD

Workstation AV?  Workstation network cabling, NIC?  Network speed (1 G, vs 100 M), memory on the workstation?  Is this advanced so you have CS ODBC?  Printer Q set to spool before printing?  Just the usual suspects.

Workstation AV?  Workstation network cabling, NIC?  Network speed (1 G, vs 100 M), memory on the workstation?  Is this advanced so you have CS ODBC?  Printer Q set to spool before printing?  Just the usual suspects.

I don't believe it is cabling, NIC, and probably not AV because picking sheet printing works fine.  It seems to be only sales order printing and it doesn't matter what form code is used.

Workstation AV?  Workstation network cabling, NIC?  Network speed (1 G, vs 100 M), memory on the workstation?  Is this advanced so you have CS ODBC?  Printer Q set to spool before printing?  Just the usual suspects.

Did you try reinitializing the SO_SalesOrderWrk file?

I don't believe it is cabling, NIC, and probably not AV because picking sheet printing works fine.  It seems to be only sales order printing and it doesn't matter what form code is used.

Workstation AV?  Workstation network cabling, NIC?  Network speed (1 G, vs 100 M), memory on the workstation?  Is this advanced so you have CS ODBC?  Printer Q set to spool before printing?  Just the usual suspects.

Yes, and I just reinitialized SO_SalesOrderWrk again and get the same slow result.  They do have some custom modifications.  I am going to get a programmer involved to try and trace through it.

Did you try reinitializing the SO_SalesOrderWrk file?

I don't believe it is cabling, NIC, and probably not AV because picking sheet printing works fine.  It seems to be only sales order printing and it doesn't matter what form code is used.

Workstation AV?  Workstation network cabling, NIC?  Network speed (1 G, vs 100 M), memory on the workstation?  Is this advanced so you have CS ODBC?  Printer Q set to spool before printing?  Just the usual suspects.

Sage 100 Standard does all the data processing over the network.  The Server simply has more efficient and speedy access to the data.

Yes, and I just reinitialized SO_SalesOrderWrk again and get the same slow result.  They do have some custom modifications.  I am going to get a programmer involved to try and trace through it.

Did you try reinitializing the SO_SalesOrderWrk file?

I don't believe it is cabling, NIC, and probably not AV because picking sheet printing works fine.  It seems to be only sales order printing and it doesn't matter what form code is used.

Workstation AV?  Workstation network cabling, NIC?  Network speed (1 G, vs 100 M), memory on the workstation?  Is this advanced so you have CS ODBC?  Printer Q set to spool before printing?  Just the usual suspects.

I understand.  2 minutes is still unacceptable so most likely rules out a network (NIC, cabling, etc) or workstation issue.

Sage 100 Standard does all the data processing over the network.  The Server simply has more efficient and speedy access to the data.

Yes, and I just reinitialized SO_SalesOrderWrk again and get the same slow result.  They do have some custom modifications.  I am going to get a programmer involved to try and trace through it.

Did you try reinitializing the SO_SalesOrderWrk file?

I don't believe it is cabling, NIC, and probably not AV because picking sheet printing works fine.  It seems to be only sales order printing and it doesn't matter what form code is used.

Workstation AV?  Workstation network cabling, NIC?  Network speed (1 G, vs 100 M), memory on the workstation?  Is this advanced so you have CS ODBC?  Printer Q set to spool before printing?  Just the usual suspects.

I understand.  2 minutes is still unacceptable so most likely rules out a network (NIC, cabling, etc) or workstation issue.

Sage 100 Standard does all the data processing over the network.  The Server simply has more efficient and speedy access to the data.

Yes, and I just reinitialized SO_SalesOrderWrk again and get the same slow result.  They do have some custom modifications.  I am going to get a programmer involved to try and trace through it.

Did you try reinitializing the SO_SalesOrderWrk file?

I don't believe it is cabling, NIC, and probably not AV because picking sheet printing works fine.  It seems to be only sales order printing and it doesn't matter what form code is used.

Workstation AV?  Workstation network cabling, NIC?  Network speed (1 G, vs 100 M), memory on the workstation?  Is this advanced so you have CS ODBC?  Printer Q set to spool before printing?  Just the usual suspects.

Two minutes isn't exceptionally bad for 30-40 SO.  That's about 5 seconds each, which I'd consider normal-ish on slower hardware.

I understand.  2 minutes is still unacceptable so most likely rules out a network (NIC, cabling, etc) or workstation issue.

Sage 100 Standard does all the data processing over the network.  The Server simply has more efficient and speedy access to the data.

Yes, and I just reinitialized SO_SalesOrderWrk again and get the same slow result.  They do have some custom modifications.  I am going to get a programmer involved to try and trace through it.

Did you try reinitializing the SO_SalesOrderWrk file?

I don't believe it is cabling, NIC, and probably not AV because picking sheet printing works fine.  It seems to be only sales order printing and it doesn't matter what form code is used.

Workstation AV?  Workstation network cabling, NIC?  Network speed (1 G, vs 100 M), memory on the workstation?  Is this advanced so you have CS ODBC?  Printer Q set to spool before printing?  Just the usual suspects.

What version of Sage 100, and is it standard or advanced

Are you creating PDFs of the Sales Orders with Paperless?

Is the user running from a workstation or a Terminal Server?

Where is the user's Windows default printer located?  Server? Terminal Server? Workstation?

2022 Standard

Not using paperless office or creating PDFs

Running from a workstation.  No terminal server.  It takes 4-5 minutes before the orders begin to print.  If I print the orders directly on the server it takes about 2 minutes.  The server is 2 years old running VMware.  32 GB allocated to Sage 100 VM, hardware RAID.  Performance is generally pretty good in other areas.

Default Windows printer is on the server.  Why does this matter?

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles
------------------------------


Original Message:
Sent: 07-26-2023 09:07
From: Chris St. Amand
Subject: It Takes 5 Minutes to Print Sales Orders - Stuck on "Processing Work Records"

What version of Sage 100, and is it standard or advanced

Are you creating PDFs of the Sales Orders with Paperless?

Is the user running from a workstation or a Terminal Server?

Where is the user's Windows default printer located?  Server? Terminal Server? Workstation?

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

2022 Standard

Not using paperless office or creating PDFs

Running from a workstation.  No terminal server.  It takes 4-5 minutes before the orders begin to print.  If I print the orders directly on the server it takes about 2 minutes.  The server is 2 years old running VMware.  32 GB allocated to Sage 100 VM, hardware RAID.  Performance is generally pretty good in other areas.

Default Windows printer is on the server.  Why does this matter?

What version of Sage 100, and is it standard or advanced

Are you creating PDFs of the Sales Orders with Paperless?

Is the user running from a workstation or a Terminal Server?

Where is the user's Windows default printer located?  Server? Terminal Server? Workstation?

Are all of the printers on the workstation valid printers? I would remove any printers that the user does not actively use or need. 

I have had cases where Sage will try to connect to an invalid printer even if it is not the one selected for printing. Sage just keeps waiting for it to respond and eventually moves on to the next printer that it finds in windows. if there are a lot of invalid printers that might be what is happening.  

2022 Standard

Not using paperless office or creating PDFs

Running from a workstation.  No terminal server.  It takes 4-5 minutes before the orders begin to print.  If I print the orders directly on the server it takes about 2 minutes.  The server is 2 years old running VMware.  32 GB allocated to Sage 100 VM, hardware RAID.  Performance is generally pretty good in other areas.

Default Windows printer is on the server.  Why does this matter?

What version of Sage 100, and is it standard or advanced

Are you creating PDFs of the Sales Orders with Paperless?

Is the user running from a workstation or a Terminal Server?

Where is the user's Windows default printer located?  Server? Terminal Server? Workstation?

I discovered the issue.  If I rename SO568APSSalesOrderPrinting_RPT.PVC then the orders print immediately.  Next step is to open a case with Repay and see how to fix it.  Thank you everyone for your recommendations!

Are all of the printers on the workstation valid printers? I would remove any printers that the user does not actively use or need. 

I have had cases where Sage will try to connect to an invalid printer even if it is not the one selected for printing. Sage just keeps waiting for it to respond and eventually moves on to the next printer that it finds in windows. if there are a lot of invalid printers that might be what is happening.  

2022 Standard

Not using paperless office or creating PDFs

Running from a workstation.  No terminal server.  It takes 4-5 minutes before the orders begin to print.  If I print the orders directly on the server it takes about 2 minutes.  The server is 2 years old running VMware.  32 GB allocated to Sage 100 VM, hardware RAID.  Performance is generally pretty good in other areas.

Default Windows printer is on the server.  Why does this matter?

What version of Sage 100, and is it standard or advanced

Are you creating PDFs of the Sales Orders with Paperless?

Is the user running from a workstation or a Terminal Server?

Where is the user's Windows default printer located?  Server? Terminal Server? Workstation?

Do they have click-to-pay enabled for SO?  It might be going out and getting the links during the printing stage.

I discovered the issue.  If I rename SO568APSSalesOrderPrinting_RPT.PVC then the orders print immediately.  Next step is to open a case with Repay and see how to fix it.  Thank you everyone for your recommendations!

Are all of the printers on the workstation valid printers? I would remove any printers that the user does not actively use or need. 

I have had cases where Sage will try to connect to an invalid printer even if it is not the one selected for printing. Sage just keeps waiting for it to respond and eventually moves on to the next printer that it finds in windows. if there are a lot of invalid printers that might be what is happening.  

2022 Standard

Not using paperless office or creating PDFs

Running from a workstation.  No terminal server.  It takes 4-5 minutes before the orders begin to print.  If I print the orders directly on the server it takes about 2 minutes.  The server is 2 years old running VMware.  32 GB allocated to Sage 100 VM, hardware RAID.  Performance is generally pretty good in other areas.

Default Windows printer is on the server.  Why does this matter?

What version of Sage 100, and is it standard or advanced

Are you creating PDFs of the Sales Orders with Paperless?

Is the user running from a workstation or a Terminal Server?

Where is the user's Windows default printer located?  Server? Terminal Server? Workstation?

Good thought @Kevin Moyes  however, they do not.  I just checked and Enable Sales Orders  is unchecked on the Click to Pay tab in Repay Payments Options.  Waiting for a response from Repay tech support. 

Do they have click-to-pay enabled for SO?  It might be going out and getting the links during the printing stage.

I discovered the issue.  If I rename SO568APSSalesOrderPrinting_RPT.PVC then the orders print immediately.  Next step is to open a case with Repay and see how to fix it.  Thank you everyone for your recommendations!

Are all of the printers on the workstation valid printers? I would remove any printers that the user does not actively use or need. 

I have had cases where Sage will try to connect to an invalid printer even if it is not the one selected for printing. Sage just keeps waiting for it to respond and eventually moves on to the next printer that it finds in windows. if there are a lot of invalid printers that might be what is happening.  

2022 Standard

Not using paperless office or creating PDFs

Running from a workstation.  No terminal server.  It takes 4-5 minutes before the orders begin to print.  If I print the orders directly on the server it takes about 2 minutes.  The server is 2 years old running VMware.  32 GB allocated to Sage 100 VM, hardware RAID.  Performance is generally pretty good in other areas.

Default Windows printer is on the server.  Why does this matter?

What version of Sage 100, and is it standard or advanced

Are you creating PDFs of the Sales Orders with Paperless?

Is the user running from a workstation or a Terminal Server?

Where is the user's Windows default printer located?  Server? Terminal Server? Workstation?