While running visual studio code for a flutter program, I am getting this error log in the terminal tab.
Please help me to resolve it.
Thanks
flutter run -d chrome
Launching lib\main.dart on Chrome in debug mode...
Waiting for connection from debug service on Chrome... 26.1s
Failed to establish connection with the application instance in Chrome.
This can happen if the websocket connection used by the web tooling is unable to correctly establish a connection, for example due to a firewall.
Try running in release mode.
flutter run -d chrome --release
Related
I am working on windows and have installed openstack on virtual box (ubuntu vm). I want to enable debugging for this code hence enabled remote debugging using ssh on VS code. Now i want whenever i run a cli command on cinder openstack (terminal) i should be able to see the flow of code. Please help.
I tried remote debugger with different python files to start in debugging mode but unable to get it.
I have a .NET Core 3.1 console app I have deployed to server and setup as a windows service. I can open cmd window as admin and navigate to the exe and it runs the exe with no errors or issues.
However when I try to start the Windows Service it immediately fails with an error:
Windows could not start the service on the local computer. Error 1053: The Service did not respond to the start or control request in a timely fashion.
We have ServicesPipeTimeout set to 180000
and rebooted server but it still fails immediately. Shouldn't it take time before the timeout error comes up?
I have also ensured we have the Release version of the code as I found posting saying Debug versions of code will cause this issue.
The folder permissions are as follows:
Since the console app runs fine from the command prompt there should not be an issue with the code/framework on the system?
Is there anything else to check?
I'm having some trouble trying to get Blazor WASM debugging to work with VS2022 17.3.3 and was wondering if anyone on here could give me a hand/ had encountered this issue before?
When running any Blazor WASM project(I've tried with a fresh project as well) with the debugger, it will open correctly and run for about ~10-60s, before crashing and closing the browser. I get the following error in the debug console:
Console output of debug run
When running without debugger or via CLI the application runs without crashing.
I originally had an error in the browser identical to the one described here: https://learn.microsoft.com/en-us/answers/questions/741393/error-with-websocket.html but after disabling Hot Reload and Browser link this no longer started appearing, the crashing error still occurred though. Interestingly after re-enabling these settings the browser error has not reoccurred, and from what I can see hot reload isn't working at all when running with the debugger attatched.
Thanks for the help and happy to post any further details on my setup if anything else could be useful.
We have a couple of ASP.Net + Angular (.Net Core 2.1, Angular5) web pages on the IIS server that suddenly stopped working.
We get "AggregateException: One or more errors occurred. (One or more errors occurred. (The NPM script 'start' exited without indicating that the Angular CLI was listening for requests. The error output was: ))".
It seems that it attempts to run npm as the web is launched and it crashes. I tried to install Nodejs on the server and I can see the npm really starts, but crashes with mkdir operation not permitted. Anyway, I don't understand why it's started in the first place.
When start the same app on local IIS npm is not started and app runs without the problem.
We can't find what happened on the server. The same apps ran smoothly before.
Many thanks.
Michal
Solved. Colleagues set ASPNETCORE_ENVIRONMENT = DEVELOPMENT. Changing it back to Production fixed it.
I've two web sites running on my IIS 7.5. Both on port 80. Since they are both on the same port, I have to stop one to start the other. I am not using the inbuilt cassini server. Debugging works fine when using cassini.
The problem I am facing is that when I try to debug my mvc application (which was created under the second website) I get the error:
Unable to start debugging on the web server. An unexpected DCOM error
occurred while trying to automatically attach to the remote web
server. Try manually attaching to the remote web server using the
'Attach To Process' dialog.
The web application has windows authentication enabled. Any ideas?
Additional details : I'm able to do a "attach to process" and debug it. But cannot debug using F5
Although I was trying to remotely debug a simple *.exe application running on a different machine but I was getting very similar error mentioned by the OP.
Unable to attach to the process. A DCOM error occurred trying to
contact the remote computer. Access is denied.
It may be possible to avoid this error by changing your settings to
debug only native code or only managed code.
I followed this Microsoft documentation and following below step helped resolve my error:
Turn off Native Compatibility Mode and Managed Compatibility Mode.
You can follow below screen shot to achieve the same:
I didn't require to reboot the machine. You can also try that way and if it doesn't work then go ahead the reboot the machine.
Set the Connect as property of the website to Application user.