Skip to main content

RTC Report It is not possible to instantiate the Visual Studio bridge.


Hi all,

As a Navision developers I have Multiple Versions of Navision running in single Machine. As discussed Earlier in the post how to run multiple Version of RTC in single machine. So my machine have following details for RTC Versions -

NAV 2009 R2    - is installed.
NAV 2009 SP1  - is copied at C:\Program Files (x86)\Microsoft Dynamics NAV\60\NAV 6.0 SP1 IN\
NAV 2009         - is copied at C:\Program Files (x86)\Microsoft Dynamics NAV\60\NAV 6.0 IN\

This approach has been working great for execution of Classic and RTC Clients.
However, after installing Dynamics NAV 2009 R2, if i tried to view the Layout for an NAV 2009 SP1 Report i was getting the following error:

--------------------------- 
Microsoft Dynamics NAV Classic 
--------------------------- 
It is not possible to instantiate  the Visual Studio bridge. 
--------------------------- 
OK   
---------------------------

After searching for the error i figured out the issue was due to -
Design change in NAV 2009 R2 which uses the .NetBridge rather than the old Visual Studio bridge component.

Solution OR Work Around

The Visual Studio bridge files are included with the binaries in the NAV 2009 SP1 Classic Client folder
so we can avoid the above error by running REGASM.EXE to register the DLL.
The REGASM.EXE is included in the .Net Framework folder so executing the following command from within the NAV 2009 SP1 Classic Client folder will remove the error.


Steps to Resolve the issue

1) Start Command Prompt (* Run as administrator if windows 7)
2) Change directory to location where NAV 2009 SP1 classic is placed.
   In my case it is C:\Program Files (x86)\Microsoft Dynamics NAV\60\NAV 6.0 SP1 IN\Classic\
   So command is CD C:\Program Files (x86)\Microsoft Dynamics NAV\60\NAV 6.0 SP1 IN\Classic\.

3) Now find the Location of regasm.exe which is located in .NET Framework
   In my machine the path is C:\Windows\Microsoft.NET\Framework64\v2.0.50727\ (for 64 bit)
                                          C:\Windows\Microsoft.NET\Framework\v2.0.50727\ (for 32 bit)

4) Now in command prompt run the command
   C:\Windows\Microsoft.NET\Framework64\v2.0.50727\regasm.exe Microsoft.Dynamics.Nav.VisualStudioBridge.DLL (64 bit)
   C:\Windows\Microsoft.NET\Framework\v2.0.50727\regasm.exe Microsoft.Dynamics.Nav.VisualStudioBridge.DLL (32 bit)

* you can find Microsoft.Dynamics.Nav.VisualStudioBridge.DLL inside classic folder.

5) If everything is correct, you will receive a message "Type Registered Succesfully" as shown in image below.



Problem Resolved !

Thanks & Regards,
Saurav Dhyani
http://saurav-nav.blogspot.in/

Comments

  1. This is brilliant! Thank you for the tip.

    ReplyDelete
  2. Hi Dynamics NAV Entusiast,
    Thanks for the comment.

    ReplyDelete
  3. Hi Saurav,
    Great Job....Excellent Work..

    ReplyDelete
  4. Thanks Saurav But one request please also mention that you have copy that dll in Microsoft.NET Frame work because without it its not working.
    Rishi

    ReplyDelete

Post a Comment

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.