Open Forum

Expand all | Collapse all

loading symbols issues when creating extension; launch.json

Jump to Best Answer
  • 1.  loading symbols issues when creating extension; launch.json

    Posted 10 days ago

    Hi all -

    Background: I have used NAV before with a training license (i.e. could modify pages etc. in dev environment). I am trying to upgrade to BC (on-premises). I have BC (on-premises) setup as a stand alone VM with demo database. I can still use the NAV with BC. I can also open BC by opening the web-client.

    I want to try extensions using visual code in BC which looks much better than dealing with old interface in NAV (i.e. without Visual Code) for creating/modifying pages/tables etc.

    Therefore, I have installed Visual Code and AL Extension. [FYI - For AL extension, I tried both installing the extension and also using .vsix file as I saw this as one solution to 'loading symbols' problem]

    Now, I am having issues downloading symbols. I believe I can't do much customization on BC without this setup. I have looked at the forum for similar issues and still can't figure out the errors. 

    Errors:
    [2019-09-05 08:32:37.95] Using reference symbols cache path: c:\Users\Administrator\Documents\AL\ALProject3\./.alpackages
    [2019-09-05 08:32:37.95] Sending request to localhost:8080/.../packages
    [2019-09-05 08:32:37.95] Sending request to localhost:8080/.../packages
    [2019-09-05 08:32:37.95] The request for path /BC140/dev/packages?publisher=Microsoft&appName=System&versionText=14.0.29530.0 failed with code NotFound. Reason: Not Found
    [2019-09-05 08:32:37.95] The request for path /BC140/dev/packages?publisher=Microsoft&appName=Application&versionText=14.0.29537.0 failed with code NotFound. Reason: Not Found
    [2019-09-05 08:32:37.95] 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 version is specified in the app.json file.
    3. The dependencies are correctly specified in the app.json file.

    Get-NAVServerInstance gives the following

    ServerInstance : MicrosoftDynamicsNavServer$BC140
    DisplayName : Microsoft Dynamics 365 Business Central Server [BC140]
    State : Running
    ServiceAccount : NT AUTHORITY\NETWORK SERVICE
    Version : 14.0.29530.0
    Default : True

    My launch.json (note: For "name" field - I tried the "your own server', 'BC140', 'Microsoft Dynamics 365 Business Central' names) settings :

    {
    "version": "0.2.0",
    "configurations": [
    {
    "type": "al",
    "request": "launch",
    //"name": "Your own server",
    "name": "BC140",
    "server": "http://localhost:8080",
    "serverInstance": "BC140",
    "authentication": "Windows",
    "startupObjectId": 22,
    "startupObjectType": "Page",
    "breakOnError": true,
    "launchBrowser": true
    }
    ]
    }

    My key app.json settings

    {
    ...<deleted for brevity>...
    "dependencies": [],
    "screenshots": [],
    "platform": "14.0.29530.0",
    "application": "14.0.29537.0",
    "idRanges": [
    {
    "from": 50100,
    "to": 50149
    }
    ],
    "contextSensitiveHelpUrl": "">https://ALProject3.com/help/",
    "showMyCode": true,
    "runtime": "3.0"
    }

    I got the platform and application numbers from help page of BC-web client. Help & Support page lists the following under 'Troubleshooting' 

    Version: Platform 14.0.29530.0 + Application 29537 (US Dynamics NAV 14.0)

    Please let me know how to solve this issue. 

    Thanks a lot!! - Rama



    ------------------------------
    Rama Ayyagari
    Associate Prof
    UMass Boston
    Boston
    ------------------------------


  • 2.  RE: loading symbols issues when creating extension; launch.json

    TOP CONTRIBUTOR
    Posted 9 days ago
    When you are using the vsix  extension, are you using the the vsix from the installation file on your BC On-Prem?

    ------------------------------
    Kristoffer Ruyeras
    Solutions Architect
    Tigunia
    Seattle, WA
    ------------------------------



  • 3.  RE: loading symbols issues when creating extension; launch.json

    Posted 6 days ago
    Yes, I tried both AL extension from VSCode and vsix file from the installation.

    ------------------------------
    Rama Ayyagari
    Associate Prof
    UMass Boston
    Boston
    ------------------------------



  • 4.  RE: loading symbols issues when creating extension; launch.json

    Posted 7 days ago
    Your servername should not include the :8080, remove that bit and try again.

    ------------------------------
    Erik Hougaard
    MVP
    E Foqus Danmark A/S
    North Vancouver BC
    ------------------------------



  • 5.  RE: loading symbols issues when creating extension; launch.json

    Posted 6 days ago
    Thanks Erik. I tried only http://localhost first - when that didn't work, I tried port number also.

    ------------------------------
    Rama Ayyagari
    Associate Prof
    UMass Boston
    Boston
    ------------------------------



  • 6.  RE: loading symbols issues when creating extension; launch.json
    Best Answer

    Posted 6 days ago

    Thanks for the replies. I got it working. I did the following (not sure which step solved exactly)

    - Erik's suggestion for NAV2018 seemed to work for me. Check "Enable Developer Service Endpoint" in BC Admin and "Allowed Extension Target Level" to "Internal". See www.hougaard.com/.../

    - Removed Port number from Server address in launch.json settings (i.e used http://localhost)

    - Used default app.json settings (i.e. didn't change platform and application settings from default 14.0.0.0)

    - Used (AL:Package) first/followed by (AL:Loading Symbols) -- this seemed to download the symbols.

    I was then able to publish the extension and check that the extension works in BC.



    ------------------------------
    Rama Ayyagari
    Associate Prof
    UMass Boston
    Boston
    ------------------------------



If you've found this thread useful, dive deeper into User Group community content by role