In some instances, you might receive Error — "The dependency service or group failed to start" — when attempting to start the Print Spooler. This can happen if the Print Spooler service relies on other services that are not running. To resolve this issue:. For additional troubleshooting assistance with the printer or network print device, contact the manufacturer of the printing device.
To determine whether the computer is low on system resources such as memory, generate a System Diagnostics Report, which presents system information collected for 60 seconds. Note : To perform this procedure, you must be a member of the local Administrators group on the print server, or you must have been delegated the appropriate authority.
To install a new printer for a printer, use the following procedure. Note that client computers automatically download and install the updated printer drivers the next time they attempt to print to the printer. Note: When installing printer drivers that are provided by the device manufacturer, follow the instructions provided with the printer driver instead of using this procedure. To support client computers that use different processor architectures than the print server, you must install additional drivers.
To add client printer drivers to the print server, click the Sharing tab in the Properties dialog box and then click Additional Drivers.
Locate the Print Spooler service in the list of services, and then confirm that its status is Started. If its status is not Started, select the service and then click Start on the Action menu. Click the Dependencies tab. The first box lists all of the system services that must be running for the print spooler to start. These are the dependencies.
Make a note of each service, click OK, and then start each service that the print spooler depends on, if the service is not already started. If a particular service is not already started, right-click it, click Properties, and then confirm that the Startup type is Automatic.
Ping the printer or network printing device again. If you continue to have problems, replace the network cable and try using a different network switch. Retry connecting to the printer from the print server.
Check resource availability To determine whether the computer is low on system resources such as memory, generate a System Diagnostics Report, which presents system information collected for 60 seconds Note: To perform this procedure, you must be a member of the local Administrators group on the print server, or you must have been delegated the appropriate authority. To collect system information for 60 seconds and generate a System Diagnostics Report: Open an elevated Command Prompt window.
Reliability and Performance Monitor will start collecting data to create the System Diagnostics Report. When the report is ready for viewing, locate the Diagnostic Results section of the report, and then check for any warnings indicated by Warnings in the report. You can follow links to additional help on resolving warnings from this section. In addition, you can expand each category in the Basic System Checks section to see more details about why warnings appear.
Also, the Performance section provides process-level details about top consumers of resources. You might need to increase the size of the paging file or add physical memory. Install a new printer driver and possibly disable advanced printing features To resolve this issue, do one or both of the following: Install a new printer driver.
Disable advanced printing features. Install a new printer driver To install a new printer for a printer, use the following procedure. Right-click the printer with the driver that you want to change or update, and then click Properties.
Click the Advanced tab. Select a new driver in the Driver box, or click New Driver to install a new printer driver. Disable advanced printing features To disable advanced printing features: Right-click the printer, and then click Properties. You can enable this again or attempt to get all the parts of the print driver installed on the client. I suggest just enabling GDI on the server for the drivers that show a problem with this configuration.
The spooler crashes are normally caused by print drivers corrupting the memory of the spoolsv. You can hit failures when the driver does not handle previous configuration settings and you are migrating to an updated version of the driver or during the printing process when the driver does not properly handle a specific type of job class. When the spooler restarts, the memory is reset. It will grow as you have more clients connected to the server. GDI resources would be something to check.
If you are near the object limit you will also hit event A busy print server should not have more that a couple If you see 0 you need to be logged onto the Console session. GDI objects are per process so restarting any process resets the object count to 0. What is the print processor used by DBFX? I've been monitoring the GDI resources for the whole week but it so far it stays between And also, there is no event logged since this event occurs for the past couple of weeks.
My previous statement is incorrect. What i'm trying to say is that i haven't tried installing new printer driver because i need to understand why the problem resolves at least for couple of days.. Yes you are okay with the GDI resources. On the printer properties Advanced tab uncheck Enable Advanced printing features.
0コメント