SOSS Console is slow to start


Versions 5.0 and later of the SOSS Console are digitally signed with an Authenticode certificate to provide additional security. The SOSS Console is a .NET application, and if the system it runs on is not connected to the Internet then it can take .NET's runtime an extended period for the signature check to time out during startup.

This is a common issue with .NET applications that use digitally signed assemblies and run in restricted environments with no internet access. When the SOSS Management Console starts up, it tries to verify the Authenticode signature by retrieving the public key infrastructure (PKI) object from a trusted certificate authority's (CA's) web site. In cases where SOSS hosts do not have access to internet, the .NET runtime must wait for this outbound call to time out, causing the extended startup time.

To suppress verification of the Authenticode signature, add the generatePublisherEvidence XML element to the configuration file for the SOSS Management Console (soss_console.exe.config), located in the ScaleOut installation directory (if the file does not exist then you can create it):

<?xml version="1.0" encoding="utf-8" ?>
        <generatePublisherEvidence enabled="false"/>
Setting the generatePublisherEvidence runtime element to false instructs the common language runtime (CLR) to suppress verification of the Authenticode signature and not to create Publisher evidence for the SOSS Console assembly. This same workaround can be applied to the SOSS Object Browser tool as well--this element can be added to the DotNetBrowser.exe.config file.