BizTalk Explorer operations fail with System.Data.SqlClient.SQLException

  • Article

This article provides information about resolving the failure of BizTalk Explorer operations when you're using the BizTalk Explorer Object Model to manipulate service instances and messages.

Original product version:   BizTalk Server 2013, 2010
Original KB number:   3054335

Symptoms

The BizTalk Explorer Object Model allows users to manipulate service instances and messages, as shown in the following example:

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Threading.Tasks;
using Microsoft.BizTalk.Operations;
namespace TestSus
{
    class Program
    {
        static void Main(string[] args)
        {
            var instanceID = new System.Guid("a5cb07b5-65cf-457b-8041-eee7463af564");
            var messageID = new System.Guid("00dca8b0-48af-40b7-a5f9-b91da7d66617");
            var biztalkOperations = new Microsoft.BizTalk.Operations.BizTalkOperations();
            var biztalkMessage = biztalkOperations.GetMessage(messageID, instanceID);
            biztalkOperations.TerminateInstance(instanceID);
        }
    }
}

You might receive the following message:

Exeption: An unhandled exception of type 'System.Data.SqlClient.SqlException' occurred in Microsoft.BizTalk.Operations.dll: Conversion failed when converting from a character string to unique identifier.

Workaround

To work around this problem, create two BizTalkOperations objects. Use one BizTalkOperations object to call GetMessage() and the other to call TerminateInstance(). Generally, you should create two BizTalkOperations objects: use one for read operations and the other for write operations.