<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Tech Ramblings from a Rainier Day &#187; Printing</title>
	<atom:link href="http://blog.rainiernetworks.com/tag/printing/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.rainiernetworks.com</link>
	<description></description>
	<lastBuildDate>Mon, 25 Jul 2011 23:10:16 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
		<item>
		<title>Spoolsv.exe with 100% CPU Usage</title>
		<link>http://blog.rainiernetworks.com/2008/08/26/spoolsvexe-with-100-cpu-usage/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=spoolsvexe-with-100-cpu-usage</link>
		<comments>http://blog.rainiernetworks.com/2008/08/26/spoolsvexe-with-100-cpu-usage/#comments</comments>
		<pubDate>Tue, 26 Aug 2008 15:59:21 +0000</pubDate>
		<dc:creator>David Wolfrom</dc:creator>
				<category><![CDATA[Troubleshooting]]></category>
		<category><![CDATA[Printing]]></category>

		<guid isPermaLink="false">http://blog.rainiernetworks.com/?p=9</guid>
		<description><![CDATA[We had an issue recently where there was a cpu lock on spoolsv.exe.  At first I figured it was related to some new drivers being installed (Trying to get an All in One printer to work in terminal services).  The ultimate fix was to delete some temporary spool files that had not automatically been deleted.  [...]]]></description>
			<content:encoded><![CDATA[<p>We had an issue recently where there was a cpu lock on spoolsv.exe.  At first I figured it was related to some new drivers being installed (Trying to get an All in One printer to work in terminal services). </p>
<p>The ultimate fix was to delete some temporary spool files that had not automatically been deleted.  These are found at</p>
<p>C:\WINDOWS\system32\spool\PRINTERS</p>
<p>Thanks to <a href="http://torque.oncloud8.com/archives/000384.html">http://torque.oncloud8.com/archives/000384.html</a> for the information</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.rainiernetworks.com/2008/08/26/spoolsvexe-with-100-cpu-usage/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

