"Printer Spooler failed to reopen error" - Server 2008 RW

Posted on 2010-03-23
Medium Priority
Last Modified: 2012-06-22
I have a problem with a terminal server environment I have set up.  There are 3 locations to this set up.  I have a VPN set up at all locations, which is functioning properly.  The server has 2008 R2 64-bit installed, and is acting ONLY as a terimnal server, not a domain.  

The problem I am having is with printing.  I originally added the printers to each remote user by sharing the printer off the user's local machine, then pathing to it ("//computername/printer").  I have verified all the drivers are Server 2008R@ 64-bit compatible as well.  Whats happening the sites will randomly lose their printers.  When this happens I have to recreate the printers by pathing to the IP address instead of the name (//, which allows the printers to be installed.  Then at random times the IP address mapping will fail, and I have to map to the name again.  

I checked on the server event viewer and keep seeing error's that read :

"The print spooler failed to reopen an existing printer connection because it could not read the configuration information from the registry key S-1-5-21-4019898469-3110971113-3073775663-500\Printers\Connections\,,computername,HP Deskjet 6500 Series. This can occur if the key name or values are malformed or missing."

I am assuming this has something to do with the problem but I have not been successful at identifying what is causing the problem.
Question by:Consolidated_Telcom
1 Comment
LVL 33

Accepted Solution

digitap earned 1500 total points
ID: 28358475
I'm puzzled as to why the printers aren't mapped through the TS session.  If the driver isn't available, then you should get an Event log error indicating that a driver could not be found.  Otherwise, you shouldn't have to manually map the printers to the server from the user's workstations.  Did you manually install the drivers by going to Printers > Server Properties > Drivers?  Is the driver on the user's workstation PCL6, PCL5?  Whichever is on the user's workstation, it must match exactly to what's on the server.  If it's PCL6 on the workstation then it must be PCL6 on the server.

If not, then try this.

Go to HKEY_USERS\S-1-5-21-4019898469-3110971113-3073775663-500\Printers. Right click and create a new key named 'Connections'.

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

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

Welcome to my series of short tips on migrations. Whilst based on Microsoft migrations the same principles can be applied to any type of migration. My first tip is around source server preparation. No migration is an easy migration, there is a…
Welcome to my series of short tips on migrations. Whilst based on Microsoft migrations the same principles can be applied to any type of migration. My first tip Migration Tip #1 – Source Server Health can be found here: http://www.experts-exchang…
Watch the video to know how one can repair corrupt Exchange OST file effortlessly and convert OST emails to MS Outlook PST file format by using Kernel for OST to PST converter tool. It can convert OST to MSG, MBOX, EML to access them. It can migrate…
Through the video, you can check the migration process of Outlook PST file to PDF. Kernel for Outlook to PDF tool can convert Outlook emails with all attributes like Subject, To, From, Cc, Bcc and other folders such as Inbox, Outbox, Sent Items, Jun…
Suggested Courses

624 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question