If you are having an issue with a Blueprint 5.1 or 5.2 TaskMaster, Secure Release Service, Logging Service, or Site Monitor service not starting during installation or during operation, it is possible that Microsoft Authenticode is getting in the way (for a good read-through on Authenticode, read Everything you need to know about Authenticode Code Signing - IEInternals - Site Home - MSDN Blogs). For those in the "tl;dr" camp, here's the quick skinny:
- Microsoft would like its developer community to digitally certify their applications.
- Microsoft .NET applications, like ours, get checked on start-up to ensure that the certificate is still good.
- If your server is not immediately able to contact the Internet for a little thing called a Certificate Revocation List (CRL), the service may not start due to timeout by the Service Control Manager.
If you have that problem, modify that application's "config" file to include this <runtime> group within <configuration>:
The following files are modification candidates (note that the folder paths are default, so your server path may be different):
- C:\Program Files (x86)\PharosSystems\SiteMonitor\Logging\PharosSystems.LoggingService.exe.config
- C:\Program Files (x86)\PharosSystems\SiteMonitor\Service\PharosSystems.SiteMonitor.Service.exe.config
- C:\Program Files (x86)\PharosSystems\SecureRelease\PharosSystems.SecureRelease.SecureReleaseService.exe.config
- C:\Program Files (x86)\PharosSystems\Blueprint\bin\PharosSystems.Blueprint.TaskMaster.exe.config
Some words of caution in the editing:
- PharosSystems.LoggingService.exe.config and PharosSystems.SIteMonitor.Service.exe.config have a <configSections> group after the initial <configuration> tag. Put the <runtime> group in after the </configSections> line.
- PharosSystems.SecureRelease.SecureReleaseService.exe.config already has a <runtime> group. So just put the <generatePublisherEvidence enabled="false"/> line in there as a child.
When you are finished editing, save the file and start the service.