Not sure if it a hard rule, just a generally accepted SOP. In my case, it was my server, somewhat vanilla install (some scripts), no enhancements, no CC processing, sales tax, etc. If it went south, then I could work the weekend to fix it or just start over. As @Beth Bowers indicates, it depends.
Bottomline Software, Inc.
Original Message:
Sent: 05-03-2024 10:41
From: David Overholt
Subject: Sage 100 v2022 32-bit to 64-bit - Sync Worked Fine
Good to know! That saves a step; at least in some cases!
Original Message:
Sent: 5/3/2024 10:32:00 AM
From: Beth Bowers
Subject: RE: Sage 100 v2022 32-bit to 64-bit - Sync Worked Fine
It kind of depends on how you handle the workstations for testing. I have users testing via RDP to the server (so I bypass the whole Crystal thing, too) and go directly from 32 to 64.
------------------------------
Beth Bowers
(269) 358-0989
------------------------------
Original Message:
Sent: 05-03-2024 10:29
From: David Overholt
Subject: Sage 100 v2022 32-bit to 64-bit - Sync Worked Fine
Did something change recently? I thought you could not migrate from 32-bit directly to 64-bit. I have a note that the steps were to first migrate from 32-bit and to 32-bit. Then after migration and conversion you could swap it to 64 bit.
Original Message:
Sent: 5/3/2024 10:13:00 AM
From: Jeff Schwenk
Subject: RE: Sage 100 v2022 32-bit to 64-bit - Sync Worked Fine
It is these types of issues that Sage needs to be aware of. When I installed 64Bit for the first time, it was on a new server image and I just migrated from the 32 bit install. With the end of life being announced for 32, we need to get the bandwagon rolling...
------------------------------
Jeff Schwenk
Bottomline Software, Inc.
(540) 221-4444
Original Message:
Sent: 05-03-2024 09:41
From: Wayne Schulz
Subject: Sage 100 v2022 32-bit to 64-bit - Sync Worked Fine
When I've encountered issues with the service not starting or being unable to uninstall it, I've occasionally used a Google search to find a way to remove it through what I believe was a direct registry edit. However, I really try to avoid doing these types of things, especially on a server, and even more so if that server is used for more than just Sage 100.
One of my concerns is that when we, as consultants, make these "easy" changes for free, the customer often sees it as us taking ownership of all problems that may arise in the next 30 days, regardless of whether they are related to the free update we provided or not.
------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT
Original Message:
Sent: 05-03-2024 08:38
From: Susan Pawlowic
Subject: Sage 100 v2022 32-bit to 64-bit - Sync Worked Fine
I did this for an Advanced client, and the service became corrupted. Uninstalling the service and rebooting did not help; the service still lurked somewhere behind the scenes and would not allow itself to be recreated or started, nor did starting Application Service work. Ultimately I had to recreate the service for a different port number. Fortunately for this client all users logged into one RDS, so we only had to uninstall/reinstall one workstation. If anyone has any tips on how to avoid this, I'll be better prepared for the next one!
------------------------------
Susan Pawlowic
Sage 100 Solutions Architect
RKL eSolutions, LLC
spawlowic@rklesolutions.com
(717) 735-9109 Ext. 4352
Original Message:
Sent: 05-02-2024 09:05
From: Wayne Schulz
Subject: Sage 100 v2022 32-bit to 64-bit - Sync Worked Fine
Yes this was standard so I don't know what impact this might have on the workstations for an Advanced or Premium. Perhaps someone else will share recent expriences.
------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT
Original Message:
Sent: 05-01-2024 16:47
From: Jeff Schwenk
Subject: Sage 100 v2022 32-bit to 64-bit - Sync Worked Fine
I am assuming this was a STD installation???
------------------------------
Jeff Schwenk
Bottomline Software, Inc.
(540) 221-4444