Error 2 Printer

[Destini Armstrong]

Iam running windows 10 on a dell optiplex 5050 with a HP officejet 6970 all-in-one printer over a network connection. All computers are running on the most up-to-date windows updates, but this problem had occurred before the most recent updates so I am not sure if it is a previous update that may have caused the problem.

The problem is that one computer in the office can not print to the printer but the rest of the computers can. With this particular computer I can scan fine just not print. On printing a document a alert appears on the bottom right corner of the screen "Can not print on HP Officejet 6970" and on the print queue under print status is "error - printing". Not on the most recent reinstall of the printer driver/software but before there was also "driver is unavailable" message under the printer in printer and scanner section of windows settings. Now when trying to print from this particular computer it shows the "Default, Error"

I feel at this stage I have went through every possible troubleshoot in the book, short of a full OS reset. I do not want to have to do this as this computer also acts as the server computer for the 3rd party software used on all computers within the business and to reset the computer would most likely result in having to close for half a day at the very least.

Check what type of interface port the print driver is using. Windows likes to default to using a WSD port, however these are unreliable. If it is using a WSD port, change the port type to Standard TCP/IP and configure the port to the IP address of the printer.

You are a life saver. I've been trying to resolve this issue for a week with no luck. I uninstalled the printer software, updated the print drivers and event HP doctor. You hit the head on the nail. Windows had defaulted to the WSD port. I changed it the standard TCP/IP and reconfigured the IP address and it worked. Thanks so much for posting this solution.

I'm using the imageclass MF733dw. Attempts to scan a document to my desktop generates "Google Cloud Print Communication Error". Printing and copying functions are fine. I have restarted both the desktop and the printer to no effect.

The downside of part 2 here is that this is a reset of the printer, so you might lose all the data you stored in the printer/fax/etc. When completed, you will have to reset things like the language, time zone, and day/time on the printer. But this additional step was what was required to get the error light to stop blinking.

I am constantly getting a "google cloud communication error" message before printing. Since I purchased the printer I have had a blinking yellow light on the console. I am only allow to print after I shut off the system and turn it back on. Any help would be approciated. I am working from a Surface 4 Proi5. I also have the same issue from my Mac.

I too was getting the amber error light blinking on my MF247dw and error message was Google Cloud Print error. I used the method above (remote user login to system manager account) to turn off Google Cloud printing since it is no longer available, but I also had to "unregister" to get the error light to disappear.

This is bug in the firmware, we will release a new version to address this problem. It will be release version soon. For now If you found the screen lock up, you may need to format SD card on the touchscreen to resolve.

Dear Jason,

Glad to hear that you are working on a fix - my printer has stopped with this problem. I will see if the solutions the users suggest above will work, but I hope that you can provide a fix very soon.

thanks, Alan

I have been using old versions and change setting in my system then it is not working because of old that is not compatible with my system. Ricoh printer has approached to install a new version to fix the problem

I was getting this message periodically. I ran the troubleshooter on my printer and for some reason the print spooler was not starting automatically. Troubleshooter "fixed" the problem and I was able to print.

QUICK SOLUTION. Had this same problem of needing to install the printer even though my printer printed fine for other docs. But I noticed that some CS4 files were able to print while others not. So I simply opened another few file, split screened the two docs, and simply copied the old layers to the new doc. During the process, I confirmed that the new doc showed printer properties window when promted to print. So wala! Problem solved! This will save you some serious time. : ) Just got an urge to share that Jesus loves you very much. Me too. : )

I can't start a print with octoprint, after starting it it only executes the commands to set the bed and hotend temperature and then the printer returns an error that makes the printer stop and turn it off accordingly (I have a relay module that turns off when the printer instructs him to do so)

the problem lies in the pause commands after the activation of the heating (M190 ED M109) .... after these commands it goes into error. I had a backup of octoprint dating back to yesterday, before doing the update that came out today on some plugins if I'm not mistaken or directly on octoprint. I restored that backup and it makes the same mistake but if you delete the M190 and M109 commands everything works except obviously the fact that the print starts before the temperature reaches the target.

kill() can only ever be called by the printer, and it does this to shut down ASAP when it detects there is something wrong. OctoPrint has nothing to do with calling this, so you need to look at the printer. Check all of the connections, particularly the heaters and the thermistors, since the errors seem to be temperature rated.

is a self-built printer with skr1.4 and latest version Marlin firmware. the error is recalled by the printer yes but it does it only with octoprint, from sd it does not give errors, from repetier host connected with usb it does not give errors ... I suspect that octoprint starts after the wait commands (M190 and M109) to send the extrusion commands and obviously the printer returns that error. the suspicion becomes almost certain from the moment I have enabled cold extrusions and actually the extruder motor starts spinning and immediately afterwards the printer stops calling up the error. so i don't think it's the firmware but octoprint

in a nutshell after I start printing, the printer activates the heating, begins to raise the Z axis and extrude (I don't know why you start extruding) and immediately afterwards the printer returns the cold extrusion error

if I write manually on the terminal m190 s70 the printer stops immediately and returns the same error that can be read in the logs so it is a problem with this command. in addition, with the command m109 t0 s220 the printer starts moving the Z axis up and immediately after it stops and turns off

I found the problem, it was the power loss that sent the printer into error, probably a firmware bug because this problem does not have it when printing from sd. probably doesn't know where to save the power loss data when printing from serial. thanks everyone for the support

Only a very few boards can detect a power loss in time (like the board on the Prusa MK3). These need a special signal from the power supply to indicate this.

If you suffer from a power issue in that way, that the 12V (or 24V) drop significantly under load - mostly it is enough for the 5V rail on the printer board - the logic still runs and the firmware detects no heating, but it does not know why. So the firmware pulls the emergency break. OctoPrint in the end is quite helpless.

OctoPrint can't do anything to help with power loss unfortunately, due to buffering on both OctoPrint's side and the printer's firmware, only the printer knows exactly where it is. Power loss recovery will only work when printing from the SD card, the only thing you could do for this is get a good UPS that would send a power panic signal to OctoPrint so it can stop sending, let the buffer run empty, save the data and then shut down. In reality, this is impractical for most and would require a custom plugin for the signals from the UPS supply.

it was working yesterday, now I have 2 Brother printers/scanner, different model that I try to scan and upload the scan on dropbox and it fail. Does dropbox have server down or any upgrades happen in last 24-48h???

I resolved this issue with my Brother MFC-L3710CW unit by logging into the machine and changing the TLS setting to 1.1/1.2. (192.168.... in web browser). It works with Dropbox Brother app now. It's always work for the MS OneDrive Brother app. You will need your units password to login to the administrator side of the Brother unit. Find it on the rear of the unit by the power cord input. Hope this helps!

Is this using a funciton that's built-in to the scanner? If so, you'll need to reach out to Brother for assistance. Brother would have created their own connection to Dropbox using the Dropbox API, and only Brother would be able to support that.

Did this post help you? If so, give it a Like below to let us know.

Need help with something else? Ask me a question!

Find Tips & Tricks Discover more ways to use Dropbox here!

Interested in Community Groups? Click here to join

Suddenly, scan to web into Dropbox didn't work anymore. Connection Error 03 on the display as soon as the scan usually is uploaded to Dropbox. Multiple MFC printers in different networks have the same issue. No network or printer setting was changed.

On one device I created a new Dropbox connection resulted in the same error at the end.

I'm having the exact same issue. Discovered it first last night, an hour or so before @hemzet wrote his last message here. Connection Error 03 saving to Dropbox, no settings changed. Using a Brother DCP-9020CDW. Internet says it's because of proxy settings, but all other features works just fine, including printing via wifi.

3a8082e126