There was a failure executing the send pipeline: “Please ensure that exsmime.dll has been registered in the system.”

  • Sandro Pereira
  • Oct 8, 2010
  • 2 min read

For no reason, one of my BizTalk 2006 R2 Lab environment begin to display the following error:

“message sent to adapter “FILE” on send port “SEND_EDI_INVOICE: FILE” with URI “C:\Projects\ Ports\OUT_EDI_INVOIC\%MessageID%_%SourceFileName%” is suspended.
Error details: There was a failure executing the send pipeline: “EDISendSMimeEncode, Version=1.0.0.10, Culture=neutral, PublicKeyToken=4dbf1ba6edc1a1f4” Source: “MIME/SMIME encoder” Send Port: “SEND_EDI_INVOICE_FILE” URI: “C:\Projects\Ports\OUT_EDI_INVOIC\%MessageID%_%SourceFileName%” Reason: Unable to initialize.
Please ensure that exsmime.dll has been registered in the system.

This is a strange behavior that occurs in a custom pipeline that uses the MIME/SMIME encoder. The solution that I found to solve the problem was the first solution presented here.

📝 One-Minute Brief

Encountering the error “There was a failure executing the send pipeline… ensure that exsmime.dll has been registered” usually happens when the MIME/SMIME encoder component is used on a 64-bit BizTalk environment. The fix involves manually registering the exsmime.dll (found in the BizTalk installation folder) using the regsvr32 command in an elevated Command Prompt. This ensures the COM component is properly recognized by the system, allowing the pipeline to execute successfully.

Cause

This error occurs because the exsmime.dll, which handles MIME and S/MIME encoding/decoding, is a COM component that isn’t always automatically registered in the Windows Registry during the BizTalk configuration process—particularly in 64-bit host instances.

Solution 1

  • Open the command prompt and type:
    • cd C:\Program Files\Microsoft BizTalk Server …\
  • and execute the following command:
regsvr32 exsmime.dll

After that, I started looking for my “exsmime.dll” file in my BizTalk environment, and to my surprise, there was none! yeh… But I found a backup file of that specific file in this directory with the following name:

  • ExsmimeBak.dll

So I tried to implement Solution 2 described below to see if it also fixed the problem, and to my surprise, it also solved my problem.

Solution 2

  • Open the command prompt and type:
    • cd C:\Program Files\Microsoft BizTalk Server …\
  • and execute the following command:
regsvr32 ExsmimeBak.dll
Thanks for Buying me a coffe
Author: Sandro Pereira

Sandro Pereira lives in Portugal and works as a consultant at DevScope. In the past years, he has been working on implementing Integration scenarios both on-premises and cloud for various clients, each with different scenarios from a technical point of view, size, and criticality, using Microsoft Azure, Microsoft BizTalk Server and different technologies like AS2, EDI, RosettaNet, SAP, TIBCO etc. He is a regular blogger, international speaker, and technical reviewer of several BizTalk books all focused on Integration. He is also the author of the book “BizTalk Mapping Patterns & Best Practices”. He has been awarded MVP since 2011 for his contributions to the integration community.

Leave a Reply

Your email address will not be published. Required fields are marked *

The Ultimate Cloud
Management Platform for Azure

Supercharge your Azure Cost Saving

Learn More
Turbo360 Widget

Back to Top