Mark Barto's Blog

BizTalk: Windows could not start the Enterprise Single Sign-On Service service on Local Computer

Microsoft BizTalk 2009 and Enterprise Single Sign-On was running smooth on all the machines and after more investigation the following error was caused by an automatic update of Microsoft .NET Framework 4.0.

---------------------------
Services
---------------------------
Windows could not start the Enterprise Single Sign-On Service service on Local Computer.

Error 0x80131700: 0x80131700
---------------------------
OK  
---------------------------

WCF, BizTalk: Root element is missing

 
We had a strange behavior when generating a WCF Service with the BizTalk Publishing Wizard. When we browse to the generated service in our browser we got the message "Root element is missing".

WCF, BizTalk: The signature is invalid

We have generated with the BizTalk WCF Publishing Wizard a WCF Service based on a Metadata only endpoint for a Receive Location. The receive location will be configured as a net-MSMQ transport type.

We have encountered a problem that the message will not be send to the queue but to the dead letter queue with the message "The signature is invalid".

BizTalk,Oracle: ORA-24777: use of non-migratable database link not allowed

When using the WCF Oracle Adapter I was getting the following error message 'ORA-24777: use of non-migratable database link not allowed' when I want to execute a stored procedure.

BizTalk, Windows: After restarting BizTalk host instances services stayed disabled

We have discovered that after a restart the BizTalk host instance services stayed disabled even when the startup type is set to automatic.

The problem is that the BizTalk host instance service has a dependency with the Enterprise Single Sign-On Service which is not starting quickly enough. Because of this the BizTalk host instance services will not start.

BizTalk: Missing context property ReceiveLocationName within orchestration

We have noticed that when you are transforming a message within an orchestration that the context properties of the original message will not be copied to the transformed message. You must declare this specific within your expression shape of your orchestration.

Because we are using ESB for exception handling we want to know the location where the message is coming from.

Unfortunately the ReceiveLocationName is missing in the standard BTS namespace.

BizTalk: Call Rules shape grayed out

When trying to use the call rules shape within my orchestration I have noticed that when right-clicking on your orchestration the call rules shape was grayed out.

BizTalk: Custom functoid in mapping return incorrect decimal

I have encountered a very strange problem by using a custom functoid in a mapping which converts a float to decimal where the returned value is not a decimal at all. 

As value I was given the -4.9E-5 but when checking the returned value was -4.9E05 and not -0,000049 what i was expected. Why this happen i don't know but I found a solution.

BizTalk, Tools: Microsoft BizTalk Server Best Practices Analyzer (BPA)

 
This tool created by Microsoft will examine your BizTalk Server deployment and configuration environment and verifies it against deployment and configuration best practices.

The Best Practices Analyzer performs configuration level verification, by reading and reporting only. For example, the Best Practices Analyzer gathers data from Windows Management Instrumentation (WMI) classes, SQL Server databases, registry entries, and other parts of your deployment, and uses the gathered data to determine whether best practices are being followed. The Best Practices Analyzer does not modify any system settings, and is therefore not a self tuning tool.

BizTalk: Unit testing

In Microsoft BizTalk 2009 there is a new feature called Enable Unit Testing.

When setting this option to True it is possible to create an unit test for validating schemas or mappings.

In the following section I will explain how-to configure your BizTalk Project, Creating/Configuring a Test Project and explain the code snippet of a test method which test the map and validate the correctness of the output.

BizTalk: WCF-SQL Adapter not displayed on x64

When installing the SQL Adapter for x64 the adapter will not be displayed in BizTalk Administration when trying to add the adapter.

Because BizTalk Server Administration console runs as a 32-bit process and not in a 64-bit process it will not be displayed in the dropdown when registering the adapter in BizTalk Administration.

BizTalk: Solved - MessageType not promoted!

In my previous post MessageType not promoted I had a problem that the MessageType will not be promoted if there was an inbound mapping failure.

Unfortunately the MSDN Forum - BizTalk General also had no solution for this problem. Because of this problem I have contacted someone from Microsoft who may answer this question.

BizTalk: WCF - SQL Adapter for BizTalk 2009

If you are using the standard SQL adapter what is part of BizTalk you must be known that this adapter in the nearby future will not be supported anymore by Microsoft.

Because of this reason it is a best-practice to replace this adapter to the new WCF-SQL adapter.

This adapter which is also part of the BizTalk Adapter Pack 2.0 is also available as stand-alone download.

BizTalk: MessageType not promoted !

On the Microsoft MSDN Forums I have asked a question why the MessageType is not promoted when an error occurred in the inbound mapping of the receiveport.

Unfortunately this was not the answer I was hoping for.

BizTalk, ESB: Microsoft ESB Toolkit 2.0

Finally the new ESB Toolkit 2.0 is available for download at the Microsoft website.
The name has also been changed from ESB Guidance to ESB Toolkit and this version will not be available on CodePlex anymore.

BizTalk, ESB: CDATA element incorrectly closed

  

We are using the Microsoft BizTalk Enterprise Server Bus (ESB) Guidance 2.0 CTP 2 as best practice within Microsoft BizTalk 2009. At the moment we are using especially the exception handling for fault handling.

We are not using the included ESB portal for resubmit the fault message but we have created a SharePoint Web Part which reads the EsbExceptionDB.

Unfortunately we have discovered that the Message Data that is written to the database is incorrectly when using CDATA elements in your original message.

BizTalk, ESB: Error converting data type nvarchar to datetime

When using the Exception Handling within ESB (Enterprise Service Bus) for BizTalk 2009 there will be a Sendport All.Exception in the Microsoft.Practices.ESB Application. This sendport will be executed if there is a failed message generated in the messagebox, if you have checked the option Enable routing for failed messages.

Issues regarding ESB 2.0 CTP 2 on BizTalk 2009

 
When installing ESB 2.0 CTP 2 on a BizTalk 2009 machine I'm facing with a couple of problems.

When running on a 64-bit machine with powerscript the script "Setup_src.cmd" in "Source\Exception Handling\Install\Scripts" will complain about ExplorerOM that this is not compatible with 64-bit.