Shulou(Shulou.com)05/31 Report--

What is the solution to the four major errors of Server 2008 as a print server? in order to solve this problem, this article introduces the corresponding analysis and solution in detail, hoping to help more partners who want to solve this problem to find a simpler and easier way.

Using Windows Server 2008 as a print server platform is undoubtedly a very good choice, because it provides a powerful print management function to meet our various printing needs. However, because it is powerful, complex, and a system platform that is not so familiar to most administrators, it is troublesome to troubleshoot in the event of a print failure. Many managers seem to be at a loss as to where to start. The following will be combined with their own practice and absorb the experience of peers and netizens, on the Windows Server 2008 print troubleshooting ideas and steps to conduct a summary, I hope it will be helpful to everyone.

From the user's point of view, the printing failure is nothing more than "no one can print", "some users can't print", and "only one user can't print". Below, the author takes this as a clue to analyze the causes of printing errors, and talk about the corresponding troubleshooting ideas and steps.

1. No one can print

In this case, we can basically conclude that it is either the printer itself or the network problem. The way of troubleshooting suggested by the author is:

(1)。 Routine examination. We can check in front of the printer ourselves, and for Windows Server 2008, the status of the printer can be viewed through the printer's status page (enter the printer's IP address in the browser). If there is no problem, you should next check the event log of the print server and find error tips and warnings related to the printer to determine and troubleshoot.

(2)。 Check the print queue. Check in the print Service Manager to see if the printer is paused or if an error has occurred in any document. If so, right-click the documents and select the cancel command to eliminate them. (figure 1)

Figure 1

(3)。 Check the printer configuration information. If someone maliciously sets the printer to obtain an IP address dynamically, or does not set a reservation for the printer. In this case, if the printer is turned off and rebooted, it may be because its IP address has changed and the print port points to the wrong IP address. For this, we also need to check the status of the subnet where the printer is located.

(4)。 Check the network. We can use the ping command on a host to level the printer's IP address. If you cannot ping the printer's IP address from any host, this indicates that the printer may be turned off or the network may be disconnected. In addition, there may be a failure of the printer's network card, or a problem with the switch or router connected to the printer.

(5)。 Retrieve changes in printer configuration. You can ask or recall when the printer last printed normally and whether the configuration of the printer has changed. If the printer has never worked properly, there is a problem with the configuration in the first place. If there is a change in the configuration of the printer, it is recommended to revert to the previous configuration if possible. If it is suspected that it is related to the printing device, we can try to uninstall and reinstall the printer driver.

(6)。 Detect disk space. This is usually ignored, and it is necessary to check the free space on the disk where the background print folder is located, because it can also cause print failures. If the free space of the partition is low, or there is no free space, the print server will not be able to create a spooled file, so the document will not print. In addition, we should also check the permission settings of the print folder. If there is a problem with the permission settings, background printing cannot be carried out either. (figure 2)

Figure 2

(7)。 Detect print processor and split page settings. Be sure to make sure that the print processor and split page settings are correct. If the wrong print processor is set, the printer may print garbled or cannot print at all. For Windows Server 2008, we can try to use either the RAW data type or the EMF data type, which usually solves the problem. If the split page is set incorrectly, the printer may print only the contents of the split page, or it may not be able to print at all. Therefore, we also need to check the settings for split pages.

(8)。 Check the Print Spooler service. Set the service to start automatically with the system, but if the service fails to start twice within 1 minute after the system starts, the Print Spooler service will no longer attempt to restart. At the same time, if there is an erroneous document in the print team and cannot be cleared, it is usually possible to cause an error in the Print Spooler service. In this case, we can first clear the error document from the print team, and then open the print service console, where we can find the Print Spooler service to start it manually. (figure 3)

Figure 3

2. Some users cannot print

This situation shows that some users can print, but some users cannot print. For this kind of printing failure, we can sum up three reasons: improper printing permission setting, application causing printing error, and network causing printing error. In that case, our troubleshooting can be carried out from the following aspects:

(1)。 Network detection. Network detection in this case is different from * *. We can choose to detect users who encounter print errors and other users who are in the same subnet. The detection method is still using the Ping command. Execute the "ping PrinterIP" command at the command prompt on Windows Server 2008, where PrinterIP is the IP address of the printer. If no computer from this subnet can ping the IP address of the printer, this means that the switch or router between the user's computer and the printer has gone wrong or disconnected. At this point, we focus on the router or switch for machine detection or configuration check.

(2)。 Permission check. The permissions here mainly refer to the permissions settings of the printer and the background print folder to ensure that specific users or user groups have access rights. If the permissions are set incorrectly, the background printing cannot be carried out, and the printing will go wrong.

(3)。 Detect the print processor. If there are many system types of clients in the domain or local area network, it is necessary to detect the print processor. Because clients based on Windows 98 and Windows me can only use the print processor of the RAW data type for printing. Printing based on the RAW data type is processed on the client, so the print server needs to handle the least work, while the EMF data type needs to send a large print server for processing. If we encounter this kind of error, we can modify the default data type of the printer. Open the printer properties dialog box, switch to the Advanced tab, and then click the print processor button to open a dialog box where we can change the current print processor and the default data type. (figure 4)

Figure 4

(4)。 Check the program used for printing. If there is a problem with the configuration of the application that calls the printer to print, it can also cause a print failure, for which we can re-check the configuration of the printer to see if there is any misconfiguration. For example, this type of print error can occur if you choose the wrong default printer.

(5)。 View print error messages. Pay special attention to the error messages generated in the printing process, which is a powerful clue for us to troubleshoot. For example, if the client encounters an error message when connecting to the printer that the printer driver must be installed, this means that the correct driver is installed on the print server, but cannot be used on the client. In this regard, we must manually update the client's print driver.

3. Only one user cannot print

If you encounter that only one user can't print, it's not a big problem, but it's not easy to debug. This is usually caused by software, the user's computer, or improper permissions. For this type of error, it is recommended that the user restart the computer and then reprint the test. If not, you can troubleshoot from the following aspects:

(1)。 Check the program used for printing. Similar to the situation above, we first check to see if it is caused by a configuration error in the application that called the printer. In addition, we also check to see if the default printer set by the user is incorrect.

(2)。 Check the user computer. First check to see if the Print Spooler service is working properly on the user's computer system, and start the service manually if not. At the same time, check whether the user's computer disk has enough temporary space to generate the initial spooled file. In addition, other important services on the computer should be started normally. If there is a problem with the related service, start it manually. If it cannot be started, it is necessary to debug the service, in short, to ensure that it starts normally. In general, we set the service to start automatically, and then restart the system to solve the problem.

(3)。 Check the network connection. Check and confirm that the user's computer can connect to other resources through the network, and usually we test the connectivity of the host to the printer through the ping command.

(4)。 Check for error messages. Similar to the above method, we should pay attention to the print error message received, for example, the client receives an "access denied" error message, which indicates that there is something wrong with the permission setting, and we can modify the print permission accordingly.

(5)。 Check the permission settings. Similarly, we need to check the permission settings of the printer to confirm that the user is denied access. In addition, make sure that the user has access to the spooled folder.

4. error confusion, printing and troubleshooting

From the user's point of view, the classification of printing errors seems to have omitted a kind of typical printing errors, that is, error chaotic printing, so it is necessary for the author to list them separately for troubleshooting analysis. If the content of the printer is confused or there is an error, it is usually caused by the misconfiguration of the printer. The idea for this type of print troubleshooting is:

(1)。 First of all, check whether the printer driver is wrong, and update the correct print driver immediately if there is any error. In addition, check to see if the print processor is set up incorrectly, and usually we can solve the problem by changing the print data type from EMF to RAW.

(2)。 Detect the print management configuration. Right-click the printer in the print management console, select Properties to open the printer properties dialog box, and then switch to the Advanced tab to select the option to start printing when you have finished printing a page in the background. To ensure that the complete document content is transferred to the printer before printing. (figure 5)

Figure 5

(3)。 Check the split page settings. In the printer properties, under the Advanced tab, click the split Page button, and then we can try to delete the split page we used. Because the use of the wrong print page description language in the use of split pages can also lead to chaotic printing. (figure 6)

Figure 6

(4)。 Disable the advanced printing feature. In the printer properties, under the Advanced tab, cancel enable Advanced Printing

Option to disable metafile spooling. Because in networks with complex system types, enabling this feature may lead to chaotic printing. (figure 7)

Figure 7

Summary: the above summary of ideas and steps for print troubleshooting is aimed at the print server on the Windows Server 2008 platform, but many of them are also applicable to Windows Server 2003.

This is the answer to the question about what is the solution to the four major errors of Server 2008 as a print server. I hope the above content can be of some help to you. If you still have a lot of doubts to be solved, you can follow the industry information channel for more related knowledge.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.