I´m invoking https://management.azure.com/subscriptions/{subscriptionId}/providers/Microsoft.DesktopVirtualization/hostPools?api-version=2021-07-12 and randomly fails, returning a "500 Internal Server Error". Is there any way to troubleshoot this obscure error? Any log I can check?
Regards
EDIT: I do not provide the source code because this is not a code issue. This restapi call have been working in prod perfectly for months and, two days ago, suddenly it started to fail returning a 500 error in (more or less) 40% of calls. I would like to check some log or whatever in order to know what is happening on behind.
Azure Virtual Desktop troubleshooting steps are documented here:
https://learn.microsoft.com/en-us/azure/virtual-desktop/troubleshoot-set-up-overview
Not really enough detail in the question to answer anything specific for your environment.
Related
I am very new to development, so I apologize in advance if I am not being clear enough. I appreciate any feedback on the question and how to better pose it.
I'm currently working on an angular app hosted in WSL2. To get it to run locally, this is what I do:
Launch solution in VS Code
From terminal, run npm start
Then, I click on Run and Debug
Once I get the Now listening on: ..... message, I move on to Chrome to start debugging my app
Since this morning, I keep getting a ERR_CONNECTION_REFUSED in the browser, and I'm currently waiting on IT to step in as there could have been some security changes placed that are blocking the requests. Also, I'm not using the VPN.
In the meantime, is there a way to know for sure (or get as close as possible to) what is causing the connection to be refused in my particular scenario? I'm curious about it, but I don't know how to even search the topic properly due to lack of proper terms.
What should one do to at least obtain more details about the issue on their own (perhaps, to help expedite help by collecting important info upfront)? Where my apps are hosted in WSL2, I get very confused between the ip address originating the request and that of the server.
I appreciate any guidance anyone could provide.
It turned out there was a VPN software running where the firewall was ON, even though I was not in the VPN (it went on after I connected to the VPN the previous day). I guess there was nothing else I could have done anyway.
I'm frequently receiving the error There was a problem connecting to your instance when connecting via AWS console. I have a database instance running there and the application connecting to this server for DB service goes down!
This is neither a new instance having a network config error nor this has been purposefully isolated. Considering a day, I am able to connect to this instance for about 10hours, and for the rest, I get this error! So this is definitely not a configuration error.
Any advice/suggestion to debug this further for a permanent fix please? TIA.
Faced this issue multiple times, each time AWS recommends to either upgrade the plan for support and if not, aws recommends to create a new instance, move the contents here and terminate the old one! So I'm actively looking for a solution aswell.
PS: Posting here as answer since I don't have reputation to make comments.
Posting here so that might help someone some day! This is not a solution to the question that I asked, but a work around. I cloned the existing instance to a new instance and monitored both for couple of days. Turns out the new instance worked perfectly while the old one still had the issue.
Probably something with the instance itself.
While am not certainly sure, the AWS mainly comprises of FPGA and there might be some interim issue within it!
Finally terminated the old one! Not a solution, but this work-around works!
This seems like simple question but I have yet to find a clear and recent answer. Here's why I'm looking for this information:
PROBLEM: We load balance 8 web servers and every server hosts the same sites. We sometimes run into situations where a specific user receives errors while doing something and in order to diagnose and correct the problem we need to determine what server the user last connected to. In some cases the issue is reproducible on all servers but in other cases it can only be reproduced on a specific server, which is why we need to find it. Currently, we do the following to find the bad server:
1) Remove all servers from the balancer except one
2) Have the user attempt to reproduce the problem
3) If the problem can't be reproduced, repeat the same process with the next server.
This is time consuming and frustrating to our customers and I'm trying to find a better/faster way of finding the affected server. I've done a lot of reading but so far I've only found one article from back in 2005 (IIS 6) that answers my question:
http://blogs.msdn.com/b/david.wang/archive/2005/10/08/howto-see-who-is-logged-into-iis.aspx
Is what's described in this article still true today, 10 years later?
Thank you for your help!
We've been encountering an issue with a particular website hosted in iis for which I've not managed to get much information from the event log. I'm a bit out of my league with these low level 'raw' diagnostic tools and I'm not if I'm barking up the wrong tree (in which case please tell me - e.g IIS is just broken) or whether I'm following the correct paths to try and locate the issue.
A process serving application pool 'MyWebsite' suffered a fatal communication error with the Windows Process Activation Service. The process id was '4372'. The data field contains the error number.
Running with DebugView open I reliably see these lines when I encounter an issue
[5904] 4692 iisutil!ReadMultiStringParameterValueFromAnyService [helpfunc.cxx # 490]:Inetinfo: Failed reading registry value
[5904]
Error(80070002): The system cannot find the file specified.
I therefore tried installing DebugDiag and looking for any exceptions, which create a number of full dumps for me. Once I've analyzed them I've got a report out the other end shown below, but I'm not sure how to further analyse this. It tells me the type and message were NOT_FOUND and suggests contacting Microsoft. While this is 1 route - I'd like to know if there are further things that can be done before considering that approach:
I managed to find the cause of my problem, a StackOverflowException because a local reproduction was possible and it was quite apparent once the debugger was attatched.
I've therefore got to assume, that StackOverflowExceptions are similar to OutOfMemoryExceptions in that it makes IIS unstable and therefore completely unable to complete running (even to the point of providing/logging exception information).
I'm getting this error: "The server encountered an error while retrieving metrics. Retry the operation." in the dashboard and no Usage overview stats displayed after I've installed and removed a squid proxy server inside an Azure Ubuntu 12.04 server VM.
Anyone know any way to restore them?
I don't think this is related to anything that you've done, I think that MS have having some issues with metrics as I'm getting the same message on instances that I haven't changed.
If it's important for you I would log an issue with MS support.
I have exactly the same error as you. My service instances ran smoothly before this error showed up. And the service instances seem to be still running smoothly even with this error. Only that I cannot get statistics about the instances. It's kind of understandable, since Azure is only CTP now. But I really hops MS will fix this soon.