Getting error while trying to import managed solution into client's tenant

(0) Share

Report

Posted on by Community Member

I am getting such error "The import of the solution XXXX failed. The following components are missing in your system and are not included in the solution. Import the managed solutions that contain these components(SolutionHistoryAPIs (9.1.0.0)) and then try importing this solution again." while trying to import my custom managed solution into client's tenant.

But I easily can install my custom solution into other test tenant those I have.

What is the appropriate solution for this error?

Any help would be appreciated.

*This post is locked for comments

I have the same question (0)

All responses (11)

Answers (0)

Suggested answer

Mahendar Pal 45,095 on at

Like (0)

Report

Hi,

You need to download the file and need to make sure every dependent component which is not present in your target, should be part of the importing solution. The log will help you to understanding what are the components missing, surely there should be something which is missing in this specific environment.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Where I can find the log?

Was this reply helpful? Yes No
Mahendar Pal 45,095 on at

Like (0)

Report

You should get that file while importing solutions, once you got error you should see download button to download log file.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

I can't see any option to download the log file on the error screen. May be download button is not available for all types of error.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Do you know how to install this plugin SolutionHistoryAPIs (9.1.0.0) into my source solution? I couldn't find this plugin as standalone to download from any where. May be it is a depended plugin with Field service or other module.

Was this reply helpful? Yes No
Suggested answer

Kokulan 18,054 on at

Like (0)

Report

If its a missing component error, you wont get an option to download log file as the actual import would not have started at this stage.

Could you check your target instance version please? I think your environment is latest and has the 9.1 Solutionhisotry API (mostly likely the sitemap dependency) where as your client's instance may be lower version.

Was this reply helpful? Yes No
Community Member on at

Like (1)

Report

I have resolved the issue removing Solution History component from the source solution's sitemap.

Was this reply helpful? Yes No
Suggested answer

Sreevalli 3,256 on at

Like (1)

Report

Hi,

If you know that the missing dependencies which are throwing error are not required for your solution and there are really no dependency with the components which you are trying to import then follow the steps below.

extract the solution file then open "solution.xml" you will find "MissingDependencies" tag. then remove everything in between and leave empty tags <MissingDependencies></MissingDependencies>. then save and zip the solution then try to import.

please note if still it throwing error means it has the dependency with the missing components and make sure of keeping backup before doing any changes to your solution file.

Was this reply helpful? Yes No
JDMCRM 1,799 on at

Like (0)

Report

Hi Shahriat, I'm having the same issue. It appears the Solution History entity - now included out of the box (is there any documentation?) - exists in our DEV environment but not our Test or Production environment. In both Test and Production we have no msdyn_solutionhistory & msdyn_solutionhistorydatasource Entities. I don't believe anyone has imported a solution that contains these Entities. It looks as though they are delivered via Microsoft updates (once again, just assuming here). All environments are running v9.0.1.1658. Therefore, I'm not sure how these entities are present in DEV but not our other Environments. What it does mean, is we can't deploy until this the Entities find their way into the target environments.

Was this reply helpful? Yes No
Suggested answer

Kokulan 18,054 on at

Like (0)

Report

I know we should not be editing the Solution XML file as its not always supported, if your missing components list is completely related to this solution history thing not any other, and if you cant wait until you get the solution history entities on Test and Production, you can force the import by removing the contents inside the missing Dependencies tag in the solution.xml file

you will have to unzip the solution file, update the above XML file and zip the solution back and import.

This is a temporary solution until you find how the Dev has these entities but Test / DEV doesn't.

Hope this helps

Was this reply helpful? Yes No