Finance | Project Operations, Human Resources, ...

assembly reference not found.

(0) Share

Report

Posted on by Neetha

157

Hi every one,

I am trying to create an entity for a IntegrationActivityCode table but when I am trying to sync I am unable to sync and getting these warnings.

C:\AOSService\PackagesLocalDirectory\ApplicationCommon\ApplicationCommon\AxReference\Microsoft.Commerce.Flighting.Common.xml(0,0): AssemblyFileNotFound: Assembly 'Microsoft.Xbox.Experimentation.Contracts, Version=1.0.0.0, Culture=neutral, PublicKeyToken=d91bba2b903dc20f' failed to load because it was not found.

C:\AOSService\PackagesLocalDirectory\ApplicationPlatform\ApplicationPlatform\AxReference\Microsoft.OData.Edm.xml(0,0): AssemblyFileNotFound: Assembly 'System.Xml, Version=2.0.5.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e' failed to load because it was not found.

All responses (10)

Answers (0)

Suggested answer

nmaenpaa 101,158 Moderator on at

Like (0)

Report

RE: assembly reference not found.

It comes from MS code, you can't resolve it.
Community Member on at

Like (0)

Report
RE: assembly reference not found.

Yes, I was talking about the warnings in the original question. Here is my X++ project building output::

Build step: X++ compilation, label generation and resource deployment started.

K:\AosService\PackagesLocalDirectory\ApplicationCommon\ApplicationCommon\AxReference\Microsoft.Commerce.Flighting.Common.xml(0,0): AssemblyFileNotFound: Assembly 'Microsoft.Xbox.Experimentation.Contracts, Version=1.0.0.0, Culture=neutral, PublicKeyToken=d91bba2b903dc20f' failed to load because it was not found.

K:\AosService\PackagesLocalDirectory\ApplicationPlatform\ApplicationPlatform\AxReference\Microsoft.OData.Edm.xml(0,0): AssemblyFileNotFound: Assembly 'System.Xml, Version=2.0.5.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e' failed to load because it was not found.

Build step: X++ compilation, label generation and resource deployment completed (4232 ms).

Build step: Database synchronization started.

Build step: Database synchronization completed (16701 ms).

Build completed (21251 ms).

I am trying to understand and resolve all warnings in order to make my building output more readable.
Suggested answer

nmaenpaa 101,158 Moderator on at

Like (0)

Report

RE: assembly reference not found.

Are you talking about the warnings that are mentioned in the original question? But you talk about errors? Are you sure your issue is the same than the original question? Could you please share all details about your scenario. What you did, what do you see etc.

If you talk about the warnings that come from the standard application, you don't need to worry about them and you can't do anything about them. Your responsibility is to make sure your own code is error free.

Any issues in the standard solution you can report to Microsoft support.
Community Member on at

Like (0)

Report

RE: assembly reference not found.

Hello,

I am getting the same errors initially reported, and regardless of their low/medium severity I would like to know what is the cause and how to resolve them.

Any idea about that?

Thanks in advance,

~Yiannis
Suggested answer

nmaenpaa 101,158 Moderator on at

Like (0)

Report

RE: assembly reference not found.

What is the sizing of your VM? Perhaps it has too few resources to use as D365 dev system.

Similar problem is discussed here: https://community.dynamics.com/ax/f/microsoft-dynamics-ax-forum/261310/db-sync-timeout
Neetha 157 on at

Like (0)

Report

RE: assembly reference not found.

These were the errors which I have been facing
nmaenpaa 101,158 Moderator on at

Like (0)

Report

RE: assembly reference not found.

Could you please share the error message? Otherwise we can't do much.
Neetha 157 on at

Like (0)

Report

RE: assembly reference not found.

I was unable to sync
Neetha 157 on at

Like (0)

Report

RE: assembly reference not found.

I am just getting the time out error
nmaenpaa 101,158 Moderator on at

Like (0)

Report

RE: assembly reference not found.

Warnings should not block you from syncing. These errors are not harmful, and since they come from the standard solution, you can ignore them.

Do you get some error in the sync?