MAPIEx VBO - EMSMDB32.DLL Issue

[AnastasiosKrap1]

Hello everyone,   we are currently facing a well-know problem of the 'EMSMDB32.DLL' using the MAPIEx VBO. Is there anyone out there that has solved this issue???   *Note: blueprism provides a link to MSDN for this problem (via the support tickets area), but there is no actual solution   Thanks in advance, Tasos

[Mustafa_UlasYig]

Hi AnastasiosKr Which issue exactly are you referring to? please provide link to MSDN, also. If you are referring to automate.exe crashing, then...: ""How do I fix the Automate.exe crash with EMSMDB32.dll faulting module? The EMSMDB32.dll file forms a part of the Microsoft API for connecting to the Exchange Server; it specifically handles the services for Messaging Application Programming Interface. This issue occurs when the EMSMDB32.dll file becomes faulty or corrupted. As a result, any subsequent attempts by Blue Prism to use MAPIEx functionality are unsuccessful because a key part of the API is not functioning correctly, causing the automate.exe process to crash. How to resolve your issue: Replace the faulty DLL file using one of the following methods: Identify a Resource that does not exhibit this behaviour, copy the EMSMDB32.dll file from this Resource to the faulty Resource and restart the machine. Contact Microsoft directly to obtain a new working version of this DLL file and move across to your Resource and restart the machine. Repair the installation of Outlook to replace the DLL file on the Resource then restart the machine. Once the EMSMDB32.dll has been replaced or repaired Blue Prism should begin to function correctly with MAPIEx."" ...This might help. Good luck BR, Mustafa

[AnastasiosKrap1]

Hello Mustafa, thanks for your response and help. I'll proceed with any of these methods and see the results. Just a question. How often do we have to make these actions (e.g. replace the faulty .dll) manually? Is there any indication that we could use to check that the .dll maybe become faulty and then for example create a script to replace it automically (so as to not interrupt the robot operations and the manual human intervention). As you can understand this can be occured in a production environment and so an admin has to make this actions/steps. Thanks a lot, Tasos

[Mustafa_UlasYig]

Hi AnastasiosKr Hopefully swapping the faulty .dll file with a new .dll file will do the trick and the file will not be corrupted again. Not sure if there is any indication and it is hard for me to reproduce your issue and see what BP reports, if anything. However you can automize a scan of outlook with the Microsoft Support and Recovery Assistant Tool (SaRa), which is a replacement for Office Configuration Analyzer Tool (OffCAT) to find issues in outlook: https://support.microsoft.com/en-us/help/4098558/how-to-scan-outlook-by-using-the-sara-tool . However this is a bigger and larger task to automatize, and there could be all sorts of issues found, might neccesarily, not even find the corrupt .dll file issue, but give it a go next time this error occurs in your environment. But if found, it could potentially repair/replace the file. You can choose to always copy/paste a new .dll file at the beginning of your process, though I am not sure about the consequences of that. Unfortunately you cannot have conditionals in the scheduler, otherwise one could imagine a setup where if a scheduled task A fails (because of faulty .dll file), then scheduled task B begins (pasting a new .dll file) and if scheduled task B succeeds, scheduled Task A begins (again), with a max retry attempts, so we do not create a infinite loop. Wishful thinking ;) You can instead create 3 scheduled tasks, that occur in a row, and always run 1) Task A --> 2) Task B --> 3) Task A. But if this is a good idea, depends entirely on you and the process you are trying to automatize.  Good luck BR, Mustafa

[AnastasiosKrap1]

Hello Mustafa,   we tried to repair the Outlook installation (1. Repair the installation of Outlook to replace the DLL file on the Resource then restart the machine.) but we noticed again the same error.  Did you manage to overcome this issue after one of the above mentioned resolution methods? *Note that in our implementation we use an infinite loop to poll email (via MAPIEx) in order to get work, using wait stages between consecutive polls. Thanks, Tasos

[Mustafa_UlasYig]

Hi AnastasiosKr I do not have the DLL file issue, and cannot provoke this error, and thus, not replicate the same error and give you an exact solution to your issue. But you need to solve this issue somehow, perhaps try to reinstall the office package on your client, and if this doesn't work, reinstall your client OS. Don't use an infinite loop. If you have Office Outlook 2007: Use Blue Prism MapiEx BO's action ""List Mails Within DateTimes"" to get a collection of e-mail ID's. Loop this e-mail ID collection with the Blue Prism MapiEx BO's action ""Get Mail"", remember to specify the ""Move to Sub-Folder"" input of the ""Get Mail"" action, otherwise, you keep reading the same email over and over. So you need to have a sub-folder in your e-mail client you move ""read"" e-mails to, in order to get this solution to work. If you have newer Office Outlook versions: You need to get the (Uncertified) MS Outlook VBO referenced in this thread: https://portal.blueprism.com/forums/technical-queries/faq-hints-tips/mapiex-save-emails-msg-files . Use MS Outlook VBO (uncertified) action ""Get Received Items (since date)"" (or one of the ofther get received items actions) to get a collection of e-mails. With this action, you do not need to move to sub-folder. You did not mention when in the process, you receive the DLL issue, perhaps this could be related to how you poll the e-mails, with your infinite loop (memory leak or other memory related issues). Try one of the suggested solutions above, depending on which MS office package you have on your client. Good luck. BR, Mustafa