Archive for July, 2008
- Windows Server 2003 R2 SP2
- SQL Server 2005
- Visual Studio 2005
- Visual Studio 2005 SP1
- BizTalk Server 2006 R2
- Visual Studio 2008
A BTS MIME error was encountered when attempting to encode a message. Error: The Signing Certificate has not been configured for AS2 party. AS2-From: <From Value> AS2-To: <To Value>
Event ID: 8132
A BTS MIME error was encountered when attempting to encode a message. Error: Exception of type ‘Microsoft.BizTalk.Component.MIMEException’ was thrown. HResult – 1061152225
There was a failure executing the send pipeline: “Microsoft.BizTalk.EdiInt.DefaultPipelines.AS2EdiSend, Microsoft.BizTalk.Edi.EdiIntPipelines, Version=184.108.40.206, Culture=neutral, PublicKeyToken=31bf3856as364e25” Source: “AS2 encoder” Send Port: <Send Port> URI: <HTTP Address> Reason: The MIME encoder failed to sign the message because the certificate has private key protection turned on or the private key does not exist.Please disable private key protection to allow BizTalk to use a certificate for signing.
- If you install onto Windows Server 2008, make sure that enough of the server roles have been enabled to install BizTalk. I would use the BizTalk application dependency chart found at the system requirements page (http://www.microsoft.com/biztalk/en/us/system-requirements.aspx) when selecting the Windows Server 2008 server roles. The roles have been expanded in Server 2008 from the handful found in Server 2003 so you will need to check quite a few boxes under Application Server in order to get all the dependencies that BizTalk requires. I would be a little generous in selecting features to install in case you are unsure so that you do not miss important ones.
- If you install BizTalk onto Server 2008 on a system that is setup with Server Core, be aware that IIS is not supported in any version of Server Core (see http://www.microsoft.com/windowsserver2008/en/us/compare-core-installation.aspx) so many of the BizTalk adapters will not work or will not work as expected. Without IIS you do will not be able to host WCF services in IIS or use various parts of the HTTP, MSMQ, or MQSC adapters and of course will not be able to expose orchestrations as web services over HTTP.
- If you are installing onto a 64-bit system, be aware that one of your BizTalk hosts will need to be configured as 32-bit only if you want to use certain 32-bit adapters. See the following article for more information on this – http://msdn.microsoft.com/en-us/library/aa560166.aspx.
- Be sure the most updated version of the .NET Framework and service pack has been installed. This may sound like something that should be installed standard, but it is actually not always.
- Be sure to run Windows Update on the Windows Server 2008 system prior to installing BizTalk
- Be sure that if you are installing onto a computer in a domain in which group policies are being employed (check with your System Administrators or IT support), all of the required dependency services are running on the future BizTalk server and separate SQL Server, including the COM+ System Application Service, and Distributed Transaction Coordinator service.
I think one reason that Microsoft has not yet provided documentation on using BizTalk with Server 2008 is that it will take a considerable knowledge of the product in order to configure Windows Server 2008 for a successful BizTalk install. Just determining all of the necessary server roles and features can take a while (see the server roles page for more details – http://technet2.microsoft.com/windowsserver2008/en/servermanager/default.mspx). Additionally, because Server Core breaks the functionality of so many of the BizTalk adapters it could be misleading or confusing to users to describe BizTalk as 100% compatible because by design, Server 2008 provides options for securing it to the point that it will not function in some configurations with BizTalk. I think it is possible there are some gaps in the system requirements page for Vista and Windows Server 2008. Its obviously not taking into consideration the Server 2008 prerequisites. Hopefully this blog post can provide some help in this regard. Now, back to the discussion on compatibility, it is possible to find some sparse documentary evidence that compatibility exists.