Quando o modulo principal tenta usar a service action de outro modulo está nos retornando o erro:

"The underlying connection was closed: An unexpected error occurred on a send."

Estou utilizando a versão 11.

Hi Joao,

Apologies as I only speak English.  It is difficult to know with only a small amount of information.  However, this looks to be a network error sending an email.

You might find more information in the email logs in ServiceCentre under Monitoring > Errors and Emails.

Have emails been sending successfully before this error? Has there been any change in the email configuration?

Some things to investigate would be the email service username, password and SMTP port in service centre under Administration > Email, as well as the TLS requirements of your email service.

I hope this helps.

Kind regards,

Stuart

Hi João,

Keep in mind that those service actions are REST's. Looks like the producer cut the connection. on the error log you need to check any error that happen on the module with the service action.

Não te podes esquecer que essas service actions são REST's. E no teu caso parece the o modulo com o service action fechou a conecção. Tens de ir ao error log e procurar por qq erro que tenha acontecido no modulo que tem a service action.

Regards,

Marcelo

Hi Joao, could you share some more information from your Service Center > Monitoring logs?


Boney Sze escreveu:

Olá João, você poderia compartilhar mais informações em seu Centro de serviços> Monitorando logs?



Segue o erro.

Marcelo Ferreira wrote:

Hi João,

Keep in mind that those service actions are REST's. Looks like the producer cut the connection. on the error log you need to check any error that happen on the module with the service action.

Não te podes esquecer que essas service actions são REST's. E no teu caso parece the o modulo com o service action fechou a conecção. Tens de ir ao error log e procurar por qq erro que tenha acontecido no modulo que tem a service action.

Regards,

Marcelo


Não tenho log no modulo que está sendo chamado, pois aparentemente a requisição nao chega nele.

Tenho o log do modulo que usa a service action: 

Stuart Harris wrote:

Hi Joao,

Apologies as I only speak English.  It is difficult to know with only a small amount of information.  However, this looks to be a network error sending an email.

You might find more information in the email logs in ServiceCentre under Monitoring > Errors and Emails.

Have emails been sending successfully before this error? Has there been any change in the email configuration?

Some things to investigate would be the email service username, password and SMTP port in service centre under Administration > Email, as well as the TLS requirements of your email service.

I hope this helps.

Kind regards,

Stuart

Hi,


I'm not using sending emails.

:( 


Hi Joao,

Ok thanks, well it cannot be email then! :)

Could you maybe share more information about when the issue is occurring?  That will help the community diagnose the issue with you.

Kind regards,

Stuart

Hi Joao,

Could you confirm if the service action is being triggered using a timer? Could it be a timeout issue in the timer?

Please provide some explanation also what kind of operations the service action is performing and if there is a huge volume of data being processed?

Kind regards,

Boney

Hi João,

If you debug the service action are you able to reach it? Did you try to other service action on the same module. What is the type of that input variable?

Regards,

Marcelo

Então pessoal, não posso depurar, não estou usando o timer.

Não sei se eles estão usando a versão 11, mas existem Ações de Serviços, e qualquer ServiceAction que eu use retorna esse erro, independentemente do módulo ou aplicativo.

Acredito que possa haver alguma configuração SSL / TLS no servidor, mas não consigo resolvê-lo.

So guys, I can't debug, I'm not using timer.

I don't know if they are using version 11, but there are Services Actions, and any ServiceAction I use returns this error, regardless of module or application.

I believe it may be some SSL / TLS configuration on the server, but I can't solve it.