Versions Compared

Version Old Version 2 New Version Current
Changes made by

Ben Ha

Ben Ha

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
  To enable verbose logging for the PrintPath Server and/or the PrintPath Printer Monitor Service, please follow the steps below:
  1. Stop all the PrintPath related services in the Windows Services list:

    1. PrintPath Service
    2. PrintPath Printer Monitor Service
    3. PrintPath FollowPrint Service
    4. Prism Authentication KMBS Service
    5. FollowPrint KMBS Service

  2. If you wish to obtain a clean set of log files, please browse to the PrintPath Logs directory (“C:\Program Files (x86)\Prism Software\PrintPath\Logs” by default) and delete all the log files shown there.  Otherwise, you may skip this step.

  3. In the PrintPath installation directory (“C:\Program Files (x86)\Prism Software\PrintPath” by default), locate the appropriate ".config" file corresponding to the PrintPath component you wish to enable verbose logging for:

    • PrintPathSvc.exe.config - PrintPath Server
    • PrinterMonitorService.exe.config - PrintPath Printer Monitor Service

  4. Open the ".config" file in a text editor (such as Notepad) and locate the line containing level value="INFO" and change the word INFO to DEBUG.  Then save the changes to the ".config" file and close the text editor.  The updated “.config” file should now look like this:

    Code Block
    <configuration>
...  
	<log4net>
	...
		<root>
			<level value="DEBUG" />
			...
	    </root>
        ...  
	</log4net>
	...
</configuration>
  5. Start all the PrintPath related services in the Windows Services list (in order):

    1. PrintPath Service
    2. PrintPath Printer Monitor Service
    3. PrintPath FollowPrint Service
    4. Prism Authentication KMBS Service
    5. FollowPrint KMBS Service

  6. At this point, the verbose logging mode should be enabled and all the logs in the PrintPath Logs directory (“C:\Program Files (x86)\Prism Software\PrintPath\Logs” by default) should contain the additional information for troubleshooting purposes.