Problema Com Driver E-mail

#1

Utilizo o driver E-mail para mandar alarmes das minhas aplicações.
Os alertas são enviados para uma lista de e-mail.
Tenho um problema que toda vez que o servidor do Elipse ou o serviço do Elipse é restartado, o driver gera um erro e não manda o e-mail.
Para solucionar o problema, sou obrigado a encaminhar para um único destinatário e depois disso posso alterar o destinatário para a lista.

Consegui capturar o seguinte log:

16/04/2018 18:03:02.286 (2248) TAG Tag(0.0.0.0).Validate = SUCCESS (type=10;flags=8)
16/04/2018 18:03:02.286 (2248) TAG ==> (0.000) Tag(0.0.0.0).WriteValue (20; 08:32:20.779) ‘walace.ferreira@ascenty.com, ferreira.walace@gmail.com’ = SUCCESS
16/04/2018 18:03:02.286 (2248) TAG <== (0.000) Tag(0.0.0.0).ReadValue = (18:03:02.286) ‘walace.ferreira@ascenty.com,ferreira.walace@gmail.com’
16/04/2018 18:03:02.286 (2248) TAG Tag(0.1.0.0).Validate = SUCCESS (type=10;flags=8)
16/04/2018 18:03:02.286 (2248) TAG ==> (0.000) Tag(0.1.0.0).WriteValue (20; 08:32:20.779) ’ = SUCCESS
16/04/2018 18:03:02.286 (2248) TAG <== (0.000) Tag(0.1.0.0).ReadValue = (18:03:02.286)
16/04/2018 18:03:02.302 (2248) TAG ==> (0.000) Tag(0.0.0.0).WriteValue (1970.01.01 00:00:00) null = SUCCESS
16/04/2018 18:03:02.302 (2248) TAG <== (0.000) Tag(0.0.0.0).ReadValue = (18:03:02.302) ‘’
16/04/2018 18:03:02.318 (2248) TAG ==> (0.000) Tag(0.1.0.0).WriteValue (1970.01.01 00:00:00) null = SUCCESS
16/04/2018 18:03:02.318 (2248) TAG <== (0.000) Tag(0.1.0.0).ReadValue = (18:03:02.318) ‘’
16/04/2018 18:03:02.568 (2248) TAG ==> (0.000) Tag(5.0.0.0).WriteValue (18:03:02.568) ‘bms.htl@ascenty.com’ = SUCCESS
16/04/2018 18:03:02.568 (2248) TAG ==> (0.000) Tag(6.0.0.0).WriteValue (18:03:02.568) ‘acesso@123’ = SUCCESS
16/04/2018 18:03:02.568 (2248) TAG ==> (0.000) Tag(1.0.0.0).WriteValue (18:03:02.568) ‘ALARME BMS - HORTOLÂNDIA | CATEGORIA: ELÉTRICA’ = SUCCESS
16/04/2018 18:03:02.568 (2248) TAG <== (0.000) Tag(1.0.0.0).ReadValue = (18:03:02.568) ‘ALARME BMS - HORTOLÂNDIA | CATEGORIA: ELÉTRICA’
16/04/2018 18:03:02.568 (2248) TAG ==> (0.000) Tag(2.0.0.0).WriteValue (18:03:02.568) ‘MENSAGEM: DRUPS 1-A EM EMERGENCY MODE | MESSAGE: DRUPS 1-A ON EMERGENCY MODE’ = SUCCESS
16/04/2018 18:03:02.568 (2248) TAG <== (0.000) Tag(2.0.0.0).ReadValue = (18:03:02.568) ‘MENSAGEM: DRUPS 1-A EM EMERGENCY MODE | MESSAGE: DRUPS 1-A ON EMERGENCY MODE’
16/04/2018 18:03:02.568 (2248) DRIVER Socket created with success!
16/04/2018 18:03:02.568 (2248) DRIVER Connecting in host smtp.office365.com port 587
16/04/2018 18:03:02.599 (2248) DRIVER Socket connected with success!
16/04/2018 18:03:02.599 (2248) DRIVER Elipse connected to Mail Server
16/04/2018 18:03:02.599 (2248) IO RX: 220 CP2P215CA0003.outlook.office365.com Microsoft ESMTP MAIL Service ready at Mon, 16 Apr 2018 21:03:03 +0000[0D][0A]
16/04/2018 18:03:02.599 (2248) IO TX: EHLO BMS-HTL-01.ascenty.local[0D][0A]
16/04/2018 18:03:02.615 (2248) IO RX: 250-CP2P215CA0003.outlook.office365.com Hello [177.185.4.151][0D][0A]250-SIZE 157286400[0D][0A]250-PIPELINING[0D][0A]250-DSN[0D][0A]250-ENHANCEDSTATUSCODES[0D][0A]250-STARTTLS[0D][0A]250-8BITMIME[0D][0A]250-BINARYMIME[0D][0A]250-CHUNKING[0D][0A]250 SMTPUTF8[0D][0A]
16/04/2018 18:03:02.615 (2248) DRIVER OK: Authentication Method: STARTTLS
16/04/2018 18:03:02.615 (2248) IO TX: STARTTLS[0D][0A]
16/04/2018 18:03:02.615 (2248) IO RX: 220 2.0.0 SMTP server ready[0D][0A]
16/04/2018 18:03:02.646 (2248) DRIVER OK: Security SSL/TLS connection is enabled!!
16/04/2018 18:03:02.646 (2248) IO TX: EHLO BMS-HTL-01.ascenty.local[0D][0A]
16/04/2018 18:03:02.646 (2248) IO RX: 250-CP2P215CA0003.outlook.office365.com Hello [177.185.4.151][0D][0A]250-SIZE 157286400[0D][0A]250-PIPELINING[0D][0A]250-DSN[0D][0A]250-ENHANCEDSTATUSCODES[0D][0A]250-AUTH LOGIN XOAUTH2[0D][0A]250-8BITMIME[0D][0A]250-BINARYMIME[0D][0A]250-CHUNKING[0D][0A]250 SMTPUTF8[0D][0A]
16/04/2018 18:03:02.646 (2248) DRIVER OK: Authentication Method: AUTH LOGIN
16/04/2018 18:03:02.646 (2248) IO TX: AUTH LOGIN[0D][0A]
16/04/2018 18:03:02.646 (2248) IO RX: 334 VXNlcm5hbWU6[0D][0A]
16/04/2018 18:03:02.646 (2248) IO TX: Ym1zLmh0bEBhc2NlbnR5LmNvbQ==[0D][0A]
16/04/2018 18:03:02.661 (2248) IO RX: 334 UGFzc3dvcmQ6[0D][0A]
16/04/2018 18:03:02.661 (2248) IO TX: YWNlc3NvQDEyMw==[0D][0A]
16/04/2018 18:03:06.865 (2248) IO RX: 235 2.7.0 Authentication successful target host FR1PR80MB0742.lamprd80.prod.outlook.com[0D][0A]
16/04/2018 18:03:06.865 (2248) DRIVER OK: Authentication successful
16/04/2018 18:03:06.865 (2248) IO TX: MAIL FROM:bms.htl@ascenty.com[0D][0A]
16/04/2018 18:03:07.068 (2248) IO RX: 250 2.1.0 Sender OK[0D][0A]
16/04/2018 18:03:07.068 (2248) IO TX: DATA[0D][0A]
16/04/2018 18:03:12.131 (2248) IO RX: 503 5.5.2 Need rcpt command [FR1PR80MB0742.lamprd80.prod.outlook.com][0D][0A]
16/04/2018 18:03:12.131 (2248) DRIVER Receive() error: Received a Negative Completion reply - SMTP code = 503
16/04/2018 18:03:12.131 (2248) DRIVER Last sent message was DATA
16/04/2018 18:03:12.131 (2248) IO TX: QUIT[0D][0A]
16/04/2018 18:03:12.193 (2248) IO RX: 221 2.0.0 Service closing transmission channel[0D][0A]
16/04/2018 18:03:12.193 (2248) DRIVER Elipse disconnected from Mail Server
16/04/2018 18:03:12.193 (2248) DRIVER SSLDisconnect() error: SSL_shutdown() failed:
16/04/2018 18:03:12.193 (2248) DRIVER OK: Security SSL/TLS connection is disabled!!
16/04/2018 18:03:12.193 (2248) DRIVER Socket closed with success!
16/04/2018 18:03:12.193 (2248) DRIVER Email couldn’t be sent
16/04/2018 18:03:12.193 (2248) TAG ==> (9.615) Tag(3.0.0.0).WriteValue (18:03:02.568) 1 = ERROR (hr=80004005)
16/04/2018 18:03:12.193 (2248) TAG ==> (0.000) Tag(5.0.0.0).WriteValue (18:03:12.193) ‘bms.htl@ascenty.com’ = SUCCESS
16/04/2018 18:03:12.193 (2248) TAG ==> (0.000) Tag(6.0.0.0).WriteValue (18:03:12.193) ‘acesso@123’ = SUCCESS
16/04/2018 18:03:12.193 (2248) TAG ==> (0.000) Tag(1.0.0.0).WriteValue (18:03:12.193) ‘ALARME BMS - HORTOLÂNDIA | CATEGORIA: ELÉTRICA’ = SUCCESS
16/04/2018 18:03:12.193 (2248) TAG <== (0.000) Tag(1.0.0.0).ReadValue = (18:03:12.193) ‘ALARME BMS - HORTOLÂNDIA | CATEGORIA: ELÉTRICA’
16/04/2018 18:03:12.193 (2248) TAG ==> (0.000) Tag(2.0.0.0).WriteValue (18:03:12.193) ‘MENSAGEM: DRUPS 1-A EM EMERGENCY MODE | MESSAGE: DRUPS 1-A ON EMERGENCY MODE’ = SUCCESS
16/04/2018 18:03:12.193 (2248) TAG <== (0.000) Tag(2.0.0.0).ReadValue = (18:03:12.193) ‘MENSAGEM: DRUPS 1-A EM EMERGENCY MODE | MESSAGE: DRUPS 1-A ON EMERGENCY MODE’
16/04/2018 18:03:12.193 (2248) DRIVER Socket created with success!
16/04/2018 18:03:12.193 (2248) DRIVER Connecting in host smtp.office365.com port 587
16/04/2018 18:03:12.193 (2248) DRIVER Socket connected with success!
16/04/2018 18:03:12.193 (2248) DRIVER Elipse connected to Mail Server
16/04/2018 18:03:12.209 (2248) IO RX: 220 CP2P215CA0001.outlook.office365.com Microsoft ESMTP MAIL Service ready at Mon, 16 Apr 2018 21:03:12 +0000[0D][0A]
16/04/2018 18:03:12.209 (2248) IO TX: EHLO BMS-HTL-01.ascenty.local[0D][0A]
16/04/2018 18:03:12.224 (2248) IO RX: 250-CP2P215CA0001.outlook.office365.com Hello [177.185.4.151][0D][0A]250-SIZE 157286400[0D][0A]250-PIPELINING[0D][0A]250-DSN[0D][0A]250-ENHANCEDSTATUSCODES[0D][0A]250-STARTTLS[0D][0A]250-8BITMIME[0D][0A]250-BINARYMIME[0D][0A]250-CHUNKING[0D][0A]250 SMTPUTF8[0D][0A]
16/04/2018 18:03:12.224 (2248) DRIVER OK: Authentication Method: STARTTLS
16/04/2018 18:03:12.224 (2248) IO TX: STARTTLS[0D][0A]
16/04/2018 18:03:12.224 (2248) IO RX: 220 2.0.0 SMTP server ready[0D][0A]
16/04/2018 18:03:12.271 (2248) DRIVER OK: Security SSL/TLS connection is enabled!!
16/04/2018 18:03:12.271 (2248) IO TX: EHLO BMS-HTL-01.ascenty.local[0D][0A]
16/04/2018 18:03:12.287 (2248) IO RX: 250-CP2P215CA0001.outlook.office365.com Hello [177.185.4.151][0D][0A]250-SIZE 157286400[0D][0A]250-PIPELINING[0D][0A]250-DSN[0D][0A]250-ENHANCEDSTATUSCODES[0D][0A]250-AUTH LOGIN XOAUTH2[0D][0A]250-8BITMIME[0D][0A]250-BINARYMIME[0D][0A]250-CHUNKING[0D][0A]250 SMTPUTF8[0D][0A]
16/04/2018 18:03:12.287 (2248) DRIVER OK: Authentication Method: AUTH LOGIN
16/04/2018 18:03:12.287 (2248) IO TX: AUTH LOGIN[0D][0A]
16/04/2018 18:03:12.287 (2248) IO RX: 334 VXNlcm5hbWU6[0D][0A]
16/04/2018 18:03:12.287 (2248) IO TX: Ym1zLmh0bEBhc2NlbnR5LmNvbQ==[0D][0A]
16/04/2018 18:03:12.303 (2248) IO RX: 334 UGFzc3dvcmQ6[0D][0A]
16/04/2018 18:03:12.303 (2248) IO TX: YWNlc3NvQDEyMw==[0D][0A]
16/04/2018 18:03:16.912 (2248) IO RX: 235 2.7.0 Authentication successful target host CP2PR80MB0738.lamprd80.prod.outlook.com[0D][0A]
16/04/2018 18:03:16.912 (2248) DRIVER OK: Authentication successful
16/04/2018 18:03:16.912 (2248) IO TX: MAIL FROM:bms.htl@ascenty.com[0D][0A]
16/04/2018 18:03:16.943 (2248) IO RX: 250 2.1.0 Sender OK[0D][0A]
16/04/2018 18:03:16.943 (2248) IO TX: DATA[0D][0A]
16/04/2018 18:03:21.959 (2248) IO RX: 503 5.5.2 Need rcpt command [CP2PR80MB0738.lamprd80.prod.outlook.com][0D][0A]
16/04/2018 18:03:21.959 (2248) DRIVER Receive() error: Received a Negative Completion reply - SMTP code = 503
16/04/2018 18:03:21.959 (2248) DRIVER Last sent message was DATA
16/04/2018 18:03:21.959 (2248) IO TX: QUIT[0D][0A]
16/04/2018 18:03:21.959 (2248) IO RX: 221 2.0.0 Service closing transmission channel[0D][0A]
16/04/2018 18:03:21.959 (2248) DRIVER Elipse disconnected from Mail Server
16/04/2018 18:03:21.959 (2248) DRIVER SSLDisconnect() error: SSL_shutdown() failed:
16/04/2018 18:03:21.959 (2248) DRIVER OK: Security SSL/TLS connection is disabled!!
16/04/2018 18:03:21.959 (2248) DRIVER Socket closed with success!
16/04/2018 18:03:21.959 (2248) DRIVER Email couldn’t be sent

#2

@Walace, bom dia.

Conforme observou, parece que há um erro no endereçamento do receptor (destinatário).

No início do log tem estas linhas, onde:

  1. Aqui ocorreu tudo bem:
  1. Logo depois foi lido novamente e retornou vazio:
  1. Aqui retorna o erro 503 [(Bad sequence of commands)]
    (https://www.greenend.org.uk/rjk/tech/smtpreplies.html#RCPT):

Por favor, para análise inicial, poderia dar mais detalhes de como está inserindo o valor na tag destinatário ou compartilhar o script que utilizou para enviar o e-mail?

Sds.

EDIT 1: Se estiver utilizando a versão nova do driver (v2.0.10) no E3, pode-se configurar uma tag com o N1 = 90 e associar a um display na tela.
Sempre que alguma escrita for feita em qualquer tag do driver Sendmail, a tag retornará um código. Este código poderá indicar um erro ou sucesso na escrita da tag (verificar manual do driver em “Códigos de Erros para Tags de Escrita”).

#3

Boa tarde,
Segue o código abaixo.

O erro que dá é o 503, bad sequence of events.

Segue o código:
Sub Alarme_alarme()

Application.GetObject(“EMAIL.USUARIO”).Value = "bms.htl@ascenty.com"
Application.GetObject(“EMAIL.SENHA”).Value = “XXXXXX”
Application.GetObject(“EMAIL.ASSUNTO”).Value = “ALARME BMS - HORTOLÂNDIA | CATEGORIA: HVAC”
Application.GetObject(“EMAIL.CORPO”).Value = “MENSAGEM: ALARME NO CHILLER - 01”

Application.GetObject(“EMAIL.PRIORIDADE”).Value = 1

End Sub

#4

@Walace, bom dia.

Neste script falta o destinatário. Como está inserindo o destinatário (fixo, setpoint, etc)?

Sds.

#5

Fernado,

Escrevo em um tag interno e no tag do driver faço uma conexão simples para este tag interno.

#6

@Walace, bom dia.

Obrigado pelo retorno.

No caso de reiniciar o servidor de aplicação, isto ocorre pois o tag interno perde o valor caso não tenha um Save() configurado nos scripts dele.

Entretanto, nos logs acima, caso o servidor não tenha “caído”, parece que o valor foi “retirado”.

Realizei alguns testes (tanto escrevendo no tag interno ou direto no tag de comunicação quanto por scripts) e não consegui reproduzir o problema de enviar os emails em lista após reiniciar o servidor.

Uma sugestão de teste seria escrevendo o e-mail do destinatário script do alarme:

Sub Alarme_alarme()

Application.GetObject(“EMAIL.PARA”).WriteEx "walace.ferreira@ascenty.com, ferreira.walace@gmail.com"

Application.GetObject(“EMAIL.USUARIO”).WriteEx "bms.htl@ascenty.com"
Application.GetObject(“EMAIL.SENHA”).WriteEx “XXXXXX”
Application.GetObject(“EMAIL.ASSUNTO”).WriteEx “ALARME BMS - HORTOLÂNDIA | CATEGORIA: HVAC”
Application.GetObject(“EMAIL.CORPO”).WriteEx “MENSAGEM: ALARME NO CHILLER - 01”

Application.GetObject(“EMAIL.PRIORIDADE”).WriteEx 1

End Sub

Obs.: Se possível, compartilhar os logs do driver novamente após o teste e, caso não funcione, a aplicação.

Sds.

#7

Bom dia, estou tendo problemas no envio de emails. Meu servidor exige autenticação. Segue os dados:

O usuário e endereço SMTP insere na tela de configuração;
Application.GetObject(“EnvioEmail.SenhaRemetente”).WriteEx “XXXX”

Application.GetObject(“EnvioEmail.PortaSMTP”).WriteEx 25

Application.GetObject(“EnvioEmail.Destinatario”).WriteEx “jesse.ti@grupoherculano.com.br”

Application.GetObject(“EnvioEmail.Assunto”).WriteEx “Teste Assunto”

Application.GetObject(“EnvioEmail.Mensagem”).WriteEx “Mensagem”

Application.GetObject(“EnvioEmail.Enviar”).WriteEx 1

Erro no log:

08/12/2021 09:40:36.519 (2C14) DRIVER Driver name: Driver ELIPSE SendMail v2.0.12 (IOKitLib v2.0.110)
08/12/2021 09:40:36.519 (2C14) DRIVER IOKitLib version 2.0.110 of Sep 11 2019 09:59:23
08/12/2021 09:40:36.621 (2C14) DRIVER OpenSSL context created with success!
08/12/2021 09:40:36.621 (2C14) DRIVER OpenSSL created with success!
08/12/2021 09:40:36.621 (2C14) DRIVER WSAStartup processed with success!
08/12/2021 09:40:36.621 (2C14) DRIVER drvStartComm(25,0,0,0)
08/12/2021 09:40:36.621 (2C14) DRIVER Current configuration (21 parameters):
08/12/2021 09:40:36.621 (2C14) DRIVER - IO.GiveUpTries = 1
08/12/2021 09:40:36.621 (2C14) DRIVER - IO.Log.Enable = 1
08/12/2021 09:40:36.621 (2C14) DRIVER - IO.Log.Filename = ‘C:\eeLogs\SendMail_%DATE%.log’
08/12/2021 09:40:36.621 (2C14) DRIVER - IO.RecoverEnable = 1
08/12/2021 09:40:36.621 (2C14) DRIVER - IO.RecoverPeriodSec = 20
08/12/2021 09:40:36.621 (2C14) DRIVER - IO.Serial.Baudrate = 9600
08/12/2021 09:40:36.621 (2C14) DRIVER - IO.Serial.DataBits = 8
08/12/2021 09:40:36.621 (2C14) DRIVER - IO.Serial.Port = 1
08/12/2021 09:40:36.621 (2C14) DRIVER - IO.TimeoutMs = 3000
08/12/2021 09:40:36.621 (2C14) DRIVER - IO.Type = ‘None’
08/12/2021 09:40:36.621 (2C14) DRIVER - SendMail.EmailAddress = ‘supervisorio@grupoherculano.com.br’
08/12/2021 09:40:36.621 (2C14) DRIVER - SendMail.SmtpServer = ‘200.209.137.131’
08/12/2021 09:40:36.621 (2C14) DRIVER - SendMail.UserName = ‘Envio Email’
08/12/2021 09:40:36.621 (2C14) DRIVER - 8 parameters with value = 0 were omitted
08/12/2021 09:40:36.621 (2C14) DRIVER I/O Interface was configured as ‘NONE’, the driver is OFFLINE!!!
08/12/2021 09:43:42.022 (2C14) TAG Tag(6.0.0.0).Validate = SUCCESS (type=10;flags=8)
08/12/2021 09:43:42.022 (2C14) TAG ==> (0.000) Tag(6.0.0.0).WriteValue (09:43:42.021) ‘@Senha@’ = SUCCESS
08/12/2021 09:43:42.022 (2C14) DRIVER Invalid N1=6 parameter - ProcessTagReading() error
08/12/2021 09:43:42.022 (2C14) TAG <== (0.000) Tag(6.0.0.0).ReadValue = ERROR (hr=8004E008)
08/12/2021 09:43:42.023 (2C14) TAG Tag(10.0.0.0).Validate = SUCCESS (type=10;flags=8)
08/12/2021 09:43:42.023 (2C14) TAG ==> (0.000) Tag(10.0.0.0).WriteValue (09:43:42.022) 25 = SUCCESS
08/12/2021 09:43:42.023 (2C14) TAG <== (0.000) Tag(10.0.0.0).ReadValue = (09:43:42.023) 25
08/12/2021 09:43:42.023 (2C14) TAG Tag(0.0.0.0).Validate = SUCCESS (type=10;flags=8)
08/12/2021 09:43:42.023 (2C14) TAG ==> (0.000) Tag(0.0.0.0).WriteValue (09:43:42.023) ‘jesse.ti@grupoherculano.com.br’ = SUCCESS
08/12/2021 09:43:42.023 (2C14) TAG <== (0.000) Tag(0.0.0.0).ReadValue = (09:43:42.023) ‘jesse.ti@grupoherculano.com.br’
08/12/2021 09:43:42.024 (2C14) TAG Tag(1.0.0.0).Validate = SUCCESS (type=10;flags=8)
08/12/2021 09:43:42.024 (2C14) TAG ==> (0.000) Tag(1.0.0.0).WriteValue (09:43:42.024) ‘Teste Assunto’ = SUCCESS
08/12/2021 09:43:42.024 (2C14) TAG <== (0.000) Tag(1.0.0.0).ReadValue = (09:43:42.024) ‘Teste Assunto’
08/12/2021 09:43:42.025 (2C14) TAG Tag(2.0.0.0).Validate = SUCCESS (type=10;flags=8)
08/12/2021 09:43:42.025 (2C14) TAG ==> (0.000) Tag(2.0.0.0).WriteValue (09:43:42.024) ‘Mensagem’ = SUCCESS
08/12/2021 09:43:42.025 (2C14) TAG <== (0.000) Tag(2.0.0.0).ReadValue = (09:43:42.025) ‘Mensagem’
08/12/2021 09:43:42.025 (2C14) TAG Tag(3.0.0.0).Validate = SUCCESS (type=10;flags=8)
08/12/2021 09:43:42.025 (2C14) DRIVER Write type mismatch. Expected Numeric data - ProcessTagWriting() error: Failed v.Get(byPriority)
08/12/2021 09:43:42.025 (2C14) TAG ==> (0.000) Tag(3.0.0.0).WriteValue (09:43:42.025) ‘1’ = ERROR (hr=80070057) (status = (09:40:36.516) 1000200)
08/12/2021 09:46:14.021 (2C14) TAG ==> (0.000) Tag(6.0.0.0).WriteValue (09:46:14.020) ‘XXXXX’ = SUCCESS
08/12/2021 09:46:14.021 (2C14) DRIVER Invalid N1=6 parameter - ProcessTagReading() error
08/12/2021 09:46:14.021 (2C14) TAG <== (0.000) Tag(6.0.0.0).ReadValue = ERROR (hr=8004E008)
08/12/2021 09:46:14.021 (2C14) TAG ==> (0.000) Tag(10.0.0.0).WriteValue (09:46:14.021) 25 = SUCCESS
08/12/2021 09:46:14.021 (2C14) TAG <== (0.000) Tag(10.0.0.0).ReadValue = (09:46:14.021) 25
08/12/2021 09:46:14.022 (2C14) TAG ==> (0.000) Tag(0.0.0.0).WriteValue (09:46:14.022) ‘jesse.ti@grupoherculano.com.br’ = SUCCESS
08/12/2021 09:46:14.022 (2C14) TAG <== (0.000) Tag(0.0.0.0).ReadValue = (09:46:14.022) ‘jesse.ti@grupoherculano.com.br’
08/12/2021 09:46:14.023 (2C14) TAG ==> (0.000) Tag(1.0.0.0).WriteValue (09:46:14.023) ‘Teste Assunto’ = SUCCESS
08/12/2021 09:46:14.023 (2C14) TAG <== (0.000) Tag(1.0.0.0).ReadValue = (09:46:14.023) ‘Teste Assunto’
08/12/2021 09:46:14.023 (2C14) TAG ==> (0.000) Tag(2.0.0.0).WriteValue (09:46:14.023) ‘Mensagem’ = SUCCESS
08/12/2021 09:46:14.024 (2C14) TAG <== (0.000) Tag(2.0.0.0).ReadValue = (09:46:14.024) ‘Mensagem’
08/12/2021 09:46:14.024 (2C14) DRIVER Write type mismatch. Expected Numeric data - ProcessTagWriting() error: Failed v.Get(byPriority)
08/12/2021 09:46:14.024 (2C14) TAG ==> (0.000) Tag(3.0.0.0).WriteValue (09:46:14.024) ‘1’ = ERROR (hr=80070057) (status = (09:40:36.516) 1000200)
#8

Olá, Jessé.
Esta parte do log indica que está sendo feita uma escrita no tag com N1=3, que é o tag de envio/prioridade do e-mail, mas o valor escrito é uma string:

08/12/2021 09:43:42.025 (2C14) DRIVER|Write type mismatch. Expected Numeric data - ProcessTagWriting() error: Failed v.Get(byPriority)|
08/12/2021 09:43:42.025 (2C14) TAG|==> (0.000) Tag(3.0.0.0).WriteValue (09:43:42.025) ‘1’ = ERROR (hr=80070057) (status = (09:40:36.516) 1000200)

O 1 entre aspas simples quer dizer que o valor escrito é do tipo string.

Mesmo que o script pareça estar correto, tente mudar para o seguinte:

Application.GetObject(“EnvioEmail.SenhaRemetente”).WriteEx “XXXX”
Application.GetObject(“EnvioEmail.PortaSMTP”).WriteEx 25
Application.GetObject(“EnvioEmail.Destinatario”).WriteEx “jesse.ti@grupoherculano.com.br”
Application.GetObject(“EnvioEmail.Assunto”).WriteEx “Teste Assunto”
Application.GetObject(“EnvioEmail.Mensagem”).WriteEx “Mensagem”
Application.GetObject(“EnvioEmail.Enviar”).WriteEx CInt(1)

#9

Boa tarde.

Caso queira tentar, você não precisa de um driver para enviar email, basta usar este script abaixo e executa-lo quando precisar

	Set objMessage = CreateObject("CDO.Message")
		objMessage.Subject = "Relatório de Pesagem"
		objMessage.Sender = "seu_email@gmail.com.br"
		objMessage.To = "destinatario@gmail.com.br"
		objMessage.TextBody = "Aqui vai o corpo do email, aceita HTML"
		objMessage.AddAttachment ("C:\relatorio.PDF") 'Anexo, pode elimiar a linha se não usar
		objMessage.Configuration.Fields.Item("http://schemas.microsoft.com/cdo/configuration/sendusing") = 2
		objMessage.Configuration.Fields.Item("http://schemas.microsoft.com/cdo/configuration/smtpserver") = "mail.seuservidorsmtp.com.br"
		objMessage.Configuration.Fields.Item("http://schemas.microsoft.com/cdo/configuration/smtpserverport") = 25
		objMessage.Configuration.Fields.Item("http://schemas.microsoft.com/cdo/configuration/smtpauthenticate") = 1
		objMessage.Configuration.Fields.Item("http://schemas.microsoft.com/cdo/configuration/sendusername") = "login_do_email"
		objMessage.Configuration.Fields.Item("http://schemas.microsoft.com/cdo/configuration/sendpassword") = "senha_do_email"
		objMessage.Configuration.Fields.Item("http://schemas.microsoft.com/cdo/configuration/smtpusessl") = false
		objMessage.Configuration.Fields.Item("http://schemas.microsoft.com/cdo/configuration/smtpconnectiontimeout") = 60
		objMessage.Configuration.Fields.Update
		objMessage.Send
#10

Boa noite. Sua sugestão deu certo sim, não apresentou mais o erro, no log informa que foi enviado mas não chegou nada. Segue log novamente: