- 22 Apr 2024
- 1 Minute to read
- Print
- DarkLight
- PDF
How to enable Server Debug Level Logging for Pharos Blueprint Enterprise.
- Updated on 22 Apr 2024
- 1 Minute to read
- Print
- DarkLight
- PDF
Goal:
By default, the logging levels for the Blueprint server components is set to level 5 & it only logs errors only when Blueprint Server components are installed. How do I increase the logging level of it to provide more details.
Environment:
Blueprint Enterprise 4.2 and greater
Information:
Logging is configured using the Blueprint Server Configuration Tool.
Start up Blueprint Server Configuration located by navigating to the Start Menu -> Programs -> Pharos Blueprint Enterprise -> Blueprint Server Configuration. In Blueprint 4.2 and greater there is a Tools folder in the Pharos Blueprint Enterprise folder.
Select the Logging Tab where you can set the Blueprint Service components logging level individually.
Please set the following components with Debuglevel of 10 and make sure you un-tick Log only errors to file:
a. TaskMaster Service
b. Secure Release Service
c. Event Log Service
d. Administrator
e. Tracker Web Service
f. EDI Web Service
Note: For Blueprint 4.2 and above you will need to enable logging for the Job Service and Event Log Service as well.
4. Once enabled just click the Apply button on the Blueprint Server Configuration for the changes to take effect.
Warning! After clicking Apply button, all Blueprint services will be restarted.
5. Take note of the file path on the Logging TAB as this is where the log files will be written to.
6. Once the logs are enabled then please reproduce the problem situation while logging is enabled and this should allow the particular problem to be captured in the log files that you can now send to Pharos Support for review.