Slow startup for K2 components when the machine has no internet access

Issues:

1. Some start performance issues can be experienced when the machine does not have internet access, for example, a virtual machine configured to have "local" network settings. This causes a number of components to startup slowly such as K2Setup, K2HostServer or K2 Designer for Visual Studio.
2. Custom Web Services that use any of the client assemblies such as the SourceCode.SmartObjects.Client assembly might experience time outs after an App-Pool recycle.

Cause:

The K2 Client.dlls are signed with an Authenticode certificate for Windows 7 Certification.By Default the CLR performs a publisher verification on Authenticode signed assemblies, via the Internet and therefore on a machine with no internet   it eventually times out on the connection and continues.

Resolution:

1. Disable publisher verification for the K2 Setup and K2 Host Server by modifying the “Machine.Config” on the relevant servers,or for asp.net the "aspnet.config" in the .NET Framework dir. as follows:

   Copy
   <configuration> ....     <runtime>         <generatePublisherEvidence enabled="false"/>     </runtime> ....  </configuration>

2. K2 Designers that startup slowly with no internet access also need the publisher verification disabled in Internet Explorer. Uncheck the "Check for publisher's certificate revocation" setting in the Internet Explorer options.