Strange Additions to Document Names (and How to Fix Them)

KB Home   |   Strange Additions to Document Names (and How to Fix Them)

Main.RemoteDownlevelDocument History

Hide minor edits - Show changes to output

August 10, 2017, at 03:41 AM by peterf - Mentions automatic ignore of Remote Downlevel Document and new ability to ignore custom strings
Changed lines 1-17 from:
(:title What is 'Remote Downlevel Document'?:)

Q: I get [@Remote Downlevel Document@] in the document name.  What is this and how do I fix it?

A: This is the
''default'' name Windows gives to documents when the program or computer does not provide a document name.  PaperCut logs any document name provided by the operating system.  This is the same name that appears in the Windows print queue.

A: Some common reasons for receiving this message are:

* The user has printed from an old legacy MS DOS application
.

* Apple Mac systems printing to Windows print queues will often display this name.  This is because of a limitation in the CUPS smb implementation.

* Windows workstations that have had their workstations added using a non standard printer mapping method such as:
** via
the user of the DOS command: [@net use lpt@] (remapping the LPT port to a network print queue)
** or added as a local printer mapping to a new port in the format of \\server\share

A: The recommended way to map the printer is as a ''Network Printer'' pointing to the queue with the name in format [@\\server\
printer@]
to:
(:title Strange Additions to Document Names (and How to Fix Them):)

!Strange Additions to Document Names...

Some users report seeing document names logged in PaperCut NG or PaperCut MF which don
't line up with the name of the document as was originally printed. For example, a document name might show as [@Remote Downlevel Document@], or be prepended by something like [@smbprn.00004@].

By default, our software accepts the document name which is reported by the host operating system to be true, and so that is the value which we record in our print log
. Sometimes, though, an operating system may override the original document name as it was recorded in the spool file, modifying it with a prefix, a suffix, or replacing it wholesale.

[@Remote Downlevel Document@], for instance, is the default name Windows gives to documents when
the program or computer does not provide a document name; this will be the same name that appears in the Windows print queue. Common reasons for seeing this document name replacement include the user printing from a legacy MS DOS application, printing to shared queues which have been mapped using a non-standard method (e.g. a local printer port defined as a UNC name, or through use of the [@net use lpt@] command), and in some cases when printing from macOS via the SMB protocol (due to a limitation in the CUPS SMB implementation).

Meanwhile, the [@smbprn.0000x@] style of prefix is most commonly seen when printing from Windows workstations through to CUPS print servers using SMB. In these cases, the actual document name will appear in full, but tailing the displayed prefix.

!... How to Fix Them

In the past, these sorts of names were often avoidable by remapping the print queues to workstations using an alternative method, such as mapping them as network printers using their UNC name (e.g. [@//server/printername@]), or by using a protocol besides SMB.

In later versions of PaperCut NG and PaperCut MF, an automatic check for certain strings like [@Remote Downlevel Document@] was added, such that these errant document names derived from the operating system were ignored in favour of an attempt to read the genuine, original document name from within the spool file.

As of version 17.2.3, we've added a special item to the [@print-provider.conf@] configuration file to allow for custom strings to be added to the list of document name additions to ignore. The [@print-provider.conf@] file can be found on your Application Server, Site Servers, and Secondary Servers in the following location, where  [@[app-path]@] is the installation directory of the application, and [@[platform]@] reflects the operating system of that print server:

[@[app-path]\providers\print\[platform]\print-provider.conf@]

From version 17.2.3 onwards, the following line can be added to this configuration file:

[@IgnoreOSDocumentNames=@]

After the [@=@] character, a comma-separated list of items can be added. If any of these items partially matches a document name the operating system reports to our application, we'll ignore that name, and instead attempt to retrieve and log the document name as it appears in the spool file. Using the two examples discussed in this article, the line in the configuration file would look like so:

[@IgnoreOSDocumentNames=Remote Downlevel Document,smbprn@]

When you've made your change, save and close the file, and then restart the Print Provider service (this can be quickly done on any platform by running the [@debug-disable@] script found in the same directory as the [@print-provider.conf@] file).
Added lines 9-10:
* The user has printed from an old legacy MS DOS application.
Changed line 18 from:
''Categories:'' [[Category.Miscellaneous|+]], [[Category.Error|+]]
to:
''Categories:'' [[Category.Error | +]]
Changed line 20 from:
[-Keywords: Local Downlevel Document-]
to:
[-Keywords: Local Downlevel Document-]
Changed lines 1-2 from:
(:title What is Remote Downlevel Document?:)
to:
(:title What is 'Remote Downlevel Document'?:)
Deleted line 16:
Changed lines 18-19 from:

''Categories:'' [[!Miscellaneous]], [[!Error]]
to:
''Categories:'' [[Category.Miscellaneous|+]], [[Category.Error|+]]
----
[-Keywords: Local Downlevel Document-
]
Changed lines 15-17 from:
A: The recommended way to map the printer is as a''Network Printer'' pointing to the queue with the name in format [@\\server\printer@]

to:
A: The recommended way to map the printer is as a ''Network Printer'' pointing to the queue with the name in format [@\\server\printer@]

Changed lines 5-6 from:
A: This is the ''default'' name Windows gives to documents when the program or computer does not provide a document name.  PaperCut uses the document name provided by Windows.  This is the same name that appears in the Windows print queue.
to:
A: This is the ''default'' name Windows gives to documents when the program or computer does not provide a document name.  PaperCut logs any document name provided by the operating system.  This is the same name that appears in the Windows print queue.
Changed lines 5-20 from:
A:
to:
A: This is the ''default'' name Windows gives to documents when the program or computer does not provide a document name.  PaperCut uses the document name provided by Windows.  This is the same name that appears in the Windows print queue.

A: Some common reasons for receiving this message are:

* Apple Mac systems printing to Windows print queues will often display this name.  This is because of a limitation in the CUPS smb implementation.

* Windows workstations that have had their workstations added using a non standard printer mapping method such as:
** via the user of the DOS command: [@net use lpt@] (remapping the LPT port to a network print queue)
** or added as a local printer mapping to a new port in the format of \\server\share

A: The recommended way to map the printer is as a''Network Printer'' pointing to the queue with the name in format [@\\server\printer@]


----

''Categories:'' [[!Miscellaneous]], [[!Error]]
Added lines 1-5:
(:title What is Remote Downlevel Document?:)

Q: I get [@Remote Downlevel Document@] in the document name.  What is this and how do I fix it?

A:

Comments

Share your findings and experience with other PaperCut users. Feel free to add comments and suggestions about this Knowledge Base article. Please don't use this for support requests.

Article last modified on August 10, 2017, at 03:41 AM
Printable View   |   Article History   |   Edit Article