Could not create SSOCSTX. To fix the problem, reinstall SSO or install SSOCSTX.dll into a COM+ library application.

Posted: October 9, 2013 in BizTalk
Tags: , , , ,

First of all let me apologies for my long absence, almost passed a month since I wrote the last time on my blog and for me is a long time but I’m back… and I assure you that I haven’t been standing doing nothing, on the contrary, I’m working in several white papers, reviewing others, speaking in events, a lot of work and so on… so I still will publish a lot content this year.

Today after installing .NET Framework 4.0 in my BizTalk Server 2006 Lab environment and of course restart the machine, the Enterprise Single Sign-On Service stopped working.

The first error that I found was:

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

This was an error that I already blogged in the past and you can find more information here. But basically you need to fix the Enterprise Single Sign-On by running the following command: regasm SSOSQL.dll.

After solving this problem I tried to start it manually the SSO Service but surprisingly, I got two new errors in the event viewer:

“Could not create SSOCSTX. To fix the problem, reinstall SSO or install SSOCSTX.dll into a COM+ library application.
Additional Data: 93
Error Code: 0x8004E00F, COM+ was unable to talk to the Microsoft Distributed Transaction Coordinator”

Could-not-create-SSOCSTX-error

Followed by:

“The SSO service failed to start.
Error Code: 0x8004E00F, COM+ was unable to talk to the Microsoft Distributed Transaction Coordinator”

The-SSO-service-failed-to-start-error

At this point for me it was clear I have issues with MSDTC.

After searching a little I found the first possible solution that basically told me to u reinstall the Microsoft Distributed Transaction Coordinator (MSDTC) to resolve the issue, of course this was a solution that I was trying to avoid.

SOLUTION

The first thing you must do is to check if the MSDTC is running and make sure the MSDTC security settings are configured correctly:

  • Network DTC Access – Checked
  • Client and Administration
    • Allow Remote Clients – Checked
  • Transaction Manager Communication
    • Allow Inbound – checked
    • Allow Outbound – Checked
    • No authentication required – checked

In my case everything was properly configured so next step:

  • Why not try to restart the Microsoft Distributed Transaction Coordinator (MSDTC) service?

Since that is the cause of the current problems… that seams a good idea, better this that reinstall the MSDTC J

Wow! Bingo! Found the solution to all my problems! After restarted successfully the MSDTS Service I was able to start the Enterprise Single Sign-On Service and of course the BizTalk Services with success.

Comments
  1. Good tip, Sandro.
    I also check to make sure the latest COM+ CU and SP is installed.

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 )

Twitter picture

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

Facebook photo

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

Google+ photo

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

Connecting to %s