web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Customer experience | Sales, Customer Insights,...
Suggested Answer

8.2 to 9.1 Migration Error

(0) ShareShare
ReportReport
Posted on by 2
Working in new Dev Environment. Fresh install of 9.1. SQL running same version of 9.1 SRS tools. 
 
When attempting to import an existing 8.2.x organization for upgrade it fails after about an hour and 45 minutes with this in the error log. 
 
[10/6/2023 11:02:25 PM]: MTPD: PackageDeployer reported status [Failed] during import: Failed to load solution Service, version: 9.0.20093.1035. See the log file.
[10/6/2023 11:02:25 PM]: MTPD: Logger LastError: Message: Importing solution threw and unforeseen exception
Source    : Microsoft.Crm.Extensibility
Method    : Execute
Date    : 7:02:25 PM
Time    : 10/6/2023
Error    : Entity incidentresolution : Quick create is not supported for non-refreshed Entity
Stack Trace    : at Microsoft.Xrm.Tooling.PackageDeployment.CrmPackageCore.ImportCode.BaseImportCustomizations.ExecuteImportSolution(ConfigSolutionFile Sol, String sSolutionImportFilePath)
======================================================================================================================
[10/6/2023 11:02:25 PM]: MTPD: Logger LastException: System.ServiceModel.FaultException`1[Microsoft.Xrm.Sdk.OrganizationServiceFault]: Entity incidentresolution : Quick create is not supported for non-refreshed Entity (Fault Detail is equal to Exception details: 
ErrorCode: 0x80040203
Message: Entity incidentresolution : Quick create is not supported for non-refreshed Entity
TimeStamp: 2023-10-06T23:02:25.1926528Z
--
Exception details: 
ErrorCode: 0x80040203
Message: Entity incidentresolution : Quick create is not supported for non-refreshed Entity
TimeStamp: 2023-10-06T23:02:25.1926528Z
--
).
[10/6/2023 11:02:25 PM]: MTPD: PackageDeployerWrapper: OrganizationServiceFault details: Exception details: 
ErrorCode: 0x80040203
Message: Entity incidentresolution : Quick create is not supported for non-refreshed Entity
TimeStamp: 2023-10-06T23:02:25.1926528Z
--
Exception details: 
ErrorCode: 0x80040203
Message: Entity incidentresolution : Quick create is not supported for non-refreshed Entity
TimeStamp: 2023-10-06T23:02:25.1926528Z
--
[10/6/2023 11:02:25 PM]: MTPD: Signaling PackageDeployer operation error: System.ServiceModel.FaultException`1[Microsoft.Xrm.Sdk.OrganizationServiceFault]: Entity incidentresolution : Quick create is not supported for non-refreshed Entity (Fault Detail is equal to Exception details: 
ErrorCode: 0x80040203
Message: Entity incidentresolution : Quick create is not supported for non-refreshed Entity
TimeStamp: 2023-10-06T23:02:25.1926528Z
--
Exception details: 
ErrorCode: 0x80040203
Message: Entity incidentresolution : Quick create is not supported for non-refreshed Entity
TimeStamp: 2023-10-06T23:02:25.1926528Z
--
).
[10/6/2023 11:02:25 PM]: MTPD: PackageDeployer operation completed.
[10/6/2023 11:02:25 PM]: System.ServiceModel.FaultException`1[Microsoft.Xrm.Sdk.OrganizationServiceFault]: Entity incidentresolution : Quick create is not supported for non-refreshed Entity (Fault Detail is equal to Exception details: 
ErrorCode: 0x80040203
Message: Entity incidentresolution : Quick create is not supported for non-refreshed Entity
TimeStamp: 2023-10-06T23:02:25.1926528Z
--
Exception details: 
ErrorCode: 0x80040203
Message: Entity incidentresolution : Quick create is not supported for non-refreshed Entity
TimeStamp: 2023-10-06T23:02:25.1926528Z
--
 
 
I checked the Case Resolution Entity and Quick Actions is greyed out, I couldn't turn it on if I wanted to. 
 
I tried going from 8.2.x to just 9.0, then to 9.6, then to just 9.1 now I am on the latest 9.1.x released.
 
Any help on this one?
I have the same question (0)
  • Suggested answer
    Community member Profile Picture
    2 on at
    Microsoft provided the below SQL script to run on the database. Ran that and the import worked as expected.
     
    /*{
        "Version": "1.0",
        "Type": "Mitigation",
        "Author": "deyilmaz",
        "EntityOwnerAlias": "deyilmaz",
        "AppVersion": "9.1",
        "Expiry": "05/11/2023",
        "DataOutput": "NoCustomerData",
        "ImpactSeverity": "CssSafe",
        "Notes": "Check Below",
        "Description": "This script mitigates orgs that has issue in setting the required base table and other metadata required for customizing the incidentResolution entity",
        "VersionHistory" : [
             {"Version": "1.0", "Author": "deyilmaz", "Change": "Base version"}
        ]
    }*/

    BEGIN TRANSACTION

    IF  NOT EXISTS (SELECT * FROM sys.objects 
    WHERE object_id = OBJECT_ID(N'[dbo].[IncidentResolutionBase]'AND type in (N'U'))
    BEGIN
    /****** Create the metadataschema to add support for the Extension Table required for the incident resolution custom attributes******/
    CREATE TABLE [dbo].[IncidentResolutionBase](
        [ActivityId] [uniqueidentifier] NOT NULL,
     CONSTRAINT [PK_IncidentResolutionBase] PRIMARY KEY CLUSTERED 
    (
        [ActivityId] ASC
    )WITH (PAD_INDEX = OFFSTATISTICS_NORECOMPUTE = OFFIGNORE_DUP_KEY = OFFALLOW_ROW_LOCKS = ONALLOW_PAGE_LOCKS = ONFILLFACTOR = 80ON [PRIMARY]
    ON [PRIMARY]

    ALTER TABLE [dbo].[IncidentResolutionBase] SET (LOCK_ESCALATION = DISABLE)

    ALTER TABLE [dbo].[IncidentResolutionBase]  WITH CHECK ADD  CONSTRAINT [FK_IncidentResolutionBase_ActivityPointerBase] FOREIGN KEY([ActivityId])
    REFERENCES [dbo].[ActivityPointerBase] ([ActivityId])

    ALTER TABLE [dbo].[IncidentResolutionBase] CHECK CONSTRAINT [FK_IncidentResolutionBase_ActivityPointerBase]

    END

    /****** updating the metadataschema to add support for the Extension Table and Required metada data attributes on incident resolution entity******/
    UPDATE mse
            SET IsReadOnlyInMobileClient = 0, IsQuickCreateEnabled = 1, CanCreateAttributes = 1, IsAIRUpdated = 1, ExtensionTableName = 'IncidentResolutionBase'
            FROM [MetadataSchema].[Entity] AS mse INNER JOIN [SolutionBase] as sb on mse.SolutionId = sb.SolutionId
            WHERE mse.LogicalName = 'incidentresolution' AND sb.UniqueName NOT IN ('msdynce_ServicePatch201911''msdynce_ServicePatch''msdynce_Service');

            DECLARE @updatedRows AS INT = @@ROWCOUNT;
            DECLARE @solutionCount AS INT = (SELECT COUNT(UniqueName) FROM [MetadataSchema].[Entity] AS mse INNER JOIN [SolutionBase] as sb on mse.SolutionId = sb.SolutionId
            WHERE mse.LogicalName = 'incidentresolution' AND sb.UniqueName NOT IN ('msdynce_ServicePatch201911''msdynce_ServicePatch''msdynce_Service'));
            
            IF @updatedRows <> @solutionCount
            BEGIN
                THROW 51000'Incorrect rows updated!'1;
            END

    COMMIT TRANSACTION
     

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
ManoVerse Profile Picture

ManoVerse 164 Super User 2026 Season 1

#2
Jimmy Passeti Profile Picture

Jimmy Passeti 51 Most Valuable Professional

#3
NeerajPawar Profile Picture

NeerajPawar 42

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans