I am getting this error on the client side in browser web application.
Unexpected error.
This appears in a totally white blank page in the browser on the top left corner when I access my web application.
It appears occasionally. There is no error in the Meteor Server Console or in the browser console. It can't be reproduced either.
Whenever this error appears, none of my client apps (Android, iOS, web app) work, when they are connected to this specific server. The server shows that it's running but it does not. When I restart Meteor Server, then it starts working fine, I get this error once in about two weeks, I don’t know what is causing this error, or how to debug this.
Any idea what is causing this issue? This is really critical, I have my Live Application running, and it should not crash like this. Please provide me with some solution or a way to debug. Thanks
Also are there any logs on my Meteor App which I can check? Plus I am running this App on staging with --production flag.
Related
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.
I'm working a ASP.NET MVC project in Visual Studio 2015 (14.0.25431.01 Update 3) that runs IISExpress to debug the application. However, sometimes (and I haven't figure out what the trigger is) when I debug the application my browser will open to the correct URL but it will just say "Unable to connect".
If I try to refresh the window nothing changes. If I check Visual Studio it still says it's debugging so the debugger or IIS doesn't seem to have crashed. Sometimes if I just click Restart it will work fine. However, sometimes this error continues and I have to kill the IIS process. I've tried deleting the files under .vs\config but that didn't help.
Is there any way to fix this or anyway to find some logs to see whats happening? This started in the last few weeks and it starting to drive me crazy.
Edit
Happened again and tried connecting via Chrome as well as my usual FireFox. Looking at the developer tools in Chrome I'm seeing the ERR_CONNECTION_REFUSED message.
I decided to check the Windows Event Viewer and found that it looks like IIS Express can't bind to the port.The error message is:
Unable to bind to the underlying transport for [::]:12345. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine. The data field contains the error number.
But why it can't bind to that port I don't understand.
I am having a problem with my application. The application works perfect on my development machine. It fails, without any errors on the live server. The page loads, but the code doesn't execute apparently.
I have been stuck on this for a while because I can't figure out how to get any information on the problem. There are no errors, so my custom errors settings in web.config are not helping.
I looked around online and I heard there was some remote debugging tool. The article was from .Net 1.0. I tried to follow it, but its not going to work because I am using a shared server. I do not have permissions to start the remote debugger on the server side.
I tried creating some output text files with variable contents, but the files are not being created either. They are created on my development machine, but never show up on the server, again with no error.
I have no idea how I'm supposed to figure out what is going on, because I'm not able to step through the code once it's on the live server.
Is there anyway to step through, or debug the code once I've published it? If I spent the extra money on a VPS, would that allow me to debug on the server side? I'm assuming I could just install Visual Studio on the VPS and step through the program. I've never used a VPS before.
Unless you do something very special in your code, it is unlikely that it behaves differently on your server compared to your workstation.
It is more likely that the configuration on the server is not correct.
You are saying your
code doesn't execute
How do you know that? You should first confirm that your code is actually executing.
you are also saying:
it is now directing me to a page that says "Directory Not Found"
a web server it never looking for directories, it is looking for resources, check your iis http logs what substatus codes are you getting?, enable Failed Request Tracing and review the logs.
Using Process Monitor can also help determine what the web server is doing.
Start with a very simple page and see whether that executes fine.
What I'm saying is, first debug/fix the execution environment before trying to debug your code.
You would never install Visual Studio on a server, the default installation of a Windows Server doesn't even allow you to install it. Instead you can use remote debugging components on the server and use your local Visual Studio to debug remotely.
Running into a strange 'error' to do with routing when deploying a Meteor app, both on meteor.com and on heroku. When the application is running locally, everything works fine. However, when the app is deployed - and I've tried this both on meteor.com's simple hosting and on Heroku - I get the default Iron Router setup page with instructions on how to set up my first route, even though the routes are defined correctly and work locally (screenshot below). This happens on all pages in the app.
Here's a screenshot of the page: http://i.stack.imgur.com/GlNd9.png
I ran into this recently may be able to shed some light on the issue.
If you are working fine in development but not in production then the first thing to do is run your development/local version like so:
meteor --production
This runs the local development version in production mode, as it does when deployed to Modulus, Heroku etc.
If you now get the iron router splash page locally you can be sure the issue is due to running in production mode.
Open up your site in Chrome (or your favourite browser) and look in the browser javascript console for errors... I had one in my client events javascript which I had recently changed.
If you have an error fix it then see whether your Meteor app now runs with the --production flag without showing the Iron Router page.
The splash page in my case was a red herring, masking the real error under the hood.
I haven't looked in depth into the difference between the development and production modes but it obviously handles errors differently so you get different behavior in the two modes.
When I try to debug my VS2010 web app (F5), the IE web browser windows pops up but then freezes, and my VS2010 IDE window pops up an error message:
Unable to start program 'http://localhost:nnnn/Login.aspx'.
Access is denied.
I'm running VS2010 (10.0.30319.1), targeted to ASP.NET 4.0 (4.0.30319), in non-administrator mode, with ASP.NET debugging enabled, on 64-bit Windows 7 Enterprise SP1, with IE 9 (9.0.8112.16421 with update 9.0.29).
This web app and others I work with have been working just fine for several months, but they all started to misbehave in this manner a few weeks ago. At first, the first time I tried to debug (F5) I'd get the error, but after clearing it and closing the IE window and trying F5 again a second time, the browser would come up just fine. I assumed it was just some glitch, so I tolerated it.
Lately, though it has gotten worse, to the point that 90% of my attempts and re-attempts to debug the web app cause a hung browser and the error. It sometimes works, but most times it doesn't. I have to kill the handing iexplorer.exe processes to clean up my user space, otherwise I eventually get a message about not having enough files to start the browser. I try rebuilding, stopping the ASP.NET Development Server process, even exiting VS2010 and restarting it, but I can't seem to find the magic sequence of events to get it to work.
If I start without debug (Shift-F5), it works, but two IE web browser windows are opened, and both attach to the web app. I don't know if this is related to the first problem. And needless to say, this does not really allow me to debug my code. I tried attaching to either of the IE processes, but I still could not get the debugger to actually debug the executing app. (There is a message about no symbols being loaded for the attached process.)
Most of the solutions for this problem I've found say something about running with administrator access. I cannot do this, however; I work at a large financial company, and developers are not allowed to have local admin rights on our PCs. I don't control system patches, but I can request Help Desk ticket to resolve the problem; but I'd like to resolve this problem myself if it is a fairly simple configuration problem on my part.
Addendum
I should also add that I am not using IIS (because I don't have it installed on my system, and I can't use it anyway because I don't have local admin rights), but instead I am using the built-in Visual Studio Development Server. I've also selected a specific HTTP port number for it to use. Also, all of the directories I'm been using were created by me (as part of my project workspace), so there should be no access permission problems.
Like I said, I can sometimes get a debugging web session started, but most of the time I can't. So whatever is causing this problem, it is probably something intermittent.
This tend to occur when you try to run the full version of IIS rather than the Visual Studio Web Server or IIS Express. Have you tried running IIS Express instead? I think there's support for IIS Express that came with one of the later updates to VS 2010?
IIS proper definitely requires full admin rights in order to attach a debugger because full IIS runs under a system account rather than your own account. IIS Express (as well as the Visual Studio Web Server) however should run under your own user account and so debugging should work on the local machine even with a non-admin account.
One issue that might cause problems is directory permissions. Make sure that the folder where your Web files live are read/execute accessible through the file system for your user account.
Finally make sure you don't have some other instance of a Web service running on the same HTTP port.
I am having the same issue, it works when i don't choose to debug but CTRL+F5 to start it. F5 Debugger al