First of all, let me apologize 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 on several white papers, reviewing others, speaking of events, a lot of work and so on… so I still will publish a lot of content this year.
Today, after installing .NET Framework 4.0 in my BizTalk Server 2006 Lab environment and, of course, restarting 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 about 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 the SSO Service manually, 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”
Followed by:
“The SSO service failed to start.
Error Code: 0x8004E00F, COM+ was unable to talk to the Microsoft Distributed Transaction Coordinator”
At this point, for me, it was clear I had issues with MSDTC.
After searching a little, I found the first possible solution, which basically told me to reinstall the Microsoft Distributed Transaction Coordinator (MSDTC) to resolve the issue. Of course, this was a solution that I was trying to avoid.
📝 One-Minute Brief
Encountering the error “Could not create SSOCSTX” in BizTalk Server often happens after installing a new .NET Framework or performing a system update. While the error suggests reinstalling SSO or registering DLLs, the root cause is frequently a communication failure between COM+ and the Microsoft Distributed Transaction Coordinator (MSDTC). This guide outlines a non-invasive fix: verifying your MSDTC network security settings and performing a simple service restart to restore the Enterprise Single Sign-On (ENTSSO) service and BizTalk functionality.
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 on my side that it was configured correctly.
- Client and Administration
- Allow Remote Clients – Checked on my side that it was configured correctly.
- Transaction Manager Communication
- Allow Inbound – Checked on my side that it was configured correctly.
- Allow Outbound – Checked on my side that it was configured correctly.
- No authentication required – Checked on my side that it was configured correctly.
In my case, everything was properly configured, so the next step:
- Why not try to restart the Microsoft Distributed Transaction Coordinator (MSDTC) service?
Since that is the cause of the current problems… that seems a good idea, better this than reinstall the MSDTC!
Wow! Bingo! Found the solution to all my problems! After restarting the MSDTS Service successfully, I was able to start the Enterprise Single Sign-On Service and, of course, the BizTalk Services with success.
Hope you find this helpful! If you liked the content or found it useful and would like to support me in writing more, consider buying (or helping to buy) a Star Wars Lego set for my son.
Good tip, Sandro.
I also check to make sure the latest COM+ CU and SP is installed.