Aspose on premise approach giving red message boxes in converted pdf

Aspose.Words Cloud Product Family
1

Hi team,

We are using on premise approach for converting docx to pdf. Yesterday, we started seeing red message boxes in the converted pdfs in production. Our credits were not completely utilized as can be seen from the ss attached below. We use aspose words on premise approach, docker image: docker.io/aspose/words-cloud:24.9

Adding the logs below for the pods. This was resolved by redeploying the pods but it shouldn’t have happened in the first place as we didn’t exceed our credit limit. Please get it checked.

image.jpg (129.1 KB)

image.jpg (222.2 KB)

In other pod, we were seeing below logs:
asposeforcloud6fbd614989c44e879a4e2a06d4b61ded, YgU0L8YBX6UAIPrzOHhjqKexsAiiJqtaEcdqRflJlLZT695VgeHdNGZZNu6xDpT2APptWzKVeqgaaJxbno0iAAzMS87C0jVWWtqJjMlX69cmAsQSFKhLKZjHKlZtxwp1EZFlMotzQBMjdgaPFyuJGnwIMotbldLdU-sP*-GxY_
Metered license is set
Credit: 21
Consumption quantity: 2.4610
LicenseInitializer:InitLicense() - Metered license for Aspose.Barcode successfully initialized.
Hosting environment: Production
Content root path: /app
Now listening on: [http://%5B::%5D:80]http://[::]:80
Application started. Press Ctrl+C to shut down.
fail: Aspose.Words.Cloud.WebApp.Filters.CoreResultExceptionFilter[0]
api exception
Aspose.Words.Cloud.Exceptions.WordsApiException: Error while loading file ‘Air Invoice - Foreign Rev1 Test.docx-c709ed77a9cb23ad-rexfqf.docx’ from storage: Unexpected end of file has occurred. The following elements are not closed: w:tbl, w:body, w:document. Line 2, position 98624.
—> System.Xml.XmlException: Unexpected end of file has occurred. The following elements are not closed: w:tbl, w:body, w:document. Line 2, position 98624.
at Aspose.Words.Document.M3(Stream d, LoadOptions v)
at Aspose.Words.Cloud.Business.DocumentCore…(Stream )
at Aspose.Words.Cloud.Storage.FileManagerExtensions.LoadDocument[T](IFileManager , String, Func2 ) --- End of inner exception stack trace --- at Aspose.Words.Cloud.Storage.FileManagerExtensions.LoadDocument[T](IFileManager , String, Func2 )
at Aspose.Words.Cloud.Business.DocumentCore.LoadDocument(String , Boolean&, Int64& , FileFormatInfo& , Boolean )
at Aspose.Words.Cloud.Business.WordsDocument.()
at Aspose.Words.Cloud.WordsApiController.GetWordsDocument(IFileManager fileManager, String path, Boolean convertMetafilesToPng, String encryptedPassword, String password, Boolean forceSpecifiedPassword)
at Aspose.Words.Cloud.DocumentActions.Convert.ConvertController…MoveNext()
— End of stack trace from previous location —

PLEASE NOTE: THIS IS A REPEATED ISSUE. OUR BUSINESS IS SERIOUSLY BEING IMPACTED.

2

Sorry for the inconvenience. In the 24.11 docker hub version, we will introduce a new field in the words/info endpoint, showing whether the license is set. Also, in the docker hub version, such an error may occur if the container can’t send data to the billing for 24 hours.

3

Hi. Any idea how can we avoid for future? And also, how did it got fixed after redeploying the aspose words pods?

4

You can set up a health check for your container to check if a license is okay when the container has already started, there is an API method to check information about the license. The URL is GET https://customeraddress.com /v4.0/words/info. It requires an authorization token, so we must first obtain it by /connect/token URL.
result will be like this:
{
“Name”: “Aspose.Words Cloud API”,
“Version”: “24.9.0”,
“AdditionalInfo”: [
{
“Key”: “ConsumptionCredit”,
“Value”: “0”
},
{
“Key”: “ConsumptionQuantity”,
“Value”: “0.0498”
}
],
“RequestId”: “77362525-9fc9-401c-af80-7aa550ee728f”
}
In this method, we will add the IsMeteredLicensed field along with “ConsumptionQuantity” so you can check this new field if it is False, your container failed to send data to billing for the previous 24 hours, and you should restart the container.

5

hi. Thanks for this suggestion. But question is, how come it suddenly stopped sending data like it’s running fine for almost a month. Is it a known issue?

6

There were a couple of times when customers observed the same behavior, and our billing team found out that it happened because the container didn’t send data; I will contact them to check the billing logs for your account.

1 Like
7

Thank you for your prompt response.