Recently we noticed an issue with ESSO with .NET 4.0 that could potentially affect Biztalk and HIS customers. We have released an update for ESSO on DLC along with a KB explaining the issue. The fix is also scheduled to go on the upcoming Microsoft Update.
SSO service fails to start after applying .NET 4.0. This is caused by a missing assembly registration entry in the SSO installation. The assembly is bound to CLR 2.0 but there is no specific entry for this requirement.
SSO is a required service for Biztalk and HIS and hence these services also would fail to start.
This issue can also be repaired by using the regasm tool to re-register the SSOSQL assembly. Regasm.exe is included with the .Net Framework.
32-bit Server1. Open a command window2. Go to C:\Windows\Microsoft.NET\Framework\v2.0.507273. Type: regasm “C:\Program Files\Common Files\Enterprise Single Sign-On\ssosql.dll”64-bit Server1. Open a command window2. Go to C:\Windows\Microsoft.NET\Framework64\v2.0.507273. 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”Note On a 64-bit server, regasm will need to be run for both the 32-bit and 64-bit versions of ssosql.dll.
Is there now an package hotfix for this? We use BizTalk 2006 and it would break our accreditation criteria to apply a unofficial fix. This means we can't move to .NET 4.
Thanks for the information. I have be struggling for about 2 hours for a fix to this and it really helped after following your instructions. Good article !!