From Crystal Manager for Sage CRM
Jump to: navigation, search
  • Sage CRM 7.2, 7.3, 2017R1/R2/R3 ,2018R1/R2 and 2019
  • Reports should be set up using ODBC
  • Crystal Run-time - CRRuntime_32bit_13_0_23.msi (shipped with the product) *(Pre 2019)you need to install the version 20 runtime (DO NOT INSTALL VERSION 21 OR LATER) (2019 release) Download from here

Pre Download from here
  • Crystal Reports - To create the reports (not required on the server)
  • .Net 4.6.x versions of the framework installed on server (CRM app pool must have 4.0 run-time)
  • Compatible with all variants of Sage CRM (inc Sage 200/300 etc)


Run the following to ensure that .Net 4.0 is installed (* Newer versions of windows will need to use Server Manager to install this)

   %windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -i

  • Note: If you are running pre 7.2 - Sage's native Crystal Reports Integration (pre 7.2 as support ended then) and Crystal Manager cannot run on the one server at the same time!
  • Note: IE 11 and some other new browsers only allow print to pdf (if they are locked down - this is environmental and does not happen in most instances).

Note: The Crystal Report Engine that is shipped with our software allows 3 reports to be executed at any one time. Reports are queued then. This is sufficient for most businesses and no locking up occurs.

SAP runtime service pack location (latest updates)

New Link (June 2017)

4 April 2019

There doesn’t seem to be a way to get around print to pdf. We think the reason is that the full report is not in fact downloaded on the screen (you can navigate next page etc) and if you just print what you see then you miss any other pages. This is not an explanation from SAP but our guess as to why this happens.