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
Labels:
Location: Dehradun, Uttarakhand, India

Comments

Post a Comment

Popular posts from this blog

Microsoft Dynamics NAV 2016 - How to Configure Phone Client.

Hi All, In this article we will discuss how we can connect Microsoft Dynamics NAV 2016 with New Client Launched i.e. Phone Client. This Article Contain Steps for a Android Phone as I have Only Android Phone. I am doing it having all tiers on my windows 8 machine, steps remain same for multiple servers but issues might be different. What we Need (Other what we discuss in this article) -  The Service Tier should be on Public IP . Some of the Data-card does not Provide you Public IP. check it for sure.
28 comments
Read Complete Article »

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.
21 comments
Read Complete Article »

🚀 Exploring Vibe Coding with GitHub Copilot for Business Central.

Hi All, In a recent #BCOpenDiscussion session, we delved into the fascinating concept of Vibe Coding —a new way of building software where developers collaborate with AI (like GitHub Copilot) to co-create solutions.  The session covered practical setup, how AI understands context, and even touched on Microsoft's new Model Context Protocol (MCP) integration for enhanced learning. Let’s break down the journey, step by step.
Post a Comment
Read Complete Article »