K
kmyerqsv
Hello,
I am having an issue in two of my remote offices, where they will lose the ability to print after a connection drop, or at least that seems to be the trigger point for the issue. They will be working in the application, and a network blip will occur. The AppServer client will reconnect, but after that point, printing no longer seems to work. I can see the job was spooled on the server, by looking at Event Viewer logs, but nothing ever comes out the other side. One solution for them is to reboot their computer, which seems to clear things out. However, I am wondering why printing takes a hit, but everything else seems to keep plugging along.
Printer driver is the Universal 2X driver, AppServer client and server are both the latest builds of the version 6 release. Desktop OS is Windows XP, and Server OS is Win2K3 Enterprise.
Thanks,
Kevin
I am having an issue in two of my remote offices, where they will lose the ability to print after a connection drop, or at least that seems to be the trigger point for the issue. They will be working in the application, and a network blip will occur. The AppServer client will reconnect, but after that point, printing no longer seems to work. I can see the job was spooled on the server, by looking at Event Viewer logs, but nothing ever comes out the other side. One solution for them is to reboot their computer, which seems to clear things out. However, I am wondering why printing takes a hit, but everything else seems to keep plugging along.
Printer driver is the Universal 2X driver, AppServer client and server are both the latest builds of the version 6 release. Desktop OS is Windows XP, and Server OS is Win2K3 Enterprise.
Thanks,
Kevin