Skip to main content

Notifications

Microsoft Dynamics CRM (Archived)

Dynamics 365 On prem Import error - caught error in trace log. How to fix?

Posted on by Microsoft Employee

I have one sandbox(dev) and one prod environment. I'm trying to move solution from dev to prod but I get an error after the latest CRM update.

I get an error saying I can't change tracking for the opportunity entity since mobile offline is already enabled. It's not possible to change tracking on opportunity in CRM customizations (it's grayed out).

This is the error from the trace log:

>Crm Exception: Message: You can not disable change tracking for opportunity entity since mobile offline is already enabled, ErrorCode: -2147087967
[2017-04-10 12:19:26.196] Process: w3wp |Organization:17293462-d679-465e-9211-11428f4d562a |Thread:   50 |Category: Application |User: 00000000-0000-0000-0000-000000000000 |Level: Error |ReqId: 003d726d-beb8-4fad-95e9-f99de3643876 |ActivityId: 003d726d-beb8-4fad-95e9-f99de3643876 | ErrorInformation.LogError  ilOffset = 0x25
>MSCRM Error Report:
--------------------------------------------------------------------------------------------------------
Error: You can not disable change tracking for opportunity entity since mobile offline is already enabled

Error Number: 0x800609A1

Error Message: You can not disable change tracking for opportunity entity since mobile offline is already enabled

Error Details: You can not disable change tracking for opportunity entity since mobile offline is already enabled

Source File: Not available

Line Number: Not available

Request URL:

Stack Trace Info: [CrmException: You can not disable change tracking for opportunity entity since mobile offline is already enabled]
   at Microsoft.Crm.Application.Platform.ServiceCommands.PlatformCommand.XrmExecuteInternal()

*This post is locked for comments

  • Verified answer
    Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Dynamics 365 On prem Import error - caught error in trace log. How to fix?

    I fixed this by programmatically changing metadata of entities:

               RetrieveEntityRequest accountEntity = new RetrieveEntityRequest

               {

                   EntityFilters = EntityFilters.Entity,

                   LogicalName = "account"

               };

               RetrieveEntityResponse accountEntityResp = (RetrieveEntityResponse)_orgService.Execute(accountEntity);

               EntityMetadata AccountEntity = accountEntityResp.EntityMetadata;

               AccountEntity.CanChangeTrackingBeEnabled = new BooleanManagedProperty(true);

               AccountEntity.ChangeTrackingEnabled = true;

               UpdateEntityRequest updateAccount = new UpdateEntityRequest

               {

                   Entity = AccountEntity

               };

               _orgService.Execute(updateAccount);

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Community AMA December 12th

Join us as we continue to demystify the Dynamics 365 Contact Center

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,240 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,149 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans