Solved

Exchange connector: SendGetAttchment @byte_arry is null when trying to save email atttachment

  • 6 October 2021
  • 5 replies
  • 125 views

Userlevel 2
Badge +2

Hello,

We are using the Exchange connector to process e-mails, which arrive on a certain e-mail address, within our ticket system. These emails often contain attachments and are saved using the sendGetAttachment + saveAttachment. However if the attachment is an e-mail the @byte_array will be NULL and will not be saved. 

Does anyone have an idea why @byte_array is NULL when the attachment is an e-mail?

Thanks in advance.

Greetings,
Randolph

 

icon

Best answer by Robbert van Tongeren 28 October 2021, 10:11

View original

5 replies

Userlevel 7
Badge +23

Hi,

Could it be that the email and attachment are no longer on the server or in the inbox of the user?

Userlevel 2
Badge +2

Hi Mark,

Thanks for the response. It doesn't look like it. It is also reproducible. If I mail the same mail with the mail attachments to the relevant mail box to be imported then it is imported without attachments. If it is a PDF, then it goes well.

 

Greetings,

Randolph

Userlevel 5

Hi Randolph,

 

Could you try and break the procedure down?
In the exh_email_table there should be a colum (in the back of the table) with exh_Attachments, in here there is the name and the exh_id for that attachment. With the procedure to retreive the attachment the first thing done is to split the attachments, then per attachment it will be retreived from the exchange server.

When you break these procedures down you are able to request the specific attachment that is not working, and putty you are able to see the logs of the exchange connector, do you see an error or message in there?

https://docs.thinkwisesoftware.com/docs/kb/exchange.html#monitoring

 

Userlevel 7
Badge +23

Hi,

Did Robbert's reply help you out and/or is the question solved?

Userlevel 2
Badge +2

Hi Marc,

Sorry for the late response, but for now we did not have time to break down the procedure, (the show had to go on). So for now we leave it as it is, because it happens incidential.

Thanks,

Randolph

Reply