I am thankful for any help or suggestions
Best Regards*This post is locked for comments
Hi,
I've been facing the same issue since NAV 2018 (now in BC14) but only in some environments (which is Citrix based; if that matters).
But anyways: a workaround would be to copy the DLL into Service parent folder of the Add-Ins folder.
HTH,
JC
Hello,
I encountered this error this morning,
It ended up being that the Microsoft.Dynamics.Nav.Server.exe.config file was no longer a CONFIG file rather just a text file on the server.
I replaced the text file with a working CONFIG file and cleared my local NAV cache by going to
%TEMP%\Microsoft Dynamics NAV\Add-Ins and deleting the folder.
re opened NAV and I was able to use all Ad-Hoc reports on the connection.
Hope this helps someone in the future.
Have you tired to registrer the DLL and then access it as an automation variable instead of an DotNet variable?
It could be that the DLL is too old to be used directly as an DotNet variable.
No it does not, it is just a normal DLL with some Functions in it that we need. I also do really not know what to do anymore.
Here is a link to the dll https://1drv.ms/u/s!Ar5DM52h81oYgcQ8vbygQ1x0RDDKww
Very strange then. Is this an addin that requires a particular setup for installing it?
Hello Stefano
Thanks for the answer, yes I know the difference between RunOnclient Yes and No and tired both scenarios and both did give the error.
I also re added the reference multiple times and also restarted the nav service.
If the DLL is in the addin folder of the client, RunOnClient must be YES. If it's placed in the add-in folder of the service tier, RunOnClient must be set to FALSE.
Have you ried to re-add the reference after placing the dll in the addin folder?
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,240 Super User 2024 Season 2
Martin Dráb 230,149 Most Valuable Professional
nmaenpaa 101,156