Fixing BizTalk ENTSSO – Could not create SSOSQL. To fix the problem, reinstall SSO or try ‘regasm SSOSQL.dll’ from a Visual Studio command prompt.

  • Sandro Pereira
  • Jul 21, 2010
  • 3 min read

The Enterprise Single Sign-On (ENTSSO) service is the backbone of BizTalk Server security. When it fails, the entire BizTalk environment can grind to a halt. For some stupid reason, the Enterprise Single Sign-On Service stopped working in one of my BizTalk machines. When I tried to start it manually, I got this error in the event log:

“Could not create SSOSQL. To fix the problem, reinstall SSO or try ‘regasm SSOSQL.dll’ from a Visual Studio command prompt.
Error Code: 0x80131700”

📝 One-Minute Brief

When configuring or starting BizTalk, you may encounter the error: “Could not create SSOSQL. To fix the problem, reinstall SSO or try regasm ssosql.dll.” This typically happens due to a registration failure of the SSO SQL assembly during installation or after a server update. Instead of a full reinstallation, the solution is to manually register the ssosql.dll using the regasm utility via a Visual Studio Command Prompt. This ensures the SSO service can correctly interface with its SQL Server database.

Cause

This error occurs when the ssosql.dll (the component that allows the SSO service to communicate with SQL Server) is not properly registered in the Windows Registry. This can happen due to interrupted installations, permission issues, or system updates that unregister COM+ components.

Solution

  • Execute Visual Studio Command Prompt (Start → All Programs → Microsoft Visual Studio 2005 → Visual Studio Tools → Visual Studio Command Prompt)
  • Navigate to SSOSQL.dll folder, usually in:
    • C:\Program Files\Common Files\Enterprise Single Sign-On\
  • And execute the following command to fix the problem:
regasm SSOSQL.dll

Another problem that you can catch, associated with this, is the error:

BizTalk 1068 the dependency service or group failed to start”

When you try to start BizTalk Service BizTalk Group : BizTalkServerApplication service, because some dependency service is not running, in my case, it was the Enterprise Single Sign-On Service.

If you don’t have Visual Studio on the machine, you need to call the regasm.exe utility explicitly from the .NET folder:

  • Execute cmd (Start → cmd)
  • Type cd C:\Windows\Microsoft.NET\Framework\v2.0.50727 (in my case)
  • And execute the following command to fix the problem:
regasm.exe C:\Program Files\Common Files\Enterprise Single Sign-On\SSOSQL.dll

While the error message suggests a full reinstallation, a simple registration of ssosql.dll is usually all it takes to fix the connection between ENTSSO and SQL Server. This quick fix saves time and avoids the risk of a messy reinstallation.

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