locked
SYSTEM user account not found. - With BU User Read Permissons, Unable to Track Email from Outlook Client RRS feed

  • Question

  • [Dynamics CRM 2013 SP1 OnPrem]

    When attempting to Track an E-mail in the Outlook Client from a new email address (not attached to a contact, user etc) we get the following error:

    <OrganizationServiceFault xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/xrm/2011/Contracts">
      <ErrorCode>-2147220933</ErrorCode>
      <ErrorDetails xmlns:d2p1="http://schemas.datacontract.org/2004/07/System.Collections.Generic" />
      <Message>SYSTEM user account not found.</Message>
      <Timestamp>2014-08-15T09:08:06.2431727Z</Timestamp>
      <InnerFault>
        <ErrorCode>-2147220933</ErrorCode>
        <ErrorDetails xmlns:d3p1="http://schemas.datacontract.org/2004/07/System.Collections.Generic" />
        <Message>SYSTEM user account not found.</Message>
        <Timestamp>2014-08-15T09:08:06.2431727Z</Timestamp>
        <InnerFault i:nil="true" />
        <TraceText i:nil="true" />
      </InnerFault>
      <TraceText i:nil="true" />
    </OrganizationServiceFault>

    The User has a Security Role with BU Read of 'User'. If we up this to Org it works.

    Presumably this is because the SYSTEM user is not in the BU, but this feels like a bit of a bug/poor design.

    Any ideas/workarounds?

    Cheers.


    • Edited by cdstudios Friday, August 15, 2014 10:37 AM
    Friday, August 15, 2014 10:36 AM

All replies

  • Hi,

    Did you ever got this fixed properly? I face the same issue.

    Thursday, September 3, 2015 9:46 AM
  • Same here. Any update?
    Friday, October 30, 2015 11:01 AM
  • Sorry guys, other requirement came in that killed the use of the Outlook Client so I never had to solve this.

    Thursday, November 5, 2015 4:33 PM
  • https://community.dynamics.com/crm/f/117/t/161154
    Thursday, February 11, 2016 8:38 AM
  • Has anyone figured out what the problem was? We are experiencing the same issue.
    Friday, April 15, 2016 1:46 PM
  • Did you figure out what was going on?
    Friday, April 15, 2016 1:47 PM
  • In our case this was solved by giving Organizational read access on the User entity (it was BU access before) Otherwise the user could not read the system user. So same solution as original post.
    • Proposed as answer by Peter Deleu Monday, April 18, 2016 5:30 AM
    • Edited by Peter Deleu Monday, April 18, 2016 5:32 AM
    Monday, April 18, 2016 5:30 AM
  • and why would the security setting working just as expected be called a bug/poor design?
    Monday, April 18, 2016 11:20 PM