EventSourceException in Application Insight - azure-application-insights

I'm getting this exception in Live Metrics Stream.
When I'm debugging locally I can't see any warning or error. Checking the Failure blad also leads to nowhere.
There is no track for this error in my logs.
AI (Internal): [Microsoft-ApplicationInsights-Data]
EventSourceException while processing event "Message":
System.Reflection.TargetException:Non-static method requires a target

This is a known bug in Application Insights. The errors can safely be ignored according to the product team. If you would like to track the status of this issue, you can do so on their Github repo: https://github.com/Microsoft/ApplicationInsights-dotnet-server/issues/850

Related

How to debug or handle Vercel FUNCTION_INVOCATION_FAILED error?

I got this error from Vercel. It pop up at random times and pages when I am navigating. There are no error raised in browser console. Vercel logs only build time error, so no info there also.
Maybe Vercel or Next.js is short in memory? These navigation works mostly, 'function invoication failed' error happens rarely. Like a ghost.
This means there's an error in either getServerSideProps or an API route, which is throwing a 500 on the server. You are correct this isn't shown in the console, because it's not happening on the client side.
Inside Vercel, you can view the Functions tab for real-time logs. Then, hit this error again and you'll be able to see the stack trace. If you can't reproduce it, set up logging with a Log Drain so you can track when it does happen.
https://vercel.com/docs/logs

Corda: Unclear corda error code with a dead link

I came across an error message when running Corda Enterprise. I was able to solve the error. But the link at the end of the error message caught my attention.
[ERROR] 16:28:02+0000 [main] internal.NodeStartupLogging.invoke - Exception during node startup: certificate key must be an instance of java.security.interfaces.RSAPrivateKey or sun.security.mscapi.RSAPrivateKey [errorCode=fnu1lw, moreInformationAt=https://errors.corda.net/ENT/4.0/fnu1lw]
This link is linked to a page that needs a login. And errors.corda.net is a dead link, too. What is the logic behind this link?
When an error occurs, the link that you see will do one of the followings:
try to find a Stack Overflow post that specifically answer to the error code (it is the fnu1lw in your case) and redirect to the page.
take you to the enterprise support site when it can't find a S/O post that is specific to the error code (as it was assumed that Enterprise customers would have a support contract).
Since you are running Corda Enterprise, so it takes you to the login page of Corda enterprise support.

WHat is the cause of "GatewayTimeout" when deploying ARM Templates?

I'm re-deploying an ARM template.
Whereas it worked last night (...) it's failing with:
{
"error": {
"code": "GatewayTimeout",
"message": "The gateway did not receive a response from 'Microsoft.Maps' within the specified time period."
}
}
This in turn causes the deployment to hang (for an hour+).
I'm pretty sure (but not 100%) that I didn't do a change that would cause this -- is this a Microsoft infrastructure problem?
If so, is there an url on Microsoft that provides information as to the status of services, and ETA as to when it would come back online?
If not, any way of getting more verbose error status report to ferret out the underlying cause (by me?). Thanks.
Turned out to be on the Azure Management API side of things, offline for a half day. The service remained up, but management/deployment apis down for a bit.

Firebase Auth error attempting sign-in offline continues even after coming back online

Description
Calling either signInWithRedirect() or signInWithPopup() while offline will throw the expected error O
{code: "auth/network-request-failed", message: "A network error (such as timeout, interrupted connection or unreachable host) has occurred."}.
However, returning online and calling signInWithRedirect() or signInWithPopup() again will throw the same error. Any attempt to call these functions afterwards results in the same error unless the browser is refreshed.
Expected outcome
Auth sign-in functions normally after coming back online
Actual outcome
Auth sing-in throws an error and continues to do so on any following attempts
Steps to reproduce
Go offline Call either signInWithRedirect() or signInWithPopup() (error should be logged here: O {code: "auth/network-request-failed", message: "A network error (such as timeout, interrupted connection or unreachable host) has occurred."})
Go online
Call either signInWithRedirect() or signInWithPopup() (same error occurs on every sign-in attempt
Can anybody provide a solution to this?
firebaser here
We've been able to confirm this behavior with signInWithRedirect(). This is indeed a bug. We'll fix it in an upcoming version.
Update: This should be fixed in version 4.1.3.
This issue appears to take place on Firebase JavaScript SDK 9.5.0 (and potentially with earlier recent releases).
The steps to reproduce are the same as described above. A few additional observations:
If the first call is made to signInWithRedirect, and it fails due to network connection, subsequent calls both to signInWithRedirect and signInWithPopup result in 'auth/network-request-failed' error even after the network connection is restored.
However, if the first call is made to signInWithPopup, and it fails due to network connection, subsequent calls both to signInWithRedirect and signInWithPopup will succeed after the network connection is restored.

Windows workflow suspends intermittently with error in DurableInstancing.InstancesTable

I am facing this error since some time, it is very intermittent in nature so, unable to understand why this error and what needs t be done t fix this.
Issue:
We have a workflow 4.5 WCF service. Everything goes well, but intermittently we see suddenly that a workflow instance gets suspended with an error in the table "DurableInstancing.InstancesTable"
The error is "Keyword Not supported: 'DB Name,1433';Initial Catalog'.
Since most times this ust workd fine without any error, I do not think this problem is related to web.config entry for connectionstring. Most times the workflow completes without any error. We have verified multiple times that the connection string is proper and there is no issue with parsing the connection string.
I suspect this issue is happening while Workflow instance is being recreated from persistence storage, and because some reason it is unable to recreate , the workflow is getting suspended with this error in DB.
I really appreciate any help in getting us through this error.
Thanks,
GD
What we found was it was an issue with permission in Database. We gave "dbo" user permission to the workflow database, and after that we have not seen this problem occur again. Has the error or exception that gets logged in the table is mre informative then it would have been better.
Thanks,
GD

Resources