Using Crystal Reports VS2010. This problem is occurring in production--hosting provided by arvixe. Sometimes when I generate the report I get the Database Logon Failed asp.net error. Sometimes it works just fine. What can I do to fix this so it works 100% of the time? I'm not actually connecting to a database here. Just using ASP.NET objects.
For intermittent errors that are not readily reproducible, comprehensive logging (at multiple places in the code) is a standard solution that can help you isolate the cause.
Related
I'm investigating by days with no results about this exception that my NextJS app is currently throwing, in particular when I try to open a single specific URL:
502: BAD_GATEWAY
Code: NO_STATUS_CODE_FROM_FUNCTION
ID: zrh1:4zx5l-1572269318137-64d401b5d058
Here's the screenshot:
Basically, I have on https://lucacattide.dev/about/en a page that this app should open. This is linked to a MongoDB third-party cloud API platform - Squidex - which is responsible to populate the page itself, via GraphQL queries. The app uses Apollo as GraphQL client. The app instead, is hosted on ZEIT.co serverless cloud, with Now 2.0 version.
During the development process, everything works fine. The page loads up and data is fetched in the right way. Notice that for development, I'm working on now-dev environment instead of a custom Express server, in order to reproduce the production one, as suggested by ZEIT itself.
The exception is being thrown on the production environment - the live one on the hosting platform, not on localhost; the main problem is that no errors are being shown on live logs or local development. So I'm literally going mad in inspecting the possible cause.
I've already tried to test the involved page, by splitting it in sections and trying to exclude child components, or focusing the inspection on the GraphQL query. But the first hasn't produced results and the latter works fine in every environment.
As last try, I deleted and re-created the back-end contents related to that page, because in the past I had a similar issue due to an old GraphQL edited schema that didn't reflected its modifications through the API - so in that case I was still receiving 502 errors. But this time it didn't worked.
Anyone could help me to understand what's going on, please?
Thanks everyone in advance
The issue was caused by an incompatibility between the d3-cloud library and the Now environment.
By replacing it with the react-wordcloud one, the error has been solved.
Thanks everyone for your assistance.
We have an automatic translation Perl script running on a client's server and we noticed that it would occasionally throw an error. The Script simply calls the Microsoft Azure Translation API to translate the data. (Replacing the deprecated Bing Translation API that was used before)
Net::SSL throws the following error:
Net::SSL::die_with_error(LWP::Protocol::https::Socket=GLOB(0x16aff1ec), "read failed")
The strange thing is that this error can't be reproduced, it seems that at some point, one of the calls doesn't return a value at all. (according to Net::SSL the error is thrown when the result of a HTTP request is undefined)
When I run the script just for the data that "caused" the error, it runs normally, so the input data does not seem to be the problem.
The script repeats the call 3 times in 10 second intervals before giving up, so a temporary connection problem seems unlikely as well.
Unfortunately I don't have direct access to the Azure account used and have to believe the partner who manages it, according to them it works normally and should.
I apologize that I can't give any more details. I just would like to know if anybody encountered a similar issue or has some experience with using the Azure Translation API.
We have a SaaS application running with an AngularJS front end and Jasper Reports integrated using the Visualize.js framework. We are seeing an issue where after the Jasper server has been running for a while, the call to get the input controls will stall in the browser. The strange thing is that all the other calls proceeding it (auth, resourcessearch, etc.) return just fine. It seems to be only the inputcontrols that stalls. When this happens, we see no errors in the logs, memory & CPU on the Jasper server are fine, etc. To fix the problem, we are generally forced to bounce the Jasper server.
Has anyone experienced this problem? Any advice?
A little more info:
Jasper Professional version 6.1.1
Seeing the problem in all supported browsers (IE, Firefox, Chrome)
Problem happens both with a single user and with concurrent users
Input controls will sometimes return after 8-10 MINUTES if we wait
long enough (with Apache timeout cranked to 15 minutes)
I have a report in SSRS with "Data-driven Subscription" , but sometimes there is errors like below
Done: 10 processed of 10 total; 10 errors.
and the reason of these errors I think network problems, ssrs can't store pdf in the network folder.
So I need a way to handle any error that happened in this stage to be able to retry again, or at least to know witch reports not generated correctly,
any Idea how can I handle these errors?
There is no technique to error capture, you just have to carefully adjust the paremeters if you have them in the report.
I have many years experience in making these statements, and in the beginning I had a similar problem but I solved it
I have my script email me when there is a problem creating a recurring transaction with authorize.net. I received the following at 5:23AM Pacific time:
SOAP-ERROR: Parsing
WSDL: Couldn't load from 'https://api.authorize.net/soap/v1/service.asmx?wsdl' :
failed to load external entity "https://api.authorize.net/soap/v1/service.asmx?wsdl"
And of course, when I did exactly the same thing that the user did, it worked fine for me.
Does this mean authorize.net's API is down? Their knowledge base simply sucks and provides no information whatsoever about this problem. I've contacted the company, but I'm not holding my breath for a response. Google reveals nothing. Looking through their code, nothing stands out. Maybe an authentication error?
Has anyone seen an error like this before? What causes this?
Maybe as a back up you can cache the WSDL file locally and in case of network issues use the local copy. I doubt it changes often so if you refresh it weekly that should be satisfactory as the file will probably not be stale by then.