Priniting report causes error "2212 couldn't print object"

I've been looking for an answer to a particular question that has been puzzling me.

I've discovered this thread:

"The shared printer on the other PC is still functional, but on the PC where I want to run the report from, the shared printer in control panel says "opening" instead of "ready". I am unable to print a test page."

The symptopms I have been experiencing are very similar - though I have more background.

The background:

I've had to reinstall a bunch of printers following an update that's been made to a W2K server.  The update seems to have caused the print spooler to become corrupted so I've had to clean out the spooler subsystem .

I've since reinstalled the printers.

Now we have an app written in VBA using Access 2003 and it is set to default to one of the printers I have just reinstalled.  I have tested the printer and it does appear to work ok - however when I trigger the VBA to start the print job the printer returns error 2212.

I am perplexed and this is urgent.
Who is Participating?
puppydogbuddyConnect With a Mentor Commented:
see the attached link:

You are going to have to go down the checklist item by item unless there is a specific item that stands out as a problem in your installation.
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.

All Courses

From novice to tech pro — start learning today.