Sage 100

@Alnoor Cassim told me that the fix that Sage was working on failed, and that they had to turn their attention to getting v2024 ready to release. 

In essence, that means effective immediately, all Sage 100 upgrades or new implementations should be installed at 64-bit.

I'll bet $100 that Sage hasn't queried their endorsed partners to see if their solutions are fully 64-bit.

@Alnoor Cassim told me that the fix that Sage was working on failed, and that they had to turn their attention to getting v2024 ready to release. 

@Wayne Schulz We can't "install" at 64-Bit if the client is not setting up a brand new application server.  Any 64-Bit Sage Install on a server running 32-Bit will break the old version.  Instead, we are installing 32-Bit for upgrades and then a week or month later, suggesting we do the change to move them to 64-Bit.  Confirming all Workstation Clients are already at 64-Bit (workstations really should already be at 64-Bit ) and that their 3-rd party add-on products support 64-Bit.  Simple instructions at server, and workstation Sync for all user PC's.  It is easy to flip back to 32-Bit if necessary but we have not seen it to be necessary for anyone.  

In essence, that means effective immediately, all Sage 100 upgrades or new implementations should be installed at 64-bit.

I'll bet $100 that Sage hasn't queried their endorsed partners to see if their solutions are fully 64-bit.

@Alnoor Cassim told me that the fix that Sage was working on failed, and that they had to turn their attention to getting v2024 ready to release. 

@Wayne Schulz We can't "install" at 64-Bit if the client is not setting up a brand new application server.  Any 64-Bit Sage Install on a server running 32-Bit will break the old version.  Instead, we are installing 32-Bit for upgrades and then a week or month later, suggesting we do the change to move them to 64-Bit.  Confirming all Workstation Clients are already at 64-Bit (workstations really should already be at 64-Bit ) and that their 3-rd party add-on products support 64-Bit.  Simple instructions at server, and workstation Sync for all user PC's.  It is easy to flip back to 32-Bit if necessary but we have not seen it to be necessary for anyone.  

In essence, that means effective immediately, all Sage 100 upgrades or new implementations should be installed at 64-bit.

I'll bet $100 that Sage hasn't queried their endorsed partners to see if their solutions are fully 64-bit.

@Alnoor Cassim told me that the fix that Sage was working on failed, and that they had to turn their attention to getting v2024 ready to release. 

This situation begs for a checklist that can be given to a customer's IT department, or we perform the work for a fee. 

The checklist would primarily be for customers who call with the DTR hanging issue and aren't willing to wait and use one of the workarounds but instead request the 32-to-64-bit upgrade.

On the surface, running this utility seems simple until it's not.

From what I can understand: 

1. Need to have all workstations on 64-bit Windows
2. 64-bit is only available for Sage 100 2021+
3. Any older Sage 100 32-bit versions that the customer may be accessing ( backup copies - think old Payroll archives ) won't work
4. All integrations must be 64-bit compatible (and there is no standard document anywhere that I've seen listing which integrations are compatible)

My customers will say either

a) they don't know or

b)they do know that everything is compatible.

Then, when we go to make the migration ( outside of a planned upgrade ), we will 75% of the time have a good chance of being stuck debugging one or two pesky workstations/integrations. And if we haven't charged a fee for this, we are now the unpaid Sage warranty department fixing a "recall" issue.

@Wayne Schulz We can't "install" at 64-Bit if the client is not setting up a brand new application server.  Any 64-Bit Sage Install on a server running 32-Bit will break the old version.  Instead, we are installing 32-Bit for upgrades and then a week or month later, suggesting we do the change to move them to 64-Bit.  Confirming all Workstation Clients are already at 64-Bit (workstations really should already be at 64-Bit ) and that their 3-rd party add-on products support 64-Bit.  Simple instructions at server, and workstation Sync for all user PC's.  It is easy to flip back to 32-Bit if necessary but we have not seen it to be necessary for anyone.  

In essence, that means effective immediately, all Sage 100 upgrades or new implementations should be installed at 64-bit.

I'll bet $100 that Sage hasn't queried their endorsed partners to see if their solutions are fully 64-bit.

@Alnoor Cassim told me that the fix that Sage was working on failed, and that they had to turn their attention to getting v2024 ready to release. 

Also note that Sage Fixed Assets and HRMS are still 32-bit only, and will have Crystal runtime issues if Sage 100 is 64bit.

This situation begs for a checklist that can be given to a customer's IT department, or we perform the work for a fee. 

The checklist would primarily be for customers who call with the DTR hanging issue and aren't willing to wait and use one of the workarounds but instead request the 32-to-64-bit upgrade.

On the surface, running this utility seems simple until it's not.

From what I can understand: 

1. Need to have all workstations on 64-bit Windows
2. 64-bit is only available for Sage 100 2021+
3. Any older Sage 100 32-bit versions that the customer may be accessing ( backup copies - think old Payroll archives ) won't work
4. All integrations must be 64-bit compatible (and there is no standard document anywhere that I've seen listing which integrations are compatible)

My customers will say either

a) they don't know or

b)they do know that everything is compatible.

Then, when we go to make the migration ( outside of a planned upgrade ), we will 75% of the time have a good chance of being stuck debugging one or two pesky workstations/integrations. And if we haven't charged a fee for this, we are now the unpaid Sage warranty department fixing a "recall" issue.

@Wayne Schulz We can't "install" at 64-Bit if the client is not setting up a brand new application server.  Any 64-Bit Sage Install on a server running 32-Bit will break the old version.  Instead, we are installing 32-Bit for upgrades and then a week or month later, suggesting we do the change to move them to 64-Bit.  Confirming all Workstation Clients are already at 64-Bit (workstations really should already be at 64-Bit ) and that their 3-rd party add-on products support 64-Bit.  Simple instructions at server, and workstation Sync for all user PC's.  It is easy to flip back to 32-Bit if necessary but we have not seen it to be necessary for anyone.  

In essence, that means effective immediately, all Sage 100 upgrades or new implementations should be installed at 64-bit.

I'll bet $100 that Sage hasn't queried their endorsed partners to see if their solutions are fully 64-bit.

@Alnoor Cassim told me that the fix that Sage was working on failed, and that they had to turn their attention to getting v2024 ready to release.