Sage 100

Customer is on 2016.3 standard - when running AR period end reports everything runs fine until the reporting hits the salesperson commisison report. I can run the commission report standalone just not in the period end reports dialog box.

Sage has a report (different error message) of AR Salesperson Commission Report not running via Period End.... [their advice](https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=59622&sliceId=1&cmd=displayKC&dialogID=20622&docType=kc&isLoadPublishedVer=&stateId=20624&docTypeID=DT_Article&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl) ""don't run the report through period end"".

When it runs thru Period End, it appears to run for all dates. Is that how you're running it?

No idea. I just removed it from the period end menu. Sage support is such a nightmare to interact with that I recommended the customer work around it unless they had 2 hours and time for 3 followup calls with support.

Known issue. Apparently the unpublished resolution from Sage doesn't work for everyone; it didn't work for my client.

What's the unpublished resolution

Download AR.Zip file Browse to client ..\..\MAS90\ rename their current AR directory to origAR Copy in the zipped AR directory Copy in the CUSTOM directory if exists from the origAR folder that was renamed This attached AR directory is from 2016.3 so it's current Reinstalling PU will not be necessary However, if you have a MOD touching AR program files those will need to be reinstalled When that is all done do a Period End, just the printing part, to make sure it will work for next Period End

This isn't running to paperless though (they use deferred). Does the fix still apply?

OMG.

The error you posted above is the same error my client got, so I would _think_ it still applies. The files provided by Sage appear to be the exact same as what's currently installed on my client's system, i.e., same exact byte size. Sage responded, ""Apparently replacing those files is not working for everybody because I have another case and I have been breaking this program apart and can't find the trigger. All I have noticed is I think the issue is we are calling the reports to fast and that is making it choke and throw an error. I did a run where it was PDF and it had to flag for file names. Because it had to wait the error never came up and that is what I will be submitting to engineering because we obviously have a problem. I'll let you know what I find out as far as a fix"".

Another one to add to my upgrade bugs list. ALL CONVERSION ERRORS ON SAGE'S PART - 1099 Electronic Consent - ACH not posting to BR - AR_RepetitiveInvoiceHeader SAGE NOT INTERESTED IN FIXING A MANUAL CC PROCESSING ISSUE - Manual credit card processing makes incorrect GL postings - invoice shows $ 0 but open balance amount posts to GL

And add @BarbaraGoldstein latest - do not use merge fields in email messages (such as invoices and customer statements)

@WayneSchulz, update from Carmen at Sage: ""Datasets were tested from multiple clients in vanilla Sage and I was able to reproduce the error message. It appears, to me, to be an issue with feeding the report so fast through the process. When I tested with a PDF printer, being my default, it did not error because it had to stop long enough to ask me where to save the PDF file. When I ran and pointed to a real printer I got the error so it tells me because it is going faster it's causing the data to choke on the send to the wrk*.*.m4t file for printing. This has been submitted to engineering for a fix. If you have any additional questions for me in regards to this issue please let me know otherwise please let your clients know we are working on a fix. Sorry for the inconvenience this is causing. Take Care"".

TL;DR: Take the Salesman Commission Report out of the period end reporting and run it manually.

Kinda reminds me of Sage tech support. I wonder if we can get the Sage folks to have a go at it as their Karaoke theme song. https://www.youtube.com/watch?v=t-wUe5aEwHM

Only questions 1. Does Sage understand the concept ""save the day""? 2. Will the audience be protected from the inevitable lighting strikes?

Had another client with this issue (this client is running v2017.0; haven't had a chance to install PU1 yet). But this time (per the apparently-updated Sage KB write-up as of 3-14-17, below), I created a new 'FOR PERIOD-END' Report Setting, removed 'STANDARD' from the P/E Report Selection screen, and added the new one - and that appears to work. Similar to others above, previously I was removing the 'STANDARD' from the P/E Report Selection screen and having the client first run the report manually via the A/R Reports menu (outside of Period-End Processing). **Error: ""42 SY_Selection.pvc 2583""** Products Sage 100 Description Error: ""42 SY_Selection.pvc 2583"" occurs when running Period End Processing reports from Period End Report Selection for the Salesperson Commission Report. Resolution Remove from Accounts Receivable, Period End, Period End Selection Report Run report from Accounts Receivable, Reports, Salesperson Commission Report or Recreate a NEW report setting and modify the report, then select NEW report setting in the Period End Report Selection and remove the old one. This has been submitted to engineering to determine why this report works from Reports menu and not from Period End Reports option. Category Performance Printing and Reporting Entitlement Open Defect ID 106968 ID:81508Last modified:3-14-2017