Windows 7 x86 - Cannot Connect to the Printer - Operation Failed 0x0000007e

Hello Experts,

I have 2 new Windows 7 clients that have an issue connecting to shared printers... It's a frustrating issue, and you should see why.

I have 3 Kyocera FS1128MFP fax printers (printer1, printer2, and printer3), setup and shared from a print server running Windows SRV 2003. The 1128 drivers are the newest available from Kyocera, and are compatible with Win7.

On the first client, I tried connecting to printer1, and it failed with the error:
- Windows Cannot Connect to the Printer - Operation Failed 0x0000007e

After I scratched my head, I tried installing Printer2 and it worked. It's the same driver! I tried Printer1, and it still failed. Rebooted, no change, tried Printer3, it worked, deleted printers, rebooted, and somehow I got Printer1 to install. Not sure what was changed...

On the second client, it was the exact opposite! Printer1 works, but printer2 fails! I've tried all the steps above, and deleted the driver many times from the Printer Manager, but I cannot get it to install...

I have also tried reinstalled the newest driver, and also tried installing locally. Local Install worked fine, but I want to find what the real issue is because we're going to start setting up more Windows 7 clients, and I would like to know what causes this.

Any ideas?
Thanks!
LVL 7
ottobockAsked:
Who is Participating?
 
ottobockAuthor Commented:
Hi. No news really.  
As mentioned, now the clients are fine, but this was only after some unknown fix. Now when I remove the printers and then the drivers from the Print Manager, I can no longer replicate the issue. So I'm stuck waiting to see if the problem reoccurs on the next set of Win7 clients.

My best guess is given the quirkyness of this issue, there is either a glitch in Win7 which will probabaly be patched sometime down the line, or there is a problem with the latest Kyocera drivers, which should also be fixed down the line.

The workarounds using local setup (instead of using the print server) is easy and valid for many ~ just not preferred for me.

But as mentioned, after installing/uninstalling/restarting/mix&repeat, it's all working fine using the print server ... so ... closing the issue for now with hopes this fixes itself with later deployments.

Thanks to all for your ideas and assistance.  
0
 
Aaron TomoskySD-WAN SimplifiedCommented:
I don't know why but I've found that sharing printers goes best from the same version/family of windows. So if you have win7 clients, my first choice is server 2008 r2 (i like 64). If you don't have a 2008 or 2008r2 server, sharing from one win7 box may work the best.

Any chance the printers are in different subnets or vlans or on different switches or something like that?
0
Cloud Class® Course: Microsoft Azure 2017

Azure has a changed a lot since it was originally introduce by adding new services and features. Do you know everything you need to about Azure? This course will teach you about the Azure App Service, monitoring and application insights, DevOps, and Team Services.

 
ottobockAuthor Commented:
Hi,
Thanks for the thoughts - I'll have a look.

I use Win7, and can connect to all 3 just fine. First time I saw this was with these 2 clients. They are on the same LAN and SN. Cant change servers at this time...
0
 
Aaron TomoskySD-WAN SimplifiedCommented:
So whats different about those two clients and your PC? Location? Switch? Sw firewall? Av? Uac?
0
 
ottobockAuthor Commented:
Nothing - this is why it's frustrating. They are both on my desk, both HP 8100 Elite SFF desktops, both Win 7 x86 SP1. They're the same!
0
 
ottobockAuthor Commented:
And as mentioed, now the first client is fine. Even after I remove the printer and reinstall it. My Win 7 laptop is fine. But the second client still has the error... grrr.
0
 
Aaron TomoskySD-WAN SimplifiedCommented:
Are they imaged? Same computer name or something confusing things?
0
 
ottobockAuthor Commented:
Factory image... Now I got it to work on the second client...
Installed Printer3 fine, printer1 fine, printer2 failed... Rebooted and printer 2 worked.
I dont know where the error is. Error logs are clean.  

Now I'm trying to replicate the error...
0
 
ottobockAuthor Commented:
Now I cannot replicate it. I've tried removing the printers and uninstalling/deleting the drivers, and after reboots, all 3 install fine as should be.

So I give up ~ if it's working, it's working. :-)
0
 
Gerwin Jansen, EE MVETopic Advisor Commented:
Hi, I've read this: http://answers.microsoft.com/en-us/windows/forum/windows_7-hardware/error-message-add-printer-connect-to-printer/a7fe6b93-5752-49a6-add7-0cf129b7b348

Did you try to connect using a dos command? Or just the printer add/remove wizard? Just curious to know if this would work for you:

net use LPT2 \\w2003server\kyocera1/persistent:yes
0
 
Gerwin Jansen, EE MVETopic Advisor Commented:
Any news?
0
 
Gerwin Jansen, EE MVETopic Advisor Commented:
Welcome :)
0
 
ottobockAuthor Commented:
Own solution includes the workarounds and observations made during problem TS. Points awarded to participants for time and effort. Thanks!
0
 
Gerwin Jansen, EE MVETopic Advisor Commented:
You're welcome :)
0
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.