Problem with Document.Print(printerName- jobName)

Aspose.Words Product Family
1

I’ve got an application that merges documents and prints them using Aspose.Words for .Net 16.2.0.0. This works very fine on my local machine (Windows 10).

But when I deploy the application to a server (Windows Server 2012 R2) there are a couple of issues.

The first issue is that the displayed name in the printer queue on the server is Always “Print Document”. I use the Document.Print(docName, jobName) method and that works fine locally.

See the attached screenshots.



The second problem is that on the server it takes about 10 times longer to print the same documents on the same printer than on my local machine.



Any help or hints would be greatly appreciated

2

Hello,

Are you sure that you use the same licence (and DLL) localy and on the server ?

I have the same issue because my licence was expired on me second environment.

Have a nice day.

3

Hi, thanks for your fast reply but I don’t think that this is the case in my solution because I’m using the license file as Embedded Resource

4

Hi Michel,


Thanks for your inquiry. Please upgrade to the latest version of Aspose.Words for .NET 16.3.0 and see how it goes on your end? What is the name/brand of the printer you’re getting these problems with? Have you tried some other soft-printer e.g. “Microsoft XPS Document Writer”?

In case the problems still remain, please attach the following resources here for testing:

  • Your input Word document you’re getting these problems with
  • Please create a standalone console application (source code without compilation errors) that helps us reproduce your problem on our end and attach it here for testing.

As soon as you get these pieces of information ready, we’ll start investigation into your issue and provide you more information. Thanks for your cooperation.

PS: To attach these resources, please zip them and Click ‘Reply’ button that will bring you to the ‘reply page’ and there at the bottom you can include any attachments with that post by clicking the ‘Add/Update’ button.

Best regards,

5

Hi Awais,



Thank you for your reply.



I’ve created a small console application and that works fine with the naming of the output in the spool queue. Strange, this needs more investigation because my original application still has the problem (only on the server, not on the local machine).

I think it has something to do with the fact that my Original application is running as a service and not as console application.



The speed issue is solved by using XPSprint.



Regards,

Michel van Vuren

6

Hi all,



I’ve found the cause of this issue:

Because on the server the service is running under a service-account, the name is not displayed to me when I’m logged on under my own account.

This is a policy issue. I’m not able to see the name because I’m not the job-owner.



Regards,

Michel van Vuren

7

Hi Michel,


Thanks for your inquiry. It is great you were able to resolve these issues on your end. Please let us know any time you have any further queries.

Best regards,
8

A post was split to a new topic: Printer printing blank pages