Check which version of the Print Server the customer is running. If they are not running the latest 6.1 Print Server Hot Fix then that’s probably the cause of the problem.

Reason:

Order of events is as follows.

  1. LPD Server starts receiving a print job. It creates an “entry” in the spool queue, with name of “Local DownLevel Document” and user of “SYSTEM”, because at this point they’re not known.
  2. LPD Server gets the rest of the job, updates the job name and user.
  3. Print Server detects new job, opens it, and gets the details.
  4. Print Server page counts the job, and puts the job details back with the page count info attached to end of the job name.

However, prior to Hot Fix 4 (6.1) for the Print Server we had the following order of events occur sometimes:

  1. LPD Server starts receiving a print job. It creates an “entry” in the spool queue, with name of “Local DownLevel Document” and user of “SYSTEM”, because at this point they’re not known.
  2. Print Server detects new job. Opens it, and gets the details (With name of “Local DownLevel Document” and user of “SYSTEM”).
  3. LPD Server gets the rest of the job, updates the job name and user.
  4. Print server finishes page counting the job, and puts the OLD job details back, with the page count info attached to end of the job name.