• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 5326
  • Last Modified:

Print spooler service crashing every half hour

Every half an hour the spooler service crashes on my 4month old 2008r2 sp1 print server. This server supplies 2x citrix xenapp servers and has the citrix universal print service etc installed on it. Enabled print driver isolation and set all drivers to isolate mode but make any difference.

Help!!
0
Gostega
Asked:
Gostega
3 Solutions
 
Haresh NikumbhSr. Tech leadCommented:
any failure event log for this?
0
 
GostegaAuthor Commented:
Yes, 7034/7036. No others. There were some driver specific ones on Thursday,  but after I removed those 3 printers, those have disappeared and only the service failure event appears.
0
 
Haresh NikumbhSr. Tech leadCommented:
In event 7034, what is description?
0
Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

 
GostegaAuthor Commented:
"The print spooler terminated unexpectedly. It has done this 64 times."

There is no other text. This is in the system section of the event log.
There is a similar entry in the Application section, which has a description as follows:

"Log Name:      Application
Source:        Application Error
Date:          9/06/2013 1:28:10 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      JSRS45
Description:
Faulting application name: spoolsv.exe, version: 6.1.7601.17777, time stamp: 0x4f35fc1d
Faulting module name: wsdapi.dll, version: 6.1.7601.17514, time stamp: 0x4ce7ca31
Exception code: 0xc0000005
Fault offset: 0x000000000006ad4a
Faulting process id: 0x11b8
Faulting application start time: 0x01ce646a7905ce64
Faulting application path: C:\Windows\System32\spoolsv.exe
Faulting module path: C:\Windows\System32\wsdapi.dll
Report Id: c979b4dd-d060-11e2-b482-00155d000f2f
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-06-08T17:28:10.000000000Z" />
    <EventRecordID>7738</EventRecordID>
    <Channel>Application</Channel>
    <Computer>JSRS45</Computer>
    <Security />
  </System>
  <EventData>
    <Data>spoolsv.exe</Data>
    <Data>6.1.7601.17777</Data>
    <Data>4f35fc1d</Data>
    <Data>wsdapi.dll</Data>
    <Data>6.1.7601.17514</Data>
    <Data>4ce7ca31</Data>
    <Data>c0000005</Data>
    <Data>000000000006ad4a</Data>
    <Data>11b8</Data>
    <Data>01ce646a7905ce64</Data>
    <Data>C:\Windows\System32\spoolsv.exe</Data>
    <Data>C:\Windows\System32\wsdapi.dll</Data>
    <Data>c979b4dd-d060-11e2-b482-00155d000f2f</Data>
  </EventData>
</Event>
"
0
 
GostegaAuthor Commented:
http://social.technet.microsoft.com/Forums/en-US/windowsserver2008r2general/thread/3122dbde-6317-455d-ae71-bb52090cc275

http://aaron-kelley.net/blog/2010/08/wsd-printers-crashing-print-spooler-service-in-windows-7/

I suspect my problem is the same as described in those links. I checked my port list and sure enough some of the ports have changed to weird ass WSD ports instaed of normal ports. I will try removing those printers and re adding, luckily it's only about 5 out of 40.
0
 
basrajCommented:
You can run StressPrinter tool to find the driver that is crashing your environment. The below link shows how to download and use this application

http://support.citrix.com/article/CTX109374

Also use this print detective tools that tells the printers that are not supported by Citrix.

http://support.citrix.com/article/CTX116474
0
 
GostegaAuthor Commented:
Thanks basraj.
When I try to run StressPrinters it says "The RPC server is unavailable"
0
 
Patrick BogersDatacenter platform engineer LindowsCommented:
Hi

Every 30 minutes a crash sounds to me something else is not going right. Did you check the basics like scandisk and SFC ? Did they come back clean?
0
 
GostegaAuthor Commented:
Yeah all clean

I have resolved. Thanks to those who responded.
This was my issue:
http://aaron-kelley.net/blog/2010/08/wsd-printers-crashing-print-spooler-service-in-windows-7/

When adding a couple of printers a week or two ago, I must have misclicked and left them on "Autodetect" instead of manually selecting port type as TCP/IP which I usually do.

As a result, Windows detected them as Web Services printers and created WSD ports for them.

I deleted the offending printers (you can't manually delete a WSD port it seems) and re-added them, making sure to select "TCP/IP" instead of Auto.
No crashes since I did that this morning.
0
 
GostegaAuthor Commented:
I resolved it myself by searching on the net. I have accepted the comment by basraj as a part solution as his links to citrix stress printers and printer detective were very useful and likely would have detected the cause if I had been able to run them.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now