MCP Servers cannot start altool
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Idoneità per principianti
- 65/100
- Tipo di issue
- Bug
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Attiva
- Stack tecnologico
- powershell
- Ambito
- devtools
Direzione di ricerca
Start by locating the Business Central Profiling MCP Server launch configuration and how it resolves altool; the issue does not name source files or tests. Check how the installed AL Language extension path can be obtained, then reproduce with altool.exe absent from PATH. Done when the server starts using the bundled executable without requiring a PATH change.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
1. Describe the bug
The Business Central Profiling MCP Server fails to start in VS Code with the following error:
Error: spawn altool ENOENT
The AL Language extension is installed and altool.exe is present in the extension's bin folder.
The issue appears to occur because the MCP server resolves altool through the system PATH instead of using the AL extension installation directory.
Adding the AL extension's bin directory to PATH resolves the issue immediately.
2. To Reproduce
Steps to reproduce the behavior:
- Install the latest AL Language extension.
- Ensure altool.exe is not available through the system PATH.
- Open Visual Studio Code.
- Start the Business Central Profiling MCP Server.
Example installation location:
C:\Users<user>.vscode\extensions\ms-dynamics-smb.al-\bin\altool.exe
Observed output:
Starting server Business Central Profiling MCP Server
Connection state: Starting
Starting server from LocalProcess extension host
Connection state: Starting
Connection state: Error spawn altool ENOENT
Workaround:
Add the AL extension's bin directory to PATH.
Restart Visual Studio Code.
The Profiling MCP Server then starts successfully.
No AL code is required to reproduce the issue.
3. Expected behavior
The Business Central Profiling MCP Server should start successfully whenever the AL Language extension is installed.
The server should locate and launch the bundled altool.exe from the installed AL extension rather than depending on the executable being available through the system PATH.
4. Actual behavior
The Profiling MCP Server fails to start with:
Error: spawn altool ENOENT
even though altool.exe is present in the installed AL extension.
The issue disappears immediately after adding the AL extension's bin folder to PATH.
Log excerpt:
2026-10-21 09:31:41.196 [info] Connection state: Error spawn altool ENOENT
Additional information:
The issue was reproduced on a clean AL-only VS Code setup. The presence of altool.exe was verified, and adding the extension's bin directory to PATH resolved the issue without any other changes.
This suggests the Profiling MCP Server is not resolving altool relative to the installed AL extension.
5. Versions:
- AL Language: Latest version available in Visual Studio Code Marketplace
- Visual Studio Code:
- Business Central:
- List of Visual Studio Code extensions that you have installed:
- AL Language
- Operating System:
- Windows
- Linux
- MacOS
Final Checklist
- Search the issue repository to ensure you are reporting a new issue
- Reproduce the issue after disabling all extensions except the AL Language extension
- Simplify your code around the issue to better isolate the problem
- Lingua principale
- PowerShell
- Stelle
- 889
- Fork
- 285
- Merge medio
- 4h 7m
- PR unite (30g)
- 1
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di microsoft/AL
-
accepted al-tools bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 48/100
-
Difficoltà 4/5 1-2 giorni Idoneità per principianti 45/100
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 25/100
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 45/100
Tutte le issue di microsoft/AL
Issue simili
-
ds-bot collides with dsh-argp: tool "recall" is already registered, Bot layer never activatesApertabug
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
Fei2411/DeepSeek-Bot#703 ·
-
enhancement help wanted
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
Git-Hospital/githealthcheck#61 ·
I maintainer di solito rispondono entro 1 giorno
-
[Server Submission]: Wiro AIAperta
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 83/100
cline/mcp-marketplace#3394 ·
-
Assembly "Go to in Memory Editor" does nothing for parallel port, scratchpad and BIOS addressesAperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
grumpycoders/pcsx-redux#2529 ·
-
语音扩展怎么让气泡和声音对上:之前的几种做法与建议Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
Pal-AI-Lab/Coopanion#538 ·
I maintainer di solito rispondono entro 1 giorno