Sage 100

Were the users getting this message when trying to start Sage 100?

If yes, I have seen this on four clients now.  They were running different base versions of Advanced (2022.3, 2023.0, etc) but the common denominator was they all recently had Payroll 2.24.0 installed.

If you look at the processes on the application server, you should see the Sage 100 application server process capping out the CPU on one core.  If you add the Command line column to the details tab and expand it, you should see another process with command line arguments similar to the second process indicated in this screenshot.  This process was present on these clients that had this issue.  The "PRL" and "50" values in the command line may differ because the former is the company code and the latter is the number of employees for their PR subscription tier.  This process appears to be PEP related even though the affected clients have PEP disabled from the administrator login.  I have a case open with Sage but no further updates or resolutions at this time.  Best thing to do is just stop the application server, kill any other stranded pvxwin32.exe processes, and then start the aplication server.

Yes & yes. These are all upon login & also all had recent PR updates installed. Its been Advanced & Premium. We also have PEP disabled everywhere. Thanks for the info!! Glad I am not just going crazy & knew it had to be related somehow.

Yes & yes. These are all upon login & also all had recent PR updates installed. Its been Advanced & Premium. We also have PEP disabled everywhere. Thanks for the info!! Glad I am not just going crazy & knew it had to be related somehow.

Were the users getting this message when trying to start Sage 100?

If yes, I have seen this on four clients now.  They were running different base versions of Advanced (2022.3, 2023.0, etc) but the common denominator was they all recently had Payroll 2.24.0 installed.

If you look at the processes on the application server, you should see the Sage 100 application server process capping out the CPU on one core.  If you add the Command line column to the details tab and expand it, you should see another process with command line arguments similar to the second process indicated in this screenshot.  This process was present on these clients that had this issue.  The "PRL" and "50" values in the command line may differ because the former is the company code and the latter is the number of employees for their PR subscription tier.  This process appears to be PEP related even though the affected clients have PEP disabled from the administrator login.  I have a case open with Sage but no further updates or resolutions at this time.  Best thing to do is just stop the application server, kill any other stranded pvxwin32.exe processes, and then start the aplication server.

Were the users getting this message when trying to start Sage 100?

If yes, I have seen this on four clients now.  They were running different base versions of Advanced (2022.3, 2023.0, etc) but the common denominator was they all recently had Payroll 2.24.0 installed.

If you look at the processes on the application server, you should see the Sage 100 application server process capping out the CPU on one core.  If you add the Command line column to the details tab and expand it, you should see another process with command line arguments similar to the second process indicated in this screenshot.  This process was present on these clients that had this issue.  The "PRL" and "50" values in the command line may differ because the former is the company code and the latter is the number of employees for their PR subscription tier.  This process appears to be PEP related even though the affected clients have PEP disabled from the administrator login.  I have a case open with Sage but no further updates or resolutions at this time.  Best thing to do is just stop the application server, kill any other stranded pvxwin32.exe processes, and then start the aplication server.

After installing PR 2.24 did you force the "Payroll > Utilities > Payroll Tax Update"?  (I'm wondering if that is what the stray process is doing...).

Were the users getting this message when trying to start Sage 100?

If yes, I have seen this on four clients now.  They were running different base versions of Advanced (2022.3, 2023.0, etc) but the common denominator was they all recently had Payroll 2.24.0 installed.

If you look at the processes on the application server, you should see the Sage 100 application server process capping out the CPU on one core.  If you add the Command line column to the details tab and expand it, you should see another process with command line arguments similar to the second process indicated in this screenshot.  This process was present on these clients that had this issue.  The "PRL" and "50" values in the command line may differ because the former is the company code and the latter is the number of employees for their PR subscription tier.  This process appears to be PEP related even though the affected clients have PEP disabled from the administrator login.  I have a case open with Sage but no further updates or resolutions at this time.  Best thing to do is just stop the application server, kill any other stranded pvxwin32.exe processes, and then start the aplication server.