Requirements: Difference between revisions
From Crystal Manager for Sage CRM
Crmtogether (talk | contribs) No edit summary |
Crmtogether (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
*Sage CRM | *Sage CRM 7.2, 7.3 | ||
*CRM DB: MSSQL | *CRM DB: MSSQL | ||
*Crystal Run-time - CRRuntime_32bit_13_0_12.msi (shipped with the product) | *Crystal Run-time - CRRuntime_32bit_13_0_12.msi (shipped with the product) | ||
Revision as of 08:59, 26 April 2017
- Sage CRM 7.2, 7.3
- CRM DB: MSSQL
- Crystal Run-time - CRRuntime_32bit_13_0_12.msi (shipped with the product)
- Crystal Reports - To create the reports (not required on the server)
- .Net 3.5 and .Net 4.0 framework installed on server (CRM app pool must have 4.0 runtime)
- Compatible with all variants of Sage CRM (inc Sage 200/300 etc)
Run the following to ensure that .Net 4.0 is installed
%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)
