Solution import failure. Error code 80040375

(0) Share

Report

Posted on by BenB

Hi,

I have imported a couple of solutions in the past, and not encountered this before. Im looking for a resolution or to be pointed in the right direction. The error tells me that the file is to big, however the ZIP is about 530ish KB

I have a new entity form i created, i want to export it from test, and import it to production. im pretty basic, i just follow the prompts tbh.

At first it tells me various dependencies are missing when i tried to import. i went back and added them to the solution, and got the below so everything seemed ok

after waiting for import i got the below error, but as mentioned i know the file size is NOT too big. Any suggestions?

I have the same question (0)

All responses (3)

Answers (0)

Suggested answer

RodRodriguez on at

Like (1)

Report

Howdy Ben,

When it throws that "file is too large" error, that is almost always (99%) a lie. That is the "default" error basically. Go to your solution history and see what the error was on that import.

From the Solution History window, click on that specific import and it will take you to the "for realsies" error on that solution import.

Was this reply helpful? Yes No
BenB 40 on at

Like (0)

Report

Thank you for the advice! I ended up resolving through trial and error. From how i pushed it through it appears as if a particular dependent entity didn't package into the solution properly? As after trying various things, i narrowed down on a particular entity, removed it and then put it back in, and re packaged and it worked with no errors. Its possible something else resolved it, but as far as i can tell removing and replacing the affected entity did the trick.

I have verified your answer as i wasn't aware i could check the solution history to see more detail and that is 100% pointing me in the right direction. Hopefully i wont spend 6 hours trying things next time :D

Was this reply helpful? Yes No
Shaun W Harvey 242 on at

Like (0)

Report

Great shout on the Import History approach! I always seem to forget about it initially.

The "Download Log File" option is also useful as well.

Even though it downloads as an "XML" file extension.

Load it up using MS Excel and you get a nicely formatted document you can read.

I used it for a solution import error myself only yesterday.

A good thing to remember about Dynamics CRM, is that it tends to store a lot of useful log information within entity records.

Solution Imports is one. Plugin Trace Logs are another. System Jobs are another.

There is a lot of information there for you.

Some of the information, particularly in plugin-trace logs can be a bit hard to read in the Dynamics UI.

But utilities like "Plugin Trace Reader", which is available through XrmToolBox can make viewing this data much easier.

Was this reply helpful? Yes No

Join the conversation

Community site session details

Solution import failure. Error code 80040375

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

Featured topics

Product updates

Community site session details

Solution import failure. Error code 80040375

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > Customer experience | Sales, Customer Insights, CRM

Featured topics

Product updates