Windows print server delay troubleshooting




















Get answers from your peers along with millions of IT pros who visit Spiceworks. Anyone know what I can do to remedy this? Best Answer. Ah yes. View this "Best Answer" in the replies below ». Popular Topics in Windows Server. Selecting certain paper types or printing in Best quality can slow print speeds. Print with plain paper in Normal or Draft quality for faster print speeds. Search Windows for printers, and then click Devices and printers in the list of results.

In the Quality Settings area, make sure Draft or Normal are selected. Remove the print driver and software using the Uninstall a program tool in Windows Programs and Features. Uninstalling the print driver allows you to install the latest driver version.

If your printer connects to the computer with a USB cable, disconnect the cable from the printer. Search Windows for programs and features, and then click Programs and Features in the list of results. In the list of installed programs, click your HP printer name, and then click Uninstall or Yes. By the end of this article all the issues should be resolved. Worked great with windows 7. Now with windows 10 i tried everything.

Uninstalled and removed everything. Then I put all new on program and drivers. Takes 15 to 20 seconds to start printing. We pay a lot of money to HP and I feel they should come up with a solution. Window 10 been out a long time and HP has no solution? Very sad. Yes I did all of them things which I should never of had to do. These settings may be unique to the make, model, and driver. If your server name is more than 15 characters, the Windows spooler will actually lop off the end of the name to shorten it to 15 characters.

This is a longstanding Windows limitation. To avoid any problems, keep it short! Especially if you have plotters or wide-format printers or CAD-related printing in your environment - they normally mean huge spool files! Find out more about this here. Disable printer redirection on any dedicated print server. This will cause a failure in the spooler service when print drivers not written for enterprise environments get installed due to printer redirection.

Follow the guidance from Microsoft regarding this configuration on the machine. If you need to deploy your print queues, check out Print Deploy! Here is the tour page about it and also the Print Deploy Help Center if you want to learn more about it. Let us know! If you suspect that the print subsystem has a problem, you can also use the Print Verifier feature of AppVerifier to examine the print subsystem in greater detail.

The Print Verifier feature is described later in this document. Print Verifier is a feature of AppVerifier that provides additional monitoring of the print subsystem. By enabling the Print tests in AppVerifier, you can test how applications call the print APIs and detect problems in applications and printer drivers.

Configure AppVerifier and the Print Verifier feature to monitor the print subsystem by entering the following command in a command window:. After configuring the AppVerifier, you might be required to restart the computer for the settings to take effect. At the very least, you must restart the print spooler service. Do Not:. Only use the AppVerifier on the spooler process to troubleshoot a problem, do not enable these options if you are not troubleshooting a printer subsystem problem.

Once the problem has been resolved, configure the AppVerifier to stop monitoring the Print Spooler process. Figure 1: AppVerifier Config 1. Figure 2 : AppVerifier Config 2. The spooler includes additional debugging features that you can configure in the system registry.

Use regedit. Use extreme caution when modifying the registry directly. Modifying some areas of the system registry can cause serious problems with the operating system.

Make sure that you back up the registry and know how to restore it before you make any edits. The following section describes how to configure the spooler debugging features in Windows Server To explicitly control whether the system terminates the spooler when it encounters an error in the spooler, create a subkey named TerminateOnFatalException under the following registry key:.

By default if the value is missing from the registry key or the registry key is missing , terminating on an error is enabled. If this feature is disabled, the spooler's exception handler allows the exception to pass to the next available handler, which is Service Control Manager SCM. To enable the system to break into the debugger when it encounters an error in the spooler, create a subkey that is named BreakOnFatalException under the following registry key:.

By default if the value is missing from the registry key or the registry key is missing , breaking on an error is disabled. A later section of this document describes how to view the log. The Print Spooler process contains an internal that is designed to handle the following exceptions:. Instead of manually creating the registry keys to configure the spooler for debugging, you can create a registry script to create the registry keys.

Load the script into the registry by using regedit. The following text is a registry script that can be saved as a text file and used to configure the spooler for debugging in Windows 7. To create this file, run Notepad and copy the following text into Notepad:.



0コメント

  • 1000 / 1000