Browse By Tags

  • Wiki Page: 492-16974 - Adding custom time zones may prevent the CRMJ webapp from starting

    Summary: Adding custom time zones to the TimezoneDelta caption family on Custom_Captions may result in the CRMJ webapp being unable to start. Symptoms: An error similar to the one shown below will appear in the localhost.log: SEVERE: Exception sending context initialized event to listener instance of...
  • Wiki Page: 605-16496 - Compatibility of Microsoft Office 2013 with Sage CRM

    Summary: When will Sage CRM be compatible with Microsoft Office 2013 (Microsoft Outlook, Microsoft Excel and Microsoft Word)? Workaround / Resolution: Sage CRM 7.2.b onwards is fully compatible wih Microsoft Office 2013.
  • Wiki Page: 492-17218 - How to: Using SQL Server Transparent Data Encryption with Sage CRM

    Summary: SQL Server Transparent Data Encryption (TDE) is a method of encrypting the data stored on a hard disk by SQL Server. A customer may have a requirement to use this with Sage CRM. More information: Transparent Data Encryption has not been tested with Sage CRM, and is therefore technically unsupported...
  • Wiki Page: 492-17356 - Unable to launch ASP pages in Windows 2008

    Summary: A permissions error may be displayed when attempting to view an ASP page created using the COM API. This is likely to be caused by a permissions issue on the anonymous user. Symptoms: The following error message will be displayed when you attempt to view the ASP page: Server.CreateObject Access...
  • Wiki Page: 492-17456 - SDATA schema URL: Windows Presentation Foundation Host has stopped working

    Summary: In Sage CRM v7.2, attempting to access the SDATA schema URL using Internet Explorer may throw an error. This is due to the format of the XML returned, and does not indicate an error in Sage CRM. Symptoms: The SDATA schema URL is commonly used as a troubleshooting step to determine if the Tomcat...
  • Wiki Page: 536-17518 - Difference in generated IDs in v 7.2 and 7.1

    Summary: If a system is upgraded from 7.1 to 7.2, does the sql_identity table still get used? Is there a difference in the method of generating IDs between a system upgraded to CRM 7.2 and a fresh install of CRM 7.2? Solution: Systems upgraded from 7.1 to 7.2 will still use the eware_get_identity_id...
  • Wiki Page: 492-17545 - Tool: URL Compare - translating Sage CRM URL key values

    Summary: Sage CRM uses URL keys to define the system context. By this we mean the main entity type, as well as the individual entity record, and any secondary entity records that are currently being accessed by a user. A full description of how this works within the product is available here . Developers...
  • Wiki Page: 492-17957 - Sage CRM system lock - unable to log back in

    Summary: A customer may lock Sage CRM for customisation using the option available under Administration | System | Lock System . If they encounter difficulties with the password of the user who created the lock, they may be unable to log back into Sage CRM. More information: Running the following SQL...
  • Wiki Page: 492-17962 - Changing User Select display format

    Summary: User Select fields in Sage CRM can be displayes in one of two ways within Sage CRM. Which format is used depends on an entry on the CustomSysparams table named DropdownThreshold. More information: When linking a Sage CRM entity record to a user, a particuklar type of field is used. This field...