Announcement

Collapse
No announcement yet.

Command line printing from IIS failure

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • cherry
    replied
    Hi Falviani,

    Please provide the relative info to [email protected] and include the url of this thread. Thank you.

    Leave a comment:


  • falviani
    replied
    I'm sorry, but I don't know how going to a web page, clicking a button, and getting a "no errors" message - BUT NO OUTPUT - would be useful. Would you prefer that I upload the code instead? It's not very long.

    Leave a comment:


  • cherry
    replied
    Hi faviani,

    Could you please make a small video that shows the problem so we could know the issue intuitively? You may choose to upload it here or email it to [email protected]. Thank you.

    Leave a comment:


  • falviani
    started a topic Command line printing from IIS failure

    Command line printing from IIS failure

    I am trying to print PDFs from a web application without success. It is an ASP.Net site using ASP.Net version 2, running on a Windows 2003 service pack 2 system (NOT 2003 R2). I am using the "conventional" approach of launching Foxit Reader (most recent version) using the Process manager with a user that has rights to access the printers on the machine (not the network user that normally is associated with IIS). When I use the command window to print on the server (logged in via RDP) it works nicely. Launching it using the process manager from within the website is successful - I can see it in the task manager using 0% CPU cycles - but it does nothing and just exits when the WaitForExit() call times out. Can you make any suggestions as to what the issue might be? If needed I can post the actual printing code used.

    Thanks in advance,
    Frank Alviani
Working...
X