Deployment of new package is failed

(0) Share

Report

Posted on by maram fraij

While deploying a new package on both development and test environments , the deployment is failed at step 11 (GlobalUpdate script for service model ,,,,,) I try to download the log file , all error files are empty except one with a error mentioned below , how can I solve such error to complete the deployment ?

The specified module 'C:\Program Files\Microsoft Security Client\MpProvider' was not loaded because no valid module file was found in any module directory.

Categories:

Development / Customization / SDK

I have the same question (0)

All responses (5)

Answers (0)

André Arnaud de Cal... 301,035 Super User 2025 Season 2 on at

Like (0)

Report

Hi Maram,

Can you tell how this package was created? It seems like it is a kind of empty package. This could be caused by wrong mappings in the original DEV instance.

Was this reply helpful? Yes No
Martin Dráb 237,882 Most Valuable Professional on at

Like (0)

Report

Note that MpProvider is a PowerShell module; it's not related to D365FO modules.

Was this reply helpful? Yes No
Suggested answer

Sheikh Sohail 6,125 on at

Like (0)

Report

Its seems you deploy-able package is empty. Can you please share the step you followed to create package. would be great if you can share the image of the package like below screenshot, it will help us to get more understanding.

If your model is not empty then restart the VM and try again to deploy package..

Was this reply helpful? Yes No
Rich 326 on at

Like (0)

Report

Aware this thread is pretty old (and a second thread not much younger suggested closing Visual Studio: not something that was relevant in my experience, since VS wasn't open), but I'm seeing the same error at step 0 of a deployment.

If MpProvider is a PowerShell module, does anyone have any thoughts on why package deployment may reference it when it's not guaranteed to be available please?

The package that's failing isn't empty (exact names redacted, but the expected model .nupkg files are present):

Was this reply helpful? Yes No
Rich 326 on at

Like (0)

Report

Looking at the detailed execution logs, this appeared to be due to an issue with an ISV solution (error The model id was not found for the artifact 'ISVApplicationObject' of type 'Microsoft.Dynamics.AX.Metadata.MetaModel.AxResource'. This can happen if the model id was changed. Perform a full build on its containing package to resolve the issue.) Given we’re not building the ISV solution, this reads odd to me, but we’ve ended up resolving it by using the module removal text file & deploying afresh.

Was this reply helpful? Yes No