Small and medium business | Business Central, N...

Attaching Debugger gives error

(0) Share

Report

Posted on by Daan Schuitmaker

Hi,

I'm trying to attach to a webservice but vs code keeps giving me the following fail:

The request for path /BC160/dev/metadata failed with code MethodNotAllowed. Reason: Method Not Allowed

Running the client with launch works only attach gives me this error.

I hope somebody can help me.

Thanks in advance

I have the same question (0)

All responses (5)

Answers (0)

THE Italian on at

Like (0)

Report

can you show here the following:

1. launch.json file

2. app.json file

3. screenshot of the AL Language version that your are using (build no.)

Was this reply helpful? Yes No
Daan Schuitmaker 5 on at

Like (0)

Report
launch.json

{ "version": "0.2.0", "configurations": [ { "name": "ELC25 Local Development", "type": "al", "request": "launch", "server": "http://localhost", "serverInstance": "BC160", "authentication": "Windows", "startupObjectId": 22, //"startupObjectId": 11021530, "startupObjectType": "Page", "breakOnError": true, "launchBrowser": true, "enableLongRunningSqlStatements": true, "enableSqlInformationDebugger": true, "schemaUpdateMode": "ForceSync" }, { "name": "Debug: ELC25 WebService", "type": "al", "request": "attach", "server": "http://localhost", "port": 7047, "serverInstance": "BC160", "authentication": "Windows", "breakOnError": true, "breakOnRecordWrite": false, "enableSqlInformationDebugger": true, "enableLongRunningSqlStatements": true, "longRunningSqlStatementsThreshold": 500, "numberOfSqlStatements": 10, "breakOnNext": "WebServiceClient" } ] }

app.json

{ "id": "781203f8-1ade-47fe-8d41-9c5319586d30", "name": "ELC25", "publisher": "Dysel", "version": "1.0.0.7", "brief": "ELC 25", "description": "ELC 25", "privacyStatement": "", "EULA": "", "help": "", "url": "", "logo": "", "dependencies": [ { "id": "63ca2fa4-4f03-4f2b-a480-172fef340d3f", "publisher": "Microsoft", "name": "System Application", "version": "16.3.14085.14238" }, { "id": "437dbf0e-84ff-417a-965d-ed2bb9650972", "publisher": "Microsoft", "name": "Base Application", "version": "16.3.14085.14238" } ], "screenshots": [], "platform": "16.0.0.0", "idRanges": [ { "from": 50000, "to": 11134251 } ], "contextSensitiveHelpUrl": "https://ELC24.com/help/", "showMyCode": true, "runtime": "5.0", "target": "OnPrem" }

Output of VS Code

Was this reply helpful? Yes No
Suggested answer

THE Italian on at

Like (0)

Report

I can see Application 13.1 this shouldn't be like that.

When upgrading you should have followed the step of running Set-NAVApplication and change the application version.

Very hard to say what might go wrong in here. I would ask your CSP Partner to open a request to Microsoft support in order to double check and verify the upgrade has been performed OK and also the Attach procedure.

Was this reply helpful? Yes No
Suggested answer

Daan Schuitmaker 5 on at

Like (0)

Report

I've found the solutions myself...

It was the port... it needed to point to the development part.

Was this reply helpful? Yes No
THE Italian on at

Like (0)

Report

port no... an evergreen trivial mistake :-)

Was this reply helpful? Yes No