Finance | Project Operations, Human Resources, ...

I cannot import a model with ModelUtil

(0) Share

Report

Posted on by Community Member

Morning,

I have an export of a model that I prepared yesterday. The epxort was made by the command line

ModelUtil.exe -export -metadatastorepath=[path of the metadata store] -modelname=[name of the model to export] -outputpath=[path of the folder where the model file should be saved]

When I wanted to import that model later on, this is what I get : 

C:\AOSService\PackagesLocalDirectory\bin>ModelUtil.exe -import -metadatastorepath=C:\AOSService\PackagesLocalDirectory -file="C:\Users\Userdev5\Desktop\ExportModels07-10-2020\Processus ABS.axmodel"
Object reference not set to an instance of an object.

And in my Packages folder: I noticed that he had created a new Folder with the name of my Model and under that, he had put the XML files.

Any help would make me greatful.

I have the same question (0)

All responses (13)

Answers (0)

Gunjan Bhattachayya 35,423 on at

Like (0)

Report

Hi Naycene,

Was this model already on this Dev server before? Since you mentioned that you got an error while importing the model earlier.

Was this reply helpful? Yes No
Suggested answer

nmaenpaa 101,160 Moderator on at

Like (1)

Report

You can only import a model if it doesn't already exist in the system.

Did it already exist before you imported it?

Anyway, you can delete the folder from PackagesLocalDirectory and try to import again.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thank you for your response.

yes of course, I have already deleted the import with the delete command. I tried also by deleting the folder from the PackagesLocalDirectory .

Always the same error when importing.

Was this reply helpful? Yes No
nmaenpaa 101,160 Moderator on at

Like (0)

Report

- What is the D365 version of the system where the model was exported from?

- What is the D365 version of the system where you are importing the model?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

It was exported/imported from the same system (same VM) with the version 10.0.9.

Was this reply helpful? Yes No
Suggested answer

nmaenpaa 101,160 Moderator on at

Like (0)

Report

I have never experienced this issue. Since it's a local VHD, have you ever installed Microsoft D365 updates on it? If yes, did you remember to update all D365 components? If you just install the update with default settings, it will not update all components.

Anyway, whenever you have strange issues in your dev VM, my suggestion is to deploy a new VM. This way you will get a clean start and don't need to waste your time fighting with problems.

Have you tried to import this model to another VM? This way you can verify the model file, and not be distracted by possible problems in your VM.

Was this reply helpful? Yes No
Gunjan Bhattachayya 35,423 on at

Like (0)

Report

Hi Naycene,

Please try the following and see if you still get the same error.

1. Delete the model from the VM. Ensure that the model folder is deleted from Packages local directory.

2. Rename the axmodel file to - "Processus_ABS.axmodel"

3. Try running the import again using this command - C:\AOSService\PackagesLocalDirectory\bin>ModelUtil.exe -import -metadatastorepath=C:\AOSService\PackagesLocalDirectory -file=C:\Users\Userdev5\Desktop\ExportModels07-10-2020\Processus_ABS.axmodel.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Naycene

1. Stop the IIS AOSService first and then delete the existing model.

2. After deleting the model, delete the respective package folder present in packages Folder directory.

3.once it is done, Start the IIS AOSService. Go to visual studio and under D365 menu --> Model Management --> RefreshModels

4. Now synchronize the Database. Once it is done.

5. Now Stop the IIS AOSService and try importing the model again.

Let me know if it works for you.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Still the same error :(

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Is it necessary to build the model + synchronize the database before making an export?

Im thinking it's probably what is causing the problem

Was this reply helpful? Yes No