Skip to main content

Microsoft Dynamics NAV Classic client was opened from an untrustworthy component. Contact your system administrator.


Hi all,

A Comman error faced while trying to Run a Report From Role Tailored Client (a report with no layout defined), it try to start the Report Engine from classic Client.

It can happen that after updating RTC, you end up with a version of RTC which is not compatible with the default classic client. In this case you will typically get this error message when trying to run the report.










First of All you need to find the build of classic and Role tailored client. The Build for both should be same.
Following screen shows how to check the build for both client.



If the build is diffrent you need to udate the Build using this link (require Partner/Customer source login).


If the build is same then we need to find out from where does RTC find the classic client for running classic reports?


RTC finds the location of Finsql.exe in this place in registry: (can be opened by typing regedit in RUN)
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\
Check the value for Default and Path, that should be the exact location where the classic and role tailored client is installed.

So if you have any of the issues above, make sure that the classic client in this folder matches the version of RTC.

Regards,
Saurav Dhyani


Comments

Popular posts from this blog

BC 21 and Higher - PowerShell Cmdlet (Replacement of Business Central Administration).

Hi Readers, As discussed in last article about deprecating of Business Central Administration, there are few common actions that we use in administration till Business Central 20. For our on-prem customers, we will still require doing activities. As Microsoft suggest we need to start using PowerShell cmdlet.    Let's see how to do those via PowerShell, or Administration Shell. I will be keep adding commands as you comment to this article.

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.