Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2022 Release Wave 1 PlanDynamics 365 release plan for the 2022 release wave 1 describes all new features releasing from April 2022 through September 2022.
2022 release wave 1 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
I've taken on a project of updating a D365 on-prem setup from 22.214.171.124 to v9.1 on-premise.
Am receiving an error when importing the organization to a 9.0.3 instance. It looks like it is a solution that has some pieces still somewhere in the database?
I searched the SolutionBase table and didn't find anything in it with the GUID. Are there other steps to troubleshoot this and get past the error?
Hope you are well.
We would suggest initially to avoid trying to upgrade orgs to the RTM v9.0 build as this one contains some defects.
Could you please update the server to something around v9.0.28 and retry? Please don't install v9.0.30+ as this one also introduces a defect when upgrading to v9.1.
Let us know how it goes and ideally sharing some details from the crmdmsnapin.log file located on %appdata%\Microsoft\MSCRM\logs
Upgrade cases can be complex, so depending on how much time you have on that task, maybe you can consider opening a support case with us.
Thank you so much for the info on using a newer version of 9.0. I installed 9.0.28, imported the organization again and received the same error. This is the information from the crmdmsnapin.log file:
11:49:28| Info| CrmAction execution time; InstallPlatformSolutionsAction; 00:03:20.5059724
11:49:28| Info| Executing Install action: Microsoft.Crm.Tools.Admin.CreateCustomControlDefaultConfigAction
11:49:28| Error| System.Exception: Error.ActionFailed Microsoft.Crm.Tools.Admin.CreateCustomControlDefaultConfigAction ---> Microsoft.Crm.BusinessEntities.CrmObjectNotFoundException: solution With Id = 3a2c99f9-fb81-48a3-a3d6-e70ee30760ca Does Not Exist
at Microsoft.Crm.Caching.SolutionDataCacheLoader.LoadCacheData(Guid key, ExecutionContext context)
at Microsoft.Crm.Caching.ObjectModelCacheLoader`2.LoadCacheDataInternal(TKey key, Object existingDataContainer, IOrganizationContext context)
at Microsoft.Crm.Caching.ObjectModelCacheLoader`2.LoadCacheData(TKey key, IOrganizationContext context)
at Microsoft.Crm.Caching.CrmMultiOrgCacheBase`2.CreateEntry(TKey key, IOrganizationContext context)
at Microsoft.PowerApps.CoreFramework.ActivityLoggerExtensions.Execute(ILogger logger, EventId eventId, ActivityType activityType, Action action)
at Microsoft.Xrm.Telemetry.XrmTelemetryExtensions.Execute(ILogger logger, XrmTelemetryActivityType activityType, Action action)
at Microsoft.Crm.Caching.CrmMultiOrgCacheBase`2.LookupEntry(TKey key, IOrganizationContext context)
at Microsoft.Crm.SE.DllMethodActions.CreateDefaultCustomControlDefaultConfigForOOB.UpdateSolutionPublisherMap(IDictionary`2 solutionPublisherIds, BusinessComponentState entityState, ExecutionContext context)
at Microsoft.Crm.Tools.Admin.CreateCustomControlDefaultConfigAction.Do(IDictionary parameters)
at Microsoft.Crm.Setup.Shared.CrmAction.ExecuteActionHelper(CrmAction action, IDictionary parameters, Boolean undo)
--- End of inner exception stack trace ---, Error, RetryCancel, Option1
That is weird as your exception is rare.
What v8.2 version are you using?
Are you retrying the attempts after failed ones?
Could it be that your DB on SQL is already on an inconsistent state in a mix between v8 and v9 ? Can you get a fresh v8 backup restored and try again?
Did you change anything on the serverrelease.xml file under \program files\dynamics 365\langpack\1033\ folder?
Are there orgs already inside the deployment that could be sharing the ORGID (Clones) ?
I feel like I will need to open a support case soon. :)
The 8.2 organization is 126.96.36.199.
When it fails, I delete the organization from Deployment Manager, drop the database in SQL Server, restore from my 8.2 backup and try again.
I didn't change anything with serverrelease.xml.
There is only one other organization showing -- a dummy org that was set up when I installed v9 on my testing server.
Am running the import again right now and have the trace enabled. Maybe that will shed some more light on my error?
Good job then.
We enable some traces automatically when we start an upgrade, and they should be inside the Dynamics 365\Trace folder.
You would have to grab those traces, use CRMreader tool and then look for that exception. Once there, remove the filters and start going up to see if there is anything interesting.
Focusing a bit on the error, maybe you have a component/attribute/etc attached to a solution id 3a2c99f9-fb81-48a3-a3d6-e70ee30760ca that doesn't really exist.
This would need some SQL tool like ApexSQL search or a full wide script to search all string on the DB and try to look for any object that is refering that solution ID.
You confirm that solution ID doesn't exist on solutionBase right?
In the SolutionBase table, there is no solution with this ID.
I ran a query on any table that has this GUID in a row and got back a lot of results. It looks like a solution that didn't uninstall properly that was used a long time ago.
Here's the schemas and tables where it is finding this solution ID:
The column names are either SolutionID or SupportingSolutionID.
My first thought is to just delete everything that references the GUID, but I have no idea how that will impact the database.
I appreciate any steps or thoughts on next steps.
Thank you for all of the troubleshooting assistance!
This is one of the worst scenarios.
We would never suggest doing something directly on the Database without having it officially provided by Microsoft.
I can only suggest to open a support ticket so my colleagues can provide the best mitigation possible.
Business Applications communities