x Want to participate? Join the group to interact
  • State Not Answered
  • Replies 1 reply
  • Subscribers 74 subscribers
  • Views 225 views
  • Users 0 members are here
Browse Forums
Announcements
106
topics
32
replies
General Discussion
6k
topics
18k
replies
ConnorM

Single user's Email address crashing Exchange Integration

Posted By

We have had a strange instance where a user has been enabled for Exchange Integration, but as soon as they are, Exchange Integration crashed. Errors in the logs give things like, potential memory leak and unable to establish connection to Exchange Integration server.

For info - the user has a double barrelled last name and their email contains a hyphen "-".
Found that no other users that are currently enabled have double barrelled last names in their email.

However, as soon as that user is disable on Exchange Integration again, all starts working again with no issues.

Tried to replicate the issue by enabling a user that does have an email in the same format (e.g. [email protected])
but Exchange seemed to work fine and reported no issues.

Has anyone else had anything like this where a single user was causing Exchange Integration to crash, but once disabled, all starts working fine again?

  • 0

    Hi,

    There shouldn't be any issues with email addresses as you describe them. The log message regarding a potential memory leak isn't really relevant here (it's logged when you restart the Tomcat service, and is due to the way that the webapp is being shut down. Since the entire service is being shut down, a memory leak can't occur).

    You might get further checking out the issues connecting to Exchange. With that being said, I wouldn't expect that a single bad email address would cause the entire synch to fail - I'd suggest checking out your logs (in particular your CXF logs), or logging a case with your local Sage support team.

    If you're feeling adventurous, you could try connecting to that user's mailbox as the CRM impersonated user using EWSEditor, and see if there's any corruption issues when attempting to access any resources on the mailbox. I'd reckon that his is overkill at this stage though - if you get a case logged, and supply the Exchange logs we should be able to take it from there.

    Thanks,

    Rob

*Community Hub is the new name for Sage City