Windows:- Guidelines for troubleshooting Print & Print Spooler Issue

-

For all the Print & Print Spooler Issue Kindly follow  below guidelines before clearing the Print Spooler and restarting the Spooler Service.

1)Check for event log for all print related information.

>> For Windows Server 2003 & Windows Server 2008   print related information will be present in System Event Logs


>> For Windows 2008 R2 and above this log will be Present in below Location


Windows 2008 R2: Server Manager --> Event Viewer --> Applications and Service Logs --> Microsoft --> Windows --> Print Service --> Operational log


Windows 2008 R2: Server Manager --> Event Viewer --> Applications and Service Logs --> Microsoft --> Windows --> Print Service -->Admin log

 

2) Check Printer Status – This will help you to check if any issue related to specific printer , like in what status and state  is the printer.


Printer Status

If you want to get information about printers you could use the Win32_Printer class.

 

Get-WmiObject Win32_Printer

 

Example:

Get-WmiObject Win32_Printer | Out-File -FilePath C:\Users\adna-9desai9\Desktop\Spool\PrintersInfo.txt 

 

 

Printer status will indicate the current condition of the printer as one of the following:

 

1: Other

2: Unknown

3: Idle

4: Printing

5: Warming Up

 

 

Printer State

Status Code (Decimal)          Status Code (Hex)     Description

0          0          Printer ready

1          1          Printer paused

2          2          Printer error

4          4          Printer pending deletion

8          8          Paper jam

16        10        Out of paper

32        20        Manual feed

64        40        Paper problem

128      80        Printer offline

256      100      IO active

512      200      Printer busy

1024    400      Printing

2048    800      Printer output bin full

4096    1000    Not available.

8192    2000    Waiting

16384  4000    Processing

32768  8000    Initializing

65536  10000  Warming up

131072            20000  Toner low

262144            40000  No toner

524288            80000  Page punt

1048576          100000            User intervention

2097152          200000            Out of memory

4194304          400000            Door open

8388608          800000            Server unknown

6777216          1000000          Power save

 

3) Get the information Related to spooler Print queue – This will help you in knowing the details such as number of jobs, Job errors ,NotReadyErrors,OutOfPaperErrors ,TotalJobsPrinted,TotalPagesPrinted,Printer Name etc.

 

Information regarding the Print queue could use the

 

Win32_PerfFormattedData_Spooler_PrintQueue class.

 

Example:

Get-WmiObject Win32_PerfFormattedData_Spooler_PrintQueue | Out-File -FilePath C:\Users\user-name\Desktop\Spool\Spooler.txt 

 

4)Take Process Dump for “spoolsv.exe”

If we are unable to get much information from above 3 steps due to spooler being in hung state or any other reason- Kindly take a process dump for “spoolsv.exe” , which can be used for further analysis.

Steps for Taking Process Dump for Spoolsv.exe.

a)On the Print Server open task manager and go to the Processes tab

b)In The Processes tab locate spoolsv.exe process

c)Right click on spoolsv.exe and click on Create Dump File

 

d) The Dump  file will be created under  C:\Users\AD528B~1\AppData\Local\Temp\spoolsc.DMP

 

 

Comments

Post a Comment

Popular posts from this blog

VMware:- Esxi Log File Locations

-
Enable SSH and connect the host through CLI tool-  *Authentication- /var/log/auth.log *ESXi host agent log - /var/log/hostd.log *Shell log - /var/log/shell.log *System messages - /var/log/syslog.log *vCenter Server agent log - /var/log/vpxa.log *Virtual machines - The same directory as the affected virtual machine's configuration files, named vmware.log and vmware*.log. For example, /vmfs/volumes/datastore/virtual machine/vmware.log *VMkernel - /var/log/vmkernel.log *VMkernel summary - /var/log/vmksummary.log *VMkernel warnings - /var/log/vmkwarning.log *Quick Boot - /var/log/loadESX.log *Trusted infrastructure agent - /var/run/log/kmxa.log *Key Provider Service - /var/run/log/kmxd.log *Attestation Service - /var/run/log/attestd.log *ESX Token Service - /var/run/log/esxtokend.log *ESX API Forwarder - /var/run/log/esxapiadapter.log
Read more

ESX and vCenter Alarms

-
Image
  Definition An  Alarms  is a   notification  that are activated in response to an event, a set of conditions, or the state of an inventory object. An alarm definition consists of the following elements in the vSphere Client: ·  Name and description - Provides an identifying label and description. ·  Targets - Defines the type of object that is  monitored. -  VM\  DataSore \N\W  etc. ·  Alarm Rules - Defines the event, condition, or state that triggers the alarm and defines the notification severity. It also defines operations that occur in response to triggered alarms. ·  Last modified - The last modified date and time of the defined alarm.   Alarm categories – Alarms have the following severity levels: ·  Normal –  green  -   Status is Good. The health of the object is Normal ·  Warning – yellow  -  Status is Warning – The Object experiencing Some Problem ·  Ale...
Read more

Convert VMware Snapshot into Memory Dump

-
Image
  Convert VMware Snapshot into Memory Dump Background   This document explains about generating a memory dump for a VMWare Virtual Machine when the machine becomes unresponsive. VM becomes unresponsive for various reasons, you may not be able to get into any OS related settings or access any application. Even users may get not be able to access any shares or resources of this machine.   In this type of situation Memory dump would be required to  analyze  the cause. Even if the OS is configured to generate a Memory Dump for System Crashes, it would not be able to generate a Memory Dump for System Unresponsiveness most of the  times. But  with a VMWare VM, you can take a snapshot of the machine when it is unresponsive and then use vmss2core.exe tool to convert the snapshot to a Memory Dump. The target audience for this information is any technician that is responsible for creating and deleting snapshot in the Levi virtualization environment.   Note ...
Read more