.Net Framework 4.0 disrupts BizTalk ENTSSO Service

October 19, 2011 at 11:03 am 2 comments

One of the greatest features of the .Net Framework is the ability of having multiple versions installed in the same computer running along without any glitch. There are some cases however in which a net .Net Framework version or service pack breaks havoc in your infrastructure.

A couple of days ago a customer contacted me in the early hours of the morning because his BizTalk 2006 server was down and unable to start after deploying a new application in the server.

Upon further inspection of the server Windows logs I found out the reason why the BizTalk Host Instances weren’t being able to start. The reason was a problem with the Enterprise Single Sign-On that prevented this requisite service to start.


As you can see in the error description above there was a DLL required by the ESSO service that wasn’t properly registered and this made the connection to the ESSO database impossible to make.

But how this happened if the server have been working without a glitch for the last year and more importantly what could be done to resolve the issue at hand?

Well, the answer to the question was in what in the new application being deployed to the server just before the ESSO service started to fail. This application was developed in the .Net Framework 4.0 and it was installed as a part of the deploying activities. Usually this would mean no problem at all but It turns out the SSOSQL.dll doesn’t specify the correct version of the .NET Framework. When .NET Framework 4 is installed, the assembly will try to use the newer framework and then fail to load.

The solution to this problem is very easy to implement, you only need to use regasm to re-register the SSOSQL.dll assembly.


If yours is a 32-bit Server follow this instructions
1.       Open a command window
2.       Go to C:\Windows\Microsoft.NET\Framework\v2.0.50727
3.       Type: regasm “C:\Program Files\Common Files\Enterprise Single Sign-On\ssosql.dll”

if your installation is a 64-bit Server you will need to perform the same operation for the 32-bit and 64-bit versions of the assembly:
1.       Open a command window
2.       Go to C:\Windows\Microsoft.NET\Framework64\v2.0.50727
3.       Type each of the following and hit ENTER:
32bit:  regasm “C:\Program Files\Common Files\Enterprise Single Sign-On\win32\ssosql.dll”
64bit:  regasm “C:\Program Files\Common Files\Enterprise Single Sign-On\ssosql.dll”

Once the regasm operations are completed you will be able to start the ESSO service right away.


It is important to mention this problem also affects Host Integration Server 2009, BizTalk Server 2006 R2 and BizTalk Server 2009.

You can find more information about it here:

Microsoft Support Article ID: 2252691


Entry filed under: BizTalk. Tags: , , .

Calling an external assembly in BizTalk Mapper Configure an HTTP Receive Location in BizTalk 2009

2 Comments Add your own

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

Trackback this post  |  Subscribe to the comments via RSS Feed

October 2011
« Sep   Nov »


%d bloggers like this: