The issue that caused that error should be in the SQL log. The 'Query failed to run successfully' indicates its a SQL error. Do you have SQL logging turned on?

The only SQL logs are in ewaresql.log am I right ? 

If I am, the SQL logging is effective but I do not have errors related to these webservices errors. 

I suggest running an SQL trace and that might help you catch any errors or at least see what happens before it fails.

Hi.  The SOAP webservices are all managed through the core eware.dll and any SQL transactions will be logged in the ewaresql log.  No other log.

Hi. So there is no other way to get more information about errors ? 

Even using SQL trace suggested by @CRMTogether ?

I would log this as a case with your local Support team.  The Dev team will be able to get to the bottom of where the message originates.

I did what you suggested but everything looks fine SQL side :

The SQL request coming from the webservice request I made looks fine. But the error is still the same :

"mars 31 2022 15:30:56.128 380 3316 1 Exception Caught In DispatchAPI. Message - Query failed to run successfully. ."

I will create a case, thank's for the suggestion.