Troubleshooting

Each problem below lists what you see, why it happens and how to fix it.

Unresolved modules

Symptom: the Diagnostics expander on the Solution page lists Unresolved modules you did not expect.

1 2

Cause: a module named in an app.json dependency is not in the workspace or its package folders. Select Unresolved modules, then select each row on the Modules tab of the Diagnostics page. Its Status names the cause:

• “Module not found in workspace”: no folder or package in the workspace provides the module.
• “Download symbols from server and reload workspace”: the module belongs to the workspace, but its symbols have not been downloaded.

Fix:

1. In Visual Studio Code, run AL: Download symbols for the workspace.
2. Select the Reload button in the Workspace window to load the workspace again.
3. If modules are still unresolved, record the workspace with Help › Troubleshoot › Record Workspace… in the Control Panel (see the Troubleshoot menu item) and email us the .wrec file. We use it to reproduce the problem.

Packages ignored when opening folder

Symptom: you opened a folder of packages, one with no app.json directly in it, and a module you expected is missing from the Solution page. In a workspace that depends on such a package, the Diagnostics expander on the Solution page lists Unresolved modules and says “The workspace has unresolved dependencies and one or more runtime packages.”

On the Discovery page, the package's row shows the error “Runtime package format not supported.”

Cause: the package is a runtime package. Runtime packages are encrypted, so Prism for AL cannot read them and leaves them out.

Fix: replace the runtime package with the app's normal package, or with its source folder and app.json, then select the Reload button in the Workspace window. If only a runtime package is available, Prism for AL cannot show that module.

Parse errors

Symptom: the Diagnostics expander on the Solution page lists Compilation unit errors, and the Compilation units tab of the Diagnostics page lists the files or objects that failed.

Cause: Prism for AL could not parse some compilation units. Usually the code does not compile, or the files changed after Prism for AL loaded them. A workspace that compiles with the AL compiler in Visual Studio Code should parse in Prism for AL.

Fix:

1. In Visual Studio Code, run AL: Package to compile the workspace. If it fails, fix the errors it reports.
2. Select the Reload button in the Workspace window to load the workspace again. Do this after any change to the workspace files in Visual Studio Code or another editor.
3. If the errors remain, open the Compilation units tab, open the context menu of the error and select Copy diagnostic info to clipboard. Send it to us through the Feedback window or by email to feedback@stati-cal.com.

Open from BC

Symptom: You get an error notification while connecting to or downloading from Business Central.

A number of things can go wrong when you open a solution from a running Business Central instance with the Open from BC window. Prism for AL pretty much mimics the AL: Download symbols command in Visual Studio Code, so if something goes wrong, the first thing to check is that you can download symbols from Visual Studio Code.

In order to download all apps, Prism for AL retrieves a list of published apps. Therefore, the connecting user needs to have a permission set that includes read permission to TableData of Published Application.

Here follows a list of typical issues grouped by notification (or browser) message:

Entra ID sign-in

“AADSTS90099: The application '08b6330b-c695-4388-a09f-e2155b3cc9c0' (Statical Prism for AL) has not been authorized in the tenant '<CUSTOMER TENANT GUID>'. Applications must be authorized to access the customer tenant before partner delegated administrators can use them.”

Please ask the customer's Azure administrator to grant admin consent for Statical Prism for AL. The breadcrumb path in Azure is Enterprise applications / Statical Prism for AL / Security / Permissions.

“Selected user account does not exist in tenant '<CUSTOMER TENANT GUID>' and cannot access the application '08b6330b-c695-4388-a09f-e2155b3cc9c0' in that tenant. The account needs to be added as an external user in the tenant first. Please use a different account.”

If you are a GDAP partner and trying to access a customer's environment, please make sure that you are added to the security group specified for the admin relationship in your Microsoft partner center.

On-premises connection errors

“Error connecting to OData services on <HOST>:<PORT> - Not Found”

No BC server instance with the specified name was found on the host/port.

• Check the instance name is correct.
• Check the instance is running on the specified server/port; compare with your server's OData configuration.
• For details, select Help › Log › Log Level Debug, try again, then select Help › Log › Open Session Log.

“Error connecting to OData services on <HOST>:<PORT> - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.”
“Error connecting to OData services on <HOST>:<PORT> - No connection could be made because the target machine actively refused it.”

OData services is not running on the server or could not be reached.

• Check that the OData service is running on the specified server/port; compare with your server's OData service configuration.
• Check that your firewall is not blocking the request.
• For details, select Help › Log › Log Level Debug, try again, then select Help › Log › Open Session Log.

“Error connecting to OData services on <HOST>:<PORT> - Web service call failed because user could not be authenticated or authorized.”

• If the server is multi-tenant then check that you have specified the correct tenant.
• Check that your credentials are of the right type (if the server is configured for Username/Password, then you will get this error if you have selected Windows.)
• Check that you can connect to the BC application in a browser and/or download symbols from Visual Studio Code.

“Error connecting to OData services on <HOST>:<PORT> - Unauthorized.”

• Check that your credentials are of the right type (if the server is configured for Windows, then you will get this error if you have selected Username/Password.)
• Check that you can connect to the BC application in a browser and/or download symbols from Visual Studio Code.

“Error connecting to OData services on <HOST>:<PORT> - Service Unavailable”

If you are hosting multiple BC instances on the same OData port, then OData might not be running for the specified instance, but still for other instances.

• Check that the specified instance/service is running.
• Check that the OData service is enabled on the specified server/port; compare with your server's OData service configuration.
• For details, select Help › Log › Log Level Debug, try again, then select Help › Log › Open Session Log.

“Error connecting to Developer services on <HOST>:<PORT> - Not Found.”
“Error connecting to Developer services on <HOST>:<PORT> - Service Unavailable”

No running Developer service was found for the specified instance.

• Check that the Developer service is running on the specified server/port; compare with your server's Developer service configuration.
• For details, select Help › Log › Log Level Debug, try again, then select Help › Log › Open Session Log.

“Error connecting to Developer services on <HOST>:<PORT> - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.”
“Error connecting to Developer services on <HOST>:<PORT> - No connection could be made because the target machine actively refused it.”

Developer services is not running on the server or could not be reached.

• Check that Developer services are running on the specified server/port; compare with your server's Developer service configuration.
• Check that your firewall is not blocking the request.
• For details, select Help › Log › Log Level Debug, try again, then select Help › Log › Open Session Log.

Online connection errors

“Error connecting to OData services on businesscentral.dynamics.com - Not Found.”

Check that the specified environment name exists on the specified tenant.

“Error connecting to Developer services on businesscentral.dynamics.com - Internal Server Error.”

Please check that you are not trying to download from a Production instance. For online, you can only download from Sandbox environments.

Download failed

“Some symbol files failed to download, see log file for more information.”

Please inspect Prism for AL's session log.

• If AL: Download symbols works in Visual Studio Code, then most likely you are only missing read permission on TableData of Published Application. Ask your administrator to give you this permission and try again.
• If the log contains "Unable to get company ID" or mentions missing permissions, please ensure the user has at least the following permissions:

  Object Type	Object ID	Object Name	Permissions
  Table Data	2000000153	NAV App Installed App	Rimd
  Table Data	2000000206	Published Application	R
  Table	2000000206	Published Application	X
  Codeunit	2504	Extension Management	X
  Page	30002	APIV2 - Aut. Extensions	X

  This was last checked with BC26. If the log mentions properties other than these, please let us know.

• If the error reads like “404 No HTTP resource was found that matches the request URI 'api/…/companies(…)/extensions'”, then the _Exclude_APIV2_ app may not be installed on the server. If so, please install it and try again.

Configuration

(Get-NAVServerConfiguration <BC>) | Where-Object { $_.Key -match "ODataServices(Enabled|Port|SSLEnabled)" }

(Get-NAVServerConfiguration <BC>) | Where-Object { $_.Key -match "DeveloperServices(Enabled|Port|SSLEnabled)" }

Get-NAVAppInfo -ServerInstance <BC> -Tenant default | Where-object { $_.Name -eq "_Exclude_APIV2_" }

Navigation inaccurate

Symptom: navigation within Prism for AL, or with View in Prism for AL from Visual Studio Code, lands on the wrong line or the wrong declaration.

Cause: the setting Memcache (Keep snapshot in memory) was off when you opened the workspace, and its files have changed since then, in Visual Studio Code or another editor. Without the snapshot, the files on disk no longer match the code Prism for AL loaded.

Fix:

1. Select the Reload button in the Workspace window to load the workspace again.
2. To keep what you see stable while files change, turn Memcache on in the Settings page. It is on by default and applies to the next workspace you open.

If navigation is inaccurate in any other situation, report it through the Feedback window or by email to feedback@stati-cal.com.

Invalid license

Symptom: Prism for AL runs with limited features, and the license status line on the Control Panel's Home page shows one of the statuses below in red. Hover over the status line: its tooltip says why and what to do.

1 2

Cause and Fix depend on the status:

A key you activate replaces the one before it. If the new key turns out to be the wrong one, the Activate license window can restore the previous license.

MCP server

Problems with the MCP Server page and with agents that use it.

For anything else, select Help › Feedback… in Prism, or let the agent call submit_mcp_feedback.