Partager via

BizTalk SSO stops working after installing Visual Studio 2010

  • Article

After installing Visual Studio 2010 on my Windows Server 2008 R2 box with BizTalk Server 2009 I got the following error when trying to deploy or access my BizTalk artefacts:

"Could not retrieve transport type data for Receive Location 'ABC' from config store. Primary SSO Server 'XYZ' failed. Could not contact the SSO server 'XYZ'. Check that SSO is configured and that the SSO service is running on that server. (RPC: 0x800706D9: There are no more endpoints available from the endpoint mapper.)

ErrorMsg_2_5D184E13

Also, when trying to start the Windows service “Enterprise Single Sign-On Service” using the Services control panel, the service will not start. I get the following 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

 

Solution:

The COM DLL SSOSQL.dll needs to be re-registered. In order to do this, locate the DLL in your file system. It can usually be found at the following location – “C:\Program Files\Common Files\Enterprise Single Sign-On”.

On a 32 bit operating system do the following:

Open a Visual Studio command prompt – “Visual Studio Command Prompt (2010)” and change directory to the location identified above. Run the command “regasm SSOSQL.dll”.

On a 64 bit operating system do the following:

The COM DLL SSOSQL.dll needs to be registered in the 32 bit and 64 bit hive of the registry. In order to do this, open a Visual Studio command prompt – “Visual Studio Command Prompt (2010)” and change directory to the location identified above. Run the following two commands

C:\Windows\Microsoft.NET\Framework\v2.0.50727\regasm.exe SSOSQL.dll

C:\Windows\Microsoft.NET\Framework64\v2.0.50727\regasm.exe SSOSQL.dll

Start the Windows service “Enterprise Single Sign-On Service” using the Services control panel or from the command line execute “NET START ENTSSO”.

 

Written by Erwin Wendland

Comments

  • Anonymous
    January 12, 2011
    many thanks for your optimal solution - I had same problem on Vista 64  (though not really using Biztalk at the moment)- and it worked also for me pietro munari

  • Anonymous
    March 14, 2011
    This happened because of VS 2010 installation .Read below article and install hotfix it will solve your problem. support.microsoft.com/.../2252691