Sage 100

Client is upgrading from Sage 2018 Standard to 2022 Premium. 2022 Premium is on a new server. All client's connect via a terminal server. This same term server will be used for 2022. For the testing period I have installed both clients on the terminal server. They are not able to put up another terminal server for testing.

The issue is this: Paperless Office will only work from one or the other, but not both. Running PL_AdvancedOptions_UI fixes the version it was run from but breaks the other. Errors are: 'unable to process the lockfile' and 'printer not activated'.

I have noticed that 2018 creates the expected registry entries under HKEY_CURRENT_CONFIG but 2022 removes them. Is that a Premuim thing or a terminal server thing? I thought those reg entries were always created. Not sure how 2022 works without them? Maybe they are in a different location in the registry?

If anyone has any experience with this and knows a work around, I would appreciate it.

TIA

------------------------------
Greg Stiles
S & W Microsystems
------------------------------

The path for 2018 and 2022 are different. 
2022 now keeps paperless registry in:
HKLM\Software\Sage 100 PDF Converter (This one has the Jobs and Locks keys)
HKCU\Software\Sage 100 PDF Converter 

What I suspect may be happening is that every time you run the PL_Advanced_Options_UI on a version (2018 vs. 2022), it's putting its own registries corresponding to the respective version (not sure if it's removing the older ones, but that could be the key to the failure if it's doing that)

I haven't tested this, but it's something you can maybe try:
- Export the registry key in HKEY_CURRENT_CONFIG\Software\Sage PDF Converter (as a backup.reg)
- Run PL_ADVANCEDOPTIONS_UI from 2022 (this will place the HKLM) registries
- Now run reimport that backed-up file back into HKCC. 

Now you'll end up with the registry entries that match both 2018 and 2022. 

This is definitely a hack, and I don't know if there are other dependencies that Sage 2018 would be relying on other than the registry that could cause the "Printer not activated error".

Caveat: you must make sure not to re-run the PL_ADVANCEDOPTIONS_UI until your go-live, and when you remove your 2018; otherwise, you'd be back at square 1 :) 

Maybe someone else might have a better idea on this.

Especially during migrations, we tend to see a lot of paperless issues to address, so this article may also help you with some things that may come up
https://support.gotomyerp.com/portal/en/kb/articles/addressing-paperless-office-printer-problems

------------------------------
George Khairallah
CTO | gotomyerp, LLC
george.k@gotomyerp.com |
------------------------------

AFAIK the workaround is not to run two versions of Sage 100 that use different Amyuni versions on the same workstation setup.
I think Amyuni version changed in 2019
In practicality, I setup 2022 then go into 2018 and run PL_AdvancedOptions_UI so that 2018 is back working for so long as the customer is on v2018.

Then have the 2022 folks test and if they need to post use a deferred printer. You're likely going to wipe their 2022 data on a reconvert anyways.

When they don't believe you, then 800-854-3415 and have them spend their time debating Sage.

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

AFAIK there is no work-around for the new v2019 Paperless driver's lack of backwards compatibility.  We warn users about how this complicates testing.  One works, or the other.  As you know, the steps to change back and forth are not arduous, but it's been a known issue since the release of v2019.

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

Thanks everyone, appreciate the info. They will adjust their testing plan accordingly.

------------------------------
Greg Stiles
S & W Microsystems
------------------------------

Original Message:
Sent: 04-20-2023 10:36
From: Kevin Moyes
Subject: sage 100 2018 and sage 100 2022 on the same terminal server - paperless will only work from one at a time

AFAIK there is no work-around for the new v2019 Paperless driver's lack of backwards compatibility.  We warn users about how this complicates testing.  One works, or the other.  As you know, the steps to change back and forth are not arduous, but it's been a known issue since the release of v2019.

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