Logging
Logging the REST interface PPRest
The logging of the REST interface captures the entire communication of the Personal Printing server, such as the access to the JobViewer and the connections from the authentication devices.
- Open the file NLog.config in
C:\inetpub\wwwroot\PPRest. Make the orange highlighted supplements:
<?xml version="1.0" encoding="utf-8" ?> <nlog xmlns="https://www.nlog-project.org/schemas/NLog.xsd" xmlns:xsi="https://www.w3.org/2001/XMLSchema-instance" autoReload="true"> <extensions> <add assembly="NLog.Web.AspNetCore"/> </extensions> <targets> <target xsi:type="File" name="all-log-file" fileName="C:\Temp\PPRest-all-${shortdate}.log" layout="${longdate}|${logger}|${uppercase:${level}}|${message}|${exception}" /> <target xsi:type="File" name="own-log-file" fileName="C:\Temp\PPRest-own-${shortdate}.log" layout="${longdate}|${logger}|${uppercase:${level}}|${message}|${exception}" /> </targets> <rules> <logger name="*" minlevel="Trace" writeTo="all-log-file" /> <logger name="Microsoft.*" maxLevel="Info" final="true" /> <logger name="*" minlevel="Trace" writeTo="own-log-file" /> </rules> </nlog>
Then you get two log files in c:\temp:
- PPRest-all-yyyy-mm-dd.log logs everything
- PPRest-own-yyyy-mm-dd.log logs everything except Windows messages
Note! Enabling logs will affect the performance. So, disable logging if no longer needed.
Logging the RegPrint module
The logging of the RegPrint module only records the sending of the self-registration instructions to the printer selected by a user.
- Copy the file NLog.config from
C:\inetpub\wwwroot\PPRestto Personal Printing’s program directory (e. g.,C:\Program Files\Personal Printing). Make the orange highlighted changes:
<?xml version="1.0" encoding="utf-8" ?> <nlog xmlns="https://www.nlog-project.org/schemas/NLog.xsd" xmlns:xsi="https://www.w3.org/2001/XMLSchema-instance" autoReload="true"> <extensions> <add assembly="NLog.Web.AspNetCore"/> </extensions> <targets> <target xsi:type="File" name="all-log-file" fileName="C:\Temp\PPReg-all-${shortdate}.log" layout="${longdate}|${logger}|${uppercase:${level}}|${message}|${exception}" /> <target xsi:type="File" name="own-log-file" fileName="C:\Temp\PPReg-own-${shortdate}.log" layout="${longdate}|${logger}|${uppercase:${level}}|${message}|${exception}" /> </targets> <rules> <logger name="*" minlevel="Trace" writeTo="all-log-file" /> <logger name="Microsoft.*" maxLevel="Info" final="true" /> <logger name="*" minlevel="Trace" writeTo="own-log-file" /> </rules> </nlog>
Then you get two log files in c:\temp:
- PPReg-all-yyyy-mm-dd.log logs everything
- PPReg-own-yyyy-mm-dd.log logs everything except Windows messages
Note! Enabling logs will affect the performance. So, disable logging if no longer needed.
Website log
The processes of the web interface are logged by default. The log files can be found in:
%SystemDrive%\inetpub\logs\LogFiles
- You can change the path or disable logging. To do this, in IIS Manager select: Default Web Site→ Logging.
IIS Manager: path to the IIS log file and Disable option
Solving issues
The table below lists some messages and gives suggestions for solving the problem.
| Message/Problem | Suggested solution |
|---|---|
| When installing Personal Printing the following message appears: “The installation of Microsoft .NET Framework 4.6 Full has failed. Setup will now exit.” |
|
| You or your users can’t connect to the JobViewer. Depending on the browser, they receive an error message like this: “Hmm, we can’t reach this page.” |
|
| You can open the JobViewer or the Release Stations web console via http, but not via https.
(http is only supported by Personal Printing 4.0, not by Personal Printing 3.0 as a component of Mobile Print 1.0) |
|
| Authentication on the printer works via http, but not via https. For this you have configured the URL of the Personal Printing server in the authentication device first with http and then with https.
(http is only supported by Personal Printing 4.0, not by Personal Printing 3.0 as a component of Mobile Print 1.0) |
|
| Although users can open the JobViewer, the displayed information is not updated. |
|
| Clicking Test connection in the web console of the Release Station displays the message: “No Personal Printing server found.“
(The button Test connection is only supported by Personal Printing 4.0, not by Personal Printing 3.0 as a component of Mobile Print 1.0) |
|
| When trying to print, authentication works, but the print jobs are not sent to the target printer. |
|
| After the printer in question has been in “sleep mode”, the printouts start with a delay of several tens of seconds. This applies both to normal print jobs and to printing the self-registration instructions. |
|
| In the web console of the Release Station, no number appears under Last identity presented when the smart card or token has been held to the card reader. |
|
| You can’t create a Personal Printer with a native printer driver. Depending on the Windows version, you receive an error message like this: “Unable to install printer. Double check the printer name and make sure that the printer is connected to the network.” |
|
| When trying to print the error message “An error occurred while spooling the print job: %d” appears. | There are two known constellations:
|
example for a type-3 driver, in this example: OKI Universal PCL 5
Render print jobs on client computers option
Disabling NetBIOS support
After a physical printer has been in “sleep mode”, printouts may not start until several tens of seconds have elapsed. This applies both to normal print jobs and to printing the self-registration instructions. The reason for the delay is the configured support for the NetBIOS network protocol. Its deactivation provides a remedy.
- Open the network configuration on the computer from which the print jobs are sent.
- Select the TCP/IPv4 network protocol properties.
- Select Advanced.
- Select Disable NetBIOS over TCP/IP, and confirm all windows with OK.
Release Station troubleshooting
See the Troubleshooting section for the ThinPrint Hub.