RTI_CDOMAIL Patch retaining OS lock on attachments (OpenInsight 64-bit) [Revelation On-Line Wiki]

OpenInsight 64-bit, chip fichot, bshumsky

Join The Works program to have access to the most current content, and to be able to ask questions and get answers from Revelation staff and the Revelation community

At 18 OCT 2022 02:15:32PM chip fichot wrote:

Hi Everyone

We recently installed the RTI_CDOMAIL patch on OI 9.4 (as identified in the link below) as we are beginning the migration process for Exchange 365

https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=WORKS_READ&KEY=892A040337B8C2479F5216DE3CE875DD

Our program which handles the generation of all correspondence creates a PDF file in the user's %TEMP% directory then deletes the file once RTI_CDOMAIL returns its value and throws an error message if delete is unsuccessful. Since the patch, we are seeing errors deleting the attachments after the email is successfully sent. We've confirmed this is not a Windows permission error.

The error returned by OSDelete is "Unknown Error", and if we try to delete the attachment file manually, we receive a Windows message that Open Insight has a lock on the file. Note that closing and re-opening OI does not release the lock.

I'm not sure if there is something we should be doing programmatically or if this might be a bug in the new version of RTI_CDOMAIL?

Thanks

At 18 OCT 2022 03:18PM bshumsky wrote:

Hi, Chip. Is it perhaps a matter of a few seconds - like the actual sending of the email might still be going on, even though we've returned from the RTI_CDOMAIL call in OI? In which case, a delay of a few seconds before the delete might be sufficient.

Or is it a persistent lock that you never see release, even after waiting some time?

Thanks,

- Bryan Shumsky

Revelation Software, Inc.

At 18 OCT 2022 04:11PM chip fichot wrote:

Hi Bryan

It's persistent. For example, i cannot delete files presently that were created and emailed yesterday.

Thanks

Chip

At 28 OCT 2022 05:51PM chip fichot wrote:

Hi Bryan

I just wanted to follow up on this - my initial thought was that this wasn't much of a pain point because the files accumulating in the temp directory wouldn't be outwardly problematic. As it turns out, there are some other processes that use attachments that are in other directories where users subsequently need to access the files and make changes or delete them, and it's now causing issues in that sensse.

Thanks

Chip

View this thread on the Works forum...