We first had reports of slow start-up of Process Navigator on some systems as far back as version 4.60. This has been found to be a problem particularly on servers that didn't have Internet access.
We now have a better understanding of its cause and how it may be addressed. The Process Navigator executable (AnalystEdition.exe) is a managed code assembly that has been digitallysigned with an Authenticode certificate identifying Triaster as its publisher. When that executable is launched, the system will try to verify that certificate over the Internet, checking that the certificate hasn't been revoked against a Certificate Revocation List (CRL) held remotely. If the connection is impossible (for example, firewall restrictions), Process Navigator start-up is delayed, and has been found to take up to 2 minutes to start in some cases.
In a recent installation of Triaster Server 12, we encountered a problem with the Triaster service executables timing out on start-up. Although that was addressed by increasing the default service time-out, it too was an issue with certificate authentication. The service executables in Triaster Server 12 are digitallysigned; those in Triaster Server 10 are not.
Particularly if the host computer doesn't and shouldn't have Internet access, the certificate revocation check can be disabled.
Disabling the check for a specific assembly
A config file can be created that disables the check for its associated assembly.
<?xml version="1.0" encoding="utf-8" ?>
Disabling the check for all managed assemblies If a computer is purposely denied Internet access, it cannot perform the certificate revocation check, so it's reasonable to disable this check generally. However, it should be confirmed that doing so would not breach your company's IT policies before you make the change.
The process for disabling this check is as follows:
Slow Process Navigator and Visio start up with 4.60 onwards: http://tinyurl.com/bx3qp2g