Support Request: Print job doesn't start until Sitekiosk closed

Ticket ID: 6876	Creation Date: 5/6/2008 8:52 PM	Product: SiteKiosk Classic Windows	Attachment: -
TicketType: Support Request	Version: 6.6.213	Language: English
Views: 37936	Last Modification Date: 3/2/2009 2:13 PM	Platform: Windows XP Professional
Level: Closed	IE: 6.0
Bug Status: Not Fixed	User account: SiteKiosk Restricted User	Bug Frequency: On every start

Support Request: Print job doesn't start until Sitekiosk closed

Reproduction

Any print jobs started from apps running in side Sitekiosk will not print until Sitekiosk is closed out to Windows XP shell.

Description

> Are you using a network printer?
> Regarding your description you haven't installed the printer like described in the SiteKiosk help...
> Michael Olbrich

Yes, it is a network printer. And I tried following the instructions to create a local printer port with the IP address of the network printer.
However, I get the exact same problem. Print jobs are paused until I close Sitekiosk; when I'm back on Windows XP shell, the jobs suddenly starts and starts print everything.

Any help will be appreciated....

Answer: (1)
Re: Print job doesn't start until Sitekiosk closed	5/7/2008 11:58 AM
Hello, Regarding your description it seems that you have overlooked this part in the help: Important: 1. Make sure to set the simulated Local Port network printer as the default Windows printer. -->2. Open the SiteKiosk configuration file on this computer, and turn off printer monitoring for the non-simulated printer (the "real" printer).<-- However, leave printer monitoring enabled for "All installed printers." To do so, open the SiteKiosk configuration file and add and edit this printer as a standalone printer. Click on Add and select the "real" printer. Now, select this printer and click on Edit. Uncheck the option "Monitor printer and make available through SiteKiosk Object Model". Because if the printer monitoring is on the real printer driver and not on the local port (at the machine the printer is connected to) it leads to this behavior. Regards, Michael Olbrich