Browse By Tags

Summary: Version: 7.2a Area: Exchange Integration Steps to Reproduce: 1. Install a v7.0 copy of CRM. Set up your users' email addresses. 2. Upgrade to v7.2. Set up the Exchange integration. 3. Create a new appointment in CRM. Your user should be the organizer. 4. Synch with Exchange. Expected result...

Summary: A customer had a query regarding the Exchange integration: What is the purpose of using an impersonated user? Would it not be better from a security perspective to have the CRM Exchange integration log in as each individual user when accessing mailboxes, rather than have a single user with the...

Version: 7.2a Language: English Area: Exchange Integration Steps to Reproduce: 1. Set up an Exchange impersonated user for an Exchange integration. Make sure that the Exchange impersonated user's primary SMTP address does not match username@domain , e.g. make it username@someotherdomain.com . 2....

Summary: An error may appear when setting up the Exchange integration - CRM cannot connect to the synch engine. Symptoms: The following error is displayed in the exchangesynch.log: ERROR: 06-Jun-2013 11:56:27.525 url: http://SERVER2/sdata/crmj/crmExchange/-/tasks/$syncSource?trackingId=ef22cb8e-0c27...

Summary: An exception may be raised when synchronising tasks. This error will prevent subsequent tasks from being synched in affected mailboxes. Symptoms: crm.log: ERROR [http-apr-11009-exec-9]: 18-Jun-2013 11:52:26.117 Due to processing errors UUID = 5d7d1e5f-1207-49be-b59b-6aedef127cdd will be removed...

Summary: Corrupt items in an Exchange mailbox may cause errors when running a synch. Symptoms: Exchangesyncengine.log: 2013-06-07/14:15:54.733/EDT [Sync Source APPOINTMENT Queue Thread] ERROR com.sage.scrm.syncengine.exchange.ews.service.SageExchangeService.getItems com.sage.scrm.syncengine.exchange...

Summary: Errors in the CRM metadata my lead to a StringIndexOutOfBoundsException when the CRMJ webapp attempts to load the metadata. Subsequent requests to use the metadata object in Java (e.g., using the Exchange integration, or viewing the SDATA schema URL) will result in a SageObjectNotInitializedException...

Summary: Adding a linked Company or Person record to an appointment always results in an updated meeting request being sent by the Exchange integration, eventhough the Exchange integration is set to not include the CRM info in the body and the Appointment synch direction is set to Bidirectional. The...

Summary: Depending on your Exchange configuration, you may need to set your CRM impersonated user's primary SMTP address to user@domain . This setting is applied on the Exchange server. Symptoms: On attempting to save a new Exchange integration in CRM 7.2, the setup fails on the second test. The...

Summary: If you need to change the default port for CRM on IIS to anything other than port 80 you may encounter an issue when setting up Exchange integration. The following error will appear on screen: "CRM is attemping to establish a connection with the Sync Engine. Please wait... The Exchange...

Summary: When setting up an Exchange Integration in CRM, an error may occur at the second stage of the set up process ("The Sync Engine is checking to see if the Exchange Web Service is available"). At this step, the synch engine is trying to verify that it can connect to the EWS endpoint,...

Summary: Under Administration -> System -> System Behaviour , the Maximum number of occurrences value is used to define the maximum number of repeating appointments that may be set. A query may arise regarding how high that value can actually go. More information: Detailed performance testing has...

Summary: On enabling the Exchange integration, an error relating to SQL parameters may appear in the logs. Symptoms: The logs appear to indicate that the colon character (:) is being interpreted as a placeholder for a SQL parameter. Thus a time (e.g. 12:30pm) can be interpreted as a parameter value of...

Summary: A customer encountered an error when setting up a new Exchange integration with Sage CRM. On saving the integration details, the setup failed at the step: "The Sync Engine is checking to see if the Exchange Web Service is available." The following error was logged in the ewaresystem...

Summary: Emails filed through exchange plugin not putting attached documents into documents library Symptoms: If an email with two recipients and an attachement is filed accross to CRM, the destination the second email is filed to will not insert the document into the document tab. The first email will...

Summary: An issue may arise on a customer's Sage CRM install whereby enabling the Exchange synchronisation for Contact records results in errors. On failing, a HTTP 500 error in logged in the exchangeConfiguration log. ERROR [http-apr-11009-exec-1]: 28-Apr-2014 15:57:27.222 url: http://CRM-SERVER...

Summary: Exchange 365 integration is not synchronising due to timezone issues. Symptoms: A variation of the following errors are appearing in the scrm logs: ERROR [pool-2-thread-1]: 27-may-2014 16:13:53.208 Cannot find windows time zone for CRM timezone: +00:00 ERROR [pool-2-thread-1]: 27-may-2014 16...

Summary: Looking at the latest Software Support Matrix, Office 365 is marked as supported for 7.1 SP2 and above. Can you confirm for me if exchange 365 supported for Exchange integration? Or does Office 365 in the matrix refer to the office products such as word, outlook & excel etc? Solution Yes...

Summary: When using concurrent licensing with Sage CRM, it is common for the total number of enabled users on the system to be greater than the number of concurrent licenses. A question may arise as to whether adding these additional users to the Exchange integration will have any effect on licensing...

Summary: When performing the pre-configuration steps for setting up the Exchange Integration for Exchange 2007 it is necessary to run the cmdlets described in chapter 36 of the System Administrator guide. You may receive the following error when running these cmdlets: InvalidArgument: (:) [Add-ADPermission...

Summary: A user creates an new appointment, for example: a meeting in CRM with external attendees. This meeting gets synced into Outlook via Exchange and invitations are sent to the attendees for this meeting. The user then sets this meeting to "completed" in CRM. Symptoms: The appointment...

Summary: An issue may occur when using the Sage CRM Exchange integration to synchronise appointments or tasks. This error will arise on a single appointment or task, and prevent the synchronisation of subsequent items. Symptoms: A HTTP 500 response code will be logged on sending a HTTP POST to the CRMJ...

Summary: Sage CRM Exchange Integration Support presentation: Download: Exchange Integration Support presentation

Summary: For the purposes of monitoring the CRM Exchange Integration there is a status page that can be displayed in a web browser in html format that will provide information about the statistics of the synchronisation including timings and the number of items synced. To access this url on the CRM server...

Summary: In CRM there is the ability to add resources to appointments. Resources can also be set up in Exchange. When creating an appointment if a resource’s email address matches a resource in Exchange it will sync with CRM the same as any user set to sync. The only difference is that resources...