I have a Win7 64-bit Toshiba Satellite laptop and a HP 8600 Pro Plus,
updated firmware and drivers about 2 weeks ago for the 8600 been a
long time since I updated, which is connected wireless decided to
setup Wireless Direct Printing once setup I tried to do a windows
Print Test Page in the printer property panel, kinda normal for
setting up a printer
Under the Wirelees connection I got the Error message 0x00000057
Under Wireless Direct Printing I got the same Error 0x00000057
After spending time verifying settings, connections and asking
why? I decided to see if I could print docs, I did print a PDF,
Notepad and Word documents in each application under both
configurations no problem.
Under the wireless Connection I started the Web Services module
and was able to do the Print Test page within the Web Services
module no problem yet could still not do the Print Test Page
within the Printer properties panel.
I did run Print and Scan Doctor which to my surprise mentioned
a Driver conflict I allowed this program to uninstall the driver,
went to look up the driver and the same driver was listed so did
not download but did remove the driver and reinstalled the driver.
Error message still there.
I am now tempted to remove Wireless direct printing and see
what happens, if the error goes away, if not unstall everything
related to the printer and do a clean reinstall. Under an emergency
is there an alternative to using the Web Service module to setting
up when not connected to the wirless network?
I'm thinking the printer panel would do this (I'll look into this later
spend enough time on this), or do I need to run Web Services to
setup Wireless Direct, just thought about this otherwise I'll pull
out a usb cable. Maybe if I setup Wireless Direct on the printer panel
the message will go away being setup on the printer not software
on the laptop?
It's a minor issue since I can still print but the question remains Why!
Seeing other questions regarding this error message thought I
would pass my experience with this error.
Still got a couple of things to think about and try, Another time.
If your getting this error message I suggest trying a print test page
within Web Service module to see if the message come up.