Skip navigation
All Places > Blueprint Enterprise > Blog > 2015 > September

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:


  1. Microsoft would like its developer community to digitally certify their applications.
  2. Microsoft .NET applications, like ours, get checked on start-up to ensure that the certificate is still good.
  3. 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.


The Site Monitor Logging service will fail to start during installation if it cannot validate the certificate or move past the operation in 30 seconds. If you receive a notification that a service can start during installation, immediately make the change below prior to retrying.


If you have that problem, modify that application's "config" file to include this <runtime> group within <configuration>:




     <generatePublisherEvidence enabled="false"/>




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.


Let me share some thoughts and experience on the topic.


HR-LDAR-Importer is a great tool, which allows to easily and what is very import quickly prepare import file to update Blueprint database. The utility is documented and useful, but is there anything else that can make Blueprint better?

Sometimes LDAP and Blueprint databases are used to address different needs. For example, one can get reliable email address stored in LDAP (mostly because they use Exchange as email server) and Printer Cost Centers are stored in Blueprint. This way to use HR-LDAP-Importer we would need to make a customer change his behavior and organize Blueprint Cost Center’s in LDAP somehow. Another example would be a customer unwilling to change anything inside a Blueprint database except for, let say, email and FullName of a user and leaving all the rest of the information unchanged. Somehow, Blueprint allows Blueprint Administrator to register a user without entering any Budget Center or Location Group information, however if you try to import HR file those fields are required, so if, let say, Blueprint database is already configured for 5000 users with their respective Cost Centers and Location Groups but that info lacks in LDAP, you will face some difficulties using HR-LDAP-Importer


This document attempts to describe a way to automate csv file creation that contains information both from actual Blueprint Database and selective LDAP fields. Import of the file into Blueprint can be achieved with PharosSystems.Blueprint.Utilities.HrLdapImporter.exe


What is necessary for us?

  1. Identify current Blueprint Users inside a Blueprint database (by current Blueprint Users I mean those users that are shown in Blueprint Administrator)
  2. Identify which LDAP attributes we need to be updated for those users and create LDAP view containing those attributes for each user
  3. Combine current Blueprint database information and those we got on step #2 to a result view
  4. Create csv from the result view


#1 is easy - we’re going to create a View inside psreports database, let’s call it LDAP_CURRENT_USER, that contains all Blueprint Current Users with all the information available and necessary for futher import

#2 is not so hard to do - we’re going to create a View inside psreports database that contains all LDAP users with all the parameters we need to be updated for our current users

#3 we will do inner join operation on the two views in order to get source view for our csv file

#4 we will use SSIS which is SQL Server Integration Services to export view #3 into import.csv file




Creating and scheduling SSIS package (#4) is not described here. In case anyone's interesting, please let me know, and I’ll update the document.



Hope this will save someday someone their time and efforts in Blueprint \ LDAP integration.


Thank you!