Browse By Tags

Summary: An error may appear in a blue notification bar when navigating to the E-Marketing tab in Sage CRM: Your Sage E-marketing for Sage CRM is disabled. To re-enable your account please contact your system administrator Assuming that your account is enabled, the issue may be caused by an incorrect...

Summary: How does the Sage E-Marketing feature determine that a mail has been opened? Resolution: Each of the email templates that you create or choose are stored on the Swiftpage server. On each of these templates, Swiftpage embeds a tiny 1x1 pixel image that’s stored on their server. Each time...

Summary: We have an issue with one of our clients not getting sync information from Swiftpage at all. We fixed the issue by modifying the file syncengine.properties in the tomcat/webapps/crmSPSyncEngine/web-inf/ folder. The CRM user password there needs to be updated. However, only the new campaigns...

Summary: Swiftpage drip marketing emails not getting sent Symptoms: Error on screen - POST on https://u01.spsend.com/SpeSendBigV7.aspx failed: 302 In swiftpage logs found No enum const class com.sage.scrm.syncengine.emarketing.communication.model.DripCampaignStatus.BUILD and Command returned error: Error...

Summary: When you use a static group with some records excluded as the group to base your E-marketing email on and then click on "Preview Recipients", the excluded records appear on the recepients preview list. Resolution: This issue has been resolved in Sage CRM 7.2F

Summary: A problem occurs with the synchronisation of statistics from Swiftpage to CRM and there is an error appearing in the logs: “There is no Swiftpage account created.” Cause: This is usually as a result of the user in the syncengine.properties file not being an emarketing user on the...

Summary: When installing patch 7.2F of CRM the value of the syncengine.crmpassword in the file tomcat/webapps/crmSPSyncengine/WEB-INF/syncengine.properties may be blanked out. It's important to check this value after installing the patch and to make sure it matches the password value on the Users...

Summary: A HTTP 500 may be returned on running the Swiftpage nightly synch task. This can result in a failure to synchronise the results of nightly batch processing. Symptoms: The following errors may be logged: spnighttask.log: com.sage.scrm.syncengine.emarketing.communication.handler.drip.SyncCampaignResultsHandler...