I'm using the CyberSource API to generate and download reports using the Postman collection.
The issue is when sending a "GET" request to download a report the following error coming back:
<errorBean>
<code>RESOURCE_NOTFOUND</code>
<detail>The requested resource is not found. Please try again later.</detail>
<localizationKey>cybsapi.resource.notfound</localizationKey>
<message>Requested Resource Not Found</message>
</errorBean>
Error when sending a request to download a report:
Success response when asking for the available reports on site:
I used the same environment variables for both requests.
Thanks,
Udi
I experienced a similar issue and had to log in to Cybersource EBC to configure the report subscriptions which were not carried over from the legacy system. It's likely that the error is caused because there is no report for the date you are requesting.
My understanding is that once you have configured the report subscriptions, Cybersource will start to create the report files as per the subscription - usually once daily. So you might only be able to request the report later in the day, or the following day.
Related
The cash summary by branch report is customized report and we can run earlier and the issue is currently happened.
Faced that the issue that is the 500 Internal Server Error when we run the report.
But We have no this server error when run for each month period (Eg- From Date to(11/1/2022), To Date(11/16/2022)) and can't run by year(Eg- From Date(1/1/2018), To Date(11/16/20220). Why is this the case and how to solve it?
enter image description here
enter image description here
enter image description here
We have no this server error when run for each month period (Eg- From Date to(11/1/2022), To Date(11/16/2022)) and can't run by year(Eg- From Date(1/1/2018), To Date(11/16/20220).
Please help to check and let me know any concern
When building the new report, I would set a default values that work, and then be able to use the Preview function. It will execute the report using the default values only during preview.
You can then use that to troubleshoot - start with the base report that works with that range that crashes on the custom report, and then slowly add your changes. You would then find out what change causes the 500 internal server error.
If you have access to the server, you can try using failed request tracing to get additional information on the errors that are not being sent to the web client. Here is a link on how to troubleshoot failed requests: https://learn.microsoft.com/en-us/iis/troubleshoot/using-failed-request-tracing/troubleshooting-failed-requests-using-tracing-in-iis?source=recommendations
We are using Google Composer for workflow orchestration, randomly we are getting An internal server error occurred while authorizing your request. Error code 28 message while opening the web UI. We don't know the cause for this issue. How to fix this?
This issue could be given for users who try to access Airflow UI from certain location. Notice that direct access to the Airflow UI is not supported in Australia, New Zealand, and India as explained here. The product team is working on the resolution. At this moment, the users from these location can use HTTP proxy for that.
Sometimes when we open folder, Alfresco shows spinning wheel and never opens the folder. The log has below exception.
2016-03-08 11:45:40,652 INFO [webscripts.connector.RemoteClient] [http-bio-8080-exec-494] Exception calling (GET) http://localhost:8080/alfresco/s/slingshot/doclib/treenode/site/test/documentLibrary/Books/science?children=true&max=-1&alf_ticket=TICKET_400a73c20348346eed011695af270f837f27a654
2016-03-08 11:45:40,652 INFO [webscripts.connector.RemoteClient] [http-bio-8080-exec-494] Error status 500 null
ClientAbortException: java.net.SocketException: Connection reset
at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:413)
If I curl the above URL or open directly in webrowser I am able to get the json response successfully.
I am using only Alfresco Share and not anyother client. The localhost:8080 is working perfectly fine in most of the cases except this one.
Can anyone please tell me what is the issue and why connection is closed or ClientAbortException exception is occurring?
Mostly this is an issue of timeout and you'll need active monitoring on your Alfresco & Share environment to see how Alfresco is running.
Easy check is to install some java monitoring or use Jmeter to load test the system and see how it responds on different load.
Mostly the outcome is more CPU/RAM for Alfresco :).
As Tahir Malik mentioned above, the issue is related to performance.
The ClientAbort error itself occurs when the client (in this case, Share) times out or the user cancels a download. The message on the log is type INFO. More details here: https://issues.alfresco.com/jira/browse/ALF-20349
If you are on SSO and using Alfresco Enterprise 5.2.3 or 5.2.4, there is a chance that you may hit a similar bug, which is discussed in the Alfresco Forum. However, this particular bug would not show the ClientAbortException.
I have some Domino servers where we run Xpage based applications. I have some issue with some HTTP JVM errors that I can find in the log from time to time can I in anyway get some more debug on the Domino server so that I can see what database this errors is occurring in?:
21-09-2015 11:26:58 HTTP JVM: com.ibm.xsp.webapp.FacesServlet$ExtendedServletException: com.ibm.xsp.FacesExceptionEx: Unable to get document page name for 39BCBE02FB280012C1257CE7006DEF2D
21-09-2015 11:26:58 HTTP JVM: CLFAD0134E: Exception processing XPage request. For more detailed information, please consult error-log-0.xml located in D:/Lotus/Domino/data/domino/workspace/logs
The code is failing on trying to open the XPage associated with the specific document. It's looking to the form and can't find the relevant XPage.
Follow the answer on the question Per links to. Without viewing the logs, there's no way for anyone who does not have access to your server to tell you which database, which Form or which XPage.
I'm looking to get some stats on the parameter retrieval from the HTTP Logs in production. We already get them when we normally execute the reports via the Report Manager or via a url. But when running the report via a schedule (we have them set up in production for the warm ups) nothing is logging....
We also tried a report via schedule in our test env and got no http entries.. :(
Scheduled reports run as SQL Server Agents jobs, so I wouldn't be at all surprised if they don't hit ReportServer, hence no HTTP logs.
Have you looked into querying the execution log? It's got quite detailed information, and will contain entries for every report execution.