How do I fix: "Job Abort Alert Job Aborted: Failure in UIO CreateAddressFromlP Address"

[wdb72]

This printer was working fine -- for years.  Then it decided on a vacation.  I need it back. 

There are analysis/repair articles online, but in such techy-ese I don't understand them.  It says there are 2 jobs stuck in the queue.  I tried to clear them without success.  I've tried disconnecting the beast and reconnecting -- no success.   The machine is connected via a wired setup.  My other printer (an HP inkjet is working fine using some sort of low powered BlueTooth connection.  Help.  PLEASE!!!!

[Hawks_Eye · Accepted solution]

Hi @wdb72 

Welcome to the HP Support Community! We're here to help you get back up and running.

Before diving into fixes, let’s slow down and gather the right details so we can isolate what’s really happening. That error message “Job Abort Alert Job Aborted: Failure in UIO CreateAddressFromIP Address” usually points to a communication breakdown between the computer and the printer, but the exact cause can vary depending on the setup. 

Let me probe a bit so we don’t waste time on the wrong path:

 

Key Details I Need From You

• Printer model: Which exact printer are we dealing with (brand + model)?
• Operating system: What computer OS are you running it on (Windows, macOS, Linux, etc.)?
• Connection type: You mentioned it’s wired — is that USB directly to the computer, or Ethernet to a router/network?
• Driver/software: Do you recall if you’re using the manufacturer’s driver package, or just the default OS driver?
• Error timing: Does the error pop up immediately when you try to print, or only after the job sits in the queue for a while?
• Other devices: Can other computers on the same network send jobs to this printer successfully, or is it failing everywhere?
• Queue behavior: You said two jobs are stuck — do they stay in “Printing” or “Error” status, or do they vanish after the abort alert?

 

Why I’m Asking

Each of these points helps narrow down whether this is:

• A driver/software issue (corrupt or outdated driver),
• A network/addressing issue (IP conflict, printer not reachable),
• Or a hardware/firmware hiccup (printer itself misbehaving).

Once I know the above, I can tailor the steps so they’re clear and not “techy-ese.”

Could you share those details with me? That way, I’ll know whether to guide you through clearing the stuck jobs, refreshing the driver, or checking the printer’s network address.

We're looking forward to helping you get back up and running! 

Regards, 

Hawks_Eye

Note: Do not share any of your personal information in public, such as serial number, phone number, email ID, etc.