microsoft / AL

Home of the Dynamics 365 Business Central AL Language extension for Visual Studio Code. Used to track issues regarding the latest version of the AL compiler and developer tools available in the Visual Studio Code Marketplace or as part of the AL Developer Preview builds for Dynamics 365 Business Central.
MIT License
748 stars 245 forks source link

Debugging Sorry, that didn't work #1642

Closed gnaaktgeboren closed 6 years ago

gnaaktgeboren commented 6 years ago

When I try to debug the webclient gives the error Sorry, that didn't work I've disable the NetFx40_LegacySecurityPolicy. `

\

` What am I doing wrong?

quadfin commented 6 years ago

I have a similar issue - if the debugger hits a breakpoint it just hangs -- resulting in the "Sorry.." error. Symbol download, app publish, app run -- all work fine, I just can't debug.

I have disabled the security policy - I have made sure the server is properly configured for development. I have run symbol generation. I have setup the launch.json and app.json as per other input in this forum. I am using a vanilla Cronus database.

If I watch the network traffic in the browser debugger I see this rather fatal looking error: HTTP502: BAD GATEWAY - The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request. (XHR)POST - http://localhost:8080/dynamicsnav110/cbs?aid=NAV

If I look in the Event Viewer on the server I see the ominous error listed below. Obviously this is telling me something is misconfigured -- but I can't figure out what. Anybody ?

Event Viewer error on server: instanceName DynamicsNAV110 message Failed request -- Method:GET; Url:http://localhost:7049/DynamicsNAV110/dev/signalr/start?clientProtocol=1.4&transport=webSockets&connectionData=[{"Name":"DebuggerHub"}]&connectionToken=AQAAANCMnd8BFdERjHoAwE%2FCl%2BsBAAAAiVyPfhFbpEiuF5dQhiT8LQAAAAACAAAAAAAQZgAAAAEAACAAAACaIH6pZZVlHkcc8y%2BDL6sny1rLA94tOomMyDdVsQJYhwAAAAAOgAAAAAIAACAAAADWFwDLWKEAtibK3cf3yhpswNM2FqyhUb%2B6pzHq5OJorEAAAAAIzvOeu6lwnuLVFvPl6qxRqvSZh%2Fd%2B4NeXp0YanLu3xpK69mRpyE6L6w26%2FRn3fsFMZkxHoNTAw2wbbn2OyxjuQAAAAJ9tX8a7sbUFjO5tNLF6UNIJjMqerHShvF5ACEmxnlG0kR6xHkVKyBI2LI4fJ6muClFCTyGwDJQRtde%2FOmBQubs%3D; StatusCode:NotFound; ReasonPhrase:Not Found; ResponseBody: {"Message":"No HTTP resource was found that matches the request URI 'http://localhost:7049/DynamicsNAV110/dev/signalr/start?clientProtocol=1.4&transport=webSockets&connectionData=[{\"Name\":\"DebuggerHub\"}]&connectionToken=AQAAANCMnd8BFdERjHoAwE%2FCl%2BsBAAAAiVyPfhFbpEiuF5dQhiT8LQAAAAACAAAAAAAQZgAAAAEAACAAAACaIH6pZZVlHkcc8y%2BDL6sny1rLA94tOomMyDdVsQJYhwAAAAAOgAAAAAIAACAAAADWFwDLWKEAtibK3cf3yhpswNM2FqyhUb%2B6pzHq5OJorEAAAAAIzvOeu6lwnuLVFvPl6qxRqvSZh%2Fd%2B4NeXp0YanLu3xpK69mRpyE6L6w26%2FRn3fsFMZkxHoNTAw2wbbn2OyxjuQAAAAJ9tX8a7sbUFjO5tNLF6UNIJjMqerHShvF5ACEmxnlG0kR6xHkVKyBI2LI4fJ6muClFCTyGwDJQRtde%2FOmBQubs%3D'.","MessageDetail":"No route data was found for this request."}

StanislawStempin commented 6 years ago

Hi, we would like to ask for some additional information. @gnaaktgeboren - could you please provide Event Log error? We would like to see if this is indeed the same error that both of you are facing.

In addition, which versions of the NAV server and AL Language extension are you using? Are you on the latest February Developer Preview?

gnaaktgeboren commented 6 years ago

Hi,

I've attached the errors as a text file.

The versions that I'm using are: AL extension 0.12.16641 NAV version CU2 (11.0.20348.0).

Nav errors.txt

olisterr commented 6 years ago

Hi @gnaaktgeboren, Try signing out and signing in again. It solved the error for me. Although I was not getting any error in VSCode, just the webclient would crash.

gnaaktgeboren commented 6 years ago

Hi @olisterrcf ,

Just tried that, no luck.

StanislawStempin commented 6 years ago

@gnaaktgeboren have you restarted the server after setting the ?
Your error log shows that this setting is still enabled.

gnaaktgeboren commented 6 years ago

@StanislawStempin I just did that again but with no luck.

StanislawStempin commented 6 years ago

Thanks. Since you're on NAV 2018 and this potentially requires deeper investigation please log a support case for your problem: https://github.com/Microsoft/AL/wiki/Frequently-Asked-Questions#nav-2018-issues