Skip to main content

MSDYN365BC - Error This AL extension version for Visual Studio Code cannot be used with the specified server.

Hi Readers,

In this article, we will discuss about the latest error message that you may face in future.

As most of you know I always try to keep my Business Central installation as latest as soon as its possible.

With this Today I Installed two updates on my local machine -

  • Installed Microsoft Dynamics 365 Business Central Cumulative Update 03.
  • Installed Visual Studio Code to 1.3.0.2
With those updates installed, I started working on my next extension using Visual Studio Code. But when I Try to publish my extension Visual Studio Code generated below Error Message.
ERROR MESSAGE - 
This AL extension version for Visual Studio Code cannot be used with the specified server.
Please update the AL extension from the Visual Studio Code marketplace.

Additional information:
Server details
- Runtime: 2.3
- Web API: 2.0
- Debugger: 2.0

AL extension details
- Supported runtimes: 1.0, 2.0, 2.1, 2.2
- Supported Web API: 1.0, 2.0
- Supported debuggers: 1.0, 2.0

What is the cause of Issue?
AL Language Extension Released from Microsoft is 2.1.69331 which is not supported with updated VS Code 1.3.0.2.

How to Fix it?
Install the AL Language Extension from the Product DVD as shown below.

Navigate to Extension Section in VS Code Editor and select Install from VSIX.


Select the ALLanguage file from the Installed Business Central. 

Default Path - C:\Program Files (x86)\Microsoft Dynamics 365 Business Central\130\AL Development Environment


Install the Extension and reload the VS Code Client. You will see two Extension now for AL Language as shown below. 


The new one is with version 2.1.79379 as above.

Keep the runtime as 2.2 and try to publish again.

Hope article helps you.

Regards,
Saurav Dhyani
www.sauravdhyani.com

Comments

Popular posts from this blog

VIEW SERVER STATE permission on SQL Server?

Hi all, Sometime While trying to Login into a database we face an error message as shown below. --------------------------- Microsoft Dynamics NAV Classic --------------------------- You cannot start Microsoft Dynamics NAV Classic because you do not have the VIEW SERVER STATE permission on SQL Server. Contact your system administrator. --------------------------- OK    ---------------------------

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 searchi...

NAV 2013 R2 - Cumulative update 12 Released.

Hi all, Please find below the details of  Cumulative Update 12 released for Microsoft Dynamics NAV 2013 R2. Title - Cumulative Update 12 for Microsoft Dynamics NAV 2013 R2 Build No. - 38053 Release Date - October, 2014 Local Version Included - AU, AT, BE, CH, DE, DK, ES, FI, FR, IS, IT, NA, NL, NO, NZ, SE, UK, RU Download Link Note: Implementing this cumulative update will require a database conversion unless you have already implemented update rollup 5.