Dear Support team,
This is an urgent matter !
We have the same incident again on aspose. We have a desclaimer on the generated documents saying “Evaluation Only, Created With ASPOSE.Words…”.
This incident has occurred 3 times this month and again this afternoon.
Please give us more details about this incident, the reasons and the possible solutions to ensure that it does not happen again.
It’s so important and urgent to find a good solution for that.
Can you please provide more details about your licensing setup and how you are currently applying the license in your application?
Thx for response.
We followed the solution that you proposed : Aspose docker - “Evaluation Only” message displayed on generated documents - Free Support Forum - aspose.cloud
Sorry for the inconvenience. It was the billing service failed again. We are investigating changing the implementation to allow more freedom from billing service uptime.
The aspose container restarting fixed the issue.
We need to know more about this incident and the reason why it’s happening. And what is the good solution to avoid that kind of incident to happen again
We are now working on changing the request pipeline to avoid such issues.
Please keep us posted once the solution proposed will be implemented
Yes, as I said in other topic we update you once solution will be ready.
We are currently experiencing a major outage with Aspose. What is going on?? We cannot activate billing on our self-hosted instance or generate your documents on your cloud API.
We need this fixed ASAP .
There was a connectivity issue with DB; the billing work has been restored, and the admin team is analyzing why this happened.
This keeps happening, and switch you Aspose not self hosted and get the following error: Error: ExecuteMailMergeOnline. Exception: Filemanager has not been initialized. => One or more error
Getting silly that you dont return something in the response to say its using evaluation so we can stop it creating anymore.
I’m getting an exception.
"message": "Authorization failed",
"exception": "Aspose\\Words\\ApiException",
Presumably this is connected to this issue and it still appears to be unresolved.
The API is working fine now; I’m waiting for the RCA from the team to share.