.\AL Package not found

(0) Share

Report

Posted on by Prayusha

I am facing this same error and on the verge of pulling my hair out. I thought maybe the problem could be some trust issues with account on my machine but no. I created an on-premise environment in an Azure VM and it still gives this issue there.

The AL: Clear Credential Cache does not work too.

Any suggestions?

Categories:

Business Central

Other

All responses (15)

Answers (0)

Sort by

Suggested answer

Mohana Yadav 61,252 Super User 2026 Season 2 on at

Like (0)

Report
Copy link

Link copied!

Did you download symbols?
Suggested answer

Teddy Herryanto (Th... 14,306 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

It looks like you are missing the symbols.

Do the AL:Download Symbols.
Suggested answer

Stefano Demiliani 37,172 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

Adding something more to what said above: have you correctly configured launch.json file? are you working with an on-premise instance on your local machine or not?

In the above picture, it seems that you're working with a server instance called BC130 on localhost and Windows authentication. Please check it because these are the default demo values and should be changed accordingly to your environment.
Suggested answer

Teddy Herryanto (Th... 14,306 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Is the server correct ? Try doing http://localhost/bc130/ in your web browser and see if you can access your BC or not. If not, you are pointing to the wrong server.
Prayusha 57 on at

Like (0)

Report
Copy link

Link copied!

I found the issue. There are two BC Instances (BC130 and BC140) created on my machine (I couldn't really find out how). This is an On-premise installation. The launch.json connected to the wrong serverinstance. I changed it to BC140 and was able to connect through. All went well since. Thank you for the helpful reponses
Prayusha 57 on at

Like (0)

Report
Copy link

Link copied!

I found the issue. There are two BC Instances (BC130 and BC140) created on my machine (I couldn't really find out how since I always overwrite). This is an On-premise installation. The launch.json connected to the wrong serverinstance. I changed it to BC140 and was able to connect through. All went well since. Thank you for the helpful responses
NadBug 20 on at

Like (0)

Report
Copy link

Link copied!

Hi, I have the same issue but happening only on a macbook. I installed VSC on a windows laptop and everything ran smoothly. Packages were downloaded and managed to connect to BC19.

Do you have any ideas what i can do to run it on a macbook. It is not downloading .AL Packages at all. I tried downloading the AL Package via the command palette, cleared the user credentials cache as well.

I
Suggested answer

Brad_P 1,551 on at

Like (0)

Report
Copy link

Link copied!

Did you download the symbols from the tenant that you have listed in the Launch file? Is there an error when downloading the symbols? Did you change the "al.packageCachePath" setting?
NadBug 20 on at

Like (0)

Report
Copy link

Link copied!

Yes, i got the error that symbols cannot be downloaded with the below details:

'Processing of message 'al/downloadSymbols' failed with error: 'GSSAPI operation failed with error - An unsupported mechanism was requested.'

In fact No folder in the defined file path is being created of type .alpackage.

I did not change any user settings with reference to .alpackage settings - it is the default settings as per below:

./.alpackages

Any ideas, it looks like I'm encountering this issue only on a mac, did not encounter this when doing the same process on a windows pc.

Thanks,

Nadine

Y
Suggested answer

Brad_P 1,551 on at

Like (0)

Report
Copy link

Link copied!

Did you try "authentication": "UserPassword"? I recall that being an authentication error.