Sage 300 Component Breaking Sage CRM Company Screen / Entity (Install Shield)

1 minute read time.

We had a recent case open from a Tech Partner who uses clean vanilla instances to do testing for their third party software.

Within Sage CRM we were getting the following error after installing the Sage 300 component and doing integration.

Nobody could replicate it. 

We went through a massive process of elimination to get down to what it could be and finally found the scenario to be the following.

  • The PC have never had any versions CRM or CRM integration installed before
  • It has Sage 300 2024 PU5 up and running
  • You install Sage CRM 2024 R1
  • You can create a CRM company
  • You install Sage CRM integration to Sage 300 2024 PU2
  • You CANNOT open any companies after installing above integration, user is presented with this  error

We even managed to just break Sage CRM by not even running the integration and just purely running the component installer alone and got the same outcome. 

This is probably not affecting many people as the work around was to go through the Upgrade path and it worked everytime. Somehow when installing the component integration from the Sage CRM or 300 Installer menu.

baffled by how to fixed this we reached out to L3 and with their help we managed to fix it. It seemed that the Sage 300 component when used via the menu had an issue with the install shield and it would play up and break CRM.

When we ran the integration component from the file location directly as an adminstrator the install shield worked and the integration worked also without an issue.

Reminder that most likely most people will not see this bahaviour as most people are using instances that have been upgraded rather then clean vanilla installs where this would be happening.