<?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>Netexceed blog by Jason Mohan&#187; Netexceed by Jason Mohan</title>
	<atom:link href="http://www.jasonmohan.com/tag/print-spooler/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.jasonmohan.com</link>
	<description>I am an IT professional who loves to stay on the leading edge of technology, and tries to tackle most commonly faced issues by computer users, and administrators.</description>
	<lastBuildDate>Mon, 19 Jul 2010 20:18:19 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Print Spooler nightmares?</title>
		<link>http://www.jasonmohan.com/windows/print-spooler-nightmares/</link>
		<comments>http://www.jasonmohan.com/windows/print-spooler-nightmares/#comments</comments>
		<pubDate>Thu, 25 Jun 2009 18:44:06 +0000</pubDate>
		<dc:creator>Jason Mohan</dc:creator>
				<category><![CDATA[windows]]></category>
		<category><![CDATA[print spooler]]></category>
		<category><![CDATA[spoolsv.exe]]></category>

		<guid isPermaLink="false">http://www.netexceed.com/?p=271</guid>
		<description><![CDATA[Got a print spooler that won&#8217;t start, or crashes everytime you start it. Well here&#8217;s a last resort fix that should bring it back up. However this will remove all printer drivers, print monitors, and printers off of the machine. If you are able to access the registry on the machine you can at least [...]]]></description>
			<content:encoded><![CDATA[<p>Got a print spooler that won&#8217;t start, or crashes everytime you start it. Well here&#8217;s a last resort fix that should bring it back up. <span style="text-decoration: underline;">However this will remove all printer drivers, print monitors, and printers off of the machine.</span> If you are able to access the registry on the machine you can at least write down the name, share name, ip, and printer driver used for each of your printers (see below for those instructions).  This instructions are for Windows Server 2003.</p>
<p><strong>Write down your current printers, drivers, and share names (if you can access the registry)</strong></p>
<p>1. Navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print\Printers</p>
<p>2. There you will see a listing of all the printers loaded on that machine.</p>
<p>3. Click on one of each of them, and you will see the NAME, PORT, and SHARE NAME of that printer.</p>
<p>4. You will need to write them down for each printer.</p>
<p><strong>Fixing and Cleaning the Spooler with CLEANSPL.exe</strong></p>
<p>1. Download the Windows Server Resource Kit at <a href="http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&amp;DisplayLang=en">http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-96ee-b18c4790cffd&amp;DisplayLang=en</a></p>
<p>2. Now run the cleanspl.exe tool that came with resource kit.</p>
<p>3. Remove everything <span style="text-decoration: underline;">except</span> these two, Standard TCP/IP Port, and BJL Language Monitor.</p>
<p>4. The tool will tell you to reboot your machine, reboot it.</p>
<p>5. After the reboot the spooler should be running once again, now comes the hard part of having to reinstall the drivers, and printers.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.jasonmohan.com/windows/print-spooler-nightmares/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
