- #Papercut ng not printing install#
- #Papercut ng not printing software#
- #Papercut ng not printing windows#
C:\Users\\web-print-logs\ on Windows Vista/2008.įor a definitive answer, open the following file on the PaperCut NG/MF Application Server in a text editor, and check the line beginning with server.log-file=: On Windows, the location of the logs folder depends on configuration and the Windows edition. If running in Sandbox mode, the relevant log files are found on the Web Print server that is in error. PaperCut uses the Application Server to manage user and account information, manage printers, calculate print costs, provide a web browser interface to administrators and end users, and much more. If you are running in Default mode, log files are collected from the PaperCut NG/MF Application Server An Application Server is the primary server program responsible for providing the PaperCut user interface, storing data, and providing services to users.
#Papercut ng not printing software#
See Where is the Web Print logs folder? for the location of the logs directory.įor further assistance, contact PaperCut Software Support.Ī separate logs folder is located on each system running the Web Print server software. Allow the webprint user read and write access.Ĭheck the Web Print server log file web-print.log. Check the Sharing and Security (NTFS/file) permissions for web-print-hot-folder share on the PaperCut primary server. If this action fails, there is a problem with permissions. The configured hot folder location is not writable.Ĭheck that the location indicated by Hot folder on the Web Print dialog is correct.Īs the webprint user, navigate to the configured web-print-hot-folder. See Why are some file formats not available? (Supported file formats listed in the section called “Supported Applications and File Formats” are not listed under Options → Mobile & Print → Web Print → Status page, or not accepted when uploading a file.) No valid handler programs installed/defined This service is not required in sandbox mode, and should be disabled. If running Web Print in Sandbox Mode, this error can indicate that the service PaperCut Web Print Server is running. Tech support will analyze this file, and help you find out the cause of the failure.
If the above steps do not fix the problem, then the failure is logged in /providers/web-print//logs/web-print-handler-pdf.log. If the printer is local, check that the printer's privileges allow the SYSTEM account to print to it. If the printer is remote, then check the steps listed in Default Mode Setup to ensure that the service is correctly configured to run as the webprint user account. The SYSTEM account does not have privileges for printing to remote printers. If running Web Print in Default Mode, check if the printer being printed to is running on the local computer. Check the log file for any obvious errors, such as not being able to find the application or problems launching it. web-print-handler-mso-word.log for Microsoft Office Word documents). Open the log file that matches the application of interest in a text editor (e.g. See below for the location of the Web Print logs folder.
The handler log files are named web-print-handler-*.log, where * is the name of the application. Each handler has a log file, which can provide more information about why the file format is not available. The Web Print server has a handler for each supported application. The next step is to check the Web Print log files. If running in sandbox mode, log in as the webprint user, then open and print a document with the application to ensure the user has the correct permissions. Next, ensure that the associated application is installed and working. Some file formats are only supported in sandbox mode.
#Papercut ng not printing install#
First, check Supported Applications and File Formats to see that the file format is supported in the mode that the Web Print Web Print enables printing from user-owned devices without the need to install printer drivers and manage server authentication.
0 kommentar(er)
