Problem connecting to a network printer. Error 0x000000d

Hi experts,

I just added Canon iR ADV C5240 printer along with the printer driver (x64) to the printer server on Windows server 2008 R2. When I go to the workstation running windows 7 x64 and try to add the printer, I am getting the following errors:
Connect to Printer - Windows cannot connect to the printer.
Operation failed with error 0x0000000d.

Any suggestion what might be causing this issue?

Thanks,
LVL 1
DeoraliAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Davis McCarnOwnerCommented:
Try this (Vista, 7, and 2K8 use the same driver modeling): https://support.microsoft.com/en-us/kb/947236
0
DeoraliAuthor Commented:
my registry settings already contains correct values pointing to correct printer driver
"Previous Names"=hex(7):(00 00 00 00)
0
Davis McCarnOwnerCommented:
The article says to look on the print server.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

DeoraliAuthor Commented:
Yes, the registry settings that I am referring to is on the print server.
0
DeoraliAuthor Commented:
Update: This might provide some clues.
I am able to install the printer on Windows Server 2008 R2 and Windows Server 2012 R2 machine without any issue. I am getting error only on Windows 7 workstations.  

Thanks,
0
sethu_uuuCommented:
Try to add the shared printer as local printer

https://www.youtube.com/watch?v=VbuXykWiFCM
0
DeoraliAuthor Commented:
Thanks. Looked at that option already but  need a separator page file to be printed at the start of each print job containing the username and some warnings.  This method prints a separator page with the IP address of the workstation and not the username which is a requirement.
0
sethu_uuuCommented:
Could you please try changing the print processor to winprint RAW, also try the canon universal print driver
0
DeoraliAuthor Commented:
By default print processor is set to winprint RAW.
0
Davis McCarnOwnerCommented:
Is this AD or a workgroup?
Have you tried using explorer to navigate to the server, finding the printer, then right-clicking on it and choosing connect?
0
DeoraliAuthor Commented:
Print Server in Windows Server 2008 R2 domain network.  Right clicking the printer on print server gives the same exact error. Pulling my hair out!
0
Jackie ManCommented:
Have you shared the printer?
0
DeoraliAuthor Commented:
Yes, this printer is added to the Windows Server 2008 R2 print server already and listed in the directory.
0
Davis McCarnOwnerCommented:
Everything keeps pointing back to that registry entry and according to the article I posted, the entry you posted is wrong which causes the problem.
"Previous Names"=hex(7):(00 00 00 00) is not the same as "Previous Names"=hex(7):00,00 Notice the comma and the lack of 4 sets of 00
Remember to restart the print spooler service!
0
DeoraliAuthor Commented:
Yup, I tried all those combinations and it didn't solve my issue.  https://support.microsoft.com/en-us/kb/947236
  - which specifies the values :
A valid value of the REG_MULTI_SZ registry value types can be in any one of the following formats:
•The value contains null only (00 00).
The value contains a valid ASCII representation of a string that points to a correct printer driver and ends with a double null (00 00 00 00)

I am not sure but there might be an issue with the server which holds print server. I installed the printer on different server without a print server, shared and listed in the directory. Now I am able to add the printer on all the w7 workstations without any issue.  I can deal with this as I am going to upgrade my Windows server 2008 R2 environment to Windows Server 2012 R2 and setup a brand new print server.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
DeoraliAuthor Commented:
Non of the solutions suggested resolved my issue. I took different path to resolve the issue temporarily.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.

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.