Notifications
Announcements
No record found.
Hi,
I received the following error after I run compile with validation on all tables.
Any idea?
*This post is locked for comments
display all tables which were not compiled. one of them references that assembly, which causes that error. did you update the .net framework? is one of the not compiled tables customized? maybe you have to refrence a newer version of that assembly.
I received the same error on another machine with fresh installation without customisation.
were all tables compiled or were one or more not compiled? if yes, which table(s) are not compiled? which .net framework is installed ?
It's .Net 4.5 and 4.6 installed. I run compile on all tables, not on selected tables only.
filter the tables in the nav development environment, which were not compiled, if there are any. if there are ones, check which one uses that assembly from the error, edit the table, check where the assembly is used.
afaik assembly Microsoft.IdentityModel.Clients.ActiveDirectory is not referenced in standard nav. it belongs to azure packages, follow www.nuget.org/.../Microsoft.IdentityModel.Clients.ActiveDirectory. so it seems to be a customization. is that an on premise database or is it on azure ?
I have 2 machines. One is Azure VM running Windows Server and NAV 2017 Cum Update 1 is completely installed with only table caption modified to change VAT to GST.
Another machine experiencing the same issue is my laptop running on Windows 10 and NAV Cum Update 1 is completely installed without any modification as i plan to use the laptop as reference during the customisation.
Both machines are experiencing the same issue with the same error message during compilation on all tables.
I'm seeing this too randomly on 2 non-Azure servers running NAV 2017 CU1.
One on Windows Server 2013R2 and one on Windows Server 2016.
I have no solution but did'nt see it on NAV 2017 RTM.
I did upgrade the servers to CU1 by overwriting files from a package created by this method: blogs.msdn.microsoft.com/.../ (patched for NAV 2017 off cause - but I don't know if that is the cause. It might be because I missed patching something)
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
HoangNam 7
