HTTP 500 errors

Aspose.PDF Product Family
1

Something is wrong with your servers. For the past 15 or more hours, we’ve been getting 500 errors at various spots in our PDF generation. We are long time users. It happens at a different point in the code each time(so its not our end), but it has happened to every attempt at some point, so my document still hasn’t been created. Sometimes it’s an error for a “PUT” and other times its a “DELETE”. Here are a few examples of the 100+ that have occurred.

Example 1)
Aspose\PDF\ApiException: [500] Server error: PUT [https://api.aspose.cloud/v3.0/pdf/51259e6feb_Agent%20Data%20Form_edited_101123.pdf/import/xml?xmlFilePath=%2Fworking%2Fxml%2F51259e6feb.xml&storage=affiliation&folder=working](https://api.aspose.cloud/v3.0/pdf/51259e6feb_Agent%20Data%20Form_edited_101123.pdf/import/xml?xmlFilePath=%2Fworking%2Fxml%2F51259e6feb.xml&storage=affiliation&folder=working) resulted in a 500 Internal Server Error response:
{“RequestId”:“7a2ed54fafaae4677590825f74bf3e15”,“Error”:{“Code”:“internalError”,“Message”:“One or more errors occurred.” (truncated…)
in /var/www/aspose-pdf-cloud-php/src/Aspose/PDF/Api/PdfApi.php on line 91460

Example2)
Aspose\PDF\ApiException: [500] Server error: DELETE [https://api.aspose.cloud/v3.0/pdf/storage/file/working/51259e6feb_Business%20Essentials%20Fee%20form.pdf](https://api.aspose.cloud/v3.0/pdf/storage/file/working/51259e6feb_Business%20Essentials%20Fee%20form.pdf) resulted in a 500 Internal Server Error response:
{“RequestId”:“1ca908e564a1501f874cab640dfc8552”,“Error”:{“Code”:“internalError”,“Message”:"The remote name could not be (truncated…)
in /var/www/aspose-pdf-cloud-php/src/Aspose/PDF/Api/PdfApi.php on line 3529

Example 3)
Aspose\PDF\ApiException: [500] Server error: PUT [https://api.aspose.cloud/v3.0/pdf/51259e6feb_credit_card_auth_101123.pdf/import/xml?xmlFilePath=%2Fworking%2Fxml%2F51259e6feb.xml&storage=affiliation&folder=working](https://api.aspose.cloud/v3.0/pdf/51259e6feb_credit_card_auth_101123.pdf/import/xml?xmlFilePath=%2Fworking%2Fxml%2F51259e6feb.xml&storage=affiliation&folder=working) resulted in a 500 Internal Server Error response:
{“RequestId”:“13c6f4ef7846ab88e084c680ccb38c92”,“Error”:{“Code”:“internalError”,“Message”:“One or more errors occurred.” (truncated…)
in /var/www/aspose-pdf-cloud-php/src/Aspose/PDF/Api/PdfApi.php on line 91460

2

@pfrworksite

It seems you are encountering HTTP 500 Internal Server Errors while using the Aspose PDF API for document generation. This type of error typically indicates a problem on the server side rather than an issue with your code. Here are a few steps you can take to troubleshoot and potentially resolve the issue:

  1. Check Server Status: Sometimes, server issues can be temporary. Check the Aspose service status page or forums to see if there are any ongoing outages or maintenance activities.

  2. Review API Usage: Ensure that you are using the API correctly. Double-check the parameters you are sending in your requests, such as file paths and storage options. Incorrect parameters can sometimes lead to server errors.

  3. Error Details: The error messages you provided indicate that the server encountered an internal error while processing your requests. It might be helpful to capture the full error response (if available) to provide more context when seeking support.

  4. Sample Application: If the issue persists, consider creating a minimal reproducible example of your code that demonstrates the problem. This can help in diagnosing the issue more effectively.

  5. Contact Support: If you continue to experience these errors, it may be beneficial to reach out to Aspose support directly. Provide them with the error details, your API usage, and any relevant code snippets. This will help them investigate the issue on their end.

In previous discussions, users have found that sharing detailed information about their server environment and the specific errors they encounter can lead to quicker resolutions. If you have not done so already, consider providing this information when seeking assistance.

If you need further help, feel free to ask!

3

This can be closed. You resolved it around the 24 hour mark.

4