共用方式為

Error when trying to configure the CRM 2015 Outlook client

  • 發行項

Error: CrmSqlCeConnection::ExecuteInNewConnection() Unexpected Exception: System.ServiceModel.FaultException`1[Microsoft.Xrm.Sdk.OrganizationServiceFault]: Therre must be one and only one Organization record (Fault Detail is equal to Microsoft.Xrm.Sdk.OrganizationServiceFault).

Cause: This can be caused because of a duplicate Organization entry in the OrganizationBase table in the OrgDB
If you have imported an organization from within the same deployment this could happen.

Resolution:
Run the query to find out if there are more than 1 record on the OrgnizationBase table.
/* Replace Orgname with your Organization name */
Use Orgname_MSCRM
Select * from OrganizationBase

Ideally there should be only 1 row. We need to delete the incorrect one. Query the ConfigDB to find the right Organization ID for your CRM org.
SELECT [DatabaseName],[FriendlyName] ,[Id] FROM [MSCRM_CONFIG].[dbo].[Organization]

Delete the unwanted record from the OrgnizationBase table in the CRM Organization database
/* Replace Orgname with your Organization name */
Use Orgname_MSCRM
Delete from Organizationbase where OrganizationId != 'Paste the correct OrganizationId here'

Disclaimer: Take a backup of your CRM databases before making any changes.

Comments

  • Anonymous
    August 28, 2015
    This helped me today. Thanks!

  • Anonymous
    September 07, 2015
    Thanks! This also helped me.

  • Anonymous
    February 12, 2016
    Huge thanks for this post - well done mate. Really solved an issue and got everything back on track. Cheers

  • Anonymous
    February 23, 2016
    I believe that this is caused by a serious bug in the Dynamics CRM import organization functionality.  I stumbled upon the problem of multiple entries in the OrganizationBase table from another direction. I created Org1, backed it up in SQL server, restored and imported it to Org2.  Then repeated with Org2 by backing it up, restoring and importing to Org3.  At this point I cannot log in to Org3 with any account.  If I do the procedure described in this post to remove the extraneous record in OrganizationBase in Org2, then I can backup and import to Org3 and it will work. Microsoft needs to address this.