New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Could not download symbols. Reason: No published package matches the provided arguments. #106

Closed
louagej opened this Issue Nov 22, 2017 · 7 comments

Comments

Projects
None yet
2 participants
@louagej

louagej commented Nov 22, 2017

I Installed a nex NAV-Container with this powershell script.
New-CSideDevContainer
-containerName DEVServer -accept_eula
-accept_outdated -auth NavUserPassword
-Credential admin -doNotExportObjectsToText
-imageName microsoft/dynamics-nav:devpreview -licenseFile "C:\Users\<Username>\Documents\Licence\fin.flf"
-memoryLimit 3G -updateHosts
-Verbose`

After installing, I can connect to the web client and the classic dev environment.
But when I'm trying to connect with Visual studio code, I get the message:

Could not download symbols. Please see the Visual Studio Code output log for more details.
2017_11_22_ 000

This is what appears in the log file:
`[2017-11-22 05:37:14.27] The request for path /nav/dev/packages?publisher=Microsoft&appName=System&versionText=11.0.19097.0&tenant=default failed with code NotFound. Reason: No published package matches the provided arguments.
[2017-11-22 05:37:14.27] Could not download reference symbols. Please ensure that:

  1. The correct server name and instance are specified in the launch.json file.
  2. The correct application locale and version are specified in the app.json file.
    The Version in my app.json matches the one on the server:"application": {
    "version": "11.0.19097.0",
    "locale": "W1"
    }`
    2017_11_22_ 002

And the servername matches the name in my launch.json:
2017_11_22_ 001

@freddydk

This comment has been minimized.

Contributor

freddydk commented Nov 23, 2017

Could you try to set the tenant to blank instead of default?

@louagej

This comment has been minimized.

louagej commented Nov 26, 2017

As you recommended in your mail, I removed the container and created a New-CSideDevContainer with -usessl:$false. and I also tried to set the tenant blank instead of default.

> when you are running navuserpassword, the container defaults to https.
you can specify -usessl:$false to your new-container command or use https in the launch.json.
After running the image, it displayed the server url, you can also write docker logs devserver and you will get the output again.

Unfortunately I still get the sames error message in the VSCode log:

[2017-11-26 08:30:54.17] The request for path /nav/dev/packages?publisher=Microsoft&appName=System&versionText=11.0.19097.0 failed with code NotFound. Reason: No published package matches the provided arguments.
[2017-11-26 08:30:54.17] Could not download reference symbols. Please ensure that:
1. The correct server name and instance are specified in the launch.json file.
2. The correct application locale and version are specified in the app.json file.
@freddydk

This comment has been minimized.

Contributor

freddydk commented Nov 26, 2017

Yeah, I actually deleted that comment because I found out it wasn't true.
What version of the AL extension is installed in VS code and where did you get it?

@louagej

This comment has been minimized.

louagej commented Nov 26, 2017

I'm using the October Update
2017_11_26_ 000

@freddydk

This comment has been minimized.

Contributor

freddydk commented Nov 26, 2017

Ok, that's the problem.
The docker image is November preview.
docker logs will show you the url for downloading the AL extension matching the docker image.
Download and install that one should solve your problem.
I will try to make it more obvious when using new-navcontainer what the .vsix is.

@louagej

This comment has been minimized.

louagej commented Nov 26, 2017

Hi,
This solved the problem:
2017_11_26_ 001

Does this mean that for future programming, we have customers with let's say 5 different NAV-versions, we'll have to download 5 different AL Language extensions in VS Code?

@freddydk

This comment has been minimized.

Contributor

freddydk commented Nov 26, 2017

Only if you are using preview or insider builds.
Else - one of the ideas of extensions v2 is to ensure that no customer is left behind.

@freddydk freddydk added the question label Dec 1, 2017

@freddydk freddydk closed this Dec 1, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment