Archive | SSO RSS for this section

Could not contact the SSO server

I started getting my hands dirty with BizTalk development after a few months of working as an architect (in the drawing pictures and writing documentation sense).  It’s good to be back!  Unfortunately, it also means that I get the fun of setting up my BizTalk configurations again.

While trying to load some settings into SSO through the Deployment Framework (, I got this beauty of an exception:

Could not contact the SSO server ‘(local)’. Check that SSO is configured and that the SSO service is running on that server.
 (RPC: 0x800706BA: The RPC server is unavailable.)

The same error also showed up when I tried to run the SSO Admin utility as well.  My first reaction was to check my BizTalk configuration to make sure that everything looked good.  I saw the pretty “Green Check” next to SSO in the configuration list, so I guessed (correctly) that it had nothing to do with my BizTalk configuration.

But the fact that I was using the server ‘local’, did make me wonder.  I know this works ok with SQL Server, but using the shortcut (local) to refer to a database server is problematic with SSO.   To set things straight, I just had to run the SSOManage command-line utility and set the server to the local machine name instead of using the term “(local)” and that fixed the problem.

So, here’s the command-line fix:

C:\Program Files\Common Files\Enterprise Single Sign-On>ssomanage -server <machineName>


C:\Program Files\Common Files\Enterprise Single Sign-On>ssomanage -serverall <machineName>

You can then run the same utility with the -showserver command-line parameter to make sure that it took. Below is an image of the results on my machine.


Enterprise SSO Won’t Start!

All my BizTalk Server hosts died on me the other day. When I attempted to restart them, I saw the following exception message:

Windows could not start the Enterprise Single Sign-On Service service on Local Computer.

Error 0x80131700: 0x80131700

Fortunately, the BizTalk console also provides easy access to event logs through the “Classic Event Viewer” (which I happen to like better than Windows Server’s newer event viewer, anyway). It gives a hint to the solution of the problem:

Could not create SSOSQL. To fix the problem, reinstall SSO or try 'regasm SSOSQL.dll' from a Visual Studio command prompt.

Error Code: 0x80131700

Re-installing SSO didn’t sound very appealing to me so I tried what the error suggested, which was to re-register the SSO SQL assembly. From the Visual Studio command prompt, you run the following:

C:\regasm "C:\Program Files\Common Files\Enterprise Single Sign-On\SSOSQL.dll"

Then I was able to restart SSO and BizTalk.

Interestingly enough, the cause of the issue was that I installed .NET 4.0 on my machine. The SSO SQL assembly tries to use .NET 4.0, when it still needs to run on an earlier version of the framework. A re-register sets it straight.

Microsoft has a knowledge base article about this problem and a patch which you can access here:

%d bloggers like this: