Sage 100

Were you able to come up with any resolution? 

I have a customer right now that has this issue. 

Fortunately, most of the users don't have to have both. But the CFO and Controller do and are not happy. Again.

According to this chart from January, I would have expected the latest HRMS release to be 13.0.30:

Were you able to come up with any resolution? 

I have a customer right now that has this issue. 

Fortunately, most of the users don't have to have both. But the CFO and Controller do and are not happy. Again.

Ahh - the Payroll in HRMS is the Sage 300 payroll...

According to this chart from January, I would have expected the latest HRMS release to be 13.0.30:

Were you able to come up with any resolution? 

I have a customer right now that has this issue. 

Fortunately, most of the users don't have to have both. But the CFO and Controller do and are not happy. Again.

The fix:

(1)  Uninstall the Sage 100 Crystal runtimes (13.30)

(2) Download  and install the 13.34 runtimes from SAP:

https://origin-az.softwaredownloads.sap.com/public/file/0020000000674342023

https://origin-az.softwaredownloads.sap.com/public/file/0020000000674412023

(3)  Uninstall the 13.34 runtimes  this will remove the embedded runtime installs done by HRMS/Sage 300

(4)  Install the 13.34 runtimes

Ahh - the Payroll in HRMS is the Sage 300 payroll...

According to this chart from January, I would have expected the latest HRMS release to be 13.0.30:

Were you able to come up with any resolution? 

I have a customer right now that has this issue. 

Fortunately, most of the users don't have to have both. But the CFO and Controller do and are not happy. Again.

Do you mean on (4) install the 13.30 Sage 100 runtimes? 

The fix:

(1)  Uninstall the Sage 100 Crystal runtimes (13.30)

(2) Download  and install the 13.34 runtimes from SAP:

https://origin-az.softwaredownloads.sap.com/public/file/0020000000674342023

https://origin-az.softwaredownloads.sap.com/public/file/0020000000674412023

(3)  Uninstall the 13.34 runtimes  this will remove the embedded runtime installs done by HRMS/Sage 300

(4)  Install the 13.34 runtimes

Ahh - the Payroll in HRMS is the Sage 300 payroll...

According to this chart from January, I would have expected the latest HRMS release to be 13.0.30:

Were you able to come up with any resolution? 

I have a customer right now that has this issue. 

Fortunately, most of the users don't have to have both. But the CFO and Controller do and are not happy. Again.

The fix:

(1)  Uninstall the Sage 100 Crystal runtimes (13.30)

(2) Download  and install the 13.34 runtimes from SAP:

https://origin-az.softwaredownloads.sap.com/public/file/0020000000674342023

https://origin-az.softwaredownloads.sap.com/public/file/0020000000674412023

(3)  Uninstall the 13.34 runtimes  this will remove the embedded runtime installs done by HRMS/Sage 300

(4)  Install the 13.34 runtimes

Ahh - the Payroll in HRMS is the Sage 300 payroll...

According to this chart from January, I would have expected the latest HRMS release to be 13.0.30:

Were you able to come up with any resolution? 

I have a customer right now that has this issue. 

Fortunately, most of the users don't have to have both. But the CFO and Controller do and are not happy. Again.

And after this, you may have to uninstall and reinstall the HRMS client to get printing working in HRMS....

The fix:

(1)  Uninstall the Sage 100 Crystal runtimes (13.30)

(2) Download  and install the 13.34 runtimes from SAP:

https://origin-az.softwaredownloads.sap.com/public/file/0020000000674342023

https://origin-az.softwaredownloads.sap.com/public/file/0020000000674412023

(3)  Uninstall the 13.34 runtimes  this will remove the embedded runtime installs done by HRMS/Sage 300

(4)  Install the 13.34 runtimes

Ahh - the Payroll in HRMS is the Sage 300 payroll...

According to this chart from January, I would have expected the latest HRMS release to be 13.0.30:

Were you able to come up with any resolution? 

I have a customer right now that has this issue. 

Fortunately, most of the users don't have to have both. But the CFO and Controller do and are not happy. Again.

Thank you. I was hoping with your description that both would be able to play together with the full 13.34 runtime installed. 

Unfortunately, this user is out until next Wednesday to try this. 

Sage indicated the KB was going to be updated with this information.

And after this, you may have to uninstall and reinstall the HRMS client to get printing working in HRMS....

The fix:

(1)  Uninstall the Sage 100 Crystal runtimes (13.30)

(2) Download  and install the 13.34 runtimes from SAP:

https://origin-az.softwaredownloads.sap.com/public/file/0020000000674342023

https://origin-az.softwaredownloads.sap.com/public/file/0020000000674412023

(3)  Uninstall the 13.34 runtimes  this will remove the embedded runtime installs done by HRMS/Sage 300

(4)  Install the 13.34 runtimes

Ahh - the Payroll in HRMS is the Sage 300 payroll...

According to this chart from January, I would have expected the latest HRMS release to be 13.0.30:

Were you able to come up with any resolution? 

I have a customer right now that has this issue. 

Fortunately, most of the users don't have to have both. But the CFO and Controller do and are not happy. Again.

A timely post.  This happened to a client running Sage 100 v2022 (Crystal 2016) and HRMS v10.7070 - Q2 2024.  Everything was working great until the Q2 2024 update was installed.  Apparently, there was no warning that this update was using Crystal 2020.  Sage 100 Custom reports stopped working.  When I reinstalled the Sage client, HRMS custom reports stopped working.

I deleted the Crystal runtimes (via the control panel).  I then launched the Sage 100 2023 workstation update.  The very first thing the installer did was install the two Crystal runtimes (below).  Once installed, I exited the installer (did not install the v2023 client).

Sage 100 2022 and HRMS can generate Crystal reports without issue.

Will post back if issues arise.

Fingers crossed.

Thank you. I was hoping with your description that both would be able to play together with the full 13.34 runtime installed. 

Unfortunately, this user is out until next Wednesday to try this. 

Sage indicated the KB was going to be updated with this information.

And after this, you may have to uninstall and reinstall the HRMS client to get printing working in HRMS....

The fix:

(1)  Uninstall the Sage 100 Crystal runtimes (13.30)

(2) Download  and install the 13.34 runtimes from SAP:

https://origin-az.softwaredownloads.sap.com/public/file/0020000000674342023

https://origin-az.softwaredownloads.sap.com/public/file/0020000000674412023

(3)  Uninstall the 13.34 runtimes  this will remove the embedded runtime installs done by HRMS/Sage 300

(4)  Install the 13.34 runtimes

Ahh - the Payroll in HRMS is the Sage 300 payroll...

According to this chart from January, I would have expected the latest HRMS release to be 13.0.30:

Were you able to come up with any resolution? 

I have a customer right now that has this issue. 

Fortunately, most of the users don't have to have both. But the CFO and Controller do and are not happy. Again.

Great post! 👍

A timely post.  This happened to a client running Sage 100 v2022 (Crystal 2016) and HRMS v10.7070 - Q2 2024.  Everything was working great until the Q2 2024 update was installed.  Apparently, there was no warning that this update was using Crystal 2020.  Sage 100 Custom reports stopped working.  When I reinstalled the Sage client, HRMS custom reports stopped working.

I deleted the Crystal runtimes (via the control panel).  I then launched the Sage 100 2023 workstation update.  The very first thing the installer did was install the two Crystal runtimes (below).  Once installed, I exited the installer (did not install the v2023 client).

Sage 100 2022 and HRMS can generate Crystal reports without issue.

Will post back if issues arise.

Fingers crossed.

Thank you. I was hoping with your description that both would be able to play together with the full 13.34 runtime installed. 

Unfortunately, this user is out until next Wednesday to try this. 

Sage indicated the KB was going to be updated with this information.

And after this, you may have to uninstall and reinstall the HRMS client to get printing working in HRMS....

The fix:

(1)  Uninstall the Sage 100 Crystal runtimes (13.30)

(2) Download  and install the 13.34 runtimes from SAP:

https://origin-az.softwaredownloads.sap.com/public/file/0020000000674342023

https://origin-az.softwaredownloads.sap.com/public/file/0020000000674412023

(3)  Uninstall the 13.34 runtimes  this will remove the embedded runtime installs done by HRMS/Sage 300

(4)  Install the 13.34 runtimes

Ahh - the Payroll in HRMS is the Sage 300 payroll...

According to this chart from January, I would have expected the latest HRMS release to be 13.0.30:

Were you able to come up with any resolution? 

I have a customer right now that has this issue. 

Fortunately, most of the users don't have to have both. But the CFO and Controller do and are not happy. Again.

Indeed!  (Finding simple fixes to Crystal Reports runtime issues is always difficult).

I'm guessing the MSI's (plus .NET 4.8?) would suffice...

Great post! 👍

A timely post.  This happened to a client running Sage 100 v2022 (Crystal 2016) and HRMS v10.7070 - Q2 2024.  Everything was working great until the Q2 2024 update was installed.  Apparently, there was no warning that this update was using Crystal 2020.  Sage 100 Custom reports stopped working.  When I reinstalled the Sage client, HRMS custom reports stopped working.

I deleted the Crystal runtimes (via the control panel).  I then launched the Sage 100 2023 workstation update.  The very first thing the installer did was install the two Crystal runtimes (below).  Once installed, I exited the installer (did not install the v2023 client).

Sage 100 2022 and HRMS can generate Crystal reports without issue.

Will post back if issues arise.

Fingers crossed.

Thank you. I was hoping with your description that both would be able to play together with the full 13.34 runtime installed. 

Unfortunately, this user is out until next Wednesday to try this. 

Sage indicated the KB was going to be updated with this information.

And after this, you may have to uninstall and reinstall the HRMS client to get printing working in HRMS....

The fix:

(1)  Uninstall the Sage 100 Crystal runtimes (13.30)

(2) Download  and install the 13.34 runtimes from SAP:

https://origin-az.softwaredownloads.sap.com/public/file/0020000000674342023

https://origin-az.softwaredownloads.sap.com/public/file/0020000000674412023

(3)  Uninstall the 13.34 runtimes  this will remove the embedded runtime installs done by HRMS/Sage 300

(4)  Install the 13.34 runtimes

Ahh - the Payroll in HRMS is the Sage 300 payroll...

According to this chart from January, I would have expected the latest HRMS release to be 13.0.30:

Were you able to come up with any resolution? 

I have a customer right now that has this issue. 

Fortunately, most of the users don't have to have both. But the CFO and Controller do and are not happy. Again.

Some day I envision Sage business units actually speaking with each other. 

Indeed!  (Finding simple fixes to Crystal Reports runtime issues is always difficult).

I'm guessing the MSI's (plus .NET 4.8?) would suffice...

Great post! 👍

A timely post.  This happened to a client running Sage 100 v2022 (Crystal 2016) and HRMS v10.7070 - Q2 2024.  Everything was working great until the Q2 2024 update was installed.  Apparently, there was no warning that this update was using Crystal 2020.  Sage 100 Custom reports stopped working.  When I reinstalled the Sage client, HRMS custom reports stopped working.

I deleted the Crystal runtimes (via the control panel).  I then launched the Sage 100 2023 workstation update.  The very first thing the installer did was install the two Crystal runtimes (below).  Once installed, I exited the installer (did not install the v2023 client).

Sage 100 2022 and HRMS can generate Crystal reports without issue.

Will post back if issues arise.

Fingers crossed.

Thank you. I was hoping with your description that both would be able to play together with the full 13.34 runtime installed. 

Unfortunately, this user is out until next Wednesday to try this. 

Sage indicated the KB was going to be updated with this information.

And after this, you may have to uninstall and reinstall the HRMS client to get printing working in HRMS....

The fix:

(1)  Uninstall the Sage 100 Crystal runtimes (13.30)

(2) Download  and install the 13.34 runtimes from SAP:

https://origin-az.softwaredownloads.sap.com/public/file/0020000000674342023

https://origin-az.softwaredownloads.sap.com/public/file/0020000000674412023

(3)  Uninstall the 13.34 runtimes  this will remove the embedded runtime installs done by HRMS/Sage 300

(4)  Install the 13.34 runtimes

Ahh - the Payroll in HRMS is the Sage 300 payroll...

According to this chart from January, I would have expected the latest HRMS release to be 13.0.30:

Were you able to come up with any resolution? 

I have a customer right now that has this issue. 

Fortunately, most of the users don't have to have both. But the CFO and Controller do and are not happy. Again.

Blame for this one is something I'd lay at the feet of SAP.  Programming the CR runtime updates to not be backwards compatible is simply evil / insanity.  Sage could certainly do a better job of communication around the conflicts, but they don't control a big piece of this.

Some day I envision Sage business units actually speaking with each other. 

Indeed!  (Finding simple fixes to Crystal Reports runtime issues is always difficult).

I'm guessing the MSI's (plus .NET 4.8?) would suffice...

Great post! 👍

A timely post.  This happened to a client running Sage 100 v2022 (Crystal 2016) and HRMS v10.7070 - Q2 2024.  Everything was working great until the Q2 2024 update was installed.  Apparently, there was no warning that this update was using Crystal 2020.  Sage 100 Custom reports stopped working.  When I reinstalled the Sage client, HRMS custom reports stopped working.

I deleted the Crystal runtimes (via the control panel).  I then launched the Sage 100 2023 workstation update.  The very first thing the installer did was install the two Crystal runtimes (below).  Once installed, I exited the installer (did not install the v2023 client).

Sage 100 2022 and HRMS can generate Crystal reports without issue.

Will post back if issues arise.

Fingers crossed.

Thank you. I was hoping with your description that both would be able to play together with the full 13.34 runtime installed. 

Unfortunately, this user is out until next Wednesday to try this. 

Sage indicated the KB was going to be updated with this information.

And after this, you may have to uninstall and reinstall the HRMS client to get printing working in HRMS....

The fix:

(1)  Uninstall the Sage 100 Crystal runtimes (13.30)

(2) Download  and install the 13.34 runtimes from SAP:

https://origin-az.softwaredownloads.sap.com/public/file/0020000000674342023

https://origin-az.softwaredownloads.sap.com/public/file/0020000000674412023

(3)  Uninstall the 13.34 runtimes  this will remove the embedded runtime installs done by HRMS/Sage 300

(4)  Install the 13.34 runtimes

Ahh - the Payroll in HRMS is the Sage 300 payroll...

According to this chart from January, I would have expected the latest HRMS release to be 13.0.30:

Were you able to come up with any resolution? 

I have a customer right now that has this issue. 

Fortunately, most of the users don't have to have both. But the CFO and Controller do and are not happy. Again.

>>Sage could certainly do a better job of communication around the conflicts, but they don't control a big piece of this.

So, wait, what? Sage doesn't control the version of Crystal runtime that they use in their own products and doesn't have a duty to ensure that there aren't conflicts with their own products?

Blame for this one is something I'd lay at the feet of SAP.  Programming the CR runtime updates to not be backwards compatible is simply evil / insanity.  Sage could certainly do a better job of communication around the conflicts, but they don't control a big piece of this.

Some day I envision Sage business units actually speaking with each other. 

Indeed!  (Finding simple fixes to Crystal Reports runtime issues is always difficult).

I'm guessing the MSI's (plus .NET 4.8?) would suffice...

Great post! 👍

A timely post.  This happened to a client running Sage 100 v2022 (Crystal 2016) and HRMS v10.7070 - Q2 2024.  Everything was working great until the Q2 2024 update was installed.  Apparently, there was no warning that this update was using Crystal 2020.  Sage 100 Custom reports stopped working.  When I reinstalled the Sage client, HRMS custom reports stopped working.

I deleted the Crystal runtimes (via the control panel).  I then launched the Sage 100 2023 workstation update.  The very first thing the installer did was install the two Crystal runtimes (below).  Once installed, I exited the installer (did not install the v2023 client).

Sage 100 2022 and HRMS can generate Crystal reports without issue.

Will post back if issues arise.

Fingers crossed.

Thank you. I was hoping with your description that both would be able to play together with the full 13.34 runtime installed. 

Unfortunately, this user is out until next Wednesday to try this. 

Sage indicated the KB was going to be updated with this information.

And after this, you may have to uninstall and reinstall the HRMS client to get printing working in HRMS....

The fix:

(1)  Uninstall the Sage 100 Crystal runtimes (13.30)

(2) Download  and install the 13.34 runtimes from SAP:

https://origin-az.softwaredownloads.sap.com/public/file/0020000000674342023

https://origin-az.softwaredownloads.sap.com/public/file/0020000000674412023

(3)  Uninstall the 13.34 runtimes  this will remove the embedded runtime installs done by HRMS/Sage 300

(4)  Install the 13.34 runtimes

Ahh - the Payroll in HRMS is the Sage 300 payroll...

According to this chart from January, I would have expected the latest HRMS release to be 13.0.30:

Were you able to come up with any resolution? 

I have a customer right now that has this issue. 

Fortunately, most of the users don't have to have both. But the CFO and Controller do and are not happy. Again.

Sage teams work in isolation.  "One Sage" is only a marketing strategy, not an indication of cohesive teamwork... but you know that already.

Technically, using the latest version of runtimes (to include all the latest bug fixes) is something each team will want to do... understandably.  But Sage has no internal communication (or outward communication) about how that impacts other Sage products... with the root cause of problems being SAP not making updates backwards compatible.  Can you imagine M$ releasing a new version of Word that can't open an old .doc file?

>>Sage could certainly do a better job of communication around the conflicts, but they don't control a big piece of this.

So, wait, what? Sage doesn't control the version of Crystal runtime that they use in their own products and doesn't have a duty to ensure that there aren't conflicts with their own products?

Blame for this one is something I'd lay at the feet of SAP.  Programming the CR runtime updates to not be backwards compatible is simply evil / insanity.  Sage could certainly do a better job of communication around the conflicts, but they don't control a big piece of this.

Some day I envision Sage business units actually speaking with each other. 

Indeed!  (Finding simple fixes to Crystal Reports runtime issues is always difficult).

I'm guessing the MSI's (plus .NET 4.8?) would suffice...

Great post! 👍

A timely post.  This happened to a client running Sage 100 v2022 (Crystal 2016) and HRMS v10.7070 - Q2 2024.  Everything was working great until the Q2 2024 update was installed.  Apparently, there was no warning that this update was using Crystal 2020.  Sage 100 Custom reports stopped working.  When I reinstalled the Sage client, HRMS custom reports stopped working.

I deleted the Crystal runtimes (via the control panel).  I then launched the Sage 100 2023 workstation update.  The very first thing the installer did was install the two Crystal runtimes (below).  Once installed, I exited the installer (did not install the v2023 client).

Sage 100 2022 and HRMS can generate Crystal reports without issue.

Will post back if issues arise.

Fingers crossed.

Thank you. I was hoping with your description that both would be able to play together with the full 13.34 runtime installed. 

Unfortunately, this user is out until next Wednesday to try this. 

Sage indicated the KB was going to be updated with this information.

And after this, you may have to uninstall and reinstall the HRMS client to get printing working in HRMS....

The fix:

(1)  Uninstall the Sage 100 Crystal runtimes (13.30)

(2) Download  and install the 13.34 runtimes from SAP:

https://origin-az.softwaredownloads.sap.com/public/file/0020000000674342023

https://origin-az.softwaredownloads.sap.com/public/file/0020000000674412023

(3)  Uninstall the 13.34 runtimes  this will remove the embedded runtime installs done by HRMS/Sage 300

(4)  Install the 13.34 runtimes

Ahh - the Payroll in HRMS is the Sage 300 payroll...

According to this chart from January, I would have expected the latest HRMS release to be 13.0.30:

Were you able to come up with any resolution? 

I have a customer right now that has this issue. 

Fortunately, most of the users don't have to have both. But the CFO and Controller do and are not happy. Again.

Isn't forward compatibility the issue, not backward compatibility?  Crystal version 20 can run a report created in version 16.  The issue I run into is forms and reports in Sage 100 don't run because there is a higher version of the run time program installed on the computer, typically by another application that uses Crystal.

Sage teams work in isolation.  "One Sage" is only a marketing strategy, not an indication of cohesive teamwork... but you know that already.

Technically, using the latest version of runtimes (to include all the latest bug fixes) is something each team will want to do... understandably.  But Sage has no internal communication (or outward communication) about how that impacts other Sage products... with the root cause of problems being SAP not making updates backwards compatible.  Can you imagine M$ releasing a new version of Word that can't open an old .doc file?

>>Sage could certainly do a better job of communication around the conflicts, but they don't control a big piece of this.

So, wait, what? Sage doesn't control the version of Crystal runtime that they use in their own products and doesn't have a duty to ensure that there aren't conflicts with their own products?

Blame for this one is something I'd lay at the feet of SAP.  Programming the CR runtime updates to not be backwards compatible is simply evil / insanity.  Sage could certainly do a better job of communication around the conflicts, but they don't control a big piece of this.

Some day I envision Sage business units actually speaking with each other. 

Indeed!  (Finding simple fixes to Crystal Reports runtime issues is always difficult).

I'm guessing the MSI's (plus .NET 4.8?) would suffice...

Great post! 👍

A timely post.  This happened to a client running Sage 100 v2022 (Crystal 2016) and HRMS v10.7070 - Q2 2024.  Everything was working great until the Q2 2024 update was installed.  Apparently, there was no warning that this update was using Crystal 2020.  Sage 100 Custom reports stopped working.  When I reinstalled the Sage client, HRMS custom reports stopped working.

I deleted the Crystal runtimes (via the control panel).  I then launched the Sage 100 2023 workstation update.  The very first thing the installer did was install the two Crystal runtimes (below).  Once installed, I exited the installer (did not install the v2023 client).

Sage 100 2022 and HRMS can generate Crystal reports without issue.

Will post back if issues arise.

Fingers crossed.

Thank you. I was hoping with your description that both would be able to play together with the full 13.34 runtime installed. 

Unfortunately, this user is out until next Wednesday to try this. 

Sage indicated the KB was going to be updated with this information.

And after this, you may have to uninstall and reinstall the HRMS client to get printing working in HRMS....

The fix:

(1)  Uninstall the Sage 100 Crystal runtimes (13.30)

(2) Download  and install the 13.34 runtimes from SAP:

https://origin-az.softwaredownloads.sap.com/public/file/0020000000674342023

https://origin-az.softwaredownloads.sap.com/public/file/0020000000674412023

(3)  Uninstall the 13.34 runtimes  this will remove the embedded runtime installs done by HRMS/Sage 300

(4)  Install the 13.34 runtimes

Ahh - the Payroll in HRMS is the Sage 300 payroll...

According to this chart from January, I would have expected the latest HRMS release to be 13.0.30:

Were you able to come up with any resolution? 

I have a customer right now that has this issue. 

Fortunately, most of the users don't have to have both. But the CFO and Controller do and are not happy. Again.

Isn't forward compatibility the issue, not backward compatibility?  Crystal version 20 can run a report created in version 16.  The issue I run into is forms and reports in Sage 100 don't run because there is a higher version of the run time program installed on the computer, typically by another application that uses Crystal.

Sage teams work in isolation.  "One Sage" is only a marketing strategy, not an indication of cohesive teamwork... but you know that already.

Technically, using the latest version of runtimes (to include all the latest bug fixes) is something each team will want to do... understandably.  But Sage has no internal communication (or outward communication) about how that impacts other Sage products... with the root cause of problems being SAP not making updates backwards compatible.  Can you imagine M$ releasing a new version of Word that can't open an old .doc file?

>>Sage could certainly do a better job of communication around the conflicts, but they don't control a big piece of this.

So, wait, what? Sage doesn't control the version of Crystal runtime that they use in their own products and doesn't have a duty to ensure that there aren't conflicts with their own products?

Blame for this one is something I'd lay at the feet of SAP.  Programming the CR runtime updates to not be backwards compatible is simply evil / insanity.  Sage could certainly do a better job of communication around the conflicts, but they don't control a big piece of this.

Some day I envision Sage business units actually speaking with each other. 

Indeed!  (Finding simple fixes to Crystal Reports runtime issues is always difficult).

I'm guessing the MSI's (plus .NET 4.8?) would suffice...

Great post! 👍

A timely post.  This happened to a client running Sage 100 v2022 (Crystal 2016) and HRMS v10.7070 - Q2 2024.  Everything was working great until the Q2 2024 update was installed.  Apparently, there was no warning that this update was using Crystal 2020.  Sage 100 Custom reports stopped working.  When I reinstalled the Sage client, HRMS custom reports stopped working.

I deleted the Crystal runtimes (via the control panel).  I then launched the Sage 100 2023 workstation update.  The very first thing the installer did was install the two Crystal runtimes (below).  Once installed, I exited the installer (did not install the v2023 client).

Sage 100 2022 and HRMS can generate Crystal reports without issue.

Will post back if issues arise.

Fingers crossed.

Thank you. I was hoping with your description that both would be able to play together with the full 13.34 runtime installed. 

Unfortunately, this user is out until next Wednesday to try this. 

Sage indicated the KB was going to be updated with this information.

And after this, you may have to uninstall and reinstall the HRMS client to get printing working in HRMS....

The fix:

(1)  Uninstall the Sage 100 Crystal runtimes (13.30)

(2) Download  and install the 13.34 runtimes from SAP:

https://origin-az.softwaredownloads.sap.com/public/file/0020000000674342023

https://origin-az.softwaredownloads.sap.com/public/file/0020000000674412023

(3)  Uninstall the 13.34 runtimes  this will remove the embedded runtime installs done by HRMS/Sage 300

(4)  Install the 13.34 runtimes

Ahh - the Payroll in HRMS is the Sage 300 payroll...

According to this chart from January, I would have expected the latest HRMS release to be 13.0.30:

Were you able to come up with any resolution? 

I have a customer right now that has this issue. 

Fortunately, most of the users don't have to have both. But the CFO and Controller do and are not happy. Again.

Po-teh-to, Po-tah-to.

Commands from a program to produce output using ABC123.rpt with parameters [1,a,3] and data source {whatever}... should continue to work with higher version of the runtime engine.  I'd expect problems if the report used was higher than the runtime is designed for... but installing a newer runtime shouldn't break programs designed to work with an older runtime. 

(I'm sure I'm not the only one to remember the nightmares of DLL H3LL in the late 90's / early 2K's... SAP should do better... seriously... this stuff is not exactly new problem type).

Isn't forward compatibility the issue, not backward compatibility?  Crystal version 20 can run a report created in version 16.  The issue I run into is forms and reports in Sage 100 don't run because there is a higher version of the run time program installed on the computer, typically by another application that uses Crystal.

Sage teams work in isolation.  "One Sage" is only a marketing strategy, not an indication of cohesive teamwork... but you know that already.

Technically, using the latest version of runtimes (to include all the latest bug fixes) is something each team will want to do... understandably.  But Sage has no internal communication (or outward communication) about how that impacts other Sage products... with the root cause of problems being SAP not making updates backwards compatible.  Can you imagine M$ releasing a new version of Word that can't open an old .doc file?

>>Sage could certainly do a better job of communication around the conflicts, but they don't control a big piece of this.

So, wait, what? Sage doesn't control the version of Crystal runtime that they use in their own products and doesn't have a duty to ensure that there aren't conflicts with their own products?

Blame for this one is something I'd lay at the feet of SAP.  Programming the CR runtime updates to not be backwards compatible is simply evil / insanity.  Sage could certainly do a better job of communication around the conflicts, but they don't control a big piece of this.

Some day I envision Sage business units actually speaking with each other. 

Indeed!  (Finding simple fixes to Crystal Reports runtime issues is always difficult).

I'm guessing the MSI's (plus .NET 4.8?) would suffice...

Great post! 👍

A timely post.  This happened to a client running Sage 100 v2022 (Crystal 2016) and HRMS v10.7070 - Q2 2024.  Everything was working great until the Q2 2024 update was installed.  Apparently, there was no warning that this update was using Crystal 2020.  Sage 100 Custom reports stopped working.  When I reinstalled the Sage client, HRMS custom reports stopped working.

I deleted the Crystal runtimes (via the control panel).  I then launched the Sage 100 2023 workstation update.  The very first thing the installer did was install the two Crystal runtimes (below).  Once installed, I exited the installer (did not install the v2023 client).

Sage 100 2022 and HRMS can generate Crystal reports without issue.

Will post back if issues arise.

Fingers crossed.

Thank you. I was hoping with your description that both would be able to play together with the full 13.34 runtime installed. 

Unfortunately, this user is out until next Wednesday to try this. 

Sage indicated the KB was going to be updated with this information.

And after this, you may have to uninstall and reinstall the HRMS client to get printing working in HRMS....

The fix:

(1)  Uninstall the Sage 100 Crystal runtimes (13.30)

(2) Download  and install the 13.34 runtimes from SAP:

https://origin-az.softwaredownloads.sap.com/public/file/0020000000674342023

https://origin-az.softwaredownloads.sap.com/public/file/0020000000674412023

(3)  Uninstall the 13.34 runtimes  this will remove the embedded runtime installs done by HRMS/Sage 300

(4)  Install the 13.34 runtimes

Ahh - the Payroll in HRMS is the Sage 300 payroll...

According to this chart from January, I would have expected the latest HRMS release to be 13.0.30:

Were you able to come up with any resolution? 

I have a customer right now that has this issue. 

Fortunately, most of the users don't have to have both. But the CFO and Controller do and are not happy. Again.

Agreed.  We and particularly the customers shouldn't have to deal with this crap.  It should just work.  The customer doesn't care nor should they if it is forward, backward, or sideways compatibility or any other reason it doesn't work.  if Sage can't or won;t work with SAP to solve the issue then the least they can do is insure compatibility of Crystal between integrated solutions.  You know, if HRMS is using Crystal 2020 then Sage 100 needs to use version 2020. 

Po-teh-to, Po-tah-to.

Commands from a program to produce output using ABC123.rpt with parameters [1,a,3] and data source {whatever}... should continue to work with higher version of the runtime engine.  I'd expect problems if the report used was higher than the runtime is designed for... but installing a newer runtime shouldn't break programs designed to work with an older runtime. 

(I'm sure I'm not the only one to remember the nightmares of DLL H3LL in the late 90's / early 2K's... SAP should do better... seriously... this stuff is not exactly new problem type).

Isn't forward compatibility the issue, not backward compatibility?  Crystal version 20 can run a report created in version 16.  The issue I run into is forms and reports in Sage 100 don't run because there is a higher version of the run time program installed on the computer, typically by another application that uses Crystal.

Sage teams work in isolation.  "One Sage" is only a marketing strategy, not an indication of cohesive teamwork... but you know that already.

Technically, using the latest version of runtimes (to include all the latest bug fixes) is something each team will want to do... understandably.  But Sage has no internal communication (or outward communication) about how that impacts other Sage products... with the root cause of problems being SAP not making updates backwards compatible.  Can you imagine M$ releasing a new version of Word that can't open an old .doc file?

>>Sage could certainly do a better job of communication around the conflicts, but they don't control a big piece of this.

So, wait, what? Sage doesn't control the version of Crystal runtime that they use in their own products and doesn't have a duty to ensure that there aren't conflicts with their own products?

Blame for this one is something I'd lay at the feet of SAP.  Programming the CR runtime updates to not be backwards compatible is simply evil / insanity.  Sage could certainly do a better job of communication around the conflicts, but they don't control a big piece of this.

Some day I envision Sage business units actually speaking with each other. 

Indeed!  (Finding simple fixes to Crystal Reports runtime issues is always difficult).

I'm guessing the MSI's (plus .NET 4.8?) would suffice...

Great post! 👍

A timely post.  This happened to a client running Sage 100 v2022 (Crystal 2016) and HRMS v10.7070 - Q2 2024.  Everything was working great until the Q2 2024 update was installed.  Apparently, there was no warning that this update was using Crystal 2020.  Sage 100 Custom reports stopped working.  When I reinstalled the Sage client, HRMS custom reports stopped working.

I deleted the Crystal runtimes (via the control panel).  I then launched the Sage 100 2023 workstation update.  The very first thing the installer did was install the two Crystal runtimes (below).  Once installed, I exited the installer (did not install the v2023 client).

Sage 100 2022 and HRMS can generate Crystal reports without issue.

Will post back if issues arise.

Fingers crossed.

Thank you. I was hoping with your description that both would be able to play together with the full 13.34 runtime installed. 

Unfortunately, this user is out until next Wednesday to try this. 

Sage indicated the KB was going to be updated with this information.

And after this, you may have to uninstall and reinstall the HRMS client to get printing working in HRMS....

The fix:

(1)  Uninstall the Sage 100 Crystal runtimes (13.30)

(2) Download  and install the 13.34 runtimes from SAP:

https://origin-az.softwaredownloads.sap.com/public/file/0020000000674342023

https://origin-az.softwaredownloads.sap.com/public/file/0020000000674412023

(3)  Uninstall the 13.34 runtimes  this will remove the embedded runtime installs done by HRMS/Sage 300

(4)  Install the 13.34 runtimes

Ahh - the Payroll in HRMS is the Sage 300 payroll...

According to this chart from January, I would have expected the latest HRMS release to be 13.0.30:

Were you able to come up with any resolution? 

I have a customer right now that has this issue. 

Fortunately, most of the users don't have to have both. But the CFO and Controller do and are not happy. Again.

Hmm... I wonder if Sage might have the weight to push SAP for correcting this systemic issue.

(Of course Sage execs would have to be motivated to try).

Agreed.  We and particularly the customers shouldn't have to deal with this crap.  It should just work.  The customer doesn't care nor should they if it is forward, backward, or sideways compatibility or any other reason it doesn't work.  if Sage can't or won;t work with SAP to solve the issue then the least they can do is insure compatibility of Crystal between integrated solutions.  You know, if HRMS is using Crystal 2020 then Sage 100 needs to use version 2020. 

Po-teh-to, Po-tah-to.

Commands from a program to produce output using ABC123.rpt with parameters [1,a,3] and data source {whatever}... should continue to work with higher version of the runtime engine.  I'd expect problems if the report used was higher than the runtime is designed for... but installing a newer runtime shouldn't break programs designed to work with an older runtime. 

(I'm sure I'm not the only one to remember the nightmares of DLL H3LL in the late 90's / early 2K's... SAP should do better... seriously... this stuff is not exactly new problem type).

Isn't forward compatibility the issue, not backward compatibility?  Crystal version 20 can run a report created in version 16.  The issue I run into is forms and reports in Sage 100 don't run because there is a higher version of the run time program installed on the computer, typically by another application that uses Crystal.

Sage teams work in isolation.  "One Sage" is only a marketing strategy, not an indication of cohesive teamwork... but you know that already.

Technically, using the latest version of runtimes (to include all the latest bug fixes) is something each team will want to do... understandably.  But Sage has no internal communication (or outward communication) about how that impacts other Sage products... with the root cause of problems being SAP not making updates backwards compatible.  Can you imagine M$ releasing a new version of Word that can't open an old .doc file?

>>Sage could certainly do a better job of communication around the conflicts, but they don't control a big piece of this.

So, wait, what? Sage doesn't control the version of Crystal runtime that they use in their own products and doesn't have a duty to ensure that there aren't conflicts with their own products?

Blame for this one is something I'd lay at the feet of SAP.  Programming the CR runtime updates to not be backwards compatible is simply evil / insanity.  Sage could certainly do a better job of communication around the conflicts, but they don't control a big piece of this.

Some day I envision Sage business units actually speaking with each other. 

Indeed!  (Finding simple fixes to Crystal Reports runtime issues is always difficult).

I'm guessing the MSI's (plus .NET 4.8?) would suffice...

Great post! 👍

A timely post.  This happened to a client running Sage 100 v2022 (Crystal 2016) and HRMS v10.7070 - Q2 2024.  Everything was working great until the Q2 2024 update was installed.  Apparently, there was no warning that this update was using Crystal 2020.  Sage 100 Custom reports stopped working.  When I reinstalled the Sage client, HRMS custom reports stopped working.

I deleted the Crystal runtimes (via the control panel).  I then launched the Sage 100 2023 workstation update.  The very first thing the installer did was install the two Crystal runtimes (below).  Once installed, I exited the installer (did not install the v2023 client).

Sage 100 2022 and HRMS can generate Crystal reports without issue.

Will post back if issues arise.

Fingers crossed.

Thank you. I was hoping with your description that both would be able to play together with the full 13.34 runtime installed. 

Unfortunately, this user is out until next Wednesday to try this. 

Sage indicated the KB was going to be updated with this information.

And after this, you may have to uninstall and reinstall the HRMS client to get printing working in HRMS....

The fix:

(1)  Uninstall the Sage 100 Crystal runtimes (13.30)

(2) Download  and install the 13.34 runtimes from SAP:

https://origin-az.softwaredownloads.sap.com/public/file/0020000000674342023

https://origin-az.softwaredownloads.sap.com/public/file/0020000000674412023

(3)  Uninstall the 13.34 runtimes  this will remove the embedded runtime installs done by HRMS/Sage 300

(4)  Install the 13.34 runtimes

Ahh - the Payroll in HRMS is the Sage 300 payroll...

According to this chart from January, I would have expected the latest HRMS release to be 13.0.30:

Were you able to come up with any resolution? 

I have a customer right now that has this issue. 

Fortunately, most of the users don't have to have both. But the CFO and Controller do and are not happy. Again.

Agreed.  We and particularly the customers shouldn't have to deal with this crap.  It should just work.  The customer doesn't care nor should they if it is forward, backward, or sideways compatibility or any other reason it doesn't work.  if Sage can't or won;t work with SAP to solve the issue then the least they can do is insure compatibility of Crystal between integrated solutions.  You know, if HRMS is using Crystal 2020 then Sage 100 needs to use version 2020. 

Po-teh-to, Po-tah-to.

Commands from a program to produce output using ABC123.rpt with parameters [1,a,3] and data source {whatever}... should continue to work with higher version of the runtime engine.  I'd expect problems if the report used was higher than the runtime is designed for... but installing a newer runtime shouldn't break programs designed to work with an older runtime. 

(I'm sure I'm not the only one to remember the nightmares of DLL H3LL in the late 90's / early 2K's... SAP should do better... seriously... this stuff is not exactly new problem type).

Isn't forward compatibility the issue, not backward compatibility?  Crystal version 20 can run a report created in version 16.  The issue I run into is forms and reports in Sage 100 don't run because there is a higher version of the run time program installed on the computer, typically by another application that uses Crystal.

Sage teams work in isolation.  "One Sage" is only a marketing strategy, not an indication of cohesive teamwork... but you know that already.

Technically, using the latest version of runtimes (to include all the latest bug fixes) is something each team will want to do... understandably.  But Sage has no internal communication (or outward communication) about how that impacts other Sage products... with the root cause of problems being SAP not making updates backwards compatible.  Can you imagine M$ releasing a new version of Word that can't open an old .doc file?

>>Sage could certainly do a better job of communication around the conflicts, but they don't control a big piece of this.

So, wait, what? Sage doesn't control the version of Crystal runtime that they use in their own products and doesn't have a duty to ensure that there aren't conflicts with their own products?

Blame for this one is something I'd lay at the feet of SAP.  Programming the CR runtime updates to not be backwards compatible is simply evil / insanity.  Sage could certainly do a better job of communication around the conflicts, but they don't control a big piece of this.

Some day I envision Sage business units actually speaking with each other. 

Indeed!  (Finding simple fixes to Crystal Reports runtime issues is always difficult).

I'm guessing the MSI's (plus .NET 4.8?) would suffice...

Great post! 👍

A timely post.  This happened to a client running Sage 100 v2022 (Crystal 2016) and HRMS v10.7070 - Q2 2024.  Everything was working great until the Q2 2024 update was installed.  Apparently, there was no warning that this update was using Crystal 2020.  Sage 100 Custom reports stopped working.  When I reinstalled the Sage client, HRMS custom reports stopped working.

I deleted the Crystal runtimes (via the control panel).  I then launched the Sage 100 2023 workstation update.  The very first thing the installer did was install the two Crystal runtimes (below).  Once installed, I exited the installer (did not install the v2023 client).

Sage 100 2022 and HRMS can generate Crystal reports without issue.

Will post back if issues arise.

Fingers crossed.

Thank you. I was hoping with your description that both would be able to play together with the full 13.34 runtime installed. 

Unfortunately, this user is out until next Wednesday to try this. 

Sage indicated the KB was going to be updated with this information.

And after this, you may have to uninstall and reinstall the HRMS client to get printing working in HRMS....

The fix:

(1)  Uninstall the Sage 100 Crystal runtimes (13.30)

(2) Download  and install the 13.34 runtimes from SAP:

https://origin-az.softwaredownloads.sap.com/public/file/0020000000674342023

https://origin-az.softwaredownloads.sap.com/public/file/0020000000674412023

(3)  Uninstall the 13.34 runtimes  this will remove the embedded runtime installs done by HRMS/Sage 300

(4)  Install the 13.34 runtimes

Ahh - the Payroll in HRMS is the Sage 300 payroll...

According to this chart from January, I would have expected the latest HRMS release to be 13.0.30:

Were you able to come up with any resolution? 

I have a customer right now that has this issue. 

Fortunately, most of the users don't have to have both. But the CFO and Controller do and are not happy. Again.

Some day I envision Sage business units actually speaking with each other. 

Indeed!  (Finding simple fixes to Crystal Reports runtime issues is always difficult).

I'm guessing the MSI's (plus .NET 4.8?) would suffice...

Great post! 👍

A timely post.  This happened to a client running Sage 100 v2022 (Crystal 2016) and HRMS v10.7070 - Q2 2024.  Everything was working great until the Q2 2024 update was installed.  Apparently, there was no warning that this update was using Crystal 2020.  Sage 100 Custom reports stopped working.  When I reinstalled the Sage client, HRMS custom reports stopped working.

I deleted the Crystal runtimes (via the control panel).  I then launched the Sage 100 2023 workstation update.  The very first thing the installer did was install the two Crystal runtimes (below).  Once installed, I exited the installer (did not install the v2023 client).

Sage 100 2022 and HRMS can generate Crystal reports without issue.

Will post back if issues arise.

Fingers crossed.

Thank you. I was hoping with your description that both would be able to play together with the full 13.34 runtime installed. 

Unfortunately, this user is out until next Wednesday to try this. 

Sage indicated the KB was going to be updated with this information.

And after this, you may have to uninstall and reinstall the HRMS client to get printing working in HRMS....

The fix:

(1)  Uninstall the Sage 100 Crystal runtimes (13.30)

(2) Download  and install the 13.34 runtimes from SAP:

https://origin-az.softwaredownloads.sap.com/public/file/0020000000674342023

https://origin-az.softwaredownloads.sap.com/public/file/0020000000674412023

(3)  Uninstall the 13.34 runtimes  this will remove the embedded runtime installs done by HRMS/Sage 300

(4)  Install the 13.34 runtimes

Ahh - the Payroll in HRMS is the Sage 300 payroll...

According to this chart from January, I would have expected the latest HRMS release to be 13.0.30:

Were you able to come up with any resolution? 

I have a customer right now that has this issue. 

Fortunately, most of the users don't have to have both. But the CFO and Controller do and are not happy. Again.

Some day I envision Sage business units actually speaking with each other. 

Indeed!  (Finding simple fixes to Crystal Reports runtime issues is always difficult).

I'm guessing the MSI's (plus .NET 4.8?) would suffice...

Great post! 👍

A timely post.  This happened to a client running Sage 100 v2022 (Crystal 2016) and HRMS v10.7070 - Q2 2024.  Everything was working great until the Q2 2024 update was installed.  Apparently, there was no warning that this update was using Crystal 2020.  Sage 100 Custom reports stopped working.  When I reinstalled the Sage client, HRMS custom reports stopped working.

I deleted the Crystal runtimes (via the control panel).  I then launched the Sage 100 2023 workstation update.  The very first thing the installer did was install the two Crystal runtimes (below).  Once installed, I exited the installer (did not install the v2023 client).

Sage 100 2022 and HRMS can generate Crystal reports without issue.

Will post back if issues arise.

Fingers crossed.

Thank you. I was hoping with your description that both would be able to play together with the full 13.34 runtime installed. 

Unfortunately, this user is out until next Wednesday to try this. 

Sage indicated the KB was going to be updated with this information.

And after this, you may have to uninstall and reinstall the HRMS client to get printing working in HRMS....

The fix:

(1)  Uninstall the Sage 100 Crystal runtimes (13.30)

(2) Download  and install the 13.34 runtimes from SAP:

https://origin-az.softwaredownloads.sap.com/public/file/0020000000674342023

https://origin-az.softwaredownloads.sap.com/public/file/0020000000674412023

(3)  Uninstall the 13.34 runtimes  this will remove the embedded runtime installs done by HRMS/Sage 300

(4)  Install the 13.34 runtimes

Ahh - the Payroll in HRMS is the Sage 300 payroll...

According to this chart from January, I would have expected the latest HRMS release to be 13.0.30:

Were you able to come up with any resolution? 

I have a customer right now that has this issue. 

Fortunately, most of the users don't have to have both. But the CFO and Controller do and are not happy. Again.

>>Some day I envision Sage business units actually speaking with each other. 

How many years have we heard the "One Sage" mantra? That's something that I think new execs tent to chant until they realize how big their challenge is.

Some day I envision Sage business units actually speaking with each other. 

Indeed!  (Finding simple fixes to Crystal Reports runtime issues is always difficult).

I'm guessing the MSI's (plus .NET 4.8?) would suffice...

Great post! 👍

A timely post.  This happened to a client running Sage 100 v2022 (Crystal 2016) and HRMS v10.7070 - Q2 2024.  Everything was working great until the Q2 2024 update was installed.  Apparently, there was no warning that this update was using Crystal 2020.  Sage 100 Custom reports stopped working.  When I reinstalled the Sage client, HRMS custom reports stopped working.

I deleted the Crystal runtimes (via the control panel).  I then launched the Sage 100 2023 workstation update.  The very first thing the installer did was install the two Crystal runtimes (below).  Once installed, I exited the installer (did not install the v2023 client).

Sage 100 2022 and HRMS can generate Crystal reports without issue.

Will post back if issues arise.

Fingers crossed.

Thank you. I was hoping with your description that both would be able to play together with the full 13.34 runtime installed. 

Unfortunately, this user is out until next Wednesday to try this. 

Sage indicated the KB was going to be updated with this information.

And after this, you may have to uninstall and reinstall the HRMS client to get printing working in HRMS....

The fix:

(1)  Uninstall the Sage 100 Crystal runtimes (13.30)

(2) Download  and install the 13.34 runtimes from SAP:

https://origin-az.softwaredownloads.sap.com/public/file/0020000000674342023

https://origin-az.softwaredownloads.sap.com/public/file/0020000000674412023

(3)  Uninstall the 13.34 runtimes  this will remove the embedded runtime installs done by HRMS/Sage 300

(4)  Install the 13.34 runtimes

Ahh - the Payroll in HRMS is the Sage 300 payroll...

According to this chart from January, I would have expected the latest HRMS release to be 13.0.30:

Were you able to come up with any resolution? 

I have a customer right now that has this issue. 

Fortunately, most of the users don't have to have both. But the CFO and Controller do and are not happy. Again.