Al imprimir PDF se estropea la cola de impresion de windows - Printing PDF Files cause Print spooler to crash


http://www.defcon-5.com/support/index.cfm?docid=375

Resolution/Fix:

If you have not already you will need to remove the bad files from your print spooler.

  1. Stop the printer spool service by right clicking on your My Computer icon and selecting "Manage"
  2. Expand "Services and Applications" and the click on services
  3. Browse through the list of services and find "Printer Spooler".
  4. Right click on the "Print Spooler" service and select "Stop" if Stop is grayed out or disabled and "Start" is an available option, then the service is already stopped.
  5. Go to the c:\Windows\System32\Spool\Printers folder
  6. You should see some files in this directory with a .SHD file extension or a .SPL extension you will want to delete these. In some cases you may see other files in this directory as well, and in general it is safe to delete them. Files besides the .SHD and .SPL should be backed up before you delete them to be safe.
  7. You may either reboot the computer or Start the "Print Spooler" service manually.

Comentarios

Publicar un comentario

Entradas populares de este blog

Bypass WSUS to Install Features/Updates Directly from Windows Update

Bypass WSUS to Install Features/Updates Directly from Windows Update To fix the problem, temporarily bypass WSUS server using the following registry edit (requires administrator privileges). Right-click Start, and click Run Type regedit.exe and click OK Go to the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU In the right-pane, if the value named UseWUServer exists, set its data to 0 Exit the Registry Editor Restart Windows. Instructions from: https://www.winhelponline.com/blog/error-0x800f0954-net-framework-3-5-optional-feature-dism/
Leer más

Error ID 2011: Espacio de almacenamiento insuficiente en el servidor para procesar este comando

Para repararlo, se debe incrementar el parámetro IRPStackSize en el registro del servidor donde está el recurso compartido, en el ejemplo el Ordenador B. Aquí tenemos el valor de registro afectado: HKEY_LOCAL_MACHINE \SYSTEM \CurrentControlSet \Services \LanmanServer \Parameters IRPStackSize DWORD 0x0000000f (15) A veces un valor de 15 no es suficiente, y solamente valores entre 16 y 25 resuelven el problema. Intentamos primero con 16. Normalmente los valores con más éxito son 16 y 18, en caso de que no resulte se puede utilizar 20 o más. No debemos olvidar reiniciar la máquina tras realizar cada cambio, porque sólo así se hará efectivo el nuevo valor. Extraído de: http://konductasoluciones.blogspot.com/2010/01/error-id-2011-espacio-de-almacenamiento.html
Leer más